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

To:	xen-users@xxxxxxxxxxxxxxxxxxx
Subject:	Re: [Xen-users] CoW works on Windows guest?
From:	"Orathai Sukwong" <kobkob@xxxxxxxxx>
Date:	Fri, 29 Sep 2006 09:08:04 -0400
Delivery-date:	Fri, 29 Sep 2006 06:09:00 -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=F7lda1XipyT5QIOTLXaAQk0ZU12X5UShXh7BgBo0M2Lv0hZihHgJFXQ10yTkUBUNcIqFSRwSeQWtQkB7sA+Z3h2v/liEk27XBosUXkWQLhBDW5kW53t+3tntOK6PL08BcgSfDKnhHn3me6zmQk5a0pgJoympCfURVZKlKVxoH8w=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<m364f74jr1.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help:	<mailto:xen-users-request@lists.xensource.com?subject=help>
List-id:	Xen user discussion <xen-users.lists.xensource.com>
List-post:	<mailto:xen-users@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References:	<748f85310609280723l49ca9725nf6a28fa234c1353f@xxxxxxxxxxxxxx> <m3psdf51av.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <748f85310609281151q586a21b7if3a97e384f59eae9@xxxxxxxxxxxxxx> <m364f74jr1.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender:	xen-users-bounces@xxxxxxxxxxxxxxxxxxx

Thank you very much for your help. Which version of Xen source are you using for those patches? I've been working on it but I still cannot get it successfully patched and compiled.

Thank you,

On 9/28/06, Dan Smith <danms@xxxxxxxxxx> wrote:

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

If you applied the dm-userspace patches to your xen tree and either
rebuilt and installed the whole tree, or at least the tools part, you
should have "dscow_tool" and "cowd" binaries on your system.  If you
don't see them, check in the tools/ directory of your tree

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

Do this:

  # dscow_tool -c /xenimages/windowsbase.dscow /xenimages/windowsbase.img

Which will create the cow file.  Then do:

  # cowd -p --sync=a dscow windowsbase /xenimages/windowsbase.dscow

Which will create a /dev/mapper/windowsbase device.  Any writes to
this device will be stored in the .dscow file; the .img file will
remain untouched.  Then, configure your domain to use the new device
with something like this:

  disk = [ '/dev/mapper/windowsbase,ioemu:hda,w' ]

(I'm not all that familiar with HVM config files, so adjust the above
line as appropriate)

Note that all the above assumes you have the dm-user.ko module
loaded.  If you built and installed Xen with the dm-userspace patches,
you should be able to just do:

  # modprobe dm-user

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