Hi guys
I have found the problem (after hours and hours of gruesome
debugging with the almighty print) and it seems that this could potentially
have quite a bit of impact if altp2m is enabled for a guest domain (even if
the
functionality is never actively used), since destroying any vcpu of this
Hi
I took the time to write a small script which restores and destroys domains
from provided state files.
Just apply the patch to a xen 4.6.1, provide some images + state files and
start the script.
python VmStarter.py -FILE /path/to/domU-0.state -FILE /path/to/domU-1.state
--loggingLevel
Hi
The reproduction should be pretty simple:
Apply the patch to enable altp2m unconditionally:
d->arch.hvm_domain.params[HVM_PARAM_HPET_ENABLED] = 1;
d->arch.hvm_domain.params[HVM_PARAM_TRIPLE_FAULT_REASON] = SHUTDOWN_reboot;
+d->arch.hvm_domain.params[HVM_PARAM_ALTP2M] = 1;
+
Hi
I took another look at Xen and a new crashdump.
The last successful __vmwrite should be in
static void vmx_vcpu_update_vmfunc_ve(struct vcpu *v)
[...]
__vmwrite(SECONDARY_VM_EXEC_CONTROL,
v->arch.hvm_vmx.secondary_exec_control);
[...]
After this the altp2m_vcpu_destroy wakes
vmx_vmenter_helper is not part of the call stack. The address is simply the
location of the ud2 to which the
__vmwrite(HOST_CR0, v->arch.hvm_vmx.host_cr0);
In
static void vmx_fpu_leave(struct vcpu *v)
jumps.
There are two vmwrites in vmx_vcpu_update_eptp (called by altp2m_vcpu_destroy):
According to the xen dmesg
(XEN) RIP:e008:[] vmx_vmenter_helper+0x27e/0x30a
(XEN) RFLAGS: 00010003 CONTEXT: hypervisor
(XEN) rax: 8005003b rbx: 8300e72fc000 rcx:
(XEN) rdx: 6c00 rsi: 830617fd7fc0 rdi: 8300e6fc
(XEN) rbp:
According to the crash-dump ( output of vcpu ) the v->arch.hvm_vmx.host_cr0 is
" 0 ".
This cannot be the correct result because of
if ( !(v->arch.hvm_vmx.host_cr0 & X86_CR0_TS) )
{
v->arch.hvm_vmx.host_cr0 |= X86_CR0_TS;
__vmwrite(HOST_CR0, v->arch.hvm_vmx.host_cr0);
}
It
Hi guys
I got around to take a closer look at the crash dump today.
tl;dr:
You were right, vmx_vmenter_helper is not called at all in the call stack.
The real reason behind the [] vmx_vmenter_helper+0x27e/0x30a
should be a failed
__vmwrite(HOST_CR0, v->arch.hvm_vmx.host_cr0); in static void
Thanks for your reply.
I installed the debug hypervisor and got a new crash dump now.
I must confess that I have little to no experience debugging crash dumps, but
this seems to be a different kind of error, or at least the way the error is
reached is different.
The pattern with “page number X
Hi guys
We are using Xen 4.6.1 to manage our virtual machines on x86-64-servers.
We start dozens of VMs and destroy them again after 60 seconds, which works
fine as it is, but the next step in our approach requires the use of the altp2m
functionality.
Since libvirt does not pass the
-Ursprüngliche Nachricht-
Von: Boris Ostrovsky [mailto:boris.ostrov...@oracle.com]
Gesendet: Donnerstag, 26. Februar 2015 17:35
An: Dietmar Hahn; xen-devel@lists.xen.org
Cc: Mayer, Kevin
Betreff: Re: [Xen-devel] Branch Trace Storage for guests and
VPMUinitialization
On
-Ursprüngliche Nachricht-
Von: Boris Ostrovsky [mailto:boris.ostrov...@oracle.com]
Gesendet: Dienstag, 24. Februar 2015 18:13
An: Mayer, Kevin; xen-devel@lists.xen.org
Betreff: Re: [Xen-devel] Branch Trace Storage for guests and VPMU
initialization
On 02/24/2015 10:27 AM,
Hi guys
I`m trying to set up the BTS so that I can log the branches taken in the guest
using Xen 4.4.1 with a WinXP SP3 guest on a Core i7 Sandy Bridge.
I added the vpmu=bts boot parameter to my grub2 configuration and extended the
libxl,libxc,domctl,... with an own command so that I can
Hi all
I`m trying to track code execution with page granularity by setting the access
rights in the EPT to not executable on Xen 4.4.1.
The idea is as follows:
According to the intel manual A reference using a guest-physical address
whose translation encounters an EPT paging-structure that is
14 matches
Mail list logo
