[Bug 212489] emulators/hyperv-is doesn't work on FreeBSD 10.3

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212489

--- Comment #14 from Dexuan Cui <decui at microsoft.com> ---
(In reply to Michael Faklis from comment #9)
Hi Michael,
So please let me summarize the issues:

1) The mouse doesn't work.
Actually it works, though there is small but annoying thing:  we must press
Control-Alt-LeftArraw to return the mouse back to the host and we have to click
into the VM window to give the mouse to the VM. This is a known issue, which
can be resolved by adding Hyper-V synthetic mouse driver. It's in our TODO.

2) DHCP can't work.
You're using "de0" (the Legacy Network Adapter) somehow.
When we create a Hyper-V VM, by default a Hyper-V Synthetic NIC (the "Network
Adapter" in the VM's "Settings")  is created for the VM. I guess you removed
the synthetic NIC and added a Legacy NIC somehow?

By default when we install FreeBSD 10.3 VM from the official .iso file, the
built-in BIS drivers support the Synthetic NIC well (the NIC name is "hn0") and
DHCP should work fine. 

If you do want use the legacy NIC ("de0")，please be noted there are known
issues:
a) the NIC can't work properly in SMP VM. It looks something is wrong here in
Hyper-V's IOAPIC emulation.
b) Even for UP VM, it looks adding 
ifconfig_de0="DHCP"
in /etc/rc.conf doesn't work reliably. If I replace the "DHCP" with "SYNCDHCP",
it looks the NIC can work, but I don't why.

Considering the poor performance and instability of "de0", we do recommend the
default synthetic NIC ("hn0") should be used.

3) VNC can't work?
In my 10.3 VM,  after I did "pkg install tightvnc" and ran "vncserver" to set
up a VNC password, my VNC-Viewer could connect to the VM without any issue. 

4) Xorg triggered VM panic/reboot?
Gnome3 works fine for me.
I'll try KDE4.

-- 
You are receiving this mail because:
You are the assignee for the bug.