[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: Tue, 3 Oct 2006 11:21:05 -0400
- Delivery-date: Tue, 03 Oct 2006 08:22:28 -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=JMPy08Div6+KFNhHIPc+0ufjOrkQKl6zY13vWucJwe+ry2Q/cyWoM3l8jXv9BA6hk6W+pJRjcY2gKMPnVrS/ytdf0+YVgTHN3/wlYY1KjX4+FMIhwFieoC4qhHVxPDrg3YH70tKP+Wzn4Y4W+FhRelA0ZI89gU7jdZGBe/hMjts=
- List-id: Xen user discussion <xen-users.lists.xensource.com>
Even though I don't see /dev/mapper/windowsbase listed, it works. Despite that, some settings, e.g. colors, was a bit weird.
Yet I have some questions. Why is the .dscow file the same size as the .img file when originally created? We didn't copy the entire .img file, did we? If not, what originally are in the .dscow file when created? If the .dscow file is originally empty, after used (xm create->modify->shut it down), is there a way to delete the changes in the .dscow file without openning up the domain? We use /dev/mapper to map any further modifications onto the .dscow file, right? And /dev/mapper/ would be changed every time we modify on the .dscow file, right?
Thank you very much.
On 10/3/06, Orathai Sukwong <kobkob@xxxxxxxxx> wrote:
I killed all cowd instance. When I did "losetup -d /dev/loop0", I got
"ioctl: LOOP_CLR_FD: Device or resource busy." Then I tried
#losetup /dev/loop0
/dev/loop0: [0803]:2981891 (/xenimages/windowsbase.img)
# losetup /dev/loop1
/dev/loop1: [0803]:2981898 (/xenimages/windowsbase.dscow)
# cowd -p dscow --sync=a windowsbase /xenimages/windowsbase.dscow
ioctl: LOOP_SET_FD: Device or resource busy
ioctl: LOOP_SET_FD: Device or resource busy
ioctl: LOOP_SET_FD: Device or resource busy
ioctl: LOOP_SET_FD: Device or resource busy
ioctl: LOOP_SET_FD: Device or resource busy
device-mapper: create ioctl failed: Device or resource busy
Failed to run device-mapper command!
Failed to create DM device
And "fdisk -l" didn't show /dev/mapper. Thank you.
On 10/2/06,
Dan Smith <
danms@xxxxxxxxxx> wrote:
OS> Even though I did losetup -f, I still got the same error.
Try doing "losetup -d /dev/loopX" for X between 0 and 3, just to make
sure they're disconnected. Make sure all cowd instances are stopped
first, though.
However, that loop error is normal in some cases. After starting, see
if cowd is running. If so, try to access the device in /dev/mapper
(fdisk -l should show a partition listing I think).
--
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
|
