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/
Home Products Support Community News


Re: [Xen-devel] xl create

To: Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
Subject: Re: [Xen-devel] xl create
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Tue, 14 Jun 2011 10:04:31 +0100
Cc: Keir Fraser <keir@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Delivery-date: Tue, 14 Jun 2011 02:10:26 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4DF12A42.2090502@xxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Citrix Systems, Inc.
References: <4DF12A42.2090502@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, 2011-06-09 at 21:17 +0100, Jonathan Tripathy wrote:
> Hi Everyone,
> I'm having some problems with the new xl command.

Which specific version of Xen are you running?

>  When I try to start my 
> DomU by doing xl create config.xen, I get the following error:
> Parsing config file config.xen
> the rate parameter for vifs is currently not supported
> libxl: error: libxl_device.c:476:libxl__wait_for_device_model Device 
> Model not ready
> xl: fatal error: libxl_create.c:535, rc=-1: 
> libxl__confirm_device_model_startup

It looks to me as if your config should not need to start a device model
in the first place.

Do you have a version of Xen which has 23044:d4ca456c0c25 "libxl: do not
start a xenpv qemu solely for tap devices if blktap is available" in it?

I don't recall if the problem when this happened was a failure (such as
the above) or just a wasted process but it would be worth trying IMHO.

I thought that change was in xen-4.1-testing.hg but it looks like it

IanJ/Keir can we backport that one please?

> My config.xen file looks like this:
> bootloader = "/usr/bin/pygrub"
> memory = 128
> name = "u23018"
> vif = [ 
> 'ip=,bridge=public,script=vif-bridge,mac=00:16:3e:29:a2:24,rate=50Mb/s,vifname=vifu23018'
> ]
> #disk = 
> ['file:/home/sysadmin/xen/ubuntu-10.04-x86_64/ubuntu.10-04.x86-64.20100426.img,sda1,w']
> disk = ['phy:/dev/vg0/u23018,xvda1,w']
> root = "/dev/xvda1"
> extra = "fastboot"
> on_poweroff = 'destroy'
> on_reboot   = 'restart'
> on_crash    = 'restart'
> Even when I comment out the vif line, the above problem still persists. 
> I'm using CentOS 5.6 x86_64 as my DomU with kernel 2.6.18-238.12.1.el5xen
> Using the xm command works fine.
> Any help is appreciated.
> Thanks
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

Xen-devel mailing list

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