Bug 1046907
| Summary: | Virtual FreeBSD boot hang on CPU XEON E5-1620 v2 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Stanislav Petr <glux> | ||||||
| Component: | qemu-kvm | Assignee: | Eduardo Habkost <ehabkost> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.5 | CC: | acathrow, bdas, bsarathy, chayang, glux, iec23801, mkenneth, qzhang, virt-maint | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-05-27 20:02:52 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Stanislav Petr
2013-12-27 11:01:07 UTC
When i try add
<qemu:commandline>
<qemu:arg value='-no-kvm'/>
</qemu:commandline>
do virtual definition, guest can boot correctly (but slow).
After installing kernel 3.8.13-16.3.1.el6uek.x86_64 (from Oracle Linux), FreeBSD guest on XEON E5-1620 v2 is booting correctly. Stanislav: thanks for taking the time to enter a bug report with us. We appreciate the feedback and look to use reports such as this to guide our efforts at improving our products. That being said, we're not able to guarantee the timeliness or suitability of a resolution for issues entered here because this is not a mechanism for requesting support. If this issue is critical or in any way time sensitive, please raise a ticket through your regular Red Hat support channels to make certain it receives the proper attention and prioritization to assure a timely resolution. For information on how to contact the Red Hat production support team, please visit: https://www.redhat.com/support/process/production/#howto Eduardo: maybe a dupe of Bug 1084200, or at least related. Very likely to be due to missing SCAS instruction emulation, like on bug 1084200. More information is needed to confirm that: * The libvirt XML data for the VM; * The data from /var/log/libvirt/qemu/*.log; * dmesg output from host; * /proc/cpuinfo output from both hosts (the one where it worked, and the new one where it didn't work). Not enough information to investigate, but maybe it is a know bug related to SMEP. Using "nosmep" on the host kernel command-line and using "SandyBridge,-smep" as the CPU model may be a workaround for it. Created attachment 900216 [details]
dmesg log
Created attachment 900217 [details]
cpuinfo in proc
I also hit the bug on Xeon(R) CPU E5-2690 v2 when installing freebsd 64 bits. The above workaround doesn't work. Any suggestions? Because I use the qemu-kvm command to start vm, the libvirt xml and /var/log/libvirt/qemu/*.log don't exist. my command is: /usr/libexec/qemu-kvm -name testbsd -M rhel6.5.0 -cpu SandyBridge,-smep -enable-kvm -m 2048 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid 7f68743b-d725-4c7d-dc7e-9aa6712584b3 -drive file=/home/test.img,if=none,id=drive-ide0-0-0,format=qcow2,cache=none -vnc 0.0.0.0:0 -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 --cdrom /home/downloads/FreeBSD-10.0-RC3-amd64-dvd1.iso PS, it works when install 32 bits freebsd such as 7.0-RELEASE-i386-livefs. (In reply to michael from comment #10) > I also hit the bug on Xeon(R) CPU E5-2690 v2 when installing freebsd 64 > bits. The above workaround doesn't work. Your cpuinfo in comment 9 still shows the smep flag. Please boot your host with "nosmep" in the kernel cmdline as Eduardo mentioned in comment 6. > Any suggestions? > > Because I use the qemu-kvm command to start vm, the libvirt xml and > /var/log/libvirt/qemu/*.log don't exist. my command is: > /usr/libexec/qemu-kvm -name testbsd -M rhel6.5.0 -cpu SandyBridge,-smep > -enable-kvm -m 2048 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 > -uuid 7f68743b-d725-4c7d-dc7e-9aa6712584b3 -drive > file=/home/test.img,if=none,id=drive-ide0-0-0,format=qcow2,cache=none -vnc > 0.0.0.0:0 -device > ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 > -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 --cdrom > /home/downloads/FreeBSD-10.0-RC3-amd64-dvd1.iso > > PS, it works when install 32 bits freebsd such as 7.0-RELEASE-i386-livefs. (In reply to Bandan Das from comment #11) > (In reply to michael from comment #10) > > I also hit the bug on Xeon(R) CPU E5-2690 v2 when installing freebsd 64 > > bits. The above workaround doesn't work. > > Your cpuinfo in comment 9 still shows the smep flag. Please boot your host > with "nosmep" in the kernel cmdline as Eduardo mentioned in comment 6. > After correcting my argument in kernel command line, the workaround works. thanks. > > Any suggestions? > > > > Because I use the qemu-kvm command to start vm, the libvirt xml and > > /var/log/libvirt/qemu/*.log don't exist. my command is: > > /usr/libexec/qemu-kvm -name testbsd -M rhel6.5.0 -cpu SandyBridge,-smep > > -enable-kvm -m 2048 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 > > -uuid 7f68743b-d725-4c7d-dc7e-9aa6712584b3 -drive > > file=/home/test.img,if=none,id=drive-ide0-0-0,format=qcow2,cache=none -vnc > > 0.0.0.0:0 -device > > ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 > > -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 --cdrom > > /home/downloads/FreeBSD-10.0-RC3-amd64-dvd1.iso > > > > PS, it works when install 32 bits freebsd such as 7.0-RELEASE-i386-livefs. |