RE: Error bringing up VMs with Xen 4.0.1 + 2.6.18-194.32.1.el5xen CentOS Dom0

["AP Xen" <apxeng@gmail.com>]

> -----Original Message-----
> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> Sent: Tuesday, January 18, 2011 11:24 AM
> To: AP Xen
> Cc: 'Xen-Devel'
> Subject: Re: [Xen-devel] Error bringing up VMs with Xen 4.0.1 + 2.6.18-
> 194.32.1.el5xen CentOS Dom0
> 
> On Tue, Jan 18, 2011 at 11:00:18AM -0800, AP Xen wrote:
> > I am running Xen 4.0.1 with a 2.6.18-194.32.1.el5xen CentOS Dom0. I
> built
> > and installed the Xen binaries from source. The systems boot
> successfully
> > however I am having issues bring up DomUs. Here is config:
> >
> >
> >
> > name = 'xyz'
> >
> > memory = 256
> >
> > vcpus = 1
> >
> > pae = 1
> >
> > vnc = 1
> >
> > vncunused = 1
> >
> > disk = [ 'phy:/dev/vg1/xyz,hda,w' ]
> >
> > vif = [ 'type=netfront,bridge=xenbr0,mac=04:01:3e:00:04:62' ]
> >
> > builder = 'hvm'
> >
> > kernel = '/usr/sbin/hvmloader'
> >
> > boot = 'c'
> >
> > device_model = '/usr/sbin/qemu-dm'
> >
> >
> >
> > When I do an xm create on the config, I get the following error:
> >
> > Error: Device 0 (vif) could not be connected. Hotplug scripts not
> working.
> 
> Does the 'xenbr0' interface exist?

Here is the output of "brctl show"
bridge name	bridge id		STP enabled	interfaces
br2026b		8000.001b2147d86c	no		eth2.2026
br2026f		8000.003048f5af19	no		eth1.2026
eth0		8000.003048f5af18	no		peth0
virbr0		8000.000000000000	yes		

> Have you tried to contact the xen-users mailing list instead of xen-
> devel?

I did and waited for 24 hrs and received no reply.

I also tried bringing up the VM without the "vif" parameter in the config.
The VM kernel panicked because it couldn't find the boot device.

Thanks,
AP