monkeytsar

Nope new/unused ports.

I've been using Docker containers for ages now and not had an issue until now. If i try and add a new docker container (I've tried 3 so far) the connection is always refused and if i do a port scan of the Unraid server the new dockers containers show as closed/blocked but my existing containers ports are all showing open and work fine. I get the same result after a reboot. I always update to the latest stable release of unraid but it's been a while since i pulled a new contianer so i'm not sure at what point (version) it stopped working. Does anyone have any ideas or seen this issue before?

I have a windows 7 VM that runs Argus, since the upgrade to RC4 i can no longer edit the xml to include. <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </source> which is my PCIe Sat tuner card. Every time I edit the xml the changes aren't being saved. This has worked well up until this point, any ideas?

I've installed it previously too, but for some reason i no longer can.

Here's the info. Model: N/A M/B: ASRock - Z77 Extreme4 CPU: Intel® Core™ i5-2500S CPU @ 2.70GHz Cache: 1024 kB, 256 kB, 6144 kB Memory: 16384 MB (max. installable capacity 32 GB) Network: bond0: IEEE 802.3ad Dynamic link aggregation eth0: 1000Mb/s - Full Duplex eth1: 1000Mb/s - Full Duplex Kernel: Linux 4.0.4-unRAID x86_64 OpenSSL: 1.0.1m

is there a show command I can run that'll list all the hardware or should I just list it? I don't have any syslogs is there a way to set up logging or does it need to log to separate syllogism server?

I'm passing through an amd 6450, I've found that if I change the machine type to 440fx the keyboard works but it won't install, it just blank screens or gives me a kernel panic message.

Ok it's still happening but this time it did it while the tv was on but the win8 vm had been idle for a while, i'v set the windows power settings to high performance and told it to never turn off the display and never go to sleep but its still killing the host. Any ideas? I can't even get kodibuntu to reinstall now, if I have the machine set to q35 it never picks up the keyboard no matter how it's passed throught. And if I have it set to 440fx it it lets me use the keyboard but once I select install or live boot it gives me a blank screen or I get kernel panic! I've never had these kinds of problems before and I've been using VMs since the early Beta's

I've installed XBMCBUNTU in the past but I'm struggling to install it again. I can't get passed the initial boot menu, I've tried assigning a keyboard through the vm menu and I've passing through a usb controller and neither works. If I use vnc I can move through the menu but it won't install because it needs a gpu. Anyone got any ideas?

?!? You turn off the TV and that causes the issue? That's pretty strange. What is the display cable you're using? HDMI? Can you try VGA OE dvi just to see if the behavior changes? Yeah its a strange one, and it is via HDMI. I've changed the system type from 440FX to Q35 and so far it seems to have fixed the issue, in fact the whole thing seems a little bit more stable and a bit faster. I let you know if it still ok tomorrow, i just need it to keep me going until the openelec VM is ready.

Hi, I'm having issues with a Win8 VM. I'm currently using Win8 with an AMD 6450 passed through to run Kodi (long story) in my living room, I have it set to never go to sleep and never turn off the display and everything is fine while I'm using it but I like to keep it powered on all the time so that its easy for the kids and wife to use however whenever I turn off the tv it seems to do something strange to the Win8 VM that takes out the unraid host and all dockers and VMs, the only way to get it back is to power cycle the host. Until recently (for 6 Months+)I was using Kodibuntu passing through the same graphics cards etc and never had an issue. Does anyone have any ideas?

Is there any chance you could release the version your using as a beta or even an alpha test? I tried multiple times to get openelec working even going as far as trying to compile my own version but I could never get it to work properly. I've been using kodibuntu since november last year but that's got issues with passing through DTS etc (at least for me) to my amp that I don't get with openelec. I don't think any of us would expect any support from you guys, I wouldn't want to distract you from working on the final release of Unraid 6 but it'd be good to have a play with it.

pcie acs override is currently set to on. I haven't had an opportunity to try a shutdown without the say tuner passed through yet.

I created a new Win7 VM via the b15 VM manager plugin, all that's passed through to it is a Sat TV tuner card. The machine itself works really well however pressing the shutdown button in VM manager doesn't do anything so the only way to shut it down is to vnc onto the machine and shut it down that way. However when I do this the machine starts to shut down and then the host itself seems to crash. I lose web and SSH access to the host, I can no longer access any shares, docker containers or my other VM. The only thing that brings it back is to physically power off the host and turn it back on again. This has happened the last two times I have shut this machine down. Does anyone have any ideas as to why this might happen or if unraid saves crash logs anywhere?

Hi just looking to upgrade to beta 15 and I've just removed dmacias72's VM manager plugin but i've also got another of dmacias72's plugins for Libvirt support do i need to remove this too?

Hi I updated from beta 12 to 14a a little over a week ago. Everything seemed fine, all my containers were still there running and auto start with the server but i just went to try and add a new container and my repositories are empty. I still have them listed in my template repositories field but there's nothing in the list. I've just tried re adding them and i get this error. Warning: unlink(/tmp/tmp-303946796.tar.gz): No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/dockerClient.php on line 157 I just wondered if anyone has had similar issues and what the fix is? Thanks

I've got SNAP installed but what file format do you recommend I use on the drive XFS, NTFS?

Hi I'm looking for a bit of advice. I've just pulled a 120Gb SSD out of a PC and I want to put it in my Unraid server as a dedicated VM drive. What's the best way of doing this while not adding it to the array or using it as a cache drive? Thanks

Just a quick question, i've been passing through PCIe cards without to much trouble but I'm now trying to pass through a PCI sound card and I'm getting errors. Can PCI cards be passed through?

Hi, I'm looking for some help I've been on Beta 12 for ages now and it was running really well for me but yesterday i decided to update it to 14b. I've got a KVM running XBMCbuntu/Kodibuntu and i've had it up and running for months without any errors or the need to reboot etc. Yesterday after the upgrade the machine started up fine and all seemed well however it now randomly freezes while watching something it could be 10mins in or 90mins in. When it freezes it doesn't register any key presses etc within the VM if i SSH into unraid and run the shutdown command (virsh shutdown XBMCBUNTU) it does shut down I don't have to destroy it I can then start it up and it'll run fine again for another 60mins or so and then it'll freeze again. If i leave it not playing anything back it'll happily sit there for hours waiting so the error only happens when its playing something back. I haven't changed anything in the XML file but i'm aware i've been away from these forums for months so i might have something in my config that may cause problems with the new beta. Would you guys be able to look at my xml below and point out anything that may need altering? <domain type='kvm' id='9' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>XBMCBUNTU</name> <memory unit='GB'>2</memory> <currentMemory unit='GB'>2</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> </cputune> <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'> <topology sockets='2' cores='1' threads='1'/> </cpu> <clock offset='localtime'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</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/cache/VMs/XBMCbuntu/XBMCbuntu.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/cache/VMs/ISO/xbmcbuntu-13.0.iso'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-1-0'/> <address type='drive' controller='0' bus='1' target='0' unit='0'/> </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> <controller type='ide' index='0'> <alias name='ide0'/> </controller> <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user/Media'/> <target dir='media'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/> </filesystem> <interface type='bridge'> <mac address='52:94:00:1A:1B:1c'/> <source bridge='br0'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </interface> <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=root.1,addr=00.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:1a.0,bus=pcie.0'/> </qemu:commandline> </domain> Thanks Luke

I'm after a docker container that'll act as a DNS server, I just want to be able to put some manual entries in and set a forwarder to 8.8.8.8 for all other resolutions. Does one exist or can anyone recommend one?

So there are two ways to write the qemu:arg statements based on whether your machine type is set to "pc" or "q35". "pc" uses the i440fx chipset, which does not have a virtual pcie interface, only standard PCI (WHICH DOES NOT MATTER EVEN IF YOU HAVE A PCIE BASED DEVICE). The difference between these two in the LATEST build of unRAID is negligible. I would wager many folks will do fine now using just the i440fx over q35, but if you already have a installed Windows VM that has been activated, changing this now will prompt windows to reactivate the license. So if you're using the machine type of "pc", all of your qemu:arg statements should be like this: <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=##:##.#,bus=root.1,addr=00.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=##:##.#,bus=root.1,addr=00.2'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=##:##.#,bus=root.1,addr=00.3'/> You cannot use "bus=pcie.0" when using the machine type of PC. When using Q35, you can use EITHER method and if you have issues such as htpcnewbie, you should try changing the method for the device having problems to see if that resolves the issue. Generally speaking, Alex Williamson from Red Hat feels that using Q35 isn't necessary and may actually cause some weird issues when used in combination with VFIO right now. I personally haven't seen that yet, but Alex is THE MAN when it comes to vfio (as in her maintains it) and so I take his opinion very seriously. My machine type is currently set to. <type arch='x86_64' machine='pc-q35-2.1'>hvm</type> I haven't seen any issue so far, I've made a few different VM's during the different Beta stages starting with XEN and i'd say this one is the most stable by far. Prior to adding the sat tuner it was up for 6+ weeks without any problems at all. The fact that I'm using Q35 does that mean i should edit my config like this. <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=pcie.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=pcie.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:1a.0,bus=pcie.2'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=07:00.0,bus=pcie.3'/> </qemu:commandline> Assuming I increment the bus=pcie.x?

Can I get a little help on a similar issue please? I have XBMCbuntu installed and I've added TVheadend as a TV back end (I really wanted to use OPENELEC but I can't get it installed because of the HDD driver issue, hopefully UnVM's will help with that) I've added a dual Sat tuner card to my VM and edited my XML like below including all relevant additions to go script's etc. <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:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:1a.0,bus=pcie.0'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=07:00.0,bus=pcie.0'/> </qemu:commandline> device 01:00.0 and 01:00.1 is my AMD 6450 graphics card and sound card. 00:1a.0 is my USB controller I've had these passed through for a while and they all work great. device 07:00.0 is the new dual sat tuner card I've added. I passed it through last night and the machine has booted fine but I haven't had chance to set the card up yet. TV headend does recognise it but before i try and configure it do i need to tweak my xml at all or does it look right as i have both the USB controller and the sat card on pcie.0?

Have you tried msize=262144 in your fstab line. It gave me another 10-15MB/s. I converted my cache to XFS. No change in speed but my vm drive is still btrfs. I have a mythbuntu vm that I can't copy. It does this on a fresh install too on btrfs. It gives an I/O error and qemu-image check shows its fine. I'll try to reinstall myth on the XFS partition. I added msize=262144 into my fstab line and re ran the same test plus a few more and now I'm seeing an average of 90.22MB/s. I can live with those speeds Nice. Is that the spinner or the ssd? Spinner, I haven't had chance to put the ssd in yet.

Have you tried msize=262144 in your fstab line. It gave me another 10-15MB/s. I converted my cache to XFS. No change in speed but my vm drive is still btrfs. I have a mythbuntu vm that I can't copy. It does this on a fresh install too on btrfs. It gives an I/O error and qemu-image check shows its fine. I'll try to reinstall myth on the XFS partition. I added msize=262144 into my fstab line and re ran the same test plus a few more and now I'm seeing an average of 90.22MB/s. I can live with those speeds