[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] pv guest fails to start after 4.2 upgrade


  • To: xen-users <xen-users@xxxxxxxxxxxxx>
  • From: Travis Osterman <tosterman@xxxxxxxxx>
  • Date: Sun, 24 Feb 2013 16:57:48 -0500
  • Delivery-date: Sun, 24 Feb 2013 21:59:31 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>

>>>
>>> I'm running xen on gentoo (3.7.0 hardened) and upgraded from 4.1 to
>>> 4.2 yesterday as 4.2 is marked as stable in the portage tree.
>>> Afterwards, I cannot start my guests and get the following error
>>> (currently running 4.2.1).  Any help in troubleshooting would be
>>> greatly appreciated.  Thanks in advance.
>>>
>>> -- T
>>>
>>> # xl create -c /data/xen/prime.pv
>>> libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 3
>>> device model: spawn failed (rc=-3)
>>> libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error:
>>> No such file or directory
>>> Daemon running with PID 8701
> ...
>>>
>>> ================== ATTACHMENTS ============================
>>>
>>> xl -vvv create -c /data/xen/prime.pv
>>> http://pastebin.com/92PW3QRH
>>>
>>> xl dmesg
>>> http://pastebin.com/ba2Xxv7w
>>>
>>> emerge --info (system info)
>>> http://pastebin.com/VKSfKjCW
>>>
>> Hello Travis,
>>
>> pleas check /var/log/xen/domainname-dm.log. ... reason was
>> that I forgot to install a special dependency in my case libsdl
>
> I have media-libs/libsdl-1.2.15-r2 installed.  No change after rebuilding.
>
> Here is the guest log:
>
> # cat /var/log/xen/xl-prime.log
> Waiting for domain prime (domid 8) to die [pid 14679]
> libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch
> w=0x626cf0 wpath=@releaseDomain token=3/0: register slotnum=3
> libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x626cf0
> wpath=@releaseDomain token=3/0: event epath=@releaseDomain
> libxl: debug: libxl.c:1015:domain_death_xswatch_callback:
> [evg=0x624fe0:8] from domid=8 nentries=1 rc=1
> libxl: debug: libxl.c:1026:domain_death_xswatch_callback:
> [evg=0x624fe0:8]   got=domaininfos[0] got->domain=8
> libxl: debug: libxl.c:1053:domain_death_xswatch_callback:  exists
> shutdown_reported=0 dominf.flags=ffff0020
> libxl: debug: libxl.c:1019:domain_death_xswatch_callback: [evg=0] all reported
> libxl: debug: libxl.c:1083:domain_death_xswatch_callback: domain death
> search done

I also tried to take pvgrub out of the picture so I mounted the image
and copied my initrd and kernel to the dom0 file system and updated my
config with the appropriate ramdisk and kernel lines.

Full output without pvgrub
http://pastebin.com/c7VWWwXk

Which dropped me in a shell asking for my root partition (progress).
No /dev/xvd? or /dev/sd? listed so I shut down the guest and mounted
my disk as a physical device (via loopback) instead of image.  Here
was a the change:

/data/xen/prime.pv
(-)disk = ['file:/data/xen/prime.img,xvda,w']
(+)disk = ['phy:/dev/loop0p2,xvda,w']
(-)kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz"
(+)kernel = "/data/xen/kernel-genkernel-x86_64-3.7.5-hardened-2013-02-18-1632"
(+)ramdisk = 
"/data/xen/initramfs-genkernel-x86_64-3.7.5-hardened-2013-02-18-1632"

Anyone have any guess why xen-tools 4.2.1 isn't able to read my disk
image files?  Everything worked in 4.1.

Thanks.

-- T

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.