whophil

Members
  • Posts

    24
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

whophil's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I did some testing and found that the audio glitches were (at least in part) related to another VM I had running which was sharing allocated CPUs. I had assigned cores 1,2,3 to the Windows VM and cores 0,1 to the other (Linux VM) -- note the duplicate assignment of core 1. When I increased CPU load on the Linux VM, my Windows VM would produce audio glitches. Here's my current setup, which hasn't produced an audio glitch in awhile: Windows VM -- Cores 2,3 (with isolcpus=2,3 in syslinux.cfg) Linux VM -- Cores 0,1 Unfortunately, I can only run my Windows VM with two CPUs (even when the Linux VM is idle or not running, due to isolcpus). But that is enough for my current needs. Hope this is helpful.
  2. The disk image is on the cache drive, which is a SSD. There is one other Ubuntu Server VM running on the system which runs my Plex server, but this VM is mostly idle during testing. When I go to the advanced settings of my audio playback device, 16bit 44000 HZ (DVD Quality) is already the default settings. Also, the two options "Allow applications to take exclusive control of this device" and "Give exclusive mode applications priority" are both checked by default.
  3. I checked the sound settings in Windows, and nothing seems to be out of the ordinary -- everything is set to stereo output, which matches my TV. I also tried switching to Q35 -- after some fiddling with QEMU commands to get the GTX 950 and its audio device recognized correctly, I can conclude that the "demon audio" is still there, and maybe even worse. Also, overall system performance is worse (including cursor lag when using wireless USB mouse). With the Q35 machine, I did confirm that MSI is again enabled (here is the output of lspci -v) 01:00.0 VGA compatible controller: NVIDIA Corporation Device 1402 (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device 36c3 Flags: bus master, fast devsel, latency 0, IRQ 39 Memory at fd000000 (32-bit, non-prefetchable) [size=16M] Memory at c0000000 (64-bit, prefetchable) [size=256M] Memory at d0000000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] Expansion ROM at fe000000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Legacy Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [258] #1e Capabilities: [128] Power Budgeting <?> Capabilities: [420] Advanced Error Reporting Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Kernel driver in use: vfio-pci 01:00.1 Audio device: NVIDIA Corporation Device 0fba (rev a1) Subsystem: Gigabyte Technology Co., Ltd Device 36c3 Flags: bus master, fast devsel, latency 0, IRQ 40 Memory at fe080000 (32-bit, non-prefetchable) [size=16K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Kernel driver in use: vfio-pci 03:00.0 Ethernet controller: Qualcomm Atheros QCA8171 Gigabit Ethernet (rev 10) Subsystem: ASRock Incorporation Device 10a1 Flags: bus master, fast devsel, latency 0, IRQ 38 Memory at fe100000 (64-bit, non-prefetchable) [size=256K] I/O ports at d000 [size=128] Capabilities: [40] Power Management version 3 Capabilities: [58] Express Endpoint, MSI 00 Capabilities: [c0] MSI: Enable+ Count=1/16 Maskable+ 64bit+ Capabilities: [d8] MSI-X: Enable- Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [180] Device Serial Number 00-00-00-00-00-00-00-00 Kernel driver in use: alx Kernel modules: alx Attached below is the XML file for the Q35 machine. <domain type='kvm' id='11' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Win8-HTPC-OVMF</name> <uuid>a2c7ea78-f49a-ef5b-6b16-521d098d40c9</uuid> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>3</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='2'/> <vcpupin vcpu='2' cpuset='3'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.3'>hvm</type> <loader type='pflash'>/usr/share/qemu/ovmf-x64/OVMF-pure-efi.fd</loader> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='3' threads='1'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='unsafe'/> <source file='/mnt/user/VM-test/Win8-HTPC-OVMF/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='00:16:3e:51:20:4c'/> <source bridge='br0'/> <target dev='vnet1'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Win8-HTPC-OVMF.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x12' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x12' function='0x2'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x09' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x13' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x0a' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x13' function='0x2'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x0b' function='0x0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x07' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=00.1'/> </qemu:commandline> </domain>
  4. If I remove the USB sound card and use only the GTX 950 audio, the audio glitches. When I was using the USB sound card, I was connecting it via a 3.5mm --> RCA adapter to my TV's audio input (the TV allows for me to choose audio sources for the HDMI input). I had the same audio glitches. I didn't do extensive testing with the USB sound card, since it also had a ton of noise (not sure if this was a ground loop problem or something else). In short: - GTX 950 HDMI audio passed through, USB sound card REMOVED --> glitches - GTX 950 HDMI audio REMOVED, USB sound card --> glitches I have not tried passing through the motherboard audio, but I can try at some point during the weekend. [EDIT: It looks like I can't pass through the motherboard audio; it's in a very populated IOMMU group and I have currently not enabled pcie_acs_override] However, I'd really like to get the GTX 950 HDMI audio working correctly. It seems some people have reported success with q35 machines; I wonder if this is at all related.
  5. Sorry if it wasn't clear. I originally had glitchy audio when using the HDMI audio of the GTX 950. I then tried to fix it by using a USB sound card, and the problem persisted.
  6. I, like many others, have problems with glitchy (demon) audio in my Windows 8 VM. This affects video playback occasionally and gaming often. Hardware: CPU: AMD A8-5500 Motherboard: Asrock FM2A78M-ITX+ GPU: Nvidia GTX 950 VM: Machine: i440fx-2.3 BIOS: OVMF Hyper-V disabled USB controller passthrough via PCI Things I've Tried: Enabled MSI on the GTX 950 video/audio devices (MSI is enabled in lspci -v ) Locked CPU cores to the VM via isolcpus (https://lime-technology.com/forum/index.php?topic=43126.15) Used a USB soundcard (connected via the passed-through USB controller) None of these fix the problem, although I think some improvements were seen when enabling MSI. I am somewhat surprised that using a USB soundcard didn't fix the problem -- does this indicate that high DPC latency is caused by something other than the GTX 950 audio? Using USB sound is non-ideal for me, since audio and video both go direct to my TV via HDMI. Are there any other ideas out there? My VM XML is here: <domain type='kvm'> <name>Win8-HTPC-OVMF</name> <uuid>a2c7ea78-f49a-ef5b-6b16-521d098d40c9</uuid> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>3</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='2'/> <vcpupin vcpu='2' cpuset='3'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> <loader type='pflash'>/usr/share/qemu/ovmf-x64/OVMF-pure-efi.fd</loader> </os> <features> <acpi/> <apic/> <hap/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='3' threads='1'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='unsafe'/> <source file='/mnt/user/VM-test/Win8-HTPC-OVMF/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='00:16:3e:51:20:4c'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Win8-HTPC-OVMF.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x12' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x12' function='0x2'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x13' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x13' function='0x2'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x0b' function='0x0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </memballoon> </devices> </domain>
  7. Thanks for sharing. What OS are you running in the VM?
  8. Thanks very much for your XML configurations. For some reason I misread your original post and thought you were running your GT 730 VM with OVMF instead of SeaBIOS. I was eventually able to get a stable Windows 8.1 (not 10) VM with a GT 730 passed through, running OVMF. In case it may help others, I've summarized my problems and findings below: SeaBIOS was unable to "flicker" on a GT 730; OVMF had no problems doing so. I installed Windows 10 on the OVMF machine. After a few reboots, the Tianocore UEFI would fail to boot from the Windows 10 disk, going into a boot loop. UEFI was still able to see my virtual disk and read from the partition which contained bootx64.efi. However, telling the machine to boot from the bootx64.efi file caused the VM to reboot. I have no idea why. I suspect it may have something to do with the fact that Secure Boot was disabled in UEFI, or with automatic Windows updates. I didn't get a chance to try a Windows 10 install with automatic updates disabled. I then installed Windows 8.1 on the OVMF machine. This installation is stable.
  9. kristisdad, I'd appreciate it if you could share your configuration XML
  10. At the time of testing I was running only the Dropbox plugin and no other VMs.
  11. Hi Jon, The Windows 10 VM had sluggish mouse movement, high CPU usage, slow opening of menus in a clean Windows 10 install. USB mouse was passed through via PCI passthrough of USB controller. I didn't have time to explore fixes. The bigger problem was that the OVMF VM would fail to boot after just a few restarts. I don't know too much about how EFI works, but after few successful VM reboots, EFI would fail to load into Windows at all. (It would flash two errors, something related to floppy...) and then reboot.
  12. I am trying to get an Nvidia GT 730 passed through to a Windows 10 guest. I initially tried running the guest with SeaBIOS, but I couldn't get the GPU to flicker or show me anything on the connected monitor (even with no vdisk). I tried passing through the appropriate GPU ROM, and tried with PCIe ACS override enabled/disabled. No go. I got it working with OVMF, but after installing Windows I found performance to be extremely poor and the system very unstable -- it only lasts a few reboots before EFI can no longer find the boot disk. This is a can of worms I don't want to deal with right now. Which brings me back to SeaBIOS -- why doesn't it work? Is there any reason why OVMF (EFI) can initialize the graphics card, but not SeaBIOS? I have another card (AMD Radeon HD 6450) which is correctly initiated by a SeaBIOS guest on the same host machine and when using the same PCI slot. Many thanks in advance.
  13. I've got a number of simultaneous problems right now. I had a Windows guest with a passthrough Radeon 6450 running just fine. I tried to switch out the graphics card for an Nvidia GT 730 and it's given me nothing but problems so far. Trying to start the VM crashes the ENTIRE SYSTEM (dom0) and forces a reboot. Unfortunately, autostart was "on" for this Windows guest VM, which means that powering on the machine puts me into a boot loop. Thankfully I can still get into Unraid safe mode. Here's my question: how do I turn off autostart from the command line? Or alternately, where does KVM manager keep the .xml files, so that I can edit out the offensive lines?
  14. I'm running Unraid 6.0-beta10a and would like to update to a newer version for the various new features and security fixes. It seems that the "preferred" way to upgrade is using the "Check for updates" button on the Plugins page. However, when I check this, it shows "No Updates" available for Unraid Server OS. Is 6.0-beta10a too old to get automatic updates? Or do I need to point the updater to a newer URL for Unraid Server OS?
  15. I upgraded to Unraid 6.0 beta 10 (by simply copying bzimage and bzroot) and was able to get an IP immediately. It appears drivers for the Qualcomm Atheros AR8171 NIC were added sometime between v6.0 beta 5 and beta 10. Hope this information helps somebody.