Bug 1563769
Summary: | XML error: Multiple 'scsi' controllers with index '0' | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | spf <spfma.tech> |
Component: | General | Assignee: | bugs <bugs> |
Status: | CLOSED DUPLICATE | QA Contact: | Pavel Stehlik <pstehlik> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.2.2 | CC: | bugs, michal.skrivanek, spfma.tech |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-16 12:59:15 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: |
Description
spf
2018-04-04 16:07:25 UTC
If that VM was incorrect before the problemativ device is already there. Try switching off virtio-scsi, run, turn it on again. Disable iothreads too. Give it a try, but it may be that a db update to drop that device is needed eventually. Yes, this VM was incorrect before. If I disable both virtio-scsi and iothreads, it can start. With only iothreads, it can start too. But if I also enable virtio-scsi, it fails. Could you explain me what to modify in the database ? I think I have found the required workaround that allows a VM with conflicting settings to be cured : - In the "vm_static" table, find the "vm_guid" related to the known "vm_name" - In the "vm_device" table, locate all "controller" devices related to this VM (vm_id = 'VM_GUID_FROM_PREVIOUS_STEP' AND type ='controller') - There will be a "device" record whose "value" is "scsi" : delete it Then I was able to configure all disks as "VirtIO-SCSI" devices again, using IO Threads, and the VM started flawlessly should be fixed by bug 1535961 *** This bug has been marked as a duplicate of bug 1535961 *** |