maxbytes_negative: Update max-bytes negative cases

[ybduan]

ID: 2469

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.

[YongxueHong]

Hi @MiriamDeng @fbq815
Could you help review it from your platform?
Thanks.

[YongxueHong]

LGTM.

[XueqiangWei]

Hi @MiriamDeng @fbq815 Could you help review it from your platform? Thanks.

[fbq815]

@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

[YongxueHong]

@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
Got your point. @ybduan How about your thoughts? Both are okay with me, depending on all the feature owners' considerations.
Thanks.
Hi @ybduan Could you help to invite other platform reviewers with this PR?
Thanks in advance.

[zhenyzha]

@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.