Виктор Мясников ( Victor Miasnikov)

 . . .

-1 blocker, this seems to be enough of a corner case to not warrant a release blocker.

2013-01-10 13-15 ( GMT +03 ):

adamwill.fedorapeople.org 20130109-prerc3-x86_64.iso on Hyper-V the fprintd bug fixed :

2013-01-09 16-02 ( GMT +03 ): another , may be minor, bug:

To All : please help me with communication with Fedora Development team

De-facto Bug 883005 is well-known problem Mouse Integration in Linux guest

-- Sub-problem N1

Ok, as temporary solution do this:

mouse work in Linux Guest without "MS Vmbus HID-compliant Mouse", if connect to it from Windows _directly_

http://vvm.blog.tut.by/2011/02/22/hyper-v_mouse_in_linux/
==
. . .
Without "Microsoft Vmbus HID-compliant Mouse" ,
mouse work in {Linux Guest without hid_hyperv} if connect to it from {Windows physical workstation} _directly_
. . .
==

-- and imm. after solve N1, we look Sub-problem N2 i.e.
CTRL + ALT + Left Arrow to release the mouse

http://blog.allanglesit.com/2010/05/ubuntu-and-hyper-v-the-paths-to-enlightenment/
==
Mouse Integration

When a user uses Hyper-V Management Console or System Center Virtual Machine Manager to connect to a VM [ with Linux without "MS Vmbus HID-compliant Mouse" ]
and they begin to interact with the desktop via the mouse, they find themselves in an interesting situation where they are unable to reclaim their mouse pointer from the VM without entering a somewhat cryptic keystroke ctrl + alt + left arrow.
==

>(In reply to comment #5)
>> (In reply to comment #4)

JB>>> The Fedora kernel builds and provides those modules,
JB>>> but they aren’t included in the initramfs.
VVM>> Yes


JB>>> If they should be (and I have no idea),
JB>>>then dracut probably needs to include them.
VVM>> Do not worry , they should be include

N.Ch.> Why ?
N.Ch.> I’m using Server2012 Eval x86_64 and at the end of the install, I have:

==
# lsmod | grep hyperv
hid_hyperv 13059 0
hv_vmbus 33752 4 hv_netvsc,hid_hyperv,hv_utils,hv_storvsc
==

N.Ch.> Despite thoses are not included in the initramfs,
N.Ch.>they are probably not useful during the boot phase?
N.Ch.>(maybe hv_storvsc should be made available thought).

!) Mouse ( as phisical/material device) is used, primary, by end-user/sysadmin for work with user interface of Fedora installer

Of course, if You use fully automated install mode ( for example, by script) worked state of mouse kernel module not important

But in _interactive_ mode -- "worked state of mouse kernel module" is welcom!

1) Of course,
driver ( ok, "kernel module" ) for SCSI and IDE disks ( hv_storvsc) is more important, what driver for mouse ( hid_hyperv)

2)"at end of the install" -- is to late, need "at begin of the install"

2b)

How exactly method:
by
-- "dracut needs to include hid_hyperv"
Or by
-- "hid_hyperv need be include in the initramfs"

will be choice by Fedora Development team

2012/08/22:

==
2012-04-11 - Justin M. Forbes jforbes (at) redhat.com - enable HyperV drivers
==

Fedora 18 install disk contain Hyper-V drivers

hv_storvsc.ko
hv_netvsc.ko

Syntetic LANCard , SCSI disks -- all Ok

Tested on
Fedora-18-Alpha-TC3-x86_64-netinst.iso

2013-01-09:

Some-Fedora-Mirror/pub/.6/fedora.redhat.com/linux/development/18/x86_64/os/images/boot.iso