Yes, I am clear on this Dexuan. Had found the same info tonight,
including the table of causes of VM exit. The issue is not the VM exit
itself, it is that hyperv adversely affects the 32 bit programs state.
Please keep posting the progress on fixing the issue if you could as
this goes along.
Thanks Dexuan. I realized later and clarified my Q on the thread,
suggesting the experiment I mentioned. I have not tried it, but anyway
you guys are now zeroing in on the issue.
On Wednesday, December 16, 2020, 6:30:48 PM PST, Dexuan Cui
<1904...@bugs.launchpad.net> wrote:
VM Exit is a
Hi Dexuan,
To clarify my question: What is the cause of the VMexit (ie. trap to the
hyperv) in this scenario?
It might be worth it to do an experiment and reverse the order of
operations i.e. first start the hello program in a loop and THEN start
the nested VM via KVM. Then it would be the
Thank you Dexuan. What does VMexit mean here please? Trying to see how
the VM exit triggers a kernel panic, since we were just running a 32 bit
hello world program, which should not cause a the host VM to "exit".
Regards.
On Wednesday, December 16, 2020, 5:11:37 PM PST, Dexuan Cui
Hi Marcelo,
This issue can also been seen on the latest Ubuntu 18.04 image. It is also seen
in the 5.10-rc7 Linux kernel as well as 5.4.
The issue can be reproduced 100% of the time using a more simple setup as
described below. A basic "hello world" C program compiled for 32 bit crashes
the
Version info about the Azure Ubuntu Host VM:
root@vm-5:~# uname -a
Linux vm-5 4.15.18+test #1 SMP Mon Oct 29 03:40:39 UTC 2018 x86_64 x86_64
x86_64 GNU/Linux
root@vm-5:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.5 LTS
Release:18.04
Public bug reported:
Running a container on an DV3 Standard_D8_v3 Azure host, as the
container comes up, the Azure host VM kernel panics per the logs below.
Isolated the issue to a process in the container which uses the virtual
NICs available on the Azure host. The container also is running
7 matches
Mail list logo
