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
Xen Minimal OS!
start_info: 0xd9f000(VA)
nr_pages: 0x80000
shared_inf: 0xba892000(MA)
pt_base: 0xda2000(VA)
nr_pt_frames: 0xb
mfn_list: 0x99f000(VA)
mod_start: 0x0(VA)
mod_len: 0
flags: 0x0
cmd_line: (hd0,0)/grub/menu.lst xencons=tty iommu=soft
stack: 0x95e960-0x97e960
MM: Init
_text: 0x0(VA)
_etext: 0x6e8d4(VA)
_erodata: 0x88000(VA)
_edata: 0x90c80(VA)
stack start: 0x95e960(VA)
_end: 0x99ef60(VA)
start_pfn: db0
max_pfn: 80000
Mapping memory range 0x1000000 - 0x80000000
setting 0x0-0x88000 readonly
skipped 0x1000
MM: Initialise page allocator for 11a9000(11a9000)-80000000(80000000)
MM: done
Demand map pfns at 80001000-2080001000.
Heap resides at 2080002000-4080002000.
Initialising timer interface
Initialising console ... done.
gnttab_table mapped at 0x80001000.
Initialising scheduler
Thread "Idle": pointer: 0x2080002050, stack: 0x15d0000
Initialising xenbus
Thread "xenstore": pointer: 0x2080002800, stack: 0x15e0000
Dummy main: start_info=0x97ea60
Thread "main": pointer: 0x2080002fb0, stack: 0x15f0000
Thread "pcifront": pointer: 0x2080003760, stack: 0x1600000
"main" "(hd0,0)/grub/menu.lst" "xencons=tty"
"iommu=soft"
pcifront_watches: waiting for backend path to appear device/pci/0/backend
vbd 51712 is hd0
******************* BLKFRONT for device/vbd/51712 **********
backend at /local/domain/0/backend/qdisk/3/51712
================== 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
================== ATTACHMENTS ============================
Hello Travis, pleas check /var/log/xen/domainname-dm.log. I think that Qemu is needed in this case of a PV guest. I had the same problem yesterday and the reason was that I forgot to install a special dependency in my case libsdl. In my case the boot stucked at some point and it wasn''t obvious that it was related to that. Eventually something in the portage package is wrong. Hope this would help. Best Regards 2013/2/24 Travis Osterman <tosterman@gmail.com>> 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 > Xen Minimal OS! > start_info: 0xd9f000(VA) > nr_pages: 0x80000 > shared_inf: 0xba892000(MA) > pt_base: 0xda2000(VA) > nr_pt_frames: 0xb > mfn_list: 0x99f000(VA) > mod_start: 0x0(VA) > mod_len: 0 > flags: 0x0 > cmd_line: (hd0,0)/grub/menu.lst xencons=tty iommu=soft > stack: 0x95e960-0x97e960 > MM: Init > _text: 0x0(VA) > _etext: 0x6e8d4(VA) > _erodata: 0x88000(VA) > _edata: 0x90c80(VA) > stack start: 0x95e960(VA) > _end: 0x99ef60(VA) > start_pfn: db0 > max_pfn: 80000 > Mapping memory range 0x1000000 - 0x80000000 > setting 0x0-0x88000 readonly > skipped 0x1000 > MM: Initialise page allocator for 11a9000(11a9000)-80000000(80000000) > MM: done > Demand map pfns at 80001000-2080001000. > Heap resides at 2080002000-4080002000. > Initialising timer interface > Initialising console ... done. > gnttab_table mapped at 0x80001000. > Initialising scheduler > Thread "Idle": pointer: 0x2080002050, stack: 0x15d0000 > Initialising xenbus > Thread "xenstore": pointer: 0x2080002800, stack: 0x15e0000 > Dummy main: start_info=0x97ea60 > Thread "main": pointer: 0x2080002fb0, stack: 0x15f0000 > Thread "pcifront": pointer: 0x2080003760, stack: 0x1600000 > "main" "(hd0,0)/grub/menu.lst" "xencons=tty" "iommu=soft" > pcifront_watches: waiting for backend path to appear device/pci/0/backend > vbd 51712 is hd0 > ******************* BLKFRONT for device/vbd/51712 ********** > > > backend at /local/domain/0/backend/qdisk/3/51712 > > ================== 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 > > ================== ATTACHMENTS ===========================> > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
>> >> 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. I think that Qemu is needed in > this case of a PV guest. I had the same problem yesterday and the reason was > that I forgot to install a special dependency in my case libsdl. In my case > the boot stucked at some point and it wasn''t obvious that it was related to > that. > > Eventually something in the portage package is wrong. Hope this would help. > > Best Regards > >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 Thanks again. -- T
>>> >>> 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 doneI 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
On Sun, 2013-02-24 at 21:57 +0000, Travis Osterman wrote:> 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).Looks like your disk backend isn''t getting setup. xl seems to want to use qemu for this. Does /usr/lib/xen/bin/qemu-system-i386 exist? Is there a qemu process running while the guest is booting? Do you get any logs in the /var/log/xen/*dm*.log relating to this domain?> Anyone have any guess why xen-tools 4.2.1 isn''t able to read my disk > image files? Everything worked in 4.1.Were you using xl or xm with Xen 4.1? Ian.
On Mon, Feb 25, 2013 at 4:30 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:> On Sun, 2013-02-24 at 21:57 +0000, Travis Osterman wrote: >> 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).Ian, thanks for the help, here are the answers.> Does /usr/lib/xen/bin/qemu-system-i386 exist?yes # ls /usr/lib/xen/bin/qemu-system-i386 /usr/lib/xen/bin/qemu-system-i386> Is there a qemu process running while the guest is booting?No. If I mount the image to a loopback device and boot the domain, I also do not have a qemu process (althought I''m not sure if I''m supposed to at that point.> Do you get any logs in the /var/log/xen/*dm*.log relating to this domain?# cat /var/log/xen/qemu-dm-prime.log bind(unix:/var/run/xen/qmp-libxl-4): No such file or directory chardev: opening backend "socket" failed: No such file or directory # ls /var/run/xen* /var/run/xenconsoled.pid /var/run/xenstored.pid /var/run/xenstored: socket socket_ro> Were you using xl or xm with Xen 4.1?xl So it looks like the lack of /var/run/xen/qmp-libxl-4 is contributing ... any idea where to head next? Thanks again. -- T
On Mon, 2013-02-25 at 14:42 +0000, Travis Osterman wrote:> On Mon, Feb 25, 2013 at 4:30 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote: > > On Sun, 2013-02-24 at 21:57 +0000, Travis Osterman wrote: > >> 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). > > Ian, thanks for the help, here are the answers. > > > Does /usr/lib/xen/bin/qemu-system-i386 exist? > > yes > # ls /usr/lib/xen/bin/qemu-system-i386 > /usr/lib/xen/bin/qemu-system-i386 > > > Is there a qemu process running while the guest is booting? > > No. If I mount the image to a loopback device and boot the domain, I > also do not have a qemu process (althought I''m not sure if I''m > supposed to at that point.I don''t think so, in the loopback case you will be using the in-kernel blkback driver. Only with file:// would you expect the qemu-base qdisk (or blktap, which your logs indicate you don''t have)> > Do you get any logs in the /var/log/xen/*dm*.log relating to this domain? > > # cat /var/log/xen/qemu-dm-prime.log > bind(unix:/var/run/xen/qmp-libxl-4): No such file or directory > chardev: opening backend "socket" failed: No such file or directory > > # ls /var/run/xen* > /var/run/xenconsoled.pid /var/run/xenstored.pid > > /var/run/xenstored: > socket socket_ro > > > Were you using xl or xm with Xen 4.1? > > xl > > So it looks like the lack of /var/run/xen/qmp-libxl-4 is contributing > ... any idea where to head next? Thanks again.I expect either libxl should have created this or qemu should, since qemu is complaining I assume libxl should have done it... Ah, you are missing the /var/run/xen/ directory so it is failing to create the socket, if you create the directory does it work? Although even if so it is obviously still a bug that libxl doesn''t handle that error... Ian.
>> >> 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). >> >> # cat /var/log/xen/qemu-dm-prime.log >> bind(unix:/var/run/xen/qmp-libxl-4): No such file or directory >> chardev: opening backend "socket" failed: No such file or directory >> >> # ls /var/run/xen* >> /var/run/xenconsoled.pid /var/run/xenstored.pid >> >> /var/run/xenstored: >> socket socket_ro > > Ah, you are missing the /var/run/xen/ directory so it is failing to > create the socket, if you create the directory does it work? Although > even if so it is obviously still a bug that libxl doesn''t handle that > error...Ian, I can confirm the manually creating /var/run/xen fixes the problem. I updated my bug report here https://bugs.gentoo.org/show_bug.cgi?id=459082 Thank you for the help. -- T
>>> >> 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). >>> >>> # cat /var/log/xen/qemu-dm-prime.log >>> bind(unix:/var/run/xen/qmp-libxl-4): No such file or directory >>> chardev: opening backend "socket" failed: No such file or directory >>> >>> # ls /var/run/xen* >>> /var/run/xenconsoled.pid /var/run/xenstored.pid >>> >>> /var/run/xenstored: >>> socket socket_ro >> >> Ah, you are missing the /var/run/xen/ directory so it is failing to >> create the socket, if you create the directory does it work? Although >> even if so it is obviously still a bug that libxl doesn''t handle that >> error... > > Ian, > > I can confirm the manually creating /var/run/xen fixes the problem. I > updated my bug report here > https://bugs.gentoo.org/show_bug.cgi?id=459082 > > Thank you for the help. >Similar error not solved by the above on a domain using pygrub (pvgrub works) /var/log/xen/qemu-dm-domain.log /var/tmp/portage/app-emulation/xen-tools-4.1.1-r6/work/xen-4.1.1/tools/ioemu-qemu-xen/hw/xen_blktap. c:628: Init blktap pipes Could not open /var/run/tap/qemu-read-2 Again loop device works fine. -- T
On Mon, 2013-02-25 at 22:47 +0000, Travis Osterman wrote:> >>> >> 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). > >>> > >>> # cat /var/log/xen/qemu-dm-prime.log > >>> bind(unix:/var/run/xen/qmp-libxl-4): No such file or directory > >>> chardev: opening backend "socket" failed: No such file or directory > >>> > >>> # ls /var/run/xen* > >>> /var/run/xenconsoled.pid /var/run/xenstored.pid > >>> > >>> /var/run/xenstored: > >>> socket socket_ro > >> > >> Ah, you are missing the /var/run/xen/ directory so it is failing to > >> create the socket, if you create the directory does it work? Although > >> even if so it is obviously still a bug that libxl doesn''t handle that > >> error... > > > > Ian, > > > > I can confirm the manually creating /var/run/xen fixes the problem. I > > updated my bug report here > > https://bugs.gentoo.org/show_bug.cgi?id=459082 > > > > Thank you for the help. > > > > Similar error not solved by the above on a domain using pygrub (pvgrub works) > > /var/log/xen/qemu-dm-domain.log > /var/tmp/portage/app-emulation/xen-tools-4.1.1-r6/work/xen-4.1.1/tools/ioemu-qemu-xen/hw/xen_blktap. > c:628: Init blktap pipes > Could not open /var/run/tap/qemu-read-2Do you have /var/run/tap ? I''m a bit surprised to see the qemu tap support getting activated, I didn''t think it was used for anything there days. Ian.
On Tue, Feb 26, 2013 at 3:11 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:> On Mon, 2013-02-25 at 22:47 +0000, Travis Osterman wrote: >> >>> >> 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). >> >>> >> >>> # cat /var/log/xen/qemu-dm-prime.log >> >>> bind(unix:/var/run/xen/qmp-libxl-4): No such file or directory >> >>> chardev: opening backend "socket" failed: No such file or directory >> >>> >> >>> # ls /var/run/xen* >> >>> /var/run/xenconsoled.pid /var/run/xenstored.pid >> >>> >> >>> /var/run/xenstored: >> >>> socket socket_ro >> >> >> >> Ah, you are missing the /var/run/xen/ directory so it is failing to >> >> create the socket, if you create the directory does it work? Although >> >> even if so it is obviously still a bug that libxl doesn''t handle that >> >> error... >> > >> > Ian, >> > >> > I can confirm the manually creating /var/run/xen fixes the problem. I >> > updated my bug report here >> > https://bugs.gentoo.org/show_bug.cgi?id=459082 >> > >> > Thank you for the help. >> > >> >> Similar error not solved by the above on a domain using pygrub (pvgrub works) >> >> /var/log/xen/qemu-dm-domain.log >> /var/tmp/portage/app-emulation/xen-tools-4.1.1-r6/work/xen-4.1.1/tools/ioemu-qemu-xen/hw/xen_blktap. >> c:628: Init blktap pipes >> Could not open /var/run/tap/qemu-read-2 > > Do you have /var/run/tap ? > > I''m a bit surprised to see the qemu tap support getting activated, I > didn''t think it was used for anything there days. > > Ian. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-usersI didn''t have it, but created the directory as before. That didn''t seem to fix things this time. I''m not familar with tap but here are the open tap libraries on my system currently. # lsof | grep -i tap xl 8451 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 xl 8451 8452 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 xl 18198 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 xl 18198 18199 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 qemu-dm 18580 root mem REG 253,0 18152 1462242 /usr/lib64/libblktap.so.3.0.0 qemu-dm 18580 18582 root mem REG 253,0 18152 1462242 /usr/lib64/libblktap.so.3.0.0 qemu-dm 18580 18583 root mem REG 253,0 18152 1462242 /usr/lib64/libblktap.so.3.0.0 xl 18671 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 xl 18671 18672 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 The 4.2 series of ebuilds really did a number on my setup (which had been previously working in 4.1). Here is the summary of changes I''ve noticed with the upgrade: pvgrub + file:/*.img: mkdir /var/run/xen does not get created so added a script to /etc/local.d as workaround (fixes) and didn''t need /var/run/tap created pygrub + file:/*.img:also seems to want /var/run/tap, after creating that, still no xvda. I didnt'' get a chance to troubleshoot that any further as I wasn''t home last evening and wanted to leave the domain up with /dev/loop hvm + file:/*.img: a windows domain would no boot normally even after the above directories were created /var/log/*dm*.log Using xvda for guest''s hda Strip off blktap sub-type prefix to /tank/xen/dev/winxp.img (drv ''aio'') Using file /tank/xen/dev/winxp.img in read-write mode That looks like the disk was being loaded fine. I was able to log in via safe mode and found the gplpv drivers wouldn''t load (which worked fine in 4.1). I''m getting around the pygrub and hvm currently by manually creating /dev/loop devices and using phy:/dev/loop in my disk config line. I''ll try to give some more debug information later. I''m not sure if others are having problems but wish 4.2 hadn''t been unmasked in portage quite yet. -- T
On Tue, 2013-02-26 at 14:04 +0000, Travis Osterman wrote:> > I''m a bit surprised to see the qemu tap support getting activated, I > > didn''t think it was used for anything there days.> I didn''t have it, but created the directory as before. That didn''t > seem to fix things this time. I''m not familar with tap but here are > the open tap libraries on my system currently.So I asked around and there is basically no way the qemu-xen-trad blktap module should be active for any reason in a Xen 4.2 system with xl. That is the deadest of dead code... Could you send a full set of logs (xl -vvv create, /var/log/xen/*) and your guest config for this new issue please. Ian.
> So I asked around and there is basically no way the qemu-xen-trad blktap > module should be active for any reason in a Xen 4.2 system with xl. That > is the deadest of dead code... > > Could you send a full set of logs (xl -vvv create, /var/log/xen/*) and > your guest config for this new issue please.Here is the full report from a freshly rebooted server. /* * Fresh reboot, all xl-related services off */ # emerge --info http://pastebin.com/XBK7fwXm # lsof -X | grep -i tap (nothing) # ls -R /var/run/{xen,tap} /var/run/tap: /var/run/xen: # ps -e | grep "xl\|qemu\|xen" 48 ? 00:00:00 xenwatch 49 ? 00:00:00 xenbus 713 ? 00:00:00 xen_pciback_wor /* * bringing up xenstored */ # /etc/init.d/xenstored start * Starting xenstored daemon ... * Setting domain0 name record # lsof -X | grep -i tap (nothing) # ls -R /var/run/{xen,tap} /var/run/tap: st /var/run/xen: # ps -e | grep "xl\|qemu\|xen" 48 ? 00:00:00 xenwatch 49 ? 00:00:00 xenbus 713 ? 00:00:00 xen_pciback_wor 9264 ? 00:00:00 xenstored /* * bringing up xenconsoled (previously in default runlevel) */ # /etc/init.d/xenconsoled start * Starting xenconsoled daemon ... [ ok ] # lsof -X | grep -i tap # ls -R /var/run/{xen,tap} /var/run/tap: /var/run/xen: xen ~ # ps -e | grep "xl\|qemu\|xen" 48 ? 00:00:00 xenwatch 49 ? 00:00:00 xenbus 713 ? 00:00:00 xen_pciback_wor 9264 ? 00:00:00 xenstored 9288 ? 00:00:00 xenconsoled /* * just dom0 started */ # xl list Name ID Mem VCPUs State Time(s) Domain-0 0 32106 8 r----- 52.7 # xl info http://pastebin.com/fx0F4cbm # xl dmesg http://pastebin.com/cX9b3Yt5 # grep ^[^[:space:]*#] /data/xen/prime.pv name = "prime" memory = 2048 vcpus=8 vif=[''bridge=xenbr0,mac=00:16:3E:1F:B8:0E,ip=192.168.1.1''] disk = [''file:/data/xen/prime.img,xvda,w''] kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz" extra = "(hd0,0)/grub/menu.lst xencons=tty iommu=soft" on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' /* * PV using pvgrub (with manually creating /var/run/xen */ # xl -vvv create /data/xen/prime.pv http://pastebin.com/FMTWAqJd # xl list Name ID Mem VCPUs State Time(s) Domain-0 0 29606 8 r----- 56.4 prime 1 2048 8 -b---- 33.9 /* * I needed to attach a couple NICs to finish brining my router online */ # xl pci-attach prime 0000:01:00.0 # xl pci-attach prime 0000:0a:00.0 /* * libblktapctl is up now */ # lsof -X | grep -i tap xl 9387 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 xl 9387 9388 root mem REG 253,0 30400 1462266 /usr/lib64/libblktapctl.so.1.0.0 # ls -R /var/run/{xen,tap} /var/run/tap: /var/run/xen: qmp-libxl-1 # ps -e | grep "xl\|qemu\|xen" 48 ? 00:00:00 xenwatch 49 ? 00:00:00 xenbus 713 ? 00:00:00 xen_pciback_wor 9264 ? 00:00:00 xenstored 9288 ? 00:00:00 xenconsoled 9327 ? 00:00:00 qemu-system-i38 9387 ? 00:00:00 xl # ls -1 /var/log/xen/*prime*.log /var/log/xen/qemu-dm-prime.log /var/log/xen/xl-prime.log # cat /var/log/xen/qemu-dm-prime.log xen ~ # cat /var/log/xen/xl-prime.log Waiting for domain prime (domid 1) to die [pid 9387] libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0x627c10 wpath=@releaseDomain token=3/0: register slotnum=3 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x627c10 wpath=@releaseDomain token=3/0: event epath=@releaseDomain libxl: debug: libxl.c:1015:domain_death_xswatch_callback: [evg=0x6299d0:1] from domid=1 nentries=1 rc=1 libxl: debug: libxl.c:1026:domain_death_xswatch_callback: [evg=0x6299d0:1] got=domaininfos[0] got->domain=1 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 /************************************************************************* * PV with pygrub */ # grep ^[^[:space:]*#] /tank/xen/config/spot.pv.orig name = "spot" memory = 2048 bootloader = "pygrub" vcpus=4 vif=[''bridge=xenbr0,mac=00:16:3E:21:56:66,ip=192.168.1.30''] disk = [''file:/tank/xen/dev/spot.img,xvda,w''] # which pygrub /usr/bin/pygrub /* * boot via pygrub using img file */ # xl -vvv create /tank/xen/config/spot.pv.orig http://pastebin.com/x1GHPXTP /* * in the console */ http://pastebin.com/kiGchPx7 Key type dns_resolver registered registered taskstats version 1 XENBUS: Waiting for devices to initialise: 25s...20s...15s...10s...5s...0s...235s...230s...225s...220s...215s...210s... ............ :: Scanning for raid10...raid10 loaded. :: Scanning for linear...linear loaded. :: Scanning for multipath...multipath loaded. :: Scanning for e1000...e1000 loaded. :: Scanning for tg3...libphy, tg3 loaded. :: Scanning for scsi_transport_iscsi...scsi_transport_iscsi loaded. :: Scanning for libiscsi...libiscsi loaded. :: Scanning for cbc...cbc loaded. :: Scanning for aes-x86_64...aes-x86_64 loaded. :: Scanning for xts...gf128mul, xts loaded.>> Hint: Use parameter scandelay[=seconds] if you need waiting here >> Determining root device...!! Block device /dev/xvda2 is not a valid root device... !! Could not find the root block device in . Please specify another value or: press Enter for the same, type "shell" for a shell, or "q" to skip... root block device() :: shell # ls /dev/sd* ls: /dev/sd*: No such file or directory # ls /dev/hd* ls: /dev/hd*: No such file or directory # ls /dev/xv* ls: /dev/xv*: No such file or directory # exit /* * Logs */ # ls -1 /var/log/xen/*spot*.log /var/log/xen/qemu-dm-spot.log /var/log/xen/xl-spot.log # cat /var/log/xen/qemu-dm-spot.log (empty) # cat /var/log/xen/xl-spot.log Waiting for domain spot (domid 2) to die [pid 9749] libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0x628a30 wpath=@releaseDomain token=3/0: register slotnum=3 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x628a30 wpath=@releaseDomain token=3/0: event epath=@releaseDomain libxl: debug: libxl.c:1015:domain_death_xswatch_callback: [evg=0x625020:2] from domid=2 nentries=1 rc=1 libxl: debug: libxl.c:1026:domain_death_xswatch_callback: [evg=0x625020:2] got=domaininfos[0] got->domain=2 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 /* * loop workaround */ # losetup /dev/loop0 /tank/xen/dev/spot.img # xl -vvv create /tank/xen/config/spot.pv http://pastebin.com/nDmmftqA (works fine) I hope this helps. Sorry for the long email. -- T