maxbytes_negative: Update max-bytes negative cases #4166
Conversation
|
Hi @MiriamDeng @fbq815 |
ybduan
force-pushed
the
maxbytes_negative_tests
branch
from
a42cf97
to
6e81891
Compare
|
Hi @MiriamDeng @fbq815 Could you help review it from your platform? Thanks. |
|
@ybduan @YongxueHong I've checked the patch is fine, but in my perspective I prefer if we could keep the supports on old versions as well, @PaulYuuu agree with the opinion and maybe we should ask feature owners on all platforms to vote |
Hi @fbq815 |
|
@ybduan For the arm platform, we have just released GA on rhel.9.4. On the other hand, tp-libvirt will retain support for older versions, so there is no requirement for forward compatibility on the arm platform on the tp-qemu side. |
ybduan
force-pushed
the
maxbytes_negative_tests
branch
4 times, most recently
from
4ae25c8
to
1af2507
Compare
1. 'max-bytes=0' setting is no longer allowed by the latest QEMU. Error prompt will be generated when 'max-bytes' is set to 0. 2. Update corresponding error info. Signed-off-by: ybduan <[email protected]>
ybduan
force-pushed
the
maxbytes_negative_tests
branch
from
1af2507
to
c26849b
Compare
|
After offline discussion, we decided to add qemu version requirement for this corner case. |
ID: 2469
Error prompt will be generated when 'max-bytes' is set to 0.