Date: Tue, 1 Nov 2016 11:45:55 -0600 From: Randy Terbush <randy@terbush.org> To: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: Windows 2016 Message-ID: <CALmWkDYrgSg9v2C02gXAr8QzgmfJ1sMFENJTjgxgsQ9qKvUQTg@mail.gmail.com> In-Reply-To: <CALmWkDY6cEbH%2B8mQ7dNH02_1XxZ-K3E5%2BRJSYZtsRdmKahf9JA@mail.gmail.com> References: <20161101044503.GA58756@doctor.nl2k.ab.ca> <ec0716c52aeb4ea18d09b193ac61b493@SERVER.ad.usd-group.com> <20161101140249.GB27402@doctor.nl2k.ab.ca> <1478009772.19546.74.camel@fastmail.fm> <20161101142257.GF27402@doctor.nl2k.ab.ca> <cd71fc6fd0cb43a9adaa33c37cb95386@SERVER.ad.usd-group.com> <CALmWkDZJX-SN1EAp-buA3dgUX%2Bo8X7ZOt16qY4e8OaUaW4=4rQ@mail.gmail.com> <c5adf717ccca43d0a57757f4ca9003ea@SERVER.ad.usd-group.com> <CALmWkDY6cEbH%2B8mQ7dNH02_1XxZ-K3E5%2BRJSYZtsRdmKahf9JA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 1, 2016 at 11:24 AM, Randy Terbush <randy@terbush.org> wrote: > On Tue, Nov 1, 2016 at 9:21 AM, Matt Churchyard < > matt.churchyard@userve.net> wrote: > >> On Tue, Nov 1, 2016 at 8:58 AM, Matt Churchyard via >> freebsd-virtualization <freebsd-virtualization@freebsd.org> wrote: >> >> On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote: >> > On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote: >> > > On Tue, Nov 01, 2016 at 09:02:57AM +0000, Matt Churchyard wrote: >> > > > >> > > > > >> > > > > I was able to install the Windows 2016 using the GUI method. >> > > > > >> > > > > One problem. >> > > > > >> > > > > It is assigned an IP but >> > > > > >> > > > > the netmask and the default route is not showing up. >> > > > > >> > > > > Also??The virtual Windows 2016 box does not see a network >> > > > > interface. >> > > > This makes very little sense. You usually specify the netmask and >> > > > default route when you assign Windows an IP address. >> > > > And how have you assigned the guest an IP address if it has no >> > > > network interface? >> > > > >> > > The taps are allocated an IP address. >> > > >> > > I fully concur. >> > > >> > > In the install at one point, I declare that the IP address, netmask >> > > and gateway are 'declared' at the 'MB ' BIOS interface. >> > > >> > > >> > > > >> > > > > >> > > > > What must I do to convince this box that is it on a switch >> > > > On the bhyve host it should be configured just like any other >> > > > bhyve virtual machine. The guest should have a virtio-net device, >> > > > which is linked to a tap interface on the host. That tap interface >> > > > should be bridged with whichever physical network adapter you want >> > > > the guest connected to. >> > > > >> > > > However, I think I mentioned in a previous message that Windows >> > > > does not have the virtio-net drivers by default. You need to boot >> > > > the guest with the virtio-net driver ISO attached and install the >> > > > driver. You should see the interface in Device Manager flagged as >> > > > not installed/working. >> > > > >> > > >> > > That is correct . >> > > >> > > I do have an iso of the MB drivers, >> > > >> > > namely a Supermicro??X10DRW-i MB? >> > > >> > > and? >> > > >> > > from Intel I did obtain the .exe file for the i350GbE drivers. >> > > I script a 2 phase installation as follows: >> > > >> > > 1) >> > > >> > > >> > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci-cd,./.iso/14393.0.160715- >> > > 1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO -s 4,ahci- >> > > hd,windows2016.img -s 5,virtio-net,tap15 -s >> > > 29,fbuf,tcp=3D0.0.0.0:5900,w=3D800,h=3D600,wait -s 30,xhci,tablet -s >> > > 31,lpc -l com1,stdio -l >> > > bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd >> > > windows2016guest >> > > >> > > 2) >> > > >> > > >> > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s >> > > 3,ahci-cd,./.iso/null-install.iso -s 4,ahci-hd,windows2016.img -s >> > > 5,virtio-net,tap15 -s 29,fbuf,tcp=3D0.0.0.0:5900,w=3D1024,h=3D768,wa= it -s >> > > 30,xhci,tablet -s 31,lpc -l com1,/dev/nmdm15A -l >> > > bootrom,/usr/local/share/uefi- firmware/BHYVE_UEFI.fd >> > > windows2016guest & >> > > >> > > As I said, I have picked up an ISO from the MB manufacturer >> > > >> > > let's call it manufacturer.iso . >> > > >> > > Where do I place said iso in the 'phase' of things? >> > >> > You use virtio network adapters, you have to install the virtio >> > drivers and NOT the drivers for the physical interface. Then configure >> > the IP Address, gateway, etc. in Windows. >> >> >All right, let me repeat what I am up aginst. >> >> >I do set the IP configuration in the virtual BIOS. >> >> >However when the Win2016 VM boots it sees >> >> >1) the localhost >> >> >2) its assigned IP address >> >> >3) A yellow triangle where the ethernet adaptor is. >> >> I'm not sure what people find so difficult about this - Just treat it >> like it was a real Windows machine >> >> 1) Do not assign the guest's IP address on the host >> 2) Do not set the IP in the guest BIOS (I'm not even sure what you mean >> by this) >> >> As you have found, the virtio-net network adapter has a yellow triangle >> in Windows, because it is not installed. You need to run bhyve but repla= ce >> the Windows ISO with the virtio-net driver ISO, which you can download o= ff >> the Internet; Then install the network driver through VNC. The guest has= a >> "virtio-net" interface which is created by bhyve - This has nothing to d= o >> with your motherboard and you do not need to install any of the motherbo= ard >> or physical interface drivers in the guest. >> >> Once you have the virtio driver installed, you will have a "Redhat >> VirtIO" network adapter in Windows, and you can assign an >> IP/Netmask/Gateway to this just as you normally would in Windows. >> >> Forget about the Linux machines. They have the virtio-net driver built >> in, so you can just configure eth0 out-of-the-box like normal. If you've >> configured their IP addresses on the bhyve host then that's not really t= he >> correct way to configure things, even if it doesn't actually break >> anything; The IP address should be configured inside the guest OS. >> >> Matt >> >> >> >> >> >> =E2=80=8B>Can you guys confirm that you actually have a Windows 2016 vm = running? >> >> >> >> >As I have said, I have installed nearly every version of Windows OS vms >> with Bhyve (vm-bhyve) successfully with the >exception of Windows 2016. >> >> >> >> >DHCP does not work. Assigning an address by hand does not work. Any >> attempt to configure the IP on the network device or >even uninstall it >> just results in long delays and spinning cursors. >> >> >> >> >If you've got this working, I would love to see a vm-bhyve template and >> to know what virtio driver package version you are >using. >> >> =E2=80=8B >> >> I have Windows 2016 Evaluation running without any problems. - >> http://imgur.com/a/b9dws >> >> >> >> The configuration for vm-bhyve I=E2=80=99m using is below (I actually wr= ote >> vm-bhyve). >> >> I used virtio-win-0.1.118.iso as that happens to be what I had lying >> around at the time. I=E2=80=99ve no idea what other virtio driver versio= ns are like. >> >> The guest is currently using DHCP although I have no reason to suspect >> there=E2=80=99d be a problem assigning a static. >> >> >> >> uefi=3D"yes" >> >> graphics=3D"yes" >> >> graphics_res=3D"1280x720" >> >> xhci_mouse=3D"yes" >> >> cpu=3D2 >> >> memory=3D2G >> >> ahci_device_limit=3D"4" >> >> network0_type=3D"virtio-net" >> >> network0_switch=3D"public" >> >> disk0_type=3D"ahci-hd" >> >> disk0_name=3D"disk0.img" >> >> uuid=3D"2381d7fe-8c99-11e6-aa44-50e549369bc6" >> >> network0_mac=3D"58:9c:fc:04:8a:a0" >> >> >> >> Matt >> >> >> > > =E2=80=8BMy setup is not much different with exception that I am attempti= ng to > install Windows Server 2016 Essentials, release version, and I have added > both guest=3D"windows" and have set disk0_opts=3D"sectorsize=3D512" based= on some > previous help you gave me regarding failed SQL server installs. > > I tried booting the existing image I was working on and switched from the > 102 release of the virtio drivers to the 118 version to see if that made > any difference. It did not. Overall, my install has taken FOREVER, to do > anything and often simple operations like deleting drivers hangs. Not sur= e > if this is because of lack of network or also suspicious of the 512 block > size. > > I threw in the towel on the old image and have tried a clean install this > time. I attempted a sectorsize=3D4096, but the end result is an image tha= t > won't boot and just provides a EFI bios message of failed boot.. > Creating an image with sectorsize=3D512 works and is bootable. Install ru= ns > normally. There is a VERY long period of "setting up computer" in this > process which runs for nearly 30 minutes. But at the end of it all, I am > unable to install a working ethernet device. I can assign an address and > that device address is pingable, but I cannot ping the router on the > network. Attempts to work with this driver to uninstall, reinstall either > take a very long time, or hang completely. > > This is working with virtio bundle 118. > > > =E2=80=8BActually... after attempting to uninstall driver and software thro= ugh Device Manager and giving up after a long hang. After the reboot... 1. I went back to Device Manager to find the device disabled.=E2=80=8B =E2=80=8B2. Successfully deleted and removed driver software for the networ= k device. 3. Went back to ISO #118 image for virtio and installed the w10 amd64 driver and the network interface immediately came up. Success. So here is my working config: Windows 2016 Essentials release vm-bhyve template as follows: guest=3D"windows" uefi=3D"yes" cpu=3D2 memory=3D4G network0_type=3D"virtio-net" network0_switch=3D"public" graphics=3D"yes" graphics_res=3D"1600x900" graphics_wait=3D"yes" graphics_port=3D"5900" xhci_mouse=3D"yes" disk0_type=3D"ahci-hd" disk0_name=3D"disk0.img" disk0_opts=3D"sectorsize=3D512" disk1_type=3D"ahci-cd" disk1_name=3D"virtio-win-0.1.118.iso" And plenty of stubborness.... =E2=80=8B
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALmWkDYrgSg9v2C02gXAr8QzgmfJ1sMFENJTjgxgsQ9qKvUQTg>