[OpenIndiana-discuss] VirtualBox 5.2.14 crashing when attempting to start VM

[Till Wegmüller]

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, 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 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
>>> <reboots>
>>
>> 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=fffffe426c6f2300 addr=fffffe426c6f2ea8
>> 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(13200000002, 2000ae41, 0, 202003, fffffea3a23ccad8,
>> fffffe426c6f2ea8)
>> spec_ioctl+0x60(fffffea3e4fa3880, 2000ae41, 0, 202003,
>> fffffea3a23ccad8, fffffe426c6f2ea8)
>> fop_ioctl+0x55(fffffea3e4fa3880, 2000ae41, 0, 202003,
>> fffffea3a23ccad8, fffffe426c6f2ea8)
>> 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 fffffffff7e7e000  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.
>