Fedora xen - Apr 2006 - RE: two fully virtualized systems crashing

I have a similar issue on a Dell Power Edge 1850 running:

Fedora Core 5
2.6.16-1.2080_FC5xen0
xen-3.0.1-4

Except my issue appears to affect the parent host as well. It seems to be
relevant during any increased NIC utilization.

If I''m copying data to or from a virtualized host the parent system
will
black screen without any kernel dump info, thus all i/o is halted and the
only solution is a reboot.

Any thoughts?



-----Original Message-----
From: fedora-xen-bounces@redhat.com [mailto:fedora-xen-bounces@redhat.com]
On Behalf Of Stephen C. Tweedie
Sent: Tuesday, April 11, 2006 11:18 AM
To: matbayer.web@web.de
Cc: fedora-xen@redhat.com
Subject: Re: [Fedora-xen] two fully virtualized systems crashing

Hi,

On Tue, 2006-04-11 at 16:05 +0200, Matthias Bayer wrote:
> i have serveral DomU''s running under Xen xen-3.0.1-4
kernel-xen0-2.6.16-1.2080_FC5.
> i have paravirtualized and fully virtualized systems (windows and
linux).
> now the problem is whenever i start 2 fully virtualized systems in
parallel (first start one then if this runs try to start the other one)
the computer completely crashes and reboots, no more log entries...
nothing.
> 
> does anybody now how to debug such a problem ? 
With serial console, usually.  There are also a number of upstream Xen
updates for VMX, and we''re putting together an update which may help
there.

Cheers,
 Stephen


--
Fedora-xen mailing list
Fedora-xen@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen


*****************************************************************
<<<Disclaimer>>>

In compliance with applicable rules and regulations, Instinet
reviews and archives incoming and outgoing email communications,
copies of which may be produced at the request of regulators.
This message is intended only for the personal and confidential
use of the recipients named above.  If the reader of this email
is not the intended recipient, you have received this email in
error and any review, dissemination, distribution or copying is
strictly prohibited. If you have received this email in error,
please notify the sender immediately by return email and
permanently delete the copy you received.  

Instinet accepts no liability for any content contained in the
email, or any errors or omissions arising as a result of email
transmission. Any opinions contained in this email constitute
the sender''s best judgment at this time and are subject to change
without notice.   Instinet does not make recommendations of a
particular security and the information contained in this email
should not be considered as a recommendation, an offer or a
solicitation of an offer to buy and sell securities.

*****************************************************************

Hi,

On Tue, 2006-04-11 at 11:24 -0400, Alex.Upton@instinet.com wrote:
> If I''m copying data to or from a virtualized host the parent
system will
> black screen without any kernel dump info, thus all i/o is halted and the
> only solution is a reboot.
> 
> Any thoughts?
The original problem described a spontaneous reboot, not a "black
screen" (what exactly do you mean by that, btw?  The screen saver kicks
in?)  And what do you mean by kernel dump info --- HV VGA output, dmesg
logs, or what?

Thanks,
 Stephen