>
>
> So here's what I will attempt to test:
> - Create thin vmdk @ 10TB with vSphere fat client: PASS
> - Create lazy zeroed vmdk @ 10 TB with vSphere fat client: PASS
> - Create eager zeroed vmdk @ 10 TB with vSphere web client: PASS! (took 1
> hour)
> - Create thin vmdk @ 10TB with vSphere web c
Am 27.03.15 um 01:05 schrieb Phil Harman:
SFPs? Are you know kidding me? For my home lab I bought a pair of
X540-T2 cards, which will even run over Cat5 for about a metre. They
use a lot more power than SFP though :)
He he… 1m doesn't buy you much in a server room, so we're using almost
only
SFPs? Are you know kidding me? For my home lab I bought a pair of X540-T2
cards, which will even run over Cat5 for about a metre. They use a lot more
power than SFP though :)
No issues at all with illumos or VMware.
> On 26 Mar 2015, at 16:45, Jeff Stockett wrote:
>
> I would concur with what
I use the myricom 10g cards (myri10g) they work just fine.
From: OmniOS-discuss [mailto:omnios-discuss-boun...@lists.omniti.com] On Behalf
Of Doug Hughes
Sent: Thursday, March 26, 2015 09:25 AM
To: omnios-discuss
Subject: [OmniOS-discuss] best or preferred 10g card for OmniOS
any recommend
Just remember that only WRITE_SAME and UNMAP are on stock illumos. If you want
the other two, you either get NexentaStor or you start an effort to upstream
them from illumos-nexenta.
Dan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
On Thu, Mar 26, 2015 at 1:05 PM, Dan McDonald wrote:
>
> WRITE_SAME is one of the four VAAI primitives. Nexenta wrote this code
> for NS, and upstreamed two of them:
>
> WRITE_SAME is "hardware assisted erase".
>
> UNMAP is "hardware assisted freeing".
>
> Those are in upstream illumos.
>
> ATS
So I was still having issues with virtio performance. I’ve finally determined
that its the child zone that is capping the throughput at 85mbps.
If I halt the zone and launch the same VM from the GZ I get 955mbps.
Another thing…the virtio driver in Centos6.6 does not work well with OmniOS kvm.
Is now back online, and cleaned of r151014 packages that shouldn't have been
there.
Thank you!
Dan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
Is offline for now. I'm trying to get rid of the 014 crud I accidentally
pushed into it on Tuesday. Those packages were just illumos-omnios ones, which
are just still the master branch of illumos-omnios.
Dan
___
OmniOS-discuss mailing list
OmniOS-di
Generally speaking the Intel ones are preferable, because Intel does the best
job of keeping those drivers up to date for all open-source platforms.
Just pushed into illumos, and coming soon to r151014 is OPEN-SOURCE support for
Broadcom NetXtreme II (now owned by QLogic) 10GigE (the "bnxe" dri
On Mar 26, 2015, at 12:24 PM, Doug Hughes wrote:
>
> any recommendations? We're having some pretty big problems with the
> Solarflare card and driver dropping network under high load. We eliminated
> LACP as a culprit, and the switch.
>
> Intel? Chelsio? other?
I’ve had a pretty good experien
> On Mar 26, 2015, at 11:47 AM, wuffers wrote:
> It looks like I'll have to make do with lazy zeroed or thin provisioned disks
> of 10TB+ for my Veeam tests, if it doesn't cause another kernel panic. I'm
> hesitant to create these now during business hours (and I shouldn't be..
> these are no
Regarding X520 and SFP+.. We tend to use Amphenol. Do those work ok?
On Thu, Mar 26, 2015 at 12:51 PM, Doug Hughes wrote:
> Thanks guys! (also, if anybody has some advice or contrary experience with
> SolarFlare (5162), I'd love to hear it. Right now they are pretty much
> unusable under load,
Thanks guys! (also, if anybody has some advice or contrary experience with
SolarFlare (5162), I'd love to hear it. Right now they are pretty much
unusable under load, though iperf tends to work fine.
On Thu, Mar 26, 2015 at 12:36 PM, Schweiss, Chip wrote:
> The Intel X520's and the Supermicro
I would concur with what Chip said. We’ve had good luck with the Intel X520s
setup with LACP to a Nexus 5000 – and also have a few X540s. The X520s are a
bit picky about SFPs but Appoved makes one that works and is reasonably
affordable.
From: OmniOS-discuss [mailto:omnios-discuss-boun...@lis
The Intel X520's and the Supermicro equivalents are rock solid. The
X540 probably is too, I just haven't used it. I prefer the Supermicro
branded Intel cards because the firmware is not as picky about the twin-ax
cables used.
-Chip
On Thu, Mar 26, 2015 at 11:24 AM, Doug Hughes wrote:
> any
any recommendations? We're having some pretty big problems with the Solarflare
card and driver dropping network under high load. We eliminated LACP as a
culprit, and the switch.
Intel? Chelsio? other?
- Doug___
OmniOS-discuss mailing list
OmniOS-discu
On Thu, Mar 26, 2015 at 11:37 AM, Dan McDonald wrote:
> I mentioned earlier:
>
> > I know Nexenta's done a LOT of improvements on this in illumos-nexenta.
> It might be time to upstream some of what they've done. I know it's a
> moving target (COMSTAR is not a well-written subsystem), so it may
I mentioned earlier:
> I know Nexenta's done a LOT of improvements on this in illumos-nexenta. It
> might be time to upstream some of what they've done. I know it's a moving
> target (COMSTAR is not a well-written subsystem), so it may take some
> unravelling.
I was looking at Nexenta's chan
> On Mar 26, 2015, at 11:04 AM, Jorge Schrauwen wrote:
>
> Do you have the right mailing list? Seems odd to send it here as only omniti
> people should have access.
Wrong mailing list.
BUT the "bloody" repo server apparently received packages for 014 when it
shouldn't have. And some people
There is no 014 on the bloody repo server, and 014 is NOT OFFICIALLY OUT YET.
An automatic build of some sort pushed out r151014 packages to
http://pkg.omniti.com/omnios/bloody/ and it shouldn't have. I'm cleaning up
the repo now.
If you updated via bloody, revert to an 013 BE now.
Dan
Do you have the right mailing list? Seems odd to send it here as only
omniti people should have access.
On 2015-03-26 16:03, Dan McDonald wrote:
Subject says it all. It's possible *I* did, but if someone else has
built omnios-build on or for r151014 without setting PKGSRVR, please
let me kno
Subject says it all. It's possible *I* did, but if someone else has built
omnios-build on or for r151014 without setting PKGSRVR, please let me know ASAP.
Thanks,
Dan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.
1.) It's "Dan" one n. :)
2.) Are you seeing 014 packages in the "bloody" repo? You shouldn't be. But
shoot, there it is.
I'll clean up the bloody repo today.
Sorry,
Dan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.
I have updated 151012 to 151014 and installed
the open-vm-tools (on ESXi 6.0.) for some basic tests.
Installation via pkg install open-vm-tools was ok and ESXi 6.0 shows
tools running (3rd party tools)
but vmxnet3 is missing. Is vmxnet3 not a part of the open-vm-tools?
Gea
Hi Dann,
Running latest Bloody , and after running a weekly check of available updates :
pkg update -nv
Creating Plan (Running solver): |
pkg update: No solution was found to satisfy constraints
Plan Creation: Package solver has not found a solution to update to latest
available versions.
This m
26 matches
Mail list logo
