d.bech

C0o0o0o0o0L... So this device (a USB condencer mic) was working fine up until today. Nothing has changed that I am aware of but currently windows won't recognise it. Nothing in audio devices, nothing in device manager. Unraid is see it fine. Bus 001 Device 024: ID 17a0:0303 Samson Technologies Corp. C01U Pro condenser microphone And I have passed it through. <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x17a0'/> <product id='0x0303'/> <address bus='1' device='23'/> </source> <alias name='hostdev0'/> </hostdev> I've tried it in another PC and it shows up and functions as normal. I've tried moving it around to other USB ports that I know are working with other devices I've tried with the VMs USB controller in nec-xhci mode and in the default mode. I'm really at a loss for what to do, this device has had some trouble showing up in this VM in the past but a reboot of the VM has always gotten it back full XML <domain type='kvm' id='8' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Windows 10</name> <uuid>fc8280c4-7269-a6dd-ebdf-41fd12e5cf5e</uuid> <description>Windows 10 64bit</description> <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'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' 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='writeback'/> <source file='/mnt/user/boot/Windows 10/vdisk1.img'/> <backingStore/> <target dev='hdb' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <controller type='usb' index='0' model='nec-xhci'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:ce:26:89'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Windows 10.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='usb' managed='yes'> <source> <vendor id='0x17a0'/> <product id='0x0303'/> <address bus='1' device='23'/> </source> <alias name='hostdev0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x045e'/> <product id='0x02e6'/> <address bus='1' device='19'/> </source> <alias name='hostdev1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> <address bus='1' device='20'/> </source> <alias name='hostdev2'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=2,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=00:1b.0,bus=root.1,addr=01.0'/> </qemu:commandline> </domain> unraid-diagnostics-20160206-1733.zip

I tried that plugin, but lost my server config, long story short I use the Docker. I recommend OpenVPN from this https://github.com/linuxserver/docker-templates source, worked for me. Any questions I had were stomped searching through: https://lime-technology.com/forum/index.php?board=56.0 and Google. kewl, I'll try it out

Probably best to creat a new post for this. Doesn't seem related to the initial question here

I think I am going to try and configure a VPN server on unraid in the mean time while I get around to upgrading my router. Should I use that plugin or would a docker be best? And how do I set it up?

ken-ji I gotta say this docker as ace. Thanks a bunch man

Wicked

Two questions... How should I go about decreasing the number of drives in my cache? and How would unraid take it if I moved my USB stick and array to a completely different PC? ---------------------------------------------------------------------------------------------------- Currently I'm running a Windows VM on unraid for my main PC but I have some spare hardware about so I'm planning to move unraid onto it's own PC and go back to running windows normally. Can I move my unraid install to completely different hardware if I keep the same drives? or will I need to setup a new one?

ooooh I gotcha, just set that up. looks like it's going great thanks!

Are there any docs or how tos on using this? I haven't setup a VPN before.

Just using symbolic links or is there a better way?

That would be pretty dope...

So windows updated and now it's fixed........???????

What if I wanted to specify a share for it to backup?

Wicked, great to hear

If you head over to tools and then click system devices you should see this As you can see each devices as it's own device number and ID we can use either of these to pass the devices through to our VMs I usually use device ID as it seems to change less often (Yes sometimes these will change after reboots or if you unplug the device and you'll have to update your XML next instead of picking the devices using the GUI click edit XML on you VM and add the either of the following for each device My examples will look at the device Bus 001 Device 002: ID 2516:0017 which happens to be my keyboard If you want to enter it by device number <hostdev mode='subsystem' type='usb' managed='yes'> <source> <address bus='1' device='2'/> </source> </hostdev> Or if you want to enter is by ID <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x2516'/> <product id='0x0017'/> </source> </hostdev>

There should be no reason that version 6.1.7 breaks your VM. Did you create a support topic? Yep I linked it in the post you quoted

Yep, this started after reboot

It all stopped working after the recent update. any ideas? XML <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Windows 10</name> <uuid>fc8280c4-7269-a6dd-ebdf-41fd12e5cf5e</uuid> <description>Windows 10 64bit</description> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>10485760</memory> <currentMemory unit='KiB'>10485760</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='off'/> <vapic state='off'/> <spinlocks state='off'/> </hyperv> <kvm> <hidden state='on'/> </kvm> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' 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='writeback'/> <source file='/mnt/user/boot/Windows 10/vdisk1.img'/> <target dev='hdb' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOs/virtio-win-0.1.112.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </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='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='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:ce:26:89'/> <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/Windows 10.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='usb' managed='yes'> <source> <vendor id='0x045e'/> <product id='0x02e6'/> </source> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x17a0'/> <product id='0x0303'/> </source> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> </source> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x22d4'/> <product id='0x130c'/> </source> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x2109'/> <product id='0x2812'/> </source> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x2516'/> <product id='0x0017'/> </source> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=2,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=00:1b.0,bus=root.1,addr=01.0'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=00.1'/> </qemu:commandline> </domain>

It seems to have broken my Windows 10 VM (details: https://lime-technology.com/forum/index.php?topic=46125) how do I downgrade?

Welp I'm out of ideas, I'll try find a way to roll back unRAID

I removed the line that contained hyperv and it went right back to crashing a bunch then booting into a laggy VM. So maybe it's not the clock and its just that that particular line was putting it back into hyper v mode which works fine but my GPU doesn't like it However going back to the stock clock <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> The VM won't boot its just stuck in the crash loop. I guess I'll try messing with it until something happens or I find more information on the parameters

I removed the line that contained hyperv and it went right back to crashing a bunch then booting into a laggy VM. So maybe it's not the clock and its just that that particular line was putting it back into hyper v mode which works fine but my GPU doesn't like it

I changed my clock to this and it's stable again but my GPU has gone back to not working with code 43 as in https://lime-technology.com/forum/index.php?topic=45486 <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> I'm guessing based on the name 'hypervclock' that this is using hyperv which stopps my GPU from working so I think I need to change the clock just not to this. Any ideas?

I had installed the recent unraid update but hadn't rebooted yet as I was mid editing a video. Everything was running normally. There was also a windows update waiting to be applied. After rebooting I also decided to add some of my shares as HDDs into my VM. I they re added my USB devices which don't show up in the gui via XML and re added a fix from a previous thread which got my GPU working (a nvidia GTX970) found here https://lime-technology.com/forum/index.php?topic=45486 I then booted my VM and it got stuck in a crash loop, most of the time it would just crash other times it would BSOD with the error UNHANDLED_THREAD_EXCEPTION. So I tried removing all the new drives I added and it was still the same. So next I took it all the way back to just the stock XML and it crashed a couple of times and then booted, I couldn't do anything as one of the USB devices I add manually is my keyboard. I then shut it down added my usb devices back in and it crashed a little then booted up. It is now very laggy but I don't see any resources within windows that are maxing out checking my stats in unRAID I am almost always very close to maxing out the memory as I give 10 gb of it to the VM and leave 6 to unRAID. So I tried giving more memory to unraid 8gb to the VM 8gb to unRAID. Still the same. Next I rolled back the windows update. Still the same. I can't imagine the unRAID update would cause this so I haven't rolled it back yet but anyone have any ideas? I had a very stable VM yesterday and now I have a laggy mess VM XML <domain type='kvm' id='38' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Windows 10</name> <uuid>fc8280c4-7269-a6dd-ebdf-41fd12e5cf5e</uuid> <description>Windows 10 64bit</description> <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'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' 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='writeback'/> <source file='/mnt/cache/boot/Windows 10/vdisk1.img'/> <backingStore/> <target dev='hda' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <controller type='usb' index='0'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:ce:26:89'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Windows 10.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='usb' managed='yes'> <source> <vendor id='0x045e'/> <product id='0x02e6'/> <address bus='1' device='4'/> </source> <alias name='hostdev0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x17a0'/> <product id='0x0303'/> <address bus='1' device='24'/> </source> <alias name='hostdev1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> <address bus='1' device='5'/> </source> <alias name='hostdev2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <address bus='1' device='2'/> </source> <alias name='hostdev3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <address bus='1' device='3'/> </source> <alias name='hostdev4'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <address bus='1' device='6'/> </source> <alias name='hostdev5'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=2,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=00:1b.0,bus=root.1,addr=01.0'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=00.1'/> </qemu:commandline> </domain> My diag file exceeds the size limit of attachments so here it is: http://puu.sh/mQ9cs/bf243fdc14.zip

Hey guys I was looking to backup a bunch of stuff to dropbox and after looking about I guessed a docker might do it? I was searching here https://hub.docker.com/search/?isAutomated=0&isOfficial=0&page=2&pullCount=0&q=dropbox&starCount=0 and found that there are a bunch of different user made dockers for dropbox. Can anyone recommend one?