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
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&t=89340), but was
> >> stuck in dtrace probes failure. No support
On Sun, 28 Oct 2018, Aurélien Larcher wrote:
I have tried to compile VirtualBox
(https://forums.virtualbox.org/viewtopic.php?f=40&t=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 il
> I have tried to compile VirtualBox
> (https://forums.virtualbox.org/viewtopic.php?f=40&t=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 s
От: 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
>
> lrwxr
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-
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
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)
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/libncurse
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 u
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 l
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
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-disc
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:
> We
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/
>>
>> I
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 thin
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 su
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 sh
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
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
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:
> &
On Tue, Oct 23, 2018 at 10:16 PM Apostolos Syropoulos via
openindiana-discuss wrote:
>
> >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 s
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
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 f
>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
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
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 comp
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
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 plea
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
dri
30 matches
Mail list logo