From: Don Slutz <dslutz@verizon.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Jun Nakajima <jun.nakajima@intel.com>, Tim Deegan <tim@xen.org>,
Kevin Tian <kevin.tian@intel.com>, Keir Fraser <keir@xen.org>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
George Dunlap <george.dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Don Slutz <don.slutz@gmail.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Eddie Dong <eddie.dong@intel.com>,
Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
BorisOstrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH v11 6/9] xen: Add ring 3 vmware_port support
Date: Fri, 12 Jun 2015 08:52:16 -0400 [thread overview]
Message-ID: <557AD600.6060408@one.verizon.com> (raw)
In-Reply-To: <557A97830200007800083F91@mail.emea.novell.com>
On 06/12/15 02:25, Jan Beulich wrote:
>>>> On 12.06.15 at 00:10, <dslutz@verizon.com> wrote:
>> On 06/05/15 06:54, Ian Campbell wrote:
>>> It would be really useful to see a comprehensive list of exactly what
>>> guest ring3 access to the vmware port actually enables i.e. a list of
>>> specific features which require it.
>>
>> Ok, I have done some testing. Here is what I know:
>>
>> Without ring3 support:
>>
>> 1) VMware tools will not install on linux and windows.
>> 2) open-vm-tools (https://github.com/vmware/open-vm-tools) will not
>> install (how ever it is not hard to change it to do so, you need to add
>> a call to iopl(3) need to be added in a few places) on linux
>>
>> However if VMware tools did get installed on the window disk bits
>> somehow, the VMware mouse support works. Linux gets this because Xorg
>> detects and uses the VMware mouse under IOPL(3).
>
> Now that tells us that the tools may not work, but not what
> implications that has on the usability of the VM once migrated
> to Xen. Them not installing is a non-issue afaict, since after
> having moved the VM to Xen there shouldn't be a need to
> install them anymore - either they've been there, or I don't
> see why they would be needed _after_ the move. And you
> say that the mouse works in both cases if the tools happen
> to be there.
>
The VMware tools service will start but does not work. It adds to the
event log:
[warning][vmusr:vmtoolsd] The vmuser service needs to run inside a
virtual machine.
And the available features of VMware tools is disabled:
1) The ability to perform virtual machine power operations gracefully
is missing. (code to access QEMU's from Xen to do this is missing).
I.E. get windows to shutdown when requested!
2) Execution of VMware provided or user configured scripts in guests
during various power operations.
3) Clock synchronization between guests and hosts or client desktops.
4) Access to VMware guest info variables (code to access QEMU's from
Xen to do this is missing). This can be used to customize guest
operating systems immediately after powering on virtual machines. It can
also be used to monitor the health of a guest.
The reason to install them after is to get the VMware mouse driver on
Windows. This mouse driver works much better on Window when there is
higher network latency.
-Don Slutz
> Jan
>
next prev parent reply other threads:[~2015-06-12 12:52 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 15:50 [PATCH v11 0/9] Xen VMware tools support Don Slutz
2015-05-22 15:50 ` [PATCH v11 1/9] tools: Add vga=vmware Don Slutz
2015-05-22 15:50 ` [PATCH v11 2/9] xen: Add support for VMware cpuid leaves Don Slutz
2015-05-22 15:50 ` [PATCH v11 3/9] tools: Add vmware_hwver support Don Slutz
2015-06-03 14:53 ` George Dunlap
2015-06-04 15:15 ` Ian Campbell
2015-06-04 15:46 ` Don Slutz
2015-06-04 15:17 ` Ian Campbell
2015-06-04 15:59 ` Don Slutz
2015-05-22 15:50 ` [PATCH v11 4/9] vmware: Add VMware provided include file Don Slutz
2015-05-22 15:50 ` [PATCH v11 5/9] xen: Add vmware_port support Don Slutz
2015-06-05 9:52 ` Jan Beulich
2015-06-05 13:18 ` Don Slutz
2015-05-22 15:50 ` [PATCH v11 6/9] xen: Add ring 3 " Don Slutz
2015-06-03 15:26 ` George Dunlap
2015-06-03 15:58 ` Andrew Cooper
2015-06-03 16:23 ` George Dunlap
2015-06-03 16:40 ` Andrew Cooper
2015-06-03 17:00 ` George Dunlap
2015-06-03 16:41 ` Don Slutz
2015-06-03 16:58 ` George Dunlap
2015-06-04 12:37 ` Don Slutz
2015-06-04 14:14 ` George Dunlap
2015-06-04 16:17 ` Don Slutz
2015-06-03 16:36 ` Don Slutz
2015-06-03 16:50 ` George Dunlap
2015-06-05 9:31 ` Jan Beulich
2015-06-05 10:54 ` Ian Campbell
2015-06-11 22:10 ` Don Slutz
2015-06-12 6:25 ` Jan Beulich
2015-06-12 12:52 ` Don Slutz [this message]
2015-06-23 16:14 ` Jan Beulich
2015-06-26 14:54 ` Don Slutz
2015-05-22 15:50 ` [PATCH v11 7/9] tools: Add " Don Slutz
2015-06-03 17:06 ` George Dunlap
2015-06-04 15:49 ` Ian Campbell
2015-06-04 16:09 ` Don Slutz
2015-06-04 15:20 ` Ian Campbell
2015-05-22 15:50 ` [PATCH v11 8/9] Add IOREQ_TYPE_VMWARE_PORT Don Slutz
2015-06-03 17:09 ` George Dunlap
2015-06-04 11:28 ` Don Slutz
2015-06-05 9:35 ` Jan Beulich
2015-06-05 10:03 ` Paul Durrant
2015-06-08 10:05 ` George Dunlap
2015-06-11 21:51 ` Don Slutz
2015-05-22 15:50 ` [PATCH v11 9/9] Add xentrace to vmware_port Don Slutz
2015-06-04 11:20 ` George Dunlap
2015-06-04 12:31 ` Don Slutz
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=557AD600.6060408@one.verizon.com \
--to=dslutz@verizon.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=don.slutz@gmail.com \
--cc=eddie.dong@intel.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jun.nakajima@intel.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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.