Re: [OmniOS-discuss] Similar tools like flowadm

4 мая 2016 г. 4:10:45 CEST, Dan McDonald пишет: > >> On May 3, 2016, at 7:54 PM, Ergi Thanasko >wrote: >> >> Hi guys, >> Is there any tools like flowadm that can control bandwidth usage on >a per pool basis? instead of host ip. Also flowadm will

Re: [OmniOS-discuss] Similar tools like flowadm

> On May 3, 2016, at 7:54 PM, Ergi Thanasko wrote: > > Hi guys, > Is there any tools like flowadm that can control bandwidth usage on a per > pool basis? instead of host ip. Also flowadm will use both in/out summary to > limit bandwidth. We are looking for

Re: [OmniOS-discuss] 151018 "entire" missing library/python-2/jsonrpclib-26?

> On May 3, 2016, at 5:50 PM, Volker A. Brandt wrote: > > > I guess that's because library/python-2/jsonrpclib-26 is missing from > the "entire" incorporation, thus it's not version-locked into 151016. > > Right? :-) Correct, and probably not a huge deal, because you shouldn't

[OmniOS-discuss] Similar tools like flowadm

Hi guys, Is there any tools like flowadm that can control bandwidth usage on a per pool basis? instead of host ip. Also flowadm will use both in/out summary to limit bandwidth. We are looking for something deeper that we can seperate control on incoming or outgoing or traffic at a pool level

[OmniOS-discuss] 151018 "entire" missing library/python-2/jsonrpclib-26?

Hi Dan! On a system running 151016, I was trying to update to 151018. Now I know that it will not work because I am using some ms.omniti.com pkgs which will effectively lock the system into the 151016 version of the "entire" incorporation. To my surprise, the system offered to update the

Re: [OmniOS-discuss] lipkg and updates

Dan, > Clearly I'm missing something about lipkg zones and pkg update. > > "zoneadm list -cv" shows all of the zones as lipkg, right? > Absolutely, yes. > > I have some recently built boxes that appear to behave, but on older > > (as in still 151014 but a few months back) systems the zones

Re: [OmniOS-discuss] lipkg and updates

> On May 3, 2016, at 4:15 PM, Peter Tribble wrote: > > Clearly I'm missing something about lipkg zones and pkg update. "zoneadm list -cv" shows all of the zones as lipkg, right? > I have some recently built boxes that appear to behave, but on older > (as in still

[OmniOS-discuss] lipkg and updates

Clearly I'm missing something about lipkg zones and pkg update. I have some recently built boxes that appear to behave, but on older (as in still 151014 but a few months back) systems the zones don't seem to follow the global zone when I run pkg update. I utter: $ pfexec pkg update ntp openssl

Re: [OmniOS-discuss] Installation Boot hangs after CPU/USB initialization - Intel Motherboard

> On May 3, 2016, at 2:15 PM, Svavar Örn Eysteinsson > wrote: > > did we dig up some ancient, or forgotten demon? :) Not really. But your symptoms reminded me of s similar problem a long time ago (2011-2012) where a system PCI ID was causing a crusty old driver that

Re: [OmniOS-discuss] Installation Boot hangs after CPU/USB initialization - Intel Motherboard

did we dig up some ancient, or forgotten demon? :) Thank you all for the support, really. I can see the light now. Best regards, Svavar - Reykjavik, Iceland Sent from mobile... > On 3. maí 2016, at 17:34, Dan McDonald wrote: > > >>> On May 3, 2016, at 1:01 PM, Eric

Re: [OmniOS-discuss] Installation Boot hangs after CPU/USB initialization - Intel Motherboard

> On May 3, 2016, at 1:01 PM, Eric Sproul wrote: > >> p.s. What does this parameter actually do? Can't find any good info on this >> one from mr.google. It disables the intel_nhmex driver from attaching, regardless of device detection. I *thought* that nhm and

Re: [OmniOS-discuss] Installation Boot hangs after CPU/USB initialization - Intel Motherboard

On Tue, 3 May 2016 13:01:57 -0400 Eric Sproul wrote: > > https://illumos.org/issues/4281 seems relevant. Odd that searching > src.illumos.org for "nhmex" turns up only the package manifest. Don't > see any driver source. > The bug report you are referring to claim

Re: [OmniOS-discuss] Installation Boot hangs after CPU/USB initialization - Intel Motherboard

On Tue, May 3, 2016 at 12:38 PM, Svavar Örn Eysteinsson wrote: > WOW! :) > > disable-intel_nhmex=true did the magic > disable-intel_nhm=true did nothing. > > Thank you so much Dan. > > p.s. What does this parameter actually do? Can't find any good info on this > one from

[OmniOS-discuss] SECURITY UPDATE - OpenSSL to 1.0.2h and NTP to 4.2.8p7

Please utter "pkg update" on your supported OmniOS releases: r151014 (LTS), r151016 (old Stable), and r151018 (current Stable). Here's the sample 014 "pkg update -nv" output: | Changed packages: | omnios | library/security/openssl | 1.0.2.7-0.151014:20160301T224747Z ->

Re: [OmniOS-discuss] Installation Boot hangs after CPU/USB initialization - Intel Motherboard

> On May 3, 2016, at 11:26 AM, Svavar Örn Eysteinsson > wrote: > > pci86,e2 (pciex8086,3423), instance #0 > pci86,e2 (pciex8086,3438) (driver not attached) > The ONLY POSSIBLE thing I can imagine is that we're seeing both of those pciex identifiers

Re: [OmniOS-discuss] Installation Boot hangs after CPU/USB initialization - Intel Motherboard

Thanks so much for the reply Dan. With pretty much every default settings in the BIOS enabled Solaris will boot up 100% fine. Output of dmesg is here : http://pastebin.com/hRtCwZrC prtconf -d will display the following information : System Configuration:

Re: [OmniOS-discuss] Installation Boot hangs after CPU/USB initialization - Intel Motherboard

If you can boot Solaris on this box, please share the output of: prtconf -d I'm very curious to see if there's some sort of bizarre-corner-case PCI ID collision. Dan ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com

Re: [OmniOS-discuss] Installation Boot hangs after CPU/USB initialization - Intel Motherboard

Hi again. I wanted to ask for the last time if anyone got some tips on debug'ing the installation of OmniOS. As stated of the emails before, I have tried -v and also -B immu-enable=true (as someone hinted me , http://blahg.josefsipek.net/?p=488 ) I have disabled pretty much anything in the

Re: [OmniOS-discuss] Wiki is slightly broken

Great, thanks Dale! On 2 May 2016 17:03, "Dale Ghent" wrote: > > > On May 2, 2016, at 10:38 AM, Jacob Vosmaer > wrote: > > > > Hi Dale, > > > > Yes, the wiki page renders correctly for me in Chrome now! I see a > quasi-warning (no green lock) which