梁朝军
2021-May-21 15:28 UTC
How to hot plugin a new vhost-user-blk-pci device to running VM?
Thanks all of you for your help. One more question regarding vhost-user-blk-pci type device, how to identify a vhost-blk disk in QEUM VM ? for example, disk name looks like vda,vdb,..., but that some application in VM want to detect that a certain entry is really the device it is waiting for. Specific for windows , they always show as disk 0, 1, 2?.etc Is there any way to identify those disk with each other in VM? thanks> ? 2021?5?17????3:13?Michal Pr?vozn?k <mprivozn at redhat.com> ??? > > On 5/17/21 7:08 AM, Liang Chaojun wrote: >> >> Thanks Michal and Peter for your response. I? m running it on qemu 5.1 build by myself. BTW, follow Peter?s suggestion, where I can get the latest rpms if I want to upgrade to Libvirt 7.1? As I know it seems need more than twenty related rpms not include dependency. > > Well, since you're building qemu yourself you could also build libvirt. > Just be aware that the v7.3.0 release was the last one that supports > RHEL-7. Newer releases might still work, but upstream does not aim to > make everything work. > > https://libvirt.org/platforms.html > > Michal >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20210521/1fcb7f3c/attachment.htm>
Michal Prívozník
2021-May-24 11:04 UTC
How to hot plugin a new vhost-user-blk-pci device to running VM?
On 5/21/21 5:28 PM, ??? wrote:> Thanks all of you for your help. > One more question regarding vhost-user-blk-pci type device, how to identify a vhost-blk disk in QEUM VM ? for example, disk name looks like vda,vdb,..., but that some application in VM want to detect that a certain entry is really the device it is waiting for. Specific for windows , they always show as disk 0, 1, 2?.etc > Is there any way to identify those disk with each other in VM?In general no. Usually disks will be enumerated sequentially - thus the first disk on a sata/scsi/usb/.. bus will be sda, the second will be sdb, and so on. But libvirt can't guarantee it - the same way you can't guarantee how a disk is going to be called with real HW. Michal