-
Notifications
You must be signed in to change notification settings - Fork 182
device_option_check:fix sq_inq paremeter error #4325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The --page 0x83 is not expected in the latest Linux. Using --page di or -i directly to get the device identification. Signed-off-by: qingwangrh <[email protected]>
adb2fb2
to
b0ef7b1
Compare
python ConfigTest.py --testcase=device_option_check --iothread_scheme=roundrobin --nr_iothreads=2 --platform=x86_64 --guestname=RHEL.9.4,RHEL.10.1 --driveformat=virtio_scsi,virtio_blk --imageformat=qcow2 --machines=q35 --customsparams="vm_mem_limit = 12G\nimage_aio=io_uring" --firmware=default_bios --netdst=virbr0 --clone=no (01/12) Host_RHEL.m10.u1.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.10.1.x86_64.io-github-autotest-qemu.device_option_check.blk_serial_check.q35: STARTED |
@XueqiangWei @fbq815 Please help to review,thanks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM,
Acked-by: [email protected]
@fbq815 Could you please help review it? Many thanks. |
@qingwangrh for RHEL9 it LGTM, but for RHEL10 I think we need to modify the block checking command on s390x, details in jira task |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
after offline discussion and double check, the failure was caused by patch aplly issue, after re aplly and run, this could PASS as expected
The --page 0x83 is not expected in latest Linux.
Using --page di or -i directly to get the
device identification.
ID:3925