Hi Paolo,
> > > The biggest problem I'm seeing is we no longer support 64-bit guests
on
> > > 32-bit hosts, and don't plan to revert that.
> >
> > Yes, so the sixth patch ("[PATCH 06/10] include/exec: Allow using 64bit
> > guest addresses on emscripten") should be considered as a temporary
> > wor
Qemu's attempts to learn whether a destination file starts life with
all zero contents are just a hueristic. There may be cases where the
caller is aware of information that qemu cannot learn quickly, in
which case telling qemu what to assume about the destination can make
the mirror operation fas
On 08/04/2025 17.55, Zhuoying Cai wrote:
The `-secure-boot on|off` command line option is implemented
to enable secure IPL.
By default, -secure-boot is set to false if not specified in
the command line.
Signed-off-by: Zhuoying Cai
---
qemu-options.hx | 8
system/vl.c | 21
On 11/4/25 15:42, Daniel P. Berrangé wrote:
On Sat, Feb 08, 2025 at 12:57:23PM -0800, Richard Henderson wrote:
For system mode, we can rarely support the amount of RAM that
the guest requires. TCG emulation is restricted to round-robin
mode, which solves many of the atomicity issues, but not tho
On Fri, Apr 11, 2025 at 05:05:20PM +0200, Philippe Mathieu-Daudé wrote:
> On 11/4/25 15:42, Daniel P. Berrangé wrote:
> > On Sat, Feb 08, 2025 at 12:57:23PM -0800, Richard Henderson wrote:
> > > For system mode, we can rarely support the amount of RAM that
> > > the guest requires. TCG emulation is
Hi Daniel,
> On Wed, Apr 09, 2025 at 03:21:15PM -0400, Stefan Hajnoczi wrote:
> > On Mon, Apr 07, 2025 at 11:45:51PM +0900, Kohei Tokunaga wrote:
> > > This patch series enables QEMU's system emulator to run in a browser
using
> > > Emscripten.
> > > It includes implementations and workarounds to
On 4/11/25 07:36, Kohei Tokunaga wrote:
Hi Pierrick, thank you for the feedback.
> first, congrats for this work!
> It would be really nice to have this available upstream, starting with a
> modest TCI port, before having the tcg backend also.
Sure, I'll split the patch series, starting with
On 4/11/25 10:46 AM, Thomas Huth wrote:
On 08/04/2025 17.55, Zhuoying Cai wrote:
The IPL Information Report Block (IIRB) immediately follows the IPL
Parameter Block (IPLB).
The IPLB struct is allocated 4KB in memory, and iplb->len indicates
the amount of memory currently used by the IPLB.
T
On 10/4/25 23:00, Pierrick Bouvier wrote:
Allow to call that function easily several times in next commit.
Signed-off-by: Pierrick Bouvier
---
target/arm/ptw.c | 24 ++--
1 file changed, 14 insertions(+), 10 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé
On 11/4/25 00:55, Pierrick Bouvier wrote:
Pierrick Bouvier (2):
system/main: transfer replay mutex ownership from main thread to main
loop thread
tests/functional/test_aarch64_replay: reenable on macos
Series:
Tested-by: Philippe Mathieu-Daudé
On Fri, Apr 11, 2025 at 02:54:29PM +0100, Daniel P. Berrangé wrote:
> On Tue, Apr 08, 2025 at 01:25:04PM +0200, Juraj Marcin wrote:
> > From: Juraj Marcin
> >
> > With the default TCP stack configuration, it could be even 2 hours
> > before the connection times out due to the other side not being
Hello Jamin
On 4/10/25 04:38, Jamin Lin wrote:
v1:
Add initial support for AST27x0
The purpose of vbootrom here is to simulate the work of BootMCU SPL (riscv)
in AST2700, because QEMU doesn't support heterogenous architecture yet.
ast27x0_bootrom.bin is a simplified, free (Apache 2.
On 4/10/25 04:38, Jamin Lin wrote:
Move the declaration of `rom_size` to an outer scope in aspeed_machine_init()
so it can be reused for setting up the vbootrom region as well.
This avoids introducing a redundant local variable and ensures consistent
ROM sizing logic when both SPI boot and vboot
On 4/10/25 04:38, Jamin Lin wrote:
Introduce a new vbootrom memory region. The region is mapped at address
"0x" and has a size of 128KB, identical to the SRAM region size.
This memory region is intended for loading a vbootrom image file as part of the
boot process.
The vbootrom region is
On 4/10/25 04:38, Jamin Lin wrote:
Refactor the AST2700 functional test to boot using the vbootrom image
instead of manually loading boot components with -device loader.
The boot ROM binary is now passed via the
-bios option, using the image located in pc-bios/ast27x0_bootrom.bin.
Signed-off-by:
On 4/10/25 04:38, Jamin Lin wrote:
The variable "sram_name" was only used for naming the SRAM memory region.
Rename it to "name" for consistency with similar code and avoid unnecessary
new local variable declarations.
Signed-off-by: Jamin Lin
Reviewed-by: Cédric Le Goater
Thanks,
C.
--
On 4/10/25 04:38, Jamin Lin wrote:
The boot ROM is a minimal implementation designed to load an AST27x0 boot image.
Its source code is available at:
https://github.com/google/vbootrom
See commit d1cb5eda67a0 ("roms: Add virtual Boot ROM for NPCM7xx SoCs")
for an example adding a ROM file.
Also
On Tue, Apr 08, 2025 at 04:30:38PM +0530, prashant patil wrote:
> Thank you, Eric, for the thorough information—truly appreciate it.
>
> Just to confirm what I understood, when we are reading a bitmap with
> 'x-dirty-bitmap' (for powered on vm of course), the 'start' is always a
> logical offset
On 4/10/25 04:38, Jamin Lin wrote:
Introduce "aspeed_load_vbootrom()" to support loading a virtual boot ROM image
into the vbootrom memory region, using the "-bios" command-line option.
Signed-off-by: Jamin Lin
---
hw/arm/aspeed.c | 32
1 file changed, 32 ins
On Tue, Apr 08, 2025 at 01:25:03PM +0200, Juraj Marcin wrote:
> From: Juraj Marcin
>
> Commit aec21d3175 (qapi: Add InetSocketAddress member keep-alive)
> introduces the keep-alive flag, which enables the SO_KEEPALIVE socket
> option, but only on client-side sockets. However, this option is also
On Mon, Apr 07, 2025 at 08:47:30AM -0700, Pinku Deb Nath wrote:
> Full Unit Access (FUA) is an optimization where a disk write with the
> flag set will be persisted to disk immediately instead of potentially
> remaining in the disk's write cache.
>
> This commit address the todo task
> for using p
On Wed, Apr 09, 2025 at 02:29:13PM -0400, Stefan Hajnoczi wrote:
> Populate the pdiscard_alignment block limit so the block layer is able
> align discard requests correctly.
>
> Signed-off-by: Stefan Hajnoczi
> ---
> block/file-posix.c | 56 +-
> 1 fil
On 4/11/25 06:44, Philippe Mathieu-Daudé wrote:
On 10/4/25 23:00, Pierrick Bouvier wrote:
We'll reuse this function later.
Signed-off-by: Pierrick Bouvier
---
target/arm/ptw.c | 21 ++---
1 file changed, 14 insertions(+), 7 deletions(-)
diff --git a/target/arm/ptw.c b/tar
Hi Pierrick, thank you for the feedback.
> first, congrats for this work!
> It would be really nice to have this available upstream, starting with a
> modest TCI port, before having the tcg backend also.
Sure, I'll split the patch series, starting with the TCI port.
> Do you have recent informat
On Fri, Apr 11, 2025 at 10:18:55AM +0200, Hanna Czenczek wrote:
> > if (ret && ret != -ENOTSUP) {
> > -goto out;
> > +if (ret == -EINVAL && (offset % align != 0 || num % align !=
> > 0)) {
>
> Could use `(offset | num) % align != 0`, but either way:
Use of | and
On 4/11/25 10:38 AM, Thomas Huth wrote:
> On 08/04/2025 17.55, Zhuoying Cai wrote:
>> From: Collin Walling
>>
>> DIAG 508 subcode 2 performs signature-verfication on signed components.
>> A signed component may be a Linux kernel image, or any other signed
>> binary. **Verification of initrd is not
On 4/8/2025 8:55 AM, Zhuoying Cai wrote:
DIAG 320 subcode 1 provides information needed to determine
the amount of storage to store one or more certificates.
The subcode value is denoted by setting the left-most bit
of an 8-byte field.
The verification-certificate-storage-size block (VCSSB) c
On 4/11/25 8:57 AM, Daniel P. Berrangé wrote:
> On Fri, Apr 11, 2025 at 12:44:17PM +0200, Thomas Huth wrote:
>> On 08/04/2025 17.55, Zhuoying Cai wrote:
>>> The `-boot-certificates /path/dir:/path/file` option is implemented
>>> to provide path to either a directory or a single certificate.
>>>
>
On Fri, Sep 13, 2024 at 07:39:35PM +0300, Andrey Drobyshev wrote:
> Move the definition from iotests/250 to common.rc. This is used to
> detect real disk usage of sparse files. In particular, we want to use
> it for checking subclusters-based discards.
>
> Signed-off-by: Andrey Drobyshev
> Revi
On Fri, Apr 11, 2025 at 13:43:39 +0200, Markus Armbruster wrote:
> Daniel P. Berrangé writes:
> > On Fri, Apr 11, 2025 at 12:40:46PM +0200, Markus Armbruster wrote:
> >> Daniel P. Berrangé writes:
> >> > Considering the bigger picture QMP design, when libvirt is trying to
> >> > understand QEMU's
On Fri, Apr 11, 2025 at 11:09 AM Daniel P. Berrangé wrote:
>
> On Fri, Apr 11, 2025 at 05:05:20PM +0200, Philippe Mathieu-Daudé wrote:
> > On 11/4/25 15:42, Daniel P. Berrangé wrote:
> > > On Sat, Feb 08, 2025 at 12:57:23PM -0800, Richard Henderson wrote:
> > > > For system mode, we can rarely sup
On Fri, Apr 11, 2025 at 04:25:10PM +1000, Nicholas Piggin wrote:
> On Wed Apr 2, 2025 at 5:17 AM AEST, Corey Minyard wrote:
> > On Wed, Apr 02, 2025 at 12:01:47AM +1000, Nicholas Piggin wrote:
> >> These little things came up when looking at behaviour of IPMI with
> >> the bmc-sim implementation ru
On 4/11/25 9:43 AM, Thomas Huth wrote:
> On 08/04/2025 17.55, Zhuoying Cai wrote:
>> From: Collin Walling
> ...
>> Signed-off-by: Zhuoying Cai
>
> So the patch is from Collin, but S-o-b only by you? Looks weird, this should
> either have an additional S-o-b by Collin, too, or not have that "Fro
...snip...
diff --git a/include/hw/s390x/ipl/qipl.h b/include/hw/s390x/ipl/qipl.h
index b8e7d1da71..2355fcecbb 100644
--- a/include/hw/s390x/ipl/qipl.h
+++ b/include/hw/s390x/ipl/qipl.h
@@ -23,6 +23,9 @@
#define MAX_CERTIFICATES 64
#define CERT_MAX_SIZE (1024 * 8)
+#define DIAG308_
The tls_creds, tls_authz and tls_hostname arguments are strings that
can be set by the user. They are allowed to be either a valid string,
an empty string or NULL. The values "" and NULL are effectively
treated the same by the code, but this is not entirely clear because
the handling is not uniform
Some migration parameters are updated immediately once they are set
via migrate-set-parameters. Move that work outside of
migrate_params_apply() and leave that function with the single
responsibility of setting s->parameters and not doing any
side-effects.
Signed-off-by: Fabiano Rosas
---
migrat
The migration parameters validation involves producing a temporary
structure which merges the current parameter values with the new
parameters set by the user.
The has_ boolean fields of MigrateSetParameter are taken into
consideration when writing the temporary structure, however the copy
of the
While validating migration parameters, a temporary structure is used
to apply the values to be validated. Only when validation succeeds on
the temporary values, they are actually copied into the internal
s->parameters.
There is however an extra step, which is to copy s->parameters into
the tempora
Continuing with the removal of parameters and capabilities, replace
the internal usage of s->capabilities with MigrationConfig.
To keep compatibility with the special format of the user-facing
migrate-set-capabilities and query-migrate-capabilities, introduce a
few compatibility routines to conver
The concepts of 'parameters' and 'capabilities' are almost
functionally identical and there is a consensus that their usage is
confusing, particularly when it comes to determine to which category a
new option should belong.
The new MigrationConfig type was introduced to eliminate the
distinction b
Since parameters and capabilities are now stored in the same structure
and both use the same method to validate the input (i.e. copy, set a
temporary, validate the temporary and overwrite), it's possible to use
the same routine for both.
With this all distinction from capabilities and parameters i
Allow the migrate and migrate_incoming commands to pass the migration
configuration options all at once, dispensing the use of
migrate-set-parameters and migrate-set-capabilities.
The motivation of this is to simplify the interface with the
management layer and avoid the usage of several command i
Now that we're removing mentions of 'parameters' from migration code,
the "Parameter X expects..." message is a little confusing, although
the "parameter" there refers to the QMP command parameter. There's
also some instances which don't make sense grammatically.
Remove all the usage of QERR_INVAL
Hi everyone, I did a cleanup (if it can be called that) of the user
input validation for capabilities and parameters and turned the two
concepts into a single 'options' to be stored in a MigrationConfig
object.
RFC mostly because this idea exposes (pre-existing) issues around how
to validate capab
From: Markus Armbruster
migrate_params_test_apply() neglects to apply tls_authz. Currently
harmless, because migrate_params_check() doesn't care. Fix it anyway.
Signed-off-by: Markus Armbruster
Reviewed-by: Fabiano Rosas
Message-ID: <20250407072833.2118928-1-arm...@redhat.com>
Signed-off-by:
Introduce a new MigrationConfigBase, to allow most of the duplication
in migration.json to be eliminated.
The reason we need MigrationParameters and MigrationSetParameters is
that the internal parameter representation in the migration code, as
well as the user-facing return of query-migrate-parame
Fabiano Rosas writes:
> Fabiano Rosas writes:
>
> +Cc Markus
>
> context:
> This series was trying to stop savevm from crashing when arbitrary
> migration capabilities are enabled. Daniel brought up the previous
> discussion around unifying capabilities + parameters and passing it all
> via the
On 08/04/2025 17.55, Zhuoying Cai wrote:
The IPL Information Report Block (IIRB) immediately follows the IPL
Parameter Block (IPLB).
The IPLB struct is allocated 4KB in memory, and iplb->len indicates
the amount of memory currently used by the IPLB.
To ensure proper alignment of the IIRB and pr
Add a new migration structure to consolidate the capabilities and
parameters. This structure will be used in place of the s->parameters
and s->capabilities data structures in the next few patches.
The QAPI migration types now look like this:
/* options previously known as parameters */
{ 'struct'
Add the QMP commands query-migrate-config and migrate-set-config to
read and write the migration configuration options.
Signed-off-by: Fabiano Rosas
---
migration/options.c | 24
migration/options.h | 2 +-
qapi/migration.json | 42 ++
On 11.04.25 04:04, Eric Blake wrote:
When doing a sync=full mirroring, QMP drive-mirror requests full
zeroing if it did not just create the destination, and blockdev-mirror
requests full zeroing unconditionally. This is because during a full
sync, we must ensure that the portions of the disk tha
The ACPI sleep button can be implemented as a fixed hardware button
or Control Method Sleep button.
The patch of implementing a fixed hardware sleep button was posted
here 1). More discussions can be found here 2). Essentially, the
discussion mainly focuses on whether the sleep button is implement
On Thu, Apr 10, 2025 at 08:04:50PM -0500, Eric Blake wrote:
> When mirroring images, it makes sense for the destination to be sparse
> even if it was not connected with "discard":"unmap"; the only time the
> destination should be fully allocated is if the user pre-allocated it,
> or if the source w
The fixed hardware sleep button isn't appropriate for hardware
reduced platform. This patch implements the control method sleep
button in a separate source file so that the button can be added
for various platforms.
Co-developed-by: Miguel Luis
Signed-off-by: Annie Li
---
hw/acpi/control_method
list changed files in tests/qtest/bios-tables-test-allowed-diff.h
Signed-off-by: Annie Li
---
tests/qtest/bios-tables-test-allowed-diff.h | 42 +
1 file changed, 42 insertions(+)
diff --git a/tests/qtest/bios-tables-test-allowed-diff.h
b/tests/qtest/bios-tables-test-allowed
Add Control Method Sleep button and its GPE event handler for
x86 platform. The GPE event handler notifies OSPM when the
Sleep button event is triggered.
Signed-off-by: Annie Li
---
hw/i386/acpi-build.c | 22 +-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/hw
Following is the diff generated by the step 5 and 6 in
tests/qtest/bios-tables-test.c
Diff from iasl to show changes in DSDT table:
--- /tmp/asl-34PV42.dsl 2025-04-09 19:04:34.846646690 +
+++ /tmp/asl-5XBW42.dsl 2025-04-09 19:04:34.839646378 +
@@ -1,30 +1,30 @@
/*
* Intel ACPI Componen
The GPE event is triggered to notify x86 guest to suppend
itself. The function acpi_send_sleep_event will also
trigger GED events on HW-reduced systems where ACPI GED
sleep event is supported.
Signed-off-by: Annie Li
---
hw/acpi/core.c | 10 ++
include/hw/acpi/acpi.
list changed files in tests/qtest/bios-tables-test-allowed-diff.h
Signed-off-by: Annie Li
---
tests/qtest/bios-tables-test-allowed-diff.h | 5 +
1 file changed, 5 insertions(+)
diff --git a/tests/qtest/bios-tables-test-allowed-diff.h
b/tests/qtest/bios-tables-test-allowed-diff.h
index dfb8
Add the support of control method sleep button and System
S3 Sleeping State for microvm.
Signed-off-by: Annie Li
---
hw/i386/acpi-microvm.c | 11 +++
include/hw/acpi/generic_event_device.h | 1 +
2 files changed, 12 insertions(+)
diff --git a/hw/i386/acpi-microvm.c b/hw
From: Miguel Luis
Add support for ACPI GED sleep event on the ACPI device
interface so that HW-reduced systems can enable guests
to sleep.
Signed-off-by: Miguel Luis
Signed-off-by: Annie Li
---
hw/acpi/generic_event_device.c | 9 +
include/hw/acpi/generic_event_device.h | 1 +
The sleep GED event is enabled for MicroVM. Also, the system
suspend is enabled when the GED register is set for sleep.
Signed-off-by: Annie Li
---
hw/i386/microvm.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/hw/i386/microvm.c b/hw/i386/microvm.c
index d0a236c74f..eba3
Following is the diff generated by the step 5 and 6 in
tests/qtest/bios-tables-test.c
Diff from iasl to show changes in DSDT table:
--- /tmp/asl-2F0N42.dsl 2025-04-11 12:50:02.892883467 +
+++ /tmp/asl-C81N42.dsl 2025-04-11 12:50:02.890883378 +
@@ -1,30 +1,30 @@
/*
* Intel ACPI Componen
Once the microvm guest requests to go to sleep state and
sets the GED register with S3 type, QEMU needs to continue
suspending the system.
Signed-off-by: Annie Li
---
hw/acpi/generic_event_device.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/hw/acpi/generic_event_device.c b/hw/acpi/ge
The function qemu_wakeup_suspend_enabled combines the suspend
and wakeup together. However, the microvm doesn't support
wakeup yet. Suspend is enabled here, but wakeup doesn't
actually work for microvm now.
Signed-off-by: Annie Li
---
hw/i386/microvm.c | 1 +
1 file changed, 1 insertion(+)
diff
Followng hmp/qmp commands are implemented for pressing virtual
sleep button,
hmp: system_sleep
qmp: { "execute": "system_sleep" }
These commands put the guest into suspend or other power states
depending on the power settings inside the guest.
These hmp/qmp command are in '*_*' format, it is int
Hello,
On behalf of the QEMU Team, I'd like to announce the availability of the
fourth release candidate for the QEMU 10.0 release. This release is meant
for testing purposes and should not be used in a production environment.
http://download.qemu.org/qemu-10.0.0-rc3.tar.xz
http://download.qe
On Thu, 10 Apr 2025 09:07:51 -0700
Farhan Ali wrote:
> On 4/3/2025 2:24 PM, Alex Williamson wrote:
> > On Thu, 3 Apr 2025 13:33:17 -0700
> > Farhan Ali wrote:
> >
> >> On 4/3/2025 11:05 AM, Alex Williamson wrote:
> >>> On Thu, 3 Apr 2025 10:33:52 -0700
> >>> Farhan Ali wrote:
> >>>
> >
On 4/11/2025 3:28 PM, Alex Williamson wrote:
On Thu, 10 Apr 2025 09:07:51 -0700
Farhan Ali wrote:
On 4/3/2025 2:24 PM, Alex Williamson wrote:
On Thu, 3 Apr 2025 13:33:17 -0700
Farhan Ali wrote:
On 4/3/2025 11:05 AM, Alex Williamson wrote:
On Thu, 3 Apr 2025 10:33:52 -0700
Farhan Ali
On Sat Apr 12, 2025 at 4:20 AM AEST, Corey Minyard wrote:
> On Fri, Apr 11, 2025 at 04:25:10PM +1000, Nicholas Piggin wrote:
>> On Wed Apr 2, 2025 at 5:17 AM AEST, Corey Minyard wrote:
>> > On Wed, Apr 02, 2025 at 12:01:47AM +1000, Nicholas Piggin wrote:
>> >> These little things came up when looki
On Fri Apr 11, 2025 at 8:55 AM AEST, Pierrick Bouvier wrote:
> On MacOS, UI event loop has to be ran in the main thread of a process.
> Because of that restriction, on this platform, qemu main event loop is
> ran on another thread [1].
>
> This breaks record/replay feature, which expects thread run
Eric Blake writes:
> Qemu's attempts to learn whether a destination file starts life with
QEMU (multiple times).
> all zero contents are just a hueristic. There may be cases where the
heuristic
> caller is aware of information that qemu cannot learn quickly, in
> which case telling qemu what
On Fri Apr 11, 2025 at 8:36 PM AEST, Philippe Mathieu-Daudé wrote:
> On 11/4/25 10:04, Nicholas Piggin wrote:
>> Add tracing for more received packet types, cbw_state changes, and
>> some more SCSI callbacks. These were useful in debugging relaxed
>> packet ordering support.
>>
>> Signed-off-by: N
On Fri Apr 11, 2025 at 8:37 PM AEST, Philippe Mathieu-Daudé wrote:
> On 11/4/25 10:04, Nicholas Piggin wrote:
>> This reflects a little better what it does, particularly with a
>> subsequent change to relax the order packets are seen in. This
>> field is not the general state of the MSD state machi
On Fri Apr 11, 2025 at 8:21 PM AEST, Philippe Mathieu-Daudé wrote:
> On 11/4/25 10:04, Nicholas Piggin wrote:
>> These structures are hardware interfaces, ensure the layout is
>> correct.
>>
>> Signed-off-by: Nicholas Piggin
>> ---
>> hw/usb/dev-storage.c | 5 -
>> 1 file changed, 4 insert
101 - 175 of 175 matches
Mail list logo
