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

Re: [Xen-devel] Failed to create a VM on -unstable

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Failed to create a VM on -unstable
From: Jun Koi <junkoi2004@xxxxxxxxx>
Date: Mon, 22 Jun 2009 17:38:57 +0900
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 22 Jun 2009 01:39:19 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=zyusZfY0g6w1k96PS2Td/fSzSB0C4AwmHOTADHjn3to=; b=RIIWzERVAaNNqNe4zTSEUUI/XfRwVp2ShKGL7fMsThgMIjZ8Vqz/DENsWw7PZtTiJq IfmI8alvEIfI9L78h0R1TrCHdrW1LPi17H7zN/4scdUM4biYEKNx40Ik5eiDwXYaE4if UMKUNWgkDLSt+GyzGk2iR9xj0YK5TU/a38NZU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ORvP009/RUPYRkHNrWDVnmF1a769gc62DuGXv1Sdkuyw1aPdbboHYbZKvJdzmZPsVK +s7y3LaXtZHLn7gD4yMoJ0u35r0J2dMW5J9ljbTQM9PdANsBQV1c55Dyd5IDnmYyGrBm iFo/h8OjI7jN2ESUm2yGqDyVXeVWW09MIG0Fs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C664F4E1.DCCE%keir.fraser@xxxxxxxxxxxxx>
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>
References: <fdaac4d50906220036y707e012dtf9ed95ffec1060df@xxxxxxxxxxxxxx> <C664F4E1.DCCE%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, Jun 22, 2009 at 4:44 PM, Keir Fraser<keir.fraser@xxxxxxxxxxxxx> wrote:
> On 22/06/2009 08:36, "Jun Koi" <junkoi2004@xxxxxxxxx> wrote:
>
>> Or do you think that the new version of Xen requires some change in below
>> line:
>>
>> vif = ['type=ioemu']
>>
>>
>> This same configuration works with older version 3.3.1.
>
> I think you should get rid of the dhcp= line from your config. It can't be
> doing good.
>

Thanks, it is a bit better now - I dont see that error anymore.
However, it still fails to create a VM, with the following report:

"Error: Device 0 (vif) could not be connected. Hotplug scripts not working."

And qemu log file is like below. I dont see much information, except
that xs_read() failed. Do you have any

Thanks,
J


domid: 1
qemu: the number of cpus is 1
config qemu network with xen bridge for  tap1.0 xenbr0
Strip off blktap sub-type prefix to /home/xenvms/img.qcow2.ubuntu904
(drv 'qcow2')
Watching /local/domain/0/device-model/1/logdirty/next-active
Watching /local/domain/0/device-model/1/command
qemu_map_cache_init nr_buckets = 4000 size 327680
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = 9b962fea-e2ed-747c-fac7-1e8d23d3889f
Time offset set 0
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
xs_read(/vm/9b962fea-e2ed-747c-fac7-1e8d23d3889f/log-throttling): read error
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/1/xen_extended_power_mgmt): read error
xs_read(): vncpasswd get error.
/vm/9b962fea-e2ed-747c-fac7-1e8d23d3889f/vncpasswd.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0

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