Jump to content
SirSterben

Some VMs not wanting to boot

1 post in this topic Last Reply

Recommended Posts

Hi,
I'm having issues with booting certain operating systems.
I've tried booting with Linux and so far Ubuntu and Manjaro work perfectally but not Debian (Kali linux to be exact). On the other hand, I tried booting with Windows 10 but no luck so far. All of the VMs that won't boot will work if I use VNC but will not boot when using any other GPU device other than VNC.

 

I have tried using both the stable and the next versions of Unraid and still have the same issue.

 

When I tried booting the Windows 10 VM I got this error as well:

Nov 9 04:39:14 Tower kernel: irq 16: nobody cared (try booting with the "irqpoll" option)
Nov 9 04:39:14 Tower kernel: CPU: 3 PID: 0 Comm: swapper/3 Tainted: P O 5.3.8-Unraid #1
Nov 9 04:39:14 Tower kernel: Hardware name: Dell Inc. Precision Tower 3620/09WH54, BIOS 2.3.5 08/06/2017
Nov 9 04:39:14 Tower kernel: Call Trace:
Nov 9 04:39:14 Tower kernel: <IRQ>
Nov 9 04:39:14 Tower kernel: dump_stack+0x5d/0x79
Nov 9 04:39:14 Tower kernel: __report_bad_irq+0x30/0xa5
Nov 9 04:39:14 Tower kernel: note_interrupt+0x1d8/0x229
Nov 9 04:39:14 Tower kernel: handle_irq_event_percpu+0x4f/0x6f
Nov 9 04:39:14 Tower kernel: handle_irq_event+0x34/0x51
Nov 9 04:39:14 Tower kernel: handle_fasteoi_irq+0x92/0xfc
Nov 9 04:39:14 Tower kernel: handle_irq+0x1c/0x1f
Nov 9 04:39:14 Tower kernel: do_IRQ+0x46/0xc8
Nov 9 04:39:14 Tower kernel: common_interrupt+0xf/0xf
Nov 9 04:39:14 Tower kernel: </IRQ>
Nov 9 04:39:14 Tower kernel: RIP: 0010:cpuidle_enter_state+0xe8/0x1f0
Nov 9 04:39:14 Tower kernel: Code: ff 45 84 ff 74 1d 9c 58 0f 1f 44 00 00 0f ba e0 09 73 09 0f 0b fa 66 0f 1f 44 00 00 31 ff e8 9d 46 ba ff fb 66 0f 1f 44 00 00 <45> 85 e4 0f 88 ea 00 00 00 49 63 cc be ff ff ff 7f 48 ba ff ff ff
Nov 9 04:39:14 Tower kernel: RSP: 0018:ffffc900000c7e90 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffdd
Nov 9 04:39:14 Tower kernel: RAX: ffff888811ae0ac0 RBX: ffff888811aea300 RCX: 000000000000001f
Nov 9 04:39:14 Tower kernel: RDX: 0000000000000000 RSI: 00000000258efbe6 RDI: 0000000000000000
Nov 9 04:39:14 Tower kernel: RBP: ffffffff820584a0 R08: 0000008ffcbaa9b9 R09: 0000000000000000
Nov 9 04:39:14 Tower kernel: R10: 071c71c71c71c71c R11: 0000000000000020 R12: 0000000000000001
Nov 9 04:39:14 Tower kernel: R13: 0000008ffcba984f R14: 0000008ffcbaa9b9 R15: 0000000000000000
Nov 9 04:39:14 Tower kernel: cpuidle_enter+0x25/0x31
Nov 9 04:39:14 Tower kernel: do_idle+0x17e/0x1fc
Nov 9 04:39:14 Tower kernel: cpu_startup_entry+0x18/0x1a
Nov 9 04:39:14 Tower kernel: start_secondary+0x154/0x16f
Nov 9 04:39:14 Tower kernel: secondary_startup_64+0xa4/0xb0
Nov 9 04:39:14 Tower kernel: handlers:
Nov 9 04:39:14 Tower kernel: [<00000000d0c6a22b>] i801_isr [i2c_i801]
Nov 9 04:39:14 Tower kernel: [<00000000bd4fc18e>] vfio_intx_handler
Nov 9 04:39:14 Tower kernel: Disabling IRQ #16

But sometimes the VM hangs at this instead of the one above:

Nov 9 04:52:36 Tower kernel: DMAR: DRHD: handling fault status reg 2
Nov 9 04:52:36 Tower kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 0 [fault reason 02] Present bit in context entry is clear
Nov 9 04:52:41 Tower kernel: br0: port 2(vnet0) entered blocking state
Nov 9 04:52:41 Tower kernel: br0: port 2(vnet0) entered disabled state
Nov 9 04:52:41 Tower kernel: device vnet0 entered promiscuous mode
Nov 9 04:52:41 Tower kernel: br0: port 2(vnet0) entered blocking state
Nov 9 04:52:41 Tower kernel: br0: port 2(vnet0) entered forwarding state
Nov 9 04:52:41 Tower kernel: vfio-pci 0000:00:02.0: enabling device (0400 -> 0403)
Nov 9 04:52:41 Tower kernel: vfio_ecap_init: 0000:00:02.0 hiding ecap 0x1b@0x100
Nov 9 04:52:42 Tower avahi-daemon[3032]: Joining mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe8f:b34e.
Nov 9 04:52:42 Tower avahi-daemon[3032]: New relevant interface vnet0.IPv6 for mDNS.
Nov 9 04:52:42 Tower avahi-daemon[3032]: Registering new address record for fe80::fc54:ff:fe8f:b34e on vnet0.*.

Here is my config for the Windows 10 VM:

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm'>
  <name>Windows 10</name>
  <uuid>a1f97e01-d6b5-c7cf-ce31-f07fa2d4fb86</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
  </metadata>
  <memory unit='KiB'>4194304</memory>
  <currentMemory unit='KiB'>4194304</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>4</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='4'/>
    <vcpupin vcpu='2' cpuset='1'/>
    <vcpupin vcpu='3' cpuset='5'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-i440fx-3.1'>hvm</type>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
      <vendor_id state='on' value='none'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='2' threads='2'/>
  </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 10/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/disks/192.168.0.32_data/ISOs/Windows.iso'/>
      <target dev='hda' bus='ide'/>
      <readonly/>
      <boot order='2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <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>
    <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>
    <interface type='bridge'>
      <mac address='52:54:00:8f:b3:4e'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </hostdev>
    <memballoon model='none'/>
  </devices>
</domain>

Here is the log for the Windows 10 VM itself:

/usr/local/sbin/qemu \
-name 'guest=Windows 10,debug-threads=on' \
-S \
-object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-5-Windows 10/master-key.aes' \
-machine pc-i440fx-3.1,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off \
-cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none \
-m 4096 \
-realtime mlock=off \
-smp 4,sockets=1,cores=2,threads=2 \
-uuid a1f97e01-d6b5-c7cf-ce31-f07fa2d4fb86 \
-display none \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=27,server,nowait \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=localtime \
-no-hpet \
-no-shutdown \
-boot strict=on \
-device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 \
-device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \
-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 \
-drive 'file=/mnt/user/domains/Windows 10/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=writeback' \
-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1,write-cache=on \
-drive file=/mnt/disks/192.168.0.32_data/ISOs/Windows.iso,format=raw,if=none,id=drive-ide0-0-0,readonly=on \
-device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2 \
-netdev tap,fd=29,id=hostnet0,vhost=on,vhostfd=30 \
-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:8f:b3:4e,bus=pci.0,addr=0x3 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=31,server,nowait \
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \
-device vfio-pci,host=00:02.0,id=hostdev0,bus=pci.0,addr=0x2 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2019-11-09 12:52:41.370+0000: Domain id=5 is tainted: high-privileges
2019-11-09 12:52:41.370+0000: Domain id=5 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)

As for the Kali linux VM that doesn't want to boot either. When looking at the system log this is what it hangs on:

Nov 9 04:48:58 Tower kernel: DMAR: DRHD: handling fault status reg 2
Nov 9 04:48:58 Tower kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 0 [fault reason 02] Present bit in context entry is clear
Nov 9 04:49:05 Tower kernel: br0: port 2(vnet0) entered blocking state
Nov 9 04:49:05 Tower kernel: br0: port 2(vnet0) entered disabled state
Nov 9 04:49:05 Tower kernel: device vnet0 entered promiscuous mode
Nov 9 04:49:05 Tower kernel: br0: port 2(vnet0) entered blocking state
Nov 9 04:49:05 Tower kernel: br0: port 2(vnet0) entered forwarding state
Nov 9 04:49:05 Tower kernel: vfio-pci 0000:00:02.0: enabling device (0400 -> 0403)
Nov 9 04:49:05 Tower kernel: vfio_ecap_init: 0000:00:02.0 hiding ecap 0x1b@0x100
Nov 9 04:49:05 Tower acpid: input device has been disconnected, fd 8
Nov 9 04:49:05 Tower acpid: input device has been disconnected, fd 9
Nov 9 04:49:05 Tower acpid: input device has been disconnected, fd 5
Nov 9 04:49:05 Tower acpid: input device has been disconnected, fd 6
Nov 9 04:49:06 Tower kernel: usb 1-8.1: reset full-speed USB device number 9 using xhci_hcd
Nov 9 04:49:06 Tower kernel: usb 1-4: reset full-speed USB device number 3 using xhci_hcd
Nov 9 04:49:06 Tower kernel: usb 1-8.1: reset full-speed USB device number 9 using xhci_hcd
Nov 9 04:49:06 Tower kernel: usb 1-4: reset full-speed USB device number 3 using xhci_hcd
Nov 9 04:49:06 Tower avahi-daemon[3032]: Joining mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe64:587f.
Nov 9 04:49:06 Tower avahi-daemon[3032]: New relevant interface vnet0.IPv6 for mDNS.
Nov 9 04:49:06 Tower avahi-daemon[3032]: Registering new address record for fe80::fc54:ff:fe64:587f on vnet0.*.
Nov 9 04:49:11 Tower kernel: usb 1-8.1: reset full-speed USB device number 9 using xhci_hcd
Nov 9 04:49:11 Tower kernel: usb 1-4: reset full-speed USB device number 3 using xhci_hcd
Nov 9 04:49:11 Tower kernel: usb 1-8.1: reset full-speed USB device number 9 using xhci_hcd
Nov 9 04:49:11 Tower kernel: usb 1-4: reset full-speed USB device number 3 using xhci_hcd

This is the config:

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm'>
  <name>Kali</name>
  <uuid>2fc34369-b7ce-997e-5c6b-b67145cc6fb7</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/>
  </metadata>
  <memory unit='KiB'>4194304</memory>
  <currentMemory unit='KiB'>4194304</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>4</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='4'/>
    <vcpupin vcpu='2' cpuset='1'/>
    <vcpupin vcpu='3' cpuset='5'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-3.1'>hvm</type>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='2' threads='2'/>
  </cpu>
  <clock offset='utc'>
    <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/local/sbin/qemu</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/Kali/vdisk1.img'/>
      <target dev='hdc' bus='virtio'/>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/disks/192.168.0.32_data/ISOs/kali-linux-2019.3-amd64.iso'/>
      <target dev='hda' bus='sata'/>
      <readonly/>
      <boot order='2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </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='pcie-root'/>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x8'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='2' port='0x9'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0xa'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
    </controller>
    <controller type='pci' index='4' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='4' port='0xb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/>
    </controller>
    <controller type='pci' index='5' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='5' port='0xc'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/>
    </controller>
    <controller type='pci' index='6' model='pcie-to-pci-bridge'>
      <model name='pcie-pci-bridge'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:64:58:7f'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <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'>
      <address type='usb' bus='0' port='3'/>
    </input>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x1038'/>
        <product id='0x1206'/>
      </source>
      <address type='usb' bus='0' port='1'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x1038'/>
        <product id='0x1724'/>
      </source>
      <address type='usb' bus='0' port='2'/>
    </hostdev>
    <memballoon model='none'/>
  </devices>
</domain>

Here is also the log for the Kali VM itself:

-display none \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=27,server,nowait \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=utc,driftfix=slew \
-global kvm-pit.lost_tick_policy=delay \
-no-hpet \
-no-shutdown \
-boot strict=on \
-device pcie-root-port,port=0x8,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x1 \
-device pcie-root-port,port=0x9,chassis=2,id=pci.2,bus=pcie.0,addr=0x1.0x1 \
-device pcie-root-port,port=0xa,chassis=3,id=pci.3,bus=pcie.0,addr=0x1.0x2 \
-device pcie-root-port,port=0xb,chassis=4,id=pci.4,bus=pcie.0,addr=0x1.0x3 \
-device pcie-root-port,port=0xc,chassis=5,id=pci.5,bus=pcie.0,addr=0x1.0x4 \
-device pcie-pci-bridge,id=pci.6,bus=pci.1,addr=0x0 \
-device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 \
-device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 \
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 \
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x7.0x2 \
-device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \
-drive file=/mnt/user/domains/Kali/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=writeback \
-device virtio-blk-pci,scsi=off,bus=pci.4,addr=0x0,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1,write-cache=on \
-drive file=/mnt/disks/192.168.0.32_data/ISOs/kali-linux-2019.3-amd64.iso,format=raw,if=none,id=drive-sata0-0-0,readonly=on \
-device ide-cd,bus=ide.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=2 \
-netdev tap,fd=29,id=hostnet0,vhost=on,vhostfd=30 \
-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:64:58:7f,bus=pci.3,addr=0x0 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=32,server,nowait \
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \
-device usb-tablet,id=input0,bus=usb.0,port=3 \
-device vfio-pci,host=00:02.0,id=hostdev0,bus=pcie.0,addr=0x2 \
-device usb-host,hostbus=1,hostaddr=9,id=hostdev1,bus=usb.0,port=1 \
-device usb-host,hostbus=1,hostaddr=3,id=hostdev2,bus=usb.0,port=2 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2019-11-09 12:50:57.240+0000: Domain id=4 is tainted: high-privileges
2019-11-09 12:50:57.240+0000: Domain id=4 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)

My specs are:
i7-6600K
GTX 1070
32 GB DDR3

 

I have also tried using both types of BIOS and it does not make a difference.

 

I have attached my diagnostics.

 

tower-diagnostics-20191109-1235.zip

Edited by SirSterben
Added config for Kali

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.