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

Re: [Xen-users] CoW works on Windows guest?


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Orathai Sukwong" <kobkob@xxxxxxxxx>
  • Date: Thu, 28 Sep 2006 14:51:52 -0400
  • Delivery-date: Thu, 28 Sep 2006 11:59:55 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=MC7KD4BiEEmZCQ8w3IxWKhVKseRay01X8KbgKGdcFRfpByCpZupQr5B8ZSggLSMee8F4+w5M35b0lNi/q4Tipx31gundHTS8rMbywf8pYq5ZeSIZlgsQOA6WPzWKnKifDARzHtnWSljrHbtiivjSQRhFZEKN6WKzbAU0318CPn8=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

However, if you start the cowd daemon ahead of time


My current dom0 was compiled from xen-3.0.2-2 source + dm patches. I cannot find the cowd daemon. I wonder if it is something I need to compile separately.
 

and point your
domain's disk at the target device (/dev/mapper/something), then it
should work.

 Which device do you mean for the target device? Previously, my installation configuration file was like disk = ["file:/xenimages/windowsbase.img,ioemu:hda,w" ]. Then, I changed to disk = ["dmu:dscow:/tmp/windowsbase.dscow:/xenimages/windowsbase.img,ioemu:hda,w" ]. Is the /tmp/windowsbase.dscow what you meant?

Thank you.

Note that qemu-dm should be able to use qcow files like qemu does, so
that may be the best option for you, if you're mostly interested in
HVM domains.

--
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms@xxxxxxxxxx



_______________________________________________
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®.