summaryrefslogtreecommitdiffstats
path: root/include/hw/ppc/spapr.h
diff options
context:
space:
mode:
authorAlexander Graf <agraf@suse.de>2014-07-24 10:46:47 +0200
committerAlexander Graf <agraf@suse.de>2014-09-08 12:50:45 +0200
commit277c7a4d717aedbcb253ca152ae4da67e4162470 (patch)
treeb579e5b34ded96331467a51087e2926057c298d2 /include/hw/ppc/spapr.h
parent30eaca3acdf17d7bcbd1213eb149c02037edfb0b (diff)
downloadhqemu-277c7a4d717aedbcb253ca152ae4da67e4162470.zip
hqemu-277c7a4d717aedbcb253ca152ae4da67e4162470.tar.gz
PPC: KVM: Fix g3beige and mac99 when HV is loaded
On PPC we have 2 different styles of KVM: PR and HV. HV can only virtualize sPAPR guests while PR can virtualize everything that's reasonably close to the host hardware platform. As long as only one kernel module (PR or HV) is loaded, the "default" kvm type is the module that's loaded. So if your hardware only supports PR mode you can easily spawn a Mac VM. However, if both HV and PR are loaded we default to HV mode. And in that case the Mac machines have to explicitly ask for PR mode to get a working VM. Fix this up by explicitly having the Mac machines ask for PR style KVM. This fixes bootup of Mac VMs on systems where bot HV and PR kvm modules are loaded for me. Signed-off-by: Alexander Graf <agraf@suse.de>
Diffstat (limited to 'include/hw/ppc/spapr.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud