https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254695
--- Comment #8 from Wei Hu <w...@microsoft.com> --- (In reply to Gordon Bergling from comment #7) I tried to reproduce in my test env without luck. I created two FreeBSD guests on same Windows Server 2019 host, one being the NFS server and the other the test client with latest commit. I tried two builds on the client: 1. a091c353235e0ee97d2531e80d9d64e1648350f4 on April 11 2. b6fd00791f2b9690b0a5d8670fc03f74eda96da2 on March 22 Build world and build kernel with NFS share all succeeded on the client. I may not have the right environment as you do. Here 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 irrelevant to this bug. - Both nfs server and client are running DEBUG build. - Both nfs server and client are Gen-1 VMs. It will be really helpful if you can bisect in your env. -- 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-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
