WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 743] Unable to start more than a few domU's on RHEL4 amd

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 743] Unable to start more than a few domU's on RHEL4 amd64 (Error: Backend device not found)
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Tue, 29 Aug 2006 08:53:50 -0700
Delivery-date: Tue, 29 Aug 2006 08:54:43 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <bug-743-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=743





------- Comment #16 from tejasvia@xxxxxxxxx  2006-08-29 08:53 -------
I can confirm that after starting 4 VM's, when I try starting the fifth VM, I
always hit this problem.

$ sudo xm list
Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0      869     1 r-----  1561.7
vm1                                1       30     2 -b----     3.4
vm10                               2       30     2 -b----     3.5
vm2                                3       30     2 -b----     3.4
vm9                                4       30     2 -b----    10.0


Starting the fifth VM fails with

[ 1867.261450] XENBUS: Timeout connecting to device: device/vbd/769 (state 3)
[ 1867.261465] XENBUS: Timeout connecting to device: device/vbd/770 (state 3)
[ 1867.261473] XENBUS: Timeout connecting to device: device/vbd/771 (state 3)
[ 1867.261834] VFS: Cannot open root device "hda1" or unknown-block(0,0)
[ 1867.261844] Please append a correct "root=" boot option
[ 1867.261852] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
----

and anything afterwards is failing with:

$ sudo xm create -c vm8/*config
Using config file "vm8/vm8-config".
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

I shall attach the xm log and the syslog exactly corresponding to the above
VM's next, and the message "Couldn't get fd for AIO poll support" is logged for
the failing VM's.


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

<Prev in Thread] Current Thread [Next in Thread>