Hi,
After updating from Xen 4.13 to Xen 4.14 I have troubles starting any
HVM: just after hvmloader saying "Invoking SeaBIOS" I get "(XEN) MMIO
emulation failed (1): d29v0 32bit @ 0008:fffeedf d -> "
I come to a situation where seemingly the same domU started via xl
works, while when started via libvirt it crashes. This seems to be
related to xl setting b_info.{acpi,apic}, while libvirt setting
b_info.u.hvm.{acpi,apic}. Modifying libvirt to use the former fixes the
issue.
So, handling the old option got broken sometime between 4.13 and 4.14.
Or perhaps it is some other related side effect.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
After updating from Xen 4.13 to Xen 4.14 I have troubles starting any
HVM: just after hvmloader saying "Invoking SeaBIOS" I get "(XEN) MMIO
emulation failed (1): d29v0 32bit @ 0008:fffeedf d -> "
I come to a situation where seemingly the same domU started via xl
works, while when started via libvirt it crashes. This seems to be
related to xl setting b_info.{acpi,apic}, while libvirt setting
b_info.u.hvm.{acpi,apic}. Modifying libvirt to use the former fixes the
issue.
So, handling the old option got broken sometime between 4.13 and 4.14.
Or perhaps it is some other related side effect.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?