[Xen-bugs] [Bug 1247] New: Cascade failure when creating multiple domU's requires dom0 reboot

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1247

           Summary: Cascade failure when creating multiple domU's requires
                    dom0 reboot
           Product: Xen
           Version: unspecified
          Platform: x86-64
        OS/Version: Linux
            Status: NEW
          Severity: critical
          Priority: P2
         Component: Guest-OS
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: jpeacock@xxxxxxxxxxxxxxxxxx


Running on Dual Core AMD Opteron(tm) Processor 280 (x86_64), 8GB RAM

Xen:  Xen 3.2.1 (built using modified RHEL 3.2.0 source RPM)
libvirt: 0.4.2 (built from source RPM)
dom0: Centos5/x86_64 (2.6.18-53.1.14.el5xen)
domU's: Centos5/x86_64, Centos5/i386, Centos4/x86_64, Centos4/i386

BACKGROUND:
I have been writing a Test::VM module for use in our in-house test
infrastructure. It relies on using LVM volumes for base domU installs and then
LVM snapshots to install our product for testing.  Performance was much better
than running VMWare instances and the module was nearly function complete.

For the last 10 days or so, I have been having problems where I get the
dreaded:

  Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

and once that happens, I must reboot the machine before I can start a domU
again.  I've tried the "nuke the tdb file" fix multiple time and uninstalled
and reinstalled the entire Xen toolchain.  What was formerly very stable is now
totally fragile and unpredictable.

I've eliminate LVM from the equation and the last domU I created a non-sparse
file and used the tap:aio driver (not loopback).  I was able to install
Centos4/i386 in the image and start it up again (where I updated the packages).
 I ran "poweroff" from within the domU and it came down fine (the domU was
destroyed properly).

However, trying to start up the same domU again, from the same conf file that
just worked locks up with the above error.  xenstore-ls reveals partially
configured vif and vbd stanzas (deleting them has no effect).  I once again had
to reboot the box to get Xen back in operation.

It doesn't appear I can attach log files from the "create bug" screen, so I'll
try and do so after the bug is added.


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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