[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: 'Pasi Kärkkäinen' <pasik@xxxxxx>
  • From: "AP Xen" <apxeng@xxxxxxxxx>
  • Date: Tue, 18 Jan 2011 12:08:09 -0800
  • Cc: 'Xen-Devel' <xen-devel@xxxxxxxxxxxxxxxxxxx>, 'Konrad Rzeszutek Wilk' <konrad.wilk@xxxxxxxxxx>
  • Delivery-date: Tue, 18 Jan 2011 12:09:12 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; b=W2N3DsX+X2DeNFujB0SHSUi4I8G1cRyz0GtbBXy94wC9ZLSN9IShOEk7f1kH27oTGr TWF/r0efzIl/EpSTmWK1dhh0c4mPqR0BiG4QWoeVFyqCmmcL8H+0KJIQtLagomAd0Vyc hF0swpUe3dSorQX4a9W6DzC1ccmIOM4pBevjI=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acu3Sg1fN2HZNxulTEOm/leWCNxqkgAAPnMw

> -----Original Message-----
> From: Pasi Kärkkäinen [mailto:pasik@xxxxxx]
> Sent: Tuesday, January 18, 2011 11:58 AM
> To: AP Xen
> Cc: 'Konrad Rzeszutek Wilk'; '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:54:42AM -0800, AP Xen wrote:
> > > -----Original Message-----
> > > From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@xxxxxxxxxx]
> > > 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
> >
> 
> Well, you don't have a bridge called 'xenbr0'.
> So it won't work, like you noticed.
> 
> You seem to have a bridge called 'eth0' - use that instead in the domU
> cfg.

I tried using eth0, br2026b, br2026f but got the same error. The same
configuration works if I use the Xen version packaged with CentOS 5.5. 

> > > 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.
> >
> 
> This question is not suitable for xen-devel mailinglist.

Sorry about that. I only posted on xen-devel when I received no reply from
xen-users. Should I try posting again on xen-users?

Thanks,
AP
 
> -- Pasi



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.