Re: Windows support in bhyve
Excerpts from Peter Grehan's message from Sun 04-Oct-15 13:11: > As of r288524, bhyve has preliminary support to run Windows in headless > mode using UEFI firmware. > > Since it's headless, the install process consists of modifying the > Windows install ISO to include an 'unattend' XML script that automates > the install, and also inserting the virtio network driver currently > required by bhyve. > > This has been tested with 64-bit Windows Server 2k12r2 and 2k16 tp3, and > Windows 10. The server versions are recommended since they have serial > console support, whereas the desktop install is a black-screen experience. > > ISO repack instructions at: > http://people.freebsd.org/~grehan/bhyve_uefi/windows_iso_repack.txt > > 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. > Another report: Windows 2012 works perfectly. FreeBSD 11-CURRENT on Thinkpad T430. Also I was able to pass through USB3 controller to Windows. Thinkpad has another USB2 controller which I kept with FreeBSD. Thanks! Sergey ___ 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"
Re: Windows support in bhyve
Excerpts from Trent Thompson's message from Mon 14-Dec-15 13:26: > Can you confirm Remote Desktop Services is running? > You can try something like `net start | more` to see services that are > running via CMD. It does: C:\Windows\system32>net start | more These Windows services are started: . Print Spooler Program Compatibility Assistant Service Remote Desktop Services Remote Procedure Call (RPC) RPC Endpoint Mapper Security Accounts Manager . The command completed successfully. C:\Windows\system32>sc query termservice SERVICE_NAME: termservice TYPE : 20 WIN32_SHARE_PROCESS STATE : 4 RUNNING (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN) WIN32_EXIT_CODE: 0 (0x0) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0 Thanks, Sergey ___ 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"
Re: Windows support in bhyve
Sergey, Can you confirm Remote Desktop Services is running? You can try something like `net start | more` to see services that are running via CMD. -Trent ___ 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"
Re: Windows support in bhyve
Excerpts from Allan Jude's message from Mon 14-Dec-15 14:26: > On 2015-12-14 11:43, Sergey Manucharian wrote: > > > > But rdesktop cannot connect: > > > > $ 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=0 ttl=128 time=0.314 ms > > > > $ rdesktop 192.168.4.5 > > ERROR: 192.168.4.5: unable to connect > > 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. I hope I've disabled it through the command line. The ping didn't go through before, then it does. I thought it could be also RDP protocol version (it's 8.0) problem, tried xfreerdp and a connection from another Win7 Windows computer - no luck... I've also disabled Network Layer autentication in Widnows Server. Don't know what else can cause that. Sergey ___ 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"
Re: Windows support in bhyve
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 headless >> mode using UEFI firmware. >> >> Since it's headless, the install process consists of modifying the >> Windows install ISO to include an 'unattend' XML script that automates >> the install, and also inserting the virtio network driver currently >> required by bhyve. >> >> This has been tested with 64-bit Windows Server 2k12r2 and 2k16 tp3, and >> Windows 10. The server versions are recommended since they have serial >> console support, whereas the desktop install is a black-screen experience. >> >> ISO repack instructions at: >> http://people.freebsd.org/~grehan/bhyve_uefi/windows_iso_repack.txt >> >> 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. >> > > That's really cool! Thanks for the instructions! > > I've installed Windows Server 2016 with no issues on a ZFS volume. Works > fine. I can get the command prompt, set up IP address and so on. > > However I cannot get Remote Desktop connection working. I tried to > (re)enable it from the command line: > > 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. > > C:\Windows\system32>reg add > "hklm\system\currentControlSet\Control\Terminal Server" /v > "AllowTSConnections" /t REG_DWORD /d 1 /f > The operation completed successfully. > > C:\Windows\system32>net start Termservice > The Remote Desktop Services service is starting. > > The Remote Desktop Services service was started successfully. > > C:\Windows\system32>ipconfig > Windows IP Configuration > > Ethernet adapter Ethernet: > > >Connection-specific DNS Suffix . : >Link-local IPv6 Address . . . . . : fe80::2cb4:3a4d:dff5:9f0c%3 > >IPv4 Address. . . . . . . . . . . : 192.168.4.5 > >Subnet Mask . . . . . . . . . . . : 255.255.255.0 > >Default Gateway . . . . . . . . . : 192.168.4.1 > > But rdesktop cannot connect: > > $ 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=0 ttl=128 time=0.314 ms > > $ rdesktop 192.168.4.5 > ERROR: 192.168.4.5: unable to connect > > Any ideas? > > Thanks, > Sergey > > ___ > 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" > 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. -- Allan Jude signature.asc Description: OpenPGP digital signature
Re: Windows support in bhyve
Excerpts from Peter Grehan's message from Sun 04-Oct-15 13:11: > As of r288524, bhyve has preliminary support to run Windows in headless > mode using UEFI firmware. > > Since it's headless, the install process consists of modifying the > Windows install ISO to include an 'unattend' XML script that automates > the install, and also inserting the virtio network driver currently > required by bhyve. > > This has been tested with 64-bit Windows Server 2k12r2 and 2k16 tp3, and > Windows 10. The server versions are recommended since they have serial > console support, whereas the desktop install is a black-screen experience. > > ISO repack instructions at: > http://people.freebsd.org/~grehan/bhyve_uefi/windows_iso_repack.txt > > 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. > That's really cool! Thanks for the instructions! I've installed Windows Server 2016 with no issues on a ZFS volume. Works fine. I can get the command prompt, set up IP address and so on. However I cannot get Remote Desktop connection working. I tried to (re)enable it from the command line: 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. C:\Windows\system32>reg add "hklm\system\currentControlSet\Control\Terminal Server" /v "AllowTSConnections" /t REG_DWORD /d 1 /f The operation completed successfully. C:\Windows\system32>net start Termservice The Remote Desktop Services service is starting. The Remote Desktop Services service was started successfully. C:\Windows\system32>ipconfig Windows IP Configuration Ethernet adapter Ethernet: Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . : fe80::2cb4:3a4d:dff5:9f0c%3 IPv4 Address. . . . . . . . . . . : 192.168.4.5 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.4.1 But rdesktop cannot connect: $ 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=0 ttl=128 time=0.314 ms $ rdesktop 192.168.4.5 ERROR: 192.168.4.5: unable to connect Any ideas? Thanks, Sergey ___ 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"
Re: Windows support in bhyve
Hi Nils, Using your instructions to install Win Server 2012r2, installation works, but it is slow as bread. I know exactly what this is - a change was lost in the final merge. I'll get a new UEFI image/diff together today. later, Peter. ___ 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"
Re: Windows support in bhyve
Hi Peter,
Peter Grehan wrote:
> As of r288524, bhyve has preliminary support to run Windows in headless
> mode using UEFI firmware.
> [...]
> Please give this a try and report back on how it goes.
trying it on a:
AMD Phenom(tm) II X6 1055T Processor
and
FreeBSD 11.0-CURRENT #0 r289027M
with debugging disabled.
Using your instructions to install Win Server 2012r2, installation works, but
it is slow as bread.
"bhyve" itself spits out:
wrmsr to register 0xc0010020(0xf80379e79000) on vcpu 0
rdmsr to register 0xc0010114 on vcpu 0
wrmsr to register 0xc0010020(0xf8095000) on vcpu 1
rdmsr to register 0xc0010114 on vcpu 1
wrmsr to register 0x10(0) on vcpu 1
wrmsr to register 0x10(0x8f722eb4c529) on vcpu 1
wrmsr to register 0x10(0x8f722eb4c529) on vcpu 0
The processes "bhyve{vcpu 0}" and "bhyve{vcpu 1}" run at 100% CPU nearly all
the time. After the three-phase installation - that succeeds - serial console
(like CMD) is slow as well. "rdesktop" works, but is barely usable due to its
slownesss.
So, something on AMD is still not quite right.
Nevertheless, many thanks and big kudos to you guys for improving "bhyve" this
far...
Regards,
Nils
___
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"
Re: Windows support in bhyve
Hi Craig, Microsoft provides free virtual machines here: https://dev.modern.ie/tools/vms/windows/ These VM's are primarily targeted at web developers, for testing Internet Explorer. Can these VM's be made to work with bhyve? For example, by using VirtualBox to export a VM to a raw disk image. Not at the moment. They are for desktop versions only, and are most likely configured for hardware that bhyve doesn't support i.e. no virtio-net driver. later, Peter. ___ 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"
Re: Windows support in bhyve
On Sun, Oct 4, 2015 at 1:11 PM, Peter Grehan wrote: > ISO repack instructions at: > http://people.freebsd.org/~grehan/bhyve_uefi/windows_iso_repack.txt > > Install/run instructions at: > http://people.freebsd.org/~grehan/bhyve_uefi/windows_install.txt > > Microsoft provides free virtual machines here: https://dev.modern.ie/tools/vms/windows/ These VM's are primarily targeted at web developers, for testing Internet Explorer. Can these VM's be made to work with bhyve? For example, by using VirtualBox to export a VM to a raw disk image. -- Craig ___ 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"
Windows support in bhyve
As of r288524, bhyve has preliminary support to run Windows in headless mode using UEFI firmware. Since it's headless, the install process consists of modifying the Windows install ISO to include an 'unattend' XML script that automates the install, and also inserting the virtio network driver currently required by bhyve. This has been tested with 64-bit Windows Server 2k12r2 and 2k16 tp3, and Windows 10. The server versions are recommended since they have serial console support, whereas the desktop install is a black-screen experience. ISO repack instructions at: http://people.freebsd.org/~grehan/bhyve_uefi/windows_iso_repack.txt 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. A big thanks to Leon Dang from Nahanni Systems who contributed the majority of Windows support; Tycho Nightingale from Pluribus Networks who did the intial UEFI work, and Ben Perrault who helped out enormously with test and debug. later, Peter. (Win 7/8 and 2k8r2 have some problems that appeared in the final merge of this work - it's being looked into). ___ 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"
