I’ve applied Neel’s patch against r273182 and am currently abusively testing it
on a mix of HP DL385s w/ dual Opteron 6378SE, & Single socket AMD G34s ( some
with Opteron 6200s, some with 6300s ), about 15 boxes in total - so far so
good.
Seriously awesome work Gentlemen.
cheers,
-bp
> On Oc
After a few days of extensive testing and abuse, i’ve run into no new issues or
unknowns what so ever. Everything that worked before still works now ( and a
few bugs from fixed from HEAD ).
Thus, I have gone ahead and pushed r273182 w/ Neel’s patch out to about 80 of
the assorted AMD boxes in
Hi all,
So I just update one of my systems to 10-STABLE r273710 ( GENERIC kernel config
) and now all the bhyve guests are unable to connect to the network ( be it
linux, freebsd, or openbsd ). They guests see their network interfaces fine -
but they are unable to connect to anything. Additiona
at 3:42 PM, Allan Jude wrote:
>
> On 2014-10-26 18:36, Benjamin Perrault wrote:
>> Hi all,
>>
>> So I just update one of my systems to 10-STABLE r273710 ( GENERIC kernel
>> config ) and now all the bhyve guests are unable to connect to the network (
>> b
Digging thru my system - I have (2) stock FreeBSD system (HP DL385s) at
r274859 - bhyve seems to be working fine for FreeBSD and Linux guests. r274900
also appears to be good.
I know it’s not a ton of help of resolving the issue
cheers,
-bp
> On Nov 22, 2014, at 7:20 PM, Shawn Webb wrote:
> On May 20, 2015, at 1:56 PM, Michael Dexter wrote:
>
> On 5/20/15 12:24 PM, Joseph Mulloy wrote:
>> Are there videos of the talks given at bhyvecon2015? I've been looking for
>> them on YouTube and I haven't been able to find them. Specifically I'm
>> looking
>> for the video of Peter Grehan'
It’s a bit limited. IMO, it is more a mutation of bhyve then a direct port. It
can only run Linux at the moment (or at least, I can’t get freebsd to run under
it, for example - and that seems to conform to the github documentation ).
SVM, PCI passthrough, VMX host & EPT where removed. It is sin
> On Jul 28, 2015, at 6:55 PM, Larry Rosenman wrote:
>
> On 2015-07-28 20:44, Michael Dexter wrote:
>> On 7/28/15 1:17 PM, Kegan Myers wrote:
>>> Make sure you have permissions. Docker isn't good at figuring out that you
>>> need sudo or other permissions to talk to the socket.
>> Also, do make
