The guest OS is up and running. It runs already workloads. The nested virt
works well mostly of the time.
On Sat, 30 Jan 2021 14:28:08 +0100
Salvatore Mazzarino wrote:
> I'm running QEMU v4.2.0 inside a Docker container. The Docker container runs
> on a VMware VM running Flatcar Linux OS with kernel version 5.4.92. It
> happens that the QEMU process starts to show up an high usage of CPU. The
> CP
Yes. This is definitely in my radar. But just in case it won't be solved, what
would you propose here? Which would be your debugging strategy that you
propose? Which function would you look at the tracing?
On Sat, 30 Jan 2021 at 13:43, Salvatore Mazzarino
wrote:
> I'm running QEMU v4.2.0 inside a Docker container. The Docker container runs
> on a VMware VM running Flatcar Linux OS with kernel version 5.4.92. It
> happens that the QEMU process starts to show up an high usage of CPU. The
> CPUs tha
I'm running QEMU v4.2.0 inside a Docker container. The Docker container runs on
a VMware VM running Flatcar Linux OS with kernel version 5.4.92. It happens
that the QEMU process starts to show up an high usage of CPU. The CPUs that the
Qemu process uses go into saturation and the guest OS runnin
Greetings,
I was wondering how qemu generates the path for edk2-x86_64-code.fd from from
60-edk2-x86_64.json
the file contains this: "filename": "share/qemu/edk2-x86_64-code.fd",
however the real path is /usr/share/qemu/edk2-x86_64-code.fd.
where does the /usr prefix comes?
the reason I'm asking
