Re: [Xen-users] Xen 3.0.2-2 + linux-2.6-xen-fedora

[Adrian Chadd <adrian@xxxxxxxxxxxxxxx>]

On Tue, Sep 19, 2006, Christophe Saout wrote:

> XEN-Hypervisor and XEN-Tools from the xen-unstable tarballs (from about
> the same date, 0815 and 0915). While it all usually worked well, I've
> seem some strange things sometimes.
> 
> After a domain crash or some manual destroys, xm suddenly told me
> "Domain 0 not connected". After a restart of xend, "xm list" worked
> again, but any further "xm create" would fail with "hotplug not
> working" (for the vif device). I also had some undestroyed vif devices
> from destroyed domains dangling around.
> 
> I don't see how hotplug (or udev to be precicse) should suddenly fail.
> And what is "Domain 0 not connected" about? It seems like something
> suddenly forgot its state and really got confused. The vif devices
> should have been destroyed by xend and not hotplug, right?
> 
> The only way to "fix" the problem was to reboot the machine. Has anybody
> else seen something like that?

Yeah - my 2.6.17 paravirt kernels from FC5 will crash (and I didn't get
a stack trace when this happened, but I will next time!) and they'll
actually take the networking for all other xen's down with them.

xm shutdown will successfully shut the domU environment down but it'll
zombie the kernel instead of cleanly destroying the domain.
I have to reboot to recover. restarting xend doesn't do anything
(and I haven't checked the logs to see what it failed to do, save
being unable to destroy domains..)

Its a bit weird that a domU crashing can take out everything else.
I'd hate to find someone reliably replicating it and using it as a
DoS.. :/




Adrian


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users