[root@test2 images]# virsh attach-disk 1 /var/lib/libvirt/images/disk.qcow2 Âvdb Â--driver file --subdriver qcow2
Disk attached successfully
Here is the log I found relevant (too much under debug mode)
15:31:52.902: debug : virEventInterruptLocked:668 : Interrupting
15:31:52.902: debug : qemuMonitorCommandWithHandler:235 : Receive command reply ret=0 errno=0 30 bytes 'unknown command: 'drive_add'^M
'
15:31:52.902: debug : virEventRunOnce:595 : Poll got 1 event
15:31:52.902: debug : virEventDispatchTimeouts:405 : Dispatch 3
15:31:52.902: debug : qemuMonitorAddDevice:1878 : mon=0x7f3628341370 device=virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk1,id=virtio-disk1
15:31:52.902: debug : virEventDispatchHandles:450 : Dispatch 8
15:31:52.902: debug : qemuMonitorCommandWithHandler:230 : Send command 'device_add virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk1,id=virtio-disk1' for write with FD -1
Than you very much.
Shi
On Thu, Mar 3, 2011 at 10:12 PM, Wen Congyang <wency@xxxxxxxxxxxxxx> wrote:
It seems attaching virtio-disk1 failed.At 03/04/2011 01:00 PM, Shi Jin Write:
>>
>>
>>
>> Â Â <disk type='file' device='disk'>
>> Â Â Â <driver name='qemu' type='qcow2' cache='none'/>
>> Â Â Â<source file='/var/lib/libvirt/images/rhel6rc_64.img'/>
>> Â Â Â<target dev='hda' bus='ide'/>
>> Â Â Â<alias name='ide0-0-0'/>
>> Â Â Â<address type='drive' controller='0' bus='0' unit='0'/>
>> Â Â</disk>
>> Â Â<disk type='file' device='cdrom'>
>> Â Â Â<driver name='qemu' type='raw'/>
>> Â Â Â<source file='/var/lib/libvirt/images/test.iso'/>
>> Â Â Â<target dev='hdc' bus='ide'/>
>> Â Â Â<readonly/>
>> Â Â Â<alias name='ide0-1-0'/>
>> Â Â Â<address type='drive' controller='0' bus='1' unit='0'/>
>> Â Â</disk>
>> Â Â <disk type='file' device='disk'>
>> Â Â Â<driver name='file' type='qcow2'/>
>> Â Â Â <source file='/var/lib/libvirt/images/test3.img'/>
>> Â Â Â <target dev='vdb' bus='virtio'/>
>> Â Â Â <alias name='virtio-disk1'/>
>> Â Â Â<address type='pci' domain='0x0000' bus='0x00' slot='0x06'
>> function='0x0'/>
>> Â Â</disk>
>> Â Â<controller type='ide' index='0'>
>> Â Â Â<alias name='ide0'/>
>> Â Â Â<address type='pci' domain='0x0000' bus='0x00' slot='0x01'
>> function='0x1'/>
>> Â Â</controller>
>>
>>
>> Thank you very much. It is exactly the same output as mine, particularly
> Â<driver name='file' type='qcow2'/>
> I thought it has to be name='qemu' to detach properly but since you didn't
> have a problem, I am very lost on why mine didn't work.
>
> My libvirtd.log shows (with debugging turned on)
> 14:43:18.965: debug : qemuMonitorCommandWithHandler:235 : Receive command
> reply ret=0 errno=0 33 bytes 'Device 'virtio-disk1' not found^M
> '
> 14:43:18.965: debug : virEventDispatchTimeouts:405 : Dispatch 3
> 14:43:18.965: debug : virEventDispatchHandles:450 : Dispatch 8
> 14:43:18.965: error : qemuMonitorTextDelDevice:2314 : operation failed:
> detaching virtio-disk1 device failed: Device 'virtio-disk1' not found^M
>
> Do you know what the "device not found" error means?
Can you provide the log when you attach virtio-disk1?
Thanks.
Wen Congyang
>
> Thanks.
>
> Shi
>
--
Shi Jin, Ph.D.
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list