Date: Mon, 14 Dec 2015 18:07:11 +0100 From: "G. Amanakis" <g_amanakis@yahoo.com> To: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: BAR and pci passthrough Message-ID: <43363997-6304-4BA3-BCCB-90FA62E00EE6@yahoo.com> In-Reply-To: <D887B227-2518-47E8-AD70-E18C9FBF0838@yahoo.com> References: <4F251D2F-8C0C-46FF-B5E1-D88DE84904D8@yahoo.com> <CAFgRE9H0_h1Dxzjn19n6Tjc9Nt8Ze6ugWnKQiZGRV363Q1z22g@mail.gmail.com> <D887B227-2518-47E8-AD70-E18C9FBF0838@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On December 14, 2015 1:34:16 PM GMT+01:00, Bendany Qian <bendany@larka=2Ejp= > wrote: Hello G=2E Amanakis I also faced your problem=2E and I try your solution, now it can pass to VM=2E but it cannot work properly=2E Linux guest's dmesg say cannot start device=2E what is your situcation? success? Best Regards=2E Qian I can also pass it through but the linux-vm cannot request the IRQ of the = device, in my case it is an onboard USB controller which shares an IRQ with= the onboard graphics card on an X9SCM=2E What is your device? --=20 Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E From owner-freebsd-virtualization@freebsd.org Mon Dec 14 19:26:53 2015 Return-Path: <owner-freebsd-virtualization@freebsd.org> Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A87E9A430DD for <freebsd-virtualization@mailman.ysv.freebsd.org>; Mon, 14 Dec 2015 19:26:53 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) by mx1.freebsd.org (Postfix) with ESMTP id 8AAF510A8 for <freebsd-virtualization@freebsd.org>; Mon, 14 Dec 2015 19:26:53 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id E22E4D411 for <freebsd-virtualization@freebsd.org>; Mon, 14 Dec 2015 19:26:46 +0000 (UTC) Subject: Re: Windows support in bhyve To: freebsd-virtualization@freebsd.org References: <561187FB.8040506@freebsd.org> <20151214164309.GB5410@debian.ara-ler.com> From: Allan Jude <allanjude@freebsd.org> Message-ID: <566F17EE.6010408@freebsd.org> Date: Mon, 14 Dec 2015 14:26:38 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <20151214164309.GB5410@debian.ara-ler.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="b6S8SnrDNQb7x9DGRLAQ7iAitJ6eTQiU1" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." <freebsd-virtualization.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-virtualization>, <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>; List-Post: <mailto:freebsd-virtualization@freebsd.org> List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 14 Dec 2015 19:26:53 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --b6S8SnrDNQb7x9DGRLAQ7iAitJ6eTQiU1 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2015-12-14 11:43, Sergey Manucharian wrote: > Excerpts from Peter Grehan's message from Sun 04-Oct-15 13:11: >> As of r288524, bhyve has preliminary support to run Windows in headles= s=20 >> mode using UEFI firmware. >> >> Since it's headless, the install process consists of modifying the=20 >> Windows install ISO to include an 'unattend' XML script that automates= =20 >> the install, and also inserting the virtio network driver currently=20 >> required by bhyve. >> >> This has been tested with 64-bit Windows Server 2k12r2 and 2k16 tp3, a= nd=20 >> Windows 10. The server versions are recommended since they have serial= =20 >> console support, whereas the desktop install is a black-screen experie= nce. >> >> ISO repack instructions at: >> http://people.freebsd.org/~grehan/bhyve_uefi/windows_iso_repack.t= xt >> >> Install/run instructions at: >> http://people.freebsd.org/~grehan/bhyve_uefi/windows_install.txt >> >> Please give this a try and report back on how it goes. >> >=20 > That's really cool! Thanks for the instructions! >=20 > I've installed Windows Server 2016 with no issues on a ZFS volume. Work= s > fine. I can get the command prompt, set up IP address and so on. >=20 > However I cannot get Remote Desktop connection working. I tried to > (re)enable it from the command line: >=20 > C:\Windows\system32>reg add > "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server" = /v fDenyTSConnections /t REG_DWORD /d 0 /f > The operation completed successfully. > =20 > C:\Windows\system32>reg add > "hklm\system\currentControlSet\Control\Terminal Server" /v "AllowTSCon= nections" /t REG_DWORD /d 1 /f =20 > The operation completed successfully. =20 >=20 > C:\Windows\system32>net start Termservice = =20 > The Remote Desktop Services service is starting. = =20 > The Remote Desktop Services service was started successfully. >=20 > C:\Windows\system32>ipconfig =20 > Windows IP Configuration >=20 > Ethernet adapter Ethernet: = =20 > =20 > Connection-specific DNS Suffix . : > Link-local IPv6 Address . . . . . : fe80::2cb4:3a4d:dff5:9f0c%3 = =20 > IPv4 Address. . . . . . . . . . . : 192.168.4.5 = =20 > Subnet Mask . . . . . . . . . . . : 255.255.255.0 = =20 > Default Gateway . . . . . . . . . : 192.168.4.1 >=20 > But rdesktop cannot connect: >=20 > $ ping 192.168.4.5 > PING 192.168.4.5 (192.168.4.5): 56 data bytes > 64 bytes from 192.168.4.5: icmp_seq=3D0 ttl=3D128 time=3D0.314 ms >=20 > $ rdesktop 192.168.4.5 > ERROR: 192.168.4.5: unable to connect >=20 > Any ideas? >=20 > Thanks, > Sergey >=20 > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@fr= eebsd.org" >=20 You likely have to allow it through the windows firewall. Last time I had to do this from a command prompt, i used netcmd or something, I don't recall now, it was 7 or 8 years ago. --=20 Allan Jude --b6S8SnrDNQb7x9DGRLAQ7iAitJ6eTQiU1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJWbxf6AAoJEBmVNT4SmAt+q8QQAJpOlz1tm1A3rVuRN/Zdqkd4 hqWPkBHb9hSJISGSmZGY8/iN/uOhRRRppUcqyO6PJNFRSuIu7Psu70/B3UaIUboT 3G/1eeXDNSi4j62M1MtxpuSGVHY8crhidntmZ+QyNZ42oRiHXkv2ObFBu/W21M/V rP9sy3jZpivu8P+v7NQzDjkErAifclhPkRf8wBNVQrjnpRWEmE8Zo2b7Vmdh9cmF LBzFVouv+nsEPG9yRhmbWsEChR3GZqynHSXCO9hLHmO0f3JBsVupXqY3KkM+Wljs +5uYLITGB82iTGQe5BYyQxZrzmXkHlJCEWU2Nf+HTIoY2j7WvMChGJsc9nXzy6FG kJJeCSlsBkCzhtNtyT9Js5vJvP6/jZ/cuvy/6OaM3EjKDH+QUrdo3Evc53otQY7s 0wTWQJjKUpP975mKaZruoAGaT44bFuUTyvjzpnNYH0hzLzCB0kyG6H1+sRO6ZYmG 57Zir5ZlV1hg27Mx75pym65b0FdqURBxnrTiWWHOsXwgRT3kGra4DR3e4tpga3Xg UUilnAyDV2aBB25KmrkdNhnwJUsSrlATRV+7neQBsAwRaZxJ5Lawn3ixErDKIFNU n6cQbOQVLsodXLXxq8ALtHLKxErAH+VSeYOFnOW55kiFiV6UFXuhfFwClpUlVyek 0WRFT9J+iq4PL+xraC78 =Vb2P -----END PGP SIGNATURE----- --b6S8SnrDNQb7x9DGRLAQ7iAitJ6eTQiU1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43363997-6304-4BA3-BCCB-90FA62E00EE6>