[Xen-bugs] [Bug 612] New: DomUs won't start because Vif connections die on start up

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

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

           Summary: DomUs won't start because Vif connections die on start
                    up
           Product: Xen
           Version: unstable
          Platform: x86-64
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: japh@xxxxxxxxxx
OtherBugsDependingO 549
             nThis:


I boot dom0 with the following grub entry:

title Xen 3.0 / XenLinux 2.6 - xen
kernel (hd0,0)/boot/xen-3.0.gz dom0_mem=512M com1=115200,8n1 console=com1
noreboot 
module /boot/vmlinuz-2.6-xen root=/dev/sda1 maxcpus=1 ro console=ttyS0,115200
console=tty0
module /boot/initrd-2.6.16-xen.img

On a dual core system.  When I try to start domains with xendomains script I
get the following:


hermes:~> sudo service xendomains start
Starting auto Xen domains: fc4_32Error: Device 0 (vif) could not be connected.
Backend device not found.
! mdv2006Error: Device 0 (vif) could not be connected. Backend device not
found.
! mdv2006_32Error: Device 0 (vif) could not be connected. Backend device not
found.
! ubuntuError: Device 0 (vif) could not be connected. Backend device not found.

And no domains are started.  In *some* cases "xm create -c DOMAIN" will work,
but just as often it tends to throw the same error.

This is blocking my ability to confirm the fix for bug 549, as I can no longer
get any DomUs started reliably.


-- 
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