GHunter

Members
  • Posts

    378
  • Joined

  • Last visited

Everything posted by GHunter

  1. Good to hear. There is so much to be excited about in 6.2!
  2. Have you tried a Win 8.1 or Win 10 installation? It has been my experience that RDP seems to work better under these OS's. Gary
  3. LOL, that's what I was going to suggest. I use it myself on Windows clients. http://synergy-project.org/
  4. Great upgrade! Thanks for all the hard work LT and Bonienl! Upgrade worked fine without any problems. Gary
  5. Thats my prediction. If the technology works correctly the extra PA power cost will likely be a fraction of the cost of a single component of a separate dedicated game machine. The key point is we need to prove it so we can then add that as a plus point to the technology. I would also be very interested in what that adding an extra GPU actually adds. Another user reported not very much but still would love to see a breakdown like: unRAID system with drives - no added GPU unRAID system with drives - add GPU - VM's Not Running unRAID system with drives - add GPU - VM's Running or similar to get an idea. I think this would be interesting to know. Compare this to a dedicated gaming rig and the power it consumes. Then calculate a months power consumption with 40 hours per month gaming usage with unRAID and a gaming VM vs. a dedicated gaming rig that only runs 40 hours per month. I'd be willing to bet that the additional power usage unRAID would consume for the month would still be less than that of a dedicated gaming rig. Gary
  6. My upgrade from v6.1 to v6.1.1 went well. This is actually the first time I have upgraded through the GUI. Very easy! Gary
  7. I would try re-downloading the file as it may have been a bad download. There is no "Run as Admin" for .msi files as they run as administrator already so you can just run them normally and you will be prompted with a warning that the application will need to modify some system settings. Gary
  8. Thanks for the information. I appreciate the detailed report and know that you guys often spend time chasing these bugs down. It's great to see people working together so diligently to get them fixed. Was this the bug that was fixed in 6.1.1? Gary
  9. If you don't plan on setting up any more VM's, you can edit your VM and remove the ISO by clearing the entry for it and save. Then you can delete the ISO file if you want to. I just keep mine on the array. They aren't very big and I might use it again later on. You can also remove the OS installation ISO too but save the ISO somewhere as you might need that one again. Gary
  10. Thanks for the blog post. It was very informative. I have wondered how Windows 7 and 8 upgrades to windows 10 have went with KVM virtualization.
  11. When trying to create a VM using OVMF and Q35, I get an error: Error creating VM: internal error: early end of file from monitor: possible problem: 2015-07-29T14:29:16.463297Z qemu-system-x86_64: -device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1: Can't create IDE unit 1, bus supports only 1 units 2015-07-29T14:29:16.463323Z qemu-system-x86_64: -device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1: Device initialization failed. 2015-07-29T14:29:16.463331Z qemu-system-x86_64: -device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1: Device 'ide-cd' could not be initialized I am using unRAID v6.0.1 release version. This error is produced by adding a VM under Advanced View and using a Custom Template. If I specify only the OS Install ISO and leave the VirtIO ISO field empty, the VM is created OK. Gary
  12. Very cool! I had tried PXE booting a long time ago using another guide here in the forums. My main use for it was for installing various operating systems and things like memtest and other boot CD tools. I'll have to give this a try. Gary
  13. I have been successful passing through a USB controller in Windows 10 but this was on an older beta. Here is my XML file for reference. I did GPU and USB controller pass through in this example. <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Win10Test</name> <uuid>b2444916-caa2-a6b8-10ab-162215a8f10f</uuid> <description>Win 10 Latest</description> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='5'/> <vcpupin vcpu='2' cpuset='6'/> <vcpupin vcpu='3' cpuset='7'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-2.2'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='2' cores='2' threads='1'/> </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'/> <source file='/mnt/cache/VMs/KVM/Win10Test/Win10Test.qcow2'/> <target dev='hda' 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/user/Programs/DreamSpark/Windows 10 Technical Preview - 9926/Windows10_TechnicalPreview_x64_EN-US_9926.iso'/> <target dev='hdc' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0' multifunction='on'/> </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:d3:ed:9e'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> <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=00:14.0,bus=root.1,addr=00.1'/> </qemu:commandline> </domain> The last 2 qemu:arg entry's are for the USB controller and I added the addresses to my vfio bind in the go file like so. /usr/local/sbin/vfio-bind 0000:01:00.0 0000:01:00.1 0000:00:14.0 Doing this required removing lines that were needed for VNC. These should not be in the XML. <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <input type='tablet' bus='usb'/> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='vmvga' vram='16384' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> I plugged my keyboard mouse and other USB devices into the controller that I passed through. Note though that things are different now where we don't use vfio bind anymore so I'm not sure if this would even work. I'll have to experiment with it myself to see if I can get it to work. EDIT: There is a new Windows 10 build out, 10162. It is a lot more polished and I've had no trouble with it. Gary
  14. I requested this a few months ago. http://lime-technology.com/forum/index.php?topic=37205.0 I mentioned a work around in that thread but things have changed since then. Now I change the license.txt file on the root of my flash drive and put my notes in there. I can then view them by clicking on the Tools -> EULA button. It works fine for now. Gary
  15. There are options available to use hdmi and usb over longer distances. Active HDMI cable http://www.monoprice.com/Product?c_id=102&cp_id=10255&cs_id=1025501&p_id=12609&seq=1&format=2 usb extension over cat5 http://www.monoprice.com/Product?c_id=103&cp_id=10303&cs_id=1030313&p_id=6042&seq=1&format=2 Have a look at meep's blog. I think you'll find some options on his site (Great site!) too. http://mediaserver8.blogspot.ie/ Gary
  16. Another approach to providing status details for yellow or red disks could be to have a "Status Details" tab on the "Main" page. Then the hover popup could be kept the way it is. On the "Status Details" tab you could list only the problem drives that might need attention with details for each one and maybe troubleshooting info. It's pretty common for users to ask questions when problems arise without providing any more info. Providing this info for troubleshooting on the "Status Details" page could help with that, like suggesting a syslog and smartdrive report for a red ball drive. Gary
  17. I think this should be simplified. Rather than trying to come up with a color / shape / blink icon for each possible state, stick with 3 icons. Then in the hover over popup box, explain the state in text. I think it was mentioned earlier, all the user is concerned about are 3 states: Green: everything is ok Yellow: warning that something the user should know about Red: critical problem that needs some attention Choose a different shape for green, yellow, and red to make it easier for colorblind people to differentiate between them. If you want to add a blinking icon for them (besides the solid icon), that gives you 6 states. But the hover over text would provide the details of each state that the drive / array is in. The less is more approach is better here in my opinion. Provide details in the hover over popup. Also, I'm not a fan of the separate spinup / spindown icon either. I'd prefer a onclick dropdown like you use on the VM page or a link in the popup if that's possible. I'm just voicing my opinion here but I do feel for those that can't see the icons clearly whether that is due to being colorblind or old age like me . 16 x 16 is kind of small! Gary
  18. When you get to the installation screen where you select the drive to install Windows on, you'll click the load drivers button and browse the CD drive to load the VIRTIO drivers. There are 3 drivers that you'll need to install (most likely) and you can install them all from that screen. Think they are Network, MemBaloon, and Storage drivers. Don't remember the exact names. Gary
  19. You might want to check out Synergy at http://synergy-project.org. I use it on my Windows systems and VM's. Not sure if there is a client for Slackware though. You might be able to compile it for yourself if your good with Linux. JonP would probably know more as I think he uses it too. Gary Edit: Here's the GitHub URL https://github.com/synergy/synergy
  20. Man, that's really nice! The video really grabs your attention and summarizes what unRAID 6 is capable of. Very professional looking. I'm thrilled with what you guys have done with unRAID 6! Gary
  21. Updated to RC3. APCUPSD doesn't autostart now. I've checked the settings and applied them, and then it runs. After a reboot though, it doesn't autostart. I confirmed that the dynamix.apcupsd folder and dynamix.apcupsd.cfg file is there on the flash drive. Syslog attached. Gary syslog.zip
  22. You might try checking if there is a bios update for your motherboard. I've had BSOD's with Windows 7 VM's and a bios update I did a few weeks back seem to have resolved them. What machine type, Q35 or i440fx? I think i440fx is the recommended type for Windows VM's now so you might want to give that a shot too. Gary
  23. I would be interested in this. If my unRAID machine should die, I would like to have the ability to plugin a USB key and boot off of it for the purpose of just running a VM. Or maybe just need to run a VM on another machine temporarily, like a laptop. I know some people use VM's for development purposes so being able to run the same VM that they have on their unRAID server on another machine would be really cool. I can see other use cases like an OpenElec VM that has been setup on unRAID copied to another PC and then running off of that. Gary