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.
Description of problem:
this bug was separated from bug 928251 #4.
disable the 'nx' flag via '-cpu model_name,-flag' when boot up guest, it will hang at 'Loading initial ramdisk...' and fail to boot up, it cann't continue and have no any call trace waiting long time.
btw,
1.if a don't disable the 'nx' flag, it can expose to guest correctly.
2.if i disable the 'kvmclock' flag, it can boot up guest sucessfully and verify the 'kvmclock' flag not existing in /sys/devices/system/clocksource/clocksource0/available_clocksource.
Version-Release number of selected component (if applicable):
host info:
kernel-3.9.0-0.rc4.45.el7.x86_64
qemu-kvm-1.4.0-1.el7.x86_64
seabios-1.7.2-0.2.gita810e4e7.el7.x86_64
seabios-bin-1.7.2-0.2.gita810e4e7.el7.noarch
guest info:
kernel-3.9.0-0.rc4.45.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.reserve Haswell host.
2.boot guest with disable 'NX' cpu flag via '-cpu model_name,-tsc' on haswell host.
e.g:/usr/libexec/qemu-kvm -S -M q35 -cpu Haswell,-nx -enable-kvm -m 4096 -smp 8,cores=2,threads=4,sockets=1,maxcpus=10 -no-kvm-pit-reinjection -usb -device usb-tablet,id=input0 -name sluo-test -uuid b03eea94-a502-4142-b541-96f86473a07a -rtc base=localtime,clock=host,driftfix=slew -device virtio-serial-pci,id=virtio-serial0,max_ports=16,vectors=0,bus=pcie.0,addr=0x4 -chardev socket,id=channel1,path=/tmp/helloworld1,server,nowait -device virtserialport,chardev=channel1,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0,id=port1 -chardev socket,id=channel2,path=/tmp/helloworld2,server,nowait -device virtserialport,chardev=channel2,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0,id=port2 -drive file=/home/RHEL-Server-7.0-64-ahci.qcow2,if=none,id=drive-system-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop,serial=QEMU-DISK1 -device ide-hd,bus=ide.0,unit=0,drive=drive-system-disk,id=system-disk,bootindex=0 -device virtio-balloon-pci,id=ballooning,bus=pcie.0,addr=0x5 -drive file=/home/my-data-disk.qcow2,if=none,id=drive-data-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop,serial=QEMU-DISK2 -device ide-hd,bus=ide.1,unit=0,drive=drive-data-disk,id=data-disk -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -serial unix:/tmp/ttyS0,server,nowait -qmp tcp:0:4444,server,nowait -k en-us -boot menu=on -vnc :1 -spice disable-ticketing,port=5931 -monitor stdio
Actual results:
after step 2,
it will stop at 'Loading initial ramdisk...' and fail to boot up, it cann't continue and have no any call trace waiting long time.
I will attach the screenshot later.
Expected results:
it should boot up successfully without any problem.
Additional info:
I couldn't reproduce this bug. Maybe it was a guest-side RHEL bug that was fixed (not unlikely), or it can be only reproduce on specific hardware. Please check if you can reproduce it, and if you can, please let me log into the system where I can reproduce it (and point me to the disk image path and qemu-kvm command-line I should use to reproduce).
(In reply to Eduardo Habkost from comment #3)
> I couldn't reproduce this bug. Maybe it was a guest-side RHEL bug that was
> fixed (not unlikely), or it can be only reproduce on specific hardware.
> Please check if you can reproduce it, and if you can, please let me log into
> the system where I can reproduce it (and point me to the disk image path and
> qemu-kvm command-line I should use to reproduce).
I also cann't reproduce this issue with the latest build on my SandyBridge host, it can boot up successfully now. Maybe we have fixed this issue with the latest build.
# uname -r && rpm -q qemu-kvm
3.10.0-76.el7.x86_64
qemu-kvm-1.5.3-41.el7.x86_64
Best Regards,
sluo