Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1585991
Summary: | RFE: support qemu ppc64 powernv machine | ||
---|---|---|---|
Product: | [Community] Virtualization Tools | Reporter: | Dan Horák <dan> |
Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> |
Status: | CLOSED DEFERRED | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | agedosier, berrange, clalancette, clg, crobinso, dan, hannsj_uhl, itamar, jforbes, laine, libvirt-maint, veillard |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | ppc64le | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-02-12 15:19:33 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1071880 |
Description
Dan Horák
2018-06-05 09:05:36 UTC
after swapping the IDE disk to virtio based one and removal of IDE CD-ROM (using the "Edit config before installation" option it gets a bit further, now complains about incorrect CPU type Looks like virt-manager creates wrong defaults for the VM. Reassigning. I can't find any real examples of working powernv qemu command lines that virt-manager is going to realistically support. Dan is this something you expect to work? Even with a minimal config: <domain type="qemu"> <name>fedora-unknown-ppc64</name> <uuid>3f936d40-b22c-4a27-b174-ee5198325e8b</uuid> <memory>2097152</memory> <currentMemory>2097152</currentMemory> <vcpu>1</vcpu> <os> <type arch="ppc64" machine="powernv">hvm</type> <boot dev="hd"/> </os> <clock offset="utc"/> <devices> <emulator>/usr/bin/qemu-system-ppc64</emulator> </devices> </domain> Libvirt tries to add memballoon, usb, pci, which fails since there's no pci bus for this machine type. Explicitly model='none' on those devices, I still get this: error: Failed to start domain fedora-unknown-ppc64 error: internal error: process exited while connecting to monitor: 2018-06-07T15:13:52.863105Z qemu-system-ppc64: error creating device tree: (fdt_property_string(fdt, "system-id", buf)): FDT_ERR_BADMAGIC Good question, /me now wonders if it's supposed to work with a virtio disk image and a network device at all, instead of being useful only for skiboot testing. But I've found http://www.kaod.org/openpower/qemu/ which makes me a a little optimistic, but likely we are not there yet. As far as I know, the powernv machine in upstream QEMU is still quite incomplete. I just asked Greg on IRC, and he pointed me to try https://github.com/legoater/qemu/commits/powernv-3.0 which should be more advanced, e.g. there is a PCI controller now (see https://github.com/legoater/qemu/commit/208a08b03f31bfa7c6). The PowerNV QEMU machine does not have a PCI host bridge controller model. So adding any storage or net devices will just fail. If you want to give it a try, the tree https://github.com/legoater/qemu has a model for the PHB3 (POWER8 PCI controller). This is currently under discussion and, possibly, it will be merged in 3.1. I think we can close this bz, I have made qemu 4.2 + powernv patchset available in https://copr.fedorainfracloud.org/coprs/sharkcz/talos/. It's a drop-in replacement for qemu from the virt-preview repo. |