|
|
|
|
|
|
|
|
|
|
xen-users
Re: [Xen-users] CoW works on Windows guest?
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
|
|
|
|
|