[Bug 347416] New: OpenSuse 10.3, Xen 3.1.0, unable to install domU over http, entire physical server hangs and crashes
https://bugzilla.novell.com/show_bug.cgi?id=347416 Summary: OpenSuse 10.3, Xen 3.1.0, unable to install domU over http, entire physical server hangs and crashes Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Keywords: dogfood Severity: Blocker Priority: P5 - None Component: Xen AssignedTo: cgriffin@novell.com ReportedBy: gb2@c5i.net QAContact: qa@suse.de Found By: Customer When running OpenSuSE 10.3 (kernel 2.6.22.13-xenpae) on a Dell PowerEdge 2950, and Xen 3.1.0, attempts to install an copy of OpenSuSE 10.3 as a domU instance while reading the source via http:// to the local dom0 host results in the entire physical server freezing at random points during the installation of packages. * This has been duplicated on four seperate Dell 2950 servers with different configurations and manufacture dates. * This occurs in both graphical (i.e. KDE/VNC) mode as well as text (i.e. xenconsole) mode, and in both runlevels 3 and 5. * Some had suspected that this might be related to bug 344877, which complains about dom0 hanging under high traffic load, and indeed it did seem to fit the profile; however, a modified kernel set to 100Hz did *not* resolve this problem. Moreover, I cannot duplicate that bug. My installations crash within 5-10 minutes of starting. But I ran "ping -f -q my.local.ip.address" for an hour with no problems: core1:/home/glen # ping -f -q my.local.ip.address PING nnn.nnn.nnn.nnn (nnn.nnn.nnn.nnn) 56(84) bytes of data. --- nnn.nnn.nnn.nnn ping statistics --- 196356167 packets transmitted, 196356167 received, 0% packet loss, time 3573391ms rtt min/avg/max/mdev = 0.010/0.010/30.037/0.003 ms, pipe 2, ipg/ewma 0.018/0.011 ms The ping flood ran successfully for hours under both the loopback address and the public-facing IPV4 address. * I am unable to install from the CD due to bugs in the vm-install python script. * My web server is just the stock apache2 server with the document root re-set to /opensuse, a directory off root which contains a copy of the installation CD. * All the troubleshooting steps in /usr/share/doc/packages/xen/README.SuSE have been followed, including booting with different kernel parameters such as pnpacpi=off, lapic, acpi=off, apm=off, noirqbalance, etc. * I also tried to grab output using sync_console, xm dmesg, etc. No log or serial output is generated, no evidence of a panic exists. The hardware... just.... stops. * Obviously, this bug prevents the use of Xen at all on any of my servers. (Plus, any bug which allows a domU instance to reach out and crash the dom0 box would certainly be a show-stopper in any event.) Please let me know how I can assist with the resolution of this bug, as we cannot move to 10.3 or use virtualization until this is corrected. Thank you! -- 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=347416 Glen Barney <gb2@c5i.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Blocker |Critical -- 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=347416 Jan Beulich <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jbeulich@novell.com AssignedTo|cgriffin@novell.com |jbeulich@novell.com Status|NEW |ASSIGNED -- 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=347416 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c1 Jan Beulich <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |gb2@c5i.net --- Comment #1 from Jan Beulich <jbeulich@novell.com> 2007-12-12 09:04:21 MST --- Please re-test with the next (not yet scheduled) kernel update. It is pretty likely that a fix in there addresses your 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=347416 User gb2@c5i.net added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c2 Glen Barney <gb2@c5i.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gb2@c5i.net --- Comment #2 from Glen Barney <gb2@c5i.net> 2007-12-12 10:55:06 MST --- Will do. However, I hope it's a fix other than changing that TIMER thing to 100 - just wanted to make sure I made clear that I tried that per suggestion in the other bug, and it did *not* resolve the problem. I will advise after the next kernel release, and thanks! Glen -- 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=347416 Jason Douglas <jdouglas@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- QAContact|qa@suse.de |jdouglas@novell.com -- 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=347416 User aj@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c3 --- Comment #3 from Andreas Jaeger <aj@novell.com> 2008-02-19 05:33:35 MST --- Glen, any update? -- 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=347416 User gb2@c5i.net added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c4 --- Comment #4 from Glen Barney <gb2@c5i.net> 2008-02-19 11:02:48 MST --- Just got the .17 kernel. I will be updating my test server today, and I'll have some testing done hopefully by the end of the week. -- 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=347416 User gb2@c5i.net added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c5 --- Comment #5 from Glen Barney <gb2@c5i.net> 2008-02-24 22:54:58 MST --- Sat down to work on this tonight remotely from home. Have all the latest patches on, plus kernel 17. Changed the /boot/grub/menu.lst default line to boot the Xen kernel, saved, rebooted the server. It never came back up. (Brand new Dell 2950 8GB, 8-core, 600GB w/ Raid, high-end machine.) *sigh* This is the top of my priority list, but I won't be in my office to figure the crash out until Tuesday. I will then get the thing back online, and report on the results of my attempt to load the machine. Thanks for your patience! -Glen -- 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=347416 User gb2@c5i.net added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c6 --- Comment #6 from Glen Barney <gb2@c5i.net> 2008-02-27 00:23:26 MST --- I am sorry to report that my server still crashes as before. Kernel 17, latest Xen updates from SuSE... no luck. The dom0 machine has an apache2 webserver running that has the DVD image in its Document Root. The domU machine is trying to install off of that http:// address. Everything starts up fine. It gets through about 1GB of the 6GB I selected for install, and EVERYTHING hangs. domU dies, dom0 dies, no console output, no panic/oops message... just... freeze. -- 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=347416 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c7 --- Comment #7 from Jan Beulich <jbeulich@novell.com> 2008-02-27 01:15:59 MST --- Might well be similar to bug 345866, therefor the same info should be collected: - collect Xen *and* kernel messages over serial (to grab a possible kernel or Xen crash's printout), or (if that doesn't provide anything) - check whether SysRq still works at the point of the hang, and if so, collect SysRq-p and SysRq-t output (again over serial), or (if that doesn't work) - collect Xen's response to sending 'd' over the serial line (after switching input to 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=347416 User gb2@c5i.net added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c8 --- Comment #8 from Glen Barney <gb2@c5i.net> 2008-02-28 10:55:42 MST --- Understood. I will need to go buy a null modem adapter to pull this off at this point; please allow me a few days to pull this together. -- 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=347416 User gb2@c5i.net added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c9 --- Comment #9 from Glen Barney <gb2@c5i.net> 2008-03-13 13:57:22 MST --- I hooked up the serial cable as requested, and switched everything over... but there is absolutely no output. Once the server halts, it is totally halted. I hope this helps! -- 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=347416 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c10 --- Comment #10 from Jan Beulich <jbeulich@novell.com> 2008-03-14 02:01:54 MST --- With "absolutely no output", do you mean you didn't even get Xen's boot messages? If so, this certainly is a setup problem. If not, did you try sending 'd' (after switching input to Xen) over serial when the system hung? Did you add "loglvl=all guest_loglvl=all" to the Xen command line. And no, if even that doesn't provide any output, then that's gonna be pretty diffcult to analyse... -- 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=347416 User gb2@c5i.net added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c11 --- Comment #11 from Glen Barney <gb2@c5i.net> 2008-03-14 09:16:13 MST --- I'm sorry. I should have said "Once the system freezes there is absolutely no output." I did try sending 'd' over the serial line - once the system had frozen - and there was no response to that. I did not try it before the system froze. Should I do so? Do you want all of the seemingly-normal output that is generated during Dom0 boot, before the system hangs? I'm sorry if I misunderstood - please let me know what you want from here and I will endeavor to get it! Thanks, Glen -- 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=347416 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c12 --- Comment #12 from Jan Beulich <jbeulich@novell.com> 2008-03-14 09:32:15 MST --- The main question is whether you properly switched input. For that reason, making sure 'd' works prior to the hang would of course be very useful since, as I said, if there's indeed no response to it after the hang it's gonna be very difficult for us to analyze the problem, especially without having a machine at hand where it is reproducible. -- 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=347416 User gb2@c5i.net added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c13 --- Comment #13 from Glen Barney <gb2@c5i.net> 2008-03-14 09:38:52 MST --- Okay, I think I understand. I will be back in my office Tuesday and/or Thursday of this coming week and will check everything and capture all the output I can. I'll also send boot strings etc to make sure I'm switching input correctly. 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=347416 User gb2@c5i.net added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c14 --- Comment #14 from Glen Barney <gb2@c5i.net> 2008-03-21 21:37:28 MST --- I've gone through everything, and I'm positive that I've done everything that I'm supposed to... and there's still no output. I have been able to duplicate this problem on four different machines - all of the machines I have access to - am I given to understand, then, that nobody else can duplicate this problem? 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=347416 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c15 --- Comment #15 from Jan Beulich <jbeulich@novell.com> 2008-03-31 03:44:31 MST --- So just to make sure (since you didn't attach anything that proves this) - 'd' works initially, but doesn't result in any output once the machine is hung? -- 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=347416 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c17 --- Comment #17 from Jan Beulich <jbeulich@novell.com> 2008-03-31 03:45:37 MST --- Oh, one additional thing: are the four machines you tried substantially different in terms of hardware? -- 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=347416 User gb2@c5i.net added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c18 --- Comment #18 from Glen Barney <gb2@c5i.net> 2008-03-31 10:53:09 MST --- I'm terribly sorry... I'm not trying to be difficult here... it's just that deep debugging of Xen is something I'm not quite familiar with yet. Since there was no output after the hang, I didn't post anything - I didn't know you wanted me to post output before the hang. I do the ^A switch thing, and the "D" thing, and they do seem to put me into a mini-console of some kind, before the hang. But after the hang, I can ^A and D to my heart's content, and get nothing. I don't really know what constitutes "substantial" but I have tried this on: 1. Dell PowerEdge 2600, 2x dual-core Xeon 2.0 with 8GB, made 5 years ago. 2. Dell PowerEdge 1800, Dual-core Pentium 3.0 with 4GB, made about 3 years ago. 3. Dell PowerEdge 2950, 4x dual-core Pentium 3.0 with 8GB, made 9 months ago. And the target machine I'm actually working on: Dell PowerEdge 2950, 4x dual-core Pentium 3.0 with 8GB, made 3 months ago. All are running OpenSuse 10.3, with all patches offered by opensuse.org automatic update applied. So I would say, same brand, but different across time. The machines 1-3 are not really available for testing - they're the ones I'm trying to move TO virtual machines on the most recent 2950. If I can get this to work. In addition to any output you might want, I can post more detailed specs on this last machine if it would help, or whatever else you need. I will be in my office tomorrow, if you want I would be glad to post whatever proof or output you desire - just tell me what you want, and I'll be glad to get it for you! I want to do whatever I can to support getting this resolved, so I will get whatever you want - just help me to understand what you want to see - and I'm terribly sorry for any misunderstanding. Glen -- 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=347416 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c19 --- Comment #19 from Jan Beulich <jbeulich@novell.com> 2008-04-01 01:23:18 MST --- Thanks, Glen. The reason I've been insisting on being very explicit here is that I don't remember a single case where Xen would itself be hung without any message (your problem summary also suggested it would not be just hung - 'crashes' implies messages to me). So based on your input we'll have to see whether we can reproduce this somehow... It might be helpful to know whether - any other way of installing domU-s (e.g. you said it doesn't work from CD, but didn't go into detail, and you didn't state whether you tried installing from a .iso) would avoid the hang (to narrow whether this is network dependent) - all of the machines use the same network card (or at least are all driven by the same driver) - by any chance, you tried the whole setup as 64-bit, or with the non-PAE Xen and kernel (or whether you would be able to try both of these) -- 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=347416 User gb2@c5i.net added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c20 --- Comment #20 from Glen Barney <gb2@c5i.net> 2008-04-03 15:02:10 MST --- Understood completely, and thanks. Poor choice of wording on my part. What's happening for me is that the entire physical server is halting. USB keyboard unresponsive - even the CAPS LOCK light won't switch states - serial port unresponsive - network unresponsive - as far as I can tell the server is completely stopped any not executing anything at any level. I am going to work on the list you just sent. It's going to take several days, because I'm only in front of this machine 2 days a week, so please be patient as I run all these tests. Today, I downloaded the non-PAE Xen kernel, and booted under it. Of course, only 3.8GB of my RAM is now recognized. Alas, the same problem appears to exist under this kernel; namely, the entire server halts with no responsiveness whatsoever, including no response to ^A^A^A or "D" or anything. The CD install didn't work - that was another bug I reported here in the past - I don't even remember why it didn't work but it was because of that that I've been trying to do it this way. I will go back and try a CD install next and report. I've never tried an ISO image load - I'll have to figure out how to do that. The apache "workaround" that exposed this current bug was the best way I could find to get the machine loaded, and I only went that route because of the failure of the CD install. At least three of the machines are in fact using the same type of network card - the built-in onboard Broadcom II NetExtreme cards - and they all appear to be using the bnx2 driver version 1.5.11 at this stage. This machine is not doing anything else, so yes I certainly can reload with the 64-bit setup and try it that way, and will do so if other events fail here. I have to leave shortly and will be back in on Tuesday, at which time I will continue with your list, and thank you again for your patience! -Glen -- 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=347416 User gb2@c5i.net added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c21 --- Comment #21 from Glen Barney <gb2@c5i.net> 2008-04-03 15:54:30 MST --- Okay, I'm pleased to report that the original problem I had previously, where I was unable to load a machine via local CD-ROM (DVD-ROM), appears to have been fixed. I booted with the XenPAE kernel again, went to runlevel 5, logged in to graphic mode, and successfully loaded a virtual machine. Of course, the machine won't reboot, because the kernel on my original 10.3 media getting loaded into domU appears to be incompatible with the dom0 kernel... ERROR (2,'Invalid kernel','xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by Xen kernel, sorry\n') but I assume I can hack around that somehow. So I can at least load machines now, and hopefully get them to work, which is farther than I got before... However, I can also still duplicate this current bug, and that worries me, because I wonder if my virtual machines, when under high network load during operation, might cause a server halt, thus halting ALL the virtual machines on the server plus the server itself plus my ability to remote restart them. In other words, I wonder if this bug is related to the network, and NOT to just the installation per se. I'm therefore more than happy, and anxious, to continue working on this bug with you all, if there is interest, and I will continue to do whatever I can to help. Specifically, next on my list is to: 1. Figure out how to install via ISO image and try that 2. Try doing this through the loopback interface instead of the eth0 public IP address, and see if that works? I'll try that under xenpae and straight xen, if you feel it would help? 3. Reload the host in 64-bit mode, and try all these things again under that mode? This will take some time, but I'm happy to try if it is desired. Or, since I can now load machines the other way, if you want to stop, that's your call. I'll also mention that, as I said, this physical host is not doing anything else. And it is directly on the internet. So I can easily set up a login account - and provide root access - to this machine if there is any interest or desire on the part of Novell/others to get in and check things out directly. It would be my pleasure to do that, or anything else needed, to help resolve this. So if I hear nothing back by Tuesday - which is when I'm in the office next - I will continue with the list as I understand it. Thank you! -Glen -- 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=347416 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c22 --- Comment #22 from Jan Beulich <jbeulich@novell.com> 2008-04-04 07:18:14 MST ---
Of course, the machine won't reboot, because the kernel on my original 10.3 media getting loaded into domU appears to be incompatible with the dom0 kernel...
ERROR (2,'Invalid kernel','xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by Xen kernel, sorry\n')
I assume this was after you changed from PAE to non-PAE (or the other way around) without re-creating the guest... But - if I get you right, you succeeded to install a new VM from CD, while in the same system configuration the network install failed. If that's correct, then I agree to
I wonder if my virtual machines, when under high network load during operation, might cause a server halt, thus halting ALL the virtual machines on the server plus the server itself plus my ability to remote restart them. In other words, I wonder if this bug is related to the network, and NOT to just the installation per se.
Rather than continuing the route you outlined, it may thus be much more interesting to see whether you'd get the box to die with (high) network traffic unrelated to VM installation/operation, and whether using a completely different NIC model (specifically driven by another driver) would avoid the problem (in fact I cannot even assure you anyone internally ever tested on a machine using the bnx2 driver - we just have to assume that the hardware drivers work well in Xen if they do so in native, which generally is a valid assumption). Btw., in light of another bug recently fixed upstream: The VM(s) you install don't take an unusually large (i.e. anything >1 ;-)) number of virtual disks or NICs? (But even if so, this could crash dom0, but shouldn't hang the hypervisor.) -- 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=347416 User gb2@c5i.net added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c23 --- Comment #23 from Glen Barney <gb2@c5i.net> 2008-04-04 22:14:13 MST --- No, the error came up after a normal install, under xen-pae, runlevel 5, freshly-created guest. Previously I was unable to do an install from CD - something wasn't being configured correctly by the vm-tools, I think. So I didn't even have a guest to work with. This time I *was* able to do an install... at least farther than before. I booted my physical machine under the xen-pae kernel, went to runlevel 5, logged in to KDE, chose to install a virtual machine, upgraded to root, set up the machine, and ran the install. The domU machine read the DVD in the dom0 machine drive, which DVD was the original download of the OpenSuSE 10.3 32-bit DVD master ISO image from opensuse.org, and went through the entire installation procedure up to and including the installation of packages. BUT, when the domU machine went to do the first reboot (preparatory to setting the root password and continuing with YaST install), the boot failed before domU even opened a console window. The popup message appeared to come from the vm-install tool, and was that "guest type xen-3.0-x86_32 not supported by Xen kernel, sorry" message (complete with the escaped newline showing :-). I haven't been able to work on it since, but I *assume* it's because there have been so many upgrades to 10.3's kernels and Xen packages since that first DVD, that the kernel loaded from the DVD is not being recognized by the significantly-upgraded kernel running on my dom0 host. (I have no idea, I'm just guessing.) My intent is to try to mount the domU filesystem from dom0, and manually copy in the kernels from dom0's boot area into the domU filesystem, and hope that lets the domU machine start and continue the installation procedure? If you have any thoughts, guidance or commentary on this, I'd love to hear it. I am most likely totally wrong. :-/ Nevertheless I did at least get this far in the installation, in that all packages from the source DVD did get applied to the domU filesystem without the entire physical machine halting, and the dom0 machine was still perfectly responsive after the process. It's just that the domU won't boot now because of this error message, so I'll have to attack that next. I understand that what you want me to do now is try to get this domU machine to boot, and run network load testing from within that machine. Fantastic! I will make that my next move. As soon as I can get the domU machine to finish the install. :-) In response to your last question, no, I just took the defaults on this test install. One disk (40GB), one virtual network card, etc. Too tired of that to customize each install. :-) I just want an install to succeed, then I'll go back and redo it the way I want it. Hope this helps and, again, if anyone has any thoughts or can point me to anything that will expedite my fight with this partially-installed domU, I would be most grateful! Thanks -Glen -- 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=347416 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c24 Jan Beulich <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|jbeulich@novell.com | --- Comment #24 from Jan Beulich <jbeulich@novell.com> 2008-04-07 01:22:44 MST ---
BUT, when the domU machine went to do the first reboot (preparatory to setting the root password and continuing with YaST install), the boot failed before domU even opened a console window. The popup message appeared to come from the vm-install tool, and was that "guest type xen-3.0-x86_32 not supported by Xen kernel, sorry" message (complete with the escaped newline showing :-).
That message, iirc, means you have a non-PAE guest with a PAE hypervisor/dom0. If you didn't customize the install, then that would seem like a YaST bug.
... My intent is to try to mount the domU filesystem from dom0, and manually copy in the kernels from dom0's boot area into the domU filesystem, and hope that lets the domU machine start and continue the installation procedure?
That ought to work, but ...
I understand that what you want me to do now is try to get this domU machine to boot, and run network load testing from within that machine. Fantastic! I will make that my next move. As soon as I can get the domU machine to finish the install.
Not necessarily. It may even be sufficient to put dom0 alone under high network load. But as I think more about it, the bug mentioned above may well affect you. The patch is queued for backporting to 10.3, I just need to find time to actually get it done. -- 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=347416 User gb2@c5i.net added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c25 --- Comment #25 from Glen Barney <gb2@c5i.net> 2008-04-07 09:55:51 MST --- I will check into the kernel thing tomorrow and see if I can get the guest to boot by replacing the kernel. I did not customize the install. Should I open a new bug report for the Yast install? Previously, I did try a ping flood on the dom0 machine - had no problems whatsoever. I could run it for an hour with no crashing at all. I'm not quite clear on which bug you're referring to or what you want me to do next but I will work on the guest as soon as I can tomorrow! Glen -- 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=347416 User aj@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c26 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|gb2@c5i.net | Resolution| |NORESPONSE --- Comment #26 from Andreas Jaeger <aj@novell.com> 2008-10-23 13:29:54 MDT --- The requested information has not been provided for over 4 weeks. The bug gets therefore closed as NORESPONSE. Please reopen the bug if you can supply the requested information. I would appreciate if you could test openSUSE 11.1 Beta3 first and report whether the bug exists there as well. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com