Archive for the ‘Mouse’ Category
RHEL 6.4 on Hyper-V
RHEL 6.4 / CentOS 6.4 include support for Hyper-V drivers
==
8.2. Hyper-V
. . .
Inclusion of, and Guest Installation Support for, Microsoft Hyper-V Drivers
-
a network driver (
hv_netvsc) -
a storage driver (
hv_storvsc) -
an HID-compliant mouse driver (
hid_hyperv) -
a VMbus driver (
hv_vmbus) -
a util driver (
hv_util) -
an IDE disk driver (
ata_piix) -
a balloon driver (
hv_balloon) -
a clock source (i386, AMD64/Intel 64:
hyperv_clocksource)
hypervkvpd) that passes basic information, such as the guest IP, the FQDN, OS name, and OS release number, to the host through VMbus. An IP injection functionality is also provided which allows you to change the IP address of a guest from the host via the hypervkvpd daemon. . . .
Hyper-V balloon Driver
On Red Hat Enterprise Linux 6.4 guests, the balloon driver, a basic driver for the dynamic memory management functionality supported on Hyper-V hosts, was added. The balloon driver is used to dynamically remove memory from a virtual machine. Windows guests support Dynamic Memory with a combination of ballooning and hot adding. In the current implementation of the balloon driver for Linux, only the ballooning functionality is implemented, not the hot-add functionality.
==
==
==
==
Andy Schmidt
Wednesday, January 23, 2013 7:45 PM
I’m new to the Unix World. Was able to install two virtual machiens, one hosting an Apache Web Server and one a MySQL server. Problem is that the Integration Services are flawed:
a) They disable the ability to mount CDROMs to that virtual machine:
http://support.microsoft.com/kb/2600152
I’m not sure if the INSMOD work-around will disable the faster disk driver? The command doesn’t seem to be specific to the CDROM devices…
b) Worse, I’m unable to install any security fixes to the kernel, because of:
http://support.microsoft.com/kb/2387594
Unfortunately, the DKMS work-around is based on IC 2.1 – when the ISO still contained the source. The 3.4 (and prior) are RPMs.
There is also a work-around floating which patches the uname string to the hardcoded new kernel name, before calling "MAKE". It claims to work with IC 3.2, but when I checked THAT ISO, it too had NO source – so I can’t imagine that working.
http://www.acumen-corp.com/Blog/tabid/298/entryid/19/HOWTO-Upgrading-the-CentOS-kernel-for-a-Hyper-V-virtual-machine-with-Linux-Integration-Components.aspx
I wonder if there is a way to "uninstall" the integration services, "re-enable" the necessary native drivers, then run the kernel updates, and after rebooting, re-install the 3.4 integration services?
In general, I’m a bit surprised that the lack of CD/DVD support and the inability to run kernel updates hasn’t bubbled to the top of he priority list after so many months/years – as I would have expected every single user to encounter that?
==
==
{{{
a) They disable the ability to mount CDROMs to that virtual machine:
http://support.microsoft.com/kb/2600152=={{
CAUSE:
This issue occurs because the Hyper-V Linux Integration Services unloads the ata_piix driver
[ VVM: "unloads" look like "prevent load" :
=={
install ata_piix { /sbin/modprobe hv_storvsc 2>&1 || /sbin/modprobe --ignore-install ata_piix; }
==}
]
in order to provide an optimized IDE driver (hv_blkvsc [ VVM: hv_blkvsc is RIP ; hv_storvsc for _both_ IDE and SCSI disks after kernel v3.2 or for LIC/LIS v3.4 ] ) for the root [ VVM to All sysadmins: on IDE _need_ be place only boot loader ( GRUB or syslinux) and /boot , _other_ ( include / ) _best_ place on SCSI. But because current RHEL not contain hv_storvsc in install CD-ROM, we are need use "Mondo Rescue" after Mondo backup ] file system.
WORKAROUND:
To mount an ISO file in the virtual machine, the following command must be run before executing the mount command:
# insmod /lib/modules/$(uname -r)/kernel/drivers/ata/ata_piix.koWORKAROUND N2:
Alternatively, copy the ISO file into the virtual machine and mount it using the -o loop option.
[ VVM: Bingo! 8-/ But . . .
How about kernel for LiveCD? In any case need patched ata_piix ]
==}}
I’m not sure if the INSMOD work-around will disable the faster disk driver? The command doesn’t seem to be specific to the CDROM devices…
~
Yes: not disable "faster disk driver", because it is hv_storvsc
Yes #2 : this command not "specific to the CDROM devices" , and after
load both unpatched ata_piix and hv_storvsc
You can see results: by run blkid and look in output of this command ( and in _fact_) duplicates(!) of IDE disks
~
~
Again: _true_ solutions is "backport patches related ata_piix on Hyper-V"
==
==
Solutions ( in order from low problematic to hi):
— use RHEL 6.4
==
State of Linux on Hyper-V — total «moved out ot staging» in kernel v3.2/v3.3
Update 2012-02-23 12-00:
a)
See
==
K. Y. Srinivasan:
With regards to the ata_piix changes, we will try to push that upstream shortly.
==
z)
Hyper-V drivers for Linux will finally leave the staging area with 3.4
http://git.kernel.org/?p=linux/kernel/git/gregkh/staging.git;a=commit;h=89ae7d709357df3a60e81c57613859d91d093ace
==
. . .
Staging: hv: storvsc: Move the storage driver out of the staging area
The storage driver (storvsc_drv.c) handles all block storage devices
assigned to Linux guests hosted on Hyper-V. This driver has been in the
staging tree for a while and this patch moves it out of the staging area.
James was willing to apply this patch during the 3.3-rc phase and a decision
was taken to defer this to 3.4 since Greg had queued up a bunch of storvsc
patches for 3.4. Now that Greg has applied all of the pending storvsc patches,
I am sending this patch to move this driver out of staging. Based on James’
recommendation, this patch gets rid of the unneeded files in the staging/hv
directory.
. . .
==
Update 2012-02-21 11-32:
See
==
«Ubuntu Way»
. . .
2. Modify the ata driver to recognize that when hosted on Hyper-V
==
Update 2012-02-17 16-05:
see later:
==
Kernel v3.2: With Arch fork Сhakra: mouse work fine ( simply — ideal) , but
— \dev\sda = = \dev\sdb
\dev\sdb is IDE Drive Master Primary ( and not work as need)
and
\dev\sda is IDE Drive Master Primary
and SCSI not \dev\sdb , but \dev\sdc — IMHO, it is may be not very well
==
http://www.simweb.ch/blog/2011/12/experimental-hyper-v-branch/
==
. . .
. . . will be coming from stagin-next, hid and the network area where some of the drivers Hyper-V have left staging as of December 2011. So with the release of 3.2 sooner or later, you can fetch a kernel that has:
• SCSI hot plug / remove
• netvsc network promiscuous mode
• netvsc and hid out of staging
. . .. . . – I’m quite positive with 3.4 most of Hyper-V code will have left staging and reached a maturity for other distributions to enable drivers in default kernel builds.
If you’re a admin that has to manage Linux on Hyper-V – other than SLES/RHEL or CentOS – now you should be asking your distributions to enable these modules (at least hyper-v bus with 3.2)
. . .
==
http://www.simweb.ch/blog/2011/12/experimental-hyper-v-branch/
==
Experimental Hyper-V branchHere is a experimental branch of the mainline kernel with some backported patches . . .
https://gitorious.org/~matsimon/linux-gymkl/matsimons-hv-kernel
==
{
http://www.simweb.ch/blog/2011/10/state-of-linux-on-hyper-v/
==
State of Linux on Hyper-V
Update 02.2012 . . .
==
==
. . . move the handling of IDE drives to hv_storvsc and drops hv_blkvsc completely . . .Update: It seems one can ommit this having only /boot and GRUB on the bootable IDE disk, thanks Victor – he has more details how to omit this.
Actually it’s not a technical problem yet. MS handles this via modprobe rules in their Linux ICs for sanity.
==
==
Partly leaving the staging area
Greg Kroah-Hartmann has put a patch in staging-next that moves the VMBus part out of drivers/staging/hv – read his commit message. It now means the VMBus drivers – the paravirtualized bus of Hyper-V where paravirt devices connect to the hypervisor backend – are considered enough cleaned up to be considered stable.Update: With Linux 3.3 only storvsc will be / is left in staging area. This means that the kernel hackers think that the overall quality of the kernel modules are believed to be good enough for daily use. For sure there are possible bugs and will be fixed hopefully as well.
==
==
Mouse support
. . .Update: I have since then tested the dirvers, 3.2 seems to work well but 3.3 contains some memory leak bugfixes others have had their issues with them in 3.0/3.1. If you dont have X.org on a Server VM, you can quietly ignore this module anyway. – I’ll let Puppet do the work or SSH to the box first
Starting 3.3 the driver has been renamed once as hid_hyperv and was moved out ot staging.
==
}
----- Original Message -----
From: "Mathieu Simon"
To: "Victor Miasnikov"
Sent: Thursday, February 16, 2012 4:32 PM
. . .
While 3.2 is quite ok, 3.3 still has a bunch of fixes that look scary - and are missing in 3.2 still (kernel oopses, memory leaks etc.)
Have fun with Arch on Hyper-V - there is a patch underway that will also remove the 4 vCPU limit that is still yet imposed by 2008 R2 and will go awa with Windows 8 Servers.
. . .
But I ( Mathieu Simon) don't think this patch is already in 3.3.
You can read here:
http://groups.google.com/group/linux.kernel/browse_thread/thread/26e70c50d24fd38c/9aa8eea98838fbf3?show_docid=9aa8eea98838fbf3
. . .
--
----- Original Message -----
From: "Victor Miasnikov"
To: "Mathieu Simon"
Sent: Thursday, February 16, 2012 5:51 PM
. . . Thanks You for very interesant and usefull blog and other work
>> If you dont have X.org on a Server VM, you can quietly ignore this module anyway. – I’ll let Puppet do the work or SSH to the box first 
If need mouse in old-kernel Linux -- simple use directly connect via Hyper-V MMC from physically Windows-workstantion
. . .
--
Update 2012-02-17 16-05:
Kernel v3.2: With Arch fork Сhakra: mouse work fine ( simply — ideal) , but
\dev\sdb is IDE Drive Master Primary ( and not work as need)
and
\dev\sda is IDE Drive Master Primary
i.e.
— \dev\sda = = \dev\sdb
and SCSI not \dev\sdb , but \dev\sdc — IMHO, it is may be not very well
see Linux on Hyper-V Image:
Full size picture:
http://vvm.blog.tut.by/files/2012/02/Linux-on-Hyper-V-Image-2012-02-17-14-04.png
–
Update 2012-02-21 11-32:
From: Miasnikov Victor
Sent: Tuesday, February 21, 2012 11:23 AM
To: 'K. Y. Srinivasan'
Subject: Ubuntu: ata_piix.prefer_ms_hyperv=0 Fw: Problem: \dev\sda == \dev\sdb is is IDE Drive Master Primary and SCSI not \dev\sdb , but \dev\sdc Fw: move the handling of IDE drives to hv_storvsc and drops hv_blkvsc completely Fw: State of Linux on Hyper-V
. . .
Can solve problem someone a-la this
Var A Or "Ubuntu Way"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/929545
==
. . .
The strategies Microsoft currently use on other distributions are based on setting up modprobe rules but these will not work on Ubuntu
as the native (ata*) driver is built directly into the kernel.
. . .
2. Modify the ata driver to recognize that when hosted on Hyper-V, it
should not control the disks.
. . .
Andy Whitcroft (apw) wrote on 2012-02-10:
I . . . add hyper-v detection to the ata_piix driver. This basically defers handling to hyper-v by default if the hypervisor is detected. I have also added an override to allow this to be suppressed from the command line. Could someone with a hyper-v based cloud test the kernels below and report whether they work here. Could you please include a dmesg of a successful boot so I can confirm the detection has recorded itself correctly. It would also be helpful to get a boot with ata_piix.prefer_ms_hyperv=0,
==
http://www.ubuntuupdates.org/package/core/precise/main/base/linux-image-3.2.0-17-generic
=>
===
...
* deviations -- note the source of the Hyper-V updates
* SAUCE: ata_piix: defer to the Hyper-V drivers by default
- LP: #929545
...
===
==
http://people.canonical.com/~apw/lp929545-precise/0001-ata_piix-defer-to-the-Hyper-V-drivers-by-default.patch
===
From 9c2e8890fee7c07540e477bac63984a53a903455 Mon Sep 17 00:00:00 2001
From: Andy Whitcroft
Date: Fri, 10 Feb 2012 12:17:14 +0000
Subject: [PATCH 01/70] ata_piix: defer to the Hyper-V drivers by default
When we are hosted on a Microsoft Hyper-V hypervisor the guest disks
are exposed both via the Hyper-V paravirtualised drivers and via an
emulated SATA disk drive. In this case we want to use the
paravirtualised drivers if we can as they are much more efficient.
Add check for the Hyper-V hypervisor during initialisation and avoid
initialising. Also adds a module parameter to override this behaviour.
BugLink: http://bugs.launchpad.net/bugs/929545
Signed-off-by: Andy Whitcroft
---
debian/rules.d/1-maintainer.mk | 1 +
drivers/ata/ata_piix.c | 17 +++++++++++++++++
2 files changed, 18 insertions(+), 0 deletions(-)
diff --git a/debian/rules.d/1-maintainer.mk b/debian/rules.d/1-maintainer.mk
index 975cd79..6477b68 100644
--- a/debian/rules.d/1-maintainer.mk
+++ b/debian/rules.d/1-maintainer.mk
@@ -92,6 +92,7 @@ prev_release="$(release)-$(prev_revision)"
printchanges:
@baseCommit=$$(git log --pretty=format:'%H %s' | \
awk '/UBUNTU: '".*Ubuntu-$(prev_release)"'$$/ { print $$1; exit }'); \
+ echo "$$baseCommit" ; \
git log "$$baseCommit"..HEAD | \
perl -w -f $(DROOT)/scripts/misc/git-ubuntu-log $(ubuntu_log_opts)
diff --git a/drivers/ata/ata_piix.c b/drivers/ata/ata_piix.c
index 69ac373..f8280c5 100644
--- a/drivers/ata/ata_piix.c
+++ b/drivers/ata/ata_piix.c
@@ -94,6 +94,9 @@
#include
#include
#include
+#ifdef CONFIG_X86
+#include
+#endif
#define DRV_NAME "ata_piix"
#define DRV_VERSION "2.13"
@@ -1666,9 +1669,21 @@ static void piix_remove_one(struct pci_dev *pdev)
ata_pci_remove_one(pdev);
}
+static int prefer_ms_hyperv = 1;
+
static int __init piix_init(void)
{
int rc;
+#ifdef CONFIG_X86
+ /*
+ * If we are on the Microsoft Hyper-V platform deferr to its block
+ * drivers.
+ */
+ if (prefer_ms_hyperv && x86_hyper == &x86_hyper_ms_hyperv) {
+ pr_info("ata_piix: deferring to Hyper-V hypervisor");
+ return -ENODEV;
+ }
+#endif
DPRINTK("pci_register_driver\n");
rc = pci_register_driver(&piix_pci_driver);
@@ -1688,3 +1703,5 @@ static void __exit piix_exit(void)
module_init(piix_init);
module_exit(piix_exit);
+
+module_param(prefer_ms_hyperv, int, 0);
--
1.7.9
===
==
==
http://people.canonical.com/~apw/lp929545-precise/0002-debug.patch
===
From b58963a158e54b716bd6e43de08df4503f273a00 Mon Sep 17 00:00:00 2001
From: Andy Whitcroft
Date: Fri, 10 Feb 2012 19:55:16 +0000
Subject: [PATCH 02/70] debug
---
drivers/ata/ata_piix.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/ata/ata_piix.c b/drivers/ata/ata_piix.c
index f8280c5..b022548 100644
--- a/drivers/ata/ata_piix.c
+++ b/drivers/ata/ata_piix.c
@@ -1682,6 +1682,8 @@ static int __init piix_init(void)
if (prefer_ms_hyperv && x86_hyper == &x86_hyper_ms_hyperv) {
pr_info("ata_piix: deferring to Hyper-V hypervisor");
return -ENODEV;
+ } else {
+ pr_info("ata_piix: no Hyper-V hypervisor found");
}
#endif
--
1.7.9
===
==
Var B Or "OpenSUSE Way"
http://patchwork.ozlabs.org/patch/112939/
===
...
Olaf Hering - Sept. 1, 2011, 3:43 p.m.
On Wed, Aug 31, Olaf Hering wrote:
> After some more testing it looks like the hv_blkvsc driver claimed the
> ide major #3, so the ide_core could not bind to the emulated IDE
> hardware. The modprobe.conf rules prevented that ata_piix gets loaded.
> If I force a module load order of 'ata_piix ;hv_blkvsc' both ata_piix
> and hv_blkvsc will bind to the same drive, just as shown in my previous
> mail. So there is appearently no way to shutdown the IDE ports like it
> is done with xen_emul_unplug= option for Xen guests.
>
> Maybe some hack is needed for a hyper-v specific unplug if Windows does
> indeed lack that feature. Now that ata_piix is compiled into the kernel,
> there is nothing to a modprobe.conf rule can "fix".
Here is an attempt to ignore disks in a hyper-v disks, and let ata_piix
handle only the configured cdrom devices (iso of physical).
If the disks are not ignored, they will appear twice, once through
ata_piix and once through hv_storvsc.
Once hv_storvsc can also handle the configured cdrom devices, the added
piix_pata_read_id() function can be removed again. Only the check in
piix_init() or something similar needs to be done.
Maybe there is a better way enable only ATA_DEV_ATAPI?
Signed-off-by: Olaf Hering
. . .
Patch
--- a/drivers/ata/ata_piix.c
+++ b/drivers/ata/ata_piix.c
@@ -98,6 +98,10 @@
#define DRV_NAME "ata_piix"
#define DRV_VERSION "2.13"
+#if defined(CONFIG_HYPERV_STORAGE) || defined(CONFIG_HYPERV_STORAGE_MODULE)
+#define PIIX_IGNORE_ATA_ON_HYPERV 1
+#endif
+
. . .
...
===
--------------------------------------------------------------------------------
From: KY Srinivasan
Sent: Tuesday, February 21, 2012 7:37 PM
To: Мясников Виктор Вячеславович
Subject: RE: . . . b) patches to ata_piix need in _official_ kernel RE: Ubuntu: ata_piix.prefer_ms_hyperv=0 Fw: Problem: \dev\sda == \dev\sdb Fw: IDE drives to hv_storvsc and drops hv_blkvsc Fw: State of Linux on Hyper-V
. . .
With regards to the ata_piix changes, we will try to push that upstream shortly.
K. Y
_http://www.virtualisation.co.uk/2009/03/hyper-v-mouse-not-captured-in-remote-desktop-session/
==
. . .
when you try to use the mouse is that you’ll receive the message popup “Mouse not captured in Remote Desktop Session”, and instead of a mouse pointer will just get a dot in it’s place.
. . .
==
_http://www.virtualisation.co.uk/2009/03/hyper-v-mouse-not-captured-in-remote-desktop-session/comment-page-1/#comment-836
http://ubuntuforums.org/showthread.php?t=1389024
==
matthew.mattoon
May 29th, 2010Now it sounds to me like the mouse is not working for you at all? If that is the case it is probably due to you using RDP from your workstation to another workstation or the server, then from their using SCVMM or Hyper-V Manager to connect to the VM. This will NOT work for mouse. If you use your workstation to connect to the VM directly via SCVMM or Hyper-V Manager it will work just fine. It is simply the problem with the RDP connection losing control of the mouse (this happens on Windows guests with no ICs as well).
==
“Windows guests with no ICs” equal by mouse support to “Linux”
Mini How-To about _practically_ method for worked mouse in {Windows guests with no ICs}/Linux guest:
Linux on Hyper-V How-To FIX “Mouse not captured in Remote Desktop session”
http://vvm.blog.tut.by/2011/02/22/hype-v_mouse_in_linux/
==
. . .
Without IC/Satori, mouse work in {Windows guests with no ICs}/{Linux Guest} if connect to it from {Windows physical workstation} _directly_
. . .
==
Sorry i’m forgot «r» in «hyper-v_mouse_in_linux» 
Right URL:
http://vvm.blog.tut.by/2011/02/22/hyper-v_mouse_in_linux/
==
Without Satori, mouse work in Linux Guest if connect to it from Windows _directly_
. . .
установите на рабочую станцию MMC-оснастку Hyper-V и _напрямую_ подключайтесь к Guest-компьютерам
==
Впрочем, пусть здесь будет сперва русский текст, затем English, а там наоборот Ж-)
Комментарии, please, в «hyper-v_mouse_in_linux»
– — – –
Without Satori, mouse work in Linux Guest if connect to it from Windows _directly_
Or
Linux on Hyper-V How-To FIX “Mouse not captured in Remote Desktop session”
Подробнее:
http://blogs.technet.com/b/abeshkov/archive/2011/01/30/3383495.aspx
==
Стоит отметить, что поддержки синтетической мыши в Ubuntu нет, а проект Satori пока что не портирован под этот дистрибутив, поэтому для удаленного управления в графическом режиме я использовал VNC.
==
На практике Satori не очень-то и нужен
http://blogs.technet.com/b/abeshkov/archive/2011/02/07/3385455.aspx
==
если вы присоединяетесь к Hyper-V через RDP а затем через консоль Hyper-V открываете окно в виртуальную машину то мышь в ней работать не будет.
==
Оказалось, что это надо понимать так: установите на рабочую станцию MMC-оснастку Hyper-V и _напрямую_ подключайтесь к Guest-компьютерам
http://technet.microsoft.com/ru-ru/library/cc742454.aspx
==
Не удается использовать мышь для управления виртуальной машиной. Для подключения к серверу, на котором установлено средство Hyper-V, используется подключение к удаленному рабочему столу.
Причина. При использовании диспетчера Hyper-V для подключения к виртуальной машине это подключение обеспечивает компонент «Подключение к виртуальной машине». Однако использование подключения к виртуальной машине в сеансе подключения к удаленному рабочему столу не поддерживается, если не установлены службы интеграции. Поэтому ожидаемый результат – потеря функциональности мыши.
Устранение. Не используйте подключение к виртуальной машине в сеансе подключения к удаленному рабочему столу, . . . Есть несколько способов решить эту проблему.
- . . .
- . . .
- На поддерживаемом клиентском компьютере установить средства управления Hyper-V, чтобы установить компонент «Подключение к виртуальной машине» и создать сеанс подключения к виртуальной машине. Дополнительные сведения см. в технической библиотеке Windows Server 2008 ( http://technet.microsoft.com/ru-ru/library/cc794756(WS.10).aspx )
==
Остается некоторое неудобство:
==
При использовании подключения к виртуальной машине указатель мыши принимает вид точки или «застревает» в окне виртуальной машины.
. . .
Устранение. . . . Если операционная система на виртуальной машине не поддерживается, то можно использовать комбинацию клавиш для перемещения мыши за пределы окна виртуальной машины. Комбинация клавиш по умолчанию – CTRL+ALT+СТРЕЛКА ВЛЕВО.
==
Linux on Hyper-V How-To FIX “Mouse not captured in Remote Desktop session”
in English:
Shane 22 Oct 2010 11:34 AM
We still need mouse integration thou and I haven’t been able to find anything on how to enable it.
==
one of the dialog windows cannot be accessed using the keyboard so I’m having to leave the comfort of my office and walk all the way over to the server room, log into it, click a mouse a couple of times, and then return to the office again.
==
==
No alternate like get used to keyboard or command line controll..
==
_http://weblog.allanglesit.net/2010/05/eight-things-you-need-to-know-about-linux-on-hyper-v/
==
It is also important to note that mouse integration is not included in the kernel, and will not work
==
«not included» — Yes
«not work» — No ( if use Hyper-V MMC оn _physical_ workstantion)
http://ubuntuforums.org/showthread.php?t=1389024
==
matthew.mattoon
May 29th, 2010Now it sounds to me like the mouse is not working for you at all? If that is the case it is probably due to you using RDP from your workstation to another workstation or the server, then from their using SCVMM or Hyper-V Manager to connect to the VM. This will NOT work for mouse. If you use your workstation to connect to the VM directly via SCVMM or Hyper-V Manager it will work just fine. It is simply the problem with the RDP connection losing control of the mouse (this happens on Windows guests with no ICs as well).
==
Without Satori, mouse work in Linux Guest if connect to it from Windows _directly_ :
http://technet.microsoft.com/en-us/library/cc742454.aspx
==
When I try to control a virtual machine, I cannot use the mouse. I am using Remote Desktop Connection to connect to a server running Hyper-V.
Cause: When you use Hyper-V Manager to connect to a virtual machine, Virtual Machine Connection provides the connection to the virtual machine. However, use of Virtual Machine Connection within a Remote Desktop Connection session is not supported until integration services ( VVM: integration services _with_ synthectic mouse support) are installed. As a result, lack of mouse functionality is expected behavior.Solution: Avoid using Virtual Machine Connection within a Remote Desktop Connection session until integration services are installed. There are several ways you can accomplish this:
. . .
On a supported client computer, install the Hyper-V management tools to install Virtual Machine Connection on the computer ( VVM: «computer» need read as «personal workstantion» ) and establish a Virtual Machine Connection session to the virtual machine. For more information, see the Windows Server 2008 Technical Library (http://go.microsoft.com/fwlink/?LinkId=143558).
==
Little imperfection:
==
When I use Virtual Machine Connection, the mouse pointer appears as a dot or the mouse pointer is stuck in the virtual machine window.. . .
Solution: . . .
If the guest operating system is not supported, you can use a key combination to move the mouse out of the virtual machine window. The default key combination is CTRL+ALT+LEFT ARROW.
==
– — – — – — – — – — – — – — – — – — – — – — – — – — – — – –
Without Satori, mouse work in Linux Guest if connect to it from Windows _directly_
Or
Linux on Hyper-V How-To FIX “Mouse not captured in Remote Desktop session”
Подробнее:
http://blogs.technet.com/b/abeshkov/archive/2011/01/30/3383495.aspx
==
Стоит отметить, что поддержки синтетической мыши в Ubuntu нет, а проект Satori пока что не портирован под этот дистрибутив, поэтому для удаленного управления в графическом режиме я использовал VNC.
==
На практике Satori не очень-то и нужен
http://blogs.technet.com/b/abeshkov/archive/2011/02/07/3385455.aspx
==
если вы присоединяетесь к Hyper-V через RDP а затем через консоль Hyper-V открываете окно в виртуальную машину то мышь в ней работать не будет.
==
Оказалось, что это надо понимать так: установите на рабочую станцию MMC-оснастку Hyper-V и _напрямую_ подключайтесь к Guest-компьютерам
http://technet.microsoft.com/ru-ru/library/cc742454.aspx
==
Не удается использовать мышь для управления виртуальной машиной. Для подключения к серверу, на котором установлено средство Hyper-V, используется подключение к удаленному рабочему столу.
Причина. При использовании диспетчера Hyper-V для подключения к виртуальной машине это подключение обеспечивает компонент «Подключение к виртуальной машине». Однако использование подключения к виртуальной машине в сеансе подключения к удаленному рабочему столу не поддерживается, если не установлены службы интеграции. Поэтому ожидаемый результат – потеря функциональности мыши.
Устранение. Не используйте подключение к виртуальной машине в сеансе подключения к удаленному рабочему столу, . . . Есть несколько способов решить эту проблему.
- . . .
- . . .
- На поддерживаемом клиентском компьютере установить средства управления Hyper-V, чтобы установить компонент «Подключение к виртуальной машине» и создать сеанс подключения к виртуальной машине. Дополнительные сведения см. в технической библиотеке Windows Server 2008 ( http://technet.microsoft.com/ru-ru/library/cc794756(WS.10).aspx )
==
Остается некоторое неудобство:
==
При использовании подключения к виртуальной машине указатель мыши принимает вид точки или «застревает» в окне виртуальной машины.
. . .
Устранение. . . . Если операционная система на виртуальной машине не поддерживается, то можно использовать комбинацию клавиш для перемещения мыши за пределы окна виртуальной машины. Комбинация клавиш по умолчанию – CTRL+ALT+СТРЕЛКА ВЛЕВО.
==