From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: AW: Re: [Qemu-devel] VMport patch
Date: Sun, 20 Jan 2008 17:09:42 -0600 [thread overview]
Message-ID: <4793D4B6.8030408@codemonkey.ws> (raw)
In-Reply-To: <20080120222742.B2F993A9B@csgraf.de>
Alexander Graf wrote:
> I think it would be great to maintain compatibility with the binary-only versions of the vm tools though.
>
But you're changing the semantics of the x86 instruction set. You
potentially break a real operating system. It also eliminates the
possibility of nesting with something like kqemu because you can't trap
all PIO operations.
Regards,
Anthony Liguori
> Regards,
>
> Alex
>
> ----- Ursprüngliche Nachricht -----
> Von: Anthony Liguori <anthony@codemonkey.ws>
> Gesendet: Sonntag, 20. Januar 2008 22:40
> An: qemu-devel@nongnu.org
> Betreff: Re: [Qemu-devel] VMport patch
>
> Filip Navara wrote:
>
>> Hello,
>>
>> the current version of QEMU emulates the VMware backdoor I/O port and
>> it works quite well. Unfortunately it doesn't emulate the VMware
>> behavior of ignoring the I/O permissions when accessing this special
>> port. The attached patch corrects it. It's important to ignore the
>> permissions, so that user mode VMware tools can communicate to the
>> backdoor. =
>>
>
> I really dislike that VMware relies on this. It's very hard to
> implement in kqemu or KVM. I think it would be better to modify
> open-vm-tools than to modify QEMU.
>
> Regards,
>
> Anthony Liguori
>
>
>> Best regards,
>> Filip Navara
>>
>
>
>
>
>
>
>
next prev parent reply other threads:[~2008-01-20 23:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-20 22:27 AW: Re: [Qemu-devel] VMport patch Alexander Graf
2008-01-20 23:09 ` Anthony Liguori [this message]
2008-01-20 23:17 ` Mark Williamson
2008-01-21 2:41 ` Anthony Liguori
2008-01-21 7:10 ` Alexander Graf
2008-01-22 18:55 ` Anthony Liguori
2008-01-21 10:13 ` Jamie Lokier
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=4793D4B6.8030408@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).