Status of ptnet patch integration into bhyve ?

Hi, What is the status of merging bhyve's ptnet patches into head ? bhyve network performance (with tap + if_bridge) prevent us to use it on production environment, but I remember an interesting presentation about netmap/ptnet patches for bhyve [1]. I believe bhyve's team is aware of this projec

Re: -current host, 10.1 client loops

On Wed, Mar 16, 2016 at 10:25 PM, Poul-Henning Kamp wrote: > > How do I tell that script to use ahci-hd ? > > ​You just need to replace virtio-blk by ahci-hd in the script, like: sed 's/virtio-blk/ahci-hd/g' /usr/share/examples/bhyve/vmrun.sh > ~/vmrun-ahci.sh ​And running ~/vmrun-ahci.sh in pl

Limited number of vale switch useable with bhyve ?

Hi, Thanks to btw's patch I can now use bhyve and vale. But I'm hitting a limitation: I want to start 5 VM connected by a full-meshed network. This mean: - VM 1 has 4 interfaces toward each other 4 VMs - and so one for all others 4 VMs This give these 5 command lines: bhyve -c 1 -m 256M -A -H -P

How to use bhyve and vale switch ?

Hi, I'm trying to start 2 VMs connected by a vale switch. Host system: FreeBSD 11.0-CURRENT #1 r296650 (Fri Mar 11) Guest systems: FreeBSD 11.0-CURRENT #0 r296721 (Sat Mar 12) Command-lines used for starting these VM are these one: sysctl dev.netmap.verbose=1 bhyve -c 1 -m 256M -A -H -P -s 0:0,h

No multicast routing support on Virtio vtnet(4) drivers ?

I'm trying to set-up a multicast network lab using bhyve (then the vtnet interfaces). But when starting a PIM multicast routing daemon, I've got this error message: [root@router]~# service pimd start Starting pimd. pimd: 17:22:59.119 Failed adding VIF 0 (MRT_ADD_VIF) for iface vtnet0:(error 45): O

Re: Enabling VIMAGE by default for FreeBSD 11?

On Tue, Oct 14, 2014 at 8:20 AM, Craig Rodrigues wrote: > On Sat, Oct 11, 2014 at 1:20 PM, Alexander V. Chernikov > wrote: > > > > > On 11 Oct 2014, at 21:58, Craig Rodrigues wrote: > > > > > Hi, > > > > > > What action items are left to enable VIMAGE by default for FreeBSD 11? > > Are there an

Re: bhyve's VM loose network connectivity after a reboot

On Thu, Aug 21, 2014 at 5:26 PM, Peter Grehan wrote: > Hi Olivier, > > Do you have the net.link.tap.up_on_open sysctl set to 1 ? (didn't see > that in the BSDRP-lab-bhyve.sh script, if that's the one you're using) > > > Yes I was using the BSDRP-lab-bhyve.sh script and correctly setting net.link

bhyve's VM loose network connectivity after a reboot

Hi, I'm using bhyve from a 11.0-CURRENT (r270177) host and I meet a problem after a VM (guest using fbsd -current too) is rebooted: This VM loose network connectivity once rebooted. vtnet interface seems OK from the VM, like the tap interface on the host: tap status correctly display the new bhyve

Re: bhyve and serial port emulation problem

On Thu, May 1, 2014 at 7:29 PM, Neel Natu wrote: > Hi Olivier, > > The UPDATING entry in r264175 describes how to fix this: > http://svnweb.freebsd.org/base?view=revision&revision=264175 > > Briefly, you will now need to change your /etc/ttys to look like this: > ttyu0 "/usr/libexec/getty 3wire

Re: bhyve and serial port emulation problem

On Wed, Apr 30, 2014 at 7:33 PM, Neel Natu wrote: > Hi Olivier, > > Can you share the command line options you pass the bhyve(8)? > > Hi Neel, sure, here it is: bhyveload -m 256M -d /tmp/BSDRP/BSDRP_1 -c /dev/nmdm1A BSDRP_1 bhyve -c 1 -m 256M -A -H -P -s 0:0,hostbridge -s 0:1,lpc -s 2:0,virtio-

bhyve and serial port emulation problem

Hi, I'm using the same nanobsd image on Virtualbox and bhyve (-CURRENT r265101). The nanobsd image I'm using is configured for serial port as default console: [root@nanobsd]~# cat /boot.config -S38400 -h [root@nanobsd]~# grep ttyu0 /etc/ttys ttyu0 "/usr/libexec/getty std.38400" vt100 on sec

Re: Report of my virtual network lab migrated from virtualbox to bhyve

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) ? >

Report of my virtual network lab migrated from virtualbox to bhyve

Hi, just a report of my migration to bhyve. I was using VirtualBox for generate full-meshed network lab of multiple VM (essentially nanobsd based) and have migrated my script to bhyve. My original script is resumed to this kind of usage: ./lab-script.sh -i FreeBSD-image-disk -n number-of-vm -l n

Re: Virtualbox Non OSE version?

On Sat, May 29, 2010 at 3:55 PM, Bram Verswalm wrote: > Will there be a non OSE-version for FreeBSD in the future? Cause VRDP is > really a basic need for headless servers. There is a VNC patch for the FreeBSD Virtualbox OSE-version made by Daisuke Aoyama here: https://sourceforge.net/mailarchiv

Qemu and serial uart drivers

Hi, I meet a problem with the new serial driver "uart" used in FreeBSD 8.0-Beta and Qemu. Hi all, Under Qemu, my "serial-console-only" FreeBSD 7.2 image (sio drivers) works great, but my "serial-console-only" FreeBSD 8.0-Beta4 image (uart drivers) doesn't works. I try to replace Qemu 0.10.6 with