https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
--- Comment #28 from Michael ---
(In reply to Harald Schmalzbauer from comment #27)
> Do you get detach kernel messages, or is it just unresponsive?
No messages. The keyboard just becomes unresponsive.
> The latter may be due to scrollLock
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
Harald Schmalzbauer changed:
What|Removed |Added
CC||bugzilla.free...@omnilan.de
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
--- Comment #26 from Michael ---
(In reply to Michael from comment #25)
I forgot to say that all VMs have Mellanox ConnectX-3 and Mellanox ConnectX-4
network cards with SR-IOV enabled (all VMs have network cards with active
SR-IOVs).
--
Y
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
--- Comment #25 from Michael ---
(In reply to Wei Hu from comment #24)
Windows Hyper-V 2019 Server 10.0.17763
(KB4586875, KB4494174, KB4523204, KB4539571, KB4549947, KB4558997, KB4561600,
KB4562562, KB4580325, KB4587735, KB4592440)
All VMs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
--- Comment #24 from Wei Hu ---
(In reply to Michael from comment #23)
I also have a Gen2 VM running for a while. I used it to developed a FreeBSD
kernel module last year, and I left it running since then. I admit I don't
directly use conso
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
--- Comment #23 from Michael ---
(In reply to Wei Hu from comment #21)
I noticed an interesting point.
We have only two Gen2 VMs on the hypervisor.
We turn on the first VM. The keyboard works for a day or two normally, it does
not disappear
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
--- Comment #22 from Michael ---
(In reply to Wei Hu from comment #21)
If so, then these patches did not help.
I updated the kernel a few days ago - the keyboard in the Hyper-V console
disappears anyway after a while of using it.
I do not i
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
--- Comment #21 from Wei Hu ---
(In reply to Michael from comment #20)
Vladimir committed following two on April 12:
commit e4643aa4c4ffd385a5be635a488cf10fb6d6cf68
Author: Vladimir Kondratyev
Date: Mon Apr 12 02:08:36 2021 +0300
h
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
--- Comment #20 from Michael ---
(In reply to Vladimir Kondratyev from comment #19)
I don't see any patch for keyboard disappearing from you in Gen2 VM in current
branch 14.0.
It is highly desirable to have a normal keyboard in the console,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
--- Comment #19 from Vladimir Kondratyev ---
(In reply to Michael from comment #18)
> disappearance of the keyboard in the Hyper-V console after a few seconds on
> the Gen2 VM
Hopefully it is fixed in 14. I added K_XLATE, K_CODE and evdev
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
Michael changed:
What|Removed |Added
CC||michael@gmail.com
--- Comment #18 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
--- Comment #17 from Dexuan Cui ---
(In reply to Vladimir Kondratyev from comment #16)
Thanks, Vladimir! Sounds like a good cooperation opportunity! :-)
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
--- Comment #16 from Vladimir Kondratyev ---
(In reply to Dexuan Cui from comment #15)
> I'm just not familiar with the HID part.
And I am not familiar with VMbus :-)
> IIRC, for every mouse event, the Hyper-V host sends
> a 7-byte "input_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
--- Comment #15 from Dexuan Cui ---
(In reply to Vladimir Kondratyev from comment #14)
Hi Vladimir, sorry I actually just did some research and didn't write any code.
:-)
The Hyper-V/VMBus part of the driver should be straightforward, I'm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
Vladimir Kondratyev changed:
What|Removed |Added
CC||w...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
--- Comment #13 from Dexuan Cui ---
(In reply to Dwerva from comment #12)
Hi Dwerva, maybe you can use a Generation-1 FreeBSD VM as a workaround? Mouse
works with Gen1 FreeBSD VMs, because Hyper-V emulates a legacy mouse.
For Gen-2 VMs, Hy
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
Dwerva changed:
What|Removed |Added
CC||btrfs...@gmail.com
--- Comment #12 from D
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
--- Comment #11 from Lars Engels ---
Sorry, disregard my last comment. It was written out of frustation.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-vir
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
Lars Engels changed:
What|Removed |Added
CC||l...@freebsd.org
--- Comment #10 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
scorpionm...@gmail.com changed:
What|Removed |Added
Version|11.1-RELEASE|CURRENT
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
--- Comment #9 from scorpionm...@gmail.com ---
(In reply to Greg V from comment #5)
(In reply to scorpionmage from comment #7)
I switched to using xmonad on FreeBSD in the interim, as it lets me use X
without a mouse. It does force learning
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
--- Comment #8 from scorpionm...@gmail.com ---
BTW, this is also happening in 12.0 and Current.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualizatio
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
--- Comment #7 from scorpionm...@gmail.com ---
(In reply to Greg V from comment #5)
Agree - the modern technologies are the reason. And it also allows the
streamlining of configurations across Linux and FreeBSD VMs. It also allows the
GPT pa
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
--- Comment #6 from scorpionm...@gmail.com ---
(In reply to Sepherosa Ziehau from comment #3)
Can you please explain why the console is not suitable? Is there a difference
between the Gen 1 and Gen 2 consoles?
I am not a fan of the VNC opti
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
Greg V changed:
What|Removed |Added
CC||greg@unrelenting.technology
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
--- Comment #4 from Sepherosa Ziehau ---
(In reply to scorpionmage from comment #2)
Well, if you _do_ want to stick w/ using the X on the Hyper-V console, then use
gen1 VM, which has an emulated PS2 mouse. I actually don't see gen2 VM buy
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
--- Comment #3 from Sepherosa Ziehau ---
(In reply to scorpionmage from comment #2)
As I said, no plan for it yet. The Hyper-V console is _not_ suitable for X
related stuffs. And again, if you want to use X, use VNC; it is recommended
an
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
--- Comment #2 from scorpionm...@gmail.com ---
(In reply to Sepherosa Ziehau from comment #1)
So, there will be no mouse working in X for a HyperV Gen 2 VM?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
Sepherosa Ziehau changed:
What|Removed |Added
CC||sepher...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-virtualization@Free
30 matches
Mail list logo