From bdha at mirrorshades.net  Mon Oct  1 01:04:35 2012
From: bdha at mirrorshades.net (Bryan Horstmann-Allen)
Date: Mon, 1 Oct 2012 01:04:35 -0400
Subject: [OmniOS-discuss] Creating KVMs
Message-ID: <20121001050435.GA25679@lab.pobox.com>

Attempted to spin my first KVM on OmniOS tonight and ran into a problem:

  # ls -l /dev/kvm
  /dev/kvm: No such file or directory

  # uname -a
  SunOS troop 5.11 omnios-eae537b i86pc i386 i86pc

  # prtdiag  | grep Intel
  Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz CPU1    
  Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz CPU2    

I'm using this same machine model (Fujitsu RX200 S7) with Joyent SDC, and KVM
is enabled there. I don't think I need to enable virtualization in the BIOS.

Is KVM not enabled on this release?

Cheers.
-- 
bdha
cyberpunk is dead. long live cyberpunk.

From esproul at omniti.com  Mon Oct  1 01:24:02 2012
From: esproul at omniti.com (Eric Sproul)
Date: Mon, 1 Oct 2012 01:24:02 -0400
Subject: [OmniOS-discuss] Creating KVMs
In-Reply-To: <20121001050435.GA25679@lab.pobox.com>
References: <20121001050435.GA25679@lab.pobox.com>
Message-ID: <CA+QY2RQ+yZhsyNSZb3-y3u8c4DDfSmZ+2sqcF5-OXRAtHcwkLQ@mail.gmail.com>

On Mon, Oct 1, 2012 at 1:04 AM, Bryan Horstmann-Allen
<bdha at mirrorshades.net> wrote:
> Attempted to spin my first KVM on OmniOS tonight and ran into a problem:
>
>   # ls -l /dev/kvm
>   /dev/kvm: No such file or directory

Bryan,
Do you have both driver/virtualization/kvm and system/kvm installed
(you should, it's part of "entire") and have the kvm driver loaded?

Eric

From bdha at mirrorshades.net  Mon Oct  1 01:58:57 2012
From: bdha at mirrorshades.net (Bryan Horstmann-Allen)
Date: Mon, 1 Oct 2012 01:58:57 -0400
Subject: [OmniOS-discuss] Creating KVMs
In-Reply-To: <CA+QY2RQ+yZhsyNSZb3-y3u8c4DDfSmZ+2sqcF5-OXRAtHcwkLQ@mail.gmail.com>
References: <20121001050435.GA25679@lab.pobox.com>
	<CA+QY2RQ+yZhsyNSZb3-y3u8c4DDfSmZ+2sqcF5-OXRAtHcwkLQ@mail.gmail.com>
Message-ID: <20121001055856.GA22530@lab.pobox.com>

+------------------------------------------------------------------------------
| On 2012-10-01 01:24:02, Eric Sproul wrote:
| 
| Do you have both driver/virtualization/kvm and system/kvm installed
| (you should, it's part of "entire") and have the kvm driver loaded?

  # pkg list | grep kvm
  driver/virtualization/kvm                         1.0.2-0.151002             i--
  system/kvm                                        1.0.2-0.151002             i--

  # modinfo -c | grep -i kvm
  # 

  # add_drv -v -n kvm
  Reboot client to install driver.
  Driver (kvm) installed.

  # grep kvm /etc/name_to_major 
  kvm 264

  # modinfo | grep kvm
  #

  # modload /kernel/drv/amd64/kvm 
  can't load module: No such device or address

Systems hangs shortly after reboot. Sadface.

It may be related to Sandy Bridge, though my SmartOS boxes usually took a bit
longer than ~30s to hang themselves.

Will try to get this into /etc/system

  set pcplusmp:apic_timer_preferred_mode=0

to see if that fixes it.
-- 
bdha
cyberpunk is dead. long live cyberpunk.

From esproul at omniti.com  Mon Oct  1 02:29:20 2012
From: esproul at omniti.com (Eric Sproul)
Date: Mon, 1 Oct 2012 02:29:20 -0400
Subject: [OmniOS-discuss] Creating KVMs
In-Reply-To: <20121001055856.GA22530@lab.pobox.com>
References: <20121001050435.GA25679@lab.pobox.com>
	<CA+QY2RQ+yZhsyNSZb3-y3u8c4DDfSmZ+2sqcF5-OXRAtHcwkLQ@mail.gmail.com>
	<20121001055856.GA22530@lab.pobox.com>
Message-ID: <CA+QY2RTcShy75vbnRa5FXepBaMsjY1J7OWiaONHnHmvfaRe6Dg@mail.gmail.com>

On Mon, Oct 1, 2012 at 1:58 AM, Bryan Horstmann-Allen
<bdha at mirrorshades.net> wrote:
> Systems hangs shortly after reboot. Sadface.

Also try in /etc/system:

set apix_enable=0

IIRC, that fixed the hangs for our Sandy Bridge boxes.

You'll probably also want "set hires_tick=1" if you're not doing that already.

Eric

From bdha at mirrorshades.net  Tue Oct  2 20:23:23 2012
From: bdha at mirrorshades.net (Bryan Horstmann-Allen)
Date: Tue, 2 Oct 2012 20:23:23 -0400
Subject: [OmniOS-discuss] Creating KVMs
In-Reply-To: <CA+QY2RTcShy75vbnRa5FXepBaMsjY1J7OWiaONHnHmvfaRe6Dg@mail.gmail.com>
References: <20121001050435.GA25679@lab.pobox.com>
	<CA+QY2RQ+yZhsyNSZb3-y3u8c4DDfSmZ+2sqcF5-OXRAtHcwkLQ@mail.gmail.com>
	<20121001055856.GA22530@lab.pobox.com>
	<CA+QY2RTcShy75vbnRa5FXepBaMsjY1J7OWiaONHnHmvfaRe6Dg@mail.gmail.com>
Message-ID: <20121003002322.GA28338@lab.pobox.com>

+------------------------------------------------------------------------------
| On 2012-10-01 02:29:20, Eric Sproul wrote:
| 
| set apix_enable=0
| 
| IIRC, that fixed the hangs for our Sandy Bridge boxes.

The fix via Joyent was:

  set pcplusmp:apic_timer_preferred_mode=0
  set apix_enable=0

Which iirc they were thinking about making default (not sure how far that got).

I'll update the wiki, though if it's safe to do so, might want to consider
setting those by default as well.

Loading KVM and reboot into a hang sort of stinks. :-)
 
| You'll probably also want "set hires_tick=1" if you're not doing that already.

Do you have a reference for that?
-- 
bdha
cyberpunk is dead. long live cyberpunk.

From gkuri at ieee.org  Wed Oct  3 13:24:26 2012
From: gkuri at ieee.org (Gabriel Kuri)
Date: Wed, 3 Oct 2012 10:24:26 -0700
Subject: [OmniOS-discuss] Installer Crashes While 'Probing for Device Nodes'
Message-ID: <CAO3KpR3pyj6PAuadAcx_9RrFVDoMSxg-2tT1pHAW=HUe9aTYaQ@mail.gmail.com>

I downloaded the stable release of OmniOS and tried to install on a
SuperMicro Superserver 6025w. I'm running an LSI Logic 9211-8i 6Gbps
HBA in Initiator Target mode with 2 SSD drives and 6 3TB Seagate
drives.

When the installer gets to "Probing for Device Nodes" it crashes and reboots.

I also tried the "bloody" release and it did the same thing.

Any ideas on how to troubleshoot or what I can do?

Thanks,
Gabe

From john at firecrest.eclipse.co.uk  Wed Oct  3 14:25:28 2012
From: john at firecrest.eclipse.co.uk (John Ratcliffe)
Date: Wed, 03 Oct 2012 19:25:28 +0100
Subject: [OmniOS-discuss] Installer Crashes While 'Probing for Device
 Nodes'
In-Reply-To: <CAO3KpR3pyj6PAuadAcx_9RrFVDoMSxg-2tT1pHAW=HUe9aTYaQ@mail.gmail.com>
References: <CAO3KpR3pyj6PAuadAcx_9RrFVDoMSxg-2tT1pHAW=HUe9aTYaQ@mail.gmail.com>
Message-ID: <506C8318.6060402@firecrest.eclipse.co.uk>


Gabriel Kuri wrote:
> I downloaded the stable release of OmniOS and tried to install on a
> SuperMicro Superserver 6025w. I'm running an LSI Logic 9211-8i 6Gbps
> HBA in Initiator Target mode with 2 SSD drives and 6 3TB Seagate
> drives.
>
> When the installer gets to "Probing for Device Nodes" it crashes and reboots.
>
> I also tried the "bloody" release and it did the same thing.
>
> Any ideas on how to troubleshoot or what I can do?
>
> Thanks,
> Gabe
I recently had the same problem with OmniOS and FreeBSD.

The solution was to load the "Fail-Safe" options in the BIOS. Both OS 
installed fine.

I tried resetting the optimised BIOS options after install, but then 
they would not load.

John

From gkuri at ieee.org  Wed Oct  3 14:31:16 2012
From: gkuri at ieee.org (Gabriel Kuri)
Date: Wed, 3 Oct 2012 11:31:16 -0700
Subject: [OmniOS-discuss] Installer Crashes While 'Probing for Device
	Nodes'
In-Reply-To: <506C8318.6060402@firecrest.eclipse.co.uk>
References: <CAO3KpR3pyj6PAuadAcx_9RrFVDoMSxg-2tT1pHAW=HUe9aTYaQ@mail.gmail.com>
	<506C8318.6060402@firecrest.eclipse.co.uk>
Message-ID: <CAO3KpR0T_oZc_mXzBz38H+c60iZwRDYpbSAdNW3Qq-QoiuYkAw@mail.gmail.com>

Unfortunately my BIOS only has "Load Defaults", which I've already tried.

Thanks,
Gabe

On Wed, Oct 3, 2012 at 11:25 AM, John Ratcliffe
<john at firecrest.eclipse.co.uk> wrote:
>
> Gabriel Kuri wrote:
>>
>> I downloaded the stable release of OmniOS and tried to install on a
>> SuperMicro Superserver 6025w. I'm running an LSI Logic 9211-8i 6Gbps
>> HBA in Initiator Target mode with 2 SSD drives and 6 3TB Seagate
>> drives.
>>
>> When the installer gets to "Probing for Device Nodes" it crashes and
>> reboots.
>>
>> I also tried the "bloody" release and it did the same thing.
>>
>> Any ideas on how to troubleshoot or what I can do?
>>
>> Thanks,
>> Gabe
>
> I recently had the same problem with OmniOS and FreeBSD.
>
> The solution was to load the "Fail-Safe" options in the BIOS. Both OS
> installed fine.
>
> I tried resetting the optimised BIOS options after install, but then they
> would not load.
>
> John

From Rob at Logan.com  Wed Oct  3 14:39:56 2012
From: Rob at Logan.com (Rob Logan)
Date: Wed, 03 Oct 2012 14:39:56 -0400
Subject: [OmniOS-discuss] Installer Crashes While 'Probing for Device
 Nodes'
In-Reply-To: <CAO3KpR0T_oZc_mXzBz38H+c60iZwRDYpbSAdNW3Qq-QoiuYkAw@mail.gmail.com>
References: <CAO3KpR3pyj6PAuadAcx_9RrFVDoMSxg-2tT1pHAW=HUe9aTYaQ@mail.gmail.com>
	<506C8318.6060402@firecrest.eclipse.co.uk>
	<CAO3KpR0T_oZc_mXzBz38H+c60iZwRDYpbSAdNW3Qq-QoiuYkAw@mail.gmail.com>
Message-ID: <506C867C.40901@Logan.com>


 > Unfortunately my BIOS only has

update it anyway.. its an apic, or S3 kinda issue... stopping grub and "e"
the boot line to add a "-v" will tell you what bios option it doesn't like.

			Rob

From henson at acm.org  Wed Oct  3 14:50:19 2012
From: henson at acm.org (Paul B. Henson)
Date: Wed, 03 Oct 2012 11:50:19 -0700
Subject: [OmniOS-discuss] Installer Crashes While 'Probing for Device
 Nodes'
In-Reply-To: <CAO3KpR3pyj6PAuadAcx_9RrFVDoMSxg-2tT1pHAW=HUe9aTYaQ@mail.gmail.com>
References: <CAO3KpR3pyj6PAuadAcx_9RrFVDoMSxg-2tT1pHAW=HUe9aTYaQ@mail.gmail.com>
Message-ID: <506C88EB.1060301@acm.org>

On 10/3/2012 10:24 AM, Gabriel Kuri wrote:

> Any ideas on how to troubleshoot or what I can do?

Turn on debugging and get a backtrace when it panics:

https://blogs.oracle.com/dmick/entry/diagnosing_kernel_hangs_panics_with



From gkuri at ieee.org  Wed Oct  3 19:54:31 2012
From: gkuri at ieee.org (Gabriel Kuri)
Date: Wed, 3 Oct 2012 16:54:31 -0700
Subject: [OmniOS-discuss] Installer Crashes While 'Probing for Device
	Nodes'
In-Reply-To: <506C867C.40901@Logan.com>
References: <CAO3KpR3pyj6PAuadAcx_9RrFVDoMSxg-2tT1pHAW=HUe9aTYaQ@mail.gmail.com>
	<506C8318.6060402@firecrest.eclipse.co.uk>
	<CAO3KpR0T_oZc_mXzBz38H+c60iZwRDYpbSAdNW3Qq-QoiuYkAw@mail.gmail.com>
	<506C867C.40901@Logan.com>
Message-ID: <CAO3KpR2EesBi-w3_6sGqVUAv+7mMBWZifbmw-18FUri+FLfkOQ@mail.gmail.com>

I think I'm crashing on this particular issue:

     https://www.illumos.org/issues/3080

The stack trace appears to be the same. How can I tell whether this
change has been integrated into the OmniOS revision I'm trying to
boot? Is there any easy way to tell which revision of illumos-gate a
specific version of OmniOS utilizes?

Thanks,
Gabe

On Wed, Oct 3, 2012 at 11:39 AM, Rob Logan <Rob at logan.com> wrote:
>
>> Unfortunately my BIOS only has
>
> update it anyway.. its an apic, or S3 kinda issue... stopping grub and "e"
> the boot line to add a "-v" will tell you what bios option it doesn't like.
>
>                         Rob
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

From gate03 at landcroft.co.uk  Wed Oct  3 20:05:35 2012
From: gate03 at landcroft.co.uk (gate03 at landcroft.co.uk)
Date: Thu, 4 Oct 2012 01:05:35 +0100
Subject: [OmniOS-discuss] Installer Crashes While 'Probing for
	DeviceNodes'
Message-ID: <57388.1349309135@landcroft.co.uk>

This looks like what I was seeing a few days ago.  I've not had a chance yet to try with 'safe' BIOS values but if the dcopy_free bug is the root-cause, safe BIOS values are merely shifting or masking the problem.

Michael.

On Thu 04/10/12 00:54 , Gabriel Kuri <gkuri at ieee.org> wrote:

> I think I'm crashing on this particular issue:
> https://www.illumos.org/issues/3080
> The stack trace appears to be the same. How can I tell whether this
> change has been integrated into the OmniOS revision I'm trying to
> boot? Is there any easy way to tell which revision of illumos-gate a
> specific version of OmniOS utilizes?

From esproul at omniti.com  Thu Oct  4 10:07:12 2012
From: esproul at omniti.com (Eric Sproul)
Date: Thu, 4 Oct 2012 07:07:12 -0700
Subject: [OmniOS-discuss] Installer Crashes While 'Probing for
	DeviceNodes'
In-Reply-To: <57388.1349309135@landcroft.co.uk>
References: <57388.1349309135@landcroft.co.uk>
Message-ID: <CA+QY2RSJG7f5nFx-k68uj2-4pWNf11_8pmrSi=zm9A1XmnTnDA@mail.gmail.com>

Gabriel,
We pulled Rich's fix for 3080 into bloody, but probably after the last
ISO spin.  I will do another spin so you can try it.

Eric

From filip.francis at telenet.be  Thu Oct  4 10:28:55 2012
From: filip.francis at telenet.be (Filip Francis)
Date: Thu, 04 Oct 2012 16:28:55 +0200
Subject: [OmniOS-discuss] Compiling runtime/perl-$NODOTVER
Message-ID: <506D9D27.4080800@telenet.be>

Hi guys,


I am trying out your omnios-build tree.
But i can not seem to find a way to compile runtime/perl-$NODOTVER
whatever i do i always get Unknown package: runtime/perl-

so tried ./buildctl runtime/perl-1542 or runtime/perl-15.4.2
But no luck

Could somebody help
Filip
Thanks in advance


From gkuri at ieee.org  Thu Oct  4 10:55:25 2012
From: gkuri at ieee.org (Gabriel Kuri)
Date: Thu, 4 Oct 2012 07:55:25 -0700
Subject: [OmniOS-discuss] Installer Crashes While 'Probing for
	DeviceNodes'
In-Reply-To: <CA+QY2RSJG7f5nFx-k68uj2-4pWNf11_8pmrSi=zm9A1XmnTnDA@mail.gmail.com>
References: <57388.1349309135@landcroft.co.uk>
	<CA+QY2RSJG7f5nFx-k68uj2-4pWNf11_8pmrSi=zm9A1XmnTnDA@mail.gmail.com>
Message-ID: <CAO3KpR2vTJz7rcF0NUpfaWpYvY24BDVQm6EXt89aTDCp5VCUDw@mail.gmail.com>

Awesome, thanks, let me know, and I'll give it a try.

Gabe

On Thu, Oct 4, 2012 at 7:07 AM, Eric Sproul <esproul at omniti.com> wrote:
> Gabriel,
> We pulled Rich's fix for 3080 into bloody, but probably after the last
> ISO spin.  I will do another spin so you can try it.
>
> Eric
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

From esproul at omniti.com  Thu Oct  4 11:02:48 2012
From: esproul at omniti.com (Eric Sproul)
Date: Thu, 4 Oct 2012 08:02:48 -0700
Subject: [OmniOS-discuss] Compiling runtime/perl-$NODOTVER
In-Reply-To: <506D9D27.4080800@telenet.be>
References: <506D9D27.4080800@telenet.be>
Message-ID: <CA+QY2RR17egbv=ozbt3trO5b9YPZBFLu9X7ZMtosa_wJ-E11qg@mail.gmail.com>

On Thu, Oct 4, 2012 at 7:28 AM, Filip Francis <filip.francis at telenet.be> wrote:
> Hi guys,
>
>
> I am trying out your omnios-build tree.
> But i can not seem to find a way to compile runtime/perl-$NODOTVER
> whatever i do i always get Unknown package: runtime/perl-
>
> so tried ./buildctl runtime/perl-1542 or runtime/perl-15.4.2

Filip,
It looks like buildctl is unable to deal with the shell variable in
the PKG line of perl/build.sh and that is the root cause of your
problem.  We don't need to be that clever in the perl build, so I'm
working on fixing that, but in the mean time you can just cd into the
perl/ directory and run ./build.sh to get those packages.

Eric

From esproul at omniti.com  Thu Oct  4 12:24:30 2012
From: esproul at omniti.com (Eric Sproul)
Date: Thu, 4 Oct 2012 09:24:30 -0700
Subject: [OmniOS-discuss] Installer Crashes While 'Probing for
	DeviceNodes'
In-Reply-To: <CAO3KpR2vTJz7rcF0NUpfaWpYvY24BDVQm6EXt89aTDCp5VCUDw@mail.gmail.com>
References: <57388.1349309135@landcroft.co.uk>
	<CA+QY2RSJG7f5nFx-k68uj2-4pWNf11_8pmrSi=zm9A1XmnTnDA@mail.gmail.com>
	<CAO3KpR2vTJz7rcF0NUpfaWpYvY24BDVQm6EXt89aTDCp5VCUDw@mail.gmail.com>
Message-ID: <CA+QY2RTdK=5_rYeOMF6pB0=YcoRe+a_aM5cWn=tkFVULWqBhEw@mail.gmail.com>

On Thu, Oct 4, 2012 at 7:55 AM, Gabriel Kuri <gkuri at ieee.org> wrote:
> Awesome, thanks, let me know, and I'll give it a try.

Gabe,
Try http://omnios.omniti.com/media/OmniOS_Text_bloody_20121004.iso and
let us know how it goes.

md5 (OmniOS_Text_bloody_20121004.iso) = a42c63ab560017999d2ba847a118aece
sha1 (OmniOS_Text_bloody_20121004.iso) =
0e1c1f6cdd01bf471deffd659fa51669c947185b

Eric

From esproul at omniti.com  Thu Oct  4 12:34:16 2012
From: esproul at omniti.com (Eric Sproul)
Date: Thu, 4 Oct 2012 09:34:16 -0700
Subject: [OmniOS-discuss] Creating KVMs
In-Reply-To: <20121003002322.GA28338@lab.pobox.com>
References: <20121001050435.GA25679@lab.pobox.com>
	<CA+QY2RQ+yZhsyNSZb3-y3u8c4DDfSmZ+2sqcF5-OXRAtHcwkLQ@mail.gmail.com>
	<20121001055856.GA22530@lab.pobox.com>
	<CA+QY2RTcShy75vbnRa5FXepBaMsjY1J7OWiaONHnHmvfaRe6Dg@mail.gmail.com>
	<20121003002322.GA28338@lab.pobox.com>
Message-ID: <CA+QY2RRuL=k8baH6_owWC3fDJ46NnTf8kQTAbQfdg3d=2_HzFQ@mail.gmail.com>

On Tue, Oct 2, 2012 at 5:23 PM, Bryan Horstmann-Allen
<bdha at mirrorshades.net> wrote:
> | You'll probably also want "set hires_tick=1" if you're not doing that already.
>
> Do you have a reference for that?

Theo talked about it on IRC a while back:
http://echelog.com/logs/browse/illumos/1332712800 (search for "hires")

The gist is that it affects the minimum sleep time available.  If a
program wants to "sleep 1ms" the least it can get with the default
tick rate is 10ms.  That leads to a non-trivial amount of busywait or
sleep time and less work getting done, especially for highly
concurrent apps like Reconnoiter and ATS.

Eric

From filip.francis at telenet.be  Thu Oct  4 13:28:03 2012
From: filip.francis at telenet.be (Filip Francis)
Date: Thu, 04 Oct 2012 19:28:03 +0200
Subject: [OmniOS-discuss] Compiling runtime/perl-$NODOTVER
In-Reply-To: <CA+QY2RR17egbv=ozbt3trO5b9YPZBFLu9X7ZMtosa_wJ-E11qg@mail.gmail.com>
References: <506D9D27.4080800@telenet.be>
	<CA+QY2RR17egbv=ozbt3trO5b9YPZBFLu9X7ZMtosa_wJ-E11qg@mail.gmail.com>
Message-ID: <506DC723.6030408@telenet.be>

ERic,
Thanks for the aswer yeah that works indeed figured that out.
What should be the defaukt shekk in what you are compiling?
I am using ksh

Filip

On 10/ 4/12 05:02 PM, Eric Sproul wrote:
> On Thu, Oct 4, 2012 at 7:28 AM, Filip Francis <filip.francis at telenet.be> wrote:
>> Hi guys,
>>
>>
>> I am trying out your omnios-build tree.
>> But i can not seem to find a way to compile runtime/perl-$NODOTVER
>> whatever i do i always get Unknown package: runtime/perl-
>>
>> so tried ./buildctl runtime/perl-1542 or runtime/perl-15.4.2
> Filip,
> It looks like buildctl is unable to deal with the shell variable in
> the PKG line of perl/build.sh and that is the root cause of your
> problem.  We don't need to be that clever in the perl build, so I'm
> working on fixing that, but in the mean time you can just cd into the
> perl/ directory and run ./build.sh to get those packages.
>
> Eric
>


From esproul at omniti.com  Thu Oct  4 13:33:16 2012
From: esproul at omniti.com (Eric Sproul)
Date: Thu, 4 Oct 2012 10:33:16 -0700
Subject: [OmniOS-discuss] Compiling runtime/perl-$NODOTVER
In-Reply-To: <506DC723.6030408@telenet.be>
References: <506D9D27.4080800@telenet.be>
	<CA+QY2RR17egbv=ozbt3trO5b9YPZBFLu9X7ZMtosa_wJ-E11qg@mail.gmail.com>
	<506DC723.6030408@telenet.be>
Message-ID: <CA+QY2RSodwZyqprWYK7qWDpxWHvu4HZ9d=UbC99R+1np1za3FA@mail.gmail.com>

On Thu, Oct 4, 2012 at 10:28 AM, Filip Francis <filip.francis at telenet.be> wrote:
> ERic,
> Thanks for the aswer yeah that works indeed figured that out.
> What should be the defaukt shekk in what you are compiling?
> I am using ksh

Filip,
Our build scripts typically use bash and declare it explicitly at the
top of the script, so it shouldn't matter what shell you are using.

Eric

From henson at acm.org  Thu Oct  4 13:45:28 2012
From: henson at acm.org (Paul B. Henson)
Date: Thu, 04 Oct 2012 10:45:28 -0700
Subject: [OmniOS-discuss] Installer Crashes While 'Probing for
	DeviceNodes'
In-Reply-To: <CA+QY2RSJG7f5nFx-k68uj2-4pWNf11_8pmrSi=zm9A1XmnTnDA@mail.gmail.com>
References: <57388.1349309135@landcroft.co.uk>
	<CA+QY2RSJG7f5nFx-k68uj2-4pWNf11_8pmrSi=zm9A1XmnTnDA@mail.gmail.com>
Message-ID: <506DCB38.9030501@acm.org>

On 10/4/2012 7:07 AM, Eric Sproul wrote:

> We pulled Rich's fix for 3080 into bloody, but probably after the last
> ISO spin.  I will do another spin so you can try it.

Is there an easy way to tell what version of upstream illumos-gate a 
given version of OmniOS is based on? When you guys sync up, do you pull 
in everything (so you could say OmniOS X is current as of illumos-gate 
commit Y, and know all commits prior to Y are included) or do you cherry 
pick which commits to pull in?

Thanks...

From filip.francis at telenet.be  Thu Oct  4 14:19:53 2012
From: filip.francis at telenet.be (Filip Francis)
Date: Thu, 04 Oct 2012 20:19:53 +0200
Subject: [OmniOS-discuss] Compiling runtime/perl-$NODOTVER
In-Reply-To: <CA+QY2RSodwZyqprWYK7qWDpxWHvu4HZ9d=UbC99R+1np1za3FA@mail.gmail.com>
References: <506D9D27.4080800@telenet.be>
	<CA+QY2RR17egbv=ozbt3trO5b9YPZBFLu9X7ZMtosa_wJ-E11qg@mail.gmail.com>
	<506DC723.6030408@telenet.be>
	<CA+QY2RSodwZyqprWYK7qWDpxWHvu4HZ9d=UbC99R+1np1za3FA@mail.gmail.com>
Message-ID: <506DD349.8090801@telenet.be>

Eric thanks
Again.


Had some weird things going with building system/zones/brand/ipkg
It always stopped at the following error:
gcc    -o support support.c /usr/lib/libzonecfg.so.1
ld: warning: file libdladm.so.1: required by /usr/lib/libdlpi.so.1, not 
found
Undefined                       first referenced
  symbol                             in file
dladm_close                         /usr/lib/libdlpi.so.1
dladm_dev2linkid                    /usr/lib/libdlpi.so.1
dladm_phys_info                     /usr/lib/libdlpi.so.1
dladm_walk                          /usr/lib/libdlpi.so.1
dladm_open                          /usr/lib/libdlpi.so.1
dladm_parselink                     /usr/lib/libdlpi.so.1
ld: fatal: symbol referencing errors. No output written to support
collect2: ld returned 1 exit status


So i changed the following ( I am not a programmer)
 From BRAND_CFLAGS="-I./gate-include " to BRAND_CFLAGS="-I./gate-include 
-R/lib -L/lib"
and all lines that contains ISALIST=i386 CC=gcc   to ISALIST=i386 CC=gcc 
CFLAGS="$BRAND_CFLAGS"

Then it would compile

Regards
Filip Francis

On 10/ 4/12 07:33 PM, Eric Sproul wrote:
> On Thu, Oct 4, 2012 at 10:28 AM, Filip Francis <filip.francis at telenet.be> wrote:
>> ERic,
>> Thanks for the aswer yeah that works indeed figured that out.
>> What should be the defaukt shekk in what you are compiling?
>> I am using ksh
> Filip,
> Our build scripts typically use bash and declare it explicitly at the
> top of the script, so it shouldn't matter what shell you are using.
>
> Eric
>


From gkuri at ieee.org  Thu Oct  4 16:05:16 2012
From: gkuri at ieee.org (Gabriel Kuri)
Date: Thu, 4 Oct 2012 13:05:16 -0700
Subject: [OmniOS-discuss] Installer Crashes While 'Probing for
	DeviceNodes'
In-Reply-To: <CA+QY2RTdK=5_rYeOMF6pB0=YcoRe+a_aM5cWn=tkFVULWqBhEw@mail.gmail.com>
References: <57388.1349309135@landcroft.co.uk>
	<CA+QY2RSJG7f5nFx-k68uj2-4pWNf11_8pmrSi=zm9A1XmnTnDA@mail.gmail.com>
	<CAO3KpR2vTJz7rcF0NUpfaWpYvY24BDVQm6EXt89aTDCp5VCUDw@mail.gmail.com>
	<CA+QY2RTdK=5_rYeOMF6pB0=YcoRe+a_aM5cWn=tkFVULWqBhEw@mail.gmail.com>
Message-ID: <CAO3KpR1mhK+F_GTnpm1eb=xFP71eQfzbjMaM13RTEHa3k7HVtw@mail.gmail.com>

Eric,

Thank You, that fixed the kernel panic. I can now install OmniOS.

Gabe

On Thu, Oct 4, 2012 at 9:24 AM, Eric Sproul <esproul at omniti.com> wrote:
> On Thu, Oct 4, 2012 at 7:55 AM, Gabriel Kuri <gkuri at ieee.org> wrote:
>> Awesome, thanks, let me know, and I'll give it a try.
>
> Gabe,
> Try http://omnios.omniti.com/media/OmniOS_Text_bloody_20121004.iso and
> let us know how it goes.
>
> md5 (OmniOS_Text_bloody_20121004.iso) = a42c63ab560017999d2ba847a118aece
> sha1 (OmniOS_Text_bloody_20121004.iso) =
> 0e1c1f6cdd01bf471deffd659fa51669c947185b
>
> Eric

From esproul at omniti.com  Thu Oct  4 18:54:14 2012
From: esproul at omniti.com (Eric Sproul)
Date: Thu, 4 Oct 2012 15:54:14 -0700
Subject: [OmniOS-discuss] Installer Crashes While 'Probing for
	DeviceNodes'
In-Reply-To: <506DCB38.9030501@acm.org>
References: <57388.1349309135@landcroft.co.uk>
	<CA+QY2RSJG7f5nFx-k68uj2-4pWNf11_8pmrSi=zm9A1XmnTnDA@mail.gmail.com>
	<506DCB38.9030501@acm.org>
Message-ID: <CA+QY2RT+ML+dsk16Du-jvPisoEmot7LiGRBYjDYMiuV8bsFcfQ@mail.gmail.com>

On Thu, Oct 4, 2012 at 10:45 AM, Paul B. Henson <henson at acm.org> wrote:
> Is there an easy way to tell what version of upstream illumos-gate a given
> version of OmniOS is based on? When you guys sync up, do you pull in
> everything (so you could say OmniOS X is current as of illumos-gate commit
> Y, and know all commits prior to Y are included) or do you cherry pick which
> commits to pull in?

Unfortunately there isn't an easy way.  It might be possible to
include that in our /etc/release but I think that would require
tracking the illumos-gate IDs separately from illumos-omnios ones.
It's the latter that get encoded in various places (uname -v,
/etc/motd) depending on when they are built.

Eric

From kent at watsen.net  Thu Oct  4 19:16:08 2012
From: kent at watsen.net (Kent Watsen)
Date: Thu, 04 Oct 2012 19:16:08 -0400
Subject: [OmniOS-discuss] Installer Crashes While 'Probing for
	DeviceNodes'
In-Reply-To: <CA+QY2RT+ML+dsk16Du-jvPisoEmot7LiGRBYjDYMiuV8bsFcfQ@mail.gmail.com>
References: <57388.1349309135@landcroft.co.uk>
	<CA+QY2RSJG7f5nFx-k68uj2-4pWNf11_8pmrSi=zm9A1XmnTnDA@mail.gmail.com>
	<506DCB38.9030501@acm.org>
	<CA+QY2RT+ML+dsk16Du-jvPisoEmot7LiGRBYjDYMiuV8bsFcfQ@mail.gmail.com>
Message-ID: <506E18B8.8040409@watsen.net>

On 10/4/12 6:54 PM, Eric Sproul wrote:
> On Thu, Oct 4, 2012 at 10:45 AM, Paul B. Henson <henson at acm.org> wrote:
>> Is there an easy way to tell what version of upstream illumos-gate a given
>> version of OmniOS is based on? When you guys sync up, do you pull in
>> everything (so you could say OmniOS X is current as of illumos-gate commit
>> Y, and know all commits prior to Y are included) or do you cherry pick which
>> commits to pull in?
> Unfortunately there isn't an easy way.  It might be possible to
> include that in our /etc/release but I think that would require
> tracking the illumos-gate IDs separately from illumos-omnios ones.
> It's the latter that get encoded in various places (uname -v,
> /etc/motd) depending on when they are built.

I'd be interested in this as well.  It seems similar to how OI could 
indicate it was pulling from ON b151

Thanks,
Kent


From henson at acm.org  Thu Oct  4 20:51:33 2012
From: henson at acm.org (Paul B. Henson)
Date: Thu, 04 Oct 2012 17:51:33 -0700
Subject: [OmniOS-discuss] Installer Crashes While 'Probing for
	DeviceNodes'
In-Reply-To: <CA+QY2RT+ML+dsk16Du-jvPisoEmot7LiGRBYjDYMiuV8bsFcfQ@mail.gmail.com>
References: <57388.1349309135@landcroft.co.uk>
	<CA+QY2RSJG7f5nFx-k68uj2-4pWNf11_8pmrSi=zm9A1XmnTnDA@mail.gmail.com>
	<506DCB38.9030501@acm.org>
	<CA+QY2RT+ML+dsk16Du-jvPisoEmot7LiGRBYjDYMiuV8bsFcfQ@mail.gmail.com>
Message-ID: <506E2F15.3040401@acm.org>

On 10/4/2012 3:54 PM, Eric Sproul wrote:

> Unfortunately there isn't an easy way.

Aw, well...

> It might be possible to include that in our /etc/release but I think
> that would require tracking the illumos-gate IDs separately from
> illumos-omnios ones. It's the latter that get encoded in various
> places (uname -v, /etc/motd) depending on when they are built.

So would the non-easy way then be to clone your git repo, find the 
commit corresponding to the OmniOS release in use, and see if the commit 
of interest from upstream was merged before that?

How do you tell which commit in your git repo a given release is from? 
The one I have installed reports "eae537b" but that doesn't seem to be a 
substring of any commit in your repo?

Thanks...

From jesus at omniti.com  Thu Oct  4 21:14:18 2012
From: jesus at omniti.com (Theo Schlossnagle)
Date: Thu, 4 Oct 2012 21:14:18 -0400
Subject: [OmniOS-discuss] Installer Crashes While 'Probing for
	DeviceNodes'
In-Reply-To: <506E2F15.3040401@acm.org>
References: <57388.1349309135@landcroft.co.uk>
	<CA+QY2RSJG7f5nFx-k68uj2-4pWNf11_8pmrSi=zm9A1XmnTnDA@mail.gmail.com>
	<506DCB38.9030501@acm.org>
	<CA+QY2RT+ML+dsk16Du-jvPisoEmot7LiGRBYjDYMiuV8bsFcfQ@mail.gmail.com>
	<506E2F15.3040401@acm.org>
Message-ID: <CACLsApugbguONA0w2A=auiZJ3MBb=UZ30rFUcznWiqGayRx+Ng@mail.gmail.com>

That uname hash will match a commit in our illumos-omnios tree:

http://omnios.omniti.com/browse.php/core/illumos-omnios

http://omnios.omniti.com/changeset.php/core/illumos-omnios/eae537bad35e09fb6be6db8ea368cd25c07ef77e

If you work backward from there you'll find that
eb36692e8e3d1add7a4530a507a828476656941b is the version of
illumos-gate we branched from.  You are running release.  My bloody
box is  bit easier:

; uname -a
SunOS vitrial 5.11 omnios-33fdde4 i86pc i386 i86pc

commit 33fdde4db8344e316d03e0582b73cdc5608c8f1e
Merge: 1568459 989f280
Author: Theo Schlossnagle <jesus at omniti.com>
Date:   Thu Oct 4 18:11:52 2012 +0000

    Merge branch 'upstream'

So we pulled in from [989f280] on illumos-gate.. which happens to be
the latest commit as of this email. :-)

Hope that helps.


On Thu, Oct 4, 2012 at 8:51 PM, Paul B. Henson <henson at acm.org> wrote:
> On 10/4/2012 3:54 PM, Eric Sproul wrote:
>
>> Unfortunately there isn't an easy way.
>
>
> Aw, well...
>
>
>> It might be possible to include that in our /etc/release but I think
>> that would require tracking the illumos-gate IDs separately from
>> illumos-omnios ones. It's the latter that get encoded in various
>> places (uname -v, /etc/motd) depending on when they are built.
>
>
> So would the non-easy way then be to clone your git repo, find the commit
> corresponding to the OmniOS release in use, and see if the commit of
> interest from upstream was merged before that?
>
> How do you tell which commit in your git repo a given release is from? The
> one I have installed reports "eae537b" but that doesn't seem to be a
> substring of any commit in your repo?
>
> Thanks...
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss



-- 
Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle

From henson at acm.org  Thu Oct  4 21:40:52 2012
From: henson at acm.org (Paul B. Henson)
Date: Thu, 04 Oct 2012 18:40:52 -0700
Subject: [OmniOS-discuss] Installer Crashes While 'Probing for
	DeviceNodes'
In-Reply-To: <CACLsApugbguONA0w2A=auiZJ3MBb=UZ30rFUcznWiqGayRx+Ng@mail.gmail.com>
References: <57388.1349309135@landcroft.co.uk>
	<CA+QY2RSJG7f5nFx-k68uj2-4pWNf11_8pmrSi=zm9A1XmnTnDA@mail.gmail.com>
	<506DCB38.9030501@acm.org>
	<CA+QY2RT+ML+dsk16Du-jvPisoEmot7LiGRBYjDYMiuV8bsFcfQ@mail.gmail.com>
	<506E2F15.3040401@acm.org>
	<CACLsApugbguONA0w2A=auiZJ3MBb=UZ30rFUcznWiqGayRx+Ng@mail.gmail.com>
Message-ID: <506E3AA4.70508@acm.org>

On 10/4/2012 6:14 PM, Theo Schlossnagle wrote:

> http://omnios.omniti.com/changeset.php/core/illumos-omnios/eae537bad35e09fb6be6db8ea368cd25c07ef77e

Hmm, in the local clone of your git repo I made, that commit seems to 
have a different hash?

----
commit a4c87b0f05abfa9d83a1eacb0328160d6bb064ec
Author: Theo Schlossnagle <jesus at omniti.com>
Date:   Tue May 8 22:17:18 2012 +0000

     Remove our dependency on ghostscript and cups.
     This breaks cups support in smbd (spool). If we decide
     we want to enable that, we should only require the cups
     header to build and should consider packaging that in ON.
----

A git show on that commit hash in my local clone seems to be identical 
to the one you referenced on your website. Just with a different hash. I 
cloned it with "git clone 
anon at src.omniti.com:~omnios/core/illumos-omnios", which I found on your 
website.

Hmm, interesting, if I plug the hash from my local clone into your website:

http://omnios.omniti.com/changeset.php/core/illumos-omnios/a4c87b0f05abfa9d83a1eacb0328160d6bb064ec

it finds it, and they look identical. But the first one you listed 
doesn't seem to be in the local clone. I'm confused now 8-/.


From henson at acm.org  Mon Oct  8 19:00:11 2012
From: henson at acm.org (Paul B. Henson)
Date: Mon, 08 Oct 2012 16:00:11 -0700
Subject: [OmniOS-discuss] stable vs "bloody"
Message-ID: <50735AFB.9040501@acm.org>

I was curious, for those of you looking to run OmniOS in production, are 
you planning to use the "stable" release or the "bloody" release?

Terminology wise, "stable" sounds better than "bloody" ;), but if you 
turn that around and call them "stale" and "fresh" it gives a different 
connotation :). It looks like stable includes upstream illumos-gate from 
about 5 months ago, whereas bloody is at the moment fully up-to-date 
with the current upstream. Generally, illumos-gate is intended to be 
production quality at all times, so arguably you're more stable tracking 
it more closely. There's only been a couple of times in the past year or 
so a commit broke anything of note, and I think both of those times it 
was caught pretty quick and backed out or resolved.

From gate03 at landcroft.co.uk  Mon Oct  8 19:10:19 2012
From: gate03 at landcroft.co.uk (gate03 at landcroft.co.uk)
Date: Tue, 9 Oct 2012 00:10:19 +0100
Subject: [OmniOS-discuss] stable vs. bloody
Message-ID: <45916.1349737819@landcroft.co.uk>

Stable can indeed mean stale.  I was unable to install stable owing to the dcopy_free() bug discussed last week on this list, but was able to install bloody and am now running with it, without problems.  So bloody can also mean 'with recent bugs removed'.

On Tue 09/10/12 00:00 , "Paul B. Henson" <henson at acm.org> wrote:

> I was curious, for those of you looking to run OmniOS in production,
> are you planning to use the "stable" release or the "bloody" release?
> Terminology wise, "stable" sounds better than "bloody" ;), but if you 
> turn that around and call them "stale" and "fresh" it gives a different 
> connotation :). It looks like stable includes upstream illumos-gate from 
> about 5 months ago, whereas bloody is at the moment fully up-to-date 
> with the current upstream. Generally, illumos-gate is intended to be 
> production quality at all times, so arguably you're more stable tracking 
> it more closely. There's only been a couple of times in the past year or 
> so a commit broke anything of note, and I think both of those times it 
> was caught pretty quick and backed out or resolved.

From esproul at omniti.com  Tue Oct  9 10:22:08 2012
From: esproul at omniti.com (Eric Sproul)
Date: Tue, 9 Oct 2012 10:22:08 -0400
Subject: [OmniOS-discuss] stable vs "bloody"
In-Reply-To: <50735AFB.9040501@acm.org>
References: <50735AFB.9040501@acm.org>
Message-ID: <CA+QY2RR43tp-s0_BUSmef906O=-ysXPBp-wcW89MoiwW66RV0A@mail.gmail.com>

On Mon, Oct 8, 2012 at 7:00 PM, Paul B. Henson <henson at acm.org> wrote:
> Terminology wise, "stable" sounds better than "bloody" ;), but if you turn
> that around and call them "stale" and "fresh" it gives a different
> connotation :). It looks like stable includes upstream illumos-gate from
> about 5 months ago, whereas bloody is at the moment fully up-to-date with
> the current upstream. Generally, illumos-gate is intended to be production
> quality at all times, so arguably you're more stable tracking it more
> closely. There's only been a couple of times in the past year or so a commit
> broke anything of note, and I think both of those times it was caught pretty
> quick and backed out or resolved.

Hi Paul,
We run "stable" in production at OmniTI.  We're also currently working
on the next stable release, intended to come out in a couple of weeks,
which will look eerily similar to what bloody is today...

That said, "bloody" is more than just "fresher illumos-gate".  It's
also newer versions of the other bits we add to make the complete OS,
including gcc, OpenSSL, zlib, libxml2, and many others.  Those may not
work correctly together or have bad bugs, but the goal is to let folks
try out the bleeding edge and ferret those out in the ~6 months
between stable releases.

I'm starting to collect a list (as a wiki page) of the things we want
to push into bloody after this month's release, so if I forget to post
that to the list (and IRC) please remind me.  :)  I know that gcc 4.7
is on that list.

Eric

From henson at acm.org  Tue Oct  9 20:28:34 2012
From: henson at acm.org (Paul B. Henson)
Date: Tue, 09 Oct 2012 17:28:34 -0700
Subject: [OmniOS-discuss] stable vs "bloody"
In-Reply-To: <CA+QY2RR43tp-s0_BUSmef906O=-ysXPBp-wcW89MoiwW66RV0A@mail.gmail.com>
References: <50735AFB.9040501@acm.org>
	<CA+QY2RR43tp-s0_BUSmef906O=-ysXPBp-wcW89MoiwW66RV0A@mail.gmail.com>
Message-ID: <5074C132.8080501@acm.org>

On 10/9/2012 7:22 AM, Eric Sproul wrote:

> That said, "bloody" is more than just "fresher illumos-gate".  It's
> also newer versions of the other bits we add to make the complete OS,
> including gcc, OpenSSL, zlib, libxml2, and many others.  Those may not
> work correctly together or have bad bugs, but the goal is to let folks
> try out the bleeding edge and ferret those out in the ~6 months
> between stable releases.

Cool, thanks for the explanation. With that clarification, it's probably 
better to go with stable for production use.


From esproul at omniti.com  Wed Oct 10 09:52:46 2012
From: esproul at omniti.com (Eric Sproul)
Date: Wed, 10 Oct 2012 09:52:46 -0400
Subject: [OmniOS-discuss] stable vs "bloody"
In-Reply-To: <5074C132.8080501@acm.org>
References: <50735AFB.9040501@acm.org>
	<CA+QY2RR43tp-s0_BUSmef906O=-ysXPBp-wcW89MoiwW66RV0A@mail.gmail.com>
	<5074C132.8080501@acm.org>
Message-ID: <CA+QY2RS+fRy0ja8FRR81eCMchimkC_sC1nmECSegAifs5vTO=w@mail.gmail.com>

On Tue, Oct 9, 2012 at 8:28 PM, Paul B. Henson <henson at acm.org> wrote:
> Cool, thanks for the explanation. With that clarification, it's probably
> better to go with stable for production use.

Yeah, we weren't terribly aggressive with moving the additional
packages forward in bloody since the initial release, but that will
likely accelerate once r151004 is out.  We're still finding our way.
:)

Plans for the upcoming release interval are collected at
http://omnios.omniti.com/wiki.php/Intervals

Eric

From esproul at omniti.com  Wed Oct 10 13:40:59 2012
From: esproul at omniti.com (Eric Sproul)
Date: Wed, 10 Oct 2012 13:40:59 -0400
Subject: [OmniOS-discuss] Compiling runtime/perl-$NODOTVER
In-Reply-To: <506DD349.8090801@telenet.be>
References: <506D9D27.4080800@telenet.be>
	<CA+QY2RR17egbv=ozbt3trO5b9YPZBFLu9X7ZMtosa_wJ-E11qg@mail.gmail.com>
	<506DC723.6030408@telenet.be>
	<CA+QY2RSodwZyqprWYK7qWDpxWHvu4HZ9d=UbC99R+1np1za3FA@mail.gmail.com>
	<506DD349.8090801@telenet.be>
Message-ID: <CA+QY2RSTh8-CdYDXdQdDMdASPb5i13o7HVVASR-8rXsr+r1eEw@mail.gmail.com>

On Thu, Oct 4, 2012 at 2:19 PM, Filip Francis <filip.francis at telenet.be> wrote:
> Eric thanks
> Again.
>
>
> Had some weird things going with building system/zones/brand/ipkg
> It always stopped at the following error:
> gcc    -o support support.c /usr/lib/libzonecfg.so.1
> ld: warning: file libdladm.so.1: required by /usr/lib/libdlpi.so.1, not
> found

Filip,
Yes, I've hit that too.  We are not sure what the issue is, though it
could indicate a problem with our gcc (4.6.3).  For now, I've
committed a workaround that allows it to build.

http://omnios.omniti.com/changeset.php/core/pkg/ad3a9511ca52819f4ac9aa427495e8fea45a57de

Eric

From henson at acm.org  Wed Oct 10 14:28:01 2012
From: henson at acm.org (Paul B. Henson)
Date: Wed, 10 Oct 2012 11:28:01 -0700
Subject: [OmniOS-discuss] stable vs "bloody"
In-Reply-To: <CA+QY2RS+fRy0ja8FRR81eCMchimkC_sC1nmECSegAifs5vTO=w@mail.gmail.com>
References: <50735AFB.9040501@acm.org>
	<CA+QY2RR43tp-s0_BUSmef906O=-ysXPBp-wcW89MoiwW66RV0A@mail.gmail.com>
	<5074C132.8080501@acm.org>
	<CA+QY2RS+fRy0ja8FRR81eCMchimkC_sC1nmECSegAifs5vTO=w@mail.gmail.com>
Message-ID: <5075BE31.30907@acm.org>

On 10/10/2012 6:52 AM, Eric Sproul wrote:

> Yeah, we weren't terribly aggressive with moving the additional
> packages forward in bloody since the initial release, but that will
> likely accelerate once r151004 is out.  We're still finding our way.

Sweet. I'm sure I don't only speak for myself when I say we appreciate 
letting us join you in the journey :), it's nice to finally have a 
production ready illumos distribution. I need to start working on my 
boss to get him softened up on migrating our Solaris 10 zfs servers to 
OmniOS sometime in the not-too-distant future...


From bdha at mirrorshades.net  Wed Oct 10 14:31:24 2012
From: bdha at mirrorshades.net (Bryan Horstmann-Allen)
Date: Wed, 10 Oct 2012 14:31:24 -0400
Subject: [OmniOS-discuss] stable vs "bloody"
In-Reply-To: <5075BE31.30907@acm.org>
References: <50735AFB.9040501@acm.org>
	<CA+QY2RR43tp-s0_BUSmef906O=-ysXPBp-wcW89MoiwW66RV0A@mail.gmail.com>
	<5074C132.8080501@acm.org>
	<CA+QY2RS+fRy0ja8FRR81eCMchimkC_sC1nmECSegAifs5vTO=w@mail.gmail.com>
	<5075BE31.30907@acm.org>
Message-ID: <20121010183124.GB4366@lab.pobox.com>

+------------------------------------------------------------------------------
| On 2012-10-10 11:28:01, Paul B. Henson wrote:
| 
> Sweet. I'm sure I don't only speak for myself when I say we appreciate 
> letting us join you in the journey :), it's nice to finally have a 
> production ready illumos distribution. I need to start working on my boss 
> to get him softened up on migrating our Solaris 10 zfs servers to OmniOS 
> sometime in the not-too-distant future...

I'm in the process of doing that with my wife's company. Configuration
management makes everything easier. :-)

Thanks to the ABI, we don't even need to recompile our code! Yay Solarish.
-- 
bdha
cyberpunk is dead. long live cyberpunk.

From kent at watsen.net  Wed Oct 10 15:49:33 2012
From: kent at watsen.net (Kent Watsen)
Date: Wed, 10 Oct 2012 15:49:33 -0400
Subject: [OmniOS-discuss] stable vs "bloody"
In-Reply-To: <20121010183124.GB4366@lab.pobox.com>
References: <50735AFB.9040501@acm.org>
	<CA+QY2RR43tp-s0_BUSmef906O=-ysXPBp-wcW89MoiwW66RV0A@mail.gmail.com>
	<5074C132.8080501@acm.org>
	<CA+QY2RS+fRy0ja8FRR81eCMchimkC_sC1nmECSegAifs5vTO=w@mail.gmail.com>
	<5075BE31.30907@acm.org> <20121010183124.GB4366@lab.pobox.com>
Message-ID: <5075D14D.1070709@watsen.net>

|
>> Sweet. I'm sure I don't only speak for myself when I say we appreciate
>> letting us join you in the journey :), it's nice to finally have a
>> production ready illumos distribution. I need to start working on my boss
>> to get him softened up on migrating our Solaris 10 zfs servers to OmniOS
>> sometime in the not-too-distant future...
> I'm in the process of doing that with my wife's company. Configuration
> management makes everything easier. :-)
>
> Thanks to the ABI, we don't even need to recompile our code! Yay Solarish.

I've decided to move my system over to OmniOS too.   I was going to go 
OI, but really just wanted JeOS.  Then I thought Illumian, but the 
project doesn't instill confidence.  Looking at OmniOS, reading 
everything about it, watching Theo's interview on MinkCast, etc...it 
seems perfect - thanks OmniOS devs!

Kent


From henson at acm.org  Wed Oct 10 18:50:45 2012
From: henson at acm.org (Paul B. Henson)
Date: Wed, 10 Oct 2012 15:50:45 -0700
Subject: [OmniOS-discuss] stable vs "bloody"
In-Reply-To: <5075D14D.1070709@watsen.net>
References: <50735AFB.9040501@acm.org>
	<CA+QY2RR43tp-s0_BUSmef906O=-ysXPBp-wcW89MoiwW66RV0A@mail.gmail.com>
	<5074C132.8080501@acm.org>
	<CA+QY2RS+fRy0ja8FRR81eCMchimkC_sC1nmECSegAifs5vTO=w@mail.gmail.com>
	<5075BE31.30907@acm.org> <20121010183124.GB4366@lab.pobox.com>
	<5075D14D.1070709@watsen.net>
Message-ID: <5075FBC5.2040409@acm.org>

On 10/10/2012 12:49 PM, Kent Watsen wrote:

> I've decided to move my system over to OmniOS too.   I was going to go
> OI, but really just wanted JeOS.  Then I thought Illumian, but the
> project doesn't instill confidence.

I was waiting a long time for illumian too, mostly for dpkg support. I 
think it's mostly in limbo right now, I've heard a few things 
unofficially but AFAIK there's been no official Nexenta statement on 
what's going on with it. Fortunately, the things other than dpkg that 
seemed attractive about illumian are also true for OmniOS -- actually 
used in production by a commercial entity with a strong interest in 
keeping it stable and addressing bugs/security issues along with the 
resources to do so... I just don't think the community is large enough 
yet for a fully community supported distribution to work at this point.


From henson at acm.org  Thu Oct 11 17:27:32 2012
From: henson at acm.org (Paul B. Henson)
Date: Thu, 11 Oct 2012 14:27:32 -0700
Subject: [OmniOS-discuss] Installer Crashes While 'Probing for
	DeviceNodes'
In-Reply-To: <506E3AA4.70508@acm.org>
References: <57388.1349309135@landcroft.co.uk>
	<CA+QY2RSJG7f5nFx-k68uj2-4pWNf11_8pmrSi=zm9A1XmnTnDA@mail.gmail.com>
	<506DCB38.9030501@acm.org>
	<CA+QY2RT+ML+dsk16Du-jvPisoEmot7LiGRBYjDYMiuV8bsFcfQ@mail.gmail.com>
	<506E2F15.3040401@acm.org>
	<CACLsApugbguONA0w2A=auiZJ3MBb=UZ30rFUcznWiqGayRx+Ng@mail.gmail.com>
	<506E3AA4.70508@acm.org>
Message-ID: <507739C4.1030405@acm.org>

I don't think I saw a reply on this? I'm sure you guys have more 
important things to do :), but I am really curious about the apparent 
discrepancy between my local git clone of your repo and your online 
version, so if at some point you had the time an explanation 
(potentially of what I'm doing wrong 8-/) would be deeply appreciated...

Thanks...

On 10/4/2012 6:40 PM, Paul B. Henson wrote:
> On 10/4/2012 6:14 PM, Theo Schlossnagle wrote:
>
>> http://omnios.omniti.com/changeset.php/core/illumos-omnios/eae537bad35e09fb6be6db8ea368cd25c07ef77e
>>
>
> Hmm, in the local clone of your git repo I made, that commit seems to
> have a different hash?
>
> ----
> commit a4c87b0f05abfa9d83a1eacb0328160d6bb064ec
> Author: Theo Schlossnagle <jesus at omniti.com>
> Date:   Tue May 8 22:17:18 2012 +0000
>
>      Remove our dependency on ghostscript and cups.
>      This breaks cups support in smbd (spool). If we decide
>      we want to enable that, we should only require the cups
>      header to build and should consider packaging that in ON.
> ----
>
> A git show on that commit hash in my local clone seems to be identical
> to the one you referenced on your website. Just with a different hash. I
> cloned it with "git clone
> anon at src.omniti.com:~omnios/core/illumos-omnios", which I found on your
> website.
>
> Hmm, interesting, if I plug the hash from my local clone into your website:
>
> http://omnios.omniti.com/changeset.php/core/illumos-omnios/a4c87b0f05abfa9d83a1eacb0328160d6bb064ec
>
>
> it finds it, and they look identical. But the first one you listed
> doesn't seem to be in the local clone. I'm confused now 8-/.


From henson at acm.org  Thu Oct 11 18:36:30 2012
From: henson at acm.org (Paul B. Henson)
Date: Thu, 11 Oct 2012 15:36:30 -0700
Subject: [OmniOS-discuss] ssl root CA certs
Message-ID: <20121011223630.GE4175@bender.unx.csupomona.edu>

I noticed omnios installs a standard set of root CA certs in
/etc/certs/CA; however, openssl is looking for them in /usr/ssl/certs,
which was empty. I ended up running

for f in /etc/certs/CA/* ; do ln -s $f /usr/ssl/certs/`openssl x509 -hash -noout -in $f`.0; done

to make the hashed symlinks so openssl based apps (such as wget) would
find the root CA's.

If there's an intention for openssl to recognize root CA's out of the
box, perhaps these symlinks can be made during the install? Or perhaps
openssl should be configured to look in /etc/certs/CA instead of
/usr/ssl/certs (which would still need hash symlinks, but just in that
directory instead). Or if the intention is for an admin to need to setup
this up themselves after an install, ignore the noise ;)...

Thanks...


From esproul at omniti.com  Fri Oct 12 10:14:37 2012
From: esproul at omniti.com (Eric Sproul)
Date: Fri, 12 Oct 2012 10:14:37 -0400
Subject: [OmniOS-discuss] ssl root CA certs
In-Reply-To: <20121011223630.GE4175@bender.unx.csupomona.edu>
References: <20121011223630.GE4175@bender.unx.csupomona.edu>
Message-ID: <CA+QY2RRYjd9=q-6GaQZfisrVVNEXstGL6eexawJTGGK21_U9WQ@mail.gmail.com>

On Thu, Oct 11, 2012 at 6:36 PM, Paul B. Henson <henson at acm.org> wrote:
> I noticed omnios installs a standard set of root CA certs in
> /etc/certs/CA; however, openssl is looking for them in /usr/ssl/certs,
> which was empty. I ended up running
>
> for f in /etc/certs/CA/* ; do ln -s $f /usr/ssl/certs/`openssl x509 -hash -noout -in $f`.0; done
>
> to make the hashed symlinks so openssl based apps (such as wget) would
> find the root CA's.

Paul,
You bring up an interesting point, and there are multiple ways we
could solve it.  For curl and wget, we ship a dependent package,
web/ca-bundle, which delivers a single .pem file containing all the
root CA certs.  We get this file from http://curl.haxx.se/ca/

We build curl to use this file, so https links work out of the box in
curl.  Wget can be induced to use it by adding "ca_certificate =
/etc/cacert.pem" to /etc/wgetrc.  We may just ship a default wgetrc
with this option added.  I don't see a downside to doing that.  That
takes care of the common case with curl/wget, but leaves the larger
question of how we want OpenSSL to behave.

>
> If there's an intention for openssl to recognize root CA's out of the
> box, perhaps these symlinks can be made during the install?

The certs in /usr/ssl/certs come from the crypto/ca-certificates
package which is part of illumos-gate.  OpenSSL is not-- we build that
ourselves, mostly following the way it was built previously in
OpenSolaris/OI, which is to say, without any connection to
crypto/ca-certificates.  I'll look into what might do there; thanks
for pointing it out.

Eric

From esproul at omniti.com  Fri Oct 12 11:53:07 2012
From: esproul at omniti.com (Eric Sproul)
Date: Fri, 12 Oct 2012 11:53:07 -0400
Subject: [OmniOS-discuss] ssl root CA certs
In-Reply-To: <CA+QY2RRYjd9=q-6GaQZfisrVVNEXstGL6eexawJTGGK21_U9WQ@mail.gmail.com>
References: <20121011223630.GE4175@bender.unx.csupomona.edu>
	<CA+QY2RRYjd9=q-6GaQZfisrVVNEXstGL6eexawJTGGK21_U9WQ@mail.gmail.com>
Message-ID: <CA+QY2RSuzH7SBtszRhaVa6fapx2MaS62ZcHB5EMj0dxhCzhamg@mail.gmail.com>

On Fri, Oct 12, 2012 at 10:14 AM, Eric Sproul <esproul at omniti.com> wrote:
> The certs in /usr/ssl/certs come from the crypto/ca-certificates
> package which is part of illumos-gate.  OpenSSL is not-- we build that
> ourselves, mostly following the way it was built previously in
> OpenSolaris/OI, which is to say, without any connection to
> crypto/ca-certificates.  I'll look into what might do there; thanks
> for pointing it out.

I found where the CA certs live in illumos-gate:
http://src.illumos.org/source/xref/illumos-gate/usr/src/cmd/cmd-crypto/etc/CA-certs/

It looks like these certs are at least 18 months old, judging solely
by the mod times.  I'm not certain how often they get updated, but
given the changes I've observed in the bundle we get from haxx.se,
this collection almost certainly contains stale data.  Given that, do
we still want to encourage the use of that set or just point apps at
/etc/cacert.pem which is more up to date?

From henson at acm.org  Fri Oct 12 19:11:02 2012
From: henson at acm.org (Paul B. Henson)
Date: Fri, 12 Oct 2012 16:11:02 -0700
Subject: [OmniOS-discuss] ssl root CA certs
In-Reply-To: <CA+QY2RSuzH7SBtszRhaVa6fapx2MaS62ZcHB5EMj0dxhCzhamg@mail.gmail.com>
References: <20121011223630.GE4175@bender.unx.csupomona.edu>
	<CA+QY2RRYjd9=q-6GaQZfisrVVNEXstGL6eexawJTGGK21_U9WQ@mail.gmail.com>
	<CA+QY2RSuzH7SBtszRhaVa6fapx2MaS62ZcHB5EMj0dxhCzhamg@mail.gmail.com>
Message-ID: <5078A386.2040001@acm.org>

On 10/12/2012 8:53 AM, Eric Sproul wrote:

> I found where the CA certs live in illumos-gate:
> http://src.illumos.org/source/xref/illumos-gate/usr/src/cmd/cmd-crypto/etc/CA-certs/
[...]
> this collection almost certainly contains stale data.  Given that, do
> we still want to encourage the use of that set or just point apps at
> /etc/cacert.pem which is more up to date?

It looks like the ones bundled in illumos-gate also come from Mozilla, 
by way of being extracted from libnssckbi.so. OI and OmniOS both include 
that library, but it doesn't seem to be part of illumos-gate? At least I 
couldn't find it. So I guess that's a distribution value added package 
;). In theory it seems it would be good for the libnssckbi.so hardcoded 
certificates to match the external certificates, so applications don't 
do different things depending on whether or not they use NSS or openssl.

I was going to say that if somebody was going to go to the trouble of 
updating CA certs, they might as well do it in upstream illumos-gate so 
all distributions can avail of it. However, if NSS is added per 
distribution, that would make it pretty difficult to keep them synced 
up. If root CA's are going to be maintained by the distribution, it 
would seem better for illumos-gate to simply not include any at all, 
again so as not to have a different set pending on where you look. The 
illumos bundled CA's also include a couple from Sun which are presumably 
owned by Oracle now, I'd just as soon not have my omnios box trusting 
Oracle for anything 8-/.

I think I will bring this up on the illumos developer list and see what 
comes of it. My initial thoughts now are that root CA's should just be 
dropped out of illumos-gate and handled at the distribution level, that 
way there'll be no confusion or mismatch.

On another note, I think it's a lot more efficient to have a directory 
full of hashes to individual certificates rather than one big file full 
of all of them. In the first case, openssl can pretty much immediately 
find what it wants (or determine it doesn't exist), and the second it 
has to read the entire file and search for it. It looks like the 
upstream certs have those hashes already in /etc/openssl/certs. Rather 
than configuring curl and/or wget to point to the big file, it seems it 
would be better to set up the hashed directory and have the openssl 
library configured to find it, so all openssl apps would work the same 
by default...


From henson at acm.org  Sat Oct 13 21:06:48 2012
From: henson at acm.org (Paul B. Henson)
Date: Sat, 13 Oct 2012 18:06:48 -0700
Subject: [OmniOS-discuss] ssl root CA certs
In-Reply-To: <CA+QY2RSuzH7SBtszRhaVa6fapx2MaS62ZcHB5EMj0dxhCzhamg@mail.gmail.com>
References: <20121011223630.GE4175@bender.unx.csupomona.edu>
	<CA+QY2RRYjd9=q-6GaQZfisrVVNEXstGL6eexawJTGGK21_U9WQ@mail.gmail.com>
	<CA+QY2RSuzH7SBtszRhaVa6fapx2MaS62ZcHB5EMj0dxhCzhamg@mail.gmail.com>
Message-ID: <20121014010648.GO4175@bender.unx.csupomona.edu>

On Fri, Oct 12, 2012 at 11:53:07AM -0400, Eric Sproul wrote:

> It looks like these certs are at least 18 months old, judging solely
> by the mod times.  I'm not certain how often they get updated, but
> given the changes I've observed in the bundle we get from haxx.se,
> this collection almost certainly contains stale data.  Given that, do
> we still want to encourage the use of that set or just point apps at
> /etc/cacert.pem which is more up to date?

The illumos dev list was in favor of just removing them from
illumos-gate, so I'm going to put together an RTI to do so. I don't know
if it will go through before you branch the next stable though, I guess
you could always cherrypick that commit.

I think the cleanest thing to do to is to have a set of individual certs
and openssl hashes to them that correspond to whatever certs are bundled
in the libnssckbi.so included in the mozilla-nss package, so behavior
between apps using nss and apps using openssl matches. From a packaging
perspective, I don't know if it would be better to just have them part
of the nss package or have them in a separate package.

On the one hand, I suppose you can just get the latest list from
Mozilla's repo, on the other, that won't necessarily match the nss
version, and if the changes are important enough, an update of the nss
package including them would also be warranted, which if the package
included the plain text external certs too, would bring them along.

Thoughts?

From jesus at omniti.com  Sun Oct 14 09:44:22 2012
From: jesus at omniti.com (Theo Schlossnagle)
Date: Sun, 14 Oct 2012 09:44:22 -0400
Subject: [OmniOS-discuss] ssl root CA certs
In-Reply-To: <20121014010648.GO4175@bender.unx.csupomona.edu>
References: <20121011223630.GE4175@bender.unx.csupomona.edu>
	<CA+QY2RRYjd9=q-6GaQZfisrVVNEXstGL6eexawJTGGK21_U9WQ@mail.gmail.com>
	<CA+QY2RSuzH7SBtszRhaVa6fapx2MaS62ZcHB5EMj0dxhCzhamg@mail.gmail.com>
	<20121014010648.GO4175@bender.unx.csupomona.edu>
Message-ID: <CACLsApuahnZEAua3Tff4UKeZjo1E15wKjZ0LbV0Bv5rF0ngGZA@mail.gmail.com>

That change sounds completely reasonable. Having the certs in gate
seems rather short-sighted.  Once that happens, we'll cope fine.

On Sat, Oct 13, 2012 at 9:06 PM, Paul B. Henson <henson at acm.org> wrote:
> On Fri, Oct 12, 2012 at 11:53:07AM -0400, Eric Sproul wrote:
>
>> It looks like these certs are at least 18 months old, judging solely
>> by the mod times.  I'm not certain how often they get updated, but
>> given the changes I've observed in the bundle we get from haxx.se,
>> this collection almost certainly contains stale data.  Given that, do
>> we still want to encourage the use of that set or just point apps at
>> /etc/cacert.pem which is more up to date?
>
> The illumos dev list was in favor of just removing them from
> illumos-gate, so I'm going to put together an RTI to do so. I don't know
> if it will go through before you branch the next stable though, I guess
> you could always cherrypick that commit.
>
> I think the cleanest thing to do to is to have a set of individual certs
> and openssl hashes to them that correspond to whatever certs are bundled
> in the libnssckbi.so included in the mozilla-nss package, so behavior
> between apps using nss and apps using openssl matches. From a packaging
> perspective, I don't know if it would be better to just have them part
> of the nss package or have them in a separate package.
>
> On the one hand, I suppose you can just get the latest list from
> Mozilla's repo, on the other, that won't necessarily match the nss
> version, and if the changes are important enough, an update of the nss
> package including them would also be warranted, which if the package
> included the plain text external certs too, would bring them along.
>
> Thoughts?
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss



-- 
Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle

From filip.francis at telenet.be  Mon Oct 15 14:29:57 2012
From: filip.francis at telenet.be (Filip Francis)
Date: Mon, 15 Oct 2012 20:29:57 +0200
Subject: [OmniOS-discuss] Building Percona-server 5.5
Message-ID: <507C5625.8090907@telenet.be>

Hi all,


I was just going thru the omnios-build but the branch omniti-ms
I saw that you are not able to compiler the Percona server.
i have just tried to build the Percona server and have success in building.
this is what i have modified:
CONFIGURE_OPTS="-DCMAKE_INSTALL_PREFIX=$PREFIX
                 -DBUILD_CONFIG=mysql_release
                 -DWITH_EMBEDDED_SERVER=OFF
                 -LAH
                 -DHAVE_FAKE_PAUSE_INSTRUCTION=1
                 -DHAVE_PAUSE_INSTRUCTION=0
                 -DWITH_AUTH_PAM=OFF
                 -DWITH_AUTH_PAM_COMPAT=OFF
                 -DWITH_DIALOG=OFF
                 -DWITH_EXTRA_CHARSETS=complex
                 -DENABLE_THREAD_SAFE_CLIENT=1
                 -DENABLE_LOCAL_INFILE=1
                 -DWITH_ZLIB=bundled
                 -DWITH_BIG_TABLES=1
                 -DWITH_READLINE=1
                 -DWITH_ARCHIVE_STORAGE_ENGINE=1
                 -DWITH_NAMED_CURSES=_LCURSES=1
                 -DWITH_BIG_TABLES=1
                 -DWITH_INNODB=1
                 -DWITH_AUTH_PAM=OFF
                 -DWITH_AUTH_PAM_COMPAT=OFF
                 -DWITH_DIALOG=OFF
                 -DWITH_EXAMPLE_STORAGE_ENGINE=1
                 -DWITH_BLACKHOLE_STORAGE_ENGINE=1
                 -DWITH_FEDERATED_STORAGE_ENGINE=1
                 -DWITH_CSV_STORAGE_ENGINE=1
                 -DWITH_SSL=bundled
                 -DWITH_MYSQLD_LIBS=_LMTMALLOC=1
                 -DHAVE_RINT=1
                 -DWITH_FAST_MUTEXES=1"


and this line
prep_build
rm -r $TMPDIR/$BUILDDIR/plugin/percona-pam-for-mysql (Only needed if you 
have version prior to Percona-Server-5.5.27-rel28.1)
build



So now i have build the following version and they are compiling correctly
Percona-Server-5.5.27-rel28.1
Percona-Server-5.5.27-rel29.0


Regards
Filip


From esproul at omniti.com  Mon Oct 15 14:43:15 2012
From: esproul at omniti.com (Eric Sproul)
Date: Mon, 15 Oct 2012 14:43:15 -0400
Subject: [OmniOS-discuss] Building Percona-server 5.5
In-Reply-To: <507C5625.8090907@telenet.be>
References: <507C5625.8090907@telenet.be>
Message-ID: <CA+QY2RQ9BgeGpvp+neQCO45uznTJKXdjkOATHxgTaRoQnaVLNQ@mail.gmail.com>

On Mon, Oct 15, 2012 at 2:29 PM, Filip Francis <filip.francis at telenet.be> wrote:
> Hi all,
>
>
> I was just going thru the omnios-build but the branch omniti-ms
> I saw that you are not able to compiler the Percona server.
> i have just tried to build the Percona server and have success in building.

Filip,
Thanks! What we had there was a work-in-progress that got stalled. :)
I appreciate the extra info, which will be very helpful.

Eric

From filip.francis at telenet.be  Mon Oct 15 14:51:39 2012
From: filip.francis at telenet.be (Filip Francis)
Date: Mon, 15 Oct 2012 20:51:39 +0200
Subject: [OmniOS-discuss] Building Percona-server 5.5
In-Reply-To: <CA+QY2RQ9BgeGpvp+neQCO45uznTJKXdjkOATHxgTaRoQnaVLNQ@mail.gmail.com>
References: <507C5625.8090907@telenet.be>
	<CA+QY2RQ9BgeGpvp+neQCO45uznTJKXdjkOATHxgTaRoQnaVLNQ@mail.gmail.com>
Message-ID: <507C5B3B.3040608@telenet.be>

Eric,


no problem.
I am willing to help.
i am working on a storage device for my company and trying to understand 
it all.
if i found some more things i will sent you the results or even diffs.

Regards
Filip Francis
Unix consultant.

On 10/15/12 08:43 PM, Eric Sproul wrote:
> On Mon, Oct 15, 2012 at 2:29 PM, Filip Francis <filip.francis at telenet.be> wrote:
>> Hi all,
>>
>>
>> I was just going thru the omnios-build but the branch omniti-ms
>> I saw that you are not able to compiler the Percona server.
>> i have just tried to build the Percona server and have success in building.
> Filip,
> Thanks! What we had there was a work-in-progress that got stalled. :)
> I appreciate the extra info, which will be very helpful.
>
> Eric
>


From emunch at utmi.in  Tue Oct 16 05:14:55 2012
From: emunch at utmi.in (Sam M)
Date: Tue, 16 Oct 2012 14:44:55 +0530
Subject: [OmniOS-discuss] Difference Between Stable and Bloody
Message-ID: <CAHDYqcpsW43j-GJeY00_2KL9RA0QOOZSMK3dYNKvJSGkJh+ojA@mail.gmail.com>

Hello.

Just joined the mailing list.

What's the difference between the two releases - stable and bloody?
Specifically with reference to the Openindiana release?

Thanks.

Sam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121016/c206f1a0/attachment.html>

From agsousa at metalcon.pt  Tue Oct 16 08:16:04 2012
From: agsousa at metalcon.pt (Agostinho Sousa)
Date: Tue, 16 Oct 2012 13:16:04 +0100
Subject: [OmniOS-discuss] command to start a kvm machine
Message-ID: <507D5004.507@metalcon.pt>

Hi,

In Openindiana I use /usr/bin/qemu-kvm to start a machine. How do I do 
in OmniOS?

-- 
assinatura

/Melhores cumprimentos | Un saludo | Best regards | Cordiali saluti |?? 
???????? | Met vriendelijke groeten | Salutations/

*Agostinho Sousa *
Direc??o de Sistemas de Informa??o | IT Department
agsousa at metalcon.pt | M. +351 968 492 741

Irm?os Silvas, S.A.
Maganha - Santiago de Bougado - Apartado 206
4786-909 - TROFA
Tel: +351 252 400 520 | Fax: +351 252 400 521
metalcon at metalcon.pt | www.metalcon.pt

*GRUPO METALCON *
Metalcon Investimentos | Brasmar | Galvaza | Grupomar | LSM | 
Metalogalva | Silvafer

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121016/fd0c402d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 5474 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121016/fd0c402d/attachment.png>

From jesus at omniti.com  Tue Oct 16 08:47:47 2012
From: jesus at omniti.com (Theo Schlossnagle)
Date: Tue, 16 Oct 2012 08:47:47 -0400
Subject: [OmniOS-discuss] Difference Between Stable and Bloody
In-Reply-To: <CAHDYqcpsW43j-GJeY00_2KL9RA0QOOZSMK3dYNKvJSGkJh+ojA@mail.gmail.com>
References: <CAHDYqcpsW43j-GJeY00_2KL9RA0QOOZSMK3dYNKvJSGkJh+ojA@mail.gmail.com>
Message-ID: <CACLsApu63pEftruEMx37PNiQyg_6ff3Jd6BNP+bOtsZ2dQ9yUg@mail.gmail.com>

I don't think there is a reference between OmniOS and OI.

OmniOS stable is designed to be run in production with minimal
disruption.  This means we release updates in a way to minimize
service disruption (reboot).  Kernel updates are only made if they are
security or stability related and no work-around exists.  User-space
applications can be treated more aggressively, but we're still
conservative.  OmniOS updates are made available weekly and a full
release is done every six months.

OmniOS bloody incorporates user-land updates and kernel updates in an
aggressive fashion and updates are made available as they are
introduced via IPS.  The only time we see an ISO install media rolled
with bloody is if there is a specific install issue address by a
change in bloody.

We should document this on a wiki page. :-)

On Tue, Oct 16, 2012 at 5:14 AM, Sam M <emunch at utmi.in> wrote:
> Hello.
>
> Just joined the mailing list.
>
> What's the difference between the two releases - stable and bloody?
> Specifically with reference to the Openindiana release?
>
> Thanks.
>
> Sam
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>



-- 
Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle

From agsousa at metalcon.pt  Tue Oct 16 09:11:21 2012
From: agsousa at metalcon.pt (Agostinho Sousa)
Date: Tue, 16 Oct 2012 14:11:21 +0100
Subject: [OmniOS-discuss] command to start a kvm machine
Message-ID: <507D5CF9.5040603@metalcon.pt>

Hi,

In Openindiana I use /usr/bin/qemu-kvm to start a machine. How do I do 
in OmniOS?

-- 
assinatura

/Melhores cumprimentos | Un saludo | Best regards | Cordiali saluti |?? 
???????? | Met vriendelijke groeten | Salutations/

*Agostinho Sousa *
Direc??o de Sistemas de Informa??o | IT Department
agsousa at metalcon.pt | M. +351 968 492 741

Irm?os Silvas, S.A.
Maganha - Santiago de Bougado - Apartado 206
4786-909 - TROFA
Tel: +351 252 400 520 | Fax: +351 252 400 521
metalcon at metalcon.pt | www.metalcon.pt

*GRUPO METALCON *
Metalcon Investimentos | Brasmar | Galvaza | Grupomar | LSM | 
Metalogalva | Silvafer

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121016/6bccec13/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 5474 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121016/6bccec13/attachment-0001.png>

From jesus at omniti.com  Tue Oct 16 09:27:41 2012
From: jesus at omniti.com (Theo Schlossnagle)
Date: Tue, 16 Oct 2012 09:27:41 -0400
Subject: [OmniOS-discuss] command to start a kvm machine
In-Reply-To: <507D5CF9.5040603@metalcon.pt>
References: <507D5CF9.5040603@metalcon.pt>
Message-ID: <CACLsAps-Gi1KMQfRKYzDoM1EmKtNmviHAY+QnirrswsgEimzJA@mail.gmail.com>

/usr/bin/qemu-system-x86_64 is the command shipped with Qemu.  That's what
I use.

2012/10/16 Agostinho Sousa <agsousa at metalcon.pt>

>  Hi,
>
> In Openindiana I use /usr/bin/qemu-kvm to start a machine. How do I do in
> OmniOS?
>
>
> --

Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121016/d64ed1ac/attachment.html>

From esproul at omniti.com  Tue Oct 16 09:51:26 2012
From: esproul at omniti.com (Eric Sproul)
Date: Tue, 16 Oct 2012 09:51:26 -0400
Subject: [OmniOS-discuss] Difference Between Stable and Bloody
In-Reply-To: <CAHDYqcpsW43j-GJeY00_2KL9RA0QOOZSMK3dYNKvJSGkJh+ojA@mail.gmail.com>
References: <CAHDYqcpsW43j-GJeY00_2KL9RA0QOOZSMK3dYNKvJSGkJh+ojA@mail.gmail.com>
Message-ID: <CA+QY2RTwe3nsebN7nDTSSpPHsDga2bpk1L=2rij5pFQvXgKWBQ@mail.gmail.com>

On Tue, Oct 16, 2012 at 5:14 AM, Sam M <emunch at utmi.in> wrote:
> Hello.
>
> Just joined the mailing list.
>
> What's the difference between the two releases - stable and bloody?
> Specifically with reference to the Openindiana release?

Hi Sam, welcome.  There's no relation whatsoever to OpenIndiana
releases here.  We're a separate distribution with our own schedule.
Stable releases are just that-- stable with respect to version
changes.  If you want more cutting-edge, then bloody is where it's at.

We are aiming for a 6-month cycle of stable releases, with bloody as a
testing ground in between.  The next stable release is in the works
and will be out Real Soon Now(tm).

HTH,
Eric

From agsousa at metalcon.pt  Tue Oct 16 08:15:24 2012
From: agsousa at metalcon.pt (Agostinho Sousa)
Date: Tue, 16 Oct 2012 13:15:24 +0100
Subject: [OmniOS-discuss] command to start a kvm machine
Message-ID: <507D4FDC.4080108@metalcon.pt>

Hi,

In Openindiana I use /usr/bin/qemu-kvm to start a machine. How do I do 
in OmniOS?

-- 
assinatura

/Melhores cumprimentos | Un saludo | Best regards | Cordiali saluti |?? 
???????? | Met vriendelijke groeten | Salutations/

*Agostinho Sousa *
Direc??o de Sistemas de Informa??o | IT Department
agsousa at metalcon.pt | M. +351 968 492 741

Irm?os Silvas, S.A.
Maganha - Santiago de Bougado - Apartado 206
4786-909 - TROFA
Tel: +351 252 400 520 | Fax: +351 252 400 521
metalcon at metalcon.pt | www.metalcon.pt

*GRUPO METALCON *
Metalcon Investimentos | Brasmar | Galvaza | Grupomar | LSM | 
Metalogalva | Silvafer

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121016/293d4925/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: METALCONSGPS.PNG
Type: image/png
Size: 5474 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121016/293d4925/attachment.png>

From esproul at omniti.com  Tue Oct 16 10:05:57 2012
From: esproul at omniti.com (Eric Sproul)
Date: Tue, 16 Oct 2012 10:05:57 -0400
Subject: [OmniOS-discuss] Difference Between Stable and Bloody
In-Reply-To: <CACLsApu63pEftruEMx37PNiQyg_6ff3Jd6BNP+bOtsZ2dQ9yUg@mail.gmail.com>
References: <CAHDYqcpsW43j-GJeY00_2KL9RA0QOOZSMK3dYNKvJSGkJh+ojA@mail.gmail.com>
	<CACLsApu63pEftruEMx37PNiQyg_6ff3Jd6BNP+bOtsZ2dQ9yUg@mail.gmail.com>
Message-ID: <CA+QY2RRpE_cGQg00LLfAewDEzXFqrExW7NGFYKhMtuV9UKUyWg@mail.gmail.com>

On Tue, Oct 16, 2012 at 8:47 AM, Theo Schlossnagle <jesus at omniti.com> wrote:
> We should document this on a wiki page. :-)

Bam! http://omnios.omniti.com/wiki.php/StableVsBloody

Shamelessly plagiarized from your email, Theo.

From agsousa at metalcon.pt  Tue Oct 16 22:56:43 2012
From: agsousa at metalcon.pt (Agostinho Sousa)
Date: Wed, 17 Oct 2012 03:56:43 +0100
Subject: [OmniOS-discuss] start a VM (kvm) on boot
Message-ID: <507E1E6B.4020709@metalcon.pt>

Hi,

Thanks Theo Schlossnagle, for your quick response.

Wich is the correct way to start a VM on boot?

-- 
assinatura

/Melhores cumprimentos | Un saludo | Best regards | Cordiali saluti |?? 
???????? | Met vriendelijke groeten | Salutations/

*Agostinho Sousa *
Direc??o de Sistemas de Informa??o | IT Department
agsousa at metalcon.pt | M. +351 968 492 741

Irm?os Silvas, S.A.
Maganha - Santiago de Bougado - Apartado 206
4786-909 - TROFA
Tel: +351 252 400 520 | Fax: +351 252 400 521
metalcon at metalcon.pt | www.metalcon.pt

*GRUPO METALCON *
Metalcon Investimentos | Brasmar | Galvaza | Grupomar | LSM | 
Metalogalva | Silvafer

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121017/eb467fda/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: METALCONSGPS.PNG
Type: image/png
Size: 5474 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121017/eb467fda/attachment.png>

From gate03 at landcroft.co.uk  Tue Oct 16 23:05:22 2012
From: gate03 at landcroft.co.uk (gate03 at landcroft.co.uk)
Date: Wed, 17 Oct 2012 04:05:22 +0100
Subject: [OmniOS-discuss] sun ray ?
Message-ID: <57011.1350443122@landcroft.co.uk>

Has anyone succeeded in running Oracles Sun Ray server on OmiOS ?





From jesus at omniti.com  Tue Oct 16 23:16:04 2012
From: jesus at omniti.com (Theo Schlossnagle)
Date: Tue, 16 Oct 2012 23:16:04 -0400
Subject: [OmniOS-discuss] start a VM (kvm) on boot
In-Reply-To: <507E1E6B.4020709@metalcon.pt>
References: <507E1E6B.4020709@metalcon.pt>
Message-ID: <CACLsAptKB41-4oYOunEfG_BGtHAg-2HSC2wqXibtb2cCY_6k9A@mail.gmail.com>

We use SMF to do this.

2012/10/16 Agostinho Sousa <agsousa at metalcon.pt>

>  Hi,
>
> Thanks Theo Schlossnagle, for your quick response.
>
> Wich is the correct way to start a VM on boot?
>
> --
>
> *Melhores cumprimentos | Un saludo | Best regards | Cordiali saluti |??
> ???????? | Met vriendelijke groeten | Salutations*
>
> * Agostinho Sousa *
>  Direc??o de Sistemas de Informa??o | IT Department
> agsousa at metalcon.pt | M. +351 968 492 741
>
> Irm?os Silvas, S.A.
> Maganha - Santiago de Bougado - Apartado 206
> 4786-909 - TROFA
> Tel: +351 252 400 520 | Fax: +351 252 400 521
> metalcon at metalcon.pt | www.metalcon.pt
>
> *GRUPO METALCON *
> Metalcon Investimentos | Brasmar | Galvaza | Grupomar | LSM | Metalogalva
> | Silvafer
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>


-- 

Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121016/cddd66f5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: METALCONSGPS.PNG
Type: image/png
Size: 5474 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121016/cddd66f5/attachment.png>

From magnus at yonderway.com  Wed Oct 17 00:30:23 2012
From: magnus at yonderway.com (Magnus)
Date: Wed, 17 Oct 2012 00:30:23 -0400
Subject: [OmniOS-discuss] OmniOS discussion points?
Message-ID: <4DFC6395-EDEC-4C43-8B6A-A99A2FA97819@yonderway.com>

I'm doing an "Intro to illumos" talk for the Triangle DevOps group tomorrow (Wednesday) night and I'm just wondering if there are some interesting factoids about OmniOS I could share, like maybe prominent web sites running on top of it, or a guesstimate of deployments, that kind of thing. I'm only talking for a couple of minutes or so about each distribution. The target audience is mostly going to be Linux people that are curious about illumos, so maybe something that lends production scale credibility to OmniOS?

http://www.meetup.com/Triangle-DevOps/events/82806542/

-Magnus

From agsousa at metalcon.pt  Wed Oct 17 06:07:45 2012
From: agsousa at metalcon.pt (Agostinho Sousa)
Date: Wed, 17 Oct 2012 11:07:45 +0100
Subject: [OmniOS-discuss] mc package for OmniOS on http://pkg.cs.umd.edu
Message-ID: <507E8371.6040805@metalcon.pt>

Hi,

I have installed mc package from the repo above and it work. But when I 
try copy (F5)/move (F6)  any file I receive a core dump and mc abort.

The is anything that I can do to solve this?

Thanks
-- 
assinatura

/Melhores cumprimentos | Un saludo | Best regards | Cordiali saluti |?? 
???????? | Met vriendelijke groeten | Salutations/

*Agostinho Sousa *
Direc??o de Sistemas de Informa??o | IT Department
agsousa at metalcon.pt | M. +351 968 492 741

Irm?os Silvas, S.A.
Maganha - Santiago de Bougado - Apartado 206
4786-909 - TROFA
Tel: +351 252 400 520 | Fax: +351 252 400 521
metalcon at metalcon.pt | www.metalcon.pt

*GRUPO METALCON *
Metalcon Investimentos | Brasmar | Galvaza | Grupomar | LSM | 
Metalogalva | Silvafer

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121017/24c72919/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: METALCONSGPS.PNG
Type: image/png
Size: 5474 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121017/24c72919/attachment.png>

From paul.jochum at alcatel-lucent.com  Wed Oct 17 08:16:44 2012
From: paul.jochum at alcatel-lucent.com (Paul Jochum)
Date: Wed, 17 Oct 2012 07:16:44 -0500
Subject: [OmniOS-discuss] pkg update and omnios repos
Message-ID: <507EA1AC.8080002@alcatel-lucent.com>

Hi All:

     Wanted to ask some questions on the OmniOS package repo:

1) As new stable OmniOS releases are published, are the new packages 
added to the omnios repo, so that a pkg update command would update a 
system to the latest stable release?

2) Is there some plan on when the omnios repo is updated?  For example, 
are all of the changed packages installed simultaneously into the OmniOS 
repo, or do they trickle in over a long time span?

3) Will there be announcements when the omnios repo is updated?

3) If I install the bloody release, can I add (or maybe it is already 
added, I haven't tried it yet), the omnios repo?

4) Will there be a repo for bloody releases?

5) If I do image a system with the bloody release, and add the omnios 
repo, and do a package update, (assuming I wait till the repo is updated 
to something beyond what is already installed on my server), will the 
update than put me back in the stable line, or will it be something else 
(somewhere between stable and bloody?)

thanks in advance for the answers,

Paul

From jesus at omniti.com  Wed Oct 17 08:37:35 2012
From: jesus at omniti.com (Theo Schlossnagle)
Date: Wed, 17 Oct 2012 08:37:35 -0400
Subject: [OmniOS-discuss] pkg update and omnios repos
In-Reply-To: <507EA1AC.8080002@alcatel-lucent.com>
References: <507EA1AC.8080002@alcatel-lucent.com>
Message-ID: <CACLsApuRxgxEKAL+TWvf=-xcdqt=SOdpjkvr25-D04n2S-zngg@mail.gmail.com>

On Wed, Oct 17, 2012 at 8:16 AM, Paul Jochum
<paul.jochum at alcatel-lucent.com> wrote:
> Hi All:
>
>     Wanted to ask some questions on the OmniOS package repo:
>
> 1) As new stable OmniOS releases are published, are the new packages added
> to the omnios repo, so that a pkg update command would update a system to
> the latest stable release?

Yes.

> 2) Is there some plan on when the omnios repo is updated?  For example, are
> all of the changed packages installed simultaneously into the OmniOS repo,
> or do they trickle in over a long time span?

They are received in over a short period of time.  We may be changing
this to be atomic in the near future.

> 3) Will there be announcements when the omnios repo is updated?

There are release announcements on the wiki.  I believe they are only
for the stable release.  For bloody, you'd need to follow the commits
on the illumos-omnios and omnios-build repos.

> 3) If I install the bloody release, can I add (or maybe it is already added,
> I haven't tried it yet), the omnios repo?

I choose to answer the second (3). bloody and omnios/release have 100%
overlap. It would be challenging to add both, as they use the same
publisher.

> 4) Will there be a repo for bloody releases?

There is. It is linked from the main wiki page.  Keep in mind that
bloody is more of a continual release process.

> 5) If I do image a system with the bloody release, and add the omnios repo,
> and do a package update, (assuming I wait till the repo is updated to
> something beyond what is already installed on my server), will the update
> than put me back in the stable line, or will it be something else (somewhere
> between stable and bloody?)

bloody will always be newer than stable, so once you go bloody, it
will be rather challenging to go back until the next stable release.

It *should* be the case that if you were to intall bloody today, then
switch the publisher url to the new stable release (due in few weeks),
it would upgrade correctly.

> thanks in advance for the answers,
>
> Paul
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss



-- 
Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle

From sergey57 at gmail.com  Wed Oct 17 16:49:43 2012
From: sergey57 at gmail.com (sergey ivanov)
Date: Wed, 17 Oct 2012 16:49:43 -0400
Subject: [OmniOS-discuss] mc package for OmniOS on http://pkg.cs.umd.edu
In-Reply-To: <507E8371.6040805@metalcon.pt>
References: <507E8371.6040805@metalcon.pt>
Message-ID: <CAAv=BDGKHed1+MrwaPV+Yt=y4cmdQb2qTORdmUyo41YsQ1Lpcw@mail.gmail.com>

Hi Agostino,
it was a bug in midnight commander's source code, patch already merged and
ready for pick-up.
See https://www.midnight-commander.org/ticket/2906.
I have published patched version at the same repo, http://pkg.cs.umd.edu.
If you run "pkg install mc", it should update midnight commander to this
fixed version.
-- 
  Regards,
  Sergey Ivanov.


On Wed, Oct 17, 2012 at 6:07 AM, Agostinho Sousa <agsousa at metalcon.pt>wrote:

>  Hi,
>
> I have installed mc package from the repo above and it work. But when I
> try copy (F5)/move (F6)  any file I receive a core dump and mc abort.
>
> The is anything that I can do to solve this?
>
> Thanks
> --
>
> *Melhores cumprimentos | Un saludo | Best regards | Cordiali saluti |??
> ???????? | Met vriendelijke groeten | Salutations*
>
> * Agostinho Sousa *
>  Direc??o de Sistemas de Informa??o | IT Department
> agsousa at metalcon.pt | M. +351 968 492 741
>
> Irm?os Silvas, S.A.
> Maganha - Santiago de Bougado - Apartado 206
> 4786-909 - TROFA
> Tel: +351 252 400 520 | Fax: +351 252 400 521
> metalcon at metalcon.pt | www.metalcon.pt
>
> *GRUPO METALCON *
> Metalcon Investimentos | Brasmar | Galvaza | Grupomar | LSM | Metalogalva
> | Silvafer
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>


-- 
Regards,
Sergey Ivanov | 443-844-6318 | sergey57 at gmail.com
http://www.linkedin.com/pub/sergey-ivanov/8/270/a09
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121017/92efd666/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: METALCONSGPS.PNG
Type: image/png
Size: 5474 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121017/92efd666/attachment.png>

From mabuqu at ilstu.edu  Wed Oct 17 19:25:56 2012
From: mabuqu at ilstu.edu (Majeed)
Date: Wed, 17 Oct 2012 18:25:56 -0500
Subject: [OmniOS-discuss] multipathing with compellent
Message-ID: <507F3E84.40208@ilstu.edu>

Hi All, We are doing some testing with omniOS in our datacenter and 
would love connect it up to our compellent san via fc connectivity. I 
slapped omniOS onto a dell r610 that has a qlogic dual port hba (each 
port is pathed to separate fabrics), performed zoning in each fabric, 
and assigned some luns. Now im not sure if compellent supports Solaris 
11 (i can contact them and see about that), but it definately support 
solaris 10 which is what we use on other production systems.

I'v actually made it pretty far through the process which is really 
exciting, except for the last multipathing bit. After mapping a volume 
to the host I can't seem to condense all the devices down to a single 
mulipathed device. It seems multipathing is enabled for the fp driver. I 
noticed there is not a mpathadm command.

Anyone have any ideas? I'll post some output from the commands i think 
of below. Let me know if you would like to see any other information.

Thanks much,
Majeed


On solaris 10 the main thing we have to do is add the following to 
/kernel/drv/scsi_vhci.conf (reconfigure reboot)
device-type-scsi-options-list =
"COMPELNTCompellent Vol", "symmetric-option";
symmetric-option = 0x1000000;


Here is the format output:
AVAILABLE DISK SELECTIONS:
        0. c13t5000CCA0213ED1E1d0 <HITACHI-HUC106030CSS600-A360 cyl 
36470 alt 2 hd 255 sec 63>
           
/pci at 0,0/pci8086,2940 at 1c/pci1028,1f1e at 0/iport at 40/disk at w5000cca0213ed1e1,0
        1. c14t5000CCA0213EFC7Dd0 <HITACHI-HUC106030CSS600-A360 cyl 
36469 alt 2 hd 255 sec 63>
           
/pci at 0,0/pci8086,2940 at 1c/pci1028,1f1e at 0/iport at 80/disk at w5000cca0213efc7d,0
        2. c16t5000D310004A064Bd1 <COMPELNT-CompellentVol-0505 cyl 65268 
alt 2 hd 255 sec 63>
           
/pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0/fp at 0,0/disk at w5000d310004a064b,1
        3. c17t5000D310004A064Cd1 <COMPELNT-CompellentVol-0505 cyl 65268 
alt 2 hd 255 sec 63>
           
/pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0,1/fp at 0,0/disk at w5000d310004a064c,1
Specify disk (enter its number): Specify disk (enter its number):



% fcinfo hba-port
HBA Port WWN: 2100001b32940767
     Port Mode: Initiator
     Port ID: 91c00
     OS Device Name: /dev/cfg/c16
     Manufacturer: QLogic Corp.
     Model: 375-3356-02
     Firmware Version: 05.03.01
     FCode/BIOS Version:  BIOS: 2.02; fcode: 2.01; EFI: 2.00;
     Serial Number: 0402H00-0941774287
     Driver Name: qlc
     Driver Version: 20100408-3.01
     Type: N-port
     State: online
     Supported Speeds: 1Gb 2Gb 4Gb
     Current Speed: 4Gb
     Node WWN: 2000001b32940767
     Max NPIV Ports: 127
     NPIV port list:
HBA Port WWN: 2101001b32b40767
     Port Mode: Initiator
     Port ID: a1900
     OS Device Name: /dev/cfg/c17
     Manufacturer: QLogic Corp.
     Model: 375-3356-02
     Firmware Version: 05.03.01
     FCode/BIOS Version:  BIOS: 2.02; fcode: 2.01; EFI: 2.00;
     Serial Number: 0402H00-0941774287
     Driver Name: qlc
     Driver Version: 20100408-3.01
     Type: N-port
     State: online
     Supported Speeds: 1Gb 2Gb 4Gb
     Current Speed: 4Gb
     Node WWN: 2001001b32b40767
     Max NPIV Ports: 127
     NPIV port list:


% cfgadm -al -o show_SCSI_LUN
Ap_Id                          Type         Receptacle   Occupant     
Condition
c16                            fc-fabric    connected    configured   
unknown
c16::5000d310004a0649          unknown      connected    unconfigured 
unknown
c16::5000d310004a064b,1        disk         connected    configured   
unknown
c17                            fc-fabric    connected    configured   
unknown
c17::5000d310004a064a          unknown      connected    unconfigured 
unknown
c17::5000d310004a064c,1        disk         connected    configured   
unknown



From mabuqu at ilstu.edu  Thu Oct 18 10:30:26 2012
From: mabuqu at ilstu.edu (Majeed)
Date: Thu, 18 Oct 2012 09:30:26 -0500
Subject: [OmniOS-discuss] multipathing with compellent
In-Reply-To: <507F3E84.40208@ilstu.edu>
References: <507F3E84.40208@ilstu.edu>
Message-ID: <50801282.9080608@ilstu.edu>

I just noticed that we do have access to the mpathadm command by 
installing the "pkg:/storage/mpathadm at 0.5.11-0.151002" package. After 
installing I don't see any paths with "mpathadm list LU" which is what 
im used to on solaris 10 (i know I should be comparing to solaris 11, 
just havn't played with it much). I wonder if there are any other bits 
that I need to install or other configuration tweaks to get this going.

Thanks in advance for any pointers,
Majeed

Some other related commands that might assist troubleshooting:

% uname -a
SunOS jhx011 5.11 omnios-eae537b i86pc i386 i86pc

% mpathadm list initiator-port
Initiator Port:  w5d4ae520937bbb00
Initiator Port:  iqn.1986-03.com.sun:01:b06a64f606ff.507f35b3,4000002a00ff
Initiator Port:  w5d4ae520937bbb00
Initiator Port:  2101001b32b40767
Initiator Port:  2100001b32940767

% luxadm -e port
/devices/pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0/fp at 0,0:devctl        CONNECTED
/devices/pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0,1/fp at 0,0:devctl      CONNECTED

% luxadm -v probe

Found Fibre Channel device(s):
   Node WWN:5000d310004a0602  Device Type:Disk device
     Logical Path:/dev/rdsk/c16t5000D310004A064Bd1s2
   Node WWN:5000d310004a0602  Device Type:Disk device
     Logical Path:/dev/rdsk/c17t5000D310004A064Cd1s2

% luxadm disp /dev/rdsk/c16t5000D310004A064Bd1s2
DEVICE PROPERTIES for disk: /dev/rdsk/c16t5000D310004A064Bd1s2
   Vendor:        COMPELNT
   Product ID:        Compellent Vol
   Revision:        0505
   Serial Num:        00004a06-00000014
   Unformatted capacity:    512000.000 MBytes
   Read Cache:        Enabled
     Minimum prefetch:    0x100
     Maximum prefetch:    0xf0
   Device Type:        Disk device
   Path(s):

   /dev/rdsk/c16t5000D310004A064Bd1s2
   
/devices/pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0/fp at 0,0/disk at w5000d310004a064b,1:c,raw
    Controller          /dev/cfg/c16
     Device Address        5000d310004a064b,1
     Host controller port WWN    2100001b32940767
    Controller          /dev/cfg/c17
     Device Address        5000d310004a064c,1
     Host controller port WWN    2101001b32b40767


On 10/17/2012 06:25 PM, Majeed wrote:
> Hi All, We are doing some testing with omniOS in our datacenter and 
> would love connect it up to our compellent san via fc connectivity. I 
> slapped omniOS onto a dell r610 that has a qlogic dual port hba (each 
> port is pathed to separate fabrics), performed zoning in each fabric, 
> and assigned some luns. Now im not sure if compellent supports Solaris 
> 11 (i can contact them and see about that), but it definately support 
> solaris 10 which is what we use on other production systems.
>
> I'v actually made it pretty far through the process which is really 
> exciting, except for the last multipathing bit. After mapping a volume 
> to the host I can't seem to condense all the devices down to a single 
> mulipathed device. It seems multipathing is enabled for the fp driver. 
> I noticed there is not a mpathadm command.
>
> Anyone have any ideas? I'll post some output from the commands i think 
> of below. Let me know if you would like to see any other information.
>
> Thanks much,
> Majeed
>
>
> On solaris 10 the main thing we have to do is add the following to 
> /kernel/drv/scsi_vhci.conf (reconfigure reboot)
> device-type-scsi-options-list =
> "COMPELNTCompellent Vol", "symmetric-option";
> symmetric-option = 0x1000000;
>
>
> Here is the format output:
> AVAILABLE DISK SELECTIONS:
>        0. c13t5000CCA0213ED1E1d0 <HITACHI-HUC106030CSS600-A360 cyl 
> 36470 alt 2 hd 255 sec 63>
>           
> /pci at 0,0/pci8086,2940 at 1c/pci1028,1f1e at 0/iport at 40/disk at w5000cca0213ed1e1,0
>        1. c14t5000CCA0213EFC7Dd0 <HITACHI-HUC106030CSS600-A360 cyl 
> 36469 alt 2 hd 255 sec 63>
>           
> /pci at 0,0/pci8086,2940 at 1c/pci1028,1f1e at 0/iport at 80/disk at w5000cca0213efc7d,0
>        2. c16t5000D310004A064Bd1 <COMPELNT-CompellentVol-0505 cyl 
> 65268 alt 2 hd 255 sec 63>
>           
> /pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0/fp at 0,0/disk at w5000d310004a064b,1
>        3. c17t5000D310004A064Cd1 <COMPELNT-CompellentVol-0505 cyl 
> 65268 alt 2 hd 255 sec 63>
>           
> /pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0,1/fp at 0,0/disk at w5000d310004a064c,1
> Specify disk (enter its number): Specify disk (enter its number):
>
>
>
> % fcinfo hba-port
> HBA Port WWN: 2100001b32940767
>     Port Mode: Initiator
>     Port ID: 91c00
>     OS Device Name: /dev/cfg/c16
>     Manufacturer: QLogic Corp.
>     Model: 375-3356-02
>     Firmware Version: 05.03.01
>     FCode/BIOS Version:  BIOS: 2.02; fcode: 2.01; EFI: 2.00;
>     Serial Number: 0402H00-0941774287
>     Driver Name: qlc
>     Driver Version: 20100408-3.01
>     Type: N-port
>     State: online
>     Supported Speeds: 1Gb 2Gb 4Gb
>     Current Speed: 4Gb
>     Node WWN: 2000001b32940767
>     Max NPIV Ports: 127
>     NPIV port list:
> HBA Port WWN: 2101001b32b40767
>     Port Mode: Initiator
>     Port ID: a1900
>     OS Device Name: /dev/cfg/c17
>     Manufacturer: QLogic Corp.
>     Model: 375-3356-02
>     Firmware Version: 05.03.01
>     FCode/BIOS Version:  BIOS: 2.02; fcode: 2.01; EFI: 2.00;
>     Serial Number: 0402H00-0941774287
>     Driver Name: qlc
>     Driver Version: 20100408-3.01
>     Type: N-port
>     State: online
>     Supported Speeds: 1Gb 2Gb 4Gb
>     Current Speed: 4Gb
>     Node WWN: 2001001b32b40767
>     Max NPIV Ports: 127
>     NPIV port list:
>
>
> % cfgadm -al -o show_SCSI_LUN
> Ap_Id                          Type         Receptacle   Occupant     
> Condition
> c16                            fc-fabric    connected    configured   
> unknown
> c16::5000d310004a0649          unknown      connected    unconfigured 
> unknown
> c16::5000d310004a064b,1        disk         connected    configured   
> unknown
> c17                            fc-fabric    connected    configured   
> unknown
> c17::5000d310004a064a          unknown      connected    unconfigured 
> unknown
> c17::5000d310004a064c,1        disk         connected    configured   
> unknown
>
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss


-- 
Majeed Abu-Qulbain
Lead Unix Admin - CISS
309-438-3455
Illinois State University


From mabuqu at ilstu.edu  Thu Oct 18 15:51:19 2012
From: mabuqu at ilstu.edu (Majeed)
Date: Thu, 18 Oct 2012 14:51:19 -0500
Subject: [OmniOS-discuss] multipathing with compellent
In-Reply-To: <50801282.9080608@ilstu.edu>
References: <507F3E84.40208@ilstu.edu> <50801282.9080608@ilstu.edu>
Message-ID: <50805DB7.2080608@ilstu.edu>

Hi Again, just wanted to update the list with my latest progress and 
thoughts on this topic. I think the issue lies in libmpscsi_vhci.so's 
lack of support for multipathing with compellent.

When I do "mpathadm show mpath-support libmpscsi_vhci.so" on omniOS I 
see many venders and models listed but not compellent. We are going to 
spin up a solaris 11 machine to see what it looks like. I wonder if this 
was forked just before SUN/oracle added support for compellent (i could 
be way off base here).

When I do the same command on solaris 10 u10, at the very bottom of the 
list i see.
                 Vendor:  COMPELNT
                 Product:  Compellent Vol
                 Revision:
                 Supported Load Balance Types:
                         round-robin

I have verified that multipathing is working properly on other arrays. I 
zoned up omniOS with all controllers on a 6140 (CSM200) that sit in 
multiple fabrics, mapped a lun, and it looks wonderful. mpatham reports 
as expected, and all paths are condensed to a single block device in 
format's output.

% mpathadm list LU
     /dev/rdsk/c0t600A0B800033816200001391507FF856d0s2
         Total Path Count: 4
         Operational Path Count: 4



It seems there are some options in /kernel/drv/scsi_vhci.conf to force 
scsi_vhci to accept 3rd party devices (hopefully compellent) for 
failover, but this is kinda getting over my head. It seems like if I had 
a proper ddi-forceload ''misc/scsi_vhci/scsi_vhci_f_<x>" file for 
compellent and I knew the proper VenderID and ProductID for the 
compellent devices, i might be able to force it. Im not sure if can use 
the information from the format inquiry to populate these values.

format> inquiry
Vendor:   COMPELNT
Product:  Compellent Vol
Revision: 0505


Any thoughts on this would be excellent.

Thanks,
Majeed Qulbain








On 10/18/2012 09:30 AM, Majeed wrote:
> I just noticed that we do have access to the mpathadm command by 
> installing the "pkg:/storage/mpathadm at 0.5.11-0.151002" package. After 
> installing I don't see any paths with "mpathadm list LU" which is what 
> im used to on solaris 10 (i know I should be comparing to solaris 11, 
> just havn't played with it much). I wonder if there are any other bits 
> that I need to install or other configuration tweaks to get this going.
>
> Thanks in advance for any pointers,
> Majeed
>
> Some other related commands that might assist troubleshooting:
>
> % uname -a
> SunOS jhx011 5.11 omnios-eae537b i86pc i386 i86pc
>
> % mpathadm list initiator-port
> Initiator Port:  w5d4ae520937bbb00
> Initiator Port:  
> iqn.1986-03.com.sun:01:b06a64f606ff.507f35b3,4000002a00ff
> Initiator Port:  w5d4ae520937bbb00
> Initiator Port:  2101001b32b40767
> Initiator Port:  2100001b32940767
>
> % luxadm -e port
> /devices/pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0/fp at 0,0:devctl        
> CONNECTED
> /devices/pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0,1/fp at 0,0:devctl      
> CONNECTED
>
> % luxadm -v probe
>
> Found Fibre Channel device(s):
>   Node WWN:5000d310004a0602  Device Type:Disk device
>     Logical Path:/dev/rdsk/c16t5000D310004A064Bd1s2
>   Node WWN:5000d310004a0602  Device Type:Disk device
>     Logical Path:/dev/rdsk/c17t5000D310004A064Cd1s2
>
> % luxadm disp /dev/rdsk/c16t5000D310004A064Bd1s2
> DEVICE PROPERTIES for disk: /dev/rdsk/c16t5000D310004A064Bd1s2
>   Vendor:        COMPELNT
>   Product ID:        Compellent Vol
>   Revision:        0505
>   Serial Num:        00004a06-00000014
>   Unformatted capacity:    512000.000 MBytes
>   Read Cache:        Enabled
>     Minimum prefetch:    0x100
>     Maximum prefetch:    0xf0
>   Device Type:        Disk device
>   Path(s):
>
>   /dev/rdsk/c16t5000D310004A064Bd1s2
>   
> /devices/pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0/fp at 0,0/disk at w5000d310004a064b,1:c,raw
>    Controller          /dev/cfg/c16
>     Device Address        5000d310004a064b,1
>     Host controller port WWN    2100001b32940767
>    Controller          /dev/cfg/c17
>     Device Address        5000d310004a064c,1
>     Host controller port WWN    2101001b32b40767
>
>
> On 10/17/2012 06:25 PM, Majeed wrote:
>> Hi All, We are doing some testing with omniOS in our datacenter and 
>> would love connect it up to our compellent san via fc connectivity. I 
>> slapped omniOS onto a dell r610 that has a qlogic dual port hba (each 
>> port is pathed to separate fabrics), performed zoning in each fabric, 
>> and assigned some luns. Now im not sure if compellent supports 
>> Solaris 11 (i can contact them and see about that), but it definately 
>> support solaris 10 which is what we use on other production systems.
>>
>> I'v actually made it pretty far through the process which is really 
>> exciting, except for the last multipathing bit. After mapping a 
>> volume to the host I can't seem to condense all the devices down to a 
>> single mulipathed device. It seems multipathing is enabled for the fp 
>> driver. I noticed there is not a mpathadm command.
>>
>> Anyone have any ideas? I'll post some output from the commands i 
>> think of below. Let me know if you would like to see any other 
>> information.
>>
>> Thanks much,
>> Majeed
>>
>>
>> On solaris 10 the main thing we have to do is add the following to 
>> /kernel/drv/scsi_vhci.conf (reconfigure reboot)
>> device-type-scsi-options-list =
>> "COMPELNTCompellent Vol", "symmetric-option";
>> symmetric-option = 0x1000000;
>>
>>
>> Here is the format output:
>> AVAILABLE DISK SELECTIONS:
>>        0. c13t5000CCA0213ED1E1d0 <HITACHI-HUC106030CSS600-A360 cyl 
>> 36470 alt 2 hd 255 sec 63>
>>           
>> /pci at 0,0/pci8086,2940 at 1c/pci1028,1f1e at 0/iport at 40/disk at w5000cca0213ed1e1,0
>>        1. c14t5000CCA0213EFC7Dd0 <HITACHI-HUC106030CSS600-A360 cyl 
>> 36469 alt 2 hd 255 sec 63>
>>           
>> /pci at 0,0/pci8086,2940 at 1c/pci1028,1f1e at 0/iport at 80/disk at w5000cca0213efc7d,0
>>        2. c16t5000D310004A064Bd1 <COMPELNT-CompellentVol-0505 cyl 
>> 65268 alt 2 hd 255 sec 63>
>>           
>> /pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0/fp at 0,0/disk at w5000d310004a064b,1
>>        3. c17t5000D310004A064Cd1 <COMPELNT-CompellentVol-0505 cyl 
>> 65268 alt 2 hd 255 sec 63>
>>           
>> /pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0,1/fp at 0,0/disk at w5000d310004a064c,1
>> Specify disk (enter its number): Specify disk (enter its number):
>>
>>
>>
>> % fcinfo hba-port
>> HBA Port WWN: 2100001b32940767
>>     Port Mode: Initiator
>>     Port ID: 91c00
>>     OS Device Name: /dev/cfg/c16
>>     Manufacturer: QLogic Corp.
>>     Model: 375-3356-02
>>     Firmware Version: 05.03.01
>>     FCode/BIOS Version:  BIOS: 2.02; fcode: 2.01; EFI: 2.00;
>>     Serial Number: 0402H00-0941774287
>>     Driver Name: qlc
>>     Driver Version: 20100408-3.01
>>     Type: N-port
>>     State: online
>>     Supported Speeds: 1Gb 2Gb 4Gb
>>     Current Speed: 4Gb
>>     Node WWN: 2000001b32940767
>>     Max NPIV Ports: 127
>>     NPIV port list:
>> HBA Port WWN: 2101001b32b40767
>>     Port Mode: Initiator
>>     Port ID: a1900
>>     OS Device Name: /dev/cfg/c17
>>     Manufacturer: QLogic Corp.
>>     Model: 375-3356-02
>>     Firmware Version: 05.03.01
>>     FCode/BIOS Version:  BIOS: 2.02; fcode: 2.01; EFI: 2.00;
>>     Serial Number: 0402H00-0941774287
>>     Driver Name: qlc
>>     Driver Version: 20100408-3.01
>>     Type: N-port
>>     State: online
>>     Supported Speeds: 1Gb 2Gb 4Gb
>>     Current Speed: 4Gb
>>     Node WWN: 2001001b32b40767
>>     Max NPIV Ports: 127
>>     NPIV port list:
>>
>>
>> % cfgadm -al -o show_SCSI_LUN
>> Ap_Id                          Type         Receptacle   Occupant     
>> Condition
>> c16                            fc-fabric    connected    configured   
>> unknown
>> c16::5000d310004a0649          unknown      connected    unconfigured 
>> unknown
>> c16::5000d310004a064b,1        disk         connected    configured   
>> unknown
>> c17                            fc-fabric    connected    configured   
>> unknown
>> c17::5000d310004a064a          unknown      connected    unconfigured 
>> unknown
>> c17::5000d310004a064c,1        disk         connected    configured   
>> unknown
>>
>>
>> _______________________________________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>

From jesus at omniti.com  Thu Oct 18 15:58:29 2012
From: jesus at omniti.com (Theo Schlossnagle)
Date: Thu, 18 Oct 2012 15:58:29 -0400
Subject: [OmniOS-discuss] multipathing with compellent
In-Reply-To: <50805DB7.2080608@ilstu.edu>
References: <507F3E84.40208@ilstu.edu> <50801282.9080608@ilstu.edu>
	<50805DB7.2080608@ilstu.edu>
Message-ID: <CACLsApuZ93z74s9d1QVerqpttkBMf2i+301H+7k6+hMevtLYvg@mail.gmail.com>

This is a more general Illumos problem, you will open your
troubleshooting to a larger audience by interfacing with the
illumos-discuss list.  I encourage you to post there! I'm subscribed
there as well, but I haven't done multipathing against compellent and
it appears no one else on the omnios-discuss list has either.
Anything learned in the illumos-discuss group can be applied directly
to OmniOS.

On Thu, Oct 18, 2012 at 3:51 PM, Majeed <mabuqu at ilstu.edu> wrote:
> Hi Again, just wanted to update the list with my latest progress and
> thoughts on this topic. I think the issue lies in libmpscsi_vhci.so's lack
> of support for multipathing with compellent.
>
> When I do "mpathadm show mpath-support libmpscsi_vhci.so" on omniOS I see
> many venders and models listed but not compellent. We are going to spin up a
> solaris 11 machine to see what it looks like. I wonder if this was forked
> just before SUN/oracle added support for compellent (i could be way off base
> here).
>
> When I do the same command on solaris 10 u10, at the very bottom of the list
> i see.
>                 Vendor:  COMPELNT
>                 Product:  Compellent Vol
>                 Revision:
>                 Supported Load Balance Types:
>                         round-robin
>
> I have verified that multipathing is working properly on other arrays. I
> zoned up omniOS with all controllers on a 6140 (CSM200) that sit in multiple
> fabrics, mapped a lun, and it looks wonderful. mpatham reports as expected,
> and all paths are condensed to a single block device in format's output.
>
> % mpathadm list LU
>     /dev/rdsk/c0t600A0B800033816200001391507FF856d0s2
>         Total Path Count: 4
>         Operational Path Count: 4
>
>
>
> It seems there are some options in /kernel/drv/scsi_vhci.conf to force
> scsi_vhci to accept 3rd party devices (hopefully compellent) for failover,
> but this is kinda getting over my head. It seems like if I had a proper
> ddi-forceload ''misc/scsi_vhci/scsi_vhci_f_<x>" file for compellent and I
> knew the proper VenderID and ProductID for the compellent devices, i might
> be able to force it. Im not sure if can use the information from the format
> inquiry to populate these values.
>
> format> inquiry
> Vendor:   COMPELNT
> Product:  Compellent Vol
> Revision: 0505
>
>
> Any thoughts on this would be excellent.
>
> Thanks,
> Majeed Qulbain
>
>
>
>
>
>
>
>
>
> On 10/18/2012 09:30 AM, Majeed wrote:
>>
>> I just noticed that we do have access to the mpathadm command by
>> installing the "pkg:/storage/mpathadm at 0.5.11-0.151002" package. After
>> installing I don't see any paths with "mpathadm list LU" which is what im
>> used to on solaris 10 (i know I should be comparing to solaris 11, just
>> havn't played with it much). I wonder if there are any other bits that I
>> need to install or other configuration tweaks to get this going.
>>
>> Thanks in advance for any pointers,
>> Majeed
>>
>> Some other related commands that might assist troubleshooting:
>>
>> % uname -a
>> SunOS jhx011 5.11 omnios-eae537b i86pc i386 i86pc
>>
>> % mpathadm list initiator-port
>> Initiator Port:  w5d4ae520937bbb00
>> Initiator Port:  iqn.1986-03.com.sun:01:b06a64f606ff.507f35b3,4000002a00ff
>> Initiator Port:  w5d4ae520937bbb00
>> Initiator Port:  2101001b32b40767
>> Initiator Port:  2100001b32940767
>>
>> % luxadm -e port
>> /devices/pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0/fp at 0,0:devctl
>> CONNECTED
>> /devices/pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0,1/fp at 0,0:devctl
>> CONNECTED
>>
>> % luxadm -v probe
>>
>> Found Fibre Channel device(s):
>>   Node WWN:5000d310004a0602  Device Type:Disk device
>>     Logical Path:/dev/rdsk/c16t5000D310004A064Bd1s2
>>   Node WWN:5000d310004a0602  Device Type:Disk device
>>     Logical Path:/dev/rdsk/c17t5000D310004A064Cd1s2
>>
>> % luxadm disp /dev/rdsk/c16t5000D310004A064Bd1s2
>> DEVICE PROPERTIES for disk: /dev/rdsk/c16t5000D310004A064Bd1s2
>>   Vendor:        COMPELNT
>>   Product ID:        Compellent Vol
>>   Revision:        0505
>>   Serial Num:        00004a06-00000014
>>   Unformatted capacity:    512000.000 MBytes
>>   Read Cache:        Enabled
>>     Minimum prefetch:    0x100
>>     Maximum prefetch:    0xf0
>>   Device Type:        Disk device
>>   Path(s):
>>
>>   /dev/rdsk/c16t5000D310004A064Bd1s2
>>
>> /devices/pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0/fp at 0,0/disk at w5000d310004a064b,1:c,raw
>>    Controller          /dev/cfg/c16
>>     Device Address        5000d310004a064b,1
>>     Host controller port WWN    2100001b32940767
>>    Controller          /dev/cfg/c17
>>     Device Address        5000d310004a064c,1
>>     Host controller port WWN    2101001b32b40767
>>
>>
>> On 10/17/2012 06:25 PM, Majeed wrote:
>>>
>>> Hi All, We are doing some testing with omniOS in our datacenter and would
>>> love connect it up to our compellent san via fc connectivity. I slapped
>>> omniOS onto a dell r610 that has a qlogic dual port hba (each port is pathed
>>> to separate fabrics), performed zoning in each fabric, and assigned some
>>> luns. Now im not sure if compellent supports Solaris 11 (i can contact them
>>> and see about that), but it definately support solaris 10 which is what we
>>> use on other production systems.
>>>
>>> I'v actually made it pretty far through the process which is really
>>> exciting, except for the last multipathing bit. After mapping a volume to
>>> the host I can't seem to condense all the devices down to a single
>>> mulipathed device. It seems multipathing is enabled for the fp driver. I
>>> noticed there is not a mpathadm command.
>>>
>>> Anyone have any ideas? I'll post some output from the commands i think of
>>> below. Let me know if you would like to see any other information.
>>>
>>> Thanks much,
>>> Majeed
>>>
>>>
>>> On solaris 10 the main thing we have to do is add the following to
>>> /kernel/drv/scsi_vhci.conf (reconfigure reboot)
>>> device-type-scsi-options-list =
>>> "COMPELNTCompellent Vol", "symmetric-option";
>>> symmetric-option = 0x1000000;
>>>
>>>
>>> Here is the format output:
>>> AVAILABLE DISK SELECTIONS:
>>>        0. c13t5000CCA0213ED1E1d0 <HITACHI-HUC106030CSS600-A360 cyl 36470
>>> alt 2 hd 255 sec 63>
>>>
>>> /pci at 0,0/pci8086,2940 at 1c/pci1028,1f1e at 0/iport at 40/disk at w5000cca0213ed1e1,0
>>>        1. c14t5000CCA0213EFC7Dd0 <HITACHI-HUC106030CSS600-A360 cyl 36469
>>> alt 2 hd 255 sec 63>
>>>
>>> /pci at 0,0/pci8086,2940 at 1c/pci1028,1f1e at 0/iport at 80/disk at w5000cca0213efc7d,0
>>>        2. c16t5000D310004A064Bd1 <COMPELNT-CompellentVol-0505 cyl 65268
>>> alt 2 hd 255 sec 63>
>>>
>>> /pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0/fp at 0,0/disk at w5000d310004a064b,1
>>>        3. c17t5000D310004A064Cd1 <COMPELNT-CompellentVol-0505 cyl 65268
>>> alt 2 hd 255 sec 63>
>>>
>>> /pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0,1/fp at 0,0/disk at w5000d310004a064c,1
>>> Specify disk (enter its number): Specify disk (enter its number):
>>>
>>>
>>>
>>> % fcinfo hba-port
>>> HBA Port WWN: 2100001b32940767
>>>     Port Mode: Initiator
>>>     Port ID: 91c00
>>>     OS Device Name: /dev/cfg/c16
>>>     Manufacturer: QLogic Corp.
>>>     Model: 375-3356-02
>>>     Firmware Version: 05.03.01
>>>     FCode/BIOS Version:  BIOS: 2.02; fcode: 2.01; EFI: 2.00;
>>>     Serial Number: 0402H00-0941774287
>>>     Driver Name: qlc
>>>     Driver Version: 20100408-3.01
>>>     Type: N-port
>>>     State: online
>>>     Supported Speeds: 1Gb 2Gb 4Gb
>>>     Current Speed: 4Gb
>>>     Node WWN: 2000001b32940767
>>>     Max NPIV Ports: 127
>>>     NPIV port list:
>>> HBA Port WWN: 2101001b32b40767
>>>     Port Mode: Initiator
>>>     Port ID: a1900
>>>     OS Device Name: /dev/cfg/c17
>>>     Manufacturer: QLogic Corp.
>>>     Model: 375-3356-02
>>>     Firmware Version: 05.03.01
>>>     FCode/BIOS Version:  BIOS: 2.02; fcode: 2.01; EFI: 2.00;
>>>     Serial Number: 0402H00-0941774287
>>>     Driver Name: qlc
>>>     Driver Version: 20100408-3.01
>>>     Type: N-port
>>>     State: online
>>>     Supported Speeds: 1Gb 2Gb 4Gb
>>>     Current Speed: 4Gb
>>>     Node WWN: 2001001b32b40767
>>>     Max NPIV Ports: 127
>>>     NPIV port list:
>>>
>>>
>>> % cfgadm -al -o show_SCSI_LUN
>>> Ap_Id                          Type         Receptacle   Occupant
>>> Condition
>>> c16                            fc-fabric    connected    configured
>>> unknown
>>> c16::5000d310004a0649          unknown      connected    unconfigured
>>> unknown
>>> c16::5000d310004a064b,1        disk         connected    configured
>>> unknown
>>> c17                            fc-fabric    connected    configured
>>> unknown
>>> c17::5000d310004a064a          unknown      connected    unconfigured
>>> unknown
>>> c17::5000d310004a064c,1        disk         connected    configured
>>> unknown
>>>
>>>
>>> _______________________________________________
>>> OmniOS-discuss mailing list
>>> OmniOS-discuss at lists.omniti.com
>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>>
>>
>>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss



-- 
Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle

From mabuqu at ilstu.edu  Thu Oct 18 16:06:00 2012
From: mabuqu at ilstu.edu (Majeed)
Date: Thu, 18 Oct 2012 15:06:00 -0500
Subject: [OmniOS-discuss] multipathing with compellent
In-Reply-To: <CACLsApuZ93z74s9d1QVerqpttkBMf2i+301H+7k6+hMevtLYvg@mail.gmail.com>
References: <507F3E84.40208@ilstu.edu> <50801282.9080608@ilstu.edu>
	<50805DB7.2080608@ilstu.edu>
	<CACLsApuZ93z74s9d1QVerqpttkBMf2i+301H+7k6+hMevtLYvg@mail.gmail.com>
Message-ID: <50806128.5030704@ilstu.edu>

Thanks Theo, that makes sense. I will definitely do that.

Majeed

On 10/18/2012 02:58 PM, Theo Schlossnagle wrote:
> This is a more general Illumos problem, you will open your
> troubleshooting to a larger audience by interfacing with the
> illumos-discuss list.  I encourage you to post there! I'm subscribed
> there as well, but I haven't done multipathing against compellent and
> it appears no one else on the omnios-discuss list has either.
> Anything learned in the illumos-discuss group can be applied directly
> to OmniOS.
>
> On Thu, Oct 18, 2012 at 3:51 PM, Majeed<mabuqu at ilstu.edu>  wrote:
>> Hi Again, just wanted to update the list with my latest progress and
>> thoughts on this topic. I think the issue lies in libmpscsi_vhci.so's lack
>> of support for multipathing with compellent.
>>
>> When I do "mpathadm show mpath-support libmpscsi_vhci.so" on omniOS I see
>> many venders and models listed but not compellent. We are going to spin up a
>> solaris 11 machine to see what it looks like. I wonder if this was forked
>> just before SUN/oracle added support for compellent (i could be way off base
>> here).
>>
>> When I do the same command on solaris 10 u10, at the very bottom of the list
>> i see.
>>                  Vendor:  COMPELNT
>>                  Product:  Compellent Vol
>>                  Revision:
>>                  Supported Load Balance Types:
>>                          round-robin
>>
>> I have verified that multipathing is working properly on other arrays. I
>> zoned up omniOS with all controllers on a 6140 (CSM200) that sit in multiple
>> fabrics, mapped a lun, and it looks wonderful. mpatham reports as expected,
>> and all paths are condensed to a single block device in format's output.
>>
>> % mpathadm list LU
>>      /dev/rdsk/c0t600A0B800033816200001391507FF856d0s2
>>          Total Path Count: 4
>>          Operational Path Count: 4
>>
>>
>>
>> It seems there are some options in /kernel/drv/scsi_vhci.conf to force
>> scsi_vhci to accept 3rd party devices (hopefully compellent) for failover,
>> but this is kinda getting over my head. It seems like if I had a proper
>> ddi-forceload ''misc/scsi_vhci/scsi_vhci_f_<x>" file for compellent and I
>> knew the proper VenderID and ProductID for the compellent devices, i might
>> be able to force it. Im not sure if can use the information from the format
>> inquiry to populate these values.
>>
>> format>  inquiry
>> Vendor:   COMPELNT
>> Product:  Compellent Vol
>> Revision: 0505
>>
>>
>> Any thoughts on this would be excellent.
>>
>> Thanks,
>> Majeed Qulbain
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On 10/18/2012 09:30 AM, Majeed wrote:
>>> I just noticed that we do have access to the mpathadm command by
>>> installing the "pkg:/storage/mpathadm at 0.5.11-0.151002" package. After
>>> installing I don't see any paths with "mpathadm list LU" which is what im
>>> used to on solaris 10 (i know I should be comparing to solaris 11, just
>>> havn't played with it much). I wonder if there are any other bits that I
>>> need to install or other configuration tweaks to get this going.
>>>
>>> Thanks in advance for any pointers,
>>> Majeed
>>>
>>> Some other related commands that might assist troubleshooting:
>>>
>>> % uname -a
>>> SunOS jhx011 5.11 omnios-eae537b i86pc i386 i86pc
>>>
>>> % mpathadm list initiator-port
>>> Initiator Port:  w5d4ae520937bbb00
>>> Initiator Port:  iqn.1986-03.com.sun:01:b06a64f606ff.507f35b3,4000002a00ff
>>> Initiator Port:  w5d4ae520937bbb00
>>> Initiator Port:  2101001b32b40767
>>> Initiator Port:  2100001b32940767
>>>
>>> % luxadm -e port
>>> /devices/pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0/fp at 0,0:devctl
>>> CONNECTED
>>> /devices/pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0,1/fp at 0,0:devctl
>>> CONNECTED
>>>
>>> % luxadm -v probe
>>>
>>> Found Fibre Channel device(s):
>>>    Node WWN:5000d310004a0602  Device Type:Disk device
>>>      Logical Path:/dev/rdsk/c16t5000D310004A064Bd1s2
>>>    Node WWN:5000d310004a0602  Device Type:Disk device
>>>      Logical Path:/dev/rdsk/c17t5000D310004A064Cd1s2
>>>
>>> % luxadm disp /dev/rdsk/c16t5000D310004A064Bd1s2
>>> DEVICE PROPERTIES for disk: /dev/rdsk/c16t5000D310004A064Bd1s2
>>>    Vendor:        COMPELNT
>>>    Product ID:        Compellent Vol
>>>    Revision:        0505
>>>    Serial Num:        00004a06-00000014
>>>    Unformatted capacity:    512000.000 MBytes
>>>    Read Cache:        Enabled
>>>      Minimum prefetch:    0x100
>>>      Maximum prefetch:    0xf0
>>>    Device Type:        Disk device
>>>    Path(s):
>>>
>>>    /dev/rdsk/c16t5000D310004A064Bd1s2
>>>
>>> /devices/pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0/fp at 0,0/disk at w5000d310004a064b,1:c,raw
>>>     Controller          /dev/cfg/c16
>>>      Device Address        5000d310004a064b,1
>>>      Host controller port WWN    2100001b32940767
>>>     Controller          /dev/cfg/c17
>>>      Device Address        5000d310004a064c,1
>>>      Host controller port WWN    2101001b32b40767
>>>
>>>
>>> On 10/17/2012 06:25 PM, Majeed wrote:
>>>> Hi All, We are doing some testing with omniOS in our datacenter and would
>>>> love connect it up to our compellent san via fc connectivity. I slapped
>>>> omniOS onto a dell r610 that has a qlogic dual port hba (each port is pathed
>>>> to separate fabrics), performed zoning in each fabric, and assigned some
>>>> luns. Now im not sure if compellent supports Solaris 11 (i can contact them
>>>> and see about that), but it definately support solaris 10 which is what we
>>>> use on other production systems.
>>>>
>>>> I'v actually made it pretty far through the process which is really
>>>> exciting, except for the last multipathing bit. After mapping a volume to
>>>> the host I can't seem to condense all the devices down to a single
>>>> mulipathed device. It seems multipathing is enabled for the fp driver. I
>>>> noticed there is not a mpathadm command.
>>>>
>>>> Anyone have any ideas? I'll post some output from the commands i think of
>>>> below. Let me know if you would like to see any other information.
>>>>
>>>> Thanks much,
>>>> Majeed
>>>>
>>>>
>>>> On solaris 10 the main thing we have to do is add the following to
>>>> /kernel/drv/scsi_vhci.conf (reconfigure reboot)
>>>> device-type-scsi-options-list =
>>>> "COMPELNTCompellent Vol", "symmetric-option";
>>>> symmetric-option = 0x1000000;
>>>>
>>>>
>>>> Here is the format output:
>>>> AVAILABLE DISK SELECTIONS:
>>>>         0. c13t5000CCA0213ED1E1d0<HITACHI-HUC106030CSS600-A360 cyl 36470
>>>> alt 2 hd 255 sec 63>
>>>>
>>>> /pci at 0,0/pci8086,2940 at 1c/pci1028,1f1e at 0/iport at 40/disk at w5000cca0213ed1e1,0
>>>>         1. c14t5000CCA0213EFC7Dd0<HITACHI-HUC106030CSS600-A360 cyl 36469
>>>> alt 2 hd 255 sec 63>
>>>>
>>>> /pci at 0,0/pci8086,2940 at 1c/pci1028,1f1e at 0/iport at 80/disk at w5000cca0213efc7d,0
>>>>         2. c16t5000D310004A064Bd1<COMPELNT-CompellentVol-0505 cyl 65268
>>>> alt 2 hd 255 sec 63>
>>>>
>>>> /pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0/fp at 0,0/disk at w5000d310004a064b,1
>>>>         3. c17t5000D310004A064Cd1<COMPELNT-CompellentVol-0505 cyl 65268
>>>> alt 2 hd 255 sec 63>
>>>>
>>>> /pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0,1/fp at 0,0/disk at w5000d310004a064c,1
>>>> Specify disk (enter its number): Specify disk (enter its number):
>>>>
>>>>
>>>>
>>>> % fcinfo hba-port
>>>> HBA Port WWN: 2100001b32940767
>>>>      Port Mode: Initiator
>>>>      Port ID: 91c00
>>>>      OS Device Name: /dev/cfg/c16
>>>>      Manufacturer: QLogic Corp.
>>>>      Model: 375-3356-02
>>>>      Firmware Version: 05.03.01
>>>>      FCode/BIOS Version:  BIOS: 2.02; fcode: 2.01; EFI: 2.00;
>>>>      Serial Number: 0402H00-0941774287
>>>>      Driver Name: qlc
>>>>      Driver Version: 20100408-3.01
>>>>      Type: N-port
>>>>      State: online
>>>>      Supported Speeds: 1Gb 2Gb 4Gb
>>>>      Current Speed: 4Gb
>>>>      Node WWN: 2000001b32940767
>>>>      Max NPIV Ports: 127
>>>>      NPIV port list:
>>>> HBA Port WWN: 2101001b32b40767
>>>>      Port Mode: Initiator
>>>>      Port ID: a1900
>>>>      OS Device Name: /dev/cfg/c17
>>>>      Manufacturer: QLogic Corp.
>>>>      Model: 375-3356-02
>>>>      Firmware Version: 05.03.01
>>>>      FCode/BIOS Version:  BIOS: 2.02; fcode: 2.01; EFI: 2.00;
>>>>      Serial Number: 0402H00-0941774287
>>>>      Driver Name: qlc
>>>>      Driver Version: 20100408-3.01
>>>>      Type: N-port
>>>>      State: online
>>>>      Supported Speeds: 1Gb 2Gb 4Gb
>>>>      Current Speed: 4Gb
>>>>      Node WWN: 2001001b32b40767
>>>>      Max NPIV Ports: 127
>>>>      NPIV port list:
>>>>
>>>>
>>>> % cfgadm -al -o show_SCSI_LUN
>>>> Ap_Id                          Type         Receptacle   Occupant
>>>> Condition
>>>> c16                            fc-fabric    connected    configured
>>>> unknown
>>>> c16::5000d310004a0649          unknown      connected    unconfigured
>>>> unknown
>>>> c16::5000d310004a064b,1        disk         connected    configured
>>>> unknown
>>>> c17                            fc-fabric    connected    configured
>>>> unknown
>>>> c17::5000d310004a064a          unknown      connected    unconfigured
>>>> unknown
>>>> c17::5000d310004a064c,1        disk         connected    configured
>>>> unknown
>>>>
>>>>
>>>> _______________________________________________
>>>> OmniOS-discuss mailing list
>>>> OmniOS-discuss at lists.omniti.com
>>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>>>
>>>
>> _______________________________________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>


-- 
Majeed Abu-Qulbain
Lead Unix Admin - CISS
309-438-3455
Illinois State University


From mabuqu at ilstu.edu  Thu Oct 18 16:35:33 2012
From: mabuqu at ilstu.edu (Majeed)
Date: Thu, 18 Oct 2012 15:35:33 -0500
Subject: [OmniOS-discuss] multipathing against compellent
In-Reply-To: <50806128.5030704@ilstu.edu>
References: <507F3E84.40208@ilstu.edu> <50801282.9080608@ilstu.edu>
	<50805DB7.2080608@ilstu.edu>
	<CACLsApuZ93z74s9d1QVerqpttkBMf2i+301H+7k6+hMevtLYvg@mail.gmail.com>
	<50806128.5030704@ilstu.edu>
Message-ID: <50806815.9000505@ilstu.edu>

Hi All, As noted below, we have attempted to test the illumos based 
omniOS in our datacenter on a dell R610 connected through dual cisco 
fiber channel fabrics to a compellent SAN with dual controllers. We got 
pretty far with an out of the box setup until the last multipathing bit. 
I was hoping there might be some additional eyes on this list that may 
be able to provide some insight.

Thanks in advance for taking the time to read through my following notes 
on this topic,
Majeed Qulbain




On 10/18/2012 03:06 PM, Majeed wrote:
> Thanks Theo, that makes sense. I will definitely do that.
>
> Majeed
>
> On 10/18/2012 02:58 PM, Theo Schlossnagle wrote:
>> This is a more general Illumos problem, you will open your
>> troubleshooting to a larger audience by interfacing with the
>> illumos-discuss list.  I encourage you to post there! I'm subscribed
>> there as well, but I haven't done multipathing against compellent and
>> it appears no one else on the omnios-discuss list has either.
>> Anything learned in the illumos-discuss group can be applied directly
>> to OmniOS.
>>
>> On Thu, Oct 18, 2012 at 3:51 PM, Majeed<mabuqu at ilstu.edu>  wrote:
>>> Hi Again, just wanted to update the list with my latest progress and
>>> thoughts on this topic. I think the issue lies in 
>>> libmpscsi_vhci.so's lack
>>> of support for multipathing with compellent.
>>>
>>> When I do "mpathadm show mpath-support libmpscsi_vhci.so" on omniOS 
>>> I see
>>> many venders and models listed but not compellent. We are going to 
>>> spin up a
>>> solaris 11 machine to see what it looks like. I wonder if this was 
>>> forked
>>> just before SUN/oracle added support for compellent (i could be way 
>>> off base
>>> here).
>>>
>>> When I do the same command on solaris 10 u10, at the very bottom of 
>>> the list
>>> i see.
>>>                  Vendor:  COMPELNT
>>>                  Product:  Compellent Vol
>>>                  Revision:
>>>                  Supported Load Balance Types:
>>>                          round-robin
>>>
>>> I have verified that multipathing is working properly on other 
>>> arrays. I
>>> zoned up omniOS with all controllers on a 6140 (CSM200) that sit in 
>>> multiple
>>> fabrics, mapped a lun, and it looks wonderful. mpatham reports as 
>>> expected,
>>> and all paths are condensed to a single block device in format's 
>>> output.
>>>
>>> % mpathadm list LU
>>>      /dev/rdsk/c0t600A0B800033816200001391507FF856d0s2
>>>          Total Path Count: 4
>>>          Operational Path Count: 4
>>>
>>>
>>>
>>> It seems there are some options in /kernel/drv/scsi_vhci.conf to force
>>> scsi_vhci to accept 3rd party devices (hopefully compellent) for 
>>> failover,
>>> but this is kinda getting over my head. It seems like if I had a proper
>>> ddi-forceload ''misc/scsi_vhci/scsi_vhci_f_<x>" file for compellent 
>>> and I
>>> knew the proper VenderID and ProductID for the compellent devices, i 
>>> might
>>> be able to force it. Im not sure if can use the information from the 
>>> format
>>> inquiry to populate these values.
>>>
>>> format>  inquiry
>>> Vendor:   COMPELNT
>>> Product:  Compellent Vol
>>> Revision: 0505
>>>
>>>
>>> Any thoughts on this would be excellent.
>>>
>>> Thanks,
>>> Majeed Qulbain
>>>
>>>
>>>
>>> On 10/18/2012 09:30 AM, Majeed wrote:
>>>> I just noticed that we do have access to the mpathadm command by
>>>> installing the "pkg:/storage/mpathadm at 0.5.11-0.151002" package. After
>>>> installing I don't see any paths with "mpathadm list LU" which is 
>>>> what im
>>>> used to on solaris 10 (i know I should be comparing to solaris 11, 
>>>> just
>>>> havn't played with it much). I wonder if there are any other bits 
>>>> that I
>>>> need to install or other configuration tweaks to get this going.
>>>>
>>>> Thanks in advance for any pointers,
>>>> Majeed
>>>>
>>>> Some other related commands that might assist troubleshooting:
>>>>
>>>> % uname -a
>>>> SunOS jhx011 5.11 omnios-eae537b i86pc i386 i86pc
>>>>
>>>> % mpathadm list initiator-port
>>>> Initiator Port:  w5d4ae520937bbb00
>>>> Initiator Port:  
>>>> iqn.1986-03.com.sun:01:b06a64f606ff.507f35b3,4000002a00ff
>>>> Initiator Port:  w5d4ae520937bbb00
>>>> Initiator Port:  2101001b32b40767
>>>> Initiator Port:  2100001b32940767
>>>>
>>>> % luxadm -e port
>>>> /devices/pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0/fp at 0,0:devctl
>>>> CONNECTED
>>>> /devices/pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0,1/fp at 0,0:devctl
>>>> CONNECTED
>>>>
>>>> % luxadm -v probe
>>>>
>>>> Found Fibre Channel device(s):
>>>>    Node WWN:5000d310004a0602  Device Type:Disk device
>>>>      Logical Path:/dev/rdsk/c16t5000D310004A064Bd1s2
>>>>    Node WWN:5000d310004a0602  Device Type:Disk device
>>>>      Logical Path:/dev/rdsk/c17t5000D310004A064Cd1s2
>>>>
>>>> % luxadm disp /dev/rdsk/c16t5000D310004A064Bd1s2
>>>> DEVICE PROPERTIES for disk: /dev/rdsk/c16t5000D310004A064Bd1s2
>>>>    Vendor:        COMPELNT
>>>>    Product ID:        Compellent Vol
>>>>    Revision:        0505
>>>>    Serial Num:        00004a06-00000014
>>>>    Unformatted capacity:    512000.000 MBytes
>>>>    Read Cache:        Enabled
>>>>      Minimum prefetch:    0x100
>>>>      Maximum prefetch:    0xf0
>>>>    Device Type:        Disk device
>>>>    Path(s):
>>>>
>>>>    /dev/rdsk/c16t5000D310004A064Bd1s2
>>>>
>>>> /devices/pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0/fp at 0,0/disk at w5000d310004a064b,1:c,raw 
>>>>
>>>>     Controller          /dev/cfg/c16
>>>>      Device Address        5000d310004a064b,1
>>>>      Host controller port WWN    2100001b32940767
>>>>     Controller          /dev/cfg/c17
>>>>      Device Address        5000d310004a064c,1
>>>>      Host controller port WWN    2101001b32b40767
>>>>
>>>>
>>>> On 10/17/2012 06:25 PM, Majeed wrote:
>>>>> Hi All, We are doing some testing with omniOS in our datacenter 
>>>>> and would
>>>>> love connect it up to our compellent san via fc connectivity. I 
>>>>> slapped
>>>>> omniOS onto a dell r610 that has a qlogic dual port hba (each port 
>>>>> is pathed
>>>>> to separate fabrics), performed zoning in each fabric, and 
>>>>> assigned some
>>>>> luns. Now im not sure if compellent supports Solaris 11 (i can 
>>>>> contact them
>>>>> and see about that), but it definately support solaris 10 which is 
>>>>> what we
>>>>> use on other production systems.
>>>>>
>>>>> I'v actually made it pretty far through the process which is really
>>>>> exciting, except for the last multipathing bit. After mapping a 
>>>>> volume to
>>>>> the host I can't seem to condense all the devices down to a single
>>>>> mulipathed device. It seems multipathing is enabled for the fp 
>>>>> driver. I
>>>>> noticed there is not a mpathadm command.
>>>>>
>>>>> Anyone have any ideas? I'll post some output from the commands i 
>>>>> think of
>>>>> below. Let me know if you would like to see any other information.
>>>>>
>>>>> Thanks much,
>>>>> Majeed
>>>>>
>>>>>
>>>>> On solaris 10 the main thing we have to do is add the following to
>>>>> /kernel/drv/scsi_vhci.conf (reconfigure reboot)
>>>>> device-type-scsi-options-list =
>>>>> "COMPELNTCompellent Vol", "symmetric-option";
>>>>> symmetric-option = 0x1000000;
>>>>>
>>>>>
>>>>> Here is the format output:
>>>>> AVAILABLE DISK SELECTIONS:
>>>>>         0. c13t5000CCA0213ED1E1d0<HITACHI-HUC106030CSS600-A360 cyl 
>>>>> 36470
>>>>> alt 2 hd 255 sec 63>
>>>>>
>>>>> /pci at 0,0/pci8086,2940 at 1c/pci1028,1f1e at 0/iport at 40/disk at w5000cca0213ed1e1,0 
>>>>>
>>>>>         1. c14t5000CCA0213EFC7Dd0<HITACHI-HUC106030CSS600-A360 cyl 
>>>>> 36469
>>>>> alt 2 hd 255 sec 63>
>>>>>
>>>>> /pci at 0,0/pci8086,2940 at 1c/pci1028,1f1e at 0/iport at 80/disk at w5000cca0213efc7d,0 
>>>>>
>>>>>         2. c16t5000D310004A064Bd1<COMPELNT-CompellentVol-0505 cyl 
>>>>> 65268
>>>>> alt 2 hd 255 sec 63>
>>>>>
>>>>> /pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0/fp at 0,0/disk at w5000d310004a064b,1
>>>>>         3. c17t5000D310004A064Cd1<COMPELNT-CompellentVol-0505 cyl 
>>>>> 65268
>>>>> alt 2 hd 255 sec 63>
>>>>>
>>>>> /pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0,1/fp at 0,0/disk at w5000d310004a064c,1 
>>>>>
>>>>> Specify disk (enter its number): Specify disk (enter its number):
>>>>>
>>>>>
>>>>>
>>>>> % fcinfo hba-port
>>>>> HBA Port WWN: 2100001b32940767
>>>>>      Port Mode: Initiator
>>>>>      Port ID: 91c00
>>>>>      OS Device Name: /dev/cfg/c16
>>>>>      Manufacturer: QLogic Corp.
>>>>>      Model: 375-3356-02
>>>>>      Firmware Version: 05.03.01
>>>>>      FCode/BIOS Version:  BIOS: 2.02; fcode: 2.01; EFI: 2.00;
>>>>>      Serial Number: 0402H00-0941774287
>>>>>      Driver Name: qlc
>>>>>      Driver Version: 20100408-3.01
>>>>>      Type: N-port
>>>>>      State: online
>>>>>      Supported Speeds: 1Gb 2Gb 4Gb
>>>>>      Current Speed: 4Gb
>>>>>      Node WWN: 2000001b32940767
>>>>>      Max NPIV Ports: 127
>>>>>      NPIV port list:
>>>>> HBA Port WWN: 2101001b32b40767
>>>>>      Port Mode: Initiator
>>>>>      Port ID: a1900
>>>>>      OS Device Name: /dev/cfg/c17
>>>>>      Manufacturer: QLogic Corp.
>>>>>      Model: 375-3356-02
>>>>>      Firmware Version: 05.03.01
>>>>>      FCode/BIOS Version:  BIOS: 2.02; fcode: 2.01; EFI: 2.00;
>>>>>      Serial Number: 0402H00-0941774287
>>>>>      Driver Name: qlc
>>>>>      Driver Version: 20100408-3.01
>>>>>      Type: N-port
>>>>>      State: online
>>>>>      Supported Speeds: 1Gb 2Gb 4Gb
>>>>>      Current Speed: 4Gb
>>>>>      Node WWN: 2001001b32b40767
>>>>>      Max NPIV Ports: 127
>>>>>      NPIV port list:
>>>>>
>>>>>
>>>>> % cfgadm -al -o show_SCSI_LUN
>>>>> Ap_Id                          Type         Receptacle   Occupant
>>>>> Condition
>>>>> c16                            fc-fabric    connected    configured
>>>>> unknown
>>>>> c16::5000d310004a0649          unknown      connected    unconfigured
>>>>> unknown
>>>>> c16::5000d310004a064b,1        disk         connected    configured
>>>>> unknown
>>>>> c17                            fc-fabric    connected    configured
>>>>> unknown
>>>>> c17::5000d310004a064a          unknown      connected    unconfigured
>>>>> unknown
>>>>> c17::5000d310004a064c,1        disk         connected    configured
>>>>> unknown
>>>>>
>>>>>
>>>>> _______________________________________________


From mabuqu at ilstu.edu  Thu Oct 18 16:45:15 2012
From: mabuqu at ilstu.edu (Majeed)
Date: Thu, 18 Oct 2012 15:45:15 -0500
Subject: [OmniOS-discuss] multipathing against compellent
In-Reply-To: <50806815.9000505@ilstu.edu>
References: <507F3E84.40208@ilstu.edu> <50801282.9080608@ilstu.edu>
	<50805DB7.2080608@ilstu.edu>
	<CACLsApuZ93z74s9d1QVerqpttkBMf2i+301H+7k6+hMevtLYvg@mail.gmail.com>
	<50806128.5030704@ilstu.edu> <50806815.9000505@ilstu.edu>
Message-ID: <50806A5B.1050907@ilstu.edu>

Sorry for the spam everyone, wrong list :(

On 10/18/2012 03:35 PM, Majeed wrote:
> Hi All, As noted below, we have attempted to test the illumos based 
> omniOS in our datacenter on a dell R610 connected through dual cisco 
> fiber channel fabrics to a compellent SAN with dual controllers. We 
> got pretty far with an out of the box setup until the last 
> multipathing bit. I was hoping there might be some additional eyes on 
> this list that may be able to provide some insight.
>
> Thanks in advance for taking the time to read through my following 
> notes on this topic,
> Majeed Qulbain
>
>
>
>
> On 10/18/2012 03:06 PM, Majeed wrote:
>> Thanks Theo, that makes sense. I will definitely do that.
>>
>> Majeed
>>
>> On 10/18/2012 02:58 PM, Theo Schlossnagle wrote:
>>> This is a more general Illumos problem, you will open your
>>> troubleshooting to a larger audience by interfacing with the
>>> illumos-discuss list.  I encourage you to post there! I'm subscribed
>>> there as well, but I haven't done multipathing against compellent and
>>> it appears no one else on the omnios-discuss list has either.
>>> Anything learned in the illumos-discuss group can be applied directly
>>> to OmniOS.
>>>
>>> On Thu, Oct 18, 2012 at 3:51 PM, Majeed<mabuqu at ilstu.edu>  wrote:
>>>> Hi Again, just wanted to update the list with my latest progress and
>>>> thoughts on this topic. I think the issue lies in 
>>>> libmpscsi_vhci.so's lack
>>>> of support for multipathing with compellent.
>>>>
>>>> When I do "mpathadm show mpath-support libmpscsi_vhci.so" on omniOS 
>>>> I see
>>>> many venders and models listed but not compellent. We are going to 
>>>> spin up a
>>>> solaris 11 machine to see what it looks like. I wonder if this was 
>>>> forked
>>>> just before SUN/oracle added support for compellent (i could be way 
>>>> off base
>>>> here).
>>>>
>>>> When I do the same command on solaris 10 u10, at the very bottom of 
>>>> the list
>>>> i see.
>>>>                  Vendor:  COMPELNT
>>>>                  Product:  Compellent Vol
>>>>                  Revision:
>>>>                  Supported Load Balance Types:
>>>>                          round-robin
>>>>
>>>> I have verified that multipathing is working properly on other 
>>>> arrays. I
>>>> zoned up omniOS with all controllers on a 6140 (CSM200) that sit in 
>>>> multiple
>>>> fabrics, mapped a lun, and it looks wonderful. mpatham reports as 
>>>> expected,
>>>> and all paths are condensed to a single block device in format's 
>>>> output.
>>>>
>>>> % mpathadm list LU
>>>>      /dev/rdsk/c0t600A0B800033816200001391507FF856d0s2
>>>>          Total Path Count: 4
>>>>          Operational Path Count: 4
>>>>
>>>>
>>>>
>>>> It seems there are some options in /kernel/drv/scsi_vhci.conf to force
>>>> scsi_vhci to accept 3rd party devices (hopefully compellent) for 
>>>> failover,
>>>> but this is kinda getting over my head. It seems like if I had a 
>>>> proper
>>>> ddi-forceload ''misc/scsi_vhci/scsi_vhci_f_<x>" file for compellent 
>>>> and I
>>>> knew the proper VenderID and ProductID for the compellent devices, 
>>>> i might
>>>> be able to force it. Im not sure if can use the information from 
>>>> the format
>>>> inquiry to populate these values.
>>>>
>>>> format>  inquiry
>>>> Vendor:   COMPELNT
>>>> Product:  Compellent Vol
>>>> Revision: 0505
>>>>
>>>>
>>>> Any thoughts on this would be excellent.
>>>>
>>>> Thanks,
>>>> Majeed Qulbain
>>>>
>>>>
>>>>
>>>> On 10/18/2012 09:30 AM, Majeed wrote:
>>>>> I just noticed that we do have access to the mpathadm command by
>>>>> installing the "pkg:/storage/mpathadm at 0.5.11-0.151002" package. After
>>>>> installing I don't see any paths with "mpathadm list LU" which is 
>>>>> what im
>>>>> used to on solaris 10 (i know I should be comparing to solaris 11, 
>>>>> just
>>>>> havn't played with it much). I wonder if there are any other bits 
>>>>> that I
>>>>> need to install or other configuration tweaks to get this going.
>>>>>
>>>>> Thanks in advance for any pointers,
>>>>> Majeed
>>>>>
>>>>> Some other related commands that might assist troubleshooting:
>>>>>
>>>>> % uname -a
>>>>> SunOS jhx011 5.11 omnios-eae537b i86pc i386 i86pc
>>>>>
>>>>> % mpathadm list initiator-port
>>>>> Initiator Port:  w5d4ae520937bbb00
>>>>> Initiator Port:  
>>>>> iqn.1986-03.com.sun:01:b06a64f606ff.507f35b3,4000002a00ff
>>>>> Initiator Port:  w5d4ae520937bbb00
>>>>> Initiator Port:  2101001b32b40767
>>>>> Initiator Port:  2100001b32940767
>>>>>
>>>>> % luxadm -e port
>>>>> /devices/pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0/fp at 0,0:devctl
>>>>> CONNECTED
>>>>> /devices/pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0,1/fp at 0,0:devctl
>>>>> CONNECTED
>>>>>
>>>>> % luxadm -v probe
>>>>>
>>>>> Found Fibre Channel device(s):
>>>>>    Node WWN:5000d310004a0602  Device Type:Disk device
>>>>>      Logical Path:/dev/rdsk/c16t5000D310004A064Bd1s2
>>>>>    Node WWN:5000d310004a0602  Device Type:Disk device
>>>>>      Logical Path:/dev/rdsk/c17t5000D310004A064Cd1s2
>>>>>
>>>>> % luxadm disp /dev/rdsk/c16t5000D310004A064Bd1s2
>>>>> DEVICE PROPERTIES for disk: /dev/rdsk/c16t5000D310004A064Bd1s2
>>>>>    Vendor:        COMPELNT
>>>>>    Product ID:        Compellent Vol
>>>>>    Revision:        0505
>>>>>    Serial Num:        00004a06-00000014
>>>>>    Unformatted capacity:    512000.000 MBytes
>>>>>    Read Cache:        Enabled
>>>>>      Minimum prefetch:    0x100
>>>>>      Maximum prefetch:    0xf0
>>>>>    Device Type:        Disk device
>>>>>    Path(s):
>>>>>
>>>>>    /dev/rdsk/c16t5000D310004A064Bd1s2
>>>>>
>>>>> /devices/pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0/fp at 0,0/disk at w5000d310004a064b,1:c,raw 
>>>>>
>>>>>     Controller          /dev/cfg/c16
>>>>>      Device Address        5000d310004a064b,1
>>>>>      Host controller port WWN    2100001b32940767
>>>>>     Controller          /dev/cfg/c17
>>>>>      Device Address        5000d310004a064c,1
>>>>>      Host controller port WWN    2101001b32b40767
>>>>>
>>>>>
>>>>> On 10/17/2012 06:25 PM, Majeed wrote:
>>>>>> Hi All, We are doing some testing with omniOS in our datacenter 
>>>>>> and would
>>>>>> love connect it up to our compellent san via fc connectivity. I 
>>>>>> slapped
>>>>>> omniOS onto a dell r610 that has a qlogic dual port hba (each 
>>>>>> port is pathed
>>>>>> to separate fabrics), performed zoning in each fabric, and 
>>>>>> assigned some
>>>>>> luns. Now im not sure if compellent supports Solaris 11 (i can 
>>>>>> contact them
>>>>>> and see about that), but it definately support solaris 10 which 
>>>>>> is what we
>>>>>> use on other production systems.
>>>>>>
>>>>>> I'v actually made it pretty far through the process which is really
>>>>>> exciting, except for the last multipathing bit. After mapping a 
>>>>>> volume to
>>>>>> the host I can't seem to condense all the devices down to a single
>>>>>> mulipathed device. It seems multipathing is enabled for the fp 
>>>>>> driver. I
>>>>>> noticed there is not a mpathadm command.
>>>>>>
>>>>>> Anyone have any ideas? I'll post some output from the commands i 
>>>>>> think of
>>>>>> below. Let me know if you would like to see any other information.
>>>>>>
>>>>>> Thanks much,
>>>>>> Majeed
>>>>>>
>>>>>>
>>>>>> On solaris 10 the main thing we have to do is add the following to
>>>>>> /kernel/drv/scsi_vhci.conf (reconfigure reboot)
>>>>>> device-type-scsi-options-list =
>>>>>> "COMPELNTCompellent Vol", "symmetric-option";
>>>>>> symmetric-option = 0x1000000;
>>>>>>
>>>>>>
>>>>>> Here is the format output:
>>>>>> AVAILABLE DISK SELECTIONS:
>>>>>>         0. c13t5000CCA0213ED1E1d0<HITACHI-HUC106030CSS600-A360 
>>>>>> cyl 36470
>>>>>> alt 2 hd 255 sec 63>
>>>>>>
>>>>>> /pci at 0,0/pci8086,2940 at 1c/pci1028,1f1e at 0/iport at 40/disk at w5000cca0213ed1e1,0 
>>>>>>
>>>>>>         1. c14t5000CCA0213EFC7Dd0<HITACHI-HUC106030CSS600-A360 
>>>>>> cyl 36469
>>>>>> alt 2 hd 255 sec 63>
>>>>>>
>>>>>> /pci at 0,0/pci8086,2940 at 1c/pci1028,1f1e at 0/iport at 80/disk at w5000cca0213efc7d,0 
>>>>>>
>>>>>>         2. c16t5000D310004A064Bd1<COMPELNT-CompellentVol-0505 cyl 
>>>>>> 65268
>>>>>> alt 2 hd 255 sec 63>
>>>>>>
>>>>>> /pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0/fp at 0,0/disk at w5000d310004a064b,1 
>>>>>>
>>>>>>         3. c17t5000D310004A064Cd1<COMPELNT-CompellentVol-0505 cyl 
>>>>>> 65268
>>>>>> alt 2 hd 255 sec 63>
>>>>>>
>>>>>> /pci at 0,0/pci8086,3410 at 9/pci1077,143 at 0,1/fp at 0,0/disk at w5000d310004a064c,1 
>>>>>>
>>>>>> Specify disk (enter its number): Specify disk (enter its number):
>>>>>>
>>>>>>
>>>>>>
>>>>>> % fcinfo hba-port
>>>>>> HBA Port WWN: 2100001b32940767
>>>>>>      Port Mode: Initiator
>>>>>>      Port ID: 91c00
>>>>>>      OS Device Name: /dev/cfg/c16
>>>>>>      Manufacturer: QLogic Corp.
>>>>>>      Model: 375-3356-02
>>>>>>      Firmware Version: 05.03.01
>>>>>>      FCode/BIOS Version:  BIOS: 2.02; fcode: 2.01; EFI: 2.00;
>>>>>>      Serial Number: 0402H00-0941774287
>>>>>>      Driver Name: qlc
>>>>>>      Driver Version: 20100408-3.01
>>>>>>      Type: N-port
>>>>>>      State: online
>>>>>>      Supported Speeds: 1Gb 2Gb 4Gb
>>>>>>      Current Speed: 4Gb
>>>>>>      Node WWN: 2000001b32940767
>>>>>>      Max NPIV Ports: 127
>>>>>>      NPIV port list:
>>>>>> HBA Port WWN: 2101001b32b40767
>>>>>>      Port Mode: Initiator
>>>>>>      Port ID: a1900
>>>>>>      OS Device Name: /dev/cfg/c17
>>>>>>      Manufacturer: QLogic Corp.
>>>>>>      Model: 375-3356-02
>>>>>>      Firmware Version: 05.03.01
>>>>>>      FCode/BIOS Version:  BIOS: 2.02; fcode: 2.01; EFI: 2.00;
>>>>>>      Serial Number: 0402H00-0941774287
>>>>>>      Driver Name: qlc
>>>>>>      Driver Version: 20100408-3.01
>>>>>>      Type: N-port
>>>>>>      State: online
>>>>>>      Supported Speeds: 1Gb 2Gb 4Gb
>>>>>>      Current Speed: 4Gb
>>>>>>      Node WWN: 2001001b32b40767
>>>>>>      Max NPIV Ports: 127
>>>>>>      NPIV port list:
>>>>>>
>>>>>>
>>>>>> % cfgadm -al -o show_SCSI_LUN
>>>>>> Ap_Id                          Type         Receptacle   Occupant
>>>>>> Condition
>>>>>> c16                            fc-fabric    connected    configured
>>>>>> unknown
>>>>>> c16::5000d310004a0649          unknown      connected    
>>>>>> unconfigured
>>>>>> unknown
>>>>>> c16::5000d310004a064b,1        disk         connected    configured
>>>>>> unknown
>>>>>> c17                            fc-fabric    connected    configured
>>>>>> unknown
>>>>>> c17::5000d310004a064a          unknown      connected    
>>>>>> unconfigured
>>>>>> unknown
>>>>>> c17::5000d310004a064c,1        disk         connected    configured
>>>>>> unknown
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss


-- 
Majeed Abu-Qulbain
Lead Unix Admin - CISS
309-438-3455
Illinois State University


From agsousa at metalcon.pt  Fri Oct 19 06:42:20 2012
From: agsousa at metalcon.pt (Agostinho Sousa)
Date: Fri, 19 Oct 2012 11:42:20 +0100
Subject: [OmniOS-discuss] hostid missing or corrupt on /etc/hostid
Message-ID: <50812E8C.1010703@metalcon.pt>

Hi everyone,

On boot I see the message above. if I cat /etc/hostid: # DO NOT EDIT

Do I must concern about?
Thanks
-- 
assinatura

/Melhores cumprimentos | Un saludo | Best regards | Cordiali saluti |?? 
???????? | Met vriendelijke groeten | Salutations/

*Agostinho Sousa *
Direc??o de Sistemas de Informa??o | IT Department
agsousa at metalcon.pt | M. +351 968 492 741

Irm?os Silvas, S.A.
Maganha - Santiago de Bougado - Apartado 206
4786-909 - TROFA
Tel: +351 252 400 520 | Fax: +351 252 400 521
metalcon at metalcon.pt | www.metalcon.pt

*GRUPO METALCON *
Metalcon Investimentos | Brasmar | Galvaza | Grupomar | LSM | 
Metalogalva | Silvafer

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121019/aa4a1335/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: METALCONSGPS.PNG
Type: image/png
Size: 5474 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121019/aa4a1335/attachment-0001.png>

From geoffn at gnaa.net  Sun Oct 21 00:46:38 2012
From: geoffn at gnaa.net (Geoff Nordli)
Date: Sat, 20 Oct 2012 21:46:38 -0700
Subject: [OmniOS-discuss] disk IO performance in a Linux KVM guest
Message-ID: <CAEAo28GQBYHBuBXx=0FXLe8zJHMyFo_-8e4QviMYn6VjmRAXVA@mail.gmail.com>

Since I can't find a decent distributed file system which runs directly on
illumos, I am thinking about putting it inside a linux KVM guest.

>From what I can see glusterFS seems like the best choice.

Any thoughts on this approach?

thanks,

Geoff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121020/d05ec2ae/attachment.html>

From agsousa at metalcon.pt  Tue Oct 23 18:06:46 2012
From: agsousa at metalcon.pt (Agostinho Sousa)
Date: Tue, 23 Oct 2012 23:06:46 +0100
Subject: [OmniOS-discuss] hostid missing or corrupt on /etc/hostid
In-Reply-To: <50812E8C.1010703@metalcon.pt>
References: <50812E8C.1010703@metalcon.pt>
Message-ID: <508714F6.8000903@metalcon.pt>

Hi,

No one?

assinatura

/Melhores cumprimentos | Un saludo | Best regards | Cordiali saluti |?? 
???????? | Met vriendelijke groeten | Salutations/

Em 19-10-2012 11:42, Agostinho Sousa escreveu:
> Hi everyone,
>
> On boot I see the message above. if I cat /etc/hostid: # DO NOT EDIT
>
> Do I must concern about?
> Thanks
> -- 
> assinatura
>
> /Melhores cumprimentos | Un saludo | Best regards | Cordiali saluti 
> |?? ???????? | Met vriendelijke groeten | Salutations/
>
> *Agostinho Sousa *
> Direc??o de Sistemas de Informa??o | IT Department
> agsousa at metalcon.pt | M. +351 968 492 741
>
> Irm?os Silvas, S.A.
> Maganha - Santiago de Bougado - Apartado 206
> 4786-909 - TROFA
> Tel: +351 252 400 520 | Fax: +351 252 400 521
> metalcon at metalcon.pt | www.metalcon.pt
>
> *GRUPO METALCON *
> Metalcon Investimentos | Brasmar | Galvaza | Grupomar | LSM | 
> Metalogalva | Silvafer
>
>
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121023/8d46093b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 5474 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121023/8d46093b/attachment.png>

From jesus at omniti.com  Tue Oct 23 18:13:57 2012
From: jesus at omniti.com (Theo Schlossnagle)
Date: Tue, 23 Oct 2012 18:13:57 -0400
Subject: [OmniOS-discuss] hostid missing or corrupt on /etc/hostid
In-Reply-To: <50812E8C.1010703@metalcon.pt>
References: <50812E8C.1010703@metalcon.pt>
Message-ID: <CACLsAptjJgVzyjinctD53CQ+Hcv1-tNgpx5b+zs6j_0VhT3OQw@mail.gmail.com>

You should have more than that in there.  Mine looks like:

; cat hostid
# DO NOT EDIT
"_I__gfhhe6"


2012/10/19 Agostinho Sousa <agsousa at metalcon.pt>

>  Hi everyone,
>
> On boot I see the message above. if I cat /etc/hostid: # DO NOT EDIT
>
> Do I must concern about?
> Thanks
> --
>
> *Melhores cumprimentos | Un saludo | Best regards | Cordiali saluti |??
> ???????? | Met vriendelijke groeten | Salutations*
>
> * Agostinho Sousa *
>  Direc??o de Sistemas de Informa??o | IT Department
> agsousa at metalcon.pt | M. +351 968 492 741
>
> Irm?os Silvas, S.A.
> Maganha - Santiago de Bougado - Apartado 206
> 4786-909 - TROFA
> Tel: +351 252 400 520 | Fax: +351 252 400 521
> metalcon at metalcon.pt | www.metalcon.pt
>
> *GRUPO METALCON *
> Metalcon Investimentos | Brasmar | Galvaza | Grupomar | LSM | Metalogalva
> | Silvafer
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>


-- 

Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121023/207b7d80/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: METALCONSGPS.PNG
Type: image/png
Size: 5474 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121023/207b7d80/attachment.png>

From jesus at omniti.com  Tue Oct 23 18:18:18 2012
From: jesus at omniti.com (Theo Schlossnagle)
Date: Tue, 23 Oct 2012 18:18:18 -0400
Subject: [OmniOS-discuss] hostid missing or corrupt on /etc/hostid
In-Reply-To: <508714F6.8000903@metalcon.pt>
References: <50812E8C.1010703@metalcon.pt>
	<508714F6.8000903@metalcon.pt>
Message-ID: <CACLsApsWvZ9EjtCY9Q1H6wm0hFGVZUoj9A-KtYP2O+6=UXrAkw@mail.gmail.com>

You can try deleting /etc/hostid and running /lib/svc/method/svc-hostid as
root.  It _should_ create you a hostid.  Then again, it should have done
that in the first place.  I've never seen that fail.

2012/10/23 Agostinho Sousa <agsousa at metalcon.pt>

>  Hi,
>
> No one?
>
>  *Melhores cumprimentos | Un saludo | Best regards | Cordiali saluti |??
> ???????? | Met vriendelijke groeten | Salutations*
> Em 19-10-2012 11:42, Agostinho Sousa escreveu:
>
> Hi everyone,
>
> On boot I see the message above. if I cat /etc/hostid: # DO NOT EDIT
>
> Do I must concern about?
> Thanks
> --
>
> *Melhores cumprimentos | Un saludo | Best regards | Cordiali saluti |??
> ???????? | Met vriendelijke groeten | Salutations*
>
> * Agostinho Sousa *
>  Direc??o de Sistemas de Informa??o | IT Department
> agsousa at metalcon.pt | M. +351 968 492 741
>
> Irm?os Silvas, S.A.
> Maganha - Santiago de Bougado - Apartado 206
> 4786-909 - TROFA
> Tel: +351 252 400 520 | Fax: +351 252 400 521
> metalcon at metalcon.pt | www.metalcon.pt
>
> *GRUPO METALCON *
> Metalcon Investimentos | Brasmar | Galvaza | Grupomar | LSM | Metalogalva
> | Silvafer
>
>
> _______________________________________________
> OmniOS-discuss mailing listOmniOS-discuss at lists.omniti.comhttp://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>


-- 

Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121023/e688e359/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 5474 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121023/e688e359/attachment-0001.png>

From agsousa at metalcon.pt  Tue Oct 23 18:16:16 2012
From: agsousa at metalcon.pt (Agostinho Sousa)
Date: Tue, 23 Oct 2012 23:16:16 +0100
Subject: [OmniOS-discuss] hostid missing or corrupt on /etc/hostid
In-Reply-To: <508714F6.8000903@metalcon.pt>
References: <50812E8C.1010703@metalcon.pt> <508714F6.8000903@metalcon.pt>
Message-ID: <50871730.7090605@metalcon.pt>

Thanks Theo for your quick anwser,
but I don't as you can see


assinatura

/Melhores cumprimentos | Un saludo | Best regards | Cordiali saluti |?? 
???????? | Met vriendelijke groeten | Salutations/

*Agostinho Sousa *
Direc??o de Sistemas de Informa??o | IT Department
agsousa at metalcon.pt | M. +351 968 492 741

Irm?os Silvas, S.A.
Maganha - Santiago de Bougado - Apartado 206
4786-909 - TROFA
Tel: +351 252 400 520 | Fax: +351 252 400 521
metalcon at metalcon.pt | www.metalcon.pt

*GRUPO METALCON *
Metalcon Investimentos | Brasmar | Galvaza | Grupomar | LSM | 
Metalogalva | Silvafer

Em 23-10-2012 23:06, Agostinho Sousa escreveu:
> Hi,
>
> No one?
>
> assinatura
>
> /Melhores cumprimentos | Un saludo | Best regards | Cordiali saluti 
> |?? ???????? | Met vriendelijke groeten | Salutations/
>
> Em 19-10-2012 11:42, Agostinho Sousa escreveu:
>> Hi everyone,
>>
>> On boot I see the message above. if I cat /etc/hostid: # DO NOT EDIT
>>
>> Do I must concern about?
>> Thanks
>> -- 
>> assinatura
>>
>> /Melhores cumprimentos | Un saludo | Best regards | Cordiali saluti 
>> |?? ???????? | Met vriendelijke groeten | Salutations/
>>
>> *Agostinho Sousa *
>> Direc??o de Sistemas de Informa??o | IT Department
>> agsousa at metalcon.pt | M. +351 968 492 741
>>
>> Irm?os Silvas, S.A.
>> Maganha - Santiago de Bougado - Apartado 206
>> 4786-909 - TROFA
>> Tel: +351 252 400 520 | Fax: +351 252 400 521
>> metalcon at metalcon.pt | www.metalcon.pt
>>
>> *GRUPO METALCON *
>> Metalcon Investimentos | Brasmar | Galvaza | Grupomar | LSM | 
>> Metalogalva | Silvafer
>>
>>
>>
>> _______________________________________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121023/fa2601d8/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hidhifdj.png
Type: image/png
Size: 2703 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121023/fa2601d8/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: METALCONSGPS.PNG
Type: image/png
Size: 5474 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121023/fa2601d8/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 5474 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121023/fa2601d8/attachment-0005.png>

From agsousa at metalcon.pt  Tue Oct 23 18:51:08 2012
From: agsousa at metalcon.pt (Agostinho Sousa)
Date: Tue, 23 Oct 2012 23:51:08 +0100
Subject: [OmniOS-discuss] Some questions about omnios
Message-ID: <50871F5C.5070701@metalcon.pt>

Hi,

First, thanks for the great system.
I hope you continue your dedication to it.

I'm in the middle of decision to put omnios on my servers as 
virtualization base (omnios+iscsi san + kvm).
I intent to use  omnios virtual machines as fileserver, mail server and 
webserver.

The omnios discuss list is very young and to small. But Theo was very 
fast in help us to resolve our problems.
Must I feel confidente on put omnios on production?

BTW
I note that when I copy files using scp between servers with omnios I 
obtain 30Mbs, Between  Linux I obtain 131Mbs
But after I share a zfs with smb I obtain transfers close 110Mbs. Is scp 
protocol fault?


From agsousa at metalcon.pt  Tue Oct 23 19:00:26 2012
From: agsousa at metalcon.pt (Agostinho Sousa)
Date: Wed, 24 Oct 2012 00:00:26 +0100
Subject: [OmniOS-discuss] hostid missing or corrupt on /etc/hostid
In-Reply-To: <CACLsApsWvZ9EjtCY9Q1H6wm0hFGVZUoj9A-KtYP2O+6=UXrAkw@mail.gmail.com>
References: <50812E8C.1010703@metalcon.pt> <508714F6.8000903@metalcon.pt>
	<CACLsApsWvZ9EjtCY9Q1H6wm0hFGVZUoj9A-KtYP2O+6=UXrAkw@mail.gmail.com>
Message-ID: <5087218A.9020204@metalcon.pt>

Hi,

I run /lib/svc/method/svc-hostid on 2 equal servers  and I obtains the 
same hostid
"_I________"

Is that OK?

assinatura

/Melhores cumprimentos | Un saludo | Best regards | Cordiali saluti |?? 
???????? | Met vriendelijke groeten | Salutations/

*Agostinho Sousa *
Direc??o de Sistemas de Informa??o | IT Department
agsousa at metalcon.pt | M. +351 968 492 741

Irm?os Silvas, S.A.
Maganha - Santiago de Bougado - Apartado 206
4786-909 - TROFA
Tel: +351 252 400 520 | Fax: +351 252 400 521
metalcon at metalcon.pt | www.metalcon.pt

*GRUPO METALCON *
Metalcon Investimentos | Brasmar | Galvaza | Grupomar | LSM | 
Metalogalva | Silvafer

Em 23-10-2012 23:18, Theo Schlossnagle escreveu:
> You can try deleting /etc/hostid and 
> running /lib/svc/method/svc-hostid as root.  It _should_ create you a 
> hostid.  Then again, it should have done that in the first place. 
>  I've never seen that fail.
>
> 2012/10/23 Agostinho Sousa <agsousa at metalcon.pt 
> <mailto:agsousa at metalcon.pt>>
>
>     Hi,
>
>     No one?
>
>     /Melhores cumprimentos | Un saludo | Best regards | Cordiali
>     saluti |?? ???????? | Met vriendelijke groeten | Salutations/
>
>     Em 19-10-2012 11:42, Agostinho Sousa escreveu:
>>     Hi everyone,
>>
>>     On boot I see the message above. if I cat /etc/hostid: # DO NOT EDIT
>>
>>     Do I must concern about?
>>     Thanks
>>     -- 
>>
>>     /Melhores cumprimentos | Un saludo | Best regards | Cordiali
>>     saluti |?? ???????? | Met vriendelijke groeten | Salutations/
>>
>>     *Agostinho Sousa *
>>     Direc??o de Sistemas de Informa??o | IT Department
>>     agsousa at metalcon.pt <mailto:agsousa at metalcon.pt> | M. +351 968
>>     492 741 <tel:%2B351%20968%20492%20741>
>>
>>     Irm?os Silvas, S.A.
>>     Maganha - Santiago de Bougado - Apartado 206
>>     4786-909 - TROFA
>>     Tel: +351 252 400 520 <tel:%2B351%20252%20400%20520> | Fax: +351
>>     252 400 521 <tel:%2B351%20252%20400%20521>
>>     metalcon at metalcon.pt <mailto:metalcon at metalcon.pt> |
>>     www.metalcon.pt <http://www.metalcon.pt>
>>
>>     *GRUPO METALCON *
>>     Metalcon Investimentos | Brasmar | Galvaza | Grupomar | LSM |
>>     Metalogalva | Silvafer
>>
>>
>>
>>     _______________________________________________
>>     OmniOS-discuss mailing list
>>     OmniOS-discuss at lists.omniti.com  <mailto:OmniOS-discuss at lists.omniti.com>
>>     http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>
>     _______________________________________________
>     OmniOS-discuss mailing list
>     OmniOS-discuss at lists.omniti.com
>     <mailto:OmniOS-discuss at lists.omniti.com>
>     http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>
>
>
> -- 
>
> Theo Schlossnagle
>
> http://omniti.com/is/theo-schlossnagle
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121024/c0721850/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: METALCONSGPS.PNG
Type: image/png
Size: 5474 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121024/c0721850/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 5474 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20121024/c0721850/attachment-0003.png>

From esproul at omniti.com  Mon Oct 29 13:44:32 2012
From: esproul at omniti.com (Eric Sproul)
Date: Mon, 29 Oct 2012 13:44:32 -0400
Subject: [OmniOS-discuss] New stable release: r151004
Message-ID: <CA+QY2RSw+7ja9PfB-pE=VmF=BRLcXcVXMVP3RhKCdWvdWRhLbA@mail.gmail.com>

Greetings from the leading edge of Hurricane Sandy!  Amidst the "Sturm
und Drang", we are announcing the availability of the next OmniOS
stable release, r151004.

Please see the release notes for what's new in this release:
http://omnios.omniti.com/wiki.php/ReleaseNotes#r151004

Installation media:
 * http://omnios.omniti.com/media/OmniOS_Text_r151004.iso
 * http://omnios.omniti.com/media/r151004.zfs.bz2

See you on the other side of the storm.
Eric

From kent at watsen.net  Tue Oct 30 08:54:49 2012
From: kent at watsen.net (Kent Watsen)
Date: Tue, 30 Oct 2012 08:54:49 -0400
Subject: [OmniOS-discuss] New stable release: r151004
In-Reply-To: <CA+QY2RSw+7ja9PfB-pE=VmF=BRLcXcVXMVP3RhKCdWvdWRhLbA@mail.gmail.com>
References: <CA+QY2RSw+7ja9PfB-pE=VmF=BRLcXcVXMVP3RhKCdWvdWRhLbA@mail.gmail.com>
Message-ID: <508FCE19.8050501@watsen.net>


Thanks Devs!

This is the release I've been waiting for  :)

Thanks again,
Kent


On 10/29/12 1:44 PM, Eric Sproul wrote:
> Greetings from the leading edge of Hurricane Sandy!  Amidst the "Sturm
> und Drang", we are announcing the availability of the next OmniOS
> stable release, r151004.
>
> Please see the release notes for what's new in this release:
> http://omnios.omniti.com/wiki.php/ReleaseNotes#r151004
>
> Installation media:
>   * http://omnios.omniti.com/media/OmniOS_Text_r151004.iso
>   * http://omnios.omniti.com/media/r151004.zfs.bz2
>
> See you on the other side of the storm.
> Eric
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss


From henson at acm.org  Wed Oct 31 19:18:45 2012
From: henson at acm.org (Paul B. Henson)
Date: Wed, 31 Oct 2012 16:18:45 -0700
Subject: [OmniOS-discuss] kvm / zones
Message-ID: <5091B1D5.9050602@acm.org>

Under SmartOS, every kvm instance is created in a dedicated zone. With 
OI/OmniOS, is that also considered a best practice, or are people for 
the most part just running qemu in the global zone?

A separate zone provides a little more isolation and separation of the 
vm from anything else, and an extra buffer in case of any qemu security 
issues that allow a vm to inappropriately interact with the host. As I 
understand it, there are also some resource restrictions that can only 
be applied to zones, which one could not avail of with a vm in the 
global zone.

On the other hand, the joyent branded zone in SmartOS is a sparse zone 
(with basically the read-only OS image lofi mounted from the global 
zone), which is pretty low overhead. Sparse zones under OI/OmniOS aren't 
currently supported (I'm not sure if there's any work underway to change 
that?) so it would be a higher cost to create them for your vm's.

On another note, vmadm seems fairly powerful and useful for managing kvm 
instances, more so than trying to do everything by hand. It is a bit 
SmartOS centric though, I don't know if it would be useful to try to 
port to other illumos-based distributions. libvirt seems fairly popular 
to manage kvm under Linux, has anyone tried to get that working under 
illumos?

Thanks...

From bdha at mirrorshades.net  Wed Oct 31 19:44:03 2012
From: bdha at mirrorshades.net (Bryan Horstmann-Allen)
Date: Wed, 31 Oct 2012 19:44:03 -0400
Subject: [OmniOS-discuss] kvm / zones
In-Reply-To: <5091B1D5.9050602@acm.org>
References: <5091B1D5.9050602@acm.org>
Message-ID: <20121031234403.GA18753@lab.pobox.com>


+------------------------------------------------------------------------------
| On 2012-10-31 16:18:45, Paul B. Henson wrote:
| 
> Under SmartOS, every kvm instance is created in a dedicated zone. With 
> OI/OmniOS, is that also considered a best practice, or are people for the 
> most part just running qemu in the global zone?

I've been working on this in my spare time. It's mostly slog work, but a bit of
refactoring is going into how Joyent's kvm brand works. There's a bit of
SDC/SmartOS specific stuff in there.

I'll see if I can't make further progresss this weekend and get it up on
GitHub.

Porting vmadm/imgadm is likely a much bigger project, but I do think it would
be pretty darn handy (if only to use to automate against with Chef/etc.)

Cheers.
-- 
bdha
cyberpunk is dead. long live cyberpunk.

From henson at acm.org  Wed Oct 31 19:53:28 2012
From: henson at acm.org (Paul B. Henson)
Date: Wed, 31 Oct 2012 16:53:28 -0700
Subject: [OmniOS-discuss] kvm / zones
In-Reply-To: <20121031234403.GA18753@lab.pobox.com>
References: <5091B1D5.9050602@acm.org> <20121031234403.GA18753@lab.pobox.com>
Message-ID: <5091B9F8.9070704@acm.org>

On 10/31/2012 4:44 PM, Bryan Horstmann-Allen wrote:
>> Under SmartOS, every kvm instance is created in a dedicated zone. With
>> OI/OmniOS, is that also considered a best practice, or are people for the
>> most part just running qemu in the global zone?
>
> I've been working on this in my spare time. It's mostly slog work, but a bit of
> refactoring is going into how Joyent's kvm brand works. There's a bit of
> SDC/SmartOS specific stuff in there.
>
> I'll see if I can't make further progresss this weekend and get it up on
> GitHub.

Cool :), although I must confess I'm not completely clear on what you're 
working on. Implementing the joyent zone brand under omnios? Or 
something else related to running kvm in zones?

> Porting vmadm/imgadm is likely a much bigger project, but I do think it would
> be pretty darn handy (if only to use to automate against with Chef/etc.)

I'm not horribly familiar with either vmadm or libvirt, and perhaps this 
would be a better question for the SmartOS mailing list, but given they 
are both intended to ease/automate management of virtual machines, I 
wonder how they compare feature-wise... I assume libvirt doesn't know 
much about zones/vnics etc out-of-the-box.

From bdha at mirrorshades.net  Wed Oct 31 20:46:50 2012
From: bdha at mirrorshades.net (Bryan Horstmann-Allen)
Date: Wed, 31 Oct 2012 20:46:50 -0400
Subject: [OmniOS-discuss] kvm / zones
In-Reply-To: <5091B9F8.9070704@acm.org>
References: <5091B1D5.9050602@acm.org> <20121031234403.GA18753@lab.pobox.com>
	<5091B9F8.9070704@acm.org>
Message-ID: <20121101004649.GB18753@lab.pobox.com>

+------------------------------------------------------------------------------
| On 2012-10-31 16:53:28, Paul B. Henson wrote:
| 
> Cool :), although I must confess I'm not completely clear on what you're 
> working on. Implementing the joyent zone brand under omnios? Or something 
> else related to running kvm in zones?

It's actually not the joyent brand, but the kvm brand. The joyent brand is a
modified standard "sparse" zones brand, which is (I think) very unlikely to
work within the context of IPS (at least within the zones themselves!)

The kvm brand does some work with networking, but not too much. It just
requires a bit of thought in how you handle getting passed VNICs vs not, and so
forth. I just haven't had much time to look at it since an initial run at
Surge.

> I'm not horribly familiar with either vmadm or libvirt, and perhaps this 
> would be a better question for the SmartOS mailing list, but given they are 
> both intended to ease/automate management of virtual machines, I wonder how 
> they compare feature-wise... I assume libvirt doesn't know much about 
> zones/vnics etc out-of-the-box.

I think vmadm/imgadm are definitely the way to go, especially once OmniOS has
its own version of the kvm brand. Unless Eric decides that shipping node in
base is something he really wants to do, they'll likely have to be installed as
packages, though. :-)

Cheers.
-- 
bdha
cyberpunk is dead. long live cyberpunk.

From jesus at omniti.com  Wed Oct 31 20:56:11 2012
From: jesus at omniti.com (Theo Schlossnagle)
Date: Wed, 31 Oct 2012 20:56:11 -0400
Subject: [OmniOS-discuss] kvm / zones
In-Reply-To: <20121101004649.GB18753@lab.pobox.com>
References: <5091B1D5.9050602@acm.org> <20121031234403.GA18753@lab.pobox.com>
	<5091B9F8.9070704@acm.org> <20121101004649.GB18753@lab.pobox.com>
Message-ID: <CACLsAptnatq3ZCuNSMc8UoBc_Px8HdRsTm94MDhuzvM+8p6CuA@mail.gmail.com>

node is actually quite small and I'm hopeful that the product wil
stabilize soon.  I've no objections to including node in the base
install if there is a very valuable tool that requires it.

On Wed, Oct 31, 2012 at 8:46 PM, Bryan Horstmann-Allen
<bdha at mirrorshades.net> wrote:
> +------------------------------------------------------------------------------
> | On 2012-10-31 16:53:28, Paul B. Henson wrote:
> |
>> Cool :), although I must confess I'm not completely clear on what you're
>> working on. Implementing the joyent zone brand under omnios? Or something
>> else related to running kvm in zones?
>
> It's actually not the joyent brand, but the kvm brand. The joyent brand is a
> modified standard "sparse" zones brand, which is (I think) very unlikely to
> work within the context of IPS (at least within the zones themselves!)
>
> The kvm brand does some work with networking, but not too much. It just
> requires a bit of thought in how you handle getting passed VNICs vs not, and so
> forth. I just haven't had much time to look at it since an initial run at
> Surge.
>
>> I'm not horribly familiar with either vmadm or libvirt, and perhaps this
>> would be a better question for the SmartOS mailing list, but given they are
>> both intended to ease/automate management of virtual machines, I wonder how
>> they compare feature-wise... I assume libvirt doesn't know much about
>> zones/vnics etc out-of-the-box.
>
> I think vmadm/imgadm are definitely the way to go, especially once OmniOS has
> its own version of the kvm brand. Unless Eric decides that shipping node in
> base is something he really wants to do, they'll likely have to be installed as
> packages, though. :-)
>
> Cheers.
> --
> bdha
> cyberpunk is dead. long live cyberpunk.
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss



-- 
Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle

From bdha at mirrorshades.net  Wed Oct 31 21:34:46 2012
From: bdha at mirrorshades.net (Bryan Horstmann-Allen)
Date: Wed, 31 Oct 2012 21:34:46 -0400
Subject: [OmniOS-discuss] kvm / zones
In-Reply-To: <CACLsAptnatq3ZCuNSMc8UoBc_Px8HdRsTm94MDhuzvM+8p6CuA@mail.gmail.com>
References: <5091B1D5.9050602@acm.org> <20121031234403.GA18753@lab.pobox.com>
	<5091B9F8.9070704@acm.org> <20121101004649.GB18753@lab.pobox.com>
	<CACLsAptnatq3ZCuNSMc8UoBc_Px8HdRsTm94MDhuzvM+8p6CuA@mail.gmail.com>
Message-ID: <20121101013446.GC18753@lab.pobox.com>

+------------------------------------------------------------------------------
| On 2012-10-31 20:56:11, Theo Schlossnagle wrote:
| 
| node is actually quite small and I'm hopeful that the product wil
| stabilize soon.  I've no objections to including node in the base
| install if there is a very valuable tool that requires it.

Well, vmadm/imgadm would certainly be that!
-- 
bdha
cyberpunk is dead. long live cyberpunk.

