StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHow to detach a disk from KVM correctly
primarykey
Id
15863255
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-04-07T14:03:37.177
FavoriteCount
0
LastActivityDate
2013-04-11T09:43:52.173
LastEditDate
2013-04-07T20:57:12.277
LastEditorUserId
2083165
OwnerUserId
2083165
ParentId
0
PostTypeId
1
Score
1
ViewCount
3912
LastEditorDisplayName
text
Body
When I try to detach a drive in KVM, I get the following error: <h1>virsh detach-disk vps_99 vde</h1> error: operation failed: disk vde cannot be detached - no PCI address for device I have tried google, but can't find anyone else with the same problem?? Here is the XML-dump of my VPS: <pre><code>(root@h2)-(/home/cloud)# virsh dumpxml vps_99 <domain type='kvm' id='218'> <name>vps_99</name> <uuid>42db1de2-f0d4-1030-ac57-0050560018a2</uuid> <memory>524288</memory> <currentMemory>524288</currentMemory> <vcpu>1</vcpu> <os> <type arch='x86_64' machine='pc-0.12'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='utc'/> <on_poweroff>restart</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/kvm</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/nbd1'/> <target dev='vda' bus='virtio'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/nbd2'/> <target dev='vdb' bus='virtio'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/nbd3'/> <target dev='vde' bus='virtio'/> </disk> <interface type='bridge'> <mac address='00:50:56:00:1b:24'/> <source bridge='br0'/> <target dev='vnet3'/> <model type='virtio'/> </interface> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='5903' autoport='yes' keymap='en-us'/> <video> <model type='cirrus' vram='9216' heads='1'/> </video> </devices> <seclabel type='dynamic' model='apparmor'> <label>libvirt-42db1de2-f0d4-1030-ac57-0050560018a2</label> <imagelabel>libvirt-42db1de2-f0d4-1030-ac57-0050560018a2</imagelabel> </seclabel> </domain> </code></pre> Another crazy thing is that the drive I specify as "vde" gets connected to the virtual server as "vdc" as if it is totally ignoring my "vde" specification. If someone can tell me how to make sure the drive is attached as the device I specify, I would be greatful. Amazon Web Services seems to be able to do it, so why should'nt I :) UPDATE: After the virtual machine has been started, it seems I can add and remove NEW disks without any problems. Seems it is only problems to detach disks that was defined in the original XML used to create the virtual server. But the question remains, how do I detach disks that was defined when the virtual server was defined? UPDATE 2: I have also tried adding a <code><address></code> entry for each disk to make sure each disk gets connected at a pre-defined slot, i.e <code><address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/></code> But still does not work to detach the disks and a "virsh dumpxml vps_99" actually shows that my entries has been entirely removed/ignored. UPDATE 3: I also tried putting the disk-definition in a temp XML-file and ran: virsh detach-device vps_99 disk.xml Still same error: error: Failed to detach device from disk.xml error: operation failed: disk vdi cannot be detached - no PCI address for device
Tags
<virtualization><kvm><libvirt>
Title
How to detach a disk from KVM correctly
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USDaniele Testa
UserOwnerUserId
1. USDaniele Testa
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.