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: Mon, 28 Aug 2006 20:27:26 -0700
Delivery-date: Mon, 28 Aug 2006 20:28:27 -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 #11 from tejasvia@xxxxxxxxx  2006-08-28 20:27 -------
Hi Andrew:

It is the correct kernel - unstable (based on 2.6.16.13 in my download)

<tejasvia@compute-5-24>
$ zcat /proc/config.gz | egrep "POLL|BLKDEV"
CONFIG_EPOLL=y
CONFIG_NETPOLL=y
# CONFIG_NETPOLL_RX is not set
CONFIG_NETPOLL_TRAP=y
CONFIG_NET_POLL_CONTROLLER=y
CONFIG_EDAC_POLL=y
CONFIG_XEN_BLKDEV_BACKEND=y
CONFIG_XEN_BLKDEV_TAP=y
CONFIG_XEN_BLKDEV_FRONTEND=y

<tejasvia@compute-5-24>
$ uname -a                                                                      
Linux compute-5-24.palab.panasas.com 2.6.16.13-xen #2 SMP Mon Aug 28 15:19:51
EDT 2006 x86_64 x86_64 x86_64 GNU/Linux  


I start the VM's sequentially using xm create
# xm create -c <config_file>

Infact, realising that some race might be the cause for the problems, I even
waited for each domU to boot up completely before trying to start another one.

A sample config file looks as follows:
kernel="/usr0/VM/vmlinuz-2.6.16.13-xen"                                         
memory=25                                                                       
vcpus=2                                                                         
name="vm1"                                                                      
vif=[ '' ]                                                                      
dhcp="dhcp"                                                                     
disk=['tap:aio:/usr0/VM/vm1/vm1-fs.img,hda1,w',
'tap:aio:/usr0/VM/vm1/vm1-swap.img,hda2,w', 'tap:aio:/usr0/VM/nonw.img,hda3,r'] 
root="/dev/hda1"
extra="ro selinux=0 3"

The disk image, nonw.img is intended to be shared between the VM's, though
using different VBD's.

I am recompiling everything now, hoping it is a misconfiguration on my part
that is causing the problem.


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