Bug 1198136
Summary: | Can't create m68k VM | ||||||
---|---|---|---|---|---|---|---|
Product: | [Community] Virtualization Tools | Reporter: | Mattias Ellert <mattias.ellert> | ||||
Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> | ||||
Status: | CLOSED DEFERRED | QA Contact: | |||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | unspecified | CC: | agedosier, berrange, clalancette, crobinso, itamar, jforbes, jtomko, laine, libvirt-maint, rbalakri, veillard, virt-maint | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-04-10 20:28:32 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: |
|
Description
Mattias Ellert
2015-03-03 13:05:01 UTC
Can you post the domain XML? It should be visible on the console when running virt-manager with the --debug option. The 'No PCI buses available' error means the domain does not have a PCI bus, but there are some devices that require a PCI address. Either virt-manager requests these devices, or libvirt adds them automatically. Memballoon and usb controller could be such devices, and you may need to disable them using: <memballoon model='none'/> <controller type='usb' model='none'/> Created attachment 998002 [details]
domain xml
Apart from memballoon and usb controller, which need to be disabled explicitly, libvirt assumes virtio-net needs a PCI address (/* Network interfaces */ section of qemuAssignDevicePCISlots) and that there is a IDE controller present. I don't know what buses are available for storage and networking on this architecture, but if libvirt's assumptions are wrong or it does not allow to represent these devices in the domain XML, you're welcome to send a patch: http://libvirt.org/contact.html QEMU also requires a -kernel image for this architecture (<os><kernel> element). Does the machine boot without network, without storage, with memballoon and usb disabled and a kernel image? No response, so just closing. The fact that libvirt doesn't work well with the esoteric qemu architectures is well known; to fix it's going to take someone to sit down with the debian images and command lines, patch libvirt to get them working, and then document how to invoke virt-install for each arch |