What does this mean? [root@potoroo qemu]# cat recovery.log /usr/bin/qemu-kvm -M pc -m 128 -smp 1 -monitor pty -boot c -hda /var/lib/xen/images/recovery.img -hdb /var/lib/xen/images/rto.img:c -net nic,macaddr=00:16:3e:22:5a:10,vlan=0 -net tap,fd=13,script=,vlan=0 -usb -vnc 0.0.0.0:0 qemu: could not open hard disk image '/var/lib/xen/images/rto.img:c' [root@potoroo qemu]#
[root@potoroo qemu]# ls -l /var/lib/xen/images/rto.img:c -rwx------ 1 root root 11999994368 Jan 9 17:03 /var/lib/xen/images/rto.img:c [root@potoroo qemu]# file /var/lib/xen/images/rto.img:c /var/lib/xen/images/rto.img:c: x86 boot sector, code offset 0x52, OEM-ID "NTFS ", sectors/cluster 8, reserved sectors 0, Media descriptor 0xf8, heads 255, hidden sectors 63, dos < 4.0 BootSector (0x80) [root@potoroo qemu]#
No selinux messages.
This filesystem is an image of a Windows partition, backed up with ntfsclone, restored, resized, cloned again (trying to eliminate alleged bad hardware sectors, a legacy of earlier problems). I expect /dev/hdb to be a "superfloppy" format drive which I can then manipulate into a partition on another virtual drive.
John Summerfield wrote:
What does this mean? [root@potoroo qemu]# cat recovery.log /usr/bin/qemu-kvm -M pc -m 128 -smp 1 -monitor pty -boot c -hda /var/lib/xen/images/recovery.img -hdb /var/lib/xen/images/rto.img:c -net nic,macaddr=00:16:3e:22:5a:10,vlan=0 -net tap,fd=13,script=,vlan=0 -usb -vnc 0.0.0.0:0 qemu: could not open hard disk image '/var/lib/xen/images/rto.img:c' [root@potoroo qemu]#
[root@potoroo qemu]# ls -l /var/lib/xen/images/rto.img:c -rwx------ 1 root root 11999994368 Jan 9 17:03 /var/lib/xen/images/rto.img:c [root@potoroo qemu]# file /var/lib/xen/images/rto.img:c /var/lib/xen/images/rto.img:c: x86 boot sector, code offset 0x52, OEM-ID "NTFS ", sectors/cluster 8, reserved sectors 0, Media descriptor 0xf8, heads 255, hidden sectors 63, dos < 4.0 BootSector (0x80) [root@potoroo qemu]#
No selinux messages.
This filesystem is an image of a Windows partition, backed up with ntfsclone, restored, resized, cloned again (trying to eliminate alleged bad hardware sectors, a legacy of earlier problems). I expect /dev/hdb to be a "superfloppy" format drive which I can then manipulate into a partition on another virtual drive.
I have not seen a reply to this; on the basis I really _must_ get something moving, I tried using /var/lib/xen/images/rto.img and that works fine.
Is something being too clever and misvalidating file names?