This series has been successfully tested by QE. Specify a directory
for the mem-path of a memory-backend-file object. Check the error
message has been improved without referring to a device, which can
lead to confusion.
Tested-by: Mario Casquero
On Wed, Sep 6, 2023 at 2:07 PM David
This patch has been successfully tested by QE. Start a VM with a
virtio-balloon device and resize it to an invalid value. Check in the
expected error message that now makes reference to 'value' instead of
'target'.
Tested-by: Mario Casquero
On Tue, Oct 31, 2023 at 12:12 PM Markus Armbruster
This patch has been successfully tested by QE. With a debug QEMU
build, start a VM with a virtio-mem device and 'dynamic-memslots=off',
this one can be resized seamlessly, no floating point exception found.
Tested-by: Mario Casquero
On Mon, Oct 23, 2023 at 1:13 PM David Hildenbrand wrote
This series has been successfully tested by QE. Start a vm using
pc.ram id but specifying a different memory-backend from the default
one. Check the error message has been improved.
Tested-by: Mario Casquero
On Wed, Aug 23, 2023 at 5:38 PM David Hildenbrand wrote:
>
> For migration pu
virtio-mem device change
>
> Cc: Peter Maydell
> Cc: Paolo Bonzini
> Cc: Richard Henderson
> Cc: Eduardo Habkost
> Cc: "Michael S. Tsirkin"
> Cc: Marcel Apfelbaum
> Cc: Igor Mammedov
> Cc: qemu-...@nongnu.org
> Cc: Gavin Shan
> Cc: Mario Casquero
This series has been tested successfully by QE. Start a VM with a 8G
virtio-mem device and start memtester on it. Enable x-ignore-shared
capability and then do migration. Migration was successful and
virtio-mem can be resized as usual.
Tested-by: Mario Casquero
BR,
Mario
On Tue, Jun 20
This series has also been successfully tested in x86_64.
Tested-by: Mario Casquero
On Thu, Jan 18, 2024 at 4:08 AM Zhenyu Zhang wrote:
>
> [PATCH v1 2/2] memory-device: reintroduce memory region size check
>
> Test on 64k basic page size aarch64
> The patches work well on
QEMU 8.2.50 monitor - type 'help' for more information
qemu-system-x86_64: cannot use stdio by multiple character devices
qemu-system-x86_64: could not connect serial device to character backend 'stdio'
real 0m0.012s
user 0m0.006s
sys 0m0.007s
Tested-by: Mario Casquero
On Wed, Jan 31, 2024 at 7
This series has been successfully tested in x86. Execute the cpu help
command and check in the list the x86 prefix is no longer present.
Tested-by: Mario Casquero
On Sat, Apr 20, 2024 at 7:47 AM Thomas Huth wrote:
>
> Printing an architecture prefix in front of each CPU name is not h
plugged
Tested-by: Mario Casquero
On Tue, Apr 16, 2024 at 4:14 PM David Hildenbrand wrote:
>
> The error message is actually expressive, considering QEMU only. But
> when called from Libvirt, talking about "size" can be confusing, because
> in Libvirt "size" trans
This series has been successfully tested by QE. Start the
qemu-storage-daemon in the background with a rhel 9.5 image and
vhost-user-blk. After that, boot up a VM with virtio-mem and
vhost-user-blk-pci. Check with the HMP command 'info mtree' that
virtio-mem is making use of multiple memslots.
.
Tested-by: Mario Casquero
On Mon, Mar 11, 2024 at 9:00 PM Mario Casquero wrote:
>
> This series has been successfully tested by QE. Start the
> qemu-storage-daemon in the background with a rhel 9.5 image and
> vhost-user-blk. After that, boot up a VM with virtio-mem and
> vhost-user
-by: Mario Casquero
On Wed, Jun 5, 2024 at 12:45 PM Michal Privoznik wrote:
>
> If memory-backend-{file,ram} has a size that's not aligned to
> underlying page size it is not only wasteful, but also may lead
> to hard to debug behaviour. For instance, in case
> memory-backend-file and hug
This patch has been successfully tested by QE. After allocating some
hugepages in the host, try to boot up a VM with the memory backed by a
file and the size unaligned, check now the message displayed by QEMU:
qemu-system-x86_64: backend memory size must be multiple of 0x20
Tested-by: Mario
-id=0
-numa cpu,node-id=0,socket-id=1,core-id=1,thread-id=0 -numa
cpu,node-id=1,socket-id=1,core-id=1,thread-id=1 -accel qtest
Tested-by: Mario Casquero
On Tue, Jun 4, 2024 at 8:24 AM Ani Sinha wrote:
>
> 'pentium' cpu is old and obsolete and should be avoided for running tests if
15 matches
Mail list logo
