[Bug 469936] New: Xen cannot start ANY paravirtualized domU on 32 bit Intel architecture?

older
[Bug 411035] New: Kpowersave shows...

bugzilla_noreply＠novell.com

27 Jan 2009 27 Jan '09

20:55

https://bugzilla.novell.com/show_bug.cgi?id=469936 Summary: Xen cannot start ANY paravirtualized domU on 32 bit Intel architecture? Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: cgriffin@novell.com ReportedBy: nice@titanic.nyme.hu QAContact: qa@suse.de Found By: --- Created an attachment (id=268085) --> (https://bugzilla.novell.com/attachment.cgi?id=268085) vm-install settings on the 32 bit system User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; hu-HU; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-1.1 Firefox/3.0.5 Am I unaware of something? I've installed openSUSE 11.1 on two identical machines (Sun Blade X6250 servers). One machine was installed with x86 and the other with x86-64, both with Xen support. I wanted to start openSUSE VM installation on both systems. (See the attached image above for details.) It succeeded on the x86-64 system, but totally failed on the 32 bit system. After a half day's struggle, finally I had to install the 32 bit domU on the 64 bit dom0 by downloading the kernel and initrd from http://download.opensuse.org/factory/repo/oss/boot/i386 and manually create a domU description file including extra=" install=http://download.opensuse.org/factory/repo/oss/ " I will attach further screen snapshots and log files. I made no attempt with fully virtualized domUs. Reproducible: Always Steps to Reproduce: 1. Install an x86 openSUSE 11.1 with xen support 2. Try to install a paravirtualized VM with setting similar to the attached image above Actual Results: total failure (At least for me. Am I an idiot?) Expected Results: It should work of course -- 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.

Show replies by date

bugzilla_noreply＠novell.com

27 Jan 27 Jan

20:56

New subject: [Bug 469936] Xen cannot start ANY paravirtualized domU on 32 bit Intel architecture?

https://bugzilla.novell.com/show_bug.cgi?id=469936 User nice@titanic.nyme.hu added comment https://bugzilla.novell.com/show_bug.cgi?id=469936#c1 --- Comment #1 from Tamás Németh 2009-01-27 13:56:13 MST --- Created an attachment (id=268086) --> (https://bugzilla.novell.com/attachment.cgi?id=268086) Screen snapshot showing the results (not too informative) -- 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.

bugzilla_noreply＠novell.com

21:04

New subject: [Bug 469936] Xen cannot start ANY paravirtualized domU on 32 bit Intel architecture?

https://bugzilla.novell.com/show_bug.cgi?id=469936 User nice@titanic.nyme.hu added comment https://bugzilla.novell.com/show_bug.cgi?id=469936#c2 --- Comment #2 from Tamás Németh 2009-01-27 14:04:30 MST --- Created an attachment (id=268092) --> (https://bugzilla.novell.com/attachment.cgi?id=268092) My xen config and log files after the faild vm creation attempt -- 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.

bugzilla_noreply＠novell.com

21:08

New subject: [Bug 469936] Xen cannot start ANY paravirtualized domU on 32 bit Intel architecture?

https://bugzilla.novell.com/show_bug.cgi?id=469936 User nice@titanic.nyme.hu added comment https://bugzilla.novell.com/show_bug.cgi?id=469936#c3 --- Comment #3 from Tamás Németh 2009-01-27 14:08:45 MST --- After I've succesfully finished the installation of the 32 bit domU on the 64 bit dom0, I copied the corresponding domU configfile from the 64 bit system to the 32 bit one (The two system can see the same multipathed volumes via fibrechannel). In spite of the fact that the 32 bit domU (almost always) worked on the 64 bit dom0, it immediately collapsed on the 32bit one: carrier5:/etc/xen/vm # cat openSUSE111-32 name="openSUSE111-32" uuid="abb18405-b7fa-2caa-fcef-03adb7be0002" memory=1024 vcpus=1 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" on_xend_start = "ignore" on_xend_stop = "shutdown" localtime=0 keymap="en-us" builder="linux" bootloader="/usr/bin/pygrub" disk=[ 'phy:/dev/mapper/openSUSE111-32,xvda,w', ] vif=[ 'mac=00:16:3e:00:00:02,bridge=br0', ] vfb=['type=vnc,vncdisplay=12'] carrier5:/etc/xen/vm # xm create /etc/xen/vm/openSUSE111-32 ; xm console openSUSE111-32 Using config file "/etc/xen/vm/openSUSE111-32". Started domain openSUSE111-32 Error: Domain 'openSUSE111-32' does not exist. -- 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.

bugzilla_noreply＠novell.com

21:10

New subject: [Bug 469936] Xen cannot start ANY paravirtualized domU on 32 bit Intel architecture?

https://bugzilla.novell.com/show_bug.cgi?id=469936 User nice@titanic.nyme.hu added comment https://bugzilla.novell.com/show_bug.cgi?id=469936#c4 --- Comment #4 from Tamás Németh 2009-01-27 14:10:16 MST --- The 64 bit domU behaved even worse on this 32 bit system: carrier5:/etc/xen/vm # cat openSUSE111-64 name="openSUSE111-64" uuid="abb18405-b7fa-2caa-fcef-03adb7be0001" memory=1024 vcpus=1 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" on_xend_start = "ignore" on_xend_stop = "shutdown" localtime=0 keymap="en-us" builder="linux" bootloader="/usr/bin/pygrub" disk=[ 'phy:/dev/mapper/openSUSE111-64,xvda,w', ] vif=[ 'mac=00:16:3e:00:00:01,bridge=br0', ] vfb=['type=vnc,vncdisplay=11'] carrier5:/etc/xen/vm # xm create /etc/xen/vm/openSUSE111-64 Using config file "/etc/xen/vm/openSUSE111-64". Error: (4, 'Out of memory', "xc_dom_boot_mem_init: can't allocate low memory for domain\n") -- 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.

bugzilla_noreply＠novell.com

28 Jan 28 Jan

08:43

New subject: [Bug 469936] Xen cannot start ANY paravirtualized domU on 32 bit Intel architecture?

https://bugzilla.novell.com/show_bug.cgi?id=469936 User kwolf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469936#c5 Kevin Wolf changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kwolf@novell.com --- Comment #5 from Kevin Wolf 2009-01-28 01:43:28 MST --- The log files don't seem to contain more than "Domain has crashed". Could you provide the output of xm dmesg? Also, if you can get some console output of the guest (start the VM with xm start -c, so you're connected from the very beginning) this could possibly be helpful. -- 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.

bugzilla_noreply＠novell.com

29 Jan 29 Jan

19:14

New subject: [Bug 469936] Xen cannot start ANY paravirtualized domU on 32 bit Intel architecture?

https://bugzilla.novell.com/show_bug.cgi?id=469936 User nice@titanic.nyme.hu added comment https://bugzilla.novell.com/show_bug.cgi?id=469936#c6 --- Comment #6 from Tamás Németh 2009-01-29 12:14:34 MST --- Created an attachment (id=268736) --> (https://bugzilla.novell.com/attachment.cgi?id=268736) xm dmesg from the 64 bit dom0 OK, at first, I was about to hang myself, because the 32bit domU was unable to start on the 64 bit dom0 too. After struggling for a whole day I was able to start it on the 64 bit dom0, but I had to start the 64 bit domU first. Without running the 64 bit domU, even the 64bit dom0 was unable to start the 32 bit domU. I will attach a commented version of xm dmesg, extracted from the 64 bit dom0. BTW, I didn't get any data from xm start -c DOMAINNAME, because the xm command simply hangs during the domU is crashed. I had to destoy the domU from an other terminal to be able to exit from the xm command, which gives not a single line of output. -- 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.

bugzilla_noreply＠novell.com

19:25

New subject: [Bug 469936] Xen cannot start ANY paravirtualized domU on 32 bit Intel architecture?

https://bugzilla.novell.com/show_bug.cgi?id=469936 User nice@titanic.nyme.hu added comment https://bugzilla.novell.com/show_bug.cgi?id=469936#c7 --- Comment #7 from Tamás Németh 2009-01-29 12:25:05 MST --- Created an attachment (id=268741) --> (https://bugzilla.novell.com/attachment.cgi?id=268741) In case this prolem is hardware dependent - I attach the output of hwinfo BTW, I used domUs like this for the experiments of today: name="openSUSE111-32" uuid="abb18405-b7fa-2caa-fcef-03adb7be0002" memory=1024 vcpus=1 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" on_xend_start = "ignore" on_xend_stop = "shutdown" localtime=0 keymap="en-us" builder="linux" kernel="/root/vmlinuz-xen" ramdisk="/root/initrd-xen" extra="install=http://ftp.gwdg.de/pub/linux/suse/opensuse/distribution/11.1/repo/oss" disk=[ 'phy:/dev/mapper/openSUSE111-32,xvda,w', ] vif=[ 'mac=00:16:3e:00:00:02,bridge=br0', ] vfb=['type=vnc,vncdisplay=12'] Vmlinuz and initrd were from http://ftp.gwdg.de/pub/linux/suse/opensuse/distribution/11.1/repo/oss/boot/i... , because the default server I was redirected to (http://www.fsn.hu) was absolutely, impossibly slow. The disk is physical fibrechannel multipath, but you can try it with a plain file, of course. -- 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.

bugzilla_noreply＠novell.com

19:42

New subject: [Bug 469936] Xen cannot start ANY paravirtualized domU on 32 bit Intel architecture?

https://bugzilla.novell.com/show_bug.cgi?id=469936 User nice@titanic.nyme.hu added comment https://bugzilla.novell.com/show_bug.cgi?id=469936#c8 --- Comment #8 from Tamás Németh 2009-01-29 12:42:43 MST --- Created an attachment (id=268746) --> (https://bugzilla.novell.com/attachment.cgi?id=268746) See, what happens on the 32 bit dom0: 32bit domU crashes, which you can see int the attached xm dmesg output. I also attempted to start the 64 bit domU several times. But it was always unsuccessful, with the following error message: carrier5:/etc/xen/vm # xm create openSUSE111-64 Using config file "./openSUSE111-64". Error: (4, 'Out of memory', "xc_dom_boot_mem_init: can't allocate low memory for domain\n") It's even more interesting, that there are do signs of the 64 bit domU in xm dmesg! Moreover, every time I attempt to start the 64 bit domU it totally empties the xm list list. Even when having a crashed 32 bit domU in the list, starting a 64 bit domU makes everything disappear. -- 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.

bugzilla_noreply＠novell.com

19:45

New subject: [Bug 469936] Xen cannot start ANY paravirtualized domU on 32 bit Intel architecture?

https://bugzilla.novell.com/show_bug.cgi?id=469936 User nice@titanic.nyme.hu added comment https://bugzilla.novell.com/show_bug.cgi?id=469936#c9 --- Comment #9 from Tamás Németh 2009-01-29 12:45:14 MST --- Sorry for the typo there are do signs of the 64 bit domU in xm dmesg wanted to be: there are NO signs of the 64 bit domU in xm dmesg -- 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.

bugzilla_noreply＠novell.com

20:02

New subject: [Bug 469936] Xen cannot start ANY paravirtualized domU on 32 bit Intel architecture?

https://bugzilla.novell.com/show_bug.cgi?id=469936 User nice@titanic.nyme.hu added comment https://bugzilla.novell.com/show_bug.cgi?id=469936#c10 --- Comment #10 from Tamás Németh 2009-01-29 13:02:35 MST --- Created an attachment (id=268750) --> (https://bugzilla.novell.com/attachment.cgi?id=268750) Corresponding xend.log from the 32 bit dom0 -- 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.

bugzilla_noreply＠novell.com

20:17

New subject: [Bug 469936] Xen cannot start ANY paravirtualized domU on 32 bit Intel architecture?

https://bugzilla.novell.com/show_bug.cgi?id=469936 User nice@titanic.nyme.hu added comment https://bugzilla.novell.com/show_bug.cgi?id=469936#c11 --- Comment #11 from Tamás Németh 2009-01-29 13:17:38 MST --- One more additional info: After a domU crash, virt-manager losts it ability to connect to xend. It always hangs, reporting that it's in connecting state. Restarting xend and/or libvirt does not help. I had restart the whole machine in order to be able to use virt-manager again. -- 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.

bugzilla_noreply＠novell.com

20:18

New subject: [Bug 469936] Xen cannot start ANY paravirtualized domU on 32 bit Intel architecture (x86-64 also unreliable)

https://bugzilla.novell.com/show_bug.cgi?id=469936 Tamás Németh changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Xen cannot start ANY |Xen cannot start ANY |paravirtualized domU on 32 |paravirtualized domU on 32 |bit Intel architecture? |bit Intel architecture | |(x86-64 also unreliable) -- 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.

bugzilla_noreply＠novell.com

20:19

New subject: [Bug 469936] Xen cannot start ANY paravirtualized domU on 32 bit Intel architecture (x86-64 also unreliable)

https://bugzilla.novell.com/show_bug.cgi?id=469936 User nice@titanic.nyme.hu added comment https://bugzilla.novell.com/show_bug.cgi?id=469936#c12 --- Comment #12 from Tamás Németh 2009-01-29 13:19:55 MST --- And one more info: the 32 bit dom0 kernel proved to be less stable than the 64 bit in general. Every second or third boot of the 32 bit dom0 results in total system lockup (I can't extract any debug info), however, the 64 bit system always boots successfully. -- 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.

bugzilla_noreply＠novell.com

20:42

New subject: [Bug 469936] Xen cannot start ANY paravirtualized domU on 32 bit Intel architecture (x86-64 also unreliable)

https://bugzilla.novell.com/show_bug.cgi?id=469936 User nice@titanic.nyme.hu added comment https://bugzilla.novell.com/show_bug.cgi?id=469936#c13 --- Comment #13 from Tamás Németh 2009-01-29 13:42:33 MST --- Even more bad news: I usually use xen by giving the dom0_vcpus_pin option the hypervisor, and using only a fractionf of the physical memory in dom0, and a single CPU (given that this is an I/O intensive system). So, a configured the new 64 bit dom0 like this (usually it was totally unconfigured, usiong the default config files.) And the result is that the 64 bit dom0 can only run the 64bit domU. The 32 bit domU always crashes and makes the whole system insane, so I have to restart the physical machine. Maybe I will test this tomorrow: https://bugzilla.novell.com/show_bug.cgi?id=406298 I have no hope :( -- 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.

bugzilla_noreply＠novell.com

2 Feb 2 Feb

16:05

New subject: [Bug 469936] Xen cannot start ANY paravirtualized domU on 32 bit Intel architecture (x86-64 also unreliable)

https://bugzilla.novell.com/show_bug.cgi?id=469936 User jdouglas@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469936#c14 Jason Douglas changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |coolo@novell.com, | |jdouglas@novell.com Resolution| |DUPLICATE --- Comment #14 from Jason Douglas 2009-02-02 09:05:31 MST --- The problems associated with 32-bit PV installs failing are due to a blocker bug (bug #457445) that was fixed during the openSUSE 11.1 RC1 time frame, but was not accepted into the GM build. As such, the only recourse is to install from factory, or to manually patch your installation source with a newer kernel-xen package, and installation vmlinuz-xen/initrd-xen. As for your other issues, I would recommend entering a separate bug for each one. *** This bug has been marked as a duplicate of bug 457445 *** https://bugzilla.novell.com/show_bug.cgi?id=457445 -- 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.

5566

Age (days ago)

5572

Last active (days ago)

List overview

Download

15 comments

1 participants

participants (1)

bugzilla_noreply＠novell.com

[Bug 469936] New: Xen cannot start ANY paravirtualized domU on 32 bit Intel architecture?

tags

participants (1)