Re: [Xen-devel] Problem starting HVM guest in Xen 4.3 RC6 when NOT using device_model_version="qemu-xen-traditional"

[Sander Eikelenboom <linux@xxxxxxxxxxxxxx>]

Saturday, June 29, 2013, 4:33:49 PM, you wrote:

> On 29/06/13 14:13, Sander Eikelenboom wrote:
>> Saturday, June 29, 2013, 2:47:40 PM, you wrote:
>>
>>> On 29/06/13 13:36, Sander Eikelenboom wrote:
>>>> Saturday, June 29, 2013, 1:33:06 PM, you wrote:
>>>>
>>>>
>>>>>> Also, in 'var/log/xen/qemu-dm-win.log' it says:-
>>>>>>
>>>>>> qemu-system-i386: Property 'isa-fdc.driveA' can't find value ''
>>>>>>
>>>>>> Which might be my overall issue.
>>>>>>
>>>>>> _______________________________________________
>>>>>> Xen-devel mailing list
>>>>>> Xen-devel@xxxxxxxxxxxxx
>>>>>> http://lists.xen.org/xen-devel
>>>>> When I manually comment out the patch "tools/libxl: Disable useless
>>>>> empty floppy drive with qemu-xen"  -
>>>>> http://lists.xen.org/archives/html/xen-devel/2013-02/msg00391.html
>>>>> ....I get...
>>>>> root@xen6:~/xensource/xen# xl create /etc/xen/win
>>>>> Parsing config from /etc/xen/win
>>>>> xc: info: VIRTUAL MEMORY ARRANGEMENT:
>>>>>      Loader:        0000000000100000->000000000019eac8
>>>>>      Modules:       0000000000000000->0000000000000000
>>>>>      TOTAL:         0000000000000000->000000007f800000
>>>>>      ENTRY ADDRESS: 0000000000100000
>>>>> xc: info: PHYSICAL MEMORY ALLOCATION:
>>>>>      4KB PAGES: 0x0000000000000200
>>>>>      2MB PAGES: 0x00000000000003fb
>>>>>      1GB PAGES: 0x0000000000000000
>>>>> Daemon running with PID 22958
>>>>> Starts up fine and is accessible via VNC (albeit with a stupid
>>>>> resolution). I am not sure why this has affected me and not everyone
>>>>> else. I assume "not everyone" for obvious reasons.
>>>> You are not having any line that mentions "floppy" in your .cfg ?
>>>>
>>>>
>>> Only in a comment:-
>>> builder='hvm'
>>> memory = '2048'
>>> name = 'win'
>>> # boot on floppy (a), hard disk (c) or CD-ROM (d)
>>> boot='c'
>>> disk = [ 'phy:/dev/xen6/win-root,hda,w' ]
>>> vcpus=2
>>> vnc=1
>>> vncviewer=0
>>> vnclisten="0.0.0.0"
>>> vncpasswd='win'
>>> vif=['mac=00:16:31:01:01:01,bridge=eth0']
>>> on_poweroff = 'destroy'
>>> on_reboot   = 'restart'
>>> on_crash    = 'restart'
>>> usbdevice='tablet'
>> Hmm just checked, xl generates that line for my HVM's as well, though they 
>> do start.
>> And i don't get that line in my qemu-dm.log
> Sorry, which line gets generated?

I don't have the error "qemu-system-i386: Property 'isa-fdc.driveA' can't find 
value ''", although my hvm's qemu also gets the "-global isa-fdc.driveA=" 
passed to it

>>
>> Are you sure it runs the qemu that is installed with you last build ?
> There was a qemu lying around at 
> /usr/local/lib/xen/bin/qemu-system-i386, which I renamed. This made no 
> difference. I renamed /usr/lib/xen/bin/qemu-system-i386 expecting the 
> create to fail badly but is succeeded. It seemed to be falling back to 
> using gemu-dm.

> So I re-performed make tools-install and the create tried again with 
> qemu-system-i386 but again failed. (slight differences of the error 
> messages, though... but ultimately the same, I think).

> ....
> libxl: debug: libxl_dm.c:1208:libxl__spawn_local_dm: 
> file=/dev/xen6/win-root,if=ide,index=0,media=disk,format=raw,cache=writeback
> libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch 
> w=0x1190380 wpath=/local/domain/0/device-model/30/state token=3/1: 
> register slotnum=3
> libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x1190380 
> wpath=/local/domain/0/device-model/30/state token=3/1: event 
> epath=/local/domain/0/device-model/30/state
> libxl: debug: libxl_event.c:596:libxl__ev_xswatch_deregister: watch 
> w=0x1190380 wpath=/local/domain/0/device-model/30/state token=3/1: 
> deregister slotnum=3
> libxl: error: libxl_dm.c:1275:device_model_spawn_outcome: domain 30 
> device model: spawn failed (rc=-3)

> ....


>> And in fact it is the latest ?
>>
>> Hrmmm it seems a make clean && git pull && make in the xen dir, does update 
>> the commit id for the qemu tree in Config.mk
>> But the tree it self in /tools/qemu-xen-dir doesn't seem to be updated 
>> accordingly ..
>>
>> Could it be your tools/qemu-xen-dir is also not on the latest commit ?

> This is beyond my knowledge, to please persevere with me :)

> Here are what I think are the relevant bits of my Config.mk. That qemu 
> commit ID seems to match the change in the last commit before RC6, 
> according to gitweb.

> How can I tell if tools/qemu-xen-dir matches this?

Just do a git log in the tools/qemu-xen-dir and seem what the latest commit is 
(and compare to what it should be according to the Config.mk).
When you are working with an old xen clone it seems you also have the change 
running an old(er) qemu since it doesn't seem to be auto updated to the commit 
id from the Config.mk

> I think I will make a new clone of Xen.

A fresh clone should fix that up since that also pulls a fresh qemu tree in.

> Thanks for all your help.


> ifeq ($(GIT_HTTP),y)
> OVMF_UPSTREAM_URL ?= http://xenbits.xen.org/git-http/ovmf.git
> QEMU_UPSTREAM_URL ?= 
> http://xenbits.xen.org/git-http/qemu-upstream-unstable.git
> SEABIOS_UPSTREAM_URL ?= http://xenbits.xen.org/git-http/seabios.git
> else
> OVMF_UPSTREAM_URL ?= git://xenbits.xen.org/ovmf.git
> QEMU_UPSTREAM_URL ?= git://xenbits.xen.org/qemu-upstream-unstable.git
> SEABIOS_UPSTREAM_URL ?= git://xenbits.xen.org/seabios.git
> endif
> OVMF_UPSTREAM_REVISION ?= b0855f925c6e2e0b21fbb03fab4b5fb5b6876871
> QEMU_UPSTREAM_REVISION ?= 1c514a7734b7f98625a0d18d5e8ee7581f26e50c
> SEABIOS_UPSTREAM_TAG ?= 3a28511b46f0c2af5fae1b6ed2b0c19d7913cee3
> # Wed Jun 26 16:30:45 2013 +0100
> # xen: Don't perform SMP setup.

> ETHERBOOT_NICS ?= rtl8139 8086100e

> # Specify which qemu-dm to use. This may be `ioemu' to use the old
> # Mercurial in-tree version, or a local directory, or a git URL.
> # CONFIG_QEMU ?= `pwd`/$(XEN_ROOT)/../qemu-xen.git
> CONFIG_QEMU ?= $(QEMU_REMOTE)

> QEMU_TAG ?= 13c144d96e825f145e5b37f97e5f6210c2c645e9



>>
>>
>> --
>> Sander
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxx
>> http://lists.xen.org/xen-devel




_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel