public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Avi Kivity <avi@qumranet.com>
Cc: Guillaume Thouvenin <guillaume.thouvenin@ext.bull.net>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Mohammed Gamal <m.gamal005@gmail.com>,
	"Kamble, Nitin A" <nitin.a.kamble@intel.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	laurent.vivier@bull.net, Alexander Graf <alex@csgraf.de>
Subject: Re: [Patch 0/7] RealMode: Support for big real mode
Date: Wed, 28 May 2008 10:46:16 -0500	[thread overview]
Message-ID: <483D7E48.9000402@us.ibm.com> (raw)
In-Reply-To: <483D00BE.4050802@qumranet.com>

Avi Kivity wrote:
> Guillaume Thouvenin wrote:
>> Hello,
>>   Those patches allow to boot OpenSuse-10.3. The problem with
>> Opensuse 10.3 is it uses a version of gfxboot that reads SS after
>> switching from real to protected mode, where SS contains an invalid
>> value, which VMX does not allow.
>>   
>
> Thanks, applied all. I dropped vcpu_sregs_table after all, in favor of 
> 1:1 mapping of VCPU_SREG_* to the opcode encoding (similar to the 
> general purpose registers).

There still seems to be an issue with this series.  When running:

sudo qemu-system-x86_64 -hda ./10gig.img -snapshot -cdrom 
isos/ubuntu-7.10-server-amd64.iso -boot dc

Occassionally, I'll get:

kvm_run: failed entry, reason 5
kvm_run returned -8

There's nothing in dmesg though.  Can you reproduce this?  If not, I'll 
dig in some more.

Regards,

Anthony Liguori

  reply	other threads:[~2008-05-28 15:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080527101851.201db183@frecb000711.frec.bull.fr>
2008-05-28  6:50 ` [Patch 0/7] RealMode: Support for big real mode Avi Kivity
2008-05-28 15:46   ` Anthony Liguori [this message]
2008-05-29  9:34     ` Avi Kivity
2008-05-29 11:05       ` Guillaume Thouvenin
2008-06-05 14:34         ` Avi Kivity
2008-06-05 22:11           ` Anthony Liguori
2008-05-29 13:48       ` Anthony Liguori

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=483D7E48.9000402@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=alex@csgraf.de \
    --cc=avi@qumranet.com \
    --cc=guillaume.thouvenin@ext.bull.net \
    --cc=kvm@vger.kernel.org \
    --cc=laurent.vivier@bull.net \
    --cc=m.gamal005@gmail.com \
    --cc=mtosatti@redhat.com \
    --cc=nitin.a.kamble@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox