qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
To: qemu-devel@nongnu.org, Will Gyda <vilhelmgyda@gmail.com>
Cc: qemu-trivial@nongnu.org, philmd@linaro.org, pbonzini@redhat.com,
	richard.henderson@linaro.org, eduardo@habkost.net,
	Will Gyda <vilhelmgyda@gmail.com>
Subject: Re: [PATCH] Issue #2294 | Machine microvm doesn't run under Xen accel for x86_64
Date: Wed, 29 May 2024 13:12:39 +0300	[thread overview]
Message-ID: <e8t34.08zb3hciwfl@linaro.org> (raw)
In-Reply-To: <20240528102339.106257-1-vilhelmgyda@gmail.com>

On Tue, 28 May 2024 13:23, Will Gyda <vilhelmgyda@gmail.com> wrote:
>Issue #2294: Machine microvm doesn't run under Xen accel for qemu-system-x86_64. 
>Solution: microvm is now not build if only Xen is available.
>
>Signed-off-by: Will Gyda <vilhelmgyda@gmail.com>
>


I suggest rewording the commit title to something like

"i386: remove microvm from default build"

And adding a commit message that explains that the microvm does not work 
on Xen, hence if only Xen is available it should not be built.

Also, you can add a

Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2294

line before your Signed-off-by. See 
https://www.qemu.org/docs/master/devel/submitting-a-patch.html

But, seeing the issue itself, it's about the microvm being stuck under 
Xen. So the commit that resolves this would either make it non-stuck or 
make it impossible to start the vm to begin with.


>---
> configs/devices/i386-softmmu/default.mak | 2 +-
> hw/i386/Kconfig                          | 2 ++
> 2 files changed, 3 insertions(+), 1 deletion(-)
>
>diff --git a/configs/devices/i386-softmmu/default.mak b/configs/devices/i386-softmmu/default.mak
>index 598c6646df..6a73aee7dd 100644
>--- a/configs/devices/i386-softmmu/default.mak
>+++ b/configs/devices/i386-softmmu/default.mak
>@@ -29,4 +29,4 @@
> CONFIG_ISAPC=y
> CONFIG_I440FX=y
> CONFIG_Q35=y
>-CONFIG_MICROVM=y
>+#CONFIG_MICROVM=n

Better remove this altogether since it's not a default anymore.

>diff --git a/hw/i386/Kconfig b/hw/i386/Kconfig
>index a6ee052f9a..f8ec8ebd7a 100644
>--- a/hw/i386/Kconfig
>+++ b/hw/i386/Kconfig
>@@ -108,6 +108,8 @@ config Q35
> 
> config MICROVM
>     bool
>+    default y
>+    depends on KVM || WHPX || NVMM || HVF

What about TCG? Will it be available if we only build with tcg?

>     select SERIAL_ISA # for serial_hds_isa_init()
>     select ISA_BUS
>     select APIC
>-- 
>2.25.1
>
>


  parent reply	other threads:[~2024-05-29 10:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28 10:23 [PATCH] Issue #2294 | Machine microvm doesn't run under Xen accel for x86_64 Will Gyda
2024-05-29  7:07 ` Paolo Bonzini
2024-05-29  8:24   ` Vilhelm Gyda
2024-05-29 10:09     ` Manos Pitsidianakis
2024-05-29 10:12 ` Manos Pitsidianakis [this message]
2024-05-29 10:56   ` Vilhelm Gyda

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e8t34.08zb3hciwfl@linaro.org \
    --to=manos.pitsidianakis@linaro.org \
    --cc=eduardo@habkost.net \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=vilhelmgyda@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).