Bug 1862035
| Summary: | [ppc64le] 'sPAPR VSCSI' interface disk attachment is not seen from the guest. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Ilan Zuckerman <izuckerm> | ||||||
| Component: | BLL.Virt | Assignee: | Arik <ahadas> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | sshmulev | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 4.4.5 | CC: | ahadas, bugs, eshenitz, sshmulev | ||||||
| Target Milestone: | ovirt-4.4.7 | Keywords: | Automation, ZStream | ||||||
| Target Release: | 4.4.7 | Flags: | pm-rhel:
ovirt-4.4+
|
||||||
| Hardware: | ppc64le | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | ovirt-engine-4.4.7 | Doc Type: | Bug Fix | ||||||
| Doc Text: |
Previously, hot-plug of virtual disks with sPAPR VSCSI interface seemed to succeed but the disks were not seen within the guest operating system on PPC environments. Now, hot-plugging a virtual disk with sPAPR VSCSI interface to a running virtual machine on PPC environments is prevented since sPAPR VSCSI adapter doesn't support hot-plug.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2021-07-06 07:28:17 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | 1862059 | ||||||||
| Bug Blocks: | |||||||||
| Attachments: |
|
||||||||
|
Description
Ilan Zuckerman
2020-07-30 09:16:11 UTC
This is likely to be a platform issue - the device appears in the domain xml and libvirt keeps reporting it. I'd suggest to file another bug to libvirt/qemu about this and in RHV this should be tracked as a storage bug. Created attachment 1702923 [details]
qemu log of the vm
Updating steps to reproduce: Steps to Reproduce: 1. On PPC env, create rhel8 vm from template 2. Create sPAPR VSCSI disk and HOT PLUG it to the vm (state = started) Libvirt bug opened on this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1862059 Failed to hotplug the sPAPR VSCSI disk, in the UI the disk is in "inactive" status, Plus it is not visible from the guest.
Verified it according to these steps:
1. On PPC env, create rhel8 VM from template
2. Create sPAPR VSCSI disk and HOT PLUG it to the VM (state = started)
versions:
ovirt-engine-4.4.6.3-0.8.el8ev.noarch
vdsm-4.40.60.3-1.el8ev.ppc64le
logs:
engine log:
2021-04-11 17:23:44,468+03 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-32) [3d509b24] Command 'HotPlugDiskVDSCommand(HostName = host_mixed_1, HotPlugDiskVDSParameters:{hostId='bbd7e15e-c955-4359-91ef-7f2d823b80af', vmId='2c3cc011-2f22-47ef-a14b-7a3a764b1951', diskId='fa9d5a74-ac6c-4d86-97b2-b807c19e0490'})' execution failed: VDSGenericException: VDSErrorException: Failed to HotPlugDiskVDS, error = internal error: unable to execute QEMU command 'device_add': Bus 'scsi0.0' does not support hotplugging, code = 45
audit log :
VDSM host_mixed_1 command HotPlugDiskVDS failed: internal error: unable to execute QEMU command 'device_add': Bus 'scsi0.0' does not support hotplugging
Failed to plug disk New_VM_Disk1 to VM New_VM (User: admin@internal-authz).
What is the RHEL version of the host? and that of qemu-kvm please Red Hat Enterprise Linux release 8.4 (Ootpa) QEMU emulator version 5.2.0 (qemu-kvm-5.2.0-14.module+el8.4.0+10425+ad586fa5) Thanks. Reading bz 1862059 more carefully, that's ok since spapr vscsi adapter doesn't support hotplug (see https://bugzilla.redhat.com/show_bug.cgi?id=1862059#c15) Verified. versions: ovirt-engine-4.4.7-0.23.el8ev.noarch QEMU emulator version 5.2.0 (qemu-kvm-5.2.0-16.module+el8.4.0+10806+b7d97207) Steps: 1) On a PPC env, start a VM and try to plug the sPAPR VSCSI interface to it (hotplug). 2) Repeat the above with the stopped VM (cold plug). Expected results: 1) Action should be blocked 2) Action should not be blocked and the attached disk is visible from the VM as well as from the UI admin. Actual results as expected. This bugzilla is included in oVirt 4.4.7 release, published on July 6th 2021. Since the problem described in this bug report should be resolved in oVirt 4.4.7 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |