[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [PATCH] Xen 4.4-rc3 regression with PVH compared to Xen 4.4-rc2.

I am hereby requesting an Xen 4.4 exemption for this bug-fix.

The PVH feature is considered experimental, but it would be good to have
it working out of the box without crashing the hypervisor.

Sadly that is not the case as 09bb434748af9bfe3f7fca4b6eef721a7d5042a4
"Nested VMX: prohibit virtual vmentry/vmexit during IO emulation"
casues an NULL pointer dereference when starting a guest with 'pvh=1'
in the guest config.

There are two ways of fixing this:
a). Add an '!xen_pvh_domain()' or '!xen_pvh_vcpu(current)' in the path, or
b). Check for ioreq() being NULL. This is actually done in other places
    in the hypervisor - so I choose to piggyback on that.

Thank you!

 xen/arch/x86/hvm/vmx/vvmx.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

Konrad Rzeszutek Wilk (1):
      pvh: Fix regression caused by assumption that HVM paths MUST use 
io-backend device.

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.