Re: bhyve networking
On Wed, Apr 25, 2018 at 4:15 PM, Paul Esson wrote: > Hi Rod, > Can you share a command line for that? https://www.freebsd.org/doc/handbook/network-vlan.html > I also tried presenting an access port from my switch on a specific VLAN - > not trimmed. Would I still have to tag the interface on the guest in that > scenario? > No. What did tcpdump see there? -- Adam ___ 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: New bhyve user
On Fri, Sep 28, 2018 at 10:08 AM D'Arcy Cain wrote: > > This is the number of virtual cpus that the guest will see. Remember > that as far as the host is concerned, the guests are processes that are > using resources, just like any other program. A guest that is not doing > much will not being using much cpu time on the host, and the host will > happily run other guests (or system processes) on the same physical cpus. > > So if I have 16 CPUs and 8 clients, there is no problem giving them each > 4 CPUs? Is that the maximum that they can use? > The comments of this bug report contain more detail about what you can expect. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222916 That stuff would be good in the wiki. -- Adam ___ 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: [vm-bhyve] shutting down VMs and kern.init_shutdown_timeout
On Mon, Apr 29, 2019 at 3:24 AM Victor Sudakov wrote: > Patrick M. Hausen wrote: > > > > > Am 28.04.2019 um 06:41 schrieb Victor Sudakov : > > > "if the /etc/rc.shutdown does not terminate within 120 seconds, init > will > > > terminate it. The timeout can be configured via the sysctl variable > > > kern.init_shutdown_timeout.“ > > > > What’s keeping you from increasing that timeout for your > > particular requirements? > > Is that really necessary? Am I correct assuming that any VM is supposed > to shut down within 2 minutes or else the bhyve processes will be > killed? Or is this kern.init_shutdown_timeout only about the rc.shutdown > script itself and not its children? > FreeBSD is tuned as a general purpose server OS. If you find the defaults don't meet your needs, you can change them. That's why tunables exist. > > IMHO 2 minutes are a reasonable > > default for a system that does not run hypervisor VMs - > > which is probably the vast majority. > > > > Anyone with the knowledge to implement a virtualized > > environment > > The lack of information about this caveat in > https://wiki.freebsd.org/bhyve, man vm-bhyve, > > https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/virtualization-host-bhyve.html > and other sources suggests that this particular knowledge may be > limited. Other hypervisors (non-bhyve) probably wait for all VMs to stop. > RH implemented this relatively recently. https://bugzilla.redhat.com/show_bug.cgi?id=1334982 > can simply set that to a more suitable value, > > can’t he/she? > > Yes if they know about it. There should be a warning somewhere in the > documentation if we want to be serious about FreeBSD as a hypervisor. > > Or better still, a warning that rcshutdown_timeout (if set) and > kern.init_shutdown_timeout can be too low when running vm-bhyve and > such is desirable. > Why don't you simply write a wrapper script which calls shutdown after shutting down guests? I doubt many admins on any hypervisor are gratuitously calling shutdown on host with important guests running. -- Adam ___ 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"
Bhyve GPU passthrough
There was a thread here a while back about some adventurer trying to passthrough an Nvidia GPU which ultimately did not work. Unfortunately that still seems to be the case. I'm using 12.x and I could not get it to work in FreeBSD, Linux, or Windows guest. Win10 wouldn't even boot with it passed through. Linux wouldn't load the driver(could have been me) and FreeBSD guest loaded the driver, but I could not do anything useful with the card. For example, nvidia-smi -q reported No devices were found. Here is the guest view: vgapci0@pci0:0:1:0: class=0x03 card=0x77101558 chip=0x1f5010de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'TU106BM [GeForce RTX 2070 Mobile]' class = display subclass = VGA bar [10] = type Memory, range 32, base 0xc000, size 16777216, enabled bar [14] = type Prefetchable Memory, range 64, base 0xd0, size 268435456, enabled bar [1c] = type Prefetchable Memory, range 64, base 0xc200, size 33554432, enabled bar [24] = type I/O Port, range 32, base 0x2000, size 128, enabled cap 01[60] = powerspec 3 supports D0 D3 current D0 cap 05[68] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[78] = PCI-Express 2 legacy endpoint max data 128(256) FLR RO NS link x16(x16) speed 2.5(8.0) ASPM disabled(L0s/L1) I believe in earlier discussion there was objection to overcoming Nvidia's virtualization restrictions, but I think since then both vmware and kvm have implemented workarounds to allow for this. Is anyone one currently working on this or needs some testing done? -- Adam ___ 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: Bhyve GPU passthrough
On Sat, Jun 15, 2019 at 5:52 AM Robert Crowston wrote: > I think I am the most recent adventurer, but if you go back a couple of > years I am only building on material I found discussed in this mailing list. > > I do have an nVidia GPU working on Linux under the nouveau drivet. It > required some changes to the bhyve source; in particular I had to remap the > 64 bit PCI BAR allocations into the lower 4 GB of the guest’s address > space. I am not sure if that is a quirk of the AMD processor I’m using. > > I think there are a few things that prevent this from working in the > general case. Probably the most serious is bhyve doesn’t support emulation > or passthrough of PCI ROMs. I am working on a hack to make that work in my > spare time. But I am not an official member of the project, just tinkering. > :-) > > The nVidia Windows driver only checks the pending break enable bit on the > feature flags register to see if it is virtualized (or at least that was > the case about a year ago). You can readily change that to 0 in the bhyve > source code. But we are some way from that yet. > Hey yes your information both previous and current is helpful. nouveau doesn't get me anything so I didn't test it. Pretty much only goal is CUDA in the VM, but it seems you are right in that this is a ways off. There are some changes relative to my experience vs what you originally describe. Maybe part of that are the changes to bhyve 12-stable. The only thing that shows in the FreeBSD VM when trying nvidia-smi is: Jun 15 14:09:38 passthrough kernel: NVRM: GPU :00:01.0: RmInitAdapter failed! (0x26:0x65:1133) Jun 15 14:09:38 passthrough kernel: nvidia0: NVRM: rm_init_adapter() failed! So I guess that is the PCI ROM issue. If you do work up some patches and need some other testing, let me know. -- Adam ___ 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"
bhyve HD12-stable
Is the new sound emulation coming to 12-stable? The lack of it currently is the only reason I'm still using vbox. -- Adam ___ 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: VMWare/Virtualbox virtio network drivers?
On Sat, Sep 24, 2011 at 9:37 PM, Craig Rodrigues wrote: > > Virtio drivers are coming. See: > > > http://lists.freebsd.org/pipermail/svn-src-projects/2011-September/004361.html > > Great news, do you know if an MFC is planned? -- Adam Vande More ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: vboxdrv.ko loaded, but no /dev/vboxdrv
On Tue, Oct 11, 2011 at 4:04 PM, G. Paul Ziemba < pz-freebsd-virtualizat...@ziemba.us> wrote: > Hello wise ones, > > I have the recent (from a few days ago) virtualbox-ose and > virtualbox-ose-kmod ports installed. Other ports are mostly > from Jan, 2011. With vboxdrv.ko loaded, /dev/vboxdrv does not > seem to be created and I don't know why. > >% kldstat >Id Refs AddressSize Name > 1 34 0xc040 c4fc74 kernel > 22 0xc105 2fc38linux.ko > 31 0xc108 1c420snd_hda.ko > 41 0xc109d000 9970 aio.ko > 61 0xc73ce000 8000 linprocfs.ko > 71 0xc78d1000 1ipfw.ko > 81 0xc7bf9000 21000kqemu.ko > 91 0xc7cc2000 2000 blank_saver.ko >101 0xc7ee2000 68000radeon.ko >111 0xc7f4a000 14000drm.ko >121 0xc92fd000 b000 netgraph.ko >131 0xcbbc9000 2e000vboxdrv.ko >% ls /dev/vboxdrv >ls: /dev/vboxdrv: No such file or directory >% > > I originally had a RELENG_8 kernel and userland from Jan, 2011 on > this host, but I csup-ed this morning (tag=RELENG_8) and built/ > installed new kernel and userland. I also rebuilt virtualbox-ose > and virtualbox-ose-kmod afterwards. > > There seems to be some logging facility in the vboxdrv code, but I > do not understand how to enable it or where to look for the output. > > Thanks for any suggestions! > On a perfectly functioning vbox host, I don't have it either: galacticdominator% ls /dev/vboxdrv ls: /dev/vboxdrv: No such file or directory but I do have: galacticdominator% ls /dev/vboxdrv* /dev/vboxdrv0 -- Adam Vande More ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: BHyVe under VMWare Workstation8/Player4/Fusion4
On Mon, Feb 6, 2012 at 8:40 AM, Peter Grehan wrote: > Hi Nikos, > > > Does this stand true for virtualbox too? >> > > Bhyve under VBox ? No; looks like virtualbox doesn't support nested > virtualization. > > VBox on FreeBSD under VMWare Fusion4/Workstation8 ? Most likely. > Some of these people these people report differently and as well as someone I know. https://forums.virtualbox.org/viewtopic.php?f=1&t=20589 -- Adam Vande More ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: VirtualBox drama - failing VDI disks, VM not starting headless, Rebuild problems on 8.2 (clang related problem?) and 9-STABLE (libpcre.so.0)
On Sun, Apr 1, 2012 at 10:54 PM, Petro Rossini wrote: > On Mon, Apr 2, 2012 at 9:55 AM, Petro Rossini > wrote: > > Hi all, > > > > I had some VirtualBox hassle over the weekend. > ... > > Anyway, I started upgading to the newest VirtualBox in the > > ports(4.1.18). > > Sorry, it is 4.1.8. > This mailing list is used for virtualization issues like VIMAGE. Questions concerning VirtualBox go to freebsd-emulation@ AFAICT, that error message is related to a permissions issue. Can you supply the VM log when you post the question to emulation? -- Adam Vande More ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: VirtualBox problem booting FreeBSD-9.0-RELEASE-amd64-bootonly.iso
On Mon, Apr 16, 2012 at 10:30 PM, Craig Rodrigues wrote: > After exchanging a few e-mails with Bernard, I think I understand the > problem. > According to the VirtualBox manual: > > http://www.virtualbox.org/manual/ch03.html#intro-64bitguests > > The CPU needs to support hardware-assisted virtualization in order for > VirtualBox to support 64-bit guests. > Without the CPU support, VirtualBox cannot do it. I double checked > this with CoreInfo.exe from Windows Sysinternals utilities, > and also from the Intel data sheet for my CPU: > > http://ark.intel.com/products/30787 > (VT-x option not supported) > > > I will use QEMU under Windows until I can get a better machine. :) > I believe a Windows 7 product key will activate either 32 or 64 install, so unless you have a specific reason to install 64 bit then you are likely better using 32 anyway. 32 bit OS's and apps use less memory than their corresponding 64 bit counterparts. -- Adam Vande More ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: [Announcement] VPS // OS Virtualization // alpha release
On Fri, Aug 31, 2012 at 3:49 AM, Klaus P. Ohrhallinger wrote: > Hello! > > I'm pleased to announce the first feature-complete alpha version > of my virtualization project VPS: > > http://www.7he.at/freebsd/vps/ > > Looks very promising, can't wait to try it out. -- Adam Vande More ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Best VM setup for FreeBSD
On Thu, Jun 6, 2013 at 9:26 AM, TJ wrote: > > I have been looking into VirtualBox. > > My biggest hurdle at the moment is getting multiple hosts on one machine > and setting up the VRDE to use different ports. Works great for me. -- Adam Vande More ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Is it possible to install a VirtualBox_Extension_Pack in FreeBSD 9.1
On Thu, Jul 25, 2013 at 5:48 AM, Leslie Jensen wrote: > > I'm trying to get USB support in a Windows7 guest under FreeBSD > 9.1-RELEASE. > > I've read that I need this Extension Pack > https://wiki.freebsd.org/VirtualBox#USB_support -- Adam Vande More ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: RFC: Changes to handbook on virtualization
On Fri, Oct 11, 2013 at 9:00 AM, Dee Nixon wrote: > Must have been a brief temporary glitch. The link is indeed working: > > http://www.petitecloud.org/handbook.jsp > > It's not resolving here from 2 different dns paths. -- Adam Vande More ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Report of my virtual network lab migrated from virtualbox to bhyve
On Sat, Feb 8, 2014 at 5:20 AM, Olivier Cochard-Labbé wrote: > On Fri, Feb 7, 2014 at 8:38 PM, Peter Grehan wrote: > > > > > > > If you create a sparse file for the bhyve raw disk (e.g. with truncate > > -s), du will show the actual blocks used rather than the total size. > > > But can I truncate an already existing image disk (downloaded nanobsd image > as example) ? There is this: https://github.com/masover/sparsify I think this or something like it used to be in ports too. -- Adam ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Report of my virtual network lab migrated from virtualbox to bhyve
On Sat, Feb 8, 2014 at 5:42 AM, Aryeh Friedman wrote: > > bhyve (as far I know) disks must be one solid file (md backed) or a /dev > block device... therefore it is unlikely the above would work > The reported size would be identical so I don't see what the problem is. -- Adam ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Report of my virtual network lab migrated from virtualbox to bhyve
On Sat, Feb 8, 2014 at 6:51 AM, Aryeh Friedman wrote: > > bhyve blindly read/writes into the middle of the file without consulting > the filesystem and thus bypassing any things like sparse fill in namely > all you gain is a few seconds of startup time (matter of fact I think > truncate might use sparse allocation [i.e. attempting to read into the > middle with guest OS control will result in potentially seeing host data]) > If this is true then there is a *critical* security issue. Using sparse files isn't to gain performance, it's to conserve disk space. Using md devices backed by sparse images would accomplish this. If the sparsify app works on FreeBSD, then there should be no problem using those type of volumes. -- Adam ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Report of my virtual network lab migrated from virtualbox to bhyve
On Sat, Feb 8, 2014 at 2:14 PM, Aryeh Friedman wrote: > > > It sounds almost identical to the qcow2 security issue being discussed on > qemu-de...@qemu.org recently. This might be a *HUGE* win for bhyve then > in considering that it's default format is raw (should ahci-hdd be the > default?). devel/qemu (not sure about -dev) uses qcow2 as a default and > when playing with it on other OS's I found that it seemed to default to > that also. It is my understand that most of the open source cloud > platforms use qcow2 as their default also (I remember this from an attempt > to install openstack grizzly last summer... I have not checked havana > though... can any of the freebsd-openstack confirm this?). > I don't consider it a huge win because the possibility of using an insecure device precludes it. Someone high on the tree bhyve needs to confirm or deny this otherwise it is unsafe to recommend bhyve or petitecloud. No offense intended, I really hope it succeeds and will likely use it if it does. I cannot use anything which leaves the host open. I am also unclear on how bhyve bypasses GEOM which *should* prevent any of the symptoms discussed. -- Adam ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Report of my virtual network lab migrated from virtualbox to bhyve
On Sat, Feb 8, 2014 at 2:57 PM, Aryeh Friedman wrote: > > > > On Sat, Feb 8, 2014 at 3:54 PM, Adam Vande More wrote: > >> >> On Sat, Feb 8, 2014 at 2:14 PM, Aryeh Friedman >> wrote: >> >>> >>> It sounds almost identical to the qcow2 security issue being discussed >>> on qemu-de...@qemu.org recently. This might be a *HUGE* win for bhyve >>> then in considering that it's default format is raw (should ahci-hdd be the >>> default?). devel/qemu (not sure about -dev) uses qcow2 as a default and >>> when playing with it on other OS's I found that it seemed to default to >>> that also. It is my understand that most of the open source cloud >>> platforms use qcow2 as their default also (I remember this from an attempt >>> to install openstack grizzly last summer... I have not checked havana >>> though... can any of the freebsd-openstack confirm this?). >>> >> >> I don't consider it a huge win because the possibility of using an >> insecure device precludes it. Someone high on the tree bhyve needs to >> confirm or deny this otherwise it is unsafe to recommend bhyve >> or petitecloud. No offense intended, I really hope it succeeds and will >> likely use it if it does. I cannot use anything which leaves the host >> open. I am also unclear on how bhyve bypasses GEOM which *should* prevent >> any of the symptoms discussed. >> > > The point was that raw has no issue and this is the default for both bhyve > and petitecloud (to avoid certain list politics I didn't mention it by name > before). Sparse is the issue and thus qemu, openstack and cloudstack (as > well as likely vbox) are a problem. > Yes but bhyve *supports* other backing devices than raw correct? Then this really bad. I don't want a politics game either, just saying you won't get adoption until security is clear. I have no problem with you mentioning petitecloud. Indeed I think you should but others may disagree. In your opinion are ZVOL's a good option? -- Adam ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Issues gatewaying through Hyper-V
On Thu, Oct 29, 2015 at 10:45 PM, Larry Baird wrote: > I have two identical setups on Hyper-V 2012R2 and Hype-V windows 10. > > I have two FreeBSD 10.2-RELEASE-p6 Hyper-V hosts in both cases. > The first FreeBSD host (client) has one NIC configured to use a Private > network. The second (gateway) has two nics. One private and one external. > The gateway box has the gateway_enable option set to YES in its rc.conf. > The boxes otherwize of very vanilla. > > I get failures forwarding thru gateway on both versions of Hyper-V. But > they fail in different ways. > There was a similar issue w/ PF resolved earlier and I'm pretty sure the fix wasn't in 10.2. If PF is in use, does switching to ipfw fix it? I know nothing of HyperV, but I also saw similar behavior on KVM. Switching the VM NIC away from virtio to intel was a successful workaround. -- Adam ___ 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: C bhyve administration tool
On Tue, Nov 3, 2015 at 4:19 PM, Shawn Debnath wrote: > Hello! > > Couple months ago I started writing a bhyve management tool in C for our > startup, in preparation for migration to FreeBSD for our servers. The > goal was to be able to create, drop, and auto-start/stop/restart VMs, > individually or all at once, and provide a plugin infrastructure to > expose some metrics / errors for reporting and aggregation. More > importantly it would detect errors/failures, report them and attempt to > restart the VM per assigned policy. > > The effort stalled due to some high priority work that crept in. > However, I am planning on restarting soon and wanted to check if there > was a need for something like this. I ran across Michael Dexter's vmrc, > and although its shell based, it does provide quite a bit of features > that we were looking for. There's also iohyve. And I heard Peter and > Neel are working on something as well. If there is interest, this would > be open sourced from the start. Or if there is an existing effort > that addresses these problems, I would love to contribute to that project. > > Thoughts, comments, concerns, please share. > vm-bhyve is most mature to this point IME, just don't use the ports version. -- Adam ___ 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: vm-bhyve port upgrade
On Thu, Nov 12, 2015 at 4:37 AM, Matt Churchyard via freebsd-virtualization wrote: > Hello, > > For anyone interested I have submitted a PR to update the version of > vm-bhyve in the ports tree. > Primarily this fixes the off-putting, but completely benign error printed > when users run 'vm init' (the very first thing to run...) > I've no idea if I've got the diff format right though. > > Also adds various small fixes, and the following changes since the last > ports version: > > Command to rename a guest > Configuration options for utctime, hostbridge, disk options, debug mode, > custom grub commands, virtual random device > Snapshot and rollback commands when using ZFS > Allows use of custom bridges and/or tap devices in addition to the normal > automated networking > Ability to specify a custom path for disk devices > Guests can now automatically attach correctly to virtual switches if the > real interface(s) (and thus the bridge) are using jumbo frames > Template options to specify zfs dataset/zvol properties to apply when > creating a guest (most useful for zvol volblocksize) > New 'info' commands showing detailed guest/switch details including disk & > network usage > No longer replaces dnsmasq.conf, just provides a sample config for the > user to apply if they want dhcp on a nat-enabled virtual switch. > If I statically define MAC addresses, is there a possibility for collisions? I think it would be better to default to an auto generated permanent MAC. -- Adam ___ 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: vm-bhyve port upgrade
On Mon, Nov 16, 2015 at 9:34 AM, Matt Churchyard wrote: > > I am now looking at actually implementing static macs for all interfaces, > as I’d rather guests saw the same mac address every run just in case they > tie configuration to the mac (important for vm-bhyve as simply starting > guests in a different order will change what tap devices they get). Also > tap/slot/func isn’t much of a uniqueness guarantee across multiple hosts. > > Yes, and udev treats MAC as ethX = MAC. So linux guests using static ip's will be quite broken unless some more fiddling is done. Static MAC's aren't the only way to handle this, but it's the best IMO. -- Adam ___ 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: available hypervisors in FreeBSD
On Sun, Dec 20, 2015 at 2:15 AM, Peter Ross wrote: > Hi all, > > I read through an older threat I kept in my archive. It started like this: > > On Wed, 1 Apr 2015, Udo Rader wrote: > > As far as my homework digging revealed, FreeBSD supports four hypervisors: >> >> * bhyve >> * KVM >> * QEMU >> * VirtualBox >> > > .. and later Xen was mentioned. > > I ask myself which of the solutions are most mature at the moment and > immediately usable in production. > > Reason is a potential company move from VMware ESXi/Centos(6/7) with some > critical Windows 2008 and 2012 IIS/.NET applications) involved. > > While most of open source may go into FreeBSD jails, we have a few > CentOS6/7 boxes with proprietary software we have to keep, as well as the > Windows VMs to maintain (there is a long term effort to move them to Open > Source too but the final migration of all may be years away). > > We may phase out ESXi gradually, or just keep it, depending on the > performance and maturity of FreeBSD based solutions. > > I have experience with Linux on VirtualBox and it worked well if the load > was not high but the performance wasn't too good when under stress (but it > never crashed, I might add). > > Which of the solutions are worth testing? Do you have recommendations? > > I am thinking of server software and "containerisation" only, so USB > passthrough or PCI etc. is not really important. > > Stability, performance and resource utilisation (e.g. possible > over-allocation of RAM) are matter most. > VBox is fine, it works well and really has all the features of vitalization of the big 3 except for clustering and a few side things. I've been using bhyve and I like it. I have no stability issues on dozens of guests some with a lot of IO net and disk. I had hoped VPS[1] would make it in, but that seems to have stalled. [1] http://www.7he.at/freebsd/vps/ -- Adam ___ 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: available hypervisors in FreeBSD
On Sun, Dec 20, 2015 at 9:25 AM, Sergey Manucharian wrote: > I agree that VirtualBox is really stable, and I'm using it in production > environments for many years. However, there are a couple of possible > drawbacks: It does not support VRDP (remote console) and USB2/3 on FreeBSD. > > Tha latter is probably not really important (although I needed it too). > The lack of remote console is bad for troubleshooting and/or remote > (re)installation. > Remote console is available via VNC, not RDP. -- Adam ___ 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: available hypervisors in FreeBSD
On Sun, Dec 20, 2015 at 10:14 AM, Sergey Manucharian wrote: > > Remote console is available via VNC, not RDP. > > It is VNC, and I use it Linux hosts, it's rather confusing since the option > is "--vrde on|off". See https://lists.freebsd.org/pipermail/freebsd-emulation/2013-January/010354.html You can also set options like VNCAddress4 for listening address. > But isn't it a part of the extension pack, which is > not available for FreeBSD? > > https://www.virtualbox.org/manual/ch07.html > The explanation lies within that page. VRDP is only in extension pack, VRDE is available to all. So someone with enough gumption could write a VRDE RDP support. -- Adam ___ 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"
Bhyve guest ntp server woes
I am unable to get a 10.2 bhyve ntp server to be stable. Most configurations of kern.timecounter.* sysctl kern.eventtimer.* in the guest seem to make little difference, however kern.eventtimer.periodic=1 does seem to stabilize it a little. However after some runtime, I get very high jitter and offsets and extraordinary dispersion and distance values when seen from the host using guest as server(not actually sync'd against). How can I get some sane ntp in bhyve? Thanks, -- Adam ___ 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: floppy image in bhyve
On Wed, Jan 20, 2016 at 8:06 PM, Sergey Manucharian wrote: > Yes, that a good idea especially taking into account that I have many > variables. I'm trying to migrate Windows 7 on an encrypted volume from > VBox to bhyve. > Another option would be to migrate to GELI, possibly on a ZVOL if available. Then tie bhyve windows vm startup/shutdown scripts to unlock/lock device as needed. -- Adam ___ 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: Re-sparse a file-backed IO device + zfs
On Mon, Dec 12, 2016 at 7:20 PM, javocado wrote: > Hi, > > I'm setting up a bhyve wherein: > > host # truncate -s 1T vol.file > host # du -ah vol.file > 200Kvol.file > > host # /usr/sbin/bhyve ... -s 4,ahci-hd,vol.file ... > > Then inside the bhyve I create a zpool (ada0 = vol.file): > > bhyve # zpool create -O devices=off -O atime=off -O compression=on -m > /mnt/data1 data1 ada0 > I think there used to be a utility called sparsify. -- Adam ___ 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: Storage overhead on zvols
On Mon, Dec 4, 2017 at 5:19 PM, Dustin Wenz wrote: > I'm starting a new thread based on the previous discussion in "bhyve uses > all available memory during IO-intensive operations" relating to size > inflation of bhyve data stored on zvols. I've done some experimenting with > this, and I think it will be useful for others. > > The zvols listed here were created with this command: > > zfs create -o volmode=dev -o volblocksize=Xk -V 30g > vm00/chyves/guests/myguest/diskY > > The zvols were created on a raidz1 pool of four disks. For each zvol, I > created a basic zfs filesystem in the guest using all default tuning (128k > recordsize, etc). I then copied the same 8.2GB dataset to each filesystem. > > volblocksizesize amplification > > 512B11.7x > 4k 1.45x > 8k 1.45x > 16k 1.5x > 32k 1.65x > 64k 1x > 128k1x > > The worst case is with a 512B volblocksize, where the space used is more > than 11 times the size of the data stored within the guest. The size > efficiency gains are non-linear as I continue from 4k and double the block > sizes; 32k blocks being the second-worst. The amount of wasted space was > minimized by using 64k and 128k blocks. > > It would appear that 64k is a good choice for volblocksize if you are > using a zvol to back your VM, and the VM is using the virtual device for a > zpool. Incidentally, I believe this is the default when creating VMs in > FreeNAS. > I'm not sure what your purpose is behind the posting, but if its simply a "why this behavior" you can find more detail here as well as some calculation leg work: https://www.delphix.com/blog/delphix-engineering/zfs-raidz-stripe-width-or-how-i-learned-stop-worrying-and-love-raidz -- Adam ___ 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: NFS alternatives (was: Re: Storage overhead on zvols)
On Wed, Dec 6, 2017 at 2:45 AM, Patrick M. Hausen wrote: > Hi all, > > > Am 05.12.2017 um 17:41 schrieb Rodney W. Grimes < > freebsd-...@pdx.rh.cn85.dnsmgr.net>: > > In effect what your asking for is what NFS does, so use NFS and get > > over the fact that this is the way to get what you want. Sure you > > could implement a virt-vfs but I wonder how close the spec of that > > would be to the spec of NFS. > > I figure it should be possible to implement something simpler > than NFS that provides full local posix semantics under the > constraint that only one "client" is allowed to mount the FS > at a time. > > I see quite a few applications for something like this, specifically > in "hyperconvergent" environments. Or vagrant, of course. > > *scratching head* isn't this what Sun's "network disk" protocol provided? > > Kind regards, > Patrick Like this? https://www.freebsd.org/doc/handbook/geom-ggate.html -- Adam ___ 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"
