Jump to content

CateFul

Members
  • Posts

    9
  • Joined

  • Last visited

Posts posted by CateFul

  1. I was able to get Linux VM's running just fine with Skylake using only the IGD (HD Graphics 530).

     

    However with a Windows 10 VM i'm getting some weird issues. Screen is being duplicated 3 or 4 times horizontally. So on startup I see the windows spinning loading gif a the top of the screen in the middle and at the bottom. Basically i'm getting a sliver of the screen stacked three times.

     

    Any suggestions on settings to fix it?

     

    This happens before installing the Intel HD Graphics driver. You can work around this by using VNC (no IGD passthrough) to setup Windows, after that, turn remote desktop access on, and passthrough the IGD, and then use remote desktop from either your phone or another windows pc to setup the intel driver. The windows logo screen would still be duplicated horizontally but once it's boot to the login screen everything should work.

  2. go ahead and do it, I did it with a Mikrotik CHR vm and it works flawlessly with pppoe connection. Though I only have 2 ports on my unRaid box so I had to use the old router as a switch. If you have the right wifi module you can even pass it to the vm and set it up as a wireless AP as well.

  3. It's not specific to Avast either. I tried two other pc management/tweaking solutions with embedded antivirus engine with the same result. They are 360 and Tencent, both are Chinese only so I don't think anyone here tried these. These two solutions, on installation seems fine, but dns does not work, i can ping 8.8.8.8 and the dns server's ip directly and nslookup works perfectly but pinging for example google.com or any other hostname fails. Then on restart the vm and the host crashes at the Windows 10 loading logo screen.

  4. Windows 10 VM guest hangs and the unRaid host system becomes unresponsive and would need a hard reset, if an antivirus software is installed and running. Steps to reproduce:

     

    1. Create a vanilla Windows 10 VM with the needed virtio drivers

    2. Install Avast, system hangs once Avast install finishes and the program starts up

     

    VM logs shows no error.

     

    Here's the my xml file, again, most settings are the default values. unRaid is on a skylake G4500 box.

    <domain type='kvm'>
      <name>Windows</name>
      <uuid>a412c976-dd0d-8d38-1726-276157e9b6d4</uuid>
      <metadata>
        <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
      </metadata>
      <memory unit='KiB'>8388608</memory>
      <currentMemory unit='KiB'>4194304</currentMemory>
      <memoryBacking>
        <nosharepages/>
      </memoryBacking>
      <vcpu placement='static'>2</vcpu>
      <cputune>
        <vcpupin vcpu='0' cpuset='0'/>
        <vcpupin vcpu='1' cpuset='1'/>
      </cputune>
      <os>
        <type arch='x86_64' machine='pc-i440fx-2.7'>hvm</type>
      </os>
      <features>
        <acpi/>
        <apic/>
        <hyperv>
          <relaxed state='on'/>
          <vapic state='on'/>
          <spinlocks state='on' retries='8191'/>
          <vendor id='none'/>
        </hyperv>
      </features>
      <cpu mode='host-passthrough'>
        <topology sockets='1' cores='2' threads='1'/>
      </cpu>
      <clock offset='localtime'>
        <timer name='hypervclock' present='yes'/>
        <timer name='hpet' present='no'/>
      </clock>
      <on_poweroff>destroy</on_poweroff>
      <on_reboot>restart</on_reboot>
      <on_crash>restart</on_crash>
      <devices>
        <emulator>/usr/local/sbin/qemu</emulator>
        <disk type='file' device='disk'>
          <driver name='qemu' type='raw' cache='writeback'/>
          <source file='/mnt/user/domains/Windows/vdisk1.img'/>
          <target dev='hdc' bus='virtio'/>
          <boot order='1'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
        </disk>
        <disk type='file' device='cdrom'>
          <driver name='qemu' type='raw'/>
          <source file='/mnt/user/isos/cn_windows_10_multiple_editions_x64_dvd_6848463.iso'/>
          <target dev='hda' bus='ide'/>
          <readonly/>
          <boot order='2'/>
          <address type='drive' controller='0' bus='0' target='0' unit='0'/>
        </disk>
        <disk type='file' device='cdrom'>
          <driver name='qemu' type='raw'/>
          <source file='/mnt/user/isos/virtio-win-0.1.126.iso'/>
          <target dev='hdb' bus='ide'/>
          <readonly/>
          <address type='drive' controller='0' bus='0' target='0' unit='1'/>
        </disk>
        <controller type='usb' index='0' model='ich9-ehci1'>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
        </controller>
        <controller type='usb' index='0' model='ich9-uhci1'>
          <master startport='0'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
        </controller>
        <controller type='usb' index='0' model='ich9-uhci2'>
          <master startport='2'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
        </controller>
        <controller type='usb' index='0' model='ich9-uhci3'>
          <master startport='4'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
        </controller>
        <controller type='pci' index='0' model='pci-root'/>
        <controller type='ide' index='0'>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
        </controller>
        <controller type='virtio-serial' index='0'>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
        </controller>
        <interface type='bridge'>
          <mac address='52:54:00:44:32:94'/>
          <source bridge='br1'/>
          <model type='virtio'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
        </interface>
        <serial type='pty'>
          <target port='0'/>
        </serial>
        <console type='pty'>
          <target type='serial' port='0'/>
        </console>
        <channel type='unix'>
          <source mode='connect'/>
          <target type='virtio' name='org.qemu.guest_agent.0'/>
          <address type='virtio-serial' controller='0' bus='0' port='1'/>
        </channel>
        <input type='tablet' bus='usb'/>
        <input type='mouse' bus='ps2'/>
        <input type='keyboard' bus='ps2'/>
        <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'>
          <listen type='address' address='0.0.0.0'/>
        </graphics>
        <video>
          <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
        </video>
        <memballoon model='virtio'>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
        </memballoon>
      </devices>
    </domain>
    

  5. PCI Devices

     

    00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM Registers [8086:191f] (rev 07)

    00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 07)

    00:01.1 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x8) [8086:1905] (rev 07)

    00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06)

    00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f] (rev 31)

    00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Thermal subsystem [8086:a131] (rev 31)

    00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H CSME HECI #1 [8086:a13a] (rev 31)

    00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] [8086:a102] (rev 31)

    00:1b.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Root Port #17 [8086:a167] (rev f1)

    00:1b.2 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Root Port #19 [8086:a169] (rev f1)

    00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #1 [8086:a110] (rev f1)

    00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #5 [8086:a114] (rev f1)

    00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #9 [8086:a118] (rev f1)

    00:1d.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #13 [8086:a11c] (rev f1)

    00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC Controller [8086:a145] (rev 31)

    00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC [8086:a121] (rev 31)

    00:1f.3 Multimedia audio controller [0401]: Intel Corporation Sunrise Point-H HD Audio [8086:a170] (rev 31)

    00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus [8086:a123] (rev 31)

    02:00.0 Serial Attached SCSI controller [0107]: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072] (rev 02)

    04:00.0 Ethernet controller [0200]: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller [1969:e091] (rev 10)

    05:00.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578]

    06:00.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578]

    06:01.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578]

    06:02.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578]

    06:04.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578]

    09:00.0 USB controller [0c03]: Intel Corporation DSL6540 USB 3.1 Controller [Alpine Ridge] [8086:15b6]

    IOMMU Groups

     

    /sys/kernel/iommu_groups/0/devices/0000:00:00.0

    /sys/kernel/iommu_groups/1/devices/0000:00:01.0

    /sys/kernel/iommu_groups/1/devices/0000:00:01.1

    /sys/kernel/iommu_groups/1/devices/0000:02:00.0

    /sys/kernel/iommu_groups/2/devices/0000:00:02.0

    /sys/kernel/iommu_groups/3/devices/0000:00:14.0

    /sys/kernel/iommu_groups/3/devices/0000:00:14.2

    /sys/kernel/iommu_groups/4/devices/0000:00:16.0

    /sys/kernel/iommu_groups/5/devices/0000:00:17.0

    /sys/kernel/iommu_groups/6/devices/0000:00:1b.0

    /sys/kernel/iommu_groups/6/devices/0000:00:1b.2

    /sys/kernel/iommu_groups/6/devices/0000:04:00.0

    /sys/kernel/iommu_groups/7/devices/0000:00:1c.0

    /sys/kernel/iommu_groups/7/devices/0000:00:1c.4

    /sys/kernel/iommu_groups/7/devices/0000:05:00.0

    /sys/kernel/iommu_groups/7/devices/0000:06:00.0

    /sys/kernel/iommu_groups/7/devices/0000:06:01.0

    /sys/kernel/iommu_groups/7/devices/0000:06:02.0

    /sys/kernel/iommu_groups/7/devices/0000:06:04.0

    /sys/kernel/iommu_groups/7/devices/0000:09:00.0

    /sys/kernel/iommu_groups/8/devices/0000:00:1d.0

    /sys/kernel/iommu_groups/8/devices/0000:00:1d.4

    /sys/kernel/iommu_groups/9/devices/0000:00:1f.0

    /sys/kernel/iommu_groups/9/devices/0000:00:1f.2

    /sys/kernel/iommu_groups/9/devices/0000:00:1f.3

    /sys/kernel/iommu_groups/9/devices/0000:00:1f.4

     

    I am looking to run a VM for Plex Media Player. I was hoping to use the IGD for graphics/sound. Above are my IOMMU groups and devices. Upon reading the posts above and from my limited understanding am I correct in thinking that I will be unable to passthrough my sound device and as such will only be able to get video on my TV? Am I better off putting in a discrete GPU? Thanks,

     

    I have the same iommu groups with audio at 0000:00:1f.3 in group 9 with other devices. I ended up passing through everything in group 9 without any issues and audio works fine. I had to manually enable MSI in my windows VM though.

×
×
  • Create New...