public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
Cc: KVM list <kvm@vger.kernel.org>, nik@nik-comp.linuxbox.cz
Subject: Re: vmwrite error: reg 401e value a0332340 (err 12) (SOLVED)
Date: Sun, 21 Apr 2013 11:02:59 +0300	[thread overview]
Message-ID: <20130421080259.GX8997@redhat.com> (raw)
In-Reply-To: <20130421080046.GA5588@nik-comp.linuxbox.cz>

On Sun, Apr 21, 2013 at 10:00:46AM +0200, Nikola Ciprich wrote:
> Hi,
> 
> I'll reply to myself - the kernel is 3.0.60, but kvm module was 3.6
> needing 29282fde80d44e587f8c152b10049a56e61659f0.
> 
> problem solved.
> 
Thanks for the update.

> nik
> 
> 
> On Fri, Apr 19, 2013 at 01:33:45PM +0200, Nikola Ciprich wrote:
> > Hi,
> > 
> > on one of my boxed I'm getting (maybe) KVM related crashes..
> > 
> > I noticed this in dmesg:
> > 
> > [   50.199372] vmwrite error: reg 401e value a0332340 (err 12)
> > [   50.199575] Pid: 5179, comm: qemu-system-x86 Not tainted 3.0.60lb6.01 #1
> > [   50.199802] Call Trace:
> > [   50.199950]  [<ffffffffa031925c>] vmwrite_error+0x2c/0x30 [kvm_intel]
> > [   50.200182]  [<ffffffffa0319280>] vmcs_writel+0x20/0x30 [kvm_intel]
> > [   50.200407]  [<ffffffffa031cb79>] vmx_cpuid_update+0x79/0x160 [kvm_intel]
> > [   50.200656]  [<ffffffffa02c9c9b>] kvm_vcpu_ioctl_set_cpuid2+0xab/0xc0 [kvm]
> > [   50.200899]  [<ffffffffa02a6b9a>] kvm_arch_vcpu_ioctl+0x94a/0x1030 [kvm]
> > [   50.201135]  [<ffffffffa031b97e>] ? vmx_vcpu_load+0x3e/0x1c0 [kvm_intel]
> > [   50.201375]  [<ffffffffa02a72d7>] ? kvm_arch_vcpu_load+0x57/0x1b0 [kvm]
> > [   50.201606]  [<ffffffffa0298d65>] kvm_vcpu_ioctl+0x135/0x6b0 [kvm]
> > [   50.201824]  [<ffffffff8102f410>] ? do_page_fault+0x1d0/0x480
> > [   50.202036]  [<ffffffff81151cba>] do_vfs_ioctl+0x9a/0x5e0
> > [   50.202234]  [<ffffffff811522a1>] sys_ioctl+0xa1/0xb0
> > [   50.202426]  [<ffffffff813c0d82>] system_call_fastpath+0x16/0x1b
> > 
> > the host is x86_64 RHEL6 based, kernel 3.0.60, qemu-kvm-1.4.0 running only
> > one guest (windows XP)
> > 
> > any idea what could this be?
> > 
> > thanks a lot in advance
> > 
> > nik
> > 
> > -- 
> > -------------------------------------
> > Ing. Nikola CIPRICH
> > LinuxBox.cz, s.r.o.
> > 28.rijna 168, 709 00 Ostrava
> > 
> > tel.:   +420 591 166 214
> > fax:    +420 596 621 273
> > mobil:  +420 777 093 799
> > www.linuxbox.cz
> > 
> > mobil servis: +420 737 238 656
> > email servis: servis@linuxbox.cz
> > -------------------------------------
> 
> 
> 
> -- 
> -------------------------------------
> Ing. Nikola CIPRICH
> LinuxBox.cz, s.r.o.
> 28. rijna 168, 709 00 Ostrava
> 
> tel.:   +420 591 166 214
> fax:    +420 596 621 273
> mobil:  +420 777 093 799
> 
> www.linuxbox.cz
> 
> mobil servis: +420 737 238 656
> email servis: servis@linuxbox.cz
> -------------------------------------



--
			Gleb.

      reply	other threads:[~2013-04-21  8:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19 11:33 vmwrite error: reg 401e value a0332340 (err 12) Nikola Ciprich
2013-04-21  8:00 ` vmwrite error: reg 401e value a0332340 (err 12) (SOLVED) Nikola Ciprich
2013-04-21  8:02   ` Gleb Natapov [this message]

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=20130421080259.GX8997@redhat.com \
    --to=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=nik@nik-comp.linuxbox.cz \
    --cc=nikola.ciprich@linuxbox.cz \
    /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