From: <Kevin.Mayer@gdata.de>
To: andrew.cooper3@citrix.com, JBeulich@suse.com
Cc: xen-devel@lists.xen.org
Subject: Re: Xen 4.6.1 crash with altp2m enabledbydefault
Date: Mon, 22 Aug 2016 12:22:48 +0000 [thread overview]
Message-ID: <5C9C3B9BEF1B354596EAE3D6800D876B2DCD8187@e3.gdata.de> (raw)
In-Reply-To: <105e972f-d20a-6beb-c5d8-1b18916d2119@citrix.com>
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;
+
vpic_init(d);
rc = vioapic_init(d);
For the guest we use one state file ( Windows 10 ) from which the guests are restored with libvirt.
Simply restore and destroy several guests (5-7 in our current setup) in fast succession (every guest has about 1-2minutes runtime).
The amount of guest-VMs seems to correlate with the time until the crash occurs, but other, random factors seem to be more important.
More VMs => the crash happens faster.
Is the following debug-setup possible?
L0: Xen / VMWare
L1: Xen with altp2m enabled
L2: Several guest-VMs being constantly restored / destroyed
Then periodically take snapshots until the hypervisor panics and try to debug from the latest snapshot on.
> -----Ursprüngliche Nachricht-----
> Von: Andrew Cooper [mailto:andrew.cooper3@citrix.com]
> Gesendet: Montag, 22. August 2016 13:58
> An: Mayer, Kevin <Kevin.Mayer@gdata.de>; JBeulich@suse.com
> Cc: xen-devel@lists.xen.org
> Betreff: Re: AW: [Xen-devel] Xen 4.6.1 crash with altp2m enabledbydefault
>
> On 19/08/16 11:01, Kevin.Mayer@gdata.de wrote:
> > 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 up the vcpu and is then
> finished.
> >
> > In nestedhvm_vcpu_destroy (nvmx_vcpu_destroy) the vmcs can
> overwritten (but is not reached in our case as far as I can see):
> > if ( nvcpu->nv_n1vmcx )
> > v->arch.hvm_vmx.vmcs = nvcpu->nv_n1vmcx;
> >
> > In conclusion:
> > When destroying a domain the altp2m_vcpu_destroy(v); path seems to
> mess up the vmcs which ( only ) sometimes leads to a failed __vmwrite in
> vmx_fpu_leave.
> > That is as far as I can get with my understanding of the Xen code.
> >
> > Do you guys have any additional ideas what I could test / analyse?
>
> Do you have easy reproduction instructions you could share? Sadly, this is
> looking like an issue which isn't viable to debug over email.
>
> ~Andrew
____________
Virus checked by G Data MailSecurity
Version: AVA 25.7981 dated 22.08.2016
Virus news: www.antiviruslab.com
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-08-22 12:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 7:33 Xen 4.6.1 crash with altp2m enabled by default Kevin.Mayer
2016-07-29 9:57 ` Dario Faggioli
2016-07-29 10:05 ` Andrew Cooper
2016-08-02 11:45 ` Kevin.Mayer
2016-08-02 12:34 ` Jan Beulich
2016-08-03 13:24 ` Kevin.Mayer
2016-08-03 13:54 ` Jan Beulich
2016-08-04 15:08 ` Kevin.Mayer
2016-08-04 15:35 ` Jan Beulich
2016-08-05 12:51 ` Xen 4.6.1 crash with altp2m enabled bydefault Kevin.Mayer
2016-08-05 14:48 ` Jan Beulich
2016-08-08 9:48 ` Xen 4.6.1 crash with altp2m enabledbydefault Kevin.Mayer
2016-08-08 10:29 ` Jan Beulich
2016-08-19 10:01 ` Kevin.Mayer
2016-08-22 11:58 ` Andrew Cooper
2016-08-22 12:22 ` Kevin.Mayer [this message]
2016-09-07 8:35 ` Kevin.Mayer
2016-09-21 14:18 ` Kevin.Mayer
2016-09-22 10:13 ` Jan Beulich
[not found] ` <5C9C3B9BEF1B354596EAE3D6800D876B2DCF7138@e3.gdata.de>
[not found] ` <57E405970200007800111B26@prv-mh.provo.novell.com>
[not found] ` <5C9C3B9BEF1B354596EAE3D6800D876B2DCF7254@e3.gdata.de>
2016-09-26 9:20 ` Xen 4.6.1 crash with altp2menabledbydefault Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5C9C3B9BEF1B354596EAE3D6800D876B2DCD8187@e3.gdata.de \
--to=kevin.mayer@gdata.de \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).