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

Re: [Xen-users] Windows XP HVM on qcow diskfile and snapshots


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Brian Conway <xen@xxxxxxx>
  • Date: Sat, 11 Apr 2009 23:50:16 -0400
  • Delivery-date: Sat, 11 Apr 2009 20:51:12 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:subject:message-id:in-reply-to:references :x-mailer:mime-version:content-type:content-transfer-encoding; b=jMx+tb83DXy5x3pTzp07KSVe3YfEOt+isboCGo3+HaSpGXeul7BEVgNtnm0jpIhV9G iBueXl+fkDqQvc+heTDPMrbUIlMmJAnzz3e/V+L+M+xRR/trtLT9EpmzzYDR3uzQRhSf qMqN6AjQdE9JNkWZo9XUIKxFeypbCNavlEPf0=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Sat, 11 Apr 2009 16:10:21 +0200
Geert Janssens <info@xxxxxxxxxxxx> wrote:

> * Created a copy-on-write disk image, based on my original image with
> qemu-img create -b <original image> -fmt qcow <new image>
> and changed the blockdevice line in my config file to
> disk = [ 'tap:qcow:<new image>,hda,w', ',hdc:cdrom,r' ]
> 
> However, this configuration won't boot. To be exact, the guest aborts
> very shortly after the bios hard drive discovery. So I presume the
> copy-on-write disk image is somehow not working.
> 
> Any hints on what goes wrong here ?

I have the same problem with a freshly created qcow2 image using the
qemu-img-xen tool.  The original qcow2 image works perfectly with
tap:qcow2, but attempting to use it as a base for a new image halts the
boot immediately.  The xend.log file don't show any errors, it only
points me to the VM-specific log, which just stops dead.

Perhaps this functionality isn't supported?

Brian Conway

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


 


Rackspace

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