RE: FreeBSD 12.1 i386 on Hyper-V Fails to Mount Root

2021-06-05 Thread Wei Hu via freebsd-virtualization
g > Subject: Re: FreeBSD 12.1 i386 on Hyper-V Fails to Mount Root > > Am 19.05.2021 um 13:26 schrieb Harry Schmalzbauer: > > ... > > I can just assure that I tracked it down to the single r332489 committ > > which makes vmbus(4) failing on i386. > > Verification don

Re: FreeBSD 12.1 i386 on Hyper-V Fails to Mount Root

2021-05-21 Thread Harry Schmalzbauer
hard time catching up with x86 basics, I found another oddity: On Hyper-V gen1, the maximum ammount of RAM I can assign a FreeBSD guest beeing able to boot i386 is 3914MB, startring with r332489. As soon as I configure the guest to have 3916MB or more, FreeBSD-i386 r332489 booting leads to g

Re: FreeBSD 12.1 i386 on Hyper-V Fails to Mount Root

2021-05-21 Thread Harry Schmalzbauer
her oddity: On Hyper-V gen1, the maximum ammount of RAM I can assign a FreeBSD guest beeing able to boot i386 is 3914MB, startring with r332489. As soon as I configure the guest to have 3916MB or more, FreeBSD-i386 r332489 booting leads to guest reset.  Loader starts kernel, machine reboot

[Bug 221074] Hyper V Gen 2 install has no mouse

2021-05-20 Thread bugzilla-noreply
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

[Bug 221074] Hyper V Gen 2 install has no mouse

2021-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074 Harald Schmalzbauer changed: What|Removed |Added CC||bugzilla.free...@omnilan.de

[Bug 221074] Hyper V Gen 2 install has no mouse

2021-05-20 Thread bugzilla-noreply
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). --

[Bug 221074] Hyper V Gen 2 install has no mouse

2021-05-20 Thread bugzilla-noreply
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

[Bug 221074] Hyper V Gen 2 install has no mouse

2021-05-19 Thread bugzilla-noreply
. In the meantime, if you can problem more information about how to reproduce it, such as the kind of operation you are using on the consoles, and Hyper-V version, it may help. -- You are receiving this mail because: You are the assignee for the bug

Re: FreeBSD 12.1 i386 on Hyper-V Fails to Mount Root

2021-05-19 Thread Harry Schmalzbauer
Knight ; freebsd-virtualization@freebsd.org Subject: Re: FreeBSD 12.1 i386 on Hyper-V Fails to Mount Root On Mon, May 17, 2021 at 04:12:20AM +, Wei Hu wrote: : : : separately. The workaround for this on amd64 is either build these Hyper-V modules into the kernel or completely disable mitigation

Re: FreeBSD 12.1 i386 on Hyper-V Fails to Mount Root

2021-05-17 Thread Harry Schmalzbauer
: FreeBSD 12.1 i386 on Hyper-V Fails to Mount Root On Mon, May 17, 2021 at 04:12:20AM +, Wei Hu wrote: : : : separately. The workaround for this on amd64 is either build these Hyper-V modules into the kernel or completely disable mitigation by setting vm.pmap.pti="0" in /boot/l

Re: FreeBSD 12.1 i386 on Hyper-V Fails to Mount Root

2021-05-17 Thread Konstantin Belousov
g > > Subject: Re: FreeBSD 12.1 i386 on Hyper-V Fails to Mount Root > > > > On Mon, May 17, 2021 at 04:12:20AM +, Wei Hu wrote: > > > Copy Kib who was the author of PTI and other relate patches. > > > > > > This looks to be caused by Meltdown and Sp

RE: FreeBSD 12.1 i386 on Hyper-V Fails to Mount Root

2021-05-17 Thread Wei Hu via freebsd-virtualization
> -Original Message- > From: Konstantin Belousov > Sent: Monday, May 17, 2021 1:47 PM > To: Wei Hu > Cc: Harry Schmalzbauer ; Chris Knight > ; freebsd-virtualization@freebsd.org > Subject: Re: FreeBSD 12.1 i386 on Hyper-V Fails to Mount Root > > On Mon, May 1

Re: FreeBSD 12.1 i386 on Hyper-V Fails to Mount Root

2021-05-16 Thread Konstantin Belousov
e > patches: > https://wiki.freebsd.org/SpeculativeExecutionVulnerabilities > > The amd64 patches also caused problems > on Hyper-V (triple fault) when vmbus and other HyperV drivers (netvsc, > storvsc etc) > were loaded separately. The workaround for this on amd64 is eit

RE: FreeBSD 12.1 i386 on Hyper-V Fails to Mount Root

2021-05-16 Thread Wei Hu via freebsd-virtualization
patches also caused problems on Hyper-V (triple fault) when vmbus and other HyperV drivers (netvsc, storvsc etc) were loaded separately. The workaround for this on amd64 is either build these Hyper-V modules into the kernel or completely disable mitigation by setting vm.pmap.pti="0"

Re: FreeBSD 12.1 i386 on Hyper-V Fails to Mount Root

2021-05-15 Thread Harry Schmalzbauer
Am 14.05.2021 um 18:44 schrieb Harry Schmalzbauer: Am 16.10.2020 um 11:35 schrieb Wei Hu via freebsd-virtualization: : Did you try 12.0? Maybe something changed in 12.x causes failure. I386 is not well tested on Hyper-V. I will try to reproduce and take a look. The regression happened

Re: FreeBSD 12.1 i386 on Hyper-V Fails to Mount Root

2021-05-14 Thread Harry Schmalzbauer
Am 16.10.2020 um 11:35 schrieb Wei Hu via freebsd-virtualization: Howdy, Just started the upgrade process on some FreeBSD 11.4 VMs to FreeBSD 12.1 using freebsd-update. VMs are running on multiple Hyper-V 2012 R2 and 2019 systems, all systems with 2020-09 Cumulative Updates installed. The amd64

[Bug 221074] Hyper V Gen 2 install has no mouse

2021-05-13 Thread bugzilla-noreply
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

[Bug 221074] Hyper V Gen 2 install has no mouse

2021-05-13 Thread bugzilla-noreply
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

[Bug 221074] Hyper V Gen 2 install has no mouse

2021-05-12 Thread bugzilla-noreply
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

[Bug 221074] Hyper V Gen 2 install has no mouse

2021-05-12 Thread bugzilla-noreply
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

[Bug 221074] Hyper V Gen 2 install has no mouse

2021-05-12 Thread bugzilla-noreply
from Michael --- At the expense of the mouse - this is certainly good, but so far no one has fixed the disappearance of the keyboard in the Hyper-V console after a few seconds on the Gen2 VM (it started somewhere in the beginning of 12.0 and at 14.0 the same thing). -- You are receiving this mail

[Bug 254695] Hyper-V + TCP_BBR: Kernel Panic: Assertion in_epoch(net_epoch_preempt) failed at netinet/tcp_lro.c:915

2021-04-19 Thread bugzilla-noreply
35c7bb340788f0ce9347b7066619d8afb31e2123 on Sept 24, 2019. I wonder if this problem existed from Day 1 of this commit and it has only been tested on Hyper-V recently by you. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization

[Bug 254695] Hyper-V + TCP_BBR: Kernel Panic: Assertion in_epoch(net_epoch_preempt) failed at netinet/tcp_lro.c:915

2021-04-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695 Gordon Bergling changed: What|Removed |Added Summary|Hyper-V: Kernel Panic: |Hyper-V + TCP_BBR: Kernel

[Bug 254695] Hyper-V: Kernel Panic: Assertion in_epoch(net_epoch_preempt) failed at netinet/tcp_lro.c:915

2021-04-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695 --- Comment #9 from Gordon Bergling --- (In reply to Wei Hu from comment #8) Thanks for the investigation. I was able to boot a kernel from today (15 April) on this machine. I tracked the issue down to the tcp_bbr or cc_htcp. I build the

[Bug 254695] Hyper-V: Kernel Panic: Assertion in_epoch(net_epoch_preempt) failed at netinet/tcp_lro.c:915

2021-04-11 Thread bugzilla-noreply
is how my test env looks: - Hyper-V Version: 10.0.17763 [SP1] - NFS mount not at boot time. I tried automount during boot but it keeps complaining the file system is not clean, couldn't find fsck_nfs to check and kick me into single user mode. I think that's something with my configuration however

[Bug 254695] Hyper-V: Kernel Panic: Assertion in_epoch(net_epoch_preempt) failed at netinet/tcp_lro.c:915

2021-04-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695 --- Comment #7 from Gordon Bergling --- (In reply to Wei Hu from comment #6) This panic occurs right at boot time when an NFS share is mounted. I have a 12-STABLE system, virtualized also via Hyper-V on the same Windows10 system, which

[Bug 254695] Hyper-V: Kernel Panic: Assertion in_epoch(net_epoch_preempt) failed at netinet/tcp_lro.c:915

2021-04-09 Thread bugzilla-noreply
miliar to the lro and epoch code. the HyperV hn driver had couple commit since March 12. The commits are about RSC support for packets from same host. Is the NFS server VM running on the same Hyper-V host? If it is easy for your reproduce on the current build, can you try any build before March 12

[Bug 254695] Hyper-V: Kernel Panic: Assertion in_epoch(net_epoch_preempt) failed at netinet/tcp_lro.c:915

2021-04-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695 --- Comment #5 from Gordon Bergling --- Backtrace #0 __curthread () at /boiler/nfs/src/sys/amd64/include/pcpu_aux.h:55 #1 doadump (textdump=textdump@entry=1) at /boiler/nfs/src/sys/kern/kern_shutdown.c:399 #2 0x80c132f0 in

[Bug 254695] Hyper-V: Kernel Panic: Assertion in_epoch(net_epoch_preempt) failed at netinet/tcp_lro.c:915

2021-04-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695 --- Comment #4 from Gordon Bergling --- The crash dump is too large for the upload. The stacktrace is the following. KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe0051761840 vpanic() at

[Bug 254695] Hyper-V: Kernel Panic: Assertion in_epoch(net_epoch_preempt) failed at netinet/tcp_lro.c:915

2021-04-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695 --- Comment #3 from Gordon Bergling --- The KERNCONF is the following --- include GENERIC options RATELIMIT options TCPHPTS options KERN_TLS options

[Bug 254695] Hyper-V: Kernel Panic: Assertion in_epoch(net_epoch_preempt) failed at netinet/tcp_lro.c:915

2021-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695 --- Comment #2 from Gordon Bergling --- (In reply to Li-Wen Hsu from comment #1) Its mainly the call chain from vmbus_chan_task() -> hn_chan_callback() which leads me towards an bug in the Hyper-V implementation, since hn0 is the defa

[Bug 254695] Hyper-V: Kernel Panic: Assertion in_epoch(net_epoch_preempt) failed at netinet/tcp_lro.c:915

2021-04-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695 --- Comment #1 from Li-Wen Hsu --- btw it looks more like an error in tcp code, this might be related: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254725 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 254695] Hyper-V: Kernel Panic: Assertion in_epoch(net_epoch_preempt) failed at netinet/tcp_lro.c:915

2021-04-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|virtualizat...@freebsd.org -- You

RE: FreeBSD on Hyper-V network driver negotiation

2021-03-24 Thread Dexuan Cui via freebsd-virtualization
Hi Alex, “the hn0 interface is set to 10GbaseT/ full-duplex” à this should not matter, because the “hn0” interface in a FreeBSD VM on Hyper-V is a virtual NIC which doesn’t really have the concept of “1000baseT”, “10GbaseT”, .etc. I think we just happen to report 10GbaseT in the “hn” driver

FreeBSD on Hyper-V network driver negotiation

2021-03-24 Thread Alex Leach
___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2021-03-14 Thread bugzilla-noreply
Author: Wei Hu AuthorDate: 2020-07-30 07:26:11 + Commit: Wei Hu CommitDate: 2021-03-15 04:47:18 + Prevent framebuffer mmio space from being allocated to other devices on HyperV. On Gen2 VMs, Hyper-V provides mmio space for framebuffer. This mmio address range

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2021-03-13 Thread bugzilla-noreply
late for it to be in 12.2. Regarding to the SRIOV NIC, we only support Mellanox CX3 and CX4 at this time. Intel NICs do not have VF drivers in the guest so they are not supported on Hyper-V. -- You are receiving this mail because: You are the assignee for the bug

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2021-03-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #54 from Dmitry --- Created attachment 223227 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223227=edit Gen2 guest FreeBSD 13.0 RC2 did not supports Hyper-V SR-IOV -- You are receiving this mail because:

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2021-03-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #53 from Dmitry --- (In reply to Dexuan Cui from comment #48) Seems, that fix is totally absent on FreeBSD 12.2-STABLE. I have download FreeBSD 13.0 RC2 and it works in Gen2 as expected - detected and by MSI-X interrupts. But

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2021-03-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 Dmitry changed: What|Removed |Added Attachment #223226|text/plain |image/png mime type|

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2021-03-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #52 from Dmitry --- Created attachment 223226 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223226=edit Gen2 guest FreeBSD 12.2-STABLE em0 passthrough error -6 Have try on another Server PC (with intel CPU) but

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2021-03-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #51 from Dmitry --- Created attachment 223225 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223225=edit Gen2 guest FreeBSD did not supports Hyper-V SR-IOV. https://docs.microsoft.com/en-us/windows-ser

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2021-03-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #50 from Dmitry --- One more notice - Intel 82576 LAN card capable of SR-IOV, i have activate this function in Win device properties, Hyper-V LAN card settings, and Guest machine settings. After guest Gen2 VM starts it shows

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2021-03-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #49 from Dmitry --- Just notice - there is issues with intel "igbX" LAN cards. In few days i will try Gen2 FreeBSD 12.2 "emX" LAN card PCIe passthrough and write results here. -- You are receiving this mail because: You are

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2021-03-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #48 from Dexuan Cui --- (In reply to Dmitry from comment #43) The screenshot shows "Setup of Shared code failed, error -2". Looks like somehow e1000_init_phy_params() returns -E1000_ERR_PHY. Since Ubuntu VM works, this should

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2021-03-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 Dmitry changed: What|Removed |Added Attachment #223208|FreeBSD 12.2|FreeBSD 12.2

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2021-03-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #47 from Dmitry --- Created attachment 223211 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223211=edit Hyper-V Gen1 PCIe Passthrough in FreeBSD 12.2-STABLE -- You are receiving this mail because:

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2021-03-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #46 from Dmitry --- Just forgot to write, in Gen1 FreeBSD 12.2-STABLE guest PCI Passhtrough generally works, but it's unable to map MSI-X table, it work by legacy MSI interrupts (with degraded performance and raised CPU usage).

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2021-03-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #45 from Dmitry --- Created attachment 223210 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223210=edit Ubuntu 20.04 passhrough on same Hyper-V Host and PICE LAN card -- You are receiving this mail because:

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2021-03-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #44 from Dmitry --- Created attachment 223209 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223209=edit WS2019 SurveyDDA -- You are receiving this mail because: You are the assignee for the bug.

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2021-03-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #43 from Dmitry --- Created attachment 223208 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223208=edit FreeBSD 12.2 IFDI_ATTACH_PRE failed 5 -- You are receiving this mail because: You are the assignee for the

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2021-03-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 Dmitry changed: What|Removed |Added Version|12.0-RELEASE|12.2-STABLE --- Comment #42 from Dmitry

[Bug 221074] Hyper V Gen 2 install has no mouse

2021-03-10 Thread bugzilla-noreply
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.

[Bug 221074] Hyper V Gen 2 install has no mouse

2021-03-10 Thread bugzilla-noreply
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 >

[Bug 221074] Hyper V Gen 2 install has no mouse

2021-03-10 Thread bugzilla-noreply
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

[Bug 221074] Hyper V Gen 2 install has no mouse

2021-03-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074 Vladimir Kondratyev changed: What|Removed |Added CC||w...@freebsd.org ---

[Bug 221074] Hyper V Gen 2 install has no mouse

2021-03-08 Thread bugzilla-noreply
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

[Bug 221074] Hyper V Gen 2 install has no mouse

2021-03-07 Thread bugzilla-noreply
Dwerva --- I thought I would load up BSD in a Hyper-v for old time sake. And then the horror on my face as I realized I could only use the keyboard. And then when I search for a workaround, I find this bug report and the fact that it has been so ignorantly brushed aside. I used to be an avid BSD

[Bug 229167] [Hyper-V] [Jun 19, 2018] Recently FreeBSD VM panics during boot-up, especially with Mellanox VF configured

2021-03-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229167 --- Comment #41 from Dexuan Cui --- (In reply to mammootty from comment #40) This sounds like a bug in the kernel function kern_kldload(): if it can't find a mounted root file system, it should return some error rather than panic. -- You

[Bug 229167] [Hyper-V] [Jun 19, 2018] Recently FreeBSD VM panics during boot-up, especially with Mellanox VF configured

2021-03-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229167 --- Comment #40 from mammootty --- Thanks Wei Hu, We have made mlxen4 module as part of the kernel and commented out the call to mlx4_request_modules() temporarily. However we are looking for any change in namei() or vrefact() to handle

[Bug 229167] [Hyper-V] [Jun 19, 2018] Recently FreeBSD VM panics during boot-up, especially with Mellanox VF configured

2021-03-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229167 --- Comment #39 from Wei Hu --- The cause of this problem is mlx4 driver was loaded before the root filesystem. On larger VM the odds of hitting this increase as more things are in parallel. Instead of adding 1 second delay in the

[Bug 229167] [Hyper-V] [Jun 19, 2018] Recently FreeBSD VM panics during boot-up, especially with Mellanox VF configured

2021-02-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229167 mammootty changed: What|Removed |Added CC||mammoot...@yahoo.com --- Comment #38

[Bug 195819] TSC calibration can hang FreeBSD in Hyper-V Generation 2 VM

2020-11-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195819 Li-Wen Hsu changed: What|Removed |Added Status|Open|Closed Resolution|---

[Bug 195819] TSC calibration can hang FreeBSD in Hyper-V Generation 2 VM

2020-11-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195819 --- Comment #29 from Dexuan Cui --- (In reply to Li-Wen Hsu from comment #28) Yes, I believe both the problems are fixed. I just created some Generation-2 32-CPU VMs on 2 different Hyper-V hosts (Build 17763, and 20195(internal build

[Bug 195819] TSC calibration can hang FreeBSD in Hyper-V Generation 2 VM

2020-11-05 Thread bugzilla-noreply
that 12.2-RELEASE and -CURRENT can boot in the Hyper-V Generation-2 VM? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd

[Bug 195819] TSC calibration can hang FreeBSD in Hyper-V Generation 2 VM

2020-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195819 --- Comment #27 from Dexuan Cui --- (In reply to Li-Wen Hsu from comment #26) I think we can close this bug, because I believe this bug was fixed in 2016 (please refer to Comment 24). This bug should not reproduce with 10.3+, 11.x, 12.x or

[Bug 195819] TSC calibration can hang FreeBSD in Hyper-V Generation 2 VM

2020-11-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195819 --- Comment #26 from Li-Wen Hsu --- Is this still happening in 12.x and, if it's possible to test with snapshot builds, 13.0-CURRENT? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 232472] Hyper-V Guest FreeBSD-current and Intel X540 SR-IOV pass-thru not working

2020-10-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232472 Wei Hu changed: What|Removed |Added CC||w...@microsoft.com --- Comment #4 from

[Bug 232472] Hyper-V Guest FreeBSD-current and Intel X540 SR-IOV pass-thru not working

2020-10-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232472 Li-Wen Hsu changed: What|Removed |Added CC||lw...@freebsd.org,

RE: FreeBSD 12.1 i386 on Hyper-V Fails to Mount Root

2020-10-16 Thread Wei Hu via freebsd-virtualization
> Howdy, > > Just started the upgrade process on some FreeBSD 11.4 VMs to FreeBSD 12.1 > using freebsd-update. VMs are running on multiple Hyper-V 2012 R2 and 2019 > systems, all systems with 2020-09 Cumulative Updates installed. > The amd64 VMs are upgrading happily.

FreeBSD 12.1 i386 on Hyper-V Fails to Mount Root

2020-10-15 Thread Chris Knight
Howdy, Just started the upgrade process on some FreeBSD 11.4 VMs to FreeBSD 12.1 using freebsd-update. VMs are running on multiple Hyper-V 2012 R2 and 2019 systems, all systems with 2020-09 Cumulative Updates installed. The amd64 VMs are upgrading happily. The i386 VMs die a horrible death

[Bug 229167] [Hyper-V] [Jun 19, 2018] Recently FreeBSD VM panics during boot-up, especially with Mellanox VF configured

2020-09-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229167 --- Comment #37 from Wei Hu --- I hit this bug on FreeBSD 12.1 image in Azure with Mellanox CX3 VF. Looks the root file system is not available at the time mlx4 driver is trying to load mlx4en kernel module. Adding one second sleep in

[Bug 248442] [Hyper-V] ng_vlan on hn interface not forwarding packets

2020-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248442 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|virtualizat...@freebsd.org -- You

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2020-07-30 Thread bugzilla-noreply
from being allocated to other devices on HyperV. On Gen2 VMs, Hyper-V provides mmio space for framebuffer. This mmio address range is not useable for other PCI devices. Currently only efifb driver is using this range without reserving it from system. Therefore, vmbus driver reserves

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2020-07-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #40 from Dexuan Cui --- (In reply to Wei Hu from comment #39) Great! -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2020-07-21 Thread bugzilla-noreply
|| --- Comment #39 from Wei Hu --- Created attachment 216621 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=216621=edit Patch to reservice mmio space for frame buffer on Gen2 Hyper-V Tested on Dmitry's VM, verified it is working. -- You are receiving this mail because:

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2020-07-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #38 from Dexuan Cui --- (In reply to Wei Hu from comment #36) "I am not sure whether the passthrough device comes before or after vmbus is loaded." --> the pass-through vmbus device comes after the vmbus driver is loaded,

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2020-07-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #37 from Dexuan Cui --- (In reply to Wei Hu from comment #36) It looks the EFI FB's MMIO base/size come from sys/dev/vt/hw/efifb/efifb.c: static int vt_efifb_init(struct vt_device *vd) { ... kmdp =

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2020-07-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #36 from Wei Hu --- (In reply to Dexuan Cui from comment #35) On Gen1, the system provided pcib driver grabs these mmio addresses way earlier than vmbus comes up. I then allocates the address to the vga driver: pcib0:

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2020-07-15 Thread bugzilla-noreply
a Gen-2 VM, or the synthetic Hyper-V graphics device, and we should make sure the MMIO range used by the Hyper-V PCIB driver doesn't conflict with the one used by the related graphics device driver. In Linux the MMIO range used by the graphics devices is reported by "screen_info.lfb_base" and "

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2020-07-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #34 from Wei Hu --- (In reply to Dexuan Cui from comment #33) It might be hard to tell which mmio space is bad for other PCI devices and how big the size it could be after user changes it according to the link. It could be

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2020-07-15 Thread bugzilla-noreply
et-VM -LowMemoryMappedIoSpace ..." (see https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/deploying-graphics-devices-using-dda). :-) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.o

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2020-07-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #32 from Wei Hu --- (In reply to Dmitry from comment #29) Dmitry, I just uploaded a proposed patch in Comment 31. If you can build a kernel on any of you test VMs, please verify if the NIC passthrough works on HyperV Gen2 VM

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2020-07-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #31 from Wei Hu --- Created attachment 216468 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=216468=edit Proposed patch to reserve io sapce 0xf800 - 0xf87f on HyperV This patch is for test. It reserves 8MB

[Bug 211136] [Hyper-V]mount root may fail because vfs' mount starts early than VMBUS

2020-07-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211136 Mark Linimon changed: What|Removed |Added Attachment #182594|file_211136.txt |vmbus.c.patch filename|

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2020-06-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #30 from Dexuan Cui --- (In reply to Dmitry from comment #29) Looks Wei made a good explanation of the issue in comment #17 earlier last year. @Wei, I guess FreeBSD can follow the way Linux handles the MMIO allocation for the

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2020-06-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #29 from Dmitry --- Almost 3 year passed, and problem still not resolved with Generation 2 Hyper-V and FreeBSD 11-12: https://bugs.freebsd.org/bugzilla/attachment.cgi?id=216006 https://bugs.freebsd.org/bugzilla/attachment.cgi

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2020-06-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #28 from Dmitry --- Created attachment 216007 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=216007=edit FreeBSD 12 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 222996] FreeBSD 11.1-12 on Hyper-V with PCI Express Pass Through

2020-06-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #27 from Dmitry --- Created attachment 216006 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=216006=edit FreeBSD 11.3 -- You are receiving this mail because: You are the assignee for the bug.

Re: [Bug 216493] [Hyper-V] Mellanox ConnectX-3 VF driver can't work when FreeBSD runs on Hyper-V 2016

2020-05-10 Thread datikan
به گزارش تدبیر، بنابر اعلام موسسه حقوقی داتیکان ، ارائه خدماتی همچون مشاوره حقوقی رایگان به صورت آنلاین تلفنی و حضوری، تفکیک تخصصی وکلا بر اساس پروندهها، ارائه و فروش اسناد حقوقی به منظور پاسخگویی به نیازهای روز جامعه، از

[Bug 236042] Windows Server 2016 Hyper-V snapshot triggers SCSI errors

2020-05-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236042 Juraj Lutter changed: What|Removed |Added CC||ju...@lutter.sk --- Comment #14

[Bug 236042] Windows Server 2016 Hyper-V snapshot triggers SCSI errors

2020-04-30 Thread bugzilla-noreply
error messages -- if we want to get rid of the messages, it looks sys/dev/hyperv/utilities/hv_snapshot.c is not an issue -- it looks we need to improve sys/dev/hyperv/storvsc/hv_storvsc_drv_freebsd.c and/or the other part of SCSI subsystem. Linux VM on Hyper-V shows the same/similar messages

[Bug 236042] Windows Server 2016 Hyper-V snapshot triggers SCSI errors

2020-04-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236042 meichthys changed: What|Removed |Added CC||mattbju2...@gmail.com --- Comment #12

[Bug 221074] Hyper V Gen 2 install has no mouse

2020-04-24 Thread bugzilla-noreply
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. ___

[Bug 221074] Hyper V Gen 2 install has no mouse

2020-04-24 Thread bugzilla-noreply
from Lars Engels --- It's sad to see that mouse integration is still not integrated with latest Hyper-V and FreeBSD 12.1. Maybe the "Microsoft <3 FreeBSD" slogan was meant not too serious. -- You are receiving this mail because: You are the assigne

Re: [Bug 216493] [Hyper-V] Mellanox ConnectX-3 VF driver can't work when FreeBSD runs on Hyper-V 2016

2020-02-02 Thread hamidvilla
خرید کاکتوس خرید انواع کاکتوس خرید گلهای اپارتمانی -- Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-virtualization-f5721547.html

[Bug 229990] FreeBSD 11.2 on Hyper-V: hn0: network changed, change 1

2019-12-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229990 --- Comment #3 from mwisnicki+free...@gmail.com --- Keeps happening with Windows 1909 and FreeBSD 12.1-R -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 229990] FreeBSD 11.2 on Hyper-V: hn0: network changed, change 1

2019-12-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229990 mwisnicki+free...@gmail.com changed: What|Removed |Added CC|

[Bug 240945] [hyper-v] [netvsc] hn network driver incorrectly detects baudrate

2019-12-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240945 Antoine Brodin changed: What|Removed |Added Flags|exp-run?| -- You are receiving this mail

[Bug 240945] [hyper-v] [netvsc] hn network driver incorrectly detects baudrate

2019-12-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240945 Nova_Logic changed: What|Removed |Added Flags|maintainer-feedback?|mfc-stable11?, |

  1   2   3   4   5   6   7   >