qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Don Slutz <dslutz@verizon.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Don Slutz <dslutz@verizon.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [BUGFIX][PATCH for 2.2 1/1] hw/i386/pc_piix.c: Also pass vmport=off for xenfv machine
Date: Thu, 20 Nov 2014 10:09:31 -0500	[thread overview]
Message-ID: <546E042B.4020302@terremark.com> (raw)
In-Reply-To: <546D83F3.3000100@redhat.com>

On 11/20/14 01:02, Paolo Bonzini wrote:
>
> On 19/11/2014 20:08, Don Slutz wrote:
>> -M pc -machine accel=xen
>>      pcms->vmport is false
> I think this should be true.  Any reason why not?
>
> Paolo

Yes, QEMU will crash if xen is enabled and the guest tries to access the 
VMware port.

(more on different thread).

    -Don Slutz

>> -M pc -machine vmport=on,accel=xen
>>      pcms->vmport is true
>> -M pc -machine vmport=off,accel=xen
>>      pcms->vmport is false

  reply	other threads:[~2014-11-20 15:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19 17:30 [Qemu-devel] [BUGFIX][PATCH for 2.2 1/1] hw/i386/pc_piix.c: Also pass vmport=off for xenfv machine Don Slutz
2014-11-19 17:35 ` Paolo Bonzini
2014-11-19 18:07   ` Don Slutz
2014-11-19 18:08     ` Paolo Bonzini
2014-11-19 19:08       ` Don Slutz
2014-11-19 19:15         ` Don Slutz
2014-11-19 19:30         ` Eduardo Habkost
2014-11-19 20:01           ` Don Slutz
2014-11-20  0:24             ` Eduardo Habkost
2014-11-20  0:49               ` Don Slutz
2014-11-20  6:02         ` Paolo Bonzini
2014-11-20 15:09           ` Don Slutz [this message]
2014-11-20 15:13         ` Eduardo Habkost
2014-11-20 15:24           ` Don Slutz
2014-11-20 15:27             ` Eduardo Habkost

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=546E042B.4020302@terremark.com \
    --to=dslutz@verizon.com \
    --cc=ehabkost@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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).