Bug 1788018
| Summary: | [VmDevicesMonitoring] ERROR managed non pluggable device was removed unexpectedly from libvirt: on vM start | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Michael Burman <mburman> |
| Component: | BLL.Virt | Assignee: | Liran Rotenberg <lrotenbe> |
| Status: | CLOSED DUPLICATE | QA Contact: | meital avital <mavital> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.4.0 | CC: | bugs, rbarry |
| Target Milestone: | ovirt-4.4.1 | Flags: | pm-rhel:
ovirt-4.4+
|
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-03-08 16:07:52 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: | |||
Shmuel - looks like a q35 side effect I see that the VM is created from template. Can you tell if the template you use created by a VM in which chipset? If it was made in Legacy BIOS than, the error is there and should be there. Libvirt will handle and remove the devices since now it is Q35. The error is a good indication to the user that he used a VM created on a different chipset in this scenario. Creating a VM on Q35 cluster and starting it don't invoke this error. Can you confirm on which chipset your VM was made? If what i'm thinking is right, then we can: 1. Update the devices to the new chipset. 2. Leave the error. In any case, I think you can't reproduce it (as I can't), because we are now executing option 1 above - since BZ 1770697 (https://gerrit.ovirt.org/#/c/105362/). Now you should see DEBUG and not ERROR, indicating new devices added. If you confirm, we can close the bug as a duplicate. *** This bug has been marked as a duplicate of bug 1775248 *** |
Description of problem: [VmDevicesMonitoring] ERROR managed non pluggable device was removed unexpectedly from libvirt: on vM start. Every time starting a VM on 4.4 engine, an error is shown in the engine log: 2020-01-06 09:15:23,201+02 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmDevicesMonitoring] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-5) [ ] VM 'e84c4d6b-64ee-4057-b46e-808caa74a16a' managed non pluggable device was removed unexpectedly from libvirt: 'VmDevice:{id='VmDeviceId:{deviceId='7ac35107-8c99-455d-9f6 8-46e555b9727d', vmId='e84c4d6b-64ee-4057-b46e-808caa74a16a'}', device='usb', type='CONTROLLER', specParams='[index=0, model=qemu-xhci]', address='', managed='true', plugg ed='false', readOnly='false', deviceAlias='usb', customProperties='[]', snapshotId='null', logicalName='null', hostDevice='null'} NO errors in vdsm logs and VM starts fine, but this error is always shown in the engine log. Version-Release number of selected component (if applicable): rhvm-4.4.0-0.13.master.el7.noarch vdsm-4.40.0-164.git38a19bb.el8ev.x86_64 libvirt-daemon-5.6.0-6.2.module+el8.1.0+4953+432c8346.x86_64 How reproducible: 100% Steps to Reproduce: 1. Start VM on 4.4.0-13 engine Actual results: managed non pluggable device was removed unexpectedly from libvirt: error in engine log Expected results: No errors in engine log