Bug 973616
| Summary: | [TEXT] Change error description in engine.log “Cannot attach Virtual Machine Disk. Maximum PCI devices exceeded” | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | vvyazmin <vvyazmin> | ||||
| Component: | ovirt-engine | Assignee: | Michal Skrivanek <michal.skrivanek> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | meital avital <mavital> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.2.0 | CC: | abaron, acathrow, amureini, iheim, jkt, lpeer, michal.skrivanek, Rhev-m-bugs, scohen, sgotliv, tcarlin, yeylon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.4.0 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | virt | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-02-28 07:29:35 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Get error : Operation Failed: [Cannot attach Virtual Machine Disk. Maximum PCI devices exceeded. Maximum is 26 PCI or 3 IDE devices to one VM] i believe its 26 PCI and 3 IDE devices. but how does customer knows what's a PCI device? enabled smartcard? virtio-console, virtio-scsi has a controller when you first attach it, besides the disk (but then the disk doesn't need to be counted iirc), etc? (i.e., not sure the MAX_PCI_SLOTS is actually up to date?) flagging as storage to work with virt since the virtio-scsi is probably the most impact here. (In reply to Itamar Heim from comment #1) > Get error : Operation Failed: [Cannot attach Virtual Machine Disk. Maximum > PCI devices exceeded. Maximum is 26 PCI or 3 IDE devices to one VM] > > i believe its 26 PCI and 3 IDE devices. > but how does customer knows what's a PCI device? > enabled smartcard? virtio-console, virtio-scsi has a controller when you > first attach it, besides the disk (but then the disk doesn't need to be > counted iirc), etc? > (i.e., not sure the MAX_PCI_SLOTS is actually up to date?) > > flagging as storage to work with virt since the virtio-scsi is probably the > most impact here. I don't see what virtio-scsi has to do here. It requires a single controller (i.e. single slot) and all disks are on it and don't affect PCI (we've tested with close to 1000 devices). This same issue will happen if you attach many NICs or other devices. This is a pure virt issue The limit check has been updated during ppc development, it should be correct. Counts known devices..having a more specific message is probably too complex. Seems to me fine as it is |
Created attachment 760092 [details] ## Logs rhevm Description of problem: Change error description in engine.log “Cannot attach Virtual Machine Disk. Maximum PCI devices exceeded” Version-Release number of selected component (if applicable): RHEVM 3.2 - SF17.5 environment: RHEVM: rhevm-3.2.0-11.30.el6ev.noarch VDSM: vdsm-4.10.2-22.0.el6ev.x86_64 LIBVIRT: libvirt-0.10.2-18.el6_4.5.x86_64 QEMU & KVM: qemu-kvm-rhev-0.12.1.2-2.355.el6_4.5.x86_64 SANLOCK: sanlock-2.6-2.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Create 50 disks with 'VirtIO' interface 2. Attached all disks to one VM Actual results: Get error : Operation Failed: [Cannot attach Virtual Machine Disk. Maximum PCI devices exceeded.] Expected results: Get error : Operation Failed: [Cannot attach Virtual Machine Disk. Maximum PCI devices exceeded. Maximum is 26 PCI or 3 IDE devices to one VM] Impact on user: Workaround: Additional info: /var/log/ovirt-engine/engine.log 2013-06-12 13:18:37,543 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (ajp-/127.0.0.1:8702-22) Operation Failed: [Cannot attach Virtual Machine Disk. Maximum PCI devices exceeded.] 2013-06-12 13:18:37,755 INFO [org.ovirt.engine.core.bll.AttachDiskToVmCommand] (ajp-/127.0.0.1:8702-17) [7a57f146] Lock freed to object EngineLock [exclusiveLocks= key: 18937d45-1fa0-4603-a211-9a254e45f8e8 value: DISK , sharedLocks= ] /var/log/vdsm/vdsm.log From investigation in code with Omer Frenkel we found folowing: // 26 PCI slots: 31 total minus 5 saved for qemu (Host Bridge, ISA Bridge, // IDE, Agent, ACPI) public final static int MAX_PCI_SLOTS = 26; // 3 IDE slots: 4 total minus 1 for CD public final static int MAX_IDE_SLOTS = 3;