All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: minor copy&paste error in vmx.c ?
Date: Mon, 07 Aug 2006 19:05:11 +0200	[thread overview]
Message-ID: <44D772C7.2000404@kaltenbrunner.cc> (raw)
In-Reply-To: <C0FCA7F6.90E%Keir.Fraser@cl.cam.ac.uk>

Keir Fraser wrote:
> 
> 
> On 6/8/06 1:33 pm, "Stefan Kaltenbrunner" <stefan@kaltenbrunner.cc> wrote:
> 
>> with that change in place i get the following when trying to boot a
>> OpenBSD/AMD64 kernel:
>>
>> (XEN) (GUEST: 1) Booting from CD-Rom...
>> (XEN) invalid cr: 8
> 
> Perhaps cr8 isn't emulated properly. Probably not very hard to fix if that's
> the case.

netbsd/amd64 fails in a similiar way:

(XEN) invalid cr: 8
(XEN) __hvm_bug at vmx.c:1822
(XEN) ----[ Xen-3.0-unstable    Not tainted ]----
(XEN) CPU:    1
(XEN) RIP:    0008:[<ffffffff802c6b8d>]
(XEN) RFLAGS: 0000000000000246   CONTEXT: hvm
(XEN) rax: 0000000000000000   rbx: 0000000000000000   rcx: ffffffff80a5a420
(XEN) rdx: 0000000000000286   rsi: 0000000000000001   rdi: 0000000000000000
(XEN) rbp: 0000000000000000   rsp: ffffffff80aa4ef0   r8:  ffffffff803a2400
(XEN) r9:  0000000000000720   r10: ffffffff80aa4ed0   r11: 0000000000000008
(XEN) r12: 0000000000000000   r13: 0000000000000000   r14: 0000000000000000
(XEN) r15: 0000000000000000   cr0: 000000008005003b   cr3: 00000000b21f6000
(XEN) ds: 0010   es: 0010   fs: 0000   gs: 0000   ss: 0010   cs: 0008
(XEN) domain_crash_sync called from vmx.c:1822
(XEN) Domain 24 (vcpu#0) crashed on cpu#1:
(XEN) ----[ Xen-3.0-unstable    Not tainted ]----
(XEN) CPU:    1
(XEN) RIP:    0008:[<ffffffff802c6b8d>]
(XEN) RFLAGS: 0000000000000246   CONTEXT: hvm
(XEN) rax: 0000000000000000   rbx: 0000000000000000   rcx: ffffffff80a5a420
(XEN) rdx: 0000000000000286   rsi: 0000000000000001   rdi: 0000000000000000
(XEN) rbp: 0000000000000000   rsp: ffffffff80aa4ef0   r8:  ffffffff803a2400
(XEN) r9:  0000000000000720   r10: ffffffff80aa4ed0   r11: 0000000000000008
(XEN) r12: 0000000000000000   r13: 0000000000000000   r14: 0000000000000000
(XEN) r15: 0000000000000000   cr0: 000000008005003b   cr3: 00000000b21f6000
(XEN) ds: 0010   es: 0010   fs: 0000   gs: 0000   ss: 0010   cs: 0008

netbsd/amd64 is actually able to get much further then OpenBSD/AMD64 -
but both seem to suffer from the same bug/issue.
OpenBSD/i386 and NetBSD/386 seem to work fine as a VT guest btw.

Stefan

      reply	other threads:[~2006-08-07 17:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-06 12:33 minor copy&paste error in vmx.c ? Stefan Kaltenbrunner
2006-08-07  7:19 ` Keir Fraser
2006-08-07 17:05   ` Stefan Kaltenbrunner [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=44D772C7.2000404@kaltenbrunner.cc \
    --to=stefan@kaltenbrunner.cc \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.