public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@qumranet.com>
Cc: Mohammed Gamal <m.gamal005@gmail.com>,
	kvm@vger.kernel.org, Rik van Riel <riel@surriel.com>,
	Guillaume Thouvenin <guillaume.thouvenin@ext.bull.net>
Subject: Re: Questions on the VMentry failure patch
Date: Mon, 07 Jul 2008 10:26:45 -0500	[thread overview]
Message-ID: <487235B5.9080407@codemonkey.ws> (raw)
In-Reply-To: <48722D99.2030009@qumranet.com>

Avi Kivity wrote:
> Mohammed Gamal wrote:
>> On Mon, Jul 7, 2008 at 5:24 PM, Avi Kivity <avi@qumranet.com> wrote:
>>  
>>> Mohammed Gamal wrote:
>>>    
>>>> Hello,
>>>> Guillaume Thouvenin's VMentry failure detection patch was reverted
>>>> before because it broke guest rebooting. Although it turned out it
>>>> didn't, it was preferred not to re-include it because it was not
>>>> reliable enough. Although it is working fine with me, I want to know
>>>> why it wasn't re-included? Did it cause any regressions? Is it
>>>> preferrable to use an alternative mechanism to detect the VM entry
>>>> failure and start real-mode emulation? If yes, What do you think it
>>>> should be?
>>>>
>>>>
>>>>       
>>> Anthony Liguori reported problems with Ubuntu IIRC.  I'd like to 
>>> know that
>>> they are fixed, or what exactly the issue was.
>>>
>>>     
>> Well, Ubuntu and openSuSE live CDs used to crash occasionally after
>> booting, it didn't happen most of the time though. I've never
>> experienced this issue after kvm-70 - with the patches the patch
>> included of course. Did anyone have any issues with the patches
>> included?
>>   
>
> I think they're fine.  Can you check the vmentry patch now, with 
> Anthony's testcase?

If I revert 0eba1b, then use the following command line:

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

After about the 7th or so run, I get:

kvm_run: failed entry, reason 5
kvm_run returned -8

So the problem still exists.

Regards,

Anthony Liguori


  reply	other threads:[~2008-07-07 15:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-07 14:07 Questions on the VMentry failure patch Mohammed Gamal
2008-07-07 14:24 ` Avi Kivity
2008-07-07 14:44   ` Mohammed Gamal
2008-07-07 14:52     ` Avi Kivity
2008-07-07 15:26       ` Anthony Liguori [this message]
2008-07-07 15:29       ` Anthony Liguori
2008-07-08  0:52         ` Mohammed Gamal
2008-07-09 17:56           ` Mohammed Gamal
2008-07-10 13:48             ` Mohammed Gamal
2008-07-14 16:10               ` Mohammed Gamal
2008-07-14 16:12                 ` Avi Kivity
2008-07-14 16:15                   ` Anthony Liguori
2008-07-14 16:24                     ` Avi Kivity
2008-07-14 17:09                       ` Mohammed Gamal
2008-07-18 16:04                       ` Mohammed Gamal
2008-07-19  7:41                         ` Avi Kivity

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=487235B5.9080407@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=avi@qumranet.com \
    --cc=guillaume.thouvenin@ext.bull.net \
    --cc=kvm@vger.kernel.org \
    --cc=m.gamal005@gmail.com \
    --cc=riel@surriel.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