* Henning Schild <[email protected]> [2017-08-22 13:42:22 +0000]:
> Am Mon, 21 Aug 2017 18:13:35 -0700 > schrieb Gustavo Lima Chaves <[email protected]>: > > > Hi, > > > > is testing xAPIC mode just a matter of having > > > > diff --git a/configs/qemu-vm.c b/configs/qemu-vm.c > > index e5a420a..6225be9 100644 > > --- a/configs/qemu-vm.c > > +++ b/configs/qemu-vm.c > > @@ -49,6 +49,7 @@ struct { > > .pci_mmconfig_end_bus = 0xff, > > .x86 = { > > .pm_timer_address = 0x608, > > + .apic_mode = > > JAILHOUSE_APIC_MODE_XAPIC, .vtd_interrupt_limit = 256, > > .iommu_units = { > > { > > > > ? If so, it gives me a segv right away, with > > > > Initializing Jailhouse hypervisor v0.7 (36-g0b1b884-dirty) on CPU 3 > > Code location: 0xfffffffff0000060 > > Using xAPIC > > Page pool usage after early setup: mem 44/1480, remap 65/131072 > > Initializing processors: > > CPU 3... (APIC ID 0) FAILED > > > > as output. > > > > Has anyone been testing that? > > Just talked to Andreas, he booted his root Linux in xapic mode to > inherit that for the non-root cell. Just add "nox2apic" to your host > Linux parameters. Interesting, because my issue was at jailhouse enable time, I did not even enter the merit of which inmate payload was used. But I'll check better what's happening, if the .apic_mode = 1 approach is really all that is needed. Regards, > > Henning > > > Regards, > > > -- Gustavo Lima Chaves Intel - Open Source Technology Center -- You received this message because you are subscribed to the Google Groups "Jailhouse" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
