Date: Sun, 11 Sep 2016 18:59:35 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 212489] emulators/hyperv-is doesn't work on FreeBSD 10.3 Message-ID: <bug-212489-13-3fLTH5nCSP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-212489-13@https.bugs.freebsd.org/bugzilla/> References: <bug-212489-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212489 --- Comment #7 from Michael Faklis <MFaklis@ACM.org> --- (In reply to Hongjiang from comment #1) C:\Users\MFaklis.EvolSwSys>systeminfo | findstr os Host Name: WIN10P64HV OS Name: Microsoft Windows 10 Pro OS Manufacturer: Microsoft Corporation Connection Name: Ethernet for Host Mouse: From the Hyper-V Manager on the Hyper-V host, doing a "connect", so local. The mouse works if you click into the client windows, but I must do= a CNTL-ALT-leftarrow to release the mouse back to the host session. DHCP: No wireless NIC on the Hyper-V client or host. Question about dmesg: dmesg is the log from the boot which works. The logs from the boots where X resync causes a reboot are not in dmesg. If you tel= l me how to capture those logs so they are preserved after the reboot, I will do that. If you really want the dmesg from the reboot which works, let me know and I will do that. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-212489-13-3fLTH5nCSP>