[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: Fri, 29 Sep 2006 11:02:49 -0400
- Delivery-date: Fri, 29 Sep 2006 08:03:34 -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=kR99AFnpN2HlxThC2HQEbc8UjyjiWyQlHJn7hcYh/HaO0ajJ6akMhYm/3llOmIOraBs1IhvmSxjqE/8w2PJDhUYQAsuIe9PWpap6J9sBdjodxA9rPx7uUlicQO3gZMWgS/8iHICq4/0Ohikot3EJyfoj8qaBmu54KSwApyVQG04=
- List-id: Xen user discussion <xen-users.lists.xensource.com>
Finally, I've got the dscow_tool & cowd binary files. Yet, I have another question. Is there any limitation of the size of image that dscow_tool can create? Because I successfully created dscow image from 1GB image or smaller image but
2.1 GB. I've got the error "segmentation fault" for 2.1GB image.
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
|