From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Stabellini Subject: Re: error when boot guest with qcow2 Date: Mon, 1 Jun 2009 13:17:48 +0100 Message-ID: <4A23C6EC.5060203@eu.citrix.com> References: <10C63FAD690C13458F0B32BCED571F14026DA1668D@pdsmsx502.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <10C63FAD690C13458F0B32BCED571F14026DA1668D@pdsmsx502.ccr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Zhang, Yang" Cc: "dmeyer@cs.ubc.ca" , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Zhang, Yang wrote: > In the old config, the arg of disk is set to [ 'tap:qcow:/root/test.qcow,hda,w', ].I use this config to create guest. It shows the error as below: > Using config file: config.vmxCPL_MEM_02 > Error: need more than 3 values tp unpack > > Then i find the c/s 19647 changed the arg of disk to ['tap:tapdisk:qcow2:/root/test.qcow,hda,w','].But after using the new config, it still has the error: > Error: Device 768 (tap) could not be connected. Hotplug scripts not working. > > Is anyone meet the same issue? > I think the argument now is tap:aio:qcow