Re: [OpenIndiana-discuss] VirtualBox 5.2.14 crashing when attempting to start VM
Hey guys, I rolled back to pkg://openindiana.org/entire@0.5.11-2018.0.0.0:20180211T131012Z which is the pre-June update and all is back to normal again. My issue was that the mod "VirtualBox HostDrv" could not load at all, and the panic/reboots were swift and brutal. Cheers, Jacques Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 jacques.h...@threetwo.co.uk -Original Message- From: Predrag Zečević - Technical Support Analyst [mailto:predrag.zece...@2e-systems.com] Sent: 22 August 2018 14:36 To: openindiana-discuss@openindiana.org Subject: Re: [OpenIndiana-discuss] VirtualBox 5.2.14 crashing when attempting to start VM On 08/22/18 15:18, Udo Grabowski (IMK) wrote: > On 22/08/2018 14:29, Udo Grabowski (IMK) wrote: >> On 22/08/2018 12:39, Jacques Hugo wrote: >>> Hey Predrag, >>> . >>> I'm on this release -> SunOS 5.11 illumos-66a2141c21 illumos ... >>> If you touch the qemu-kvm bin the host panics immediately and >>> reboots >>> >> >> Checked that on real hardware (DataON CIB-9470V12, E5-2600 V2, C602) >> with current hipster: >> >> illumos-6640c13bea i86pc i386 i86pc >> >> qemu-kvm reboots the host immediately. Seems to be a serious bug. >> No panic message, just a reboot, starting in dbx looks like this: >> >> ro sunth7 ~ # dbx /usr/bin/qemu-kvm >> For information about new features see `help changes' >> To remove this message, put `dbxenv suppress_startup_message 7.7' in >> your .dbxrc Reading qemu-kvm Reading ld.so.1 Reading libc.so.1 >> (dbx) run -m 4g -smp 3 -cdrom >> /tftpboot/OI-hipster-minimal-20180427.iso >> Running: qemu-kvm -m 4g -smp 3 -cdrom >> /tftpboot/OI-hipster-minimal-20180427.iso >> (process id 1238) >> Reading libm.so.2 >> Reading libnsl.so.1 >> > > Have got a crashdump: > > > ::status > debugging crash dump vmcore.0 (64-bit) from imksunth7 operating > system: 5.11 illumos-6640c13bea (i86pc) image uuid: > ba4a4d5d-58bd-6dbd-ab55-ba047c459f90 > panic message: BAD TRAP: type=7 (#nm Device not available) > rp=fe426c6f2300 addr=fe426c6f2ea8 dump content: kernel pages > only > > > > ::stack > kvm_fx_finit() > vmx_vcpu_reset+0x97() > kvm_arch_vcpu_reset+0x6c() > kvm_arch_vcpu_setup+0x28() > kvm_vm_ioctl_create_vcpu+0x44() > kvm_ioctl+0xa2c() > cdev_ioctl+0x39(1320002, 2000ae41, 0, 202003, fea3a23ccad8, > fe426c6f2ea8) > spec_ioctl+0x60(fea3e4fa3880, 2000ae41, 0, 202003, > fea3a23ccad8, > fe426c6f2ea8) > fop_ioctl+0x55(fea3e4fa3880, 2000ae41, 0, 202003, > fea3a23ccad8, > fe426c6f2ea8) > ioctl+0x9b(9, 2000ae41, 0) > sys_syscall+0x177() > > > /dev/kvm is available and module is loaded: > > ro sunth7 /var/crash/crashcore # modinfo |grep kvm > 261 f7e7e000 376b0 306 1 kvm (kvm driver v0.1) > I have impression that incompatible changes was made on illumos level ... Thanks for looking at. Now, we need someone to get it working back... Regards. -- Predrag Zečević Technical Support Analyst 2e Systems GmbH tel: +49 - 6196 - 95058 - 15 mob: +49 - 174 - 3109288 fax: +49 - 6196 - 95058 - 94 e-mail: predrag.zece...@2e-systems.com headquarter: 2e Systems GmbH, Koenigsteiner Str. 87, 65812 Bad Soden am Taunus, Germany registration: Amtsgericht Koenigstein (Germany), HRB 7303 managing director: Phil Douglas http://www.2e-systems.com/ - Making your business fly! ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] VirtualBox 5.2.14 crashing when attempting to start VM
Hey Predrag, I'm on this release -> SunOS 5.11 illumos-66a2141c21 illumos I have exactly the same issues as you with VBox after years of working perfectly. I removed all VB instances and tried the latest qemu-kvm package available in the repo, with exactly the same results. If you touch the qemu-kvm bin the host panics immediately and reboots. I have emailed the fmdump output in a previous post. I really don't want to roll-back just yet since I have a few Zones I need to degrade as well. Any info from the community will be greatly appreciated. Cheers, Jacques Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 jacques.h...@threetwo.co.uk -Original Message- From: Predrag Zečević - Technical Support Analyst [mailto:predrag.zece...@2e-systems.com] Sent: 20 August 2018 08:37 To: openindiana-discuss@openindiana.org Subject: Re: [OpenIndiana-discuss] VirtualBox 5.2.14 crashing when attempting to start VM On 07/25/18 22:02, Michal Nowak wrote: > On 07/25/18 04:46 PM, russell wrote: >> Hi, >> >> I have been VirtualBox 5.2.14 since it came out without any issues >> until I performed a pkg update on 22nd July. >> Everytime I perform a pkg update I always specify a new boot >> environment, so last update which VirtualBox 5.2.14 worked on is the >> one I performed on the 12th July. I have made this BE activate so I >> do not have to remember to select it on boot. >> >> Regards >> >> Russell > > I think it might be the "eager FPU" changes which landed in > illumos-gate on June 13th: > > https://github.com/illumos/illumos-gate/commit/4c28a617e3922d92a58e813 > a5b955eb526b9c386 > > https://github.com/illumos/illumos-gate/commit/a32a1f376ed9360264e4a37 > 4608fdcc5c4927d63 > > > It's reported to the authors of those patches at > https://github.com/joyent/smartos-live/issues/792. > > I don't know of a workaround apart from sticking to versions before > the change. > > Michal > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > Hi all, just quick update on this: there were some changes in illumos, back (in July, I presume) which have messed up run of VirualBox package (solaris one, from virtualbox.org site, which is still running on old BE from July 6th, 2018). I have tried with OI /hipster update last time and as I have started VBox guest, system has crashed (I can provide core dump if required - I was reading it, but not sure what is causing problems). BTW, almost latest VBox (5.2.16) is running fine on mentioned BE: $ uname -rosv SunOS 5.11 illumos-229852ddf2 illumos I have tried to compile VBox from source and after some tweaks, managed to get it compiled w/o errors, but it simply does not start (did not have time to do deeper analysis): $ LD_LIBRARY_PATH=/usr/lib/qt/5.8/lib/amd64 ./VirtualBox caused error: -- Failed to create the VirtualBoxClient COM object. The application will now terminate. [Callee RC: NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154)] -- Till Wegmüller asked if I can boot VBox guest in qemu - not investigated although it is an option - I would like to stay at VirtualBox! Does anyone knows how to solve this problem (failure of VBox prevents me from OI upgrade). With best regards. Predrag Zečević -- Predrag Zečević Technical Support Analyst 2e Systems GmbH tel: +49 - 6196 - 95058 - 15 mob: +49 - 174 - 3109288 fax: +49 - 6196 - 95058 - 94 e-mail: predrag.zece...@2e-systems.com headquarter: 2e Systems GmbH, Koenigsteiner Str. 87, 65812 Bad Soden am Taunus, Germany registration: Amtsgericht Koenigstein (Germany), HRB 7303 managing director: Phil Douglas http://www.2e-systems.com/ - Making your business fly! ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Amazon AMI
Got it, thanks Peter. -Jacques Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 jacques.h...@threetwo.co.uk <mailto:jacques.h...@threetwo.co.uk> > On 25 May 2018, at 21:21, Peter Tribble <peter.trib...@gmail.com> wrote: > > On Thu, May 24, 2018 at 2:14 PM, Jacques Hugo <jacques.h...@threetwo.co.uk> > wrote: > >> Hi guys, >> >> I’m assuming the question was asked before, but did anyone successfully >> create an AMI image of OI Hipster? >> > > The OpenZFS project has one, but it's only available in us-east-1 as far as > I know (ami-c5c0a7d3 is the current one). > > So you can run it directly there, or copy it if you want or need to run it > in a different region. > > -- > -Peter Tribble > http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Amazon AMI
Excellent! Thanks, Al. Cheers, Jacques Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 jacques.h...@threetwo.co.uk <mailto:jacques.h...@threetwo.co.uk> > On 24 May 2018, at 16:06, Al Slater <al.sla...@scluk.com> wrote: > > Hi Jacques, > > On 24/05/18 14:14, Jacques Hugo wrote: >> I’m assuming the question was asked before, but did anyone successfully >> create an AMI image of OI Hipster? > > See > https://www.prakashsurya.com/post/2017-02-06-creating-a-custom-amazon-ec2-ami-from-iso/ > > regards > > -- > Al Slater > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Amazon AMI
Hi guys, I’m assuming the question was asked before, but did anyone successfully create an AMI image of OI Hipster? Cheers, Jacques Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 jacques.h...@threetwo.co.uk <mailto:jacques.h...@threetwo.co.uk> ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] mkvmerge fails
See if ffmpeg works for you. Something like ffmpeg -i video.avi -i audio.avi -map 0:0 -map 1:0 -c copy -f matroska games.mkv -Jacques Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 jacques.h...@threetwo.co.uk <mailto:jacques.h...@threetwo.co.uk> > On 23 May 2018, at 16:28, Apostolos Syropoulos via openindiana-discuss > <openindiana-discuss@openindiana.org> wrote: > > After upgrading I have noticed that neither mkvmerge nor mkvextract > work anymore! > $ mkvmerge -D audio.avi -A video.avi -o GAMES.mkv > terminate called after throwing an instance of 'std::bad_cast' > what(): std::bad_cast > Abort (core dumped) > > I have no idea what this KTPI thing does but it certainly has > made my life more difficult. How can I deactivate it? > > A.S. > > > -- > Apostolos Syropoulos > Xanthi, Greece > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Unified archives/installadm
Thanks, Alexander OK, I’m assuming that leaves the distraction constructor as an option. Do we have anything equivalent to `aimanifest` in OI? Cheers, Jacques Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 jacques.h...@threetwo.co.uk <mailto:jacques.h...@threetwo.co.uk> > On 22 May 2018, at 08:47, Alexander Pyhalov <a...@rsu.ru> wrote: > > On 05/21/18 10:50 PM, Jacques Hugo wrote: >> Hi all, >> Do we have anything equivalent to unified archives in Hipster? I also see >> that installadm is obsoleted: > > Hi. > Currently no. AI/installadm were unmaintained for a time enough to rot > completely and so were removed when underlying interfaces disappeared. > > I think, Till Wegmüller worked on some tool for automatic deployment, but I > don't know how far he has gone. > > -- > Best regards, > Alexander Pyhalov, > system administrator of Southern Federal University IT department ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Unified archives/installadm
Hi all, Do we have anything equivalent to unified archives in Hipster? I also see that installadm is obsoleted: $ pkg list -af installadm NAME (PUBLISHER) VERSION IFO install/installadm0.5.11-2018.0.0.1029 --o install/installadm0.5.11-2018.0.0.1025 --o install/installadm0.5.11-2018.0.0.1022 --o install/installadm0.5.11-2018.0.0.1020 --o Cheers for the info in advance. -Jacques Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 <mailto:jacques.h...@threetwo.co.uk> jacques.h...@threetwo.co.uk ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Start Xvnc on 2018.04
Spot on! Thanks, Michal. # pkg refresh openindiana.org # pkg list -af xvnc NAME (PUBLISHER) VERSIONIFO x11/server/xvnc 1.8.0-2018.0.0.0 --- x11/server/xvnc 1.7.1-2018.0.0.2 i-- x11/server/xvnc 1.7.1-2018.0.0.1 --- Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 jacques.h...@threetwo.co.uk <mailto:jacques.h...@threetwo.co.uk> > On 20 May 2018, at 08:30, Michal Nowak <mno...@startmail.com> wrote: > > Perhaps you just need a `pkg refresh`? This is what I see: > > $ pkg list -af xvnc > > NAME (PUBLISHER) VERSION IFO > x11/server/xvnc 1.8.0-2018.0.0.0 i-- > x11/server/xvnc 1.7.1-2018.0.0.2 --- > x11/server/xvnc 1.7.1-2018.0.0.1 --- > > I did `pkg update` yesterday. > > Michal > > On 05/20/18 09:16 AM, Jacques Hugo wrote: >> Hi Alexander, >> Thanks for the reply. What repo are you pointing to? I can’t see those pkg >> versions in the standard /hipster branch: >> $ pkg list -af xvnc >> NAME (PUBLISHER) VERSION >> IFO >> x11/server/xvnc 1.7.1-2018.0.0.2 >> i-- >> x11/server/xvnc 1.7.1-2018.0.0.1 >> --- >> Cheers for your help on this. >> -Jacques >> Jacques Hugo >> Three Two Labs >> Information Technology | Solaris Engineering 32L >> Phone +44 7939 433701 >> jacques.h...@threetwo.co.uk <mailto:jacques.h...@threetwo.co.uk> >>> On 19 May 2018, at 17:35, Alexander Pyhalov <a...@rsu.ru> wrote: >>> >>> On 12.05.2018 17:57, Jacques Hugo wrote: >>>> Hi all, >>>> Just double-checking here: but no one has ever seen this error on a new >>>> install? >>> >>> Hi. >>> >>> Sorry for long delay, the issue with Xvnc was fixed in >>> x11/server/xvnc@1.8.0,5.11-2018.0.0.0 . >>> >>> --- >>> System Administrator of Southern Federal University Computer Center >>> >> ___ >> openindiana-discuss mailing list >> openindiana-discuss@openindiana.org >> https://openindiana.org/mailman/listinfo/openindiana-discuss > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Start Xvnc on 2018.04
Hi Alexander, Thanks for the reply. What repo are you pointing to? I can’t see those pkg versions in the standard /hipster branch: $ pkg list -af xvnc NAME (PUBLISHER) VERSIONIFO x11/server/xvnc 1.7.1-2018.0.0.2 i-- x11/server/xvnc 1.7.1-2018.0.0.1 --- Cheers for your help on this. -Jacques Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 jacques.h...@threetwo.co.uk <mailto:jacques.h...@threetwo.co.uk> > On 19 May 2018, at 17:35, Alexander Pyhalov <a...@rsu.ru> wrote: > > On 12.05.2018 17:57, Jacques Hugo wrote: >> Hi all, >> Just double-checking here: but no one has ever seen this error on a new >> install? > > Hi. > > Sorry for long delay, the issue with Xvnc was fixed in > x11/server/xvnc@1.8.0,5.11-2018.0.0.0 . > > --- > System Administrator of Southern Federal University Computer Center > ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] find cycle's detected
Spot on! Thanks, Peter. Cheers, Jacques Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 jacques.h...@threetwo.co.uk -Original Message- From: Peter Tribble [mailto:peter.trib...@gmail.com] Sent: 12 May 2018 16:32 To: Discussion list for OpenIndiana <openindiana-discuss@openindiana.org> Subject: Re: [OpenIndiana-discuss] find cycle's detected On Sat, May 12, 2018 at 3:59 PM, Jacques Hugo <jacques.h...@threetwo.co.uk> wrote: > Hi all, > > Has anyone seen this error when compiling/installing from source: > > find: cycle detected for /lib/crypto/32/ > Something is picking up /usr/sbin/install (which behaves differently to the BSD and GNU versions of install). Many packages now are smart enough to autodetect, but not all. You'll need to help it find the gnu install. A couple of ways are: - 'make install INSTALL=ginstall' - ensuring /usr/gnu/bin is at the front of the path -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Start Xvnc on 2018.04
Hi there, Thanks for getting back to me. I have SUID'ed Xvnc, and opened permissions on /tmp/.X11xx including sticky bit, etc but still no joy. If it is any help, I kept the Xvnc binaries from the previous release and the work 100% fine For reference: $ for i in `/bin/ls` ; do md5sum $i; done 07b5afedde5747010a6f3bf97e38df96 Xvnc e65ebcea5d1ecd6051d31bc5b1ce1847 vncpasswd 24a0890f32108e76aab24b7fec8ab73b vncserver $ ls -l -r-xr-sr-x 1 root root 3019968 Apr 9 15:18 Xvnc -r-xr-xr-x 1 root root 28912 Apr 9 15:19 vncpasswd -r-xr-xr-x 1 root root 21296 Apr 9 15:18 vncserver The bins above work perfecly. Thanks for your help on this. Cheers, Jacques Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 jacques.h...@threetwo.co.uk -Original Message- From: Aurélien Larcher [mailto:aurelien.larc...@gmail.com] Sent: 12 May 2018 18:31 To: Discussion list for OpenIndiana <openindiana-discuss@openindiana.org> Subject: Re: [OpenIndiana-discuss] Start Xvnc on 2018.04 On Sat, May 12, 2018 at 4:57 PM, Jacques Hugo <jacques.h...@threetwo.co.uk> wrote: > Hi all, > > > > Just double-checking here: but no one has ever seen this error on a > new install? > > I did not have time to check but the actual error seems: Could not setppriv() PRIV_PERMITTED_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root _XSERVTransmkdir: Owner of /tmp/.X11-pipe should be set to root This package worked as expected the last time I updated Xorg, so not sure what happened. Andreas, can you check it? > > -Jacques > > > > > > Jacques Hugo > > Three Two Labs > > Information Technology | Solaris Engineering 32L > > Phone +44 7939 433701 > > <mailto:jacques.h...@threetwo.co.uk> jacques.h...@threetwo.co.uk > > > > From: Jacques Hugo [mailto:jacques.h...@threetwo.co.uk] > Sent: 08 May 2018 20:25 > To: 'openindiana-discuss@openindiana.org' > <openindiana-discuss@openindiana.org> > Subject: Start Xvnc on 2018.04 > > > > Hi guys, > > > > Any help appreciated. I'm trying to start Xvnc which have worked fine > until build a new host running 2018.04; the error message is below. > It complains about fonts but I'm not a 100% sure if that really is the > issue. All the pkg dependencies I have double checked with > > `pkg contents -r -o fmri,type -t depend xvnc` > > and they are all installed. > > > > The /tmp/.X11- is not being set to root correctly although Xvnc is > running with the default SGUID bit set > > `$ ls -l /usr/bin/Xvnc > > -r-xr-sr-x 1 root root 13577016 May 7 16:06 /usr/bin/Xvnc > > ` > > > > Not really sure what is causing this. Has anyone else seen this before? > > > > Cheers, > > Jacques > > > > > > > > > > $ vncserver > > > > WARNING: The first attempt to start Xvnc failed, possibly because the > font > > catalog is not properly configured. Attempting to determine an > appropriate > > font path for this system and restart Xvnc using that font path ... > > Could not start Xvnc. > > > > Could not setppriv() PRIV_PERMITTED_XSERVTransmkdir: Owner of > /tmp/.X11-unix should be set to root > > _XSERVTransmkdir: Owner of /tmp/.X11-pipe should be set to root > > > > Xvnc TigerVNC 1.7.1 > > Copyright (C) 1999-2016 TigerVNC Team and many others (see README.txt) > > See http://www.tigervnc.org for information on TigerVNC. > > Underlying X server release 11906000, The X.Org Foundation > > > > (EE) > > (EE) Backtrace: > > (EE) 0: /usr/bin/Xvnc (xorg_backtrace+0x49) [0x81020a9] > > (EE) 1: /usr/bin/Xvnc (OsSigHandler+0x64) [0x8108f54] > > (EE) 2: /lib/libc.so.1 (__sighndlr+0x15) [0xfebfed05] > > (EE) 3: /lib/libc.so.1 (call_user_handler+0x292) [0xfebf35b3] > > (EE) 4: /usr/bin/Xvnc (AddResource+0x2c) [0x80f07ec] > > (EE) 5: /usr/bin/Xvnc (PictureInit+0x143) [0x819d6d3] > > (EE) 6: /usr/bin/Xvnc (miPictureInit+0x23) [0x819b303] > > (EE) 7: /usr/bin/Xvnc (fbPictureInit+0x23) [0x8116913] > > (EE) 8: /usr/bin/Xvnc (vfbScreenInit+0x497) [0x80b8877] > > (EE) 9: /usr/bin/Xvnc (AddScreen+0xce) [0x80ca88e] > > (EE) 10: /usr/bin/Xvnc (InitOutput+0x147) [0x80b8a57] > > (EE) 11: /usr/bin/Xvnc (dix_main+0x258) [0x80ceba8] > > (EE) 12: /usr/bin/Xvnc (main+0x2a) [0x81fde6a] > > (EE) 13: /usr/bin/Xvnc (_start_crt+0x97) [0x80b64a8] > > (EE) 14: /usr/bin/Xvnc (_start+0x1a) [0x80b637a] > > (EE) > > (EE) Segmentation Fault at address 0x1 > > (EE) > > Fatal server error: > > (EE) Caught signal 11 (Segmentation Fault). S
[OpenIndiana-discuss] find cycle's detected
Hi all, Has anyone seen this error when compiling/installing from source: find: cycle detected for /lib/crypto/32/ find: cycle detected for /lib/32/ find: cycle detected for /lib/secure/32/ find: cycle detected for /usr/lib/firefox/bin/ find: cycle detected for /usr/lib/32/ find: cycle detected for /usr/lib/lwp/32/ find: cycle detected for /usr/lib/secure/32/ find: cycle detected for /usr/lib/link_audit/32/ find: cycle detected for /usr/lib/elfedit/32/ The 32bit dirs. Are soft symlinks back to "." if you look at the contents of the dirs above. Any pointers appreciated. Cheers, Jacques Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 <mailto:jacques.h...@threetwo.co.uk> jacques.h...@threetwo.co.uk ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Start Xvnc on 2018.04
Hi all, Just double-checking here: but no one has ever seen this error on a new install? -Jacques Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 <mailto:jacques.h...@threetwo.co.uk> jacques.h...@threetwo.co.uk From: Jacques Hugo [mailto:jacques.h...@threetwo.co.uk] Sent: 08 May 2018 20:25 To: 'openindiana-discuss@openindiana.org' <openindiana-discuss@openindiana.org> Subject: Start Xvnc on 2018.04 Hi guys, Any help appreciated. I'm trying to start Xvnc which have worked fine until build a new host running 2018.04; the error message is below. It complains about fonts but I'm not a 100% sure if that really is the issue. All the pkg dependencies I have double checked with `pkg contents -r -o fmri,type -t depend xvnc` and they are all installed. The /tmp/.X11- is not being set to root correctly although Xvnc is running with the default SGUID bit set `$ ls -l /usr/bin/Xvnc -r-xr-sr-x 1 root root 13577016 May 7 16:06 /usr/bin/Xvnc ` Not really sure what is causing this. Has anyone else seen this before? Cheers, Jacques $ vncserver WARNING: The first attempt to start Xvnc failed, possibly because the font catalog is not properly configured. Attempting to determine an appropriate font path for this system and restart Xvnc using that font path ... Could not start Xvnc. Could not setppriv() PRIV_PERMITTED_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root _XSERVTransmkdir: Owner of /tmp/.X11-pipe should be set to root Xvnc TigerVNC 1.7.1 Copyright (C) 1999-2016 TigerVNC Team and many others (see README.txt) See http://www.tigervnc.org for information on TigerVNC. Underlying X server release 11906000, The X.Org Foundation (EE) (EE) Backtrace: (EE) 0: /usr/bin/Xvnc (xorg_backtrace+0x49) [0x81020a9] (EE) 1: /usr/bin/Xvnc (OsSigHandler+0x64) [0x8108f54] (EE) 2: /lib/libc.so.1 (__sighndlr+0x15) [0xfebfed05] (EE) 3: /lib/libc.so.1 (call_user_handler+0x292) [0xfebf35b3] (EE) 4: /usr/bin/Xvnc (AddResource+0x2c) [0x80f07ec] (EE) 5: /usr/bin/Xvnc (PictureInit+0x143) [0x819d6d3] (EE) 6: /usr/bin/Xvnc (miPictureInit+0x23) [0x819b303] (EE) 7: /usr/bin/Xvnc (fbPictureInit+0x23) [0x8116913] (EE) 8: /usr/bin/Xvnc (vfbScreenInit+0x497) [0x80b8877] (EE) 9: /usr/bin/Xvnc (AddScreen+0xce) [0x80ca88e] (EE) 10: /usr/bin/Xvnc (InitOutput+0x147) [0x80b8a57] (EE) 11: /usr/bin/Xvnc (dix_main+0x258) [0x80ceba8] (EE) 12: /usr/bin/Xvnc (main+0x2a) [0x81fde6a] (EE) 13: /usr/bin/Xvnc (_start_crt+0x97) [0x80b64a8] (EE) 14: /usr/bin/Xvnc (_start+0x1a) [0x80b637a] (EE) (EE) Segmentation Fault at address 0x1 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation Fault). Server aborting (EE) Could not setppriv() PRIV_PERMITTED_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root _XSERVTransmkdir: Owner of /tmp/.X11-pipe should be set to root Xvnc TigerVNC 1.7.1 Copyright (C) 1999-2016 TigerVNC Team and many others (see README.txt) See http://www.tigervnc.org for information on TigerVNC. Underlying X server release 11906000, The X.Org Foundation (EE) (EE) Backtrace: (EE) 0: /usr/bin/Xvnc (xorg_backtrace+0x49) [0x81020a9] (EE) 1: /usr/bin/Xvnc (OsSigHandler+0x64) [0x8108f54] (EE) 2: /lib/libc.so.1 (__sighndlr+0x15) [0xf8d5ed05] (EE) 3: /lib/libc.so.1 (call_user_handler+0x292) [0xf8d535b3] (EE) 4: /usr/bin/Xvnc (AddResource+0x2c) [0x80f07ec] (EE) 5: /usr/bin/Xvnc (PictureInit+0x143) [0x819d6d3] (EE) 6: /usr/bin/Xvnc (miPictureInit+0x23) [0x819b303] (EE) 7: /usr/bin/Xvnc (fbPictureInit+0x23) [0x8116913] (EE) 8: /usr/bin/Xvnc (vfbScreenInit+0x497) [0x80b8877] (EE) 9: /usr/bin/Xvnc (AddScreen+0xce) [0x80ca88e] (EE) 10: /usr/bin/Xvnc (InitOutput+0x147) [0x80b8a57] (EE) 11: /usr/bin/Xvnc (dix_main+0x258) [0x80ceba8] (EE) 12: /usr/bin/Xvnc (main+0x2a) [0x81fde6a] (EE) 13: /usr/bin/Xvnc (_start_crt+0x97) [0x80b64a8] (EE) 14: /usr/bin/Xvnc (_start+0x1a) [0x80b637a] (EE) (EE) Segmentation Fault at address 0x1 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation Fault). Server aborting (EE) Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 <mailto:jacques.h...@threetwo.co.uk> jacques.h...@threetwo.co.uk ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Start Xvnc on 2018.04
Hi guys, Any help appreciated. I'm trying to start Xvnc which have worked fine until build a new host running 2018.04; the error message is below. It complains about fonts but I'm not a 100% sure if that really is the issue. All the pkg dependencies I have double checked with `pkg contents -r -o fmri,type -t depend xvnc` and they are all installed. The /tmp/.X11- is not being set to root correctly although Xvnc is running with the default SGUID bit set `$ ls -l /usr/bin/Xvnc -r-xr-sr-x 1 root root 13577016 May 7 16:06 /usr/bin/Xvnc ` Not really sure what is causing this. Has anyone else seen this before? Cheers, Jacques $ vncserver WARNING: The first attempt to start Xvnc failed, possibly because the font catalog is not properly configured. Attempting to determine an appropriate font path for this system and restart Xvnc using that font path ... Could not start Xvnc. Could not setppriv() PRIV_PERMITTED_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root _XSERVTransmkdir: Owner of /tmp/.X11-pipe should be set to root Xvnc TigerVNC 1.7.1 Copyright (C) 1999-2016 TigerVNC Team and many others (see README.txt) See http://www.tigervnc.org for information on TigerVNC. Underlying X server release 11906000, The X.Org Foundation (EE) (EE) Backtrace: (EE) 0: /usr/bin/Xvnc (xorg_backtrace+0x49) [0x81020a9] (EE) 1: /usr/bin/Xvnc (OsSigHandler+0x64) [0x8108f54] (EE) 2: /lib/libc.so.1 (__sighndlr+0x15) [0xfebfed05] (EE) 3: /lib/libc.so.1 (call_user_handler+0x292) [0xfebf35b3] (EE) 4: /usr/bin/Xvnc (AddResource+0x2c) [0x80f07ec] (EE) 5: /usr/bin/Xvnc (PictureInit+0x143) [0x819d6d3] (EE) 6: /usr/bin/Xvnc (miPictureInit+0x23) [0x819b303] (EE) 7: /usr/bin/Xvnc (fbPictureInit+0x23) [0x8116913] (EE) 8: /usr/bin/Xvnc (vfbScreenInit+0x497) [0x80b8877] (EE) 9: /usr/bin/Xvnc (AddScreen+0xce) [0x80ca88e] (EE) 10: /usr/bin/Xvnc (InitOutput+0x147) [0x80b8a57] (EE) 11: /usr/bin/Xvnc (dix_main+0x258) [0x80ceba8] (EE) 12: /usr/bin/Xvnc (main+0x2a) [0x81fde6a] (EE) 13: /usr/bin/Xvnc (_start_crt+0x97) [0x80b64a8] (EE) 14: /usr/bin/Xvnc (_start+0x1a) [0x80b637a] (EE) (EE) Segmentation Fault at address 0x1 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation Fault). Server aborting (EE) Could not setppriv() PRIV_PERMITTED_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root _XSERVTransmkdir: Owner of /tmp/.X11-pipe should be set to root Xvnc TigerVNC 1.7.1 Copyright (C) 1999-2016 TigerVNC Team and many others (see README.txt) See http://www.tigervnc.org for information on TigerVNC. Underlying X server release 11906000, The X.Org Foundation (EE) (EE) Backtrace: (EE) 0: /usr/bin/Xvnc (xorg_backtrace+0x49) [0x81020a9] (EE) 1: /usr/bin/Xvnc (OsSigHandler+0x64) [0x8108f54] (EE) 2: /lib/libc.so.1 (__sighndlr+0x15) [0xf8d5ed05] (EE) 3: /lib/libc.so.1 (call_user_handler+0x292) [0xf8d535b3] (EE) 4: /usr/bin/Xvnc (AddResource+0x2c) [0x80f07ec] (EE) 5: /usr/bin/Xvnc (PictureInit+0x143) [0x819d6d3] (EE) 6: /usr/bin/Xvnc (miPictureInit+0x23) [0x819b303] (EE) 7: /usr/bin/Xvnc (fbPictureInit+0x23) [0x8116913] (EE) 8: /usr/bin/Xvnc (vfbScreenInit+0x497) [0x80b8877] (EE) 9: /usr/bin/Xvnc (AddScreen+0xce) [0x80ca88e] (EE) 10: /usr/bin/Xvnc (InitOutput+0x147) [0x80b8a57] (EE) 11: /usr/bin/Xvnc (dix_main+0x258) [0x80ceba8] (EE) 12: /usr/bin/Xvnc (main+0x2a) [0x81fde6a] (EE) 13: /usr/bin/Xvnc (_start_crt+0x97) [0x80b64a8] (EE) 14: /usr/bin/Xvnc (_start+0x1a) [0x80b637a] (EE) (EE) Segmentation Fault at address 0x1 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation Fault). Server aborting (EE) Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 <mailto:jacques.h...@threetwo.co.uk> jacques.h...@threetwo.co.uk ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] The end is near
Off topic, yes, but definitely relevant. I for one would love to replace FreeBSD with OI on my Raspi's. -Jacques Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 jacques.h...@threetwo.co.uk -Original Message- From: openbabel [mailto:openba...@gmail.com] Sent: 20 March 2017 10:34 To: Discussion list for OpenIndiana <openindiana-discuss@openindiana.org> Subject: Re: [OpenIndiana-discuss] The end is near I think this is off topic noise..but my opinion is that this is the result of a decision by Fujitsu to back ARM technologies in the data centre. Following the announced takeover of this industry leading UK chip company the Japanise company now wants to launch new ARM technologies into the data centres. This may explain https://www.theregister.co.uk/2016/08/23/fujitsu_arm_post_k/ The question for oi is will it run on these ARM chips which will likely be common place after the downward fortunes of intels monoploy. On 25/01/2017 19:35, Alan Coopersmith wrote: > On 01/25/17 11:15 AM, Tim Mooney wrote: >> In regard to: Re: [OpenIndiana-discuss] The end is near, Udo >> Grabowski said...: >> >>> You need reliable sources: >>> <http://www.theregister.co.uk/2017/01/23/oracle_layoffs_in_hardware_div/> >>> >> >> I haven't seen any posts to the list from Alan Coopersmith since this >> thread started; here's hoping Alan escaped this unscathed. > > Then you must have deleted all the e-mails I sent: > https://openindiana.org/pipermail/openindiana-discuss/2017-January/020100.ht ml > > https://openindiana.org/pipermail/openindiana-discuss/2017-January/020102.ht ml > > https://openindiana.org/pipermail/openindiana-discuss/2017-January/020110.ht ml > > https://openindiana.org/pipermail/openindiana-discuss/2017-January/020113.ht ml > > https://openindiana.org/pipermail/openindiana-discuss/2017-January/020131.ht ml > > > As long as we're cluttering the OI list with off-topic noise, some > further > reading material on what we're doing with Solaris: > https://blogs.oracle.com/solaris/entry/oracle_solaris_moving_to_a > https://www.linkedin.com/pulse/approachable-innovation-bill-nesheim > > https://twitter.com/ORCL_Solaris & https://twitter.com/opensolaris > have both > been sharing various links as well (though obviously with different > biases). > https://twitter.com/alanc on the other hand is completely off-topic. 8-) > > -alan- > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Hipster & multi-user-desktop
Hi all, I have upgraded from /dev -> /hipster without any issues, however I am having trouble installing the multi-user-desktop group into a zone. Had no issues at all in /dev. My setup: - SunOS hipstervm 5.11 illumos-72136b4 i86pc i386 i86pc Output from installing the group: # pkg install multi-user-desktop 2>&1 | tee /var/tmp/desktop Startup: Refreshing catalog 'hipster-encumbered' ... Done Startup: Refreshing catalog 'openindiana.org' ... Done Planning: Solver setup ... Done Planning: Running solver ... pkg install: No matching version of group/feature/multi-user-desktop can be installed: Reject: pkg://openindiana.org/group/feature/multi-user-desktop@0.5.11-2015.0.2.5166: 20161003T120825Z Reason: No version matching 'require' dependency metapackages/gui-install@0.1-2015.0.2.0 can be installed Reject: pkg://openindiana.org/metapackages/gui-install@0.1-2016.0.0.3:20160823T20190 4Z Reason: All acceptable versions of 'require' dependency on runtime/python-26 are obsolete Reject: pkg://openindiana.org/metapackages/gui-install@0.1-2016.0.1.3:20161004T08245 7Z Reason: No version matching 'require' dependency system/install/auto-install can be installed Reject: pkg://openindiana.org/system/install/auto-install@0.5.11-2016.0.1.988:201609 30T180525Z to pkg://openindiana.org/system/install/auto-install@0.5.11-2016.1.0.996:201612 04T203226Z Reason: This version is excluded by installed incorporation consolidation/install/install-incorporation@0.5.11-2017.0.0.998 Reject: pkg://openindiana.org/system/install/auto-install@0.5.11-2017.0.0.998:201701 23T173451Z Reason: Package supports image variant variant.opensolaris.zone=[global] but doesn't support this image's variant.opensolaris.zone (nonglobal) Reject: pkg://openindiana.org/metapackages/gui-install@0.1-2016.0.1.3:20161004T10435 0Z to pkg://openindiana.org/metapackages/gui-install@0.1-2017.0.0.11:20170124T2122 55Z Reason: No version matching 'require' dependency system/install/auto-install can be installed Reject: pkg://openindiana.org/group/feature/multi-user-desktop@0.5.11-2015.0.2.5166: 20161018T134706Z to pkg://openindiana.org/group/feature/multi-user-desktop@0.5.11-2015.0.2.5166: 20170110T132149Z Reason: No version matching 'require' dependency metapackages/gui-install@0.1-2015.0.2.0 can be installed I have changed the facet version-lock to false on the above pkgs, but still cannot install the desktop. Any help appreciate. Cheers, Jacques Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 <mailto:jacques.h...@threetwo.co.uk> jacques.h...@threetwo.co.uk ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] KVM in Zones && networking
Hey John, Cheers for your help on this, much appreciated. I have tried it below in the past, but still get the same results even if you enable forwarding between the interfaces. I now doubt you can run a KVM in a Zone on OpenIndiana so it's back to OmniOS. All the best, Jacques Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 jacques.h...@threetwo.co.uk -Original Message- From: John D Groenveld [mailto:jdg...@elvis.arl.psu.edu] Sent: 22 February 2016 21:25 To: Discussion list for OpenIndiana <openindiana-discuss@openindiana.org> Subject: Re: [OpenIndiana-discuss] KVM in Zones && networking In message <003501d16db4$7bfc7ae0$73f570a0$@threetwo.co.uk>, "Jacques Hugo" wri tes: >I have done that earlier this evening. I can see only UDP and ICMP >based traffic, that's all. Nothing TCP related. It seem that a step >is needed to That's great, you've confirmed that your kvm1 interface is on the wire. >the the NGZ (via the GZ??) to route traffic from the kvm1 NIC to the KVM ... >not sure how to do that in a Zone. ifconfig down and unplumb your kvm1 interface, boot your KVM guest. Confirm within the KVM guest, that the e1000g interface has the correct MAC address and can snoop the wire. John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] KVM in Zones && networking
Hi John, I have done that earlier this evening. I can see only UDP and ICMP based traffic, that's all. Nothing TCP related. It seem that a step is needed to the the NGZ (via the GZ??) to route traffic from the kvm1 NIC to the KVM ... not sure how to do that in a Zone. -Jacques Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 jacques.h...@threetwo.co.uk -Original Message- From: John D Groenveld [mailto:jdg...@elvis.arl.psu.edu] Sent: 22 February 2016 20:47 To: Discussion list for OpenIndiana <openindiana-discuss@openindiana.org> Subject: Re: [OpenIndiana-discuss] KVM in Zones && networking In message <002a01d16db0$8b975f00$a2c61d00$@threetwo.co.uk>, "Jacques Hugo" wri tes: >Here's my NGZ KVM script ... exactly the same as my GZ KVM script with >the only difference being the vnic. > >#!/bin/ksh >MAC=$(dladm show-vnic -po macaddress kvm1) /usr/bin/qemu-kvm \ >-boot cd \ >-cpu host \ >-enable-kvm \ >-vnc 0.0.0.0:43 \ >-smp 4 \ >-m 8192 \ >-no-hpet \ >-localtime \ >-drive >file=/dev/zvol/rdsk/naspool/zones/src/kvm/disk0,if=ide,index=0 \ >-drive >file=/naspool/zones/src/kvm/iso/sol-11_3-text-x86.iso,media=cdrom,if=id >e,ind >ex=2 \ >-net nic,vlan=0,name=net0,model=e1000,macaddr=$MAC \ >-net vnic,vlan=0,name=net0,ifname=kvm1,macaddr=$MAC \ >-vga std That looks correct. Within your NGZ, shutdown your KVM, plumb your kvm1 interface, and snoop -d kvm1, do you see network traffic? John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] KVM in Zones && networking
And sorry, yes ... the NGZ works 100% with vnic1, no problems there. The GZ <-> NGZ <-> Local net/Internet is fully working. -Jacques Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 jacques.h...@threetwo.co.uk -Original Message- From: Jacques Hugo [mailto:jacques.h...@threetwo.co.uk] Sent: 22 February 2016 20:35 To: 'Discussion list for OpenIndiana' <openindiana-discuss@openindiana.org> Subject: Re: [OpenIndiana-discuss] KVM in Zones && networking Hey John, Cheers for the quick reply. Here's my NGZ KVM script ... exactly the same as my GZ KVM script with the only difference being the vnic. #!/bin/ksh MAC=$(dladm show-vnic -po macaddress kvm1) /usr/bin/qemu-kvm \ -boot cd \ -cpu host \ -enable-kvm \ -vnc 0.0.0.0:43 \ -smp 4 \ -m 8192 \ -no-hpet \ -localtime \ -drive file=/dev/zvol/rdsk/naspool/zones/src/kvm/disk0,if=ide,index=0 \ -drive file=/naspool/zones/src/kvm/iso/sol-11_3-text-x86.iso,media=cdrom,if=ide,ind ex=2 \ -net nic,vlan=0,name=net0,model=e1000,macaddr=$MAC \ -net vnic,vlan=0,name=net0,ifname=kvm1,macaddr=$MAC \ -vga std I need to somehow tell the KVM and the Zone that the the KVM's net0 is the Zones's kvm1 ... not sure how to! -Jacques Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 jacques.h...@threetwo.co.uk -Original Message- From: John D Groenveld [mailto:jdg...@elvis.arl.psu.edu] Sent: 22 February 2016 20:28 To: Discussion list for OpenIndiana <openindiana-discuss@openindiana.org> Subject: Re: [OpenIndiana-discuss] KVM in Zones && networking In message <001f01d16dab$a65d69b0$f3183d10$@threetwo.co.uk>, "Jacques Hugo" wri tes: > # zonecfg -z src export > create -b > set zonepath=/naspool/zones/src > set brand=ipkg > set autoboot=false > set ip-type=exclusive > add net > set physical=vnic1 > end > add net > set physical=kvm1 > end > add device > set match=/dev/kvm > end > add device > set match=/dev/zvol/rdsk/naspool/zones/src/kvm > end > add dataset > set name=naspool/zones/src/kvm > end > > > I have 2 x vnics presented to it ... vnic1 for the Zone, and kvm1 for >the KVM > > And this is what it looks like inside the Zone: > > # dladm show-vnic > LINK OVER SPEED MACADDRESSMACADDRTYPE >VID > vnic1?1000 2:8:20:d8:ad:72 random >0 > kvm1 ?1000 2:8:20:52:33:8e random >0 > > # ifconfig -a > lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> >mtu 8232 index 1 > inet 127.0.0.1 netmask ff00 > vnic1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 >index 2 > inet 192.168.1.41 netmask ff00 broadcast 192.168.1.255 > ether 2:8:20:d8:ad:72 > > You can see both NIC instances: > > # ls -l /dev/net/ > total 0 > crw-rw-rw- 1 root sys 265, 1024 Feb 21 18:24 kvm1 > crw-rw-rw- 1 root sys 265, 1005 Feb 21 18:20 vnic1 Your NGZ is correctly networked with vnic1? >When the KVM starts, it *does not* plumb the vnic assigned to it (kvm1). >Doing it manually it complains about the interface already in use. > >I have seen various documentation in the INET describing this to work >perfectly, however I can't get the networking to work. Any help >appreciated. I run my NGZ KVMs with VNICs over etherstubs but I doubt that difference is your problem. What's your NGZ KVM shell script? John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] KVM in Zones && networking
Hey John, Cheers for the quick reply. Here's my NGZ KVM script ... exactly the same as my GZ KVM script with the only difference being the vnic. #!/bin/ksh MAC=$(dladm show-vnic -po macaddress kvm1) /usr/bin/qemu-kvm \ -boot cd \ -cpu host \ -enable-kvm \ -vnc 0.0.0.0:43 \ -smp 4 \ -m 8192 \ -no-hpet \ -localtime \ -drive file=/dev/zvol/rdsk/naspool/zones/src/kvm/disk0,if=ide,index=0 \ -drive file=/naspool/zones/src/kvm/iso/sol-11_3-text-x86.iso,media=cdrom,if=ide,ind ex=2 \ -net nic,vlan=0,name=net0,model=e1000,macaddr=$MAC \ -net vnic,vlan=0,name=net0,ifname=kvm1,macaddr=$MAC \ -vga std I need to somehow tell the KVM and the Zone that the the KVM's net0 is the Zones's kvm1 ... not sure how to! -Jacques Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 jacques.h...@threetwo.co.uk -Original Message- From: John D Groenveld [mailto:jdg...@elvis.arl.psu.edu] Sent: 22 February 2016 20:28 To: Discussion list for OpenIndiana <openindiana-discuss@openindiana.org> Subject: Re: [OpenIndiana-discuss] KVM in Zones && networking In message <001f01d16dab$a65d69b0$f3183d10$@threetwo.co.uk>, "Jacques Hugo" wri tes: > # zonecfg -z src export > create -b > set zonepath=/naspool/zones/src > set brand=ipkg > set autoboot=false > set ip-type=exclusive > add net > set physical=vnic1 > end > add net > set physical=kvm1 > end > add device > set match=/dev/kvm > end > add device > set match=/dev/zvol/rdsk/naspool/zones/src/kvm > end > add dataset > set name=naspool/zones/src/kvm > end > > > I have 2 x vnics presented to it ... vnic1 for the Zone, and kvm1 for >the KVM > > And this is what it looks like inside the Zone: > > # dladm show-vnic > LINK OVER SPEED MACADDRESSMACADDRTYPE >VID > vnic1?1000 2:8:20:d8:ad:72 random >0 > kvm1 ?1000 2:8:20:52:33:8e random >0 > > # ifconfig -a > lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> >mtu 8232 index 1 > inet 127.0.0.1 netmask ff00 > vnic1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 >index 2 > inet 192.168.1.41 netmask ff00 broadcast 192.168.1.255 > ether 2:8:20:d8:ad:72 > > You can see both NIC instances: > > # ls -l /dev/net/ > total 0 > crw-rw-rw- 1 root sys 265, 1024 Feb 21 18:24 kvm1 > crw-rw-rw- 1 root sys 265, 1005 Feb 21 18:20 vnic1 Your NGZ is correctly networked with vnic1? >When the KVM starts, it *does not* plumb the vnic assigned to it (kvm1). >Doing it manually it complains about the interface already in use. > >I have seen various documentation in the INET describing this to work >perfectly, however I can't get the networking to work. Any help >appreciated. I run my NGZ KVMs with VNICs over etherstubs but I doubt that difference is your problem. What's your NGZ KVM shell script? John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] KVM in Zones && networking
Hi all, Apologies for the late reply; work, life, etc ... Here are the answers to your questions, if you need anything else please let me know: The reason for running KVM in Zones is pretty much around security and a bit more. You have the "layered virtualisation" approach, should your KVM instance be compromised, the intruder will find himself on an empty Zone. You also have the advantage of managing the KVM via standard Solaris Zone commands including SMF. In a clustered environment (i.e.: VCS) we have the capability of being able to "fail over" a Zone between nodes, and indeed to DR even if the DR cluster is on another continent; works a treat. Running KVM in the GZ is straight forward. Some info: 1. GZ: # dladm show-phys LINK MEDIASTATE SPEED DUPLEX DEVICE igb0 Ethernet up 1000 full igb0 # dladm show-vnic LINK OVER SPEED MACADDRESS MACADDRTYPE VID net0 igb0 1000 2:8:20:4:5e:e1random 0 net1 igb0 1000 2:8:20:d:5b:d2random 0 vnic0igb0 1000 2:8:20:d8:c2:5d random 0 vnic1igb0 1000 2:8:20:d8:ad:72 random 0 kvm1 igb0 1000 2:8:20:52:33:8e random 0 2. Current KVM in GZ: GZ runs on net0, and KVM in GZ runs on net1 ... all good there. # ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff00 net0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3 inet 192.168.1.39 netmask ff00 broadcast 192.168.1.255 ether 2:8:20:4:5e:e1 net1: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4 inet 0.0.0.0 netmask 0 ether 2:8:20:d:5b:d2 From the ifconfig output above, I *did not* have to plumb the net1 interface for the KVM instance, it appeared automatically. 3. Here's the Zone: # zonecfg -z src export create -b set zonepath=/naspool/zones/src set brand=ipkg set autoboot=false set ip-type=exclusive add net set physical=vnic1 end add net set physical=kvm1 end add device set match=/dev/kvm end add device set match=/dev/zvol/rdsk/naspool/zones/src/kvm end add dataset set name=naspool/zones/src/kvm end I have 2 x vnics presented to it ... vnic1 for the Zone, and kvm1 for the KVM And this is what it looks like inside the Zone: # dladm show-vnic LINK OVER SPEED MACADDRESSMACADDRTYPE VID vnic1?1000 2:8:20:d8:ad:72 random 0 kvm1 ?1000 2:8:20:52:33:8e random 0 # ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff00 vnic1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 192.168.1.41 netmask ff00 broadcast 192.168.1.255 ether 2:8:20:d8:ad:72 You can see both NIC instances: # ls -l /dev/net/ total 0 crw-rw-rw- 1 root sys 265, 1024 Feb 21 18:24 kvm1 crw-rw-rw- 1 root sys 265, 1005 Feb 21 18:20 vnic1 When the KVM starts, it *does not* plumb the vnic assigned to it (kvm1). Doing it manually it complains about the interface already in use. I have seen various documentation in the INET describing this to work perfectly, however I can't get the networking to work. Any help appreciated. Cheers, Jacques Jacques Hugo Three Two Labs Information Technology | Solaris Engineering 32L Phone +44 7939 433701 jacques.h...@threetwo.co.uk -Original Message- From: John D Groenveld [mailto:jdg...@elvis.arl.psu.edu] Sent: 22 February 2016 14:55 To: Discussion list for OpenIndiana <openindiana-discuss@openindiana.org> Subject: Re: [OpenIndiana-discuss] KVM in Zones && networking In message <56cb0d12.20...@calin.de>, Calin Somoza writes: >No Connection to/from kvm Solaris 11 Guest: As Jon explained to Jacques, its probably because the interface you handed to KVM is already plumbed. John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] KVM in Zones && networking
Hi all, This post is around running a KVM inside a Zone and trying to get the networking working. I hope some of you have a working config and any help is appreciated. Although networking in the Zone is working fine, I cannot seem to connect in the KVM running inside it. I'm def missing a networking/routing issue here. I am sure this is the standard setup (output shortened for brevities sake): 1. Global Zone's network interfaced. We're using vnic1 for the Zone # dladm show-vnic LINK OVER SPEED MACADDRESSMACADDRTYPE VID net0 igb0 1000 2:8:20:4:5e:e1random 0 net1 igb0 1000 2:8:20:d:5b:d2random 0 vnic1igb0 1000 2:8:20:d8:ad:72 random 0 ## using this VNIC 2. Zone setup. The Zone has exclusive rights to the physical interface (vnic 1) # zonecfg -z src info zonename: src zonepath: /naspool/zones/src brand: ipkg autoboot: true bootargs: pool: limitpriv: scheduling-class: ip-type: exclusive hostid: fs-allowed: net: address not specified allowed-address not specified physical: vnic1 defrouter not specified device: match: /dev/kvm device: match: /dev/zvol/rdsk/naspool/zones/src/kvm dataset: name: naspool/zones/src/kvm 3. The startscript for the KVM: #!/bin/ksh MAC=$(dladm show-vnic -po macaddress vnic1) /usr/bin/qemu-kvm \ -boot cd \ -cpu host \ -enable-kvm \ -vnc 0.0.0.0:43 \ -smp 4 \ -m 8192 \ -no-hpet \ -localtime \ -drive file=/dev/zvol/rdsk/naspool/zones/src/kvm/disk0,if=ide,index=0 \ -drive file=/naspool/zones/src/kvm/iso/sol-11_3-text-x86.iso,media=cdrom,if=ide,ind ex=2 \ -net nic,vlan=0,name=net0,model=e1000,macaddr=$MAC \ -net vnic,vlan=0,name=net0,ifname=vnic1,macaddr=$MAC \ -vga std The KVM (Solaris 11) start fine and the installation goes through without a hitch (quite fast to be honest, very good performance). However I cannot connect to it from the outside. The KVM host I have configured with an IP but cannot ping it, or from the KVM itself cannot see the default gw. However traffic to/from the Zone is working fine. Running a KVM in the Global Zone works a treat, however inside a Zone I am definitely missing a step in getting the routing from the KVM to the Zone sorted. Any help appreciated. Thanks for your time. Regards, Jacques ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
