Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
On Wed, Oct 24, 2018 at 8:52 AM Predrag Zečević - Technical Support Analyst wrote: > > > On 10/23/18 22:10, John D Groenveld wrote: > > In message < > alpine.soc.2.20.1810231249340.28...@dogbert.cc.ndsu.nodak.edu>, Tim > > Mooney writes: > >> 3) what other things are missing to bring KVM/QEMU to good feature > parity, > >> at least for Windows VMs, with VB? Anyone looked at USB passthrough? > >> How's audio support? Does a working libspice get us both shared > clipboard > >> and shared folders? > > > > Neither KVM nor bhyve support USB passthru. > > bhyve supports PCI passthru, but you would have to pass an entire > > USB add-on card to your guest. > > > > Shared folders can be solved with NFS and CIFS. > > > > > > BTW has anyone tried to port VBox to OI? > > Even without Oracle's proprietary bits it may be useful. > > It is for FreeBSD hosts and guests. > > > > John > > groenv...@acm.org > > I have tried to compile VirtualBox > (https://forums.virtualbox.org/viewtopic.php?f=40=89340), but was > stuck in dtrace probes failure. No support from VB guys can be expected... > I updated Alexander's recipe but could use help with the install stage. It seems there is not scripted install, Arch Linux and Debian use a homebrewed install target. https://github.com/OpenIndiana/oi-userland/pull/4569 > > So, I have switched to KVM. Not ideal - but what choice I had IF I want > to keep OI (because native zfs support)? > > With best regards. > Predrag Zečević > > > > ___ > > openindiana-discuss mailing list > > openindiana-discuss@openindiana.org > > https://openindiana.org/mailman/listinfo/openindiana-discuss > > > > -- > 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 > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
On Sun, Oct 28, 2018 at 12:33 AM Bob Friesenhahn < bfrie...@simple.dallas.tx.us> wrote: > On Sun, 28 Oct 2018, Aurélien Larcher wrote: > > >> I have tried to compile VirtualBox > >> (https://forums.virtualbox.org/viewtopic.php?f=40=89340), but was > >> stuck in dtrace probes failure. No support from VB guys can be > expected... > > > > > > Back then when I checked there was a difference between Solaris and > illumos > > w.r.t files without probes. > > Solaris skips them whereas illumos throws an error. > > I found the patch that allowed me to build and install VirtualBox 5.1.6 > > back then, attached for reference. > > It was usable besides some issues with the clipboard and USB devices. > > There was nothing attached! > I guess it was removed by the mail server. It appears as attachment in my client. I will upload to the Wiki. > > Bob > -- > Bob Friesenhahn > bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ > GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
On Sun, 28 Oct 2018, Aurélien Larcher wrote: I have tried to compile VirtualBox (https://forums.virtualbox.org/viewtopic.php?f=40=89340), but was stuck in dtrace probes failure. No support from VB guys can be expected... Back then when I checked there was a difference between Solaris and illumos w.r.t files without probes. Solaris skips them whereas illumos throws an error. I found the patch that allowed me to build and install VirtualBox 5.1.6 back then, attached for reference. It was usable besides some issues with the clipboard and USB devices. There was nothing attached! Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
> I have tried to compile VirtualBox > (https://forums.virtualbox.org/viewtopic.php?f=40=89340), but was > stuck in dtrace probes failure. No support from VB guys can be expected... Back then when I checked there was a difference between Solaris and illumos w.r.t files without probes. Solaris skips them whereas illumos throws an error. I found the patch that allowed me to build and install VirtualBox 5.1.6 back then, attached for reference. It was usable besides some issues with the clipboard and USB devices. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
Hi. If you find issues with distro_const configuration files, please, be sure to fix them in https://github.com/OpenIndiana/slim_source/ С уважением, Александр Пыхалов, программист отдела телекоммуникационной инфраструктуры управления информационно-коммуникационной инфраструктуры ЮФУ От: Aurélien Larcher Отправлено: 25 октября 2018 г. 3:02:38 Кому: Discussion list for OpenIndiana Тема: Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20 On Wed, Oct 24, 2018 at 2:14 PM Till Wegmüller wrote: > You'll at least need > > lrwxrwxrwx 1 root root 15 Sep 15 2017 > /usr/lib/64/libncurses.so -> libncurses.so.5 > lrwxrwxrwx 1 root root 17 Sep 15 2017 > /usr/lib/64/libncurses.so.5 -> libncurses.so.5.9 > -r-xr-xr-x 2 root bin 470K Apr 3 2018 > /usr/lib/64/libncurses.so.5.9 > lrwxrwxrwx 1 root root 16 Sep 15 2017 > /usr/lib/64/libncursesw.so -> libncursesw.so.5 > lrwxrwxrwx 1 root root 18 Sep 15 2017 > /usr/lib/64/libncursesw.so.5 -> libncursesw.so.5.9 > -r-xr-xr-x 2 root bin 470K Apr 3 2018 > /usr/lib/64/libncursesw.so.5.9 > > It will not autoresolve symlinks. > I have regenerated the image http://dlc-int.openindiana.org/users/aurelien/gcc-next/20181024/ > > Greetings > Till > > On 24.10.18 14:11, Aurélien Larcher wrote: > > On Wed, Oct 24, 2018 at 2:09 PM Till Wegmüller > wrote: > > > >> It was a 32bit 64bit problem the last time I ran into it. Fact is the > >> boot archive is missing libraries in it's default configuration as it is > >> in slim_source repository and you will need to add those files to the > >> filelist. > >> > > > > I added type="file">usr/lib/64/libncurses.so.5 > > to the manifest and started the job again. > > We'll see... > > > > > >> > >> And yes It could also be that for some reason distro_const failed to > >> copy libncurses to boot_archive. Also note that you will only hit that > >> problem when solaris.zlib can not be loaded. i.e. CD-ROM not found or > >> Netboot. > >> > > > > Thanks for your help! > > > > Aurélien > > > >> > >> Greetings > >> Till > >> > >> On 24.10.18 13:45, Aurélien Larcher wrote: > >>> Thanks for the help! > >>> I am not sure what you meant by dependency to 32- and 64-bit bash since > >> we > >>> only have 64-bit. > >>> Coud it just be a punctual problem with the image creation by > >> distro_const? > >>> I tested the 20181016 image at > >>> > >>> http://dlc-int.openindiana.org/users/aurelien/gcc-next/20181016/ > >>> > >>> without any problem on my machine and it should contain the same > packages > >>> aside from mate-system-monitor. > >>> > >>> I will re-run the image > >> > >> ___ > >> 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 > -- --- Praise the Caffeine embeddings ___ 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] Upgraded to VirtualBox 5.2.20
On Wed, Oct 24, 2018 at 2:14 PM Till Wegmüller wrote: > You'll at least need > > lrwxrwxrwx 1 root root 15 Sep 15 2017 > /usr/lib/64/libncurses.so -> libncurses.so.5 > lrwxrwxrwx 1 root root 17 Sep 15 2017 > /usr/lib/64/libncurses.so.5 -> libncurses.so.5.9 > -r-xr-xr-x 2 root bin 470K Apr 3 2018 > /usr/lib/64/libncurses.so.5.9 > lrwxrwxrwx 1 root root 16 Sep 15 2017 > /usr/lib/64/libncursesw.so -> libncursesw.so.5 > lrwxrwxrwx 1 root root 18 Sep 15 2017 > /usr/lib/64/libncursesw.so.5 -> libncursesw.so.5.9 > -r-xr-xr-x 2 root bin 470K Apr 3 2018 > /usr/lib/64/libncursesw.so.5.9 > > It will not autoresolve symlinks. > I have regenerated the image http://dlc-int.openindiana.org/users/aurelien/gcc-next/20181024/ > > Greetings > Till > > On 24.10.18 14:11, Aurélien Larcher wrote: > > On Wed, Oct 24, 2018 at 2:09 PM Till Wegmüller > wrote: > > > >> It was a 32bit 64bit problem the last time I ran into it. Fact is the > >> boot archive is missing libraries in it's default configuration as it is > >> in slim_source repository and you will need to add those files to the > >> filelist. > >> > > > > I added type="file">usr/lib/64/libncurses.so.5 > > to the manifest and started the job again. > > We'll see... > > > > > >> > >> And yes It could also be that for some reason distro_const failed to > >> copy libncurses to boot_archive. Also note that you will only hit that > >> problem when solaris.zlib can not be loaded. i.e. CD-ROM not found or > >> Netboot. > >> > > > > Thanks for your help! > > > > Aurélien > > > >> > >> Greetings > >> Till > >> > >> On 24.10.18 13:45, Aurélien Larcher wrote: > >>> Thanks for the help! > >>> I am not sure what you meant by dependency to 32- and 64-bit bash since > >> we > >>> only have 64-bit. > >>> Coud it just be a punctual problem with the image creation by > >> distro_const? > >>> I tested the 20181016 image at > >>> > >>> http://dlc-int.openindiana.org/users/aurelien/gcc-next/20181016/ > >>> > >>> without any problem on my machine and it should contain the same > packages > >>> aside from mate-system-monitor. > >>> > >>> I will re-run the image > >> > >> ___ > >> 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 > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
On 24/10/2018 10:32 PM, Aurélien Larcher wrote: On Wed, Oct 24, 2018 at 8:07 AM Carl Brewer wrote: Could you try to boot this? http://dlc-int.openindiana.org/users/aurelien/gcc-next/20181023/ It boots! Good to know! I will regenerate an image with Till's fix. Great, thank you! Carl ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
On Mon, Oct 22, 2018 at 7:36 PM russell wrote: > Hi, > > Upgraded to VirtualBox 5.2.20 yesterday, this works fine on the BE > completed on the 11th July but still get the lockup and reboot on any > later BE. > > As aside I also managed to get ESXi 6.5u2 (the last supported release > for my CPUs) running within VirtualBox 5.2.20 as a VM, a 300GB IDE > drive, 4 cpus and 4 Intel 82543GC (Pro/1000 T) interfaces. While the > Intel 82545EM where identified correctly, no traffic was transferred. > If there was enough interest we could move forward on https://github.com/OpenIndiana/oi-userland/pull/3722 add my old patches to Virtualbox and work on the FPU stuff. But I do not have time to work on this alone. Aurelien > > Regards > > Russell > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
You'll at least need lrwxrwxrwx 1 root root 15 Sep 15 2017 /usr/lib/64/libncurses.so -> libncurses.so.5 lrwxrwxrwx 1 root root 17 Sep 15 2017 /usr/lib/64/libncurses.so.5 -> libncurses.so.5.9 -r-xr-xr-x 2 root bin 470K Apr 3 2018 /usr/lib/64/libncurses.so.5.9 lrwxrwxrwx 1 root root 16 Sep 15 2017 /usr/lib/64/libncursesw.so -> libncursesw.so.5 lrwxrwxrwx 1 root root 18 Sep 15 2017 /usr/lib/64/libncursesw.so.5 -> libncursesw.so.5.9 -r-xr-xr-x 2 root bin 470K Apr 3 2018 /usr/lib/64/libncursesw.so.5.9 It will not autoresolve symlinks. Greetings Till On 24.10.18 14:11, Aurélien Larcher wrote: > On Wed, Oct 24, 2018 at 2:09 PM Till Wegmüller wrote: > >> It was a 32bit 64bit problem the last time I ran into it. Fact is the >> boot archive is missing libraries in it's default configuration as it is >> in slim_source repository and you will need to add those files to the >> filelist. >> > > I added usr/lib/64/libncurses.so.5 > to the manifest and started the job again. > We'll see... > > >> >> And yes It could also be that for some reason distro_const failed to >> copy libncurses to boot_archive. Also note that you will only hit that >> problem when solaris.zlib can not be loaded. i.e. CD-ROM not found or >> Netboot. >> > > Thanks for your help! > > Aurélien > >> >> Greetings >> Till >> >> On 24.10.18 13:45, Aurélien Larcher wrote: >>> Thanks for the help! >>> I am not sure what you meant by dependency to 32- and 64-bit bash since >> we >>> only have 64-bit. >>> Coud it just be a punctual problem with the image creation by >> distro_const? >>> I tested the 20181016 image at >>> >>> http://dlc-int.openindiana.org/users/aurelien/gcc-next/20181016/ >>> >>> without any problem on my machine and it should contain the same packages >>> aside from mate-system-monitor. >>> >>> I will re-run the image >> >> ___ >> 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] Upgraded to VirtualBox 5.2.20
On Wed, Oct 24, 2018 at 2:09 PM Till Wegmüller wrote: > It was a 32bit 64bit problem the last time I ran into it. Fact is the > boot archive is missing libraries in it's default configuration as it is > in slim_source repository and you will need to add those files to the > filelist. > I added usr/lib/64/libncurses.so.5 to the manifest and started the job again. We'll see... > > And yes It could also be that for some reason distro_const failed to > copy libncurses to boot_archive. Also note that you will only hit that > problem when solaris.zlib can not be loaded. i.e. CD-ROM not found or > Netboot. > Thanks for your help! Aurélien > > Greetings > Till > > On 24.10.18 13:45, Aurélien Larcher wrote: > > Thanks for the help! > > I am not sure what you meant by dependency to 32- and 64-bit bash since > we > > only have 64-bit. > > Coud it just be a punctual problem with the image creation by > distro_const? > > I tested the 20181016 image at > > > > http://dlc-int.openindiana.org/users/aurelien/gcc-next/20181016/ > > > > without any problem on my machine and it should contain the same packages > > aside from mate-system-monitor. > > > > I will re-run the image > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
It was a 32bit 64bit problem the last time I ran into it. Fact is the boot archive is missing libraries in it's default configuration as it is in slim_source repository and you will need to add those files to the filelist. And yes It could also be that for some reason distro_const failed to copy libncurses to boot_archive. Also note that you will only hit that problem when solaris.zlib can not be loaded. i.e. CD-ROM not found or Netboot. Greetings Till On 24.10.18 13:45, Aurélien Larcher wrote: > Thanks for the help! > I am not sure what you meant by dependency to 32- and 64-bit bash since we > only have 64-bit. > Coud it just be a punctual problem with the image creation by distro_const? > I tested the 20181016 image at > > http://dlc-int.openindiana.org/users/aurelien/gcc-next/20181016/ > > without any problem on my machine and it should contain the same packages > aside from mate-system-monitor. > > I will re-run the image ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
On Wed, Oct 24, 2018 at 12:49 PM Till Wegmüller wrote: > Usually if solaris.zlib (/usr) is found and mounted boot progresses > properly but this error usually means that it only booted into the > boot_archive and not mounted /usr. But to figure out why you'll need the > bash stuff in boot archive. > Thanks for the help! I am not sure what you meant by dependency to 32- and 64-bit bash since we only have 64-bit. Coud it just be a punctual problem with the image creation by distro_const? I tested the 20181016 image at http://dlc-int.openindiana.org/users/aurelien/gcc-next/20181016/ without any problem on my machine and it should contain the same packages aside from mate-system-monitor. I will re-run the image > > Greetings > Till > On 24.10.18 11:21, Aurélien Larcher wrote: > > Weird... I booted 20181016 in Virtualbox with the exact same manifest. > > What could be the difference? > > > > On 10/24/18, Till Wegmüller wrote: > >> Hi > >> > >> > >> On 24.10.18 08:06, Carl Brewer wrote: > Could you try to boot this? > > http://dlc-int.openindiana.org/users/aurelien/gcc-next/20181023/ > >>> > >>> It boots! > >>> > >>> gets stuck though, after boot : > >>> Console login service(s) cannot run > >>> . > >>> . > >>> . > >>> > >>> bash: fatal: libncurses.so.5 open failed, no such file or directory > >>> then some error about relocation in /usr/bin/bash: symbol PC: > referenced > >>> symbol not found > >> > >> That is a problem with the image building Process :) > >> > >> @Aurélien you will need to make sure to have both 32 and 64bit bash and > >> its dependencies in the files section when using distro_const > >> > >> The distro const files from the slim_source repo are incomplete. > >> > >> Greetings > >> Till > >> > >> ___ > >> 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 > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
On Wed, Oct 24, 2018 at 8:07 AM Carl Brewer wrote: > On 24/10/2018 8:06 AM, Aurélien Larcher wrote: > > On Tue, Oct 23, 2018 at 11:02 PM Carl Brewer > wrote: > > > >> On 24/10/2018 5:10 AM, Tim Mooney wrote: > >>> In regard to: Re: [OpenIndiana-discuss] Upgraded to VirtualBox > >> 5.2.20,...: > >>> > >>>> Hi, > >>>> > >>>> On 10/22/18 07:35 PM, russell wrote: > >>>>> Hi, > >>>>> > >>>>> Upgraded to VirtualBox 5.2.20 yesterday, this works fine on the BE > >>>>> completed on the 11th July but still get the lockup and reboot on any > >>>>> later BE. > >>>> > >>>> I know it bothers some of you guys, that VirtualBox does not work on > >>>> OpenIndiana anymore, but please take into account that VirtualBox is > >>>> meant for Oracle Solaris 11 and when it worked on illumos it was just > by > >>>> an accident. The more illumos diverges from Solaris heritage (and > >>>> mitigating Intel bugs in "helped" here a lot), the worst for > VirtualBox > >>>> on illumos. > >>>> > >>>> Those who can, please, don't hold your breath and consider migrating > >>>> to illumos KVM. This is in many respects saner, safer, and more > >>>> supportable solution moving forward. > >>> > >>> I know you're right, Michael. I'm one of the VB users that's been > >>> dragging my feet and hoping that a fix happens so that I can continue > to > >>> use VB. It's not because I'm in love with VirtualBox, just that I > >>> absolutely need a fully-functional Windows VM. > >> > >> I'm in the same boat. I've been running OI (well, OpenSolaris) since it > >> was first released, as a ZFS LAN fileserver and VirtualBox host, with a > >> gaggle of little VM's (Older NetBSD's, some newer CentOS) for over 10 > >> years, it's been mostly faultless and *easy* - VirtualBox's GUI is > >> great, it makes VM's trivial to install and manage for a guy like me who > >> just wants to spin up some VM's with minimal effort and have them Just > >> Work for most-any guest OS. > >> > >> The idea of having to learn yet another VM system .. gak .. that may or > >> may not support my older NetBSD VMs etc .. and doesn't appear to have a > >> nice GUI to drive it. > >> > >> But then, I need to replace my hardware as it's getting old, so I need > >> to install a newer openIndiana, which doesn't seem to work (yet) on > >> recent Coffee-Lake Gigabyte motherboards. At least I haven't yet been > >> able to get it to install. Sorry for the whiny rant :) > >> > > > > Could you try to boot this? > > > > http://dlc-int.openindiana.org/users/aurelien/gcc-next/20181023/ > > It boots! > Good to know! I will regenerate an image with Till's fix. > > gets stuck though, after boot : > Console login service(s) cannot run > . > . > . > > bash: fatal: libncurses.so.5 open failed, no such file or directory > then some error about relocation in /usr/bin/bash: symbol PC: referenced > symbol not found > > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
Usually if solaris.zlib (/usr) is found and mounted boot progresses properly but this error usually means that it only booted into the boot_archive and not mounted /usr. But to figure out why you'll need the bash stuff in boot archive. Greetings Till On 24.10.18 11:21, Aurélien Larcher wrote: > Weird... I booted 20181016 in Virtualbox with the exact same manifest. > What could be the difference? > > On 10/24/18, Till Wegmüller wrote: >> Hi >> >> >> On 24.10.18 08:06, Carl Brewer wrote: Could you try to boot this? http://dlc-int.openindiana.org/users/aurelien/gcc-next/20181023/ >>> >>> It boots! >>> >>> gets stuck though, after boot : >>> Console login service(s) cannot run >>> . >>> . >>> . >>> >>> bash: fatal: libncurses.so.5 open failed, no such file or directory >>> then some error about relocation in /usr/bin/bash: symbol PC: referenced >>> symbol not found >> >> That is a problem with the image building Process :) >> >> @Aurélien you will need to make sure to have both 32 and 64bit bash and >> its dependencies in the files section when using distro_const >> >> The distro const files from the slim_source repo are incomplete. >> >> Greetings >> Till >> >> ___ >> 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] Upgraded to VirtualBox 5.2.20
Weird... I booted 20181016 in Virtualbox with the exact same manifest. What could be the difference? On 10/24/18, Till Wegmüller wrote: > Hi > > > On 24.10.18 08:06, Carl Brewer wrote: >>> Could you try to boot this? >>> >>> http://dlc-int.openindiana.org/users/aurelien/gcc-next/20181023/ >> >> It boots! >> >> gets stuck though, after boot : >> Console login service(s) cannot run >> . >> . >> . >> >> bash: fatal: libncurses.so.5 open failed, no such file or directory >> then some error about relocation in /usr/bin/bash: symbol PC: referenced >> symbol not found > > That is a problem with the image building Process :) > > @Aurélien you will need to make sure to have both 32 and 64bit bash and > its dependencies in the files section when using distro_const > > The distro const files from the slim_source repo are incomplete. > > Greetings > Till > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
If it is the same issue as when I compiled it you need to remove a line in a makefile to skip a file that has no probe. On 10/24/18, Predrag Zečević - Technical Support Analyst wrote: > > > On 10/23/18 22:10, John D Groenveld wrote: >> In message >> , Tim >> Mooney writes: >>> 3) what other things are missing to bring KVM/QEMU to good feature >>> parity, >>> at least for Windows VMs, with VB? Anyone looked at USB passthrough? >>> How's audio support? Does a working libspice get us both shared >>> clipboard >>> and shared folders? >> >> Neither KVM nor bhyve support USB passthru. >> bhyve supports PCI passthru, but you would have to pass an entire >> USB add-on card to your guest. >> >> Shared folders can be solved with NFS and CIFS. >> >> >> BTW has anyone tried to port VBox to OI? >> Even without Oracle's proprietary bits it may be useful. >> It is for FreeBSD hosts and guests. >> >> John >> groenv...@acm.org > > I have tried to compile VirtualBox > (https://forums.virtualbox.org/viewtopic.php?f=40=89340), but was > stuck in dtrace probes failure. No support from VB guys can be expected... > > So, I have switched to KVM. Not ideal - but what choice I had IF I want > to keep OI (because native zfs support)? > > With best regards. > Predrag Zečević >> >> ___ >> openindiana-discuss mailing list >> openindiana-discuss@openindiana.org >> https://openindiana.org/mailman/listinfo/openindiana-discuss >> > > -- > 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 > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
Hi On 24.10.18 08:06, Carl Brewer wrote: >> Could you try to boot this? >> >> http://dlc-int.openindiana.org/users/aurelien/gcc-next/20181023/ > > It boots! > > gets stuck though, after boot : > Console login service(s) cannot run > . > . > . > > bash: fatal: libncurses.so.5 open failed, no such file or directory > then some error about relocation in /usr/bin/bash: symbol PC: referenced > symbol not found That is a problem with the image building Process :) @Aurélien you will need to make sure to have both 32 and 64bit bash and its dependencies in the files section when using distro_const The distro const files from the slim_source repo are incomplete. Greetings Till ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
On 10/23/18 22:10, John D Groenveld wrote: > In message , > Tim > Mooney writes: >> 3) what other things are missing to bring KVM/QEMU to good feature parity, >> at least for Windows VMs, with VB? Anyone looked at USB passthrough? >> How's audio support? Does a working libspice get us both shared clipboard >> and shared folders? > > Neither KVM nor bhyve support USB passthru. > bhyve supports PCI passthru, but you would have to pass an entire > USB add-on card to your guest. > > Shared folders can be solved with NFS and CIFS. > > > BTW has anyone tried to port VBox to OI? > Even without Oracle's proprietary bits it may be useful. > It is for FreeBSD hosts and guests. > > John > groenv...@acm.org I have tried to compile VirtualBox (https://forums.virtualbox.org/viewtopic.php?f=40=89340), but was stuck in dtrace probes failure. No support from VB guys can be expected... So, I have switched to KVM. Not ideal - but what choice I had IF I want to keep OI (because native zfs support)? With best regards. Predrag Zečević > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- 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
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
On 24/10/2018 8:06 AM, Aurélien Larcher wrote: On Tue, Oct 23, 2018 at 11:02 PM Carl Brewer wrote: On 24/10/2018 5:10 AM, Tim Mooney wrote: In regard to: Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20,...: Hi, On 10/22/18 07:35 PM, russell wrote: Hi, Upgraded to VirtualBox 5.2.20 yesterday, this works fine on the BE completed on the 11th July but still get the lockup and reboot on any later BE. I know it bothers some of you guys, that VirtualBox does not work on OpenIndiana anymore, but please take into account that VirtualBox is meant for Oracle Solaris 11 and when it worked on illumos it was just by an accident. The more illumos diverges from Solaris heritage (and mitigating Intel bugs in "helped" here a lot), the worst for VirtualBox on illumos. Those who can, please, don't hold your breath and consider migrating to illumos KVM. This is in many respects saner, safer, and more supportable solution moving forward. I know you're right, Michael. I'm one of the VB users that's been dragging my feet and hoping that a fix happens so that I can continue to use VB. It's not because I'm in love with VirtualBox, just that I absolutely need a fully-functional Windows VM. I'm in the same boat. I've been running OI (well, OpenSolaris) since it was first released, as a ZFS LAN fileserver and VirtualBox host, with a gaggle of little VM's (Older NetBSD's, some newer CentOS) for over 10 years, it's been mostly faultless and *easy* - VirtualBox's GUI is great, it makes VM's trivial to install and manage for a guy like me who just wants to spin up some VM's with minimal effort and have them Just Work for most-any guest OS. The idea of having to learn yet another VM system .. gak .. that may or may not support my older NetBSD VMs etc .. and doesn't appear to have a nice GUI to drive it. But then, I need to replace my hardware as it's getting old, so I need to install a newer openIndiana, which doesn't seem to work (yet) on recent Coffee-Lake Gigabyte motherboards. At least I haven't yet been able to get it to install. Sorry for the whiny rant :) Could you try to boot this? http://dlc-int.openindiana.org/users/aurelien/gcc-next/20181023/ It boots! gets stuck though, after boot : Console login service(s) cannot run . . . bash: fatal: libncurses.so.5 open failed, no such file or directory then some error about relocation in /usr/bin/bash: symbol PC: referenced symbol not found ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
On 24/10/2018 8:06 AM, Aurélien Larcher wrote: On Tue, Oct 23, 2018 at 11:02 PM Carl Brewer wrote: But then, I need to replace my hardware as it's getting old, so I need to install a newer openIndiana, which doesn't seem to work (yet) on recent Coffee-Lake Gigabyte motherboards. At least I haven't yet been able to get it to install. Sorry for the whiny rant :) Could you try to boot this? http://dlc-int.openindiana.org/users/aurelien/gcc-next/20181023/ Downloadimg, will give it a try thank you Carl ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
On Tue, Oct 23, 2018 at 11:02 PM Carl Brewer wrote: > On 24/10/2018 5:10 AM, Tim Mooney wrote: > > In regard to: Re: [OpenIndiana-discuss] Upgraded to VirtualBox > 5.2.20,...: > > > >> Hi, > >> > >> On 10/22/18 07:35 PM, russell wrote: > >>> Hi, > >>> > >>> Upgraded to VirtualBox 5.2.20 yesterday, this works fine on the BE > >>> completed on the 11th July but still get the lockup and reboot on any > >>> later BE. > >> > >> I know it bothers some of you guys, that VirtualBox does not work on > >> OpenIndiana anymore, but please take into account that VirtualBox is > >> meant for Oracle Solaris 11 and when it worked on illumos it was just by > >> an accident. The more illumos diverges from Solaris heritage (and > >> mitigating Intel bugs in "helped" here a lot), the worst for VirtualBox > >> on illumos. > >> > >> Those who can, please, don't hold your breath and consider migrating > >> to illumos KVM. This is in many respects saner, safer, and more > >> supportable solution moving forward. > > > > I know you're right, Michael. I'm one of the VB users that's been > > dragging my feet and hoping that a fix happens so that I can continue to > > use VB. It's not because I'm in love with VirtualBox, just that I > > absolutely need a fully-functional Windows VM. > > I'm in the same boat. I've been running OI (well, OpenSolaris) since it > was first released, as a ZFS LAN fileserver and VirtualBox host, with a > gaggle of little VM's (Older NetBSD's, some newer CentOS) for over 10 > years, it's been mostly faultless and *easy* - VirtualBox's GUI is > great, it makes VM's trivial to install and manage for a guy like me who > just wants to spin up some VM's with minimal effort and have them Just > Work for most-any guest OS. > > The idea of having to learn yet another VM system .. gak .. that may or > may not support my older NetBSD VMs etc .. and doesn't appear to have a > nice GUI to drive it. > > But then, I need to replace my hardware as it's getting old, so I need > to install a newer openIndiana, which doesn't seem to work (yet) on > recent Coffee-Lake Gigabyte motherboards. At least I haven't yet been > able to get it to install. Sorry for the whiny rant :) > Could you try to boot this? http://dlc-int.openindiana.org/users/aurelien/gcc-next/20181023/ > > I want ZFS, it's *the* filesystem. I want VirtualBox or something else > that works as well as it does in terms of ease of use - performance is > acceptable, I'm not thrashing filesystems etc. Maybe Solaris 11.4 is a > viable host? I dunno, after 30 years in this game in some form or > another, I'm tired of having to change things all the time to do the > same job! > > > > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- --- Praise the Caffeine embeddings ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
On 24/10/2018 5:10 AM, Tim Mooney wrote: In regard to: Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20,...: Hi, On 10/22/18 07:35 PM, russell wrote: Hi, Upgraded to VirtualBox 5.2.20 yesterday, this works fine on the BE completed on the 11th July but still get the lockup and reboot on any later BE. I know it bothers some of you guys, that VirtualBox does not work on OpenIndiana anymore, but please take into account that VirtualBox is meant for Oracle Solaris 11 and when it worked on illumos it was just by an accident. The more illumos diverges from Solaris heritage (and mitigating Intel bugs in "helped" here a lot), the worst for VirtualBox on illumos. Those who can, please, don't hold your breath and consider migrating to illumos KVM. This is in many respects saner, safer, and more supportable solution moving forward. I know you're right, Michael. I'm one of the VB users that's been dragging my feet and hoping that a fix happens so that I can continue to use VB. It's not because I'm in love with VirtualBox, just that I absolutely need a fully-functional Windows VM. I'm in the same boat. I've been running OI (well, OpenSolaris) since it was first released, as a ZFS LAN fileserver and VirtualBox host, with a gaggle of little VM's (Older NetBSD's, some newer CentOS) for over 10 years, it's been mostly faultless and *easy* - VirtualBox's GUI is great, it makes VM's trivial to install and manage for a guy like me who just wants to spin up some VM's with minimal effort and have them Just Work for most-any guest OS. The idea of having to learn yet another VM system .. gak .. that may or may not support my older NetBSD VMs etc .. and doesn't appear to have a nice GUI to drive it. But then, I need to replace my hardware as it's getting old, so I need to install a newer openIndiana, which doesn't seem to work (yet) on recent Coffee-Lake Gigabyte motherboards. At least I haven't yet been able to get it to install. Sorry for the whiny rant :) I want ZFS, it's *the* filesystem. I want VirtualBox or something else that works as well as it does in terms of ease of use - performance is acceptable, I'm not thrashing filesystems etc. Maybe Solaris 11.4 is a viable host? I dunno, after 30 years in this game in some form or another, I'm tired of having to change things all the time to do the same job! ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
In message <575245557.367344.1540325739...@mail.yahoo.com>, Apostolos Syropoulo s via openindiana-discuss writes: >PS I had tried KVM in the old times and it took me an eon to install >Windows 98... I manage a Samba-based Active Directory with a Windows 7 guest on top of Illumos KVM. Its usable for that purpose. Switching to a ZFS volume for guest storage seemed to help performance. I'll likely migrate the VM to bhyve when Omnios bumps to r151028 RSN. John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
>BTW has anyone tried to port VBox to OI? >Even without Oracle's proprietary bits it may be useful. >It is for FreeBSD hosts and guests. Someone did it a couple of years ago but now he has abandoned ship... I guess we could continue from where he left things... A.S. PS I had tried KVM in the old times and it took me an eon to install Windows 98... -- Apostolos Syropoulos Xanthi, Greece ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
In message , Tim Mooney writes: >3) what other things are missing to bring KVM/QEMU to good feature parity, >at least for Windows VMs, with VB? Anyone looked at USB passthrough? >How's audio support? Does a working libspice get us both shared clipboard >and shared folders? Neither KVM nor bhyve support USB passthru. bhyve supports PCI passthru, but you would have to pass an entire USB add-on card to your guest. Shared folders can be solved with NFS and CIFS. BTW has anyone tried to port VBox to OI? Even without Oracle's proprietary bits it may be useful. It is for FreeBSD hosts and guests. John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
The other wrinkle is that Illumos seems likely to move away from KVM to FreeBSD's bhyve since it is a much better fit for Illumos. See https://omniosce.org/info/bhyve for some info. Both KVM and bhyve seem to currently require Intel (not AMD) CPUs to work properly. Given that AMD is now competitive again with CPUs, and given that Joyent is working hard on bhyve, and given that Illumos and FreeBSD developers have a history of working together, it appears that bhyve will eventually dominate and KVM will eventually be deprecated. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
In regard to: Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20,...: Hi, On 10/22/18 07:35 PM, russell wrote: Hi, Upgraded to VirtualBox 5.2.20 yesterday, this works fine on the BE completed on the 11th July but still get the lockup and reboot on any later BE. I know it bothers some of you guys, that VirtualBox does not work on OpenIndiana anymore, but please take into account that VirtualBox is meant for Oracle Solaris 11 and when it worked on illumos it was just by an accident. The more illumos diverges from Solaris heritage (and mitigating Intel bugs in "helped" here a lot), the worst for VirtualBox on illumos. Those who can, please, don't hold your breath and consider migrating to illumos KVM. This is in many respects saner, safer, and more supportable solution moving forward. I know you're right, Michael. I'm one of the VB users that's been dragging my feet and hoping that a fix happens so that I can continue to use VB. It's not because I'm in love with VirtualBox, just that I absolutely need a fully-functional Windows VM. The only reason I can use OI as my $work desktop is that between OI and my Windows VM in VirtualBox, I can get all my work done. VB made it easy to have a Windows VM with a shared folder, USB passthrough, full audio support, etc. If that ever changes, and it's no longer possible for me to host a fully-functional Windows VM on OI, then I'll probably have to quit using OI at work. I haven't tried KVM/QEMU for a Windows VM yet, but I have been watching the discussion closely. The information that Predrag has shared and added to the wiki article makes it appear that KVM still has a ways to go before there would be feature parity for a Windows desktop VM. Would you say my interpretation is correct, or have I come to the wrong conclusion? Based on the wiki article, it appears that at least 1) shared clipboard doesn't work. I believe it was Alp that indicated that's because of missing libspice in OI. Has anyone ported or started working on porting libspice to OI? I took a look at that last night, and got past the struct socket issues (requires -D__XOPEN_SOURCE=600) and the missing SUN_LEN macro (needs code from sys/un.h), but I stopped when I hit the need for mremap(). Not sure what to do about that. 2) video display support maxed at 1024x768 in Predrag's tests. Any idea why that is, or how difficult that would be to improve? 3) what other things are missing to bring KVM/QEMU to good feature parity, at least for Windows VMs, with VB? Anyone looked at USB passthrough? How's audio support? Does a working libspice get us both shared clipboard and shared folders? Tim -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing & Infrastructure 701-231-1076 (Voice) Room 242-J6, Quentin Burdick Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgraded to VirtualBox 5.2.20
Hi, On 10/22/18 07:35 PM, russell wrote: Hi, Upgraded to VirtualBox 5.2.20 yesterday, this works fine on the BE completed on the 11th July but still get the lockup and reboot on any later BE. I know it bothers some of you guys, that VirtualBox does not work on OpenIndiana anymore, but please take into account that VirtualBox is meant for Oracle Solaris 11 and when it worked on illumos it was just by an accident. The more illumos diverges from Solaris heritage (and mitigating Intel bugs in "helped" here a lot), the worst for VirtualBox on illumos. Those who can, please, don't hold your breath and consider migrating to illumos KVM. This is in many respects saner, safer, and more supportable solution moving forward. As aside I also managed to get ESXi 6.5u2 (the last supported release for my CPUs) running within VirtualBox 5.2.20 as a VM, a 300GB IDE drive, 4 cpus and 4 Intel 82543GC (Pro/1000 T) interfaces. While the Intel 82545EM where identified correctly, no traffic was transferred. I tested latest OI on both VirtualBox 5.2.18 and ESXi 6.5, and the default Intel NIC and the default ESXi one, respectively, worked fine. Too much layers of virtualization I am afraid :). Michal Regards Russell ___ 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] Upgraded to VirtualBox 5.2.20
Hi, Upgraded to VirtualBox 5.2.20 yesterday, this works fine on the BE completed on the 11th July but still get the lockup and reboot on any later BE. As aside I also managed to get ESXi 6.5u2 (the last supported release for my CPUs) running within VirtualBox 5.2.20 as a VM, a 300GB IDE drive, 4 cpus and 4 Intel 82543GC (Pro/1000 T) interfaces. While the Intel 82545EM where identified correctly, no traffic was transferred. Regards Russell ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
