Mario Casquero
Mario Casquero
@zhenyzha @MiriamDeng @PaulYuuu @yanan-fu could you review this PR? Thanks !
@menli820 do you consider this test case could be executed in windows too?
@PaulYuuu @yanan-fu this is a kindly reminder, please could you review this PR? Thanks !
@yanan-fu this is a kindly reminder, could you please review this PR? Thanks !
> Compare this case with case `virtio_mem_numa_basic.with_migration`, The difference is use one virtio_mem instead of two and use memory-backend-file instead of memory-backend-rom, it can be controlled easily with configuration IMO....
``` (1/1) Host_RHEL.m9.u5.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.5.0.x86_64.io-github-autotest-qemu.virtio_mem_hugetlb_migration.q35: STARTED (1/1) Host_RHEL.m9.u5.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.5.0.x86_64.io-github-autotest-qemu.virtio_mem_hugetlb_migration.q35: PASS (162.08 s) RESULTS : PASS 1 | ERROR 0 | FAIL 0 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL...
This is a kindly reminder, @yanan-fu please could you review again this PR? Thanks !
Hi again @yanan-fu this is a kindly reminder, please could you review this PR? Thanks !
> Do we need to cover the negative scenario: > > ``` > If the virtio-mem device is resized to a higher value, a warning message is displayed. > (qemu)...
> > > Do we need to cover the negative scenario: > > > ``` > > > If the virtio-mem device is resized to a higher value, a warning...