You are not logged in.
Pages: 1
Hi folks,
I don’t typically (ever) post, but my google foo is failing me with this issue. I'm encountering a hard freeze of the host, and it seemingly only happens when the single Win7/64 guest blanks the screen. I don't recall it happening with an ArchLinux guest blanking using the same basic hardware configuration. At this point I've disabled screen shutdown and it seems to not be crashing. I can play games and overall stress out the VM and it seems to not care.
Background information:
Hardware:
Dell Precision T7500, single quad Xeon and 32GB RAM
LSI 9211-8i flashed to IT Mode
On board PERC 6/I, running mirror for host with:
250 Mb boot partition
Remainder LVM partition with one XFS LV for Arch root
Radeon R7 250 (Passed through to Guest)
nVidia Quadro FX 580 (staying on host for now)
lspci for background
[root@kvmhost ~]# lspci
00:00.0 Host bridge: Intel Corporation 5520 I/O Hub to ESI Port (rev 22)
00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 (rev 22)
00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 22)
00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 22)
00:14.0 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub System Management Registers (rev 22)
00:14.1 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 22)
00:14.2 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 22)
00:1a.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4
00:1a.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5
00:1a.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6
00:1a.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2
00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller
00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1
00:1c.5 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 6
00:1d.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1
00:1d.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2
00:1d.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3
00:1d.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90)
00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller
00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller
00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller
01:00.0 PCI bridge: Pericom Semiconductor PCI Express to PCI-XPI7C9X130 PCI-X Bridge (rev 04)
03:00.0 VGA compatible controller: NVIDIA Corporation G96GL [Quadro FX 580] (rev a1)
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750 / R7 250E]
04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]
05:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS (rev 08)
06:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5761 Gigabit Ethernet PCIe (rev 10)
07:0a.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx]
20:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 22)
20:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 22)
20:09.0 PCI bridge: Intel Corporation 7500/5520/5500/X58 I/O Hub PCI Express Root Port 9 (rev 22)
20:14.0 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub System Management Registers (rev 22)
20:14.1 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 22)
20:14.2 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 22)
22:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03)
24:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 02)
3f:00.0 Host bridge: Intel Corporation Xeon 5500/Core i7 QuickPath Architecture Generic Non-Core Registers (rev 05)
3f:00.1 Host bridge: Intel Corporation Xeon 5500/Core i7 QuickPath Architecture System Address Decoder (rev 05)
3f:02.0 Host bridge: Intel Corporation Xeon 5500/Core i7 QPI Link 0 (rev 05)
3f:02.1 Host bridge: Intel Corporation Xeon 5500/Core i7 QPI Physical 0 (rev 05)
3f:02.4 Host bridge: Intel Corporation Xeon 5500/Core i7 QPI Link 1 (rev 05)
3f:02.5 Host bridge: Intel Corporation Xeon 5500/Core i7 QPI Physical 1 (rev 05)
3f:03.0 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller (rev 05)
3f:03.1 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Target Address Decoder (rev 05)
3f:03.2 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller RAS Registers (rev 05)
3f:03.4 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Test Registers (rev 05)
3f:04.0 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 0 Control Registers (rev 05)
3f:04.1 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 0 Address Registers (rev 05)
3f:04.2 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 0 Rank Registers (rev 05)
3f:04.3 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 0 Thermal Control Registers (rev 05)
3f:05.0 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 1 Control Registers (rev 05)
3f:05.1 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 1 Address Registers (rev 05)
3f:05.2 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 1 Rank Registers (rev 05)
3f:05.3 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 1 Thermal Control Registers (rev 05)
3f:06.0 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 2 Control Registers (rev 05)
3f:06.1 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 2 Address Registers (rev 05)
3f:06.2 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 2 Rank Registers (rev 05)
3f:06.3 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated Memory Controller Channel 2 Thermal Control Registers (rev 05)Software--not sure what's relevant, lets start with this. All current stuff, installed Sunday/Monday of this week:
[root@kvmhost ~]# uname -a
Linux kvmhost 3.17.3-1-ARCH #1 SMP PREEMPT Fri Nov 14 23:13:48 CET 2014 x86_64 GNU/Linux
[jallen@kvmhost ~]$ qemu-system-x86_64 --version
QEMU emulator version 2.1.2, Copyright (c) 2003-2008 Fabrice BellardNot using libvirt, just a basic qemu script to launch...as below:# Startup Windows 7 guest
Also, for what it's worth, I am planning to use ZFS on the host as well. I had it running, but have uninstalled the zfs-git package for now, as I thought it could be contributing to my issues. The data drive for my VM files is running on btrfs temporarily.
sudo qemu-system-x86_64 \
-bios /usr/share/qemu/bios.bin -vga none \
-name win7 \
-cpu host \
-smp 2,sockets=1,cores=2,threads=0 \
-enable-kvm \
-m 8G \
-rtc clock=host \
-vga none \
-serial null \
-parallel null \
-monitor none \
-display none \
-k en-us \
-machine type=q35,accel=kvm \
-usb -device usb-host,hostbus=6,hostaddr=2 \
-boot order=cd \
-device ahci,id=ahci \
-device virtio-scsi-pci,id=scsi \
-drive file=/mnt/ssd_mirror/vm/win7/win7.qcow2,cache=none,if=virtio \
-drive file=/mnt/ssd_mirror/vm/wingames/games.qcow2,cache=none,if=virtio \
-device ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1 \
-device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on \
-device vfio-pci,host=04:00.1,bus=pcie.0 \
-device vfio-pci,host=00:1b.0,bus=pcie.0 \
-net nic,model=virtio,macaddr=00:16:3e:00:0a:0a -net bridge,br=br0I've blacklisted the radeon driver and have the cards being claimed by stub:
[root@kvmhost kvm_scripts]# dmesg | grep stub
[ 0.000000] Command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/mapper/kvmhost--vg-archroot rw intel_iommu=on pci-stub.ids=1002:683f,1002:aab0,8086:3a3e initrd=../initramfs-linux.img
[ 0.000000] Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/mapper/kvmhost--vg-archroot rw intel_iommu=on pci-stub.ids=1002:683f,1002:aab0,8086:3a3e initrd=../initramfs-linux.img
[ 0.921647] pci-stub: add 1002:683F sub=FFFFFFFF:FFFFFFFF cls=00000000/00000000
[ 0.921666] pci-stub 0000:04:00.0: claimed by stub
[ 0.921678] pci-stub: add 1002:AAB0 sub=FFFFFFFF:FFFFFFFF cls=00000000/00000000
[ 0.921686] pci-stub 0000:04:00.1: claimed by stub
[ 0.921691] pci-stub: add 8086:3A3E sub=FFFFFFFF:FFFFFFFF cls=00000000/00000000
[ 0.921698] pci-stub 0000:00:1b.0: claimed by stubWhat else can I look at? What other information would be helpful?
Thanks.
Last edited by mopar_geek (2014-11-19 16:36:44)
Offline
Hey,
what's the problem if disabling display shutdown solved the issue?
Other information that might be interesting would be drivers including versions and maybe the display configuration (number, connector, resolution, …).
Another possible workaround might be using ovmf (see this blog if you want/need more information).
The people in this thread (especially aw) might also be able to help you… there has been a lot of discussion about a ton of different issues relating to setups similar to your own and I read most of the thread, but problem similar to yours comes to my mind at the moment.
i'm sorry for my poor english wirting skills…
Offline
what's the problem if disabling display shutdown solved the issue?
Fair enough. I thought about that--the whole thing of "If poking yourself in the eye hurts, don't poke yourself in the eye." That's what I typically will do in these sort of situations, but a hard lock due to screen shutdown seems extreme, and I tend to think that I'm not the only one experiencing a given problem. I guess I figure issues on the guest shouldn't affect the host, but suppose that as soon as you're passing real device through, that may go out the window. Still don't think something as "simple" as a screen timeout should cause a hard lock on the host.
Thanks for the links--the MSI/OVMF seems like it could be fruitful, but I can't mess with it now. This does seem like an interrupt problem and I didn't do anything on the guest re interrupts. I may have missed some step along the way while trying to follow the 20 how-to threads I did.
Thanks!
Offline
I tend to think that I'm not the only one experiencing a given problem
I used to think that, too. Then I started configuring really strange setups and it lead me to having to submit a kernel patch, because apparently noone uses that specific SATA controller in combination with those UEFI settings and that driver.
i'm sorry for my poor english wirting skills…
Offline
Pages: 1