Re: [OmniOS-discuss] LX: real ksh93 broken

[Nahum Shalman]

As a data point, I tested this on a very recent SmartOS and was unable to
reproduce:

root@ksh-debian:~# set -o xtrace ; /native/usr/bin/uname -a; uname -a ; cat
/etc/debian_version ; dpkg-query -l ksh | grep ksh ; /bin/ksh93
+ set -o xtrace
+ /native/usr/bin/uname -a
SunOS ksh-debian 5.11 joyent_20170427T222500Z i86pc i386 i86pc
+ uname -a
Linux ksh-debian 3.16.10 BrandZ virtual linux x86_64 GNU/Linux
+ cat /etc/debian_version
8.8
+ dpkg-query -l ksh
+ grep ksh
ii  ksh93u+20120801-1 amd64Real, AT version of the
Korn shell
+ /bin/ksh93
# ps | grep $$
77074 pts/200:00:00 ksh93
# exit
root@ksh-debian:~#

On Tue, May 9, 2017 at 5:52 AM, Ludovic Orban  wrote:

> Hi,
>
> I've installed the real ksh93 (this stuff: https://packages.debian.org/
> jessie/ksh) on a r151020 LX zone running the latest Debian (
> https://images.joyent.com/images/e74a9cd0-f2d0-11e6-8b69-b3acf2ef87f7)
> and it behaves strangely.
>
> Here is what I get:
>
> root@debian-8:~# /bin/ksh93
> # ls /
>
>
> ^C^C
> ^Z^Z^Z
> ^\^\^\^\
> Killed
> root@debian-8:~#
> root@debian-8:~#
>
> (note: the "Killed" line is due to a kill -9 from another terminal).
>
> Basically, any command I type just hangs there. Sometimes the shell reacts
> to ^C and/or ^D allowing me to try a different command that also gonna
> hang, and sometimes it doesn't and I have to kill the shell from another
> terminal. In the latter case, ksh93 starts kind of a "fork bomb" where it
> seems to fork itself in a loop.
>
> I can reproduce this problem from a zlogin term as well as from a direct
> ssh session. I've also tried ksh93 on a CentOS zone to make sure the
> problem wasn't caused by Debian's build and the exact same problem arises.
>
> Any idea what's going on?
>
> Thanks,
> Ludovic
>
> ___
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] qemu: too many IDE bus

[Nahum Shalman]

On my SmartOS box I have a one-line script I use for verifying that my USB
stick is still bootable after I update the platform image on it.
It contains:

qemu-system-x86_64 -m 4096 -smp 4 -hda /dev/dsk/c0t0d0p0 -serial stdio

So you should be able to do that with any raw hard drive you might want to
pass through to a virtual machine. (Though I would recommend doing it with
the fancier "-drive" syntax and passing it through with a non-ide
controller.)

-Nahum


On Wed, Mar 8, 2017 at 1:53 PM, Dirk Willems <dirk.will...@exitas.be> wrote:

> Hello Nahum,
>
>
> My apologize in the meantime I had found the solution with changing the
> IDE with the virtio, the ide is indeed limit to 4 devices but now it's
> running perfectly  thanks ;)
>
> But another question, do you have experience with adding raw devices in
> KVM ?
>
>
> Thanks in advance.
>
>
> Kind Regards,
>
>
> Dirk
>
> On 08-03-17 16:06, Nahum Shalman wrote:
>
> I would think that depending on how you're invoking QEMU (it looked like
> the full qemu command line was truncated from the output you pasted) it'
> allocating one of the 4 available IDE slots to a virtual CDROM. Depending
> on your guest OS you could consider using a different virtual controller
> for the virtual disks, or you might be able to tell qemu not to allocate a
> virtual cdrom drive.
>
> If you want to share the full qemu command line being invoked I'm happy to
> take a quick look at it to see if I can figure out a simple way to improve
> it.
>
> (I suspect that "cd /KVM_Machines/JDN && bash -x ./JDN01_Start-VM.sh" will
> provide the information needed)
>
> -Nahum
>
> On Fri, Mar 3, 2017 at 10:12 AM, Dirk Willems <dirk.will...@exitas.be>
> wrote:
>
>> Hello,
>>
>> I experience some issue's with too many IDE bus on KVM ?
>>
>> I'm only allowed to having 3 HDD, when I add the fourth HDD I get the
>> following error
>>
>> qemu: too many IDE bus
>>
>> root@OmniosExitas:/KVM_Machines/JDN# ./JDN01_Start-VM.sh
>> qemu-system-x86_64: -net vnic,vlan=0,name=net0,ifname=V
>> LJDN01,macaddr=2:8:20:2:4b:a4,: vnic dhcp disabled
>>
>> qemu-system-x86_64: -net vnic,vlan=1,name=net1,ifname=V
>> SJDN01,macaddr=2:8:20:67:1:7c,: vnic dhcp disabled
>>
>> qemu: too many IDE bus
>> Failed to start VM
>> Started VM:
>> Public: 127.0.0.1
>> 10.100.23.86
>> ::1/128
>> ::/0:5903
>>
>>
>> I just upgrade to
>>
>> root@OmniosExitas:/KVM_Machines/JDN# uname -a
>> SunOS OmniosExitas 5.11 omnios-r151020-4151d05 i86pc i386 i86pc
>>
>> Any suggestions ?
>>
>>
>> Thanks in advance.
>>
>>
>> Kind Regards.
>>
>>
>> Dirk
>>
>>
>>
>> --
>> Dirk Willems
>> System Engineer
>>
>>
>> +32 (0)3 443 12 38 <+32%203%20443%2012%2038>
>> dirk.will...@exitas.be
>>
>> Quality. Passion. Personality
>>
>> www.exitas.be | Veldkant 31 | 2550 Kontich
>>
>> Illumos OmniOS Installation and Configuration Implementation Specialist.
>> Oracle Solaris 11 Installation and Configuration Certified Implementation
>> Specialist.
>>
>> ___
>> OmniOS-discuss mailing list
>> OmniOS-discuss@lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>>
>>
>
> --
> Dirk Willems
> System Engineer
>
>
> +32 (0)3 443 12 38 <+32%203%20443%2012%2038>
> dirk.will...@exitas.be
>
> Quality. Passion. Personality
>
> www.exitas.be | Veldkant 31 | 2550 Kontich
>
> Illumos OmniOS Installation and Configuration Implementation Specialist.
> Oracle Solaris 11 Installation and Configuration Certified Implementation
> Specialist.
>
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] qemu: too many IDE bus

[Nahum Shalman]

I would think that depending on how you're invoking QEMU (it looked like
the full qemu command line was truncated from the output you pasted) it'
allocating one of the 4 available IDE slots to a virtual CDROM. Depending
on your guest OS you could consider using a different virtual controller
for the virtual disks, or you might be able to tell qemu not to allocate a
virtual cdrom drive.

If you want to share the full qemu command line being invoked I'm happy to
take a quick look at it to see if I can figure out a simple way to improve
it.

(I suspect that "cd /KVM_Machines/JDN && bash -x ./JDN01_Start-VM.sh" will
provide the information needed)

-Nahum

On Fri, Mar 3, 2017 at 10:12 AM, Dirk Willems 
wrote:

> Hello,
>
> I experience some issue's with too many IDE bus on KVM ?
>
> I'm only allowed to having 3 HDD, when I add the fourth HDD I get the
> following error
>
> qemu: too many IDE bus
>
> root@OmniosExitas:/KVM_Machines/JDN# ./JDN01_Start-VM.sh
> qemu-system-x86_64: -net vnic,vlan=0,name=net0,ifname=
> VLJDN01,macaddr=2:8:20:2:4b:a4,: vnic dhcp disabled
>
> qemu-system-x86_64: -net vnic,vlan=1,name=net1,ifname=
> VSJDN01,macaddr=2:8:20:67:1:7c,: vnic dhcp disabled
>
> qemu: too many IDE bus
> Failed to start VM
> Started VM:
> Public: 127.0.0.1
> 10.100.23.86
> ::1/128
> ::/0:5903
>
>
> I just upgrade to
>
> root@OmniosExitas:/KVM_Machines/JDN# uname -a
> SunOS OmniosExitas 5.11 omnios-r151020-4151d05 i86pc i386 i86pc
>
> Any suggestions ?
>
>
> Thanks in advance.
>
>
> Kind Regards.
>
>
> Dirk
>
>
>
> --
> Dirk Willems
> System Engineer
>
>
> +32 (0)3 443 12 38 <+32%203%20443%2012%2038>
> dirk.will...@exitas.be
>
> Quality. Passion. Personality
>
> www.exitas.be | Veldkant 31 | 2550 Kontich
>
> Illumos OmniOS Installation and Configuration Implementation Specialist.
> Oracle Solaris 11 Installation and Configuration Certified Implementation
> Specialist.
>
> ___
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] LX Zone DTrace

[Nahum Shalman]

Have you tried simply tracing the lx-syscall probes?

On Fri, Jan 13, 2017 at 9:24 AM, Mini Trader <miniflowtra...@gmail.com>
wrote:

> I followed these instructions prior to my post and my zone would not boot
> after doing the mod to add the flag to the file.
>
>
> On Fri, Jan 13, 2017 at 8:55 AM Nahum Shalman <nshal...@omniti.com> wrote:
>
>> The short answer is yes.
>>
>> My experience debugging LX was on SmartOS and there are some notes on
>> https://wiki.smartos.org/display/DOC/LX+Branded+Zones#
>> LXBrandedZones-Debugging
>>
>> Some of the details on that page are Specific to SmartOS, but some of it
>> is generic to LX.
>>
>> -Nahum
>>
>> On Fri, Jan 13, 2017 at 12:46 AM, Mini Trader <miniflowtra...@gmail.com>
>> wrote:
>>
>> Is there anything that can be done to trace a program having issues on an
>> LX Zone.
>>
>> I am seeing:
>>
>> OSError: [Errno 2] No such file or directory:
>>
>> Again under certain conditions which I am trying to trace - unfortunately
>> this is a closed source program.  Can DTrace be used to help track
>> something like this?
>>
>> Thanks!
>>
>>
>>
>> ___
>>
>>
>> OmniOS-discuss mailing list
>>
>>
>> OmniOS-discuss@lists.omniti.com
>>
>>
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>>
>>
>>
>>
>>
>>
>>
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] LX Zone DTrace

[Nahum Shalman]

The short answer is yes.

My experience debugging LX was on SmartOS and there are some notes on
https://wiki.smartos.org/display/DOC/LX+Branded+Zones#LXBrandedZones-Debugging

Some of the details on that page are Specific to SmartOS, but some of it is
generic to LX.

-Nahum

On Fri, Jan 13, 2017 at 12:46 AM, Mini Trader 
wrote:

> Is there anything that can be done to trace a program having issues on an
> LX Zone.
>
> I am seeing:
>
> OSError: [Errno 2] No such file or directory:
>
> Again under certain conditions which I am trying to trace - unfortunately
> this is a closed source program.  Can DTrace be used to help track
> something like this?
>
> Thanks!
>
> ___
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] LX zones: configurations

[Nahum Shalman]

On Wed, Jan 11, 2017 at 11:01 AM, Mini Trader 
wrote:

> With respect to virtualization, should one be turning on any hardware
> specific feature for the VM to properly use LX or it doesn't matter?
>

LX doesn't require hardware virtualization support. LX zones are like other
zones except that they use an emulated Linux system call table instead of a
native illumos system call table.
No actual Linux kernel is used so there's no need for the hardware
shenanigans (and their associated performance costs) to trick Linux into
thinking it's on hardware.

-Nahum
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] VNC access to KVM

[Nahum Shalman]

Have you tried Chicken of the VNC?
I seem to recall people in the SmartOS community having to be particular
about which VNC client worked.
Since the code is pretty much the same, I think OmniOS has the same issue...

-Nahum

On Fri, Dec 2, 2016 at 7:18 AM, Daniil V. Landau 
wrote:

> Hi!
>
> I have a clearly installed OmniOS r151020 and trying to setup a KVM
> virtual machine but can't connect to it's console using VNC client.
>
> I created a simple script to start my VM following the instructions on the
> OmniOS site:
>
> #!/usr/bin/bash
>
> HDD=/dev/zvol/rdsk/rpool/vmdisks/mds-system
>
> CD=/export/vm-distr/CentOS-6.7-x86_64-bin-DVD1.iso
>
> VNC=0
>
> MEM=4096
>
>
> mac1=`dladm show-vnic -po macaddress $VNIC1`
>
> mac2=`dladm show-vnic -po macaddress $VNIC2`
>
>
> /usr/bin/qemu-system-x86_64 \
>
> -name "$(basename $CD)" \
>
> -boot cd \
>
> -enable-kvm \
>
> -vnc 0.0.0.0:$VNC \
>
> -smp 2 \
>
> -m $MEM \
>
> -no-hpet \
>
> -localtime \
>
> -drive file=$HDD,if=ide,index=0 \
>
> -drive file=$CD,media=cdrom,if=ide,index=2  \
>
> -vga std
>
> When I start it looks like the VM starts normally:
>
> # ./mds-kvm.sh.tmp
> Start bios (version 0.6.1.2-20110201_165504-titi)
> Ram Size=0xe000 (0x2000 high)
> CPU Mhz=2096
> PCI: pci_bios_init_bus_rec bus = 0x0
> PIIX3/PIIX4 init: elcr=00 0c
> PCI: bus=0 devfn=0x00: vendor_id=0x8086 device_id=0x1237
> PCI: bus=0 devfn=0x08: vendor_id=0x8086 device_id=0x7000
> PCI: bus=0 devfn=0x09: vendor_id=0x8086 device_id=0x7010
> region 4: 0xc000
>
> <---skipped--->
>
> Booting from Hard Disk...
> Boot failed: not a bootable disk
>
> enter handle_18:
>   NULL
> Booting from DVD/CD...
> 3714MB medium detected
> Booting from :7c00
>
> In the same time I can't connect to VM console using VNC: OS X native
> client hangs in loop and Real VNC Viewer client just exits. It's log says:
>
> <14> 2016-12-02T12:15:23.963Z Fingolfin vncviewer[2568]: Child:
> CConnection: close: [EndOfStream] The connection closed unexpectedly.
>
> What could be the reason of this problem?
>
>
> Daniil
>
> ___
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] upgrading pkgsrc

[Nahum Shalman]

I'm glad to hear you got it working. :)

I had pinged Jonathan just before sending my response and he said he would
fix the instructions. He has done so [1].

Hopefully you have saved others from the same pain!

-Nahum

[1]
https://github.com/joyent/pkgsrc.joyent.com/commit/5744de534499a1a0ad0652b4c8f04da231eb509c

On Tue, Nov 1, 2016 at 10:56 PM, Geoff Nordli <geo...@gnaa.net> wrote:

>
>
> On 2016-11-01 10:36 AM, Nahum Shalman wrote:
>
> On Tue, Nov 1, 2016 at 1:32 AM, Geoff Nordli <geo...@gnaa.net> wrote:
>
>> I am running   OmniOS v11 r151016
>>
>
> You didn't mention which quarterly release of pkgsrc you were on.
>
> I tried to upgrade pkgsrc using the steps outlined here:
>>
>> https://pkgsrc.joyent.com/install-on-illumos/
>
>
> Note that those say:
> "Upgrades aren't fully supported (we don't yet handle major configuration
> changes) but this procedure may work fine for many users and avoid having
> to re-bootstrap. If in doubt ensure you have backed up your data and
> configuration files. Make sure you use the same set that was originally
> installed."
>
> Upgrades from release to release on pkgsrc have always been tricky. The
> general advice from Joyent when it comes to e.g. running joyent-brand
> pkgsrc zones under SmartOS has been "reprovision". That means make a note
> of which software you use, perhaps with config management, and start each
> time from scratch, that said, not all hope is lost.
>
> when I tried to upgrade pkgin it gives me this error:
>>
>> root@pc-oi1:~# /opt/local/sbin/pkg_add -U pkgin
>> SSL support disabled
>> pkg_add: Can't process https://pkgsrc.joyent.com:443/
>> packages/SmartOS/2016Q3/x86_64/All/pkgin*: Not owner
>> pkg_add: no pkg found for 'pkgin', sorry.
>> pkg_add: 1 package addition failed
>>
>>
>> If I try to do a pkgin update:
>>
>> root@pc-oi1:~# /opt/local/bin/pkgin update
>> reading local summary...
>> processing local summary...
>> SSL support disabled
>> SSL support disabled
>> SSL support disabled
>> pkgin: Could not fetch https://pkgsrc.joyent.com/pack
>> ages/SmartOS/2016Q3/x86_64/All/pkg_summary.gz
>>
>>
>>
>> If I use wget, i can download the gz file OK, so definitely the
>> networking is working fine.
>>
>> Any thoughts?
>>
>
> If you read through https://pkgsrc.joyent.com/changes/ for 2016Q3 you
> will notice that:
> "The pkg_install tools now support HTTPS, and both pkgin and pkg_add now
> fetch packages over HTTPS by default."
>
> That's a new feature for 2016Q3. Whatever quarterly release you're
> currently on doesn't support HTTPS yet.
>
> You may be able to use a "http://; URL (rather than "https://;) to
> perform the initial upgrade procedure you linked originally. After pkgin
> and the pkg_install tools have been upgraded you should be able to switch
> back to "https://;.
>
> All the same caveats about the upgrade process still apply.
>
> If you're upgrading a Postgres server I hope you've dumped the database in
> advance of attempting such an upgrade.
>
> -Nahum
>
>
> Hi Nahum.
>
> Yes, I had backups.
>
> There were only a few packages that needed to get upgrade and I know that
> Joyents doesn't recommend to upgrade, but to re-provision.
>
> Jonathan Perkin gave me some guidance.
>
> In order to get back to a working state, first edit this file:
>
>/opt/local/etc/pkg_install.conf
>
> and change the PKG_PATH URL to use "http://; instead of "https://;.
> You should then be able to follow the upgrade instructions.
>
> But I also needed to change http in:  /opt/local/etc/pkgin/repositories.conf
>
>
> Have a great day!!
>
> Geoff
>
>
>
>
> ___
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] upgrading pkgsrc

[Nahum Shalman]

On Tue, Nov 1, 2016 at 1:32 AM, Geoff Nordli  wrote:

> I am running   OmniOS v11 r151016
>

You didn't mention which quarterly release of pkgsrc you were on.

I tried to upgrade pkgsrc using the steps outlined here:
>
> https://pkgsrc.joyent.com/install-on-illumos/


Note that those say:
"Upgrades aren't fully supported (we don't yet handle major configuration
changes) but this procedure may work fine for many users and avoid having
to re-bootstrap. If in doubt ensure you have backed up your data and
configuration files. Make sure you use the same set that was originally
installed."

Upgrades from release to release on pkgsrc have always been tricky. The
general advice from Joyent when it comes to e.g. running joyent-brand
pkgsrc zones under SmartOS has been "reprovision". That means make a note
of which software you use, perhaps with config management, and start each
time from scratch, that said, not all hope is lost.

when I tried to upgrade pkgin it gives me this error:
>
> root@pc-oi1:~# /opt/local/sbin/pkg_add -U pkgin
> SSL support disabled
> pkg_add: Can't process https://pkgsrc.joyent.com:443/
> packages/SmartOS/2016Q3/x86_64/All/pkgin*: Not owner
> pkg_add: no pkg found for 'pkgin', sorry.
> pkg_add: 1 package addition failed
>
>
> If I try to do a pkgin update:
>
> root@pc-oi1:~# /opt/local/bin/pkgin update
> reading local summary...
> processing local summary...
> SSL support disabled
> SSL support disabled
> SSL support disabled
> pkgin: Could not fetch https://pkgsrc.joyent.com/pack
> ages/SmartOS/2016Q3/x86_64/All/pkg_summary.gz
>
>
>
> If I use wget, i can download the gz file OK, so definitely the networking
> is working fine.
>
> Any thoughts?
>

If you read through https://pkgsrc.joyent.com/changes/ for 2016Q3 you will
notice that:
"The pkg_install tools now support HTTPS, and both pkgin and pkg_add now
fetch packages over HTTPS by default."

That's a new feature for 2016Q3. Whatever quarterly release you're
currently on doesn't support HTTPS yet.

You may be able to use a "http://; URL (rather than "https://;) to perform
the initial upgrade procedure you linked originally. After pkgin and the
pkg_install tools have been upgraded you should be able to switch back to
"https://;.

All the same caveats about the upgrade process still apply.

If you're upgrading a Postgres server I hope you've dumped the database in
advance of attempting such an upgrade.

-Nahum
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Booting omnios from grub2

[Nahum Shalman]

Hi,

I see I will now have to pay for my sins for having written that wiki
page...
The short answer is that SmartOS is far more amenable to booting from
arbitrary boot loaders than OmniOS.

With SmartOS all you care about is booting the correct kernel and boot
archive.

OmniOS has boot environments (BEs). Booting into the correct BE requires
more information on the kernel command line than SmartOS does.
The `beadm` tool on OmniOS integrates with GRUB but has no integration for
GRUB2.

In the future, upstream illumos has recently landed a port of the FreeBSD
loader which has many of the same desirable features as GRUB2, but also
includes BE/beadm integration.

 Also, you'd have to be certain that the version of GRUB2 in question is
compatible with the pool features of the pool that OmniOS is on.

There are possibly some very clunky ways to get GRUB2 to look at the GRUB
configuration from OmniOS, but without explanation of *why* you want to do
this and how you expect it to behave, I'm not prepared to opine about
precisely how difficult it would be.

Could you clarify what you're trying to accomplish?

-Nahum

On Tue, Sep 27, 2016 at 7:23 AM, Bouktaib Mohssin <
bouktaib.mohs...@gmail.com> wrote:

> ​Hello Community
>
> I'm trying to boot omnios from grub2 using my ubuntu server ,i've triedit
> with smartos & it work (https://wiki.smartos.org/
> display/DOC/Booting+SmartOS+from+GRUB2)
> my question is how to boot omnios from grub2
>
> thanks :)​
>
> ___
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss