[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 #16 from Michael Faklis <MFaklis at ACM.org> ---
(In reply to Dexuan Cui from comment #14)

2) DHCP can't work.

When I was studying documents for using the BIS for Linux and FreeBSD, I
thought I read that I should use the legacy network NIC.  That was obviusly
wrong for FreeBSD or I was mistaken.  I revised rc.conf references from de0 to
hn0, shutdown, revised the Hyper-V client settings to use the synthetic NIC,
and started it back up.  Upon the first boot, the hn0 NIC was disabled, so I
re-enabled it. It now comes up with DHCP giving hn0 an IP address.  By the way,
I had revised rc.conf from DHCP to SYNCDHCP when I first encountered de0 not
having an IP address.  Thank you.

4) Xorg triggered VM panic/reboot?

I have found if I do not "connect" to the FreeBSD hyper-v client when I start
it from the hyper-v manager, it starts up the X login screen without problems. 
I can then connect to the hyper-v client and log into KDE (in my case). 
However, it I switch to another virtual terminal (text mode), X comes up
showing garbage and forcing the panic/reboot three times to get to a clean X
logon screen.

I wonder if I screwed up with xorg.conf?  I reading that the xorg.conf.d
directory is the current preferred definition over xorg.conf.  Not seeing how
this was done, I looked at a linux virtual machine and saw how it constructed
the xorg.conf.d, so I took my xorg.conf, broke it up by section and placed each
in a text file in xorg.conf.d.  Can you show me how xorg.conf should be defined
for running FreeBSD 10.3 as a hyper-V client?

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