From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: AW: Re: [Qemu-devel] VMport patch
Date: Tue, 22 Jan 2008 12:55:13 -0600 [thread overview]
Message-ID: <47963C11.70109@codemonkey.ws> (raw)
In-Reply-To: <59344E6D-9028-4D4B-8961-41B62B4C0782@csgraf.de>
Alexander Graf wrote:
>
> On Jan 21, 2008, at 3:41 AM, Anthony Liguori wrote:
>
>> Mark Williamson 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.
>>>>
>>>
>>> Maybe have a commandline flag, and have it switched off by default?
>>> Or, even better, would be to detect valid vmware tools behaviour and
>>> switch it on iff that happened; the default being to behave normally
>>> for OSes that aren't running the VMware tools..
>>>
>>
>> There is no way to know for sure that it's vm-tools running. You
>> would have to make use of the cpu option to support it I reckon.
>>
>
> I completely agree with the point of breaking x86 semantics is bad.
> Yes, it is. What is the point in emulating the VMWare interface
> though, if the only program actually requiring that interface does not
> work, namely vmware tools, especially the windows version. So as far
> as I know VMWare uses VMX to run 64-bit code on Intel as well, so
> there has to be a way to forcefully break the checks.
vmmouse uses the vmport interface but runs in ring 0 under Linux so it's
not an issue. FWIW, the folks on open-vm-tools-devel have expressed an
interest in moving to a different interface then their "backdoor" interface.
Regards,
Anthony Liguori
> Regards,
>
> Alex
>
>> Regards,
>>
>> Anthony Liguori
>>
>>> Cheers,
>>> Mark
>>>
>>>
>>>> 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-22 18:55 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
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 [this message]
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=47963C11.70109@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 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.