Re: Status of bhyve
Hello, Do have plans for Suspend/Resume? I'm really waiting for this feature. -- Alexander > On Feb 16, 2017, at 4:07 AM, Shane Ambler wrote: > > > CC'ing to freebsd-virtualization as a better place to ask this. > > On 16/02/2017 05:11, Andrea Venturoli wrote: >> Hello. >> >> I've been searching the web for a while, but the info I got is sparse >> (many howtos, little on the big picture) and it's not always clear what >> is current and what is outdated. >> >> I might be in need to permanently run a Windows 64b VM (with SQL server) >> on a new FreeBSD box, so... > > Permanently as in a development environment or production? > >> What's the current status of bhyve? >> I mean, it is it production ready (meaning no critical feature is >> missing and I can count on this VM to behave properly nearly as much as >> the host)? >> Any difference between 10.3 and 11.0? (I got the idea the former will be >> supported for longer and I'd have to upgrade my poudriere in order to >> install the latter). > > 11.0 includes a "VNC accessible framebuffer driver" which is not in 10.x > This will allow you to vnc into the bhyve instance during boot to > install/repair windows. > > You will need to run poudriere on an 11 host to build 11 packages, > while you can sometimes have success building newer systems than the > host, building 11 packages on a 10 host does fail for many ports. > >> >> How well does it run Windows? >> Would I better run W7 instead of W10 (or the other way round)? >> What's the maximum amount of RAM I can dedicate to a VM? >> >> >> How does it compare to VirtualBox wrt to stability and performance? >> (I know I can find benchmarks, but, again, it's hard to tell whether >> they can be trusted or considered current). >> >> >> Should I use a dedicated disk (or disk mirror) for better speed? >> Or should I use a dedicated partition on the host's disk/disk mirror? >> Will a ZFS volume perform as good as a partition? >> >> >> >> Any caveat or hint? >> >> >> >> bye & Thanks >>av. > > > > -- > FreeBSD - the place to B...Sharing Devices > > Shane Ambler > > ___ > 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"
Re: Status of bhyve
On Thu, 16 Feb 2017 11:37:44 +1030, Shane Ambler wrote: CC'ing to freebsd-virtualization as a better place to ask this. Thanks, I hadn't noticed this list; I subscribed now. I might be in need to permanently run a Windows 64b VM (with SQL server) on a new FreeBSD box, so... Permanently as in a development environment or production? Production. 11.0 includes a "VNC accessible framebuffer driver" which is not in 10.x Then, if the "thing" will start, 11.0 will be. bye & Thanks av. ___ 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: Status of bhyve
On Thu, 16 Feb 2017 10:46:34 +0100, Harry Schmalzbauer wrote: Hello, it depends on the features you need. Not much, really. Running SQL Server Express (for now) with decent performance. · virtio-blk and jumbo frames (e1000 works with jumbo frames but performance is not comparaable with ESXi e1000(e)) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215737 I don't think the underlying network equipment will support Jumbo Frames :( · PCI-Passthru is very picky. If you have a card with BAR memorysize < | != pagesize, byhve(4) won't accept it. > > · device(9) as block storage backend (virtio-blk, ahci-hd) doesn't work > if you use any PCI-passthru device > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215740 I don't think I'd need PCI passthrough (I'm fine with a disk and a network card). · virtio-blk isn't virtio-win (Windows driver) compatible, guest will crash! · virtio-net doesn't work with latest Windows drivers, which is not a bhyve(4) problem as far as I can tell. Version 0.1.118 works, newer ones are known to have problems on other hypervisors too. Good to know. · See if_bridge(4) for some limitations (all members need to have exactly the same MTU, uplink gets checksum offloading disabled). Generally, soft-switching capabilities ar not comparable with those of ESXi, especially not the performace (outside netmap world). This is a good point. :( Other than that, it's rock solid for me ... How well does it run Windows? Would I better run W7 instead of W10 (or the other way round)? Fine. Should I use a dedicated disk (or disk mirror) for better speed? Or should I use a dedicated partition on the host's disk/disk mirror? Will a ZFS volume perform as good as a partition? ZVOL is the best option offering great performance (depending on your pool setup of yourse) as long as there is the PCI-passthru bug mentioned above. Thanks again. bye av. ___ 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: Status of bhyve
CC'ing to freebsd-virtualization as a better place to ask this. On 16/02/2017 05:11, Andrea Venturoli wrote: Hello. I've been searching the web for a while, but the info I got is sparse (many howtos, little on the big picture) and it's not always clear what is current and what is outdated. I might be in need to permanently run a Windows 64b VM (with SQL server) on a new FreeBSD box, so... Permanently as in a development environment or production? What's the current status of bhyve? I mean, it is it production ready (meaning no critical feature is missing and I can count on this VM to behave properly nearly as much as the host)? Any difference between 10.3 and 11.0? (I got the idea the former will be supported for longer and I'd have to upgrade my poudriere in order to install the latter). 11.0 includes a "VNC accessible framebuffer driver" which is not in 10.x This will allow you to vnc into the bhyve instance during boot to install/repair windows. You will need to run poudriere on an 11 host to build 11 packages, while you can sometimes have success building newer systems than the host, building 11 packages on a 10 host does fail for many ports. How well does it run Windows? Would I better run W7 instead of W10 (or the other way round)? What's the maximum amount of RAM I can dedicate to a VM? How does it compare to VirtualBox wrt to stability and performance? (I know I can find benchmarks, but, again, it's hard to tell whether they can be trusted or considered current). Should I use a dedicated disk (or disk mirror) for better speed? Or should I use a dedicated partition on the host's disk/disk mirror? Will a ZFS volume perform as good as a partition? Any caveat or hint? bye & Thanks av. -- FreeBSD - the place to B...Sharing Devices Shane Ambler ___ 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"
