https://bugzilla.novell.com/show_bug.cgi?id=347416 Jan Beulich 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 gb2@c5i.net added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c2 Glen Barney changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gb2@c5i.net --- Comment #2 from Glen Barney 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 User aj@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c3 --- Comment #3 from Andreas Jaeger 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#c5 --- Comment #5 from Glen Barney 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 jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c7 --- Comment #7 from Jan Beulich 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#c9 --- Comment #9 from Glen Barney 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 gb2@c5i.net added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c11 --- Comment #11 from Glen Barney 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 gb2@c5i.net added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c13 --- Comment #13 from Glen Barney 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 jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c15 --- Comment #15 from Jan Beulich 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 gb2@c5i.net added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c18 --- Comment #18 from Glen Barney 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 gb2@c5i.net added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c20 --- Comment #20 from Glen Barney 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 jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c22 --- Comment #22 from Jan Beulich 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 jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c24 Jan Beulich changed: What |Removed |Added ---------------------------------------------------------------------------- CC|jbeulich@novell.com | --- Comment #24 from Jan Beulich 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 aj@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=347416#c26 Andreas Jaeger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|gb2@c5i.net | Resolution| |NORESPONSE --- Comment #26 from Andreas Jaeger 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.