Re: Windows 2016 Server
-- Randy On Tue, Oct 25, 2016 at 9:38 AM, Dave Shariff Yadallee - System Administrator a.k.a. The Root of the Problem wrote: > On Tue, Oct 25, 2016 at 08:33:47AM -0600, Randy Terbush wrote: > > On Tue, Oct 25, 2016 at 7:58 AM, The Doctor > > wrote: > > > > > On Tue, Oct 25, 2016 at 09:20:28AM +, Matt Churchyard wrote: > > > > > > > One other issue is that Windows doesn't support the virtio-net > network > > > device by default. The easiest way to get this working is to boot the > > > guest with the virtio driver ISO attached instead of the Windows > install > > > disk (once Windows is installed and working). You can then install the > > > driver for the network interface from the CD using the VNC console. > > > > > > > > Depending on what you are doing you may find it easier to use > something > > > like iohyve/chyves/vm-bhyve/vmrc that handles all the raw bhyve > commands > > > for you. > > > > > > > > Matt > > > > > > I will look into the iohyve , saw that last night. > > > > > > Does this also apply to UEFU BSDs / Linuxes ? > > > > > > > ???Just to chime in quickly on this thread... I am a big fan of > vm-bhyve. It > > has made it much easier to sort bhyve out in general and get through some > > of these new options for supported guests. > > > > Regarding Linux and UEFI, much of this also applies there. I've > > successfully installed a LinuxMint guest. I will offer that after the > > install, the boot process hung at the EFI. After exiting from the Shell> > > prompt that eventually appears, it is possible to navigate the UEFI bios > > settings to pick a bootable device. Only after rerunning 'grub2-install' > > was I able to have a Linux guest that would boot without fiddling. > > ??? > Let me give you my setup. > > No Zpool here. > > I am running FreeBSD 11 UEFI on x86_64. > > I have set up some non-UEFI guest successfull , > > Fedora, Centos and Ubuntu. > > If it the UEFI part using a non-zpool environment > > that I am trying to wrap my head around. > > Smilir to Windows, I did install Fedora using > UEFI but then > could not go to the > second stage, i.e. booting into the VM. > > Hence I do need to understand how to this with my environment using > purely bhyve. As mentioned, I'm using vm-bhyve to insulating me from the learning curve of "pure bhyve". https://github.com/churchers/vm-bhyve A few more details about my setup. FreeBSD 11-stable (reguired for vnc graphics to work with UEFI guests) Relevant installed packages: vm-bhyve bhyve-firmware grub2-bhyve uefi-edk2-bhyve uefi-edk2-bhyve-csm While vm-bhyve is running in a zpool, the guests are using disk image files. The following template allowed me to install LinuxMint through graphic VNC interface. guest="linux" uefi="yes" cpu=1 memory=2G graphics="yes" graphics_res="1600x1200" graphics_wait="yes" xhci_mouse="yes" network0_type="virtio-net" network0_switch="public" disk0_type="virtio-blk" disk0_name="disk0.img" grub_run_partition="1" vm create -t mint -s 30G mint vm install mint linuxmint-18-cinnamon-64bit.iso (32bit would not install as a UEFI guest) vm list (shows running bhyve guests and indicates the IP and port that VNC is running on for this guest) vncviewer 127.0.0.1:5900 Top-level listing of the vm zpool shows the layout which includes a .template and .iso directory to collect your configs and install isos. Nice clean setup. [root: /vm]# ls -l total 171 drwxr-xr-x 2 root wheel 5 Jul 20 10:01 .config drwxr-xr-x 2 root wheel 10 Oct 24 12:10 .iso drwxr-xr-x 2 root wheel 17 Oct 24 11:56 .templates drwxr-xr-x 2 root wheel 8 Oct 3 21:41 kali drwxr-xr-x 2 root wheel 6 Oct 2 18:13 macos drwxr-xr-x 2 root wheel 8 Oct 25 05:37 mint drwxr-xr-x 2 root wheel 7 Oct 22 15:31 win2012 drwxr-xr-x 2 root wheel 5 Oct 10 16:58 winapp (NOTE: still trying to get a working MacOS guest running...) ___ 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 2016 Server
On Tue, Oct 25, 2016 at 08:33:47AM -0600, Randy Terbush wrote: > On Tue, Oct 25, 2016 at 7:58 AM, The Doctor > wrote: > > > On Tue, Oct 25, 2016 at 09:20:28AM +, Matt Churchyard wrote: > > > > > One other issue is that Windows doesn't support the virtio-net network > > device by default. The easiest way to get this working is to boot the > > guest with the virtio driver ISO attached instead of the Windows install > > disk (once Windows is installed and working). You can then install the > > driver for the network interface from the CD using the VNC console. > > > > > > Depending on what you are doing you may find it easier to use something > > like iohyve/chyves/vm-bhyve/vmrc that handles all the raw bhyve commands > > for you. > > > > > > Matt > > > > I will look into the iohyve , saw that last night. > > > > Does this also apply to UEFU BSDs / Linuxes ? > > > > ???Just to chime in quickly on this thread... I am a big fan of vm-bhyve. It > has made it much easier to sort bhyve out in general and get through some > of these new options for supported guests. > > Regarding Linux and UEFI, much of this also applies there. I've > successfully installed a LinuxMint guest. I will offer that after the > install, the boot process hung at the EFI. After exiting from the Shell> > prompt that eventually appears, it is possible to navigate the UEFI bios > settings to pick a bootable device. Only after rerunning 'grub2-install' > was I able to have a Linux guest that would boot without fiddling. > ??? Let me give you my setup. No Zpool here. I am running FreeBSD 11 UEFI on x86_64. I have set up some non-UEFI guest successfull , Fedora, Centos and Ubuntu. If it the UEFI part using a non-zpool environment that I am trying to wrap my head around. Smilir to Windows, I did install Fedora using UEFI but then could not go to the second stage, i.e. booting into the VM. Hence I do need to understand how to this with my environment using purely bhyve. -- For effective Internet Etiquette and communications read http://catb.org/jargon/html/T/top-post.html, http://idallen.com/topposting.html & http://www.caliburn.nl/topposting.html ___ 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 2016 Server
On Tue, Oct 25, 2016 at 7:58 AM, The Doctor wrote: > On Tue, Oct 25, 2016 at 09:20:28AM +, Matt Churchyard wrote: > > > One other issue is that Windows doesn't support the virtio-net network > device by default. The easiest way to get this working is to boot the > guest with the virtio driver ISO attached instead of the Windows install > disk (once Windows is installed and working). You can then install the > driver for the network interface from the CD using the VNC console. > > > > Depending on what you are doing you may find it easier to use something > like iohyve/chyves/vm-bhyve/vmrc that handles all the raw bhyve commands > for you. > > > > Matt > > I will look into the iohyve , saw that last night. > > Does this also apply to UEFU BSDs / Linuxes ? > Just to chime in quickly on this thread... I am a big fan of vm-bhyve. It has made it much easier to sort bhyve out in general and get through some of these new options for supported guests. Regarding Linux and UEFI, much of this also applies there. I've successfully installed a LinuxMint guest. I will offer that after the install, the boot process hung at the EFI. After exiting from the Shell> prompt that eventually appears, it is possible to navigate the UEFI bios settings to pick a bootable device. Only after rerunning 'grub2-install' was I able to have a Linux guest that would boot without fiddling. ___ 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 2016 Server
On Tue, Oct 25, 2016 at 09:20:28AM +, Matt Churchyard wrote: > >On Mon, Oct 24, 2016 at 08:07:13AM +, Matt Churchyard wrote: > > On Fri, Oct 21, 2016 at 03:21:10PM -0700, Peter Grehan wrote: > > > >> [Windows could not parse or process unattend answer file > > > >> [D:\autounattend.xml] for pass [windowsPE]. The answer file is > > > >> invalid.] > > > > > > > > Something is wrong with your autounattend.xml file. > > > > > > Still working on the 2k16 unattend file. Unfortunately things have > > > changed from TP5 in a non-obvious way :( > > > > > > A workaround is to do a GUI install. > > > > > > later, > > > > > > Peter. > > > > > Please explain what you mean by a GUI install. > > > > Not sure if anyone's replied directly to you - > > > > 1) Make sure you are running at least 11-RELEASE > > > > 2) Use an "off-the-shelf" Windows install CD > > > > 3) Add the following to your bhyve command > > > > -s 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait > > -s 30,xhci,tablet > > > > 4) Run bhyve and then use a VNC client to connect and install using > > the normal Windows GUI > > > > >Well all right did follow https://wiki.freebsd.org/bhyve/UEFI > > > >My next question is after the initial install is done, how do I followup on > >the next step , i.e. to see if the VM is booting. > > As long as you have the fbuf device specified you can connect to the IP > address of the bhyve host using VNC to view the "physical" guest console and > watch it boot. Usually with Windows you'd then use the VNC console to log in > and set up permanent RDP access. > > One other issue is that Windows doesn't support the virtio-net network device > by default. The easiest way to get this working is to boot the guest with > the virtio driver ISO attached instead of the Windows install disk (once > Windows is installed and working). You can then install the driver for the > network interface from the CD using the VNC console. > > Depending on what you are doing you may find it easier to use something like > iohyve/chyves/vm-bhyve/vmrc that handles all the raw bhyve commands for you. > > Matt I will look into the iohyve , saw that last night. Does this also apply to UEFU BSDs / Linuxes ? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Time for the USA to hold a referendum on its republic and vote to dissolve!! ___ 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 2016 Server
>On Mon, Oct 24, 2016 at 08:07:13AM +, Matt Churchyard wrote: > On Fri, Oct 21, 2016 at 03:21:10PM -0700, Peter Grehan wrote: > > >> [Windows could not parse or process unattend answer file > > >> [D:\autounattend.xml] for pass [windowsPE]. The answer file is > > >> invalid.] > > > > > > Something is wrong with your autounattend.xml file. > > > > Still working on the 2k16 unattend file. Unfortunately things have > > changed from TP5 in a non-obvious way :( > > > > A workaround is to do a GUI install. > > > > later, > > > > Peter. > > > Please explain what you mean by a GUI install. > > Not sure if anyone's replied directly to you - > > 1) Make sure you are running at least 11-RELEASE > > 2) Use an "off-the-shelf" Windows install CD > > 3) Add the following to your bhyve command > > -s 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait > -s 30,xhci,tablet > > 4) Run bhyve and then use a VNC client to connect and install using > the normal Windows GUI > >Well all right did follow https://wiki.freebsd.org/bhyve/UEFI >My next question is after the initial install is done, how do I followup on >the next step , i.e. to see if the VM is booting. As long as you have the fbuf device specified you can connect to the IP address of the bhyve host using VNC to view the "physical" guest console and watch it boot. Usually with Windows you'd then use the VNC console to log in and set up permanent RDP access. One other issue is that Windows doesn't support the virtio-net network device by default. The easiest way to get this working is to boot the guest with the virtio driver ISO attached instead of the Windows install disk (once Windows is installed and working). You can then install the driver for the network interface from the CD using the VNC console. Depending on what you are doing you may find it easier to use something like iohyve/chyves/vm-bhyve/vmrc that handles all the raw bhyve commands for you. Matt ___ 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 2016 Server
On Mon, Oct 24, 2016 at 08:07:13AM +, Matt Churchyard wrote: > On Fri, Oct 21, 2016 at 03:21:10PM -0700, Peter Grehan wrote: > > >> [Windows could not parse or process unattend answer file > > >> [D:\autounattend.xml] for pass [windowsPE]. The answer file is > > >> invalid.] > > > > > > Something is wrong with your autounattend.xml file. > > > > Still working on the 2k16 unattend file. Unfortunately things have > > changed from TP5 in a non-obvious way :( > > > > A workaround is to do a GUI install. > > > > later, > > > > Peter. > > > Please explain what you mean by a GUI install. > > Not sure if anyone's replied directly to you - > > 1) Make sure you are running at least 11-RELEASE > > 2) Use an "off-the-shelf" Windows install CD > > 3) Add the following to your bhyve command > > -s 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait > -s 30,xhci,tablet > > 4) Run bhyve and then use a VNC client to connect and install using the > normal Windows GUI > Well all right did follow https://wiki.freebsd.org/bhyve/UEFI My next question is after the initial install is done, how do I followup on the next step , i.e. to see if the VM is booting. > Matt -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Time for the USA to hold a referendum on its republic and vote to dissolve!! ___ 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 2016 Server
On Fri, Oct 21, 2016 at 03:21:10PM -0700, Peter Grehan wrote: > >> [Windows could not parse or process unattend answer file > >> [D:\autounattend.xml] for pass [windowsPE]. The answer file is > >> invalid.] > > > > Something is wrong with your autounattend.xml file. > > Still working on the 2k16 unattend file. Unfortunately things have > changed from TP5 in a non-obvious way :( > > A workaround is to do a GUI install. > > later, > > Peter. > Please explain what you mean by a GUI install. Not sure if anyone's replied directly to you - 1) Make sure you are running at least 11-RELEASE 2) Use an "off-the-shelf" Windows install CD 3) Add the following to your bhyve command -s 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait -s 30,xhci,tablet 4) Run bhyve and then use a VNC client to connect and install using the normal Windows GUI Matt ___ 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 2016 Server
On Fri, Oct 21, 2016 at 03:21:10PM -0700, Peter Grehan wrote: > >> [Windows could not parse or process unattend answer file > >> [D:\autounattend.xml] for pass [windowsPE]. The answer file is > >> invalid.] > > > > Something is wrong with your autounattend.xml file. > > Still working on the 2k16 unattend file. Unfortunately things have > changed from TP5 in a non-obvious way :( > > A workaround is to do a GUI install. > > later, > > Peter. Please explain what you mean by a GUI install. -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Time for the USA to hold a referendum on its republic and vote to dissolve!! ___ 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 2016 Server
[Windows could not parse or process unattend answer file [D:\autounattend.xml] for pass [windowsPE]. The answer file is invalid.] Something is wrong with your autounattend.xml file. Still working on the 2k16 unattend file. Unfortunately things have changed from TP5 in a non-obvious way :( A workaround is to do a GUI install. 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 2016 Server
On Fri, 21 Oct 2016, The Doctor wrote: > What went wrong? Windows: > [Windows could not parse or process unattend answer file > [D:\autounattend.xml] for pass [windowsPE]. The answer file is invalid.] Something is wrong with your autounattend.xml file. Marcin ___ 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 2016 Server
On Fri, Oct 21, 2016 at 12:31:20PM -0600, The Doctor wrote: > Does anyone have Windows 2016 Server Release 1 working on thier sysem. > > After following https://wiki.freebsd.org/bhyve/Windows > > I run > > /usr/sbin/bhyve -c 2 -s 0,hostbridge -s 3,ahci-hd,./windows2016.img -s > 4,ahci-cd,./.iso/win2k16install.iso -s 10,virtio-net,tap15 -s 31,lpc -l > com1,/dev/nmdm15A -l com2,/dev/nmdm16A -l > bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -m 2G -H -w > windows2016guest > > I can cu -l into /dev/nmdm15B I see SAC > > but cannot seem to go further. > > Help. Further in one of the Windows, I see = 0x0, hrValidated = 0x1, hrResult = 0x80220005 2016-10-21 12:58:10, Info IBSUnattendErrorFromResults: Hit an unattend error; dumping any info we have about the failure... 2016-10-21 12:58:10, Info IBSUnattendDumpSetting: --Un attend setting error / warning-- 2016-10-21 12:58:10, Info IBSUnattendDumpSetting: Error co de = 0x80220005 2016-10-21 12:58:10, Info IBSUnattendDumpSetting: Pass = w indowsPE 2016-10-21 12:58:10, Info IBSUnattendDumpSetting: 2016-10-21 12:58:10, Info IBSUnattendErrorFromResults: Err or text = Windows could not parse or process unattend answer file [D:\autounatt end.xml] for pass [windowsPE]. The answer file is invalid. 2016-10-21 12:58:10, Error [0x0600c2] IBSCallback_Unattend_InitEngine: An error occurred while finding/loading the unattend file; hr = 0x1, hrResult = 0x80220005[gle=0x0490] 2016-10-21 12:58:10, Info IBSLIB PublishCriticalError: Publish ing blocked message [Windows could not parse or process unattend answer file [D :\autounattend.xml] for pass [windowsPE]. The answer file is invalid.] 2016-10-21 12:58:10, Info This installation is blocked from completing due to compliance failures or invalid input; this is not an int ernal error. What went wrong? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Time for the USA to hold a referendum on its republic and vote to dissolve!! ___ 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"
