Fedora 18 on Hyper-V

2013-10-18:

Look like whate
==
Bug 883005 is minor issue related *-netinstall.iso ( in *LiveCD*.iso mouse work as need )
==

FIXed in Fedora 20 Alpha 4

2013-01-13:

IMHO, Bug 883005 is minor issue related *-netinstall.iso ( in *LiveCD*.iso mouse work as need )

See later *.png [ related non-netinstal, but LiveCD ] with example _good_ work mouse driver , look on hid_hyperv in lsmod output

How exactly Fedora Team fixed this issue , not principial for me

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

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

2013-01-09 16-02 ( GMT +03 ):

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

==
— Comment #62 from Giovanni Tirloni <FFFFFFFF@FFFFFFF.ibm.com> —
+1 blocker – F18 does not work on Hyper-V and from what I can tell from other
comments, it has issues on Vmware and Xen too. It would not consider that a
corner case.
==
Thanks for help!
.
.
—– Original Message —–
From: { May be, public in future } WWWWWWWWW@redhat.com
To: "Victor Miasnikov"
Sent: Wednesday, January 09, 2013 5:06 PM
Subject: Re: Fw: Problem is solved? or not? FW: Bug 810040 https://bugzilla.redhat.com/show_bug.cgi?id=810040

> On 01/09/2013 09:01 AM, Victor Miasnikov wrote:
>>
>> Hi!
>> Problem exist? Or not?
Yes, the problem exists, but there is a fix.
The fprintd maintainer has told me [ WWWWWWWWW@redhat.com] he will do a release this week, . . .
—– Original Message —–
From: "Victor Miasnikov" <vvm ( at )tut (dot) by>
. . . To ZZZZZ , YYYYYYYYYYYYY . . .
Cc: <CCCCCCCC@redhat.com>; <DDDDDDDDD@redhat.com>
Sent: Wednesday, January 09, 2013 4:53 PM

Hi!
Problem is solved? or not?
==

5) yum update *.rpm
6) telinit 3; telinit 5; No gnome-shell error
7) Reboot VM and verify no gnome-shell error

Now for KVM guests via libvirt, disabling USB is not something most people will do. However xen and other virt platforms don’t seem to add a USB bus by default so this bug makes fedora and gnome look pretty bad.

halfline, hadess, can someone spin up F17 and F18 updates?

 . . .

Tested with Success on Hyper-V Server 2012 x86_64 (Fedora-18 x86_64 Guest)
I was able to login with gnome3.
Why this was not added into the repo more early?

This bug should have been considered as a blocker IMHO. (or NTH at least). This affect the ability to have a usable system at the end of a graphical install in order to later make updates.

. . .
. . .
2013-01-09 08:25:16 EST
-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 :

==

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

Fedora-18-development-x86_64-2013-01-08 problem Mouse Integration in Linux guest

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.
==


Fedora-18-development-x86_64-2013-01-08 problem CTRL + ALT + Left Arrow to release the mouse


>(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

3 комментария to “Fedora 18 on Hyper-V”

  • vvm:

    http://social.technet.microsoft.com/Forums/en/linuxintegrationservices/thread/19d21642-dd11-4c30-bbb1-bf5982ee1c83

    ==
    . . .

    2)

    In Fedora do “enable HyperV drivers” _after_ 2012-04-12 :

    http://lists.fedoraproject.org/pipermail/test/2012-April/106870.html
    ===

    . . .
    kernel-3.4.0-0.rc2.git2.1.fc18
    ——————————
    * Thu Apr 12 2012

    . . .

    * Wed Apr 11 2012 Justin M. Forbes
    - enable HyperV drivers

    . . .


    ===

    i.e. _before_ 2012-04-12 — need recompile kernel, etc.

    Z)

    Total: _best_ wait Fedora 18

    . . .
    ==

  • vvm:

    https://bugzilla.redhat.com/show_bug.cgi?id=883005
    ==
    Fedora-18-Beta-x86_64-netinst.iso
    not include
    hid-hyperv.ko
    ( “Microsoft Vmbus HID-compliant Mouse”)

    Reproducible: Always

    Steps to Reproduce:
    Run
    lsmod | grep hyperv

    Expected Results:
    hid_hyperv 9999 9
    ==

    ==
    Victor Miasnikov 2012-12-04 03:28:22 EST
    JB> The Fedora kernel builds and provides those modules,
    JB> but they aren’t included in the initramfs.

    Yes

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

    Do not worry :-) , they should be include
    =>
    dracut needs to include them

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

    — Sub-problem N1
    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.
    ==

    P.P.S.

    Users and administrators of Hyper-V get a bad first impression about Fedora 18 ,
    when see problem with mouse, even on install step

    This problem already solved in OpenSUSE, Ubuntu, Debian , etc.
    ==

  • vvm:

    Fedora 17 on Hyper-V

    https://bugzilla.redhat.com/show_bug.cgi?id=810040
    {=
    http://forums.fedoraforum.org/showthread.php?t=280686
    ==

    Fedora 17 and Hyper-V

    – — – — –

    Inorder
    5th June 2012, 05:13 PM

    Hello!
    I took Fedora-17-x86_64-DVD.iso and installed Fedora 17 on a Hyper-V virtual machine. The installation went fine, but booting a system fails with a “Oh no! Something has gone wrong.” screen.

    Fedora 16 runs on Hyper-V without problems. So there is something in version 17 that breaks the compatibility. I can help investigating this issue by collecting logs etc.

    . . .

    EvanJones
    27th June 2012, 06:40 PM

    Re: Fedora 17 and Hyper-V

    http://comments.gmane.org/gmane.linux.redhat.fedora.general/415271

    Basically reboot and enter command line mode. At the prompt enter “yum remove fprintd” (no quotes). Answer yes to questions and then reboot when finished. It should take you to a good login with no problems

    ==

Leave a Reply

*
Для того, чтобы убедиться что Вы человек, а не спам-бот, введите пожалуйста ответ.
Анти-спам выражение.

Copyright © 2014 Виктор Мясников ( Victor Miasnikov). Search Engine Optimization by Star Nine. Distributed by Wordpress Themes
Хостинг hoster.by   Сервис белорусских блогов: BLOGS.TUT.BY