On 08/14/18 10:22, Till Wegmüller wrote:
Can you boot the VM's with Qemu?
I doubt Bugs in June are affecting that Issue given that a Patch level
from 12th July still works.
Hi all,
I have moved from VirtualBox to KVM and updated wiki page:
na-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,
>&
Ticket created
https://www.illumos.org/issues/9761
Greetings
Till
On 8/22/18 3:35 PM, Predrag Zečević - Technical Support Analyst wrote:
> 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
Hi
I get the same result on my machine illumos-49714e869e
Syscall 177 which is at the bottom of the stack is munmap. So my
assumption is there was a bug introduced in KVM some tima ago.
I have also tested disabling KPTI with no luck. so it's not that.
Greetings
Till
On 8/22/18 3:35 PM,
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
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
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
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 perfo
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
On 08/14/18 10:45, Till Wegmüller wrote:
On 14.08.2018 10:28, Predrag Zečević - Technical Support Analyst wrote:
Did the Workaround work?
Yes, we have added it to wiki
we have had similar case in the past, and workaround was found:
* https://www.illumos.org/issues/6919#note-7
* that was
On 14.08.2018 10:28, Predrag Zečević - Technical Support Analyst wrote:
>> Did the Workaround work?
> Yes, we have added it to wiki
we have had similar case in the past, and workaround was found:
* https://www.illumos.org/issues/6919#note-7
* that was added to wiki too:
>>
On 08/14/18 10:22, Till Wegmüller wrote:
Hi
Are you trying to boot 32-bit VM's?
Nope.
Or is Virtualbox still part 32bit?
No:
/opt/VirtualBox/amd64/VBoxSVC: ELF 64-bit LSB executable, x86-64,
version 1 (Solaris), dynamically linked, interpreter
/usr/lib/amd64/ld.so.1, stripped, uses SSE
Hi
Are you trying to boot 32-bit VM's?
Or is Virtualbox still part 32bit?
The referenced Bug mentions that only 32bit VM's are affected.
Can you boot the VM's with Qemu?
I doubt Bugs in June are affecting that Issue given that a Patch level
from 12th July still works.
What type of VM's are
On 08/06/18 12:36, Predrag Zečević - Technical Support Analyst wrote:
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
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
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
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
What is the last successful version of Vbox you have used on OI.
I use VBox 5.0.x on OmniOS.
The last time I tried anything newer there were issues.
Geoff
On 2018-07-24 11:15 AM, russell wrote:
Hi,
After upgrading to the latest hipster on the 22nd July I did not
attempt to start any VMs
18 matches
Mail list logo
