[CFT] VirtIO SCSI Driver

2012-06-07 Thread Bryan Venteicher
Hi, VirtIO SCSI is a virtualized HBA that offers a couple of advantages over the existing VirtIO block disk devices. Instead of having a vtbdX disk, familiar daX and cdX devices are created like from other SCSI drivers. A single HBA is able to support multiple devices unlike the VirtIO block where

Re: [CFT] VirtIO SCSI Driver

2012-06-19 Thread Bryan Venteicher
Hi, - Original Message - > From: "Bryan Venteicher" > To: freebsd-s...@freebsd.org > Cc: freebsd-virtualization@freebsd.org > Sent: Friday, June 8, 2012 1:29:18 AM > Subject: [CFT] VirtIO SCSI Driver > > Hi, > > VirtIO SCSI is a virtualized HBA that

Re: dev/virtio stuff

2012-10-29 Thread Bryan Venteicher
Hi, - Original Message - > From: "Sean Bruno" > To: freebsd-virtualization@freebsd.org > Sent: Monday, October 29, 2012 4:49:42 PM > Subject: dev/virtio stuff > > So ... I see we have virtio nowish. I've started my hackery to make > some man(4) pages for this, but have some questions.

Re: Virtio NIC

2012-10-31 Thread Bryan Venteicher
Hi, - Original Message - > From: t...@tms3.com > To: freebsd-virtualization@freebsd.org > Sent: Wednesday, October 31, 2012 11:19:21 AM > Subject: Virtio NIC > > Hey list, > > Running a 9.1rc-2 VM on Smartos using virtio drivers and the network > performance seems to cap at 10MiB for ftp

Re: dev/virtio stuff

2012-10-31 Thread Bryan Venteicher
Hi, - Original Message - > From: "Sean Bruno" > To: "Bryan Venteicher" > Cc: sbr...@freebsd.org, freebsd-virtualization@freebsd.org > Sent: Wednesday, October 31, 2012 12:33:11 PM > Subject: Re: dev/virtio stuff > > See below. > > On M

Re: dev/virtio stuff

2012-10-31 Thread Bryan Venteicher
Hi, - Original Message - > From: "Sean Bruno" > To: "Bryan Venteicher" > Cc: sbr...@freebsd.org, freebsd-virtualization@freebsd.org > Sent: Wednesday, October 31, 2012 2:22:03 PM > Subject: Re: dev/virtio stuff > > > > > > There ar

Re: vtnet cannot allocate interrupts

2013-02-11 Thread Bryan Venteicher
Hi, - Original Message - > From: "Marat Bakeev" > To: freebsd-virtualization@freebsd.org > Sent: Monday, February 11, 2013 6:30:51 AM > Subject: vtnet cannot allocate interrupts > > Hello. > > After updating from http://svn.freebsd.org/base/projects/bhyve to > http://svn.freebsd.org/bas

Re: virtio-net vs qemu 1.5.0

2013-05-27 Thread Bryan Venteicher
Hi, - Original Message - > Hello, > > I filed a bug: > http://www.freebsd.org/cgi/query-pr.cgi?pr=178955 > I committed a fix to this in the multiqueue driver [1] during BSDCan, haven't merged it back into HEAD yet. I'll do that in a couple of days. Unless you have multiple MAC unicast

Re: virtio-net vs qemu 1.5.0

2013-05-28 Thread Bryan Venteicher
- Original Message - > Thx! Do you plan to merge the multiqueue branch? > Hopefully within 1-2 months. > Julian > > > ___ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >

Re: ot: who to report a bug in if_tap to?

2013-08-13 Thread Bryan Venteicher
- Original Message - > It is connected to the physical nic via a switch (no intermediate > routers). DHCP doesn't even attempt because there is no carrier on > tap0: > > em0: flags=8843 metric 0 mtu 1500 > > options=4219b > ether 30:85:a9:ec:24:95 > inet 10.0.10.10 n

Re: virtio problems (was: pf deadly slow)

2013-10-04 Thread Bryan Venteicher
- Original Message - > Now that I switched from virtio to 82545EM all my networking problems > disappeared. > > Appart from pf, I had also some other small networking problems that I > thought were apache/php related, but were in fact due to virtio. > > virtio is clearly the culprit, bu

Re: Virtio Driver

2014-01-12 Thread Bryan Venteicher
- Original Message - > What happens if you "camcontrol rescan all" ? > A VirtIO block device (and a parent VirtIO PCI device) is what is likely getting created here, so there is no SCSI bus to rescan. I had a prior private conversation with Robert last week. This particular use case w

Re: Virtio Driver

2014-01-13 Thread Bryan Venteicher
- Original Message - > I have created an image of 10-RC5 that I will try the same conditions > I described earlier on. Unfortunately, I'm using a cloud service, so I > don't have control to change the settings of OpenStack. > And just to be clear: In 10.0, you can only resize a disk tha

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

2014-02-07 Thread Bryan Venteicher
- Original Message - > Hi Olivier, > > just a report of my migration to bhyve. > > Yeah !!! > > > First remark comparing the disk format: With an original nanobsd disk image > > of 488MB. > > - Virtualbox format disk size: 133M > > - bhyve raw disk size: 488M > > If you create a sp

Re: Using virtio_random

2014-09-16 Thread Bryan Venteicher
On Mon, Sep 15, 2014 at 6:17 PM, John Nielsen wrote: > Hi all- > > I am happy to see that virtio_random(4) will be included in FreeBSD 10.1. > To try it out, I loaded up BETA1 in a virtual machine with entropy > passthrough enabled. After booting it with the virtio_random module loaded > I see th

Re: can a bhyve instance be resized? adding another virtual disk?

2014-10-15 Thread Bryan Venteicher
On Wed, Oct 15, 2014 at 9:38 AM, John Nielsen wrote: > On Oct 15, 2014, at 5:56 AM, freebsd-li...@potato.growveg.org wrote: > > > Can a bhyve instance be resized? I'm talking about the disk. > > Say your end user needs more diskspace. They have 32GB. They need 64GB. > > How do you do it? I presum

Re: Bug in virtio-net

2014-12-08 Thread Bryan Venteicher
On Mon, Dec 8, 2014 at 5:34 PM, Shawn Webb wrote: > I was running Poudriere in bhyve. I got this kernel panic. I'm on a new > 11-CURRENT as of this morning. Would this be a NULL pointer deref? > > `uname -a`: FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #1 > b5310d8(hardened/current/master)-dirty:

Re: bhyve clock problem, solved by kern.timecounter.hardware="TSC-low" in /etc/sysctl.conf

2015-04-10 Thread Bryan Venteicher
On Fri, Apr 10, 2015 at 4:36 PM, Ryan Stone wrote: > Using the TSC as the default timecounter in a VM is dangerous. On some > hardware, the TSC is not synchronized across all CPU cores. This means > that if a VM migrates from one core to another, it could see the > timecounter value go backward