This repository has been archived by the owner on Jan 28, 2023. It is now read-only.
QEMU/haxm: Multiple segmentation faults on Ubuntu 18.04 #39
Labels
Comments
|
Seems to be some sort of race condition. If I remove the SMP option the failure sqeuence is a bit different, but it still crashes at the early beginning. |
|
Thanks for the bug report, as well as for all the other issues you've filed! We are busy with something else at the moment, but we'll start looking into these issues later this week. |
|
Ok, thanks for your update! |
|
Our QA has reproduced this issue, but we need more details about the segmentation fault, e.g. a core dump. Does the Ubuntu installer do that? Does it keep an installation log somewhere? |
|
On alt+F4 you get the current log. I think it writes a install log onto /var/log as well. |
|
You could try the hints shown in https://linux-audit.com/understand-and-configure-core-dumps-work-on-linux/ immediately after start (switch to alt-f2) |
|
Further insights: right after the message box, make a alt+f2, enter, find | grep /core . Sometimes there are error messages like "%s%s%s not found". Sometimes (seldom) it even crashes. Current bootline: I run: After a while (30 seconds to 2 minutes), I got a segmentation fault. I wrote the coredump with I packeted following things into https://mifritscher.de/austausch/_packet.zip :
I get the same symptoms also with only -smp 1 . |
|
Do you need any additional information? |
|
Sorry for the late response, and thanks a lot for providing the additional information. I tried to load the core dump ( Anything I did wrong? Meanwhile, the latest Android 4.9 kernel also runs into segfaults under HAXM: https://issuetracker.google.com/issues/78465772 I'm not sure if these two issues share the same root cause. But at least Android dumps more information about the crash, so maybe we should look into the Android issue first (and kill two birds with one stone, hopefully). |
|
Grml - ok, it seems that the file somehow got \r inserted... I hackfixed it and re-uploaded the file under https://mifritscher.de/austausch/test.core. Then, gdb can at least read the file: Sadly, the backtrace isn't such usefull, but the binaries are in the initramdisk. |
|
Regarding android: Yes, that could be an idea ;-) |
|
This issue looks similar with #74 . We are working on fix. |
junxiaoc
added a commit
that referenced
this issue
Jul 31, 2018
Guest OS kernel/app might use SSE instruction and registers. When Guest OS VMM exits, these registers should be saved, or else it might be corrupted by host OS/app. In next time guest VMM enter, guest's SSE registers context might be corrupted. Guest app segment fault, coredump, and kernel panic were reported which should be related with this issue. This change is to remove is_fpu_used flag so guest FPU registers could be saved in VM exit and restored in VM enter unconditionally. Fixes #39, fixes #74.
junxiaoc
added a commit
that referenced
this issue
Aug 1, 2018
Guest OS kernel/app might use SSE instruction and registers. When Guest OS VMM exits, these registers should be saved, or else it might be corrupted by host OS/app. In next time VM entry, guest's SSE registers context might be corrupted. Guest app segfault and kernel panic were reported which should be related with this issue. This change is to remove is_fpu_used flag so guest FPU registers could be saved in VM exit and restored in VM entry unconditionally. Fixes #39, fixes #74.
junxiaoc
added a commit
that referenced
this issue
Aug 1, 2018
Guest OS kernel/app might use SSE instruction and registers. When Guest OS VM exits, these registers should be saved, or else it might be corrupted by host OS/app. In next time VM entry, guest's SSE registers context might be corrupted. Guest app segfault and kernel panic were reported which should be related with this issue. This change is to remove is_fpu_used flag so guest FPU registers could be saved in VM exit and restored in VM entry unconditionally. Fixes #39, fixes #74.
junxiaoc
added a commit
that referenced
this issue
Aug 1, 2018
Guest OS kernel/app might use SSE instruction and registers. When Guest OS VM exits, these registers should be saved, or else it might be corrupted by host OS/app. In next time VM entry, guest's SSE registers context might be corrupted. Guest app segfault and kernel panic were reported which should be related with this issue. This change is to remove is_fpu_used flag so guest FPU registers could be saved in VM exit and restored in VM entry unconditionally. Fixes #39, fixes #74.
|
I can confirm that this issue is fixed with 7.3.2! Thanks! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
While installation of a Ubuntu 16.04 works fine with qemu 2.11 and haxm 7.1, 18.04 produces multiple user mode segmentation faults in the guest on early steps and eventually hangs. The netboot images can be obtained from http://de.archive.ubuntu.com/ubuntu/dists/artful/main/installer-amd64/current/images/netboot/netboot.tar.gz .
Parameters:
-m 1024 -smp 2 -rtc base=utc -drive file=temp.vmdk,if=virtio,detect-zeroes=unmap,discard=unmap -drive file=fat:rw:fat-type=32:label=kernel:C:\temp,format=raw,if=virtio -vga std -device virtio-net,netdev=natted -netdev user,id=natted -kernel linux_initrd/linux -initrd linux_initrd/initrd.gz -append "nofb fb=false pti=off interface=auto auto=true" -nodefaultsThe text was updated successfully, but these errors were encountered: