https://bugzilla.novell.com/show_bug.cgi?id=645251 https://bugzilla.novell.com/show_bug.cgi?id=645251#c1 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |pmillett@novell.com QAContact|qa@suse.de |jdouglas@novell.com --- Comment #1 from James Fehlig 2010-10-14 06:12:43 UTC --- Preston, Can you reproduce this issue with latest 11.3 xen packages? If so I would also expect the issue to exist in SLES11 SP1 since they are tracking closely. You could even try to reproduce in SP1 if that is more convenient. Thanks! -- 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=645251 https://bugzilla.novell.com/show_bug.cgi?id=645251#c3 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |pgngw+dev001+novell.com@f-m | |.fm --- Comment #3 from James Fehlig 2010-10-19 04:37:05 UTC --- I've had some time to look at this bug but the only issue I've noticed is a bootloader problem when bootargs is specified in the domain config, e.g. xen41:~ # grep bootargs /etc/xen/vm/os11.3-pv bootargs="3" xen41:~ # xm create /etc/xen/vm/os11.3-pv Using config file "/etc/xen/vm/os11.3-pv". Error: Boot loader didn't return any data! If bootargs is empty (bootargs="") the domain is created as expected. But I think this is a different error than you are seeing right? Regardless, what is your domain config? Does domUloader work? It can be used in place of pygrub (default) by replacing bootloader and bootargs in domain config with e.g. bootloader="/usr/lib/xen/boot/domUloader.py" bootargs="--entry=xvda2:/boot/vmlinuz-xen,/boot/initrd-xen" -- 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=645251 https://bugzilla.novell.com/show_bug.cgi?id=645251#c5 dev001x _ changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|pgngw+dev001+novell.com@f-m | |.fm | --- Comment #5 from dev001x _ 2010-10-19 05:45:27 UTC --- hm ... rereading ... i'm not sure you ARE suggesting using domUloader.py for the Ubuntu Guest. fyi, _all_ of my openSUSE domU's always _do_ use domUloader.py. e.g., here's an example of a domain config for a guest that, as above, works perfectly with 'old' xen, fails with 'new' xen: ---------- name = 'fw' builder = 'linux' bootloader = '/usr/lib/xen/boot/domUloader.py' bootargs = '--entry=xvda1:vmlinuz-xen,/boot/initrd-xen' disk = [ 'phy:/dev/VG0/fw_boot,xvda,w', 'phy:/dev/VG0/fw_swap,xvdb,w', 'phy:/dev/VG0/fw_root,xvdc,w', ] root = '/dev/xvdc1' vif = [ 'mac=00:16:3E:02:00:00, bridge=br0, vifname=vif.fw'] pci = [ '02:00.0', '04:00.0'] vfb = [ 'type=vnc, vncdisplay=200, vnclisten=127.0.0.1' ] extra = 'textmode=1 xencons=xvc0 elevator=noop swiotlb=force' localtime = 0 on_shutdown = 'destroy' on_reboot = 'restart' on_crash = 'destroy' maxmem = 512 memory = 512 vcpus = 4 cpu_cap = 0 cpu_weight = 384 ---------- can you clarify what you need 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=645251 https://bugzilla.novell.com/show_bug.cgi?id=645251#c7 --- Comment #7 from dev001x _ 2010-10-19 06:01:22 UTC --- (In reply to comment #6)

Is this bug about openSUSE 11.3 domUs failing to start? Thanks :-)

yes, it is. i'd mistakenly thought you might be giving me a way -- using domUbootloader -- to launch Ubuntu while staying on 'old' xen, where my openSUSE domUs work. :-/ so, to be clear ... yes, the problem _is_ openSUSE domUs don't launch after switching to the 'new' xen, which is atm required to launch an Ubuntu 10.04.1 run-time domU. thanks. -- 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=645251 https://bugzilla.novell.com/show_bug.cgi?id=645251#c9 --- Comment #9 from dev001x _ 2010-10-19 15:20:30 UTC --- (In reply to comment #8)

What kernel versions in dom0 and domU?

@ Dom0, uname -a Linux server 2.6.34.7-0.4-xen #1 SMP 2010-10-07 19:07:51 +0200 x86_64 x86_64 x86_64 GNU/Linux rpm -qa | grep xen- xen-4.0.1_21326_01-1.1.x86_64 xen-libs-4.0.1_21326_01-1.1.x86_64 xen-tools-4.0.1_21326_01-1.1.x86_64 kernel-xen-2.6.34.7-0.4.1.x86_64 kernel-xen-devel-2.6.34.7-0.4.1.x86_64 @ DomU uname -a Linux fw 2.6.34.7-0.4-xen #1 SMP 2010-10-07 19:07:51 +0200 x86_64 x86_64 x86_64 GNU/Linux rpm -qa | grep xen- kernel-xen-2.6.34.7-0.4.1.x86_64 xen-libs-4.0.0_21091_06-0.1.1.x86_64 xen-tools-domU-4.0.0_21091_06-0.1.1.x86_64

Can you attach /var/log/boot.msg and /var/log/messages from "stalled" domU?

i'm not sure what to provide, here ... the point is that the domU doesn't launch, and nothing, therefore, is written to its logs: @ Server rpm -qa | grep xen-4 xen-4.0.0_21091_06-0.1.1.x86_64 xm create -c fw.cfg xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1010 1 r----- 44.2 fw 1 512 4 -b---- 22.0 @ DomU uname -a Linux fw 2.6.34.7-0.4-xen #1 SMP 2010-10-07 19:07:51 +0200 x86_64 x86_64 x86_64 GNU/Linux rm /var/log/{boot.*,messages} shutdown -h now @ Server ( upgrade to 'new' xen ) shutdown -r now rpm -qa | grep xen-4 xen-4.0.1_21326_01-1.1.x86_64 kpartx -a /dev/VG0/fw_root mount -o loop /dev/mapper/VG0-fw_root1 /mnt/tmp ls -ald /mnt/tmp/var/log drwxr-xr-x 15 root root 4096 2010-10-19 07:59 /mnt/tmp/var/log/ ls -al /mnt/tmp/var/log/{messages,boot*} /bin/ls: No match. umount /mnt/tmp kpartx -d /dev/VG0/fw_root xm create -c fw.cfg Using config file "./fw_run.cfg". Copy kernel /vmlinuz-xen from xvda1 to /var/lib/xen/tmp/kernel._HeNcO for booting Started domain fw (id=1) ( ... hang/stall ...) xm destroy fw xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1010 1 r----- 43.7 ls -al /mnt/tmp/var/log/{messages,boot*} <---- NO LOGS @ DomU /bin/ls: No match. umount /mnt/tmp kpartx -d /dev/VG0/fw_root please clarify if you want some other info, or if i've otherwise misunderstood -- 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=645251 https://bugzilla.novell.com/show_bug.cgi?id=645251#c10 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |pgngw+dev001+novell.com@f-m | |.fm --- Comment #10 from James Fehlig 2010-10-19 21:00:43 UTC --- Ok, I've finally reproduced the issue with *one* of my openSUSE 11.3 domUs using the xen packages from Virtualization:openSUSE11.3. Odd that other openSUSE 11.3 domUs work fine. Anyhow, the problem stems from moving the grant device (gntdev) from /dev/xen/ to /dev/. It has been fixed and new bits uploaded to Virtualization:openSUSE11.3. Please try the new packages. Thanks! -- 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=645251 https://bugzilla.novell.com/show_bug.cgi?id=645251#c12 --- Comment #12 from dev001x _ 2010-10-19 21:58:24 UTC --- assuming the fix in Virtualization:openSUSE11.3 is good, please notify here when it's pushed to d.o.o/update/11.3 i'd like to get back to release-repos asap. thanks. -- 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=645251 https://bugzilla.novell.com/show_bug.cgi?id=645251#c14 --- Comment #14 from dev001x _ 2011-01-12 15:56:53 UTC --- hi, i just saw this swamp update, https://bugzilla.novell.com/show_bug.cgi?id=635380#c18 is that to imply/recommend that "this" fix has, in fact, landed in 11.3 distro repos, and that we can/should switch 'off' Virtualization:openSUSE11.3? or, is ther any particular harm in leaving it on, atm? -- 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.