From jstockett at molalla.com  Tue Apr  3 17:00:14 2018
From: jstockett at molalla.com (Jeff Stockett)
Date: Tue, 3 Apr 2018 17:00:14 +0000
Subject: [OmniOS-discuss] vmware tools -> open-vm-tools gotcha
Message-ID: <60168ff0db994d47a3f4ec300da01418@molalla.com>

I have an omnios vm that I had installed vmware tools on back before open-vm-tools was in the repo (or I knew it was).  I was going to update it to use open-vm-tools because I hate getting nagged when we apply updates to our vmware cluster so sometime back, I ran "vmware-uninstall-tools.pl" and then "pkg install open-vm-tools" and all appeared to be well.  However, this morning I rebooted that machine, and when it came back up it had no network - dladm show-link returned nothing despite two nics being configured in vmware.  I'm assuming "vmware-uninstall-tools.pl" got a little over zealous and removed the vmxnet3 driver even though it was provided as part of omnios.  Anyone know an easy way to manually uninstall vmware tools without this nasty side effect?  Thank goodness for boot environments or I would have been struggling to remember how to mount the cdrom so I could re-install vmware tools while under pressure!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20180403/766265c2/attachment.html>

From al.slater at scluk.com  Mon Apr  9 07:49:30 2018
From: al.slater at scluk.com (Al Slater)
Date: Mon, 9 Apr 2018 08:49:30 +0100
Subject: [OmniOS-discuss] xnf panic
Message-ID: <790fc159-e61a-975d-93ea-f7d9488f7615@scluk.com>

Hi,

Has the fix for 7186 (xnf: panic on Xen 4.x) been integrated into
r151022 since the initial CE release?

I have an instance in AWS that they required me to stop and start again
due to host patching.  When I started it again the instance went into a
panic/reboot loop.  The stack dump looked similar to the one in the
error report.

I managed to get the instance started by changing the instance type from
m4.large to t2.large.  Presumably AWS are migrating towards Xen versions
> 4 in london region.  I don't know how long until the t2 hosts are updated.

regards

-- 
Al Slater


From al.slater at scluk.com  Mon Apr  9 08:26:35 2018
From: al.slater at scluk.com (Al Slater)
Date: Mon, 9 Apr 2018 09:26:35 +0100
Subject: [OmniOS-discuss] xnf panic
In-Reply-To: <790fc159-e61a-975d-93ea-f7d9488f7615@scluk.com>
References: <790fc159-e61a-975d-93ea-f7d9488f7615@scluk.com>
Message-ID: <151b0433-eae1-0ab5-aa01-506af4bf3756@scluk.com>

On 09/04/2018 08:49, Al Slater wrote:
> Has the fix for 7186 (xnf: panic on Xen 4.x) been integrated into
> r151022 since the initial CE release?
> 
> I have an instance in AWS that they required me to stop and start again
> due to host patching.  When I started it again the instance went into a
> panic/reboot loop.  The stack dump looked similar to the one in the
> error report.
> 
> I managed to get the instance started by changing the instance type from
> m4.large to t2.large.  Presumably AWS are migrating towards Xen versions
>> 4 in london region.  I don't know how long until the t2 hosts are updated.

Repeatable on any m4 instance type I tried.

Technical Director
SCL

Phone : +44 (0)1273 666607
Fax   : +44 (0)1273 666601
email : al.slater at scluk.com

Stanton Consultancy Ltd

Park Gate, 161 Preston Road, Brighton, East Sussex, BN1 6AU

Registered in England Company number: 1957652 VAT number: GB 760 2433 55
panic[cpu0]/thread=ffffff000f4e6c40: BAD TRAP: type=e (#pf Page fault)
rp=ffffff000f4e69b0 addr=40 occurred in module "xnf" due to a NULL
pointer dereference

sched: #pf Page fault

Bad kernel fault at addr=0x40

pid=0, pc=0xfffffffff79b6e67, sp=0xffffff000f4e6aa0, eflags=0x10206

cr0: 8005003b<pg,wp,ne,et,ts,mp,pe> cr4:
1406b8<smep,osxsav,xmme,fxsr,pge,pae,pse,de>


cr2: 40cr3: c400000cr8: c
????????rdi:??????????????286 rsi:????????????????6 rdx:????????????????c
????????rcx: ffffff03d5dbf064??r8:????????????????0??r9:????????????????0
????????rax:??????????????150 rbx:????????????????3 rbp: ffffff000f4e6af0
????????r10:????????????????0 r11: fffffffffb800983 r12: ffffff03d5d90000
????????r13:????????????????0 r14:?????????????? 15 r15:????????????????9
????????fsb:????????????????0 gsb: fffffffffbc397e0??ds:?????????????? 4b
???????? es:?????????????? 4b??fs:????????????????0??gs:??????????????1c3
????????trp:????????????????e err:????????????????0 rip: fffffffff79b6e67
???????? cs:?????????????? 30 rfl:????????????10206 rsp: ffffff000f4e6aa0
???????? ss:?????????????? 38

Warning - stack not written to the dump buffer
ffffff000f4e6890 unix:die+df ()
ffffff000f4e69a0 unix:trap+e18 ()
ffffff000f4e69b0 unix:cmntrap+e6 ()
ffffff000f4e6af0 xnf:xnf_tx_clean_ring+c7 ()
ffffff000f4e6b60 xnf:tx_slots_get+95 ()
ffffff000f4e6ba0 xnf:xnf_intr+15b ()
ffffff000f4e6bf0 unix:av_dispatch_softvect+78 ()
ffffff000f4e6c20 unix:dispatch_softint+39 ()
ffffff000f635460 unix:switch_sp_and_call+13 ()
ffffff000f6354a0 unix:dosoftint+44 ()
ffffff000f635500 unix:do_interrupt+ba ()
ffffff000f635510 unix:cmnint+ba ()
fffffffff7c6aec0 sha2:SHA256TransformBlocks+109f ()


-- 
Al Slater


From omnios at citrus-it.net  Mon Apr  9 13:55:32 2018
From: omnios at citrus-it.net (Andy Fiddaman)
Date: Mon, 9 Apr 2018 13:55:32 +0000 (UTC)
Subject: [OmniOS-discuss] xnf panic
In-Reply-To: <790fc159-e61a-975d-93ea-f7d9488f7615@scluk.com>
References: <790fc159-e61a-975d-93ea-f7d9488f7615@scluk.com>
Message-ID: <nycvar.TFB.7.76.1804091354420.21704@erncre.pvgehf-vg.arg>


On Mon, 9 Apr 2018, Al Slater wrote:

; Hi,
;
; Has the fix for 7186 (xnf: panic on Xen 4.x) been integrated into
; r151022 since the initial CE release?

Hi Al,

No, that one was not selected for back-porting. I'll get it added to the list
for the next weekly release.

Regards,

Andy

-- 
Citrus IT Limited | +44 (0)333 0124 007 | enquiries at citrus-it.co.uk
Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ
Registered in England and Wales | Company number 4899123


From omnios at citrus-it.net  Mon Apr  9 15:04:34 2018
From: omnios at citrus-it.net (Andy Fiddaman)
Date: Mon, 9 Apr 2018 15:04:34 +0000 (UTC)
Subject: [OmniOS-discuss] xnf panic
In-Reply-To: <790fc159-e61a-975d-93ea-f7d9488f7615@scluk.com>
References: <790fc159-e61a-975d-93ea-f7d9488f7615@scluk.com>
Message-ID: <nycvar.TFB.7.76.1804091458300.13909@erncre.pvgehf-vg.arg>


Al,

I've prepared a hot-fix containing this driver update if you'd like to
test. I tried to test it myself on AWS but can't provision any type of
machine from that unofficial CE r151022 AMI in London. Just snapshot the
EBS volume first in case of problems.

To install:

  pkg apply-hot-fix https://downloads.omniosce.org/pkg/r151022/7186-xnf.p5p

which will create a new boot-environment, and reboot.

Assuming it looks ok, this update will be part of next Monday's release.

Regards,

Andy

On Mon, 9 Apr 2018, Al Slater wrote:

; Hi,
;
; Has the fix for 7186 (xnf: panic on Xen 4.x) been integrated into
; r151022 since the initial CE release?
;
; I have an instance in AWS that they required me to stop and start again
; due to host patching.  When I started it again the instance went into a
; panic/reboot loop.  The stack dump looked similar to the one in the
; error report.
;
; I managed to get the instance started by changing the instance type from
; m4.large to t2.large.  Presumably AWS are migrating towards Xen versions
; > 4 in london region.  I don't know how long until the t2 hosts are updated.
;
; regards
;
;
-- 
Citrus IT Limited | +44 (0)333 0124 007 | enquiries at citrus-it.co.uk
Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ
Registered in England and Wales | Company number 4899123


From al.slater at scluk.com  Mon Apr  9 17:05:37 2018
From: al.slater at scluk.com (Al Slater)
Date: Mon, 9 Apr 2018 18:05:37 +0100
Subject: [OmniOS-discuss] xnf panic
In-Reply-To: <nycvar.TFB.7.76.1804091458300.13909@erncre.pvgehf-vg.arg>
References: <790fc159-e61a-975d-93ea-f7d9488f7615@scluk.com>
	<nycvar.TFB.7.76.1804091458300.13909@erncre.pvgehf-vg.arg>
Message-ID: <6d06ebd2-a8a2-3013-c139-c9791625faee@scluk.com>

Hi Andy,

Wow, that was fast.  I will test this when I have fed the family.

I have my own AMI, so I can spin a server as a T2 instance, apply the
fix and then restart after changing to an M4.

regards

Al

On 09/04/18 16:04, Andy Fiddaman wrote:
> 
> Al,
> 
> I've prepared a hot-fix containing this driver update if you'd like to
> test. I tried to test it myself on AWS but can't provision any type of
> machine from that unofficial CE r151022 AMI in London. Just snapshot the
> EBS volume first in case of problems.
> 
> To install:
> 
>   pkg apply-hot-fix https://downloads.omniosce.org/pkg/r151022/7186-xnf.p5p
> 
> which will create a new boot-environment, and reboot.
> 
> Assuming it looks ok, this update will be part of next Monday's release.
> 
> Regards,
> 
> Andy
> 
> On Mon, 9 Apr 2018, Al Slater wrote:
> 
> ; Hi,
> ;
> ; Has the fix for 7186 (xnf: panic on Xen 4.x) been integrated into
> ; r151022 since the initial CE release?
> ;
> ; I have an instance in AWS that they required me to stop and start again
> ; due to host patching.  When I started it again the instance went into a
> ; panic/reboot loop.  The stack dump looked similar to the one in the
> ; error report.
> ;
> ; I managed to get the instance started by changing the instance type from
> ; m4.large to t2.large.  Presumably AWS are migrating towards Xen versions
> ; > 4 in london region.  I don't know how long until the t2 hosts are updated.
> ;
> ; regards
> ;
> ;
> 


From al.slater at scluk.com  Mon Apr  9 20:16:53 2018
From: al.slater at scluk.com (Al Slater)
Date: Mon, 9 Apr 2018 21:16:53 +0100
Subject: [OmniOS-discuss] xnf panic
In-Reply-To: <6d06ebd2-a8a2-3013-c139-c9791625faee@scluk.com>
References: <790fc159-e61a-975d-93ea-f7d9488f7615@scluk.com>
	<nycvar.TFB.7.76.1804091458300.13909@erncre.pvgehf-vg.arg>
	<6d06ebd2-a8a2-3013-c139-c9791625faee@scluk.com>
Message-ID: <826d0931-5135-9a2d-95b0-0bed6ceea720@scluk.com>

Hi Andy,

OK, I booted a t2.micro instance from my AMI (Original OmniOS CE r151022
HVM).  Updated pkg and then updated to r151022as.

Then shut the instance down, changed the type to m4.large, then started
the instance.  A panic/reboot loop ensued.  Stopped the instance.

Changed the instance back to t2.micro and booted.  Applied the hotfix
and rebooted.  Rebooted fine.

Stopped the instance, changed instance type to m4.large, and started the
instance.  The instance started and I could log in just fine.

To be sure, I stopped and restarted the instance a few times. It always
came back up ok.

So, the patch looks good to me.  If you can think of any more tests you
would like me to run, I'll give them a go for you.

Thank you for the speedy fix.

regards

Al


On 09/04/18 18:05, Al Slater wrote:
> Hi Andy,
> 
> Wow, that was fast.  I will test this when I have fed the family.
> 
> I have my own AMI, so I can spin a server as a T2 instance, apply the
> fix and then restart after changing to an M4.
> 
> regards
> 
> Al
> 
> On 09/04/18 16:04, Andy Fiddaman wrote:
>>
>> Al,
>>
>> I've prepared a hot-fix containing this driver update if you'd like to
>> test. I tried to test it myself on AWS but can't provision any type of
>> machine from that unofficial CE r151022 AMI in London. Just snapshot the
>> EBS volume first in case of problems.
>>
>> To install:
>>
>>   pkg apply-hot-fix https://downloads.omniosce.org/pkg/r151022/7186-xnf.p5p
>>
>> which will create a new boot-environment, and reboot.
>>
>> Assuming it looks ok, this update will be part of next Monday's release.
>>
>> Regards,
>>
>> Andy
>>
>> On Mon, 9 Apr 2018, Al Slater wrote:
>>
>> ; Hi,
>> ;
>> ; Has the fix for 7186 (xnf: panic on Xen 4.x) been integrated into
>> ; r151022 since the initial CE release?
>> ;
>> ; I have an instance in AWS that they required me to stop and start again
>> ; due to host patching.  When I started it again the instance went into a
>> ; panic/reboot loop.  The stack dump looked similar to the one in the
>> ; error report.
>> ;
>> ; I managed to get the instance started by changing the instance type from
>> ; m4.large to t2.large.  Presumably AWS are migrating towards Xen versions
>> ; > 4 in london region.  I don't know how long until the t2 hosts are updated.
>> ;
>> ; regards
>> ;
>> ;
>>
> 
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
> 

From omnios at citrus-it.net  Thu Apr 12 11:07:36 2018
From: omnios at citrus-it.net (Andy Fiddaman)
Date: Thu, 12 Apr 2018 11:07:36 +0000 (UTC)
Subject: [OmniOS-discuss] xnf panic
In-Reply-To: <826d0931-5135-9a2d-95b0-0bed6ceea720@scluk.com>
References: <790fc159-e61a-975d-93ea-f7d9488f7615@scluk.com>
	<nycvar.TFB.7.76.1804091458300.13909@erncre.pvgehf-vg.arg>
	<6d06ebd2-a8a2-3013-c139-c9791625faee@scluk.com>
	<826d0931-5135-9a2d-95b0-0bed6ceea720@scluk.com>
Message-ID: <nycvar.TFB.7.76.1804121106020.4849@erncre.pvgehf-vg.arg>


Al, that's great thanks. The fix will be in Monday's update - the same as
the hotfix you already have.

Thanks for reporting this, it's likely to hit people as Amazon upgrade
their platform.

Regards,

Andy

On Mon, 9 Apr 2018, Al Slater wrote:

; Hi Andy,
;
; OK, I booted a t2.micro instance from my AMI (Original OmniOS CE r151022
; HVM).  Updated pkg and then updated to r151022as.
;
; Then shut the instance down, changed the type to m4.large, then started
; the instance.  A panic/reboot loop ensued.  Stopped the instance.
;
; Changed the instance back to t2.micro and booted.  Applied the hotfix
; and rebooted.  Rebooted fine.
;
; Stopped the instance, changed instance type to m4.large, and started the
; instance.  The instance started and I could log in just fine.
;
; To be sure, I stopped and restarted the instance a few times. It always
; came back up ok.
;
; So, the patch looks good to me.  If you can think of any more tests you
; would like me to run, I'll give them a go for you.
;
; Thank you for the speedy fix.
;
; regards
;
; Al
;
;
; On 09/04/18 18:05, Al Slater wrote:
; > Hi Andy,
; >
; > Wow, that was fast.  I will test this when I have fed the family.
; >
; > I have my own AMI, so I can spin a server as a T2 instance, apply the
; > fix and then restart after changing to an M4.
; >
; > regards
; >
; > Al
; >
; > On 09/04/18 16:04, Andy Fiddaman wrote:
; >>
; >> Al,
; >>
; >> I've prepared a hot-fix containing this driver update if you'd like to
; >> test. I tried to test it myself on AWS but can't provision any type of
; >> machine from that unofficial CE r151022 AMI in London. Just snapshot the
; >> EBS volume first in case of problems.
; >>
; >> To install:
; >>
; >>   pkg apply-hot-fix https://downloads.omniosce.org/pkg/r151022/7186-xnf.p5p
; >>
; >> which will create a new boot-environment, and reboot.
; >>
; >> Assuming it looks ok, this update will be part of next Monday's release.
; >>
; >> Regards,
; >>
; >> Andy
; >>
; >> On Mon, 9 Apr 2018, Al Slater wrote:
; >>
; >> ; Hi,
; >> ;
; >> ; Has the fix for 7186 (xnf: panic on Xen 4.x) been integrated into
; >> ; r151022 since the initial CE release?
; >> ;
; >> ; I have an instance in AWS that they required me to stop and start again
; >> ; due to host patching.  When I started it again the instance went into a
; >> ; panic/reboot loop.  The stack dump looked similar to the one in the
; >> ; error report.
; >> ;
; >> ; I managed to get the instance started by changing the instance type from
; >> ; m4.large to t2.large.  Presumably AWS are migrating towards Xen versions
; >> ; > 4 in london region.  I don't know how long until the t2 hosts are updated.
; >> ;
; >> ; regards
; >> ;
; >> ;
; >>
; >
; > _______________________________________________
; > 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
;
-- 
Citrus IT Limited | +44 (0)333 0124 007 | enquiries at citrus-it.co.uk
Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ
Registered in England and Wales | Company number 4899123


From oliver.weinmann at telespazio-vega.de  Wed Apr 25 06:00:33 2018
From: oliver.weinmann at telespazio-vega.de (Oliver Weinmann)
Date: Wed, 25 Apr 2018 06:00:33 +0000
Subject: [OmniOS-discuss] NFS Server in non-global zone possible?
Message-ID: <767138E0D064A148B03FE8EC1E9325A20138E032F8@GEDAEVW01.a.space.corp>

Hi all,

I have started using zones. I really like the concept, it is very similar to NetApps SVMs. Only problem so far is that I can't get a NFS server running inside a zone. Is this technically possible? I have googled a lot and I found many different statements. My zone is configured with the following privs:

set limitpriv=default,sys_smb,sys_nfs

root at omnios02-dmz:/ds4243/omnios02-dmz-volumes/veeam_dmz# svcs | grep -i nfs
disabled       12:20:58 svc:/network/nfs/server:default
online         12:20:58 svc:/network/nfs/status:default
online         12:20:58 svc:/network/nfs/nlockmgr:default
root at omnios02-dmz:/ds4243/omnios02-dmz-volumes/veeam_dmz# svcadm enable svc:/network/nfs/server:default
root at omnios02-dmz:/ds4243/omnios02-dmz-volumes/veeam_dmz# svcs -vx svc:/network/nfs/server:default
svc:/network/nfs/server:default (NFS server)
State: disabled since Wed Apr 25 05:57:12 2018
Reason: Temporarily disabled by an administrator.
   See: http://illumos.org/msg/SMF-8000-1S
   See: man -M /usr/share/man -s 1M nfsd
   See: /var/svc/log/network-nfs-server:default.log
Impact: This service is not running.
root at omnios02-dmz:/ds4243/omnios02-dmz-volumes/veeam_dmz# tail -f /var/svc/log/network-nfs-server:default.log
[ Apr 24 12:20:58 Stopping because service disabled. ]
[ Apr 24 12:20:58 Executing stop method ("/lib/svc/method/nfs-server stop 310"). ]
[ Apr 24 12:20:58 Method "stop" exited with status 0. ]
[ Apr 25 05:57:11 Enabled. ]
[ Apr 25 05:57:11 Executing start method ("/lib/svc/method/nfs-server start"). ]
The NFS server is not supported in a local zone
[ Apr 25 05:57:11 Method "start" exited with status 0. ]
[ Apr 25 05:57:11 Stopping because service disabled. ]
[ Apr 25 05:57:11 Executing stop method ("/lib/svc/method/nfs-server stop 319"). ]
[ Apr 25 05:57:12 Method "stop" exited with status 0. ]

Best Regards,
Oliver



[cid:Logo_Telespazio_180_px_signature_eng_b58fa623-e26d-4116-9230-766adacfe55e1111111111111.png]

Oliver Weinmann
Head of Corporate ICT

Telespazio VEGA Deutschland GmbH
Europaplatz 5 - 64293 Darmstadt - Germany
Ph: +49 (0)6151 8257 744 | Fax: +49 (0)6151 8257 799
oliver.weinmann at telespazio-vega.de<mailto:oliver.weinmann at telespazio-vega.de>
www.telespazio-vega.de

Registered office/Sitz: Darmstadt, Register court/Registergericht: Darmstadt, HRB 89231; Managing Director/Gesch?ftsf?hrer: Sigmar Keller


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20180425/4e9c0b37/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Logo_Telespazio_180_px_signature_eng_b58fa623-e26d-4116-9230-766adacfe55e1111111111111.png
Type: image/png
Size: 7535 bytes
Desc: Logo_Telespazio_180_px_signature_eng_b58fa623-e26d-4116-9230-766adacfe55e1111111111111.png
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20180425/4e9c0b37/attachment.png>

