Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 892792[details]
screenshotforguest
Description of problem:
After setting max-bytes and period to zero win7-32 guest with virtio-rng device boot up failed as dark screen.
Version-Release number of selected component (if applicable):
qemu-kvm-rhev-1.5.3-60.el7ev.x86_64
kernel-3.10.0-121.el7.x86_64
virtio-win-prewhql-0.1-81
How reproducible:
3/3
Steps to Reproduce:
1.boot up guest with the following CLI
/usr/libexec/qemu-kvm -M pc -m 2G -smp 2 -cpu Nehalem -usb -device usb-tablet -drive file=win7-32-rng-81.raw,format=raw,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=none -device ide-drive,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device rtl8139,netdev=hostnet0,mac=00:52:4f:75:65:35,id=net0 -uuid 4870b5fd-65d1-488a-9333-3c4e095285b0 -rtc-td-hack -no-kvm-pit-reinjection -chardev socket,id=a111,path=/tmp/monitor-win2012-serial,server,nowait -mon chardev=a111,mode=readline -vnc :1 -vga cirrus -monitor stdio -device virtio-balloon-pci,id=balloon1 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -cdrom en_windows_7_ultimate_with_sp1_x86_dvd_u_677460.iso -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0 -device virtio-rng-pci,id=rng0,max-bytes=0,period=0
2.
3.
Actual results:
The guest could not boot up as it was displayed with dark screen.See screenshot
Expected results:
The guest could boot up
Additional info:
The same behavior also happens with a Linux guest.
It is probably a bug in qemu-kvm that was fixed upstream:
QEMU 2.0.50 monitor - type 'help' for more information
(qemu) qemu-system-x86_64: -device virtio-rng-pci,rng=rng0,id=virtrng0,max-bytes=0,period=0: Parameter 'period' expects a positive number
qemu-system-x86_64: -device virtio-rng-pci,rng=rng0,id=virtrng0,max-bytes=0,period=0: Device initialization failed.
qemu-system-x86_64: -device virtio-rng-pci,rng=rng0,id=virtrng0,max-bytes=0,period=0: Device 'virtio-rng-pci' could not be initialized
(In reply to lijin from comment #3)
> with or without assigning max-bytes value,win7-64 can reproduce this issue
> with period=0
This is a qemu's behavior and is not related to Windows (see comment #2). Both max-bytes and period values should be positive numbers.
Created attachment 892792 [details] screenshotforguest Description of problem: After setting max-bytes and period to zero win7-32 guest with virtio-rng device boot up failed as dark screen. Version-Release number of selected component (if applicable): qemu-kvm-rhev-1.5.3-60.el7ev.x86_64 kernel-3.10.0-121.el7.x86_64 virtio-win-prewhql-0.1-81 How reproducible: 3/3 Steps to Reproduce: 1.boot up guest with the following CLI /usr/libexec/qemu-kvm -M pc -m 2G -smp 2 -cpu Nehalem -usb -device usb-tablet -drive file=win7-32-rng-81.raw,format=raw,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=none -device ide-drive,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device rtl8139,netdev=hostnet0,mac=00:52:4f:75:65:35,id=net0 -uuid 4870b5fd-65d1-488a-9333-3c4e095285b0 -rtc-td-hack -no-kvm-pit-reinjection -chardev socket,id=a111,path=/tmp/monitor-win2012-serial,server,nowait -mon chardev=a111,mode=readline -vnc :1 -vga cirrus -monitor stdio -device virtio-balloon-pci,id=balloon1 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -cdrom en_windows_7_ultimate_with_sp1_x86_dvd_u_677460.iso -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0 -device virtio-rng-pci,id=rng0,max-bytes=0,period=0 2. 3. Actual results: The guest could not boot up as it was displayed with dark screen.See screenshot Expected results: The guest could boot up Additional info: