Re: VBox 5 getting window height wrong
Hi, Do you have the right version of Guest Additions installed on your guests? I also have Windows 10 as a VM in VirtualBox (though it's FreeBSD 11), but it works for me without any problems. Daniel Tihanyi On Wed, 2017-06-14 at 11:54 +0100, Gary Palmer wrote: > Hi, > > Ever since upgrading from vbox 4 (which had occasional window placement > or size issues, but nothing serious), vbox 5 has consistently had a problem > where on starting a VM the window height is always reset to a fraction of > what it should be. If I size the window properly by hand, and then select > View -> Adjust Window Size it goes back to the wrong size again. > > Anyone else seen this? > > With Win10 it's worse - unless I maximise the window it keeps getting reset > to the wrong height, I think by communication with the additions installed > in the client. > > virtualbox-ose-5.1.22_1General-purpose full virtualizer for x86 > hardware > virtualbox-ose-kmod-5.1.22 VirtualBox kernel module for FreeBSD > > 10.3-RELEASE-p18 > > Thanks, > > Gary > > P.S. Please keep me on CC as I am not subscribed to this list > ___ > 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" ___ 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"
Assigning PCI ethernet interfaces to VMs in bhyve
Hello, I have a FreeBSD host running VMs on bhyve. I already have a few PCI-X ethernet cards assigned to each of them, but only with one ethernet interface. I would like to purchase a few PCI-X Ethernet cards with 4 interfaces. My question is if it is possible to assign the individual interfaces on the card to different VMs? On the bhyve Wiki, there is an example for this, but it is assigning the interfaces into the same VM, although to different slots. I am planning to use Intel cards for this of course. Has anyone experience in this? Thank you very much in advance! Daniel Tihanyi signature.asc Description: This is a digitally signed message part
Re: Windows 2016
On Tue, 2016-11-01 at 08:22 -0600, The Doctor 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 +, 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=0.0.0.0:5900,w=800,h=600,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=0.0.0.0:5900,w=1024,h=768,wait -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 don't really understand, what do you mean by virtual BIOS. If you boot up Windows, configure the IP Address, etc from there. Follow this guide to do so: https://ittutorials.net/microsoft/windows-server-2016/s et-windows-server-2016-with-a-static-ip-address/ ___ 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
On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote: > On Tue, Nov 01, 2016 at 09:02:57AM +, 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=0.0.0.0:5900,w=800,h=600,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=0.0.0.0:5900,w=1024,h=768,wait -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. ___ 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
Hi, first of all, could you please clarify if you use VirtualBox, bhyve or any other virtualization platform? Additionally, could you please share, how did you configured your network for the VMs? What do you use for DHCP Server? Is it configured properly? Thank you very much! -- Daniel Tihanyi On Tue, Nov 1, 2016, at 04:45, The Doctor wrote: > I was able to install the Windows 2016 using the GUI method. > > One proble. > > 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. > > What must I do to convince this box that is it on a switch > > 192.168.0.60 > > Thar is handling the default routing to the interent. > > For argument sake , > > the Windows server is IP as 192.168.0.68 > > > I have an ubuntu up at 192.168.0.57 > a Centos at 192.168.0.54 > and > Fedora at 192.168.0.53 > > all running successfully. > > -- > 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" ___ 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"
