https://bugzilla.novell.com/show_bug.cgi?id=465379 User novell-web@zmi.at added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c1 Michael Monnerie changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |novell-web@zmi.at --- Comment #1 from Michael Monnerie 2009-01-12 07:53:43 MST --- One more thing: After trying a startup, I have this in dom0: *********************************** # xm block-list 0 Vdev BE handle state evt-ch ring-ref BE-path 51952 0 0 4 30 8 /local/domain/0/backend/tap/0/51952 *********************************** Trying to remove it does not work: *********************************** # xm block-detach 0 xvdp Error: Device 51952 not connected Usage: xm block-detach <Domain> <DevId> [-f|--force] Destroy a domain's virtual block device. *********************************** But I have no more reference to that file, and it's definitely xvdp: # l /dev/xv* crw-rw---- 1 root root 204, 191 12. Jan 14:33 /dev/xvc0 brw-rw---- 1 root root 202, 240 12. Jan 15:32 /dev/xvdp brw-rw---- 1 root root 202, 241 12. Jan 15:32 /dev/xvdp1 brw-rw---- 1 root root 202, 242 12. Jan 15:32 /dev/xvdp2 # pvscan PV /dev/dm-2 VG mailsrv-vg lvm2 [25,33 GB / 0 free] Total: 1 [25,33 GB] / in use: 1 [25,33 GB] / in no VG: 0 [0 ] # lvscan inactive '/dev/mailsrv-vg/mailsrv-data' [25,33 GB] inherit # lsof -n|grep xvd tapdisk-i 7073 root 2u REG 253,0 32212254720 13328 /disks/daten/xen/mailsrv/root20080923.xvd Why does tapdisk-ioemu still have a reference? And how to remove it? I did a "kill 7073" now, but XEN didn't react anymore, had to reboot the whole machine. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=465379 User kwolf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c2 --- Comment #2 from Kevin Wolf 2009-01-12 10:03:58 MST --- Let me see if I understand your scenario: You're using a VM config which is pretty much standard, i.e. the guest harddisk is file-based and that file is accessed through file: (works) or tap:aio: (doesn't work). The one special thing about your setup is that the guest uses LVM for everything (including /boot), so to extract the kernel domUloader needs to attach the file first and then we need to bring up the LVM volumes on top of that. Is that the right description? What guest OS are you using? Is the assumption right that you are using domUloader and not pygrub? The relevant log files are /var/log/messages, /var/log/xen/tapdisk-ioemu.log and possibly /var/log/xen/qemu-dm-$YOUR_VM_NAME.log. Could you please attach the corresponding log file snippets (if in doubt, attach the complete files) after a failed VM start? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=465379 User novell-web@zmi.at added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c4 --- Comment #4 from Michael Monnerie 2009-01-16 16:45:56 MST --- I will attach all the files you mentioned. LVM is just for the data partition, my xen virtual disks are all partitioned (xvdp1 in above case is /, xvdp2 is /disks/data). So booting is no problem. domUloader is used, as I found this in an example on the Novell site. Didn't know about pygrub, is that the preferred thing to use now? Do you have a link to more info at hand? Right now I had a problem again. A xen host didn't react when trying to "xm create mailsrv2", so I tried looking with "xm block-list 0", which also just blocked. CTRL-C and "rcxend restart" helped, then I got this output: # xm block-list 0 Vdev BE handle state evt-ch ring-ref BE-path 51952 0 0 1 -1 -1 /local/domain/0/backend/tap/0/51952 How to get rid of this? I simply restarted the whole machine, then the domU started (autostart via xendomains) normally. I would really like to find the problem, as we want to use XEN in production. Here's the xen config I use for the domU: # cat /etc/xen/auto/mailsrv2 name="mailsrv2" uuid="07b3b164-721e-70ec-0d5e-d79a4c65f0fb" memory=600 maxmem=4000 vcpus=1 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" localtime=0 keymap="de" builder="linux" # this lines active during install time: #kernel="/boot/xen-install-kernel" #ramdisk="/boot/xen-install-initrd" # this lines activate during normal boot time: bootloader="/usr/lib/xen/boot/domUloader.py" bootargs="--entry=xvda1:/boot/vmlinuz-xen,/boot/initrd-xen" #extra=" ssh=1 root=/dev/xvda1 install=hd:/dev/xvdz " extra=" root=/dev/xvda1 " boot="c" disk=[ 'tap:aio:/disks/daten/xen/mailsrv2/root20090113.xvd,xvda,w', 'tap:aio:/disks/daten/xen/mailsrv2/work20090116.xvd,xvdb,w', 'tap:aio:/disks/daten/xen/mailsrv2/data20090115.xvd,xvdc,w', 'tap:aio:/disks/daten/xen/mailsrv2/swap20090113.xvd,xvdd,w', 'tap:cdrom:/disks/daten/dvd/openSUSE-11.1-DVD-x86_64.iso,xvdz,r', ] vif=[ 'mac=00:16:3e:10:00:31,bridge=br0', 'mac=00:16:3e:00:00:01,bridge=br1', ] vfb=['type=vnc,vncunused=1'] -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=465379 User kwolf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c6 --- Comment #6 from Kevin Wolf 2009-01-19 03:29:51 MST --- I think we have two separate problems here. The first one is that tapdisk-ioemu/qemu sometimes fails to open your images. Your tapdisk-ioemu.log contains several times "Could not open image file /disks/daten/xen/mailsrv2/root20090115.xvd". From reading the code I can't tell what's going wrong, this isn't doing anything special. If you can't think of a reason why the image really wouldn't be accessible, I would need to have this reproduced with more debugging code. The second problem seems to be that the failed open results in a block device which is in some strange state between attached and detached. I will try if I can reproduce at least this one. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=465379 User kwolf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c8 --- Comment #8 from Kevin Wolf 2009-01-19 09:50:17 MST --- It might not be obvious what xvdp is for, but that's easy to explain. If you use domUloader (or pygrub) instead of directly specifying kernel and initrd in the config, domUloader needs to extract the kernel from the guest's /boot. So it temporarily attaches your image to xvdp on the host and mounts the right partition. In your case the attach fails inside tapdisk-ioemu for an unknown reason but the error handling doesn't notice that (so the second problem is only revealed by the first one). The good news is that it's easy for me to provoke such failure and I'm currently trying to understand what's happening in all detail. So for the second problem I might find a solution soon, but for the first one I still don't have a clue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=465379 User kwolf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c10 Kevin Wolf changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |novell-web@zmi.at --- Comment #10 from Kevin Wolf 2009-01-30 05:47:11 MST --- Forgot to set NEEDINFO. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=465379 User novell-web@zmi.at added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c12 Michael Monnerie changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|novell-web@zmi.at | --- Comment #12 from Michael Monnerie 2009-02-04 10:45:02 MST --- Created an attachment (id=270095) --> (https://bugzilla.novell.com/attachment.cgi?id=270095) Logs needed to see problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=465379 User kwolf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c14 Kevin Wolf changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |novell-web@zmi.at --- Comment #14 from Kevin Wolf 2009-02-04 11:34:24 MST --- I actually wouldn't have expected the new package to resolve the root of your problems (I still can't explain what's going on). However, in any case you should no longer see disks in a "half-attached" state as mentioned in comment #1 where the device doesn't really appear, but you also can't detach it any more. I also didn't see these failures in the logs again, so can you confirm this? Do you still have problems with attaching or detaching xvdp if you start the VMs manually? Do the problems also occur if you manually try to xm block-attach/block-detach an image to Dom0? For the freezes please open another bug report. Of course without additional information it's unlikely that we can do anything about it. Is there no chance to attach a serial console to catch the crash dumps? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=465379 User jdouglas@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c16 --- Comment #16 from Jason Douglas 2009-02-04 17:55:17 MST --- (In reply to comment #15)

Can you explain me how to attach a serial console? A null modem cable from a notebook to the server? But what to set up? Never did that...

http://en.opensuse.org/How_to_Capture_Xen_Hypervisor_and_Kernel_Messages_usi... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=465379 User kwolf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c18 Kevin Wolf changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |novell-web@zmi.at --- Comment #18 from Kevin Wolf 2009-02-10 04:57:37 MST --- Any news here? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=465379 User novell-web@zmi.at added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c20 Michael Monnerie changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|novell-web@zmi.at | --- Comment #20 from Michael Monnerie 2009-02-13 10:20:26 MST --- I just have the problem again. My daughter (3.5 years) switched of the power behind the UPS for the server running XEN. So I installed your tools now, and made /etc/init.d/xen restart. It didn't start then. So I rebooted the machine again - it works now! BTW: When I "xm list", there's an old version of my xen mailserver which I cannot get rid of: # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 2768 2 r----- 36.6 mailsrv 400 1 450.3 mailsrv2 1 1200 2 -b---- 12.4 orion:~ # xm destroy mailsrv orion:~ # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 2768 2 r----- 37.1 mailsrv 400 1 450.3 mailsrv2 1 1200 2 -b---- 12.4 How can I remove that? Is that also a problem with the xen-tools I guess? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.