|Subject:||Re: AW: Re: [Qemu-devel] VMport patch|
|Date:||Sun, 20 Jan 2008 20:41:09 -0600|
|User-agent:||Thunderbird 184.108.40.206 (X11/20071022)|
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.
Regards, Anthony Liguori
Cheers, MarkRegards, Anthony LiguoriRegards, Alex ----- Ursprüngliche Nachricht ----- Von: Anthony Liguori <address@hidden> Gesendet: Sonntag, 20. Januar 2008 22:40 An: address@hidden 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 LiguoriBest regards, Filip Navara
|[Prev in Thread]||Current Thread||[Next in Thread]|