On Wed, Jul 29, 2015 at 4:53 PM, Eliezer Croitoru elie...@ngtech.co.il
wrote:
I am testing couple VMs under kvm and from my tests it seems that there
might not be support for hot-plug of virtio disks or virtio-scsi disks in
freebsd?
Hot plug of VirtIO block devices is not supported, but
On Wed, Jan 21, 2015 at 3:15 PM, Peter Jeremy pe...@rulingia.com wrote:
On 2015-Jan-04 11:56:14 -0600, Bryan Venteicher
bry...@daemoninthecloset.org wrote:
For the last few weeks, I've been working on adding support for KVM clock
in the projects/paravirt branch. Currently, a KVM VM guest
On Thu, Jan 15, 2015 at 9:44 AM, Slawa Olhovchenkov s...@zxy.spb.ru wrote:
On Thu, Jan 15, 2015 at 06:28:23PM +0300, Lev Serebryakov wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 15.01.2015 14:29, Lev Serebryakov wrote:
kassert_panic(const char *fmt, ...) __printflike(1, 2);
diff --git a/sys/x86/include/hypervisor.h b/sys/x86/include/hypervisor.h
new file mode 100644
index 000..d5d30eb
--- /dev/null
+++ b/sys/x86/include/hypervisor.h
@@ -0,0 +1,56 @@
+/*-
+ * Copyright (c) 2014 Bryan Venteicher bry...@freebsd.org
of the clock calls from the GEOM code for each I/O would kill
performance.
-adrian
On 4 January 2015 at 09:56, Bryan Venteicher
bry...@daemoninthecloset.org wrote:
For the last few weeks, I've been working on adding support for KVM
clock
in the projects/paravirt branch. Currently, a KVM
On Mon, Dec 8, 2014 at 5:34 PM, Shawn Webb latt...@gmail.com 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
- Original Message -
On 10.06.2014 07:03, Bryan Venteicher wrote:
Hi,
- Original Message -
So, after finding out that nc has a stupidly small buffer size (2k
even though there is space for 16k), I was still not getting as good
as performance using nc between machines
Hi,
- Original Message -
So, after finding out that nc has a stupidly small buffer size (2k
even though there is space for 16k), I was still not getting as good
as performance using nc between machines, so I decided to generate some
flame graphs to try to identify issues... (Thanks
On Wed, Jun 4, 2014 at 8:49 AM, Luigi Rizzo ri...@iet.unipi.it wrote:
Hi,
if I read correctly the code, there are a few network device drivers
(igb, ixgbe, i40e, vtnet, vmxnet) where ifp-if_transmit(ifp, m)
can return ENOBUFS even when 'm' has _not_ been dropped:
e1000/if_igb.c ::
- Original Message -
Hi,
GENERIC has
# VirtIO support
device virtio # Generic VirtIO bus (required)
device virtio_pci # VirtIO PCI device
device vtnet # VirtIO Ethernet device
device virtio_blk # VirtIO Block
- Original Message -
Hi list,
I'm observing a 100%-reproducible panic in the following setup:
Host system: FreeBSD 9.1-RELEASE-p7 amd64
$ pkg info | grep virtualbox
virtualbox-ose-4.2.18_1A general-purpose full virtualizer for
x86 hardware
virtualbox-ose-kmod-4.2.18
, it would be
nice to know the difference this patch makes. I've got a second
set of patches that further reduces the dump time by over half that
I'll try to clean up soon.
http://people.freebsd.org/~bryanv/patches/minidump.patchcommit 25f9e82e4ac93e71c6cf06fe2faa1899967db725
Author: Bryan Venteicher
- Original Message -
- Original Message -
Bezüglich Bryan Venteicher's Nachricht vom 27.08.2013 06:18 (localtime):
...
snip
The intr usage is higher than the other drivers you compared against
because if_vmx does the off-level processing in ithreads where as the
- Original Message -
Bezüglich Bryan Venteicher's Nachricht vom 27.08.2013 06:18 (localtime):
...
It seems if_vmx doesn't support jumbo frames. If I set mtu 9000, I get
»vmx0: cannot populate Rx queue 0«, I have no problems using jumbo
frames with vmxnet3.
This could fail
- Original Message -
Bezüglich Bryan Venteicher's Nachricht vom 05.08.2013 02:12 (localtime):
Hi,
I've ported the OpenBSD vmxnet3 ethernet driver to FreeBSD. I did a
lot of cleanup, bug fixes, new features, etc (+2000 new lines) along
the way so there is not much of a
- Original Message -
it'd be nice if we could get vmware to just support the drivers in tree..
by which I mean, just submit patches.. why do they need to have it out
of tree?
I agree. But they are all unfriendly licensed. The FF had a discussion
to get them relicensed to something
- Original Message -
Perhaps not, but they do support FreeBSD. I've started several support cases
with FreeBSD-specific problems and they've fixed all so far.
Yes, it is not a blackhole of support. At $JOB, we got caught by the FreeBSD
specific issue of the busted timer that was
- Original Message -
i am slightly unclear of what mechanisms we use to prevent races
between interface being reconfigured (up/down/multicast setting, etc,
all causing reinitialization of the rx and tx rings) and
i) packets from the host stack being sent out;
ii) interrupts from
- Original Message -
On Mon, Aug 5, 2013 at 8:19 PM, Adrian Chadd adr...@freebsd.org wrote:
No, brian said two things:
* the flag, protected by the core lock
* per-queue flags
i see no mentions on per-queue flags on his email.
This is the relevant part
Right, I just
- Original Message -
I have ~100 FreeBSD 8/9 VMs in my vSphere 5.1 environment, all using the
VMware tools package from VMware. Everything has been running great for
years.
(we skipped vSphere 5.0). Why should I use this vmxnet driver instead of the
VMware tools driver or the
Hi,
I've ported the OpenBSD vmxnet3 ethernet driver to FreeBSD. I did a
lot of cleanup, bug fixes, new features, etc (+2000 new lines) along
the way so there is not much of a resemblance left.
The driver is in good enough shape I'd like additional testers. A patch
against -CURRENT is at [1].
On Tuesday, July 30, 2013 5:25:06 am Alexander Yerenkow wrote:
Hello all.
I have panics in vmware with installed vmwaretools (they are guessed
culprit).
Seems that memory balooning (or using more memory in all vms than there is
in host)
produces some kind of weird behavior in FreeBSD.
On Mon, Dec 17, 2012 at 1:17 AM, Bryan Venteicher bry...@freebsd.org wrote:
On Sun, Dec 16, 2012 at 11:06 PM, Jim Harris jimhar...@freebsd.org wrote:
On Sun, Dec 16, 2012 at 6:53 PM, Andrew Thompson thom...@freebsd.org
wrote:
On 17 December 2012 13:17, Bryan Venteicher bry...@freebsd.org
On Mon, Dec 17, 2012 at 12:06 AM, Andrew Thompson thom...@freebsd.org wrote:
On 17 December 2012 18:06, Jim Harris jimhar...@freebsd.org wrote:
On Sun, Dec 16, 2012 at 6:53 PM, Andrew Thompson thom...@freebsd.org
wrote:
On 17 December 2012 13:17, Bryan Venteicher bry...@freebsd.org wrote
There's been lots of requests to have VirtIO in GENERIC for i386 and
amd64. Anybody have any issues or concerns with this or the patch at
[1]. This also removes the kludge that was introduced in r239009.
I've compiled LINT for i386 and amd64 so hopefully there won't be any
surprise breakages.
On Sun, Dec 16, 2012 at 11:06 PM, Jim Harris jimhar...@freebsd.org wrote:
On Sun, Dec 16, 2012 at 6:53 PM, Andrew Thompson thom...@freebsd.org
wrote:
On 17 December 2012 13:17, Bryan Venteicher bry...@freebsd.org wrote:
There's been lots of requests to have VirtIO in GENERIC for i386
Hi,
- Original Message -
From: FreeBSD Tinderbox tinder...@freebsd.org
To: FreeBSD Tinderbox tinder...@freebsd.org, curr...@freebsd.org,
i...@freebsd.org
Sent: Friday, October 12, 2012 6:11:27 AM
Subject: [head tinderbox] failure on i386/i386
TB --- 2012-10-12 04:50:01 -
- Original Message -
From: Dieter BSD dieter...@engineer.com
To: hack...@freebsd.org, curr...@freebsd.org
Sent: Sunday, July 22, 2012 1:19:32 AM
Subject: Re: Awful FreeBSD 9 block IO performance in KVM
da0: 3.300MB/s transfers
da0: Command Queueing enabled
On a recent -current, I got the following panic from deadlkres:
Assertion wchan != NULL failed at /usr/src-nfs/sys/kern/subr_sleepqueue.c:680
Tracing pid 0 tid 100058 td 0xff00024bf7a0
kdb_enter() at kdb_enter+0x3d
panic() at panic+0x176
sleepq_type() at sleepq_type+0x56
deadlkres() at
29 matches
Mail list logo
