Hi, When trying to attach a created volume to an instance using the virsh utility I am running into this error :- [] $ sudo virsh attach-device instance-00000015 disk.xml error: Failed to attach device from disk.xml error: internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk21' could not be initialized For experimental purpose I have libvirt 0.10.2 and QEMU 0.12.1. The volume to be attached is on a remote storage. Any idea what I might be missing ? Thanks, Vilobh
On 05/06/2014 02:51 AM, Vilobh Meshram wrote:> Hi, > > When trying to attach a created volume to an instance using the virsh utility I am running into this error :- > > > [] $ sudo virsh attach-device instance-00000015 disk.xml > > error: Failed to attach device from disk.xml > > error: internal error unable to execute QEMU command '__com.redhat_drive_add': Device 'drive-virtio-disk21' could not be initializedThat's an error message from RHEL qemu, and not available from upstream qemu nor triggered by upstream libvirt (that is, a RHEL-specific downstream patch to libvirt is attempting to use a downstream qemu command that upstream does not have). Have you opened a support ticket with Red Hat?> > > For experimental purpose I have libvirt 0.10.2 and QEMU 0.12.1. The volume to be attached is on a remote storage.This list is probably better suited to help if you can reproduce with upstream versions (libvirt 1.2.4 and qemu 2.0), or at a bare minimum, post the contents of disk.xml that is failing on you. It's hard to say whether the error is in libvirt (perhaps botched SELinux permissions getting in the way?) or in qemu; but since libvirt is just parroting qemu's error message, the investigation needs to look more at why qemu is throwing the message. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
The contents of disk.xml <disk type='network' device="disk"> <driver name="qemu" type="raw" cache="writeback"/> <source protocol="rbd" name="volumes/volume-3cd6fc4d-3855-49ca-820c-2e0db8f45085"> <host name='68.142.237.36' port='6789'/> </source> <target dev="vdg" bus="virtio"/> <auth username='client.admin'> <secret type='ceph' uuid='c621f0e9-49fc-4ac2-82a9-34aa80122e33'/> </auth> </disk> Trying to attach a volume created on CEPH RBD backend to an VM created. CanĀ¹t see meaningful information in QEMU log nor in libvirt logs. I have the needed CEPH libs installed like librbd, librados. On 5/6/14, 4:35 PM, "Eric Blake" <eblake@redhat.com> wrote:>On 05/06/2014 02:51 AM, Vilobh Meshram wrote: >> Hi, >> >> When trying to attach a created volume to an instance using the virsh >>utility I am running into this error :- >> >> >> [] $ sudo virsh attach-device instance-00000015 disk.xml >> >> error: Failed to attach device from disk.xml >> >> error: internal error unable to execute QEMU command >>'__com.redhat_drive_add': Device 'drive-virtio-disk21' could not be >>initialized > >That's an error message from RHEL qemu, and not available from upstream >qemu nor triggered by upstream libvirt (that is, a RHEL-specific >downstream patch to libvirt is attempting to use a downstream qemu >command that upstream does not have). Have you opened a support ticket >with Red Hat? > >> >> >> For experimental purpose I have libvirt 0.10.2 and QEMU 0.12.1. The >>volume to be attached is on a remote storage. > >This list is probably better suited to help if you can reproduce with >upstream versions (libvirt 1.2.4 and qemu 2.0), or at a bare minimum, >post the contents of disk.xml that is failing on you. It's hard to say >whether the error is in libvirt (perhaps botched SELinux permissions >getting in the way?) or in qemu; but since libvirt is just parroting >qemu's error message, the investigation needs to look more at why qemu >is throwing the message. > >-- >Eric Blake eblake redhat com +1-919-301-3266 >Libvirt virtualization library http://libvirt.org >
Maybe Matching Threads
- Virsh Attach Volume Fails
- Queries regarding Lustre Throughput Numbers with mdtest benchmark
- Queries regarding Lustre Throughput Numbers with mdtest benchmark
- Failure when mounting Lustre
- Re: failure when trying to add a channel device via virsh attach-device