On Jul 29, 2009, at 7:52 AM, "Andrea Dell'Amico" adellam@sevenseas.org wrote:
On Tue, 2009-07-28 at 14:31 -0400, William L. Maltby wrote:
When the two hosts are in sync, if I activate more than a few (six or seven) xen guests, the master server crashes spectacularly and reboots.
I've seen a kernel dump over the serial console, but the machine restarts immediately so I didn't write it down.
If you have an available pc, hook it up in place of the serial console and start a terminal emulator, e.g. minicom or whatever you prefer, and turn on full logging. This should save everyting in a file that you can then review.
Uhm. The console is on the DRAC5 card. I think I would need to activate some network kernel crash dump feature.
If it's a Windows based, just remember to get rid of the ^M with dos2unix, or equivalent, after you send it to a *IX box.
I don't know anything about the rest of your problem, sorry.
As I wrote, it's a production server. I cannot stop it when I want, I need to reserve a weekend session. In the meantime, I was asking if there's a known problem with a setup like mine.
I read on another forum how a user using iSCSI for domUs was experiencing network hangs due to the fact that dom0 didn't have enough scheduler credits to handle the network throughput. That might be related.
http://lists.centos.org/pipermail/centos-virt/2009-June/001021.html
-Ross
On Wed, 2009-07-29 at 09:55 -0400, Ross Walker wrote:
I read on another forum how a user using iSCSI for domUs was experiencing network hangs due to the fact that dom0 didn't have enough scheduler credits to handle the network throughput. That might be related.
http://lists.centos.org/pipermail/centos-virt/2009-June/001021.html
I'm pretty sure the crash is DRBD related: until the secondary drbd server is detached, all is working well. There are 23 guests running, right now, some of them paravirtualized, other full virtualized. Some of them use files images, other logical volumes (all of them over a drbd device). And I don't have a resource starvation, but a kernel crash and an immediate reboot.
-Ross
ciao andrea
On Wed, 2009-07-29 at 16:16 +0200, Andrea Dell'Amico wrote:
On Wed, 2009-07-29 at 09:55 -0400, Ross Walker wrote:
I'm pretty sure the crash is DRBD related: until the secondary drbd server is detached, all is working well. There are 23 guests running, right now, some of them paravirtualized, other full virtualized. Some of them use files images, other logical volumes (all of them over a drbd device). And I don't have a resource starvation, but a kernel crash and an immediate reboot.
It seems that one: http://thread.gmane.org/gmane.linux.network.drbd/17537 but I didn't loose the link between primary and secondary.
Andrea
On Jul 29, 2009, at 2:30 PM, "Andrea Dell'Amico" adellam@sevenseas.org wrote:
On Wed, 2009-07-29 at 16:16 +0200, Andrea Dell'Amico wrote:
On Wed, 2009-07-29 at 09:55 -0400, Ross Walker wrote:
I'm pretty sure the crash is DRBD related: until the secondary drbd server is detached, all is working well. There are 23 guests running, right now, some of them paravirtualized, other full virtualized. Some of them use files images, other logical volumes (all of them over a drbd device). And I don't have a resource starvation, but a kernel crash and an immediate reboot.
It seems that one: http://thread.gmane.org/gmane.linux.network.drbd/17537 but I didn't loose the link between primary and secondary
The OP with the iSCSI problem saw no resource starvation either, yet the hypervisor was rate limiting his dom0 CPU usage to the point where he was missing interrupts.
-Ross
-
Andrea Dell'Amico -
Ross Walker