htpcnewbie
-
Posts
295 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by htpcnewbie
-
-
9 hours ago, trurl said:
Ouch, thanks for pointing out. Saw rc2 on top of the thread topic and assumed this was recent.
-
Sluggish WIN10 KVM performance on rc2
Hi, I have been missing from the forums for a while which goes to tell how trouble free unraid has been. Recently battled with horrible win10 kvm performance after upgrading to rc2 and had a hard time pinpointing the root cause. I didn't anticipate unraid version to be the problem since it was a while after the upgrade I used the kvm. While on rc2, the cores dedicated to the kvm were almost at 100% just by opening a browser.
After I rolled back to beta25 the kvm is working as expected. If this is not a known issue I am happy to provide additional info to help diagnose the problem with rc2.
-
<rant> Feels frustrating when the docker just stops working and you realize a week later something isnt working and dont have time for another week to sit in front of the computer to pull up and try to diagnose what's working. I guess getting old means we need 'stuff' to work, there are times when we have ability and interest to spend tinkering but not always. <end rant>
I stopped my deluge container until I can get some time to sit and figure out what's wrong. Would be nice to see in bold letters, change xx variable to yy to get things working to minimize effort in diagnosis. Appreciate the effort by binhex and team, guess the pains of growing up.
-
binhex - In have set my ip addresses to start at 10.10.1.1. I would think that should be the LAN network value. isnt it?
ok, just so you know the LAN_NETWORK value you have is incorrect, it should be 10.10.1.0/24
-
Adding snapshots of my delugevpn docker setup for a fellow user who needs some help. This post is for reference only to share my setup pictures and I am not asking for help!
-
I was waiting to uninstall SNAP since I had trouble mounting one of my SSD with btrfs using unassigned plugin. I decided now is the right time to move away from SNAP.
a. I need help with one of my btrfs SSD. Although this drive is getting mounted, there is no status message indicating it has been mounted. The 'mount' button is enabled and temperature shows *
b. I see that all unassigned drives (mounted and unmounted) show drive temperatures anytime I refresh the screen. These drive icons are also green. Raid drives are greyed out indicating they are spun down and show * temperatures. The default spin down time is 15 mins. Does unassigned devices plugin spin down drives (mounted and unmounted)?
SNAP is not supported.
As for mounting with this plugin, did you watch the video in the first post, all the way to the end?
-
Hi - I am using this plugin in a 6.1.6 pro server with about 9 unassigned disks. All f them are working fine, thank you for the plugin!
I have a question on the spindown. The default spindown is 15 mins and I do not seem to see the disks spinning down. Anytime I pull up the tower main page, all the disks are lit up green and show a disk temperature including unmounted disks. The raid disks do not show this behavior. If they are spinned down, the disk icon is greyed and there no disk temperature reported. Am I interpreting this behavior correctly?
Also, how do I custom mount the disks at a specified mount point and name? I am still using the SNAP plugin that mounts one of my vm ssd.
-
Great work guys, Thank you for coordinating and getting a plugin out for the user community.
-
+1 on b12 until the b13 issues are sorted out. Can you please elaborate on what does vm-tools help with? I would love to have the ability of some programs (like Plex) bypassing the VPN. (not related to vm tools at all)
EDIT: open vm tools: http://open-vm-tools.sourceforge.net/about.php
http://unraid.zeron.ca/plugins/open-vm-tools/openVMTools.plg
Finally work with unRAID 6.
Requires the Powerdown package.
Currently compiled for the beta13 Kernel. Will update to B14 when it is out assuming they do not switch to kernel 3.19 as it will not yet compile with that kernel version.
-
I have seen the GUI non-responsive couple of times when attempting to clean stop, maybe something in my VM settings could be the cause. I am more comfortable with the terminal and hence I have used it to stop and start the VM. The Win 8.1 installation on my system behaves pleasantly strange. The VM goes into a 'suspend' mode. When I destroy and restart it, it seems the VM starts from a suspend state, all the previous windows are back on. Copied below is my terminal script. I also use this script through my Android phone using "Script Kitty" and it works perfectly.
root@Tower:~# cat /boot/bin/restartvm.sh
virsh destroy win81pci2 virsh start win81pci2
As for the installation part, I have edited the xml's manually and used the GUI only for creating the VM's and hence cannot help much there.
I still haven't fixed this, but here is what I tried:
- Reverted my syslinux.cfg and go scripts
- Rebooted
- Created a new vanilla test VM with VM Manager and chose to create a new disk
- Started VNC - Success.
This worked, however I tried forcing the domain to shutdown with the eject button in VM Manager. This shut down the domain, but now it will not start back up and I get the same boot device error. Why does forcing the domain to shutdown cause this to happen?
This persists through a reboot. It looks like forcing the domain to shutdown possibly corrupted the disk image. Can anyone else confirm?
Is there a better way to shutdown when the standard graceful shutdown in VM Manager does not work?
-
I am trying get started setting up a kodi server. Installed Mariadb but little lost at this point on what to do. Can someone help with a quick walk through for a fresh install to get this docker for kodi server and the appropriate setup for kodi client?
Sounds good, let me know when it's ready, I did clear the db folder ....
Appreciate your assistance.
another build finished, with this "stable" build.
have removed the EDGE routine, because if this stable version works better, running edge to update will screw it up again.
-
Peter - Would it be possible to skip one or couple of application from routing through the VPN and let is go through the WAN? I need plex and madsonic to pass through, PIA VPN allows only one port forward.
Hi,
First, I did this function with help from other resources that asked for this features, and If some one can highlight to me how to verify above issue and how to solve it I would be happy, I'm far away an expert of routing.
Since I don't can't support these extra function to route traffic, I think to remove this from the plugin, and user hopefully can come up with a solution outside the plugin.
//Peter
-
Yep, I am passing the Intel controller.The right usb ports (below the PS/2 KB) are USB5 and I had trouble passing it when using Win7 (no passthrough worked for me with Win7). I have not checked passing through the USB5 port with Win8. I think most of the ports are on usb3, the Intel controller. Maybe a x1 usb pcie card could help, like this one http://www.newegg.com/Product/Product.aspx?Item=N82E16815166026?
root@Tower:~# lspci | grep USB 00:14.0 USB controller: Intel Corporation Device 8cb1 00:1a.0 USB controller: Intel Corporation Device 8cad 00:1d.0 USB controller: Intel Corporation Device 8ca6 0c:00.0 USB controller: ASMedia Technology Inc. Device 1142
So you are using the intel controller. Crud, I was really hoping to avoid that. Aren't the four rear USB ports and the internal port all on that controller? That's a lot of ports for me to forward through when I only need one of them for my USB active extender, and that only leaves me with 2 for other machines. Maybe I did my testing wrong.
-
reluctantflux - Here is my output from lspci and the highlighted one is the one I am passing for USB (usb3/BUS 003). This config has the pci usb slots passing through, so I am not sure whether some of them are not visible to Unraid.
EDIT: looks like I cannot make the bold that is input in code format but I have not removed the bold code to highlight the relevant code.
"
root@Tower:/mnt/disk/SSD1/vm/image# lspci 00:00.0 Host bridge: Intel Corporation Haswell DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Haswell PCI Express x16 Controller (rev 06) 00:01.1 PCI bridge: Intel Corporation Haswell PCI Express x8 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation Haswell Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Haswell HD Audio Controller (rev 06) [b]00:14.0 USB controller: Intel Corporation Device 8cb1[/b] 00:16.0 Communication controller: Intel Corporation Device 8cba 00:19.0 Ethernet controller: Intel Corporation Device 15a1 00:1a.0 USB controller: Intel Corporation Device 8cad 00:1b.0 Audio device: Intel Corporation Device 8ca0 00:1c.0 PCI bridge: Intel Corporation Device 8c90 (rev d0) 00:1c.2 PCI bridge: Intel Corporation Device 8c94 (rev d0) 00:1c.3 PCI bridge: Intel Corporation Device 8c96 (rev d0) 00:1c.6 PCI bridge: Intel Corporation Device 8c9c (rev d0) 00:1d.0 USB controller: Intel Corporation Device 8ca6 00:1f.0 ISA bridge: Intel Corporation Device 8cc4 00:1f.2 SATA controller: Intel Corporation Device 8c82 00:1f.3 SMBus: Intel Corporation Device 8ca2 01:00.0 VGA compatible controller: AMD/ATI [Advanced Micro Devices, Inc.] Tahiti XT [Radeon HD 7970] 01:00.1 Audio device: AMD/ATI [Advanced Micro Devices, Inc.] Tahiti XT HDMI Audio [Radeon HD 7970 Series] 02:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 11) 05:00.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:01.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:03.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:05.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:07.0 PCI bridge: ASMedia Technology Inc. Device 1184 08:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) 0a:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) 0b:00.0 USB controller: ASMedia Technology Inc. Device 1142
output from lsusb (note BUS 003 is missing here since it is being passed through)
root@Tower:/mnt/disk/SSD1/vm/image# lsusb Bus 002 Device 002: ID 8087:8001 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard Bus 005 Device 002: ID 8564:1000 <<- This is the unraid key. Location: Leftmost bottom slot on the mobo, forward looking aft. Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8009 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
vfio-bind in go, the last address is for usb pci
#For KVM videocard video & hdmi audio pass thru /usr/local/sbin/vfio-bind 0000:01:00.0 0000:01:00.1 0000:00:14.0
my xml (bold toward the end is the pci passthrough for usb3)
<domain type='kvm' id='2' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>win81x64pci</name> <uuid>d8d5720f-e23f-40d4-8a6b-19864c464c41</uuid> <description>win81x64pci</description> <memory unit='KiB'>13107200</memory> <currentMemory unit='KiB'>13107200</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.1'>hvm</type> <boot dev='hd'/> <bootmenu enable='yes'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> </cpu> <clock offset='localtime'/> <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='qcow2' cache='none' io='native'/> <source file='/mnt/disk/SSD1/vm/image/Win81x64.qcow2'/> <backingStore/> <target dev='vdc' bus='virtio'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/disk/SSD1/vm/media/Windows81Pro.iso'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <alias name='sata0-0-0'/> <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/disk/SSD1/vm/media/virtio-win-0.1-81.iso'/> <backingStore/> <target dev='sdd' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb0'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb0'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb0'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x2'/> </controller> <controller type='sata' index='0'> <alias name='sata0'/> <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> <interface type='bridge'> <mac address='52:54:00:0e:6d:3d'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </interface> <input type='tablet' bus='usb'> <alias name='input0'/> </input> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </memballoon> </devices> <seclabel type='none' model='none'/> <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=pcie.0'/> [b] <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:14.0,bus=root.1,addr=00.1'/>[/b] </qemu:commandline> </domain>
So you're passing through the ASMedia controller, and not the intel one, correct? Can you show me your "Universal Serial Bus Controllers" section of Device Manager? I'm curious on if you have different host controllers showing than me. Also, I read this could be an issue with the Bios, having the USB 3.0 supporting legacy devices.
-
Hey reluctantflux - I have been meaning to ping and let you know about this but travelling this week and got busy. I tried win8.1 with the xml that I posted earlier on this thread and the Pci pass through for usb3 worked without trouble in first go. You were right about it not working in win7 though but it worked in win8.1.
My unraid key is moved to usb5 slot, bottom left side (front looking aft). I think the inside USB slot, inside usb2 headers and mobo right side slots are on usb3 which I am passing through. Can you try this config and see whether it works on your win8.1?
Merry Christmas and Happy Holidays!
EDIT: I just checked the xml I posted earlier and seems it is my first pass using usb5 pass through. If you are having trouble let me know and I can send my working version of xml. I will be back home this Monday.
htpcnewbie and I have the same motherboard, and I came across having the same issues as they were. It is not a Win7 issue, as the same thing happens in Win8. Basically, the controller shows up in device manager, but it has a yellow exclamation because it has failed to start. We have the ASRock Xtreme6 LGA1150 motherboard. Here's a few commands with their outputs:
root@Tower:~# lspci | grep ASMedia 05:00.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:01.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:03.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:05.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:07.0 PCI bridge: ASMedia Technology Inc. Device 1184 08:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) 0a:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) 0c:00.0 USB controller: ASMedia Technology Inc. Device 1142 root@Tower:~# lsusb Bus 002 Device 002: ID 8087:8001 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 007: ID 04f2:0841 Chicony Electronics Co., Ltd HP Multimedia Keyboard Bus 005 Device 016: ID 1532:0101 Razer USA, Ltd Copperhead Mouse Bus 005 Device 008: ID 046d:0a1f Logitech, Inc. G930 Bus 005 Device 006: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub Bus 005 Device 013: ID 0cf3:3002 Atheros Communications, Inc. AR3011 Bluetooth Bus 005 Device 011: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 005 Device 005: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub Bus 005 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub Bus 005 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub Bus 005 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8009 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 174c:3074 ASMedia Technology Inc. Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 010: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 003 Device 004: ID 045e:006d Microsoft Corp. eHome Remote Control Keyboard keys Bus 003 Device 003: ID 174c:2074 ASMedia Technology Inc. Bus 003 Device 002: ID 0781:5580 SanDisk Corp. SDCZ80 Flash Drive Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@Tower:~# readlink /sys/bus/usb/devices/usb5 ../../../devices/pci0000:00/0000:00:1c.6/0000:0c:00.0/usb5 root@Tower:~#
-
Spent sometime debugging and think it could be Win 7 related. I moved all the pci passthru intended usb's to usb003 (has one pci address similar to OP) and moved my unraid flash drive to usb005 (has two pci addresses). Defined the vfio-bind and qemu. The VM started and everything looked good except that the usb devices on pci pass thru were not recognized. In fact as soon as I defined the vfio-bind, the keyboards and mice on usb003 lost their power and kvm>devices did not show any usb003 devices.
I am going back to define my usb's in host mode until I get around to installing Win 8
The usb pci part of your XML looks correct to me. Have you tired a different USB device when to turn on the VM (just to see if that works). If a different USB device does not work, you could try passing a different bus instead. If it still is giving you issues maybe it is a Windows 7 issue? I have never tried Windows 7 as a VM so I am not sure.
-
Arche - I realized that unraid cannot see bus005 by accident. After I started the VM and the usb devices weren't responding, I saw that none of the bus005 devices were not visible in VM > devices > pci. I thought they were disconnected and double checked they were all connected. A reboot showed they were visible again. So to answer your question, yes they were correctly vfio binded.
I was wondering whether my interpretation of the pci address to xml is incorrect since I see two parts in there and I am using only the second part in the pci address. I am going to try to check again later tonight ... Meanwhile let me know if you have any suggestions to try out.
Double check to make sure bus 005 is part of vifo-bind. Type lsusb and make sure that any bus 005 devices do not show up. That means that unRAID cannot see them which is what you eant
-
Yes, the VM starts but the usb devices are not recognized in Windows. If I add the second part of the pci address (to vfio bind and qemu part in xml), the VM doesn't start.
So if you use 0b:00.0 your VM starts correct?
-
Excellent write up, thank you! I just setup my KVM and this couldn't come at a better time. I did a little bit of usb-investigation and not having much luck with pci passthrough. I have a long 40ft monoprice usb cable (think it has a in-built repeater) that goes to my htpc and need to passthrough just this port for now. I have rearranged the usb ports so that bus 005 has only these devices. I defined the xml and vfio binds based on the archedraft's example. I have two pci address and that could be the tricky part here. I am having trouble Windows 7 recognizing the devices ...
output of >lsusb
Bus 002 Device 002: ID 8087:8001 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 017: ID 046d:c714 Logitech, Inc. diNovo Edge Keyboard Bus 005 Device 016: ID 046d:c713 Logitech, Inc. Bus 005 Device 013: ID 046d:0b04 Logitech, Inc. Bus 005 Device 012: ID 0471:0815 Philips (or NXP) eHome Infrared Receiver Bus 005 Device 015: ID 04d8:003f Microchip Technology, Inc. Bus 005 Device 014: ID 046d:082d Logitech, Inc. HD Pro Webcam C920 Bus 005 Device 011: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 005 Device 010: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 005 Device 009: ID 0409:005a NEC Corp. HighSpeed Hub Bus 005 Device 008: ID 0409:005a NEC Corp. HighSpeed Hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8009 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 174c:3074 ASMedia Technology Inc. Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 021: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS Bus 003 Device 020: ID 1a40:0101 Terminus Technology Inc. Hub Bus 003 Device 019: ID 046d:c227 Logitech, Inc. G15 Refresh Keyboard Bus 003 Device 018: ID 0458:0007 KYE Systems Corp. (Mouse Systems) Bus 003 Device 017: ID 046d:c226 Logitech, Inc. G15 Refresh Keyboard Bus 003 Device 016: ID 046d:c223 Logitech, Inc. G11/G15 Keyboard / USB Hub Bus 003 Device 003: ID 174c:2074 ASMedia Technology Inc. Bus 003 Device 002: ID 8564:1000 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
output of readlink, note there are two parts of address next to pci unlike the example from OP (0000:00:1c.6/0000:0b:00.0)
root@Tower:/boot/INSTALL# readlink /sys/bus/usb/devices/usb5 ../../../devices/pci0000:00/0000:00:1c.6/0000:0b:00.0/usb5
for vfio bind (the first two are for videocard video, hdmi audio)
/usr/local/sbin/vfio-bind 0000:01:00.0 0000:01:00.1 0000:0b:00.0
my xml
<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>win7x64-usbpci</name> <uuid>5239b56c-419e-407e-86d0-eaf2c0bad2b5</uuid> <description>win7x64usbpci</description> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.1'>hvm</type> <boot dev='hd'/> <bootmenu enable='no'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> </cpu> <clock offset='localtime'/> <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='qcow2' cache='none' io='native'/> <source file='/mnt/disk/SSD1/vm/image/Win7x64.qcow2'/> <target dev='vdc' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/disk/SSD1/vm/media/X17-24281.iso'/> <target dev='hda' bus='sata'/> <readonly/> <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/disk/SSD1/vm/media/virtio-win-0.1-81.iso'/> <target dev='sdd' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x2'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:0e:6d:3d'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </interface> <input type='tablet' bus='usb'/> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </memballoon> </devices> <seclabel type='none' model='none'/> <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=pcie.0'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=0b:00.0,bus=root.1,addr=00.1'/> </qemu:commandline> </domain>
I have removed all sections I previously had for hostdev usb definitions and added the pci for usb, the relevant qemu code is:
<qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=0b:00.0,bus=root.1,addr=00.1'/>
Am I defining the xml part correctly? The root and addr part look mysterious to me. I used only the second part of the readlink pci address. Using the first part (0000:00:1c.6) gives an xml error and the vm does not start.
-
Yep, makes sense. I will run the disk for another 2 cycles before setting it in the server.
Thanks for the suggestions!
The inability to clear the drive had nothing to do with thr existing partitions, or the starting. sector.
Existing partitions would have been cleared, that had nothing to do with the error message you saw.
Do not fall under a false impression all is well. You will probably experience random parity errors. They are very hard to isolate, so keep this disk in mind if it happens to you. And do not forget to test your memory. It is critical as anything.
-
Wanted to give a quick update .. my preclear run from yesterday got done just a while ago and everything looks okay. I am speculating it maybe either due to the 3 windows partitions that preclear did not clear or lack of -A option (first sector started at 63, now it is 64).
=============
========================================================================1.13
== invoked as: ./preclear_disk.sh -A -m [email protected] /dev/sde
== SAMSUNG HD204UI S2H7J1RZ913400
== Disk /dev/sde has been successfully precleared
== with a starting sector of 64
== Ran 1 cycle
==
== Using :Read block size = 8225280 Bytes
== Last Cycle's Pre Read Time : 6:47:42 (81 MB/s)
== Last Cycle's Zeroing time : 6:19:39 (87 MB/s)
== Last Cycle's Post Read Time : 19:18:59 (28 MB/s)
== Last Cycle's Total Time : 32:27:28
==
== Total Elapsed Time 32:27:28
==
== Disk Start Temperature: 22C
==
== Current Disk Temperature: 22C,
==
============================================================================
No SMART attributes are FAILING_NOW
0 sectors were pending re-allocation before the start of the preclear.
0 sectors were pending re-allocation after pre-read in cycle 1 of 1.
0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.
0 sectors are pending re-allocation at the end of the preclear,
the number of sectors pending re-allocation did not change.
0 sectors had been re-allocated before the start of the preclear.
0 sectors are re-allocated at the end of the preclear,
the number of sectors re-allocated did not change.
=============================================================================
Joe - I noticed that bit but didn't see why that would be the case. I also noticed that the MBR on this disk had 3 partitions similar to before the preclear process. I reasoned that since the partitions were not deleted (as I hope they would) and preclear was having issues with it. So I started a second pass of preclear this morning after explicitly deleting the partitions with "preclear.sh -Z" option. I was planning on waiting on the second pass result to see what to do further .. sounds reasonable? I ran stress tests (with prime95) for a day which stressed out both the memory & CPU at 100% before I started converting the machine to unraid server.
Newbie to unraid here, got my first pass of 4 HDD's done and one of them did not pass the preclear. Surprising that I did not find any errors from the output. I have explicitly cleared the MBR with -Z option (there were 3 partitions from Windows) and have started the 2nd pass this morning. Any thoughts on why the preclear did not go through?
Report
========================================================================1.13
== invoked as: ./preclear_disk.sh -m [email protected] /dev/sde
==
== Disk /dev/sde has NOT been successfully precleared
== Postread detected un-expected non-zero bytes on disk==
== Ran 1 cycle
==
== Using :Read block size = 8225280 Bytes
Yes, and it told you why, you just missed it. The post-read expected the disk to be all zeros. It was not.
The actual cause could be almost anything except the "mouse" It could be a bad disk, or bad memory, or a flaky power supply, or motherboard, or disk controller.
I'd start with a memory test, preferably overnight. Then, tests using badblocks on the disk itself. Then go from there.
Joe L.
-
Joe - I noticed that bit but didn't see why that would be the case. I also noticed that the MBR on this disk had 3 partitions similar to before the preclear process. I reasoned that since the partitions were not deleted (as I hope they would) and preclear was having issues with it. So I started a second pass of preclear this morning after explicitly deleting the partitions with "preclear.sh -Z" option. I was planning on waiting on the second pass result to see what to do further .. sounds reasonable? I ran stress tests (with prime95) for a day which stressed out both the memory & CPU at 100% before I started converting the machine to unraid server.
Newbie to unraid here, got my first pass of 4 HDD's done and one of them did not pass the preclear. Surprising that I did not find any errors from the output. I have explicitly cleared the MBR with -Z option (there were 3 partitions from Windows) and have started the 2nd pass this morning. Any thoughts on why the preclear did not go through?
Report
========================================================================1.13
== invoked as: ./preclear_disk.sh -m [email protected] /dev/sde
==
== Disk /dev/sde has NOT been successfully precleared
== Postread detected un-expected non-zero bytes on disk==
== Ran 1 cycle
==
== Using :Read block size = 8225280 Bytes
Yes, and it told you why, you just missed it. The post-read expected the disk to be all zeros. It was not.
The actual cause could be almost anything except the "mouse" It could be a bad disk, or bad memory, or a flaky power supply, or motherboard, or disk controller.
I'd start with a memory test, preferably overnight. Then, tests using badblocks on the disk itself. Then go from there.
Joe L.
-
Newbie to unraid here, got my first pass of 4 HDD's done and one of them did not pass the preclear. Surprising that I did not find any errors from the output. I have explicitly cleared the MBR with -Z option (there were 3 partitions from Windows) and have started the 2nd pass this morning. Any thoughts on why the preclear did not go through?
Report
========================================================================1.13
== invoked as: ./preclear_disk.sh -m [email protected] /dev/sde
==
== Disk /dev/sde has NOT been successfully precleared
== Postread detected un-expected non-zero bytes on disk==
== Ran 1 cycle
==
== Using :Read block size = 8225280 Bytes
== Last Cycle's Pre Read Time : 8:12:02 (67 MB/s)
== Last Cycle's Zeroing time : 6:03:45 (91 MB/s)
== Last Cycle's Post Read Time : 13:47:05 (40 MB/s)
== Last Cycle's Total Time : 28:03:59
==
== Total Elapsed Time 28:03:59
==
== Disk Start Temperature: 21C
==
== Current Disk Temperature: 23C,
==
============================================================================
No SMART attributes are FAILING_NOW
0 sectors were pending re-allocation before the start of the preclear.
0 sectors were pending re-allocation after pre-read in cycle 1 of 1.
0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.
0 sectors are pending re-allocation at the end of the preclear,
the number of sectors pending re-allocation did not change.
0 sectors had been re-allocated before the start of the preclear.
0 sectors are re-allocated at the end of the preclear,
the number of sectors re-allocated did not change.
============================================================================
Output -
========================================================================1.13
== invoked as: ./preclear_disk.sh -m [email protected] /dev/sde
==
== Disk /dev/sde has NOT been successfully precleared
== Postread detected un-expected non-zero bytes on disk==
== Ran 1 cycle
==
== Using :Read block size = 8225280 Bytes
== Last Cycle's Pre Read Time : 8:12:02 (67 MB/s)
== Last Cycle's Zeroing time : 6:03:45 (91 MB/s)
== Last Cycle's Post Read Time : 13:47:05 (40 MB/s)
== Last Cycle's Total Time : 28:03:59
==
== Total Elapsed Time 28:03:59
==
== Disk Start Temperature: 21C
==
== Current Disk Temperature: 23C,
==
============================================================================
No SMART attributes are FAILING_NOW
0 sectors were pending re-allocation before the start of the preclear.
0 sectors were pending re-allocation after pre-read in cycle 1 of 1.
0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.
0 sectors are pending re-allocation at the end of the preclear,
the number of sectors pending re-allocation did not change.
0 sectors had been re-allocated before the start of the preclear.
0 sectors are re-allocated at the end of the preclear,
the number of sectors re-allocated did not change.
============================================================================
============================================================================
==
== S.M.A.R.T Initial Report for /dev/sde
==
Disk: /dev/sde
smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)
Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Device Model: SAMSUNG HD204UI
Serial Number: S2H7J1RZ913400
Firmware Version: 1AQ10001
User Capacity: 2,000,398,934,016 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 6
Local Time is: Mon Nov 12 21:25:03 2012 Local time zone must be set--see zic m
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
Unraid OS version 6.9.1 available
in Announcements
Posted
Upgraded from 6.9.0-beta25 to 6.9.1. I am seeing poor video performance for my windows 10 kvm home theater setup. Have a Nvidia gtx 960 assigned to this kvm.
Are there any known issues and fixes to improve pefromace?