GHunter

I also noticed some problems in the <clock /> node in the XML while experimenting tonight. <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> With a Windows 7 and a Windows 10 VM, if either of those <timer /> lines were in my XML, the latest Nvidia drivers would not install correctly. Without modifying the XML for either of the VM's, I could install Nvidia driver version 340.52 without any issue or errors. Once I removed the 2 <timer /> lines like so: <clock offset='localtime'> </clock> I was then able to install the latest Nvidia drivers without any issues in both VM's and they seem to be running just fine. One issue I have left to play with in regards to Nvidia drivers is the CPU that is being reported to Windows and the Nvidia Gaming Experience. The CPU is being reported as an QEMU Virtual CPU Version 2.2.0 3.60 GHz. I am pretty sure I read somewhere on the libvirt website that you can change how the CPU is reported to the guest OS. Hope this info is helpful for those experiencing driver install problems. Edit: Here is the link on CPU model information. http://libvirt.org/formatdomain.html#elementsCPU Gary

beta14b install we well and seems to be working good. My spin down issues have been fixed in this version too. Thanks. I know this problem was a tough one to find. Gary

Found the bug and corrected it ! Thanks for testing. Thanks. This issue is fixed in beta 14b. Gary

My update to beta 14a went fine. My drives are spinning down normally too. I'm having some webGUI issues where it seems to hang. I think it might be related to setting the page update frequency to real time under the display settings but I haven't done enough testing with it to be sure. webGUI doesn't seem to be hanging with the page update frequency set to disabled. I'll have to test more. I'm also seeing the status on the main page and dashboard page as spun down when it is really spun up. I noticed this with page update frequency set to disabled. I need to test more on this too. One other thing I have been seeing (since beta 13?) is my notification email for "array is active" is missing disk 1 and 2. This is consistent where this email never has disk 1 and 2 included in it. Here is the contents of the email and syslog attached: Event: unRAID active array Subject: Notice [FILESVR] - array is active Description: Array has 9 active disks (including parity & cache) Importance: normal Parity disk - ST3000DM001-1CH166_W1F1WJCM (sdb) (30 C) Disk 3 - ST3000DM001-1ER166_W500JBH3 (sdf) (27 C) Disk 4 - WDC_WD20EARS-00MVWB0_WD-WMAZA3888280 (sdg) (26 C) Disk 5 - ST3000DM001-1CH166_Z1F4AP89 (sdl) (29 C) Disk 6 - ST3000DM001-1ER166_Z5007S1K (sdk) (28 C) Disk 7 - ST3000DM001-1CH166_W1F1WJ9Y (sdj) (30 C) Disk 8 - ST3000DM001-1CH166_W1F1WHCQ (sdi) (29 C) Disk 9 - WDC_WD20EARS-00MVWB0_WD-WCAZA4999014 (sdm) (23 C) Cache disk - WDC_WD6400AAKS-00A7B0_WD-WMASY1070643 (sdc) (32 C) Gary syslog.zip

The "active" notification email that I am sent doesn't report the status correctly. Here is my email contents: Disk 1 and 2 are also spun up but not listed in the email message. I've also got an "active" email notification where only disk 7 was reported as being spun up. But all disks were really spun up. Disks spin up normally when accessed and I have no problems with this operating as it should. Just the email message is inaccurate. All drives are on the same spin up group. I'll attach a syslog in case it is helpful. Thanks, Gary syslog.txt

Probably not. We have not had an opportunity to properly test out 4.5. There are supposedly a large number of changes that could affect existing configurations, so without proper testing against that, we wouldn't feel comfortable putting out a release. An upgrade to the Xen version would be something for consideration for 6.1, not 6.0. Ok. I understand and realize that it isn't just a matter of updating some files. I see there is some updates to QEMU and that might help with KVM and some stability issues I've had. Or maybe not. Who knows. I'll play around with it more and see what happens. I haven't spent a whole lot of time with it because Xen works so well. Gary

Thanks for the update. I was really hoping for an update to Xen! Will you guys be updating Xen in the next beta or RC? Gary

See this post here: http://lime-technology.com/forum/index.php?topic=36527.msg341361#msg341361 There is a missing file in the download. Gary

I did and think it is a nice enhancement! Really looks good and hope that it is easy for other plugin authors to implement. Thanks for the updates to these awesome plugins! Gary

Change the "Home" page to "Dashboard" instead of "Main" and rename the "Main" page to something else, like "Array". When you go to http://Tower in your web browser, it would make more sense to show the "Dashboard" page first as that is more of an array overview. The "Main" page needs a more suitable name like "Array" or something along those lines. You could go a step further and make it user configurable, but I don't think that is necessary. I thought I read somewhere that this change was in discussion but I thought I would bring it up here as I've thought about this myself. Gary

I backup all my Windows PC's to unRAID using Windows Backup and Restore by creating a Windows System Image of the C: drive. I use a batch file that is scheduled on each Windows PC. The first time it runs it takes a while but the incremental backups take just a few minutes. Here is an example of my batch file contents: wbAdmin start backup -backupTarget:\\TOWER\Backups -include:C: -allCritical -quiet If you really want to run WHS for this, I'd setup a VM using unRAID and Xen or KVM, and install WHS on it and then go that way. It seems like a lot of trouble to migrate drives and tear down an unRAID server just for this purpose. Of course, if you are just trying to get rid of 1 unRAID server and consolidate some hardware, then I can understand you going forward with this. Just something to think about. Gary

Here is my error: Warning: libvirt_domain_create_xml(): internal error: early end of file from monitor: possible problem: 2014-12-25T04:32:52.796650Z qemu-system-x86_64: -device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1: Can't create IDE unit 1, bus supports only 1 units 2014-12-25T04:32:52.796671Z qemu-system-x86_64: -device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1: Device initialization failed. 2014-12-25T04:32:52.796679Z qemu-system-x86_64: -device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1: Device 'ide-cd' could not be initialized in /usr/local/emhttp/plugins/dynamix.kvm.manager/classes/libvirt.php on line 173 I've tried several times using different iso files and locations. Gary Which of your systems is this on? Can you give me an example of a working config? Did you get an error with a name only? Maybe I can specify the bus in the create xml. No, I didn't get an error with a name only when creating a vm. Here is a screenshot of my info using the create vm tab that throws the error. This is a working xml config with Windows 10 and GPU, mouse, and keyboard pass-through. Ok got it. Thanks. No ide for q35. My issue is resolved. I've been able to create several VM's just fine. Thanks again.

Cool. I'll try again after you post an update to the plugin.

Here is my error: Warning: libvirt_domain_create_xml(): internal error: early end of file from monitor: possible problem: 2014-12-25T04:32:52.796650Z qemu-system-x86_64: -device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1: Can't create IDE unit 1, bus supports only 1 units 2014-12-25T04:32:52.796671Z qemu-system-x86_64: -device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1: Device initialization failed. 2014-12-25T04:32:52.796679Z qemu-system-x86_64: -device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1: Device 'ide-cd' could not be initialized in /usr/local/emhttp/plugins/dynamix.kvm.manager/classes/libvirt.php on line 173 I've tried several times using different iso files and locations. Gary Which of your systems is this on? Can you give me an example of a working config? Did you get an error with a name only? Maybe I can specify the bus in the create xml. No, I didn't get an error with a name only when creating a vm. Here is a screenshot of my info using the create vm tab that throws the error. This is a working xml config with Windows 10 and GPU, mouse, and keyboard pass-through. <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Windows 10</name> <uuid>cbeab418-cc59-41a1-9d87-17da907ab5ef</uuid> <description>Windows 10 Tech Preview x64</description> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <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> <cpu mode='host-passthrough'> <topology sockets='2' cores='2' threads='1'/> </cpu> <os> <type arch='x86_64' machine='pc-q35-2.1'>hvm</type> <boot dev='cdrom'/> <bootmenu enable='no'/> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> </hyperv> </features> <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/SSD/KVM/Windows10/Windows10.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/user/Programs/DreamSpark/Windows 10 Tech Preview/WindowsTechnicalPreview-x64-EN-US.iso'/> <target dev='sdc' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/Programs/Virtualization ISOs/virtio-win-0.1-94.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:88:b8:de:13'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </interface> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc31c'/> </source> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc05a'/> </source> </hostdev> <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:commandline> </domain>

Here is my error: Warning: libvirt_domain_create_xml(): internal error: early end of file from monitor: possible problem: 2014-12-25T04:32:52.796650Z qemu-system-x86_64: -device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1: Can't create IDE unit 1, bus supports only 1 units 2014-12-25T04:32:52.796671Z qemu-system-x86_64: -device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1: Device initialization failed. 2014-12-25T04:32:52.796679Z qemu-system-x86_64: -device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1: Device 'ide-cd' could not be initialized in /usr/local/emhttp/plugins/dynamix.kvm.manager/classes/libvirt.php on line 173 I've tried several times using different iso files and locations. Gary

Thanks. I'll give it a try again and report back.

Yeah, I have 4 VM's created now and have run all of them. I've done about 10 total in testing. I've had a couple of xml errors due to bad paths to an ISO image but no other problems during the creation by Add XML tab. Thanks again.

Think it is not working when choosing to Create a New Disk. Using an Existing Disk does work. It is odd though as choosing to Create a New Disk does create the sub-folder and qcow2 image but doesn't finish creating the VM nor do I get a confirmation message or any errors in the creation process. Gary

Do you have a network bridge setup in unRAID webgui? Did the plugin say it created it successfully at the bottom of the page? It sounds like there was an error during libvirt create. You should be able to just enter a name and nothing else then click create vm. Yes, I have a network bridge setup as br0. It does not say it was successfully created at the bottom. Since you mentioned it, I put in a name for a VM and changed nothing else, and a VM was created successfully and I got a confirmation at the bottom of the page. So there must be something else on the Create VM tab that is causing a problem. I'll play with it a bit and report back. Thanks.

I finally have had the time to play with this plugin and KVM! I setup my spare USB flash drive with a fresh copy of unRAID 6b12 and your plugins (Virtman and KVM Manager v2014.12.21a). The create VM tab doesn't seem to setup VM's properly. It creates the sub-folder and qcow2 image but doesn't actually create the VM as there are no VM's listed under the Virtual Machines tab after clicking the Create VM button. Am I doing something wrong? I have been using Add XML tab to create my VM's instead. This has worked out really well and I have created several VM's this way. I even passed through my GPU, keyboard, and mouse on my 1st attempt! This is an awesome plugin and I appreciate all the work you have put into it. This will go a long way into easing people into creating VM's under KVM hypervisor. Gary

Both WeeboTech and bjp999 add some great ideas. I do use the extended features available in the unMenu and MyMain plugin for drive information like place and date purchased, warranty expiration, etc. I was unaware of the SMART attribute tracking feature though. My feeling though is that SMART attribute tracking should be part of notifications. I don't want to have to look at the attributes every so often but would rather be notified when they change and what the new values are and what they were and the time lapse between the changes. The changed attributes most of us care about is reallocated sector count but id like to see this somewhat configurable and some threshold values for the ones we configure to track and notify us about. Gary

Thought it would be cool to have a Custom Notes page similar to the Release Note and EULA pages. This would be a place for the user to add whatever notes and forum links or whatever that they might want to add and view it in unRAID under the Tools menu. As an example, I modified the Readme.txt file on the root of my flash drive to add my notes. Now I can view them and click the links to take me to forum pages! Gary readme.txt

I found a newer version of sensors-detect which found my super I/O chip correctly where the version in unRAID didn't. It might help those of you using the System Temp plugin on newer motherboards / chipsets. I just downloaded the file to my flash drive saving it as SD.sh and then ran it. You might have to set permissions to make it executable but I didn't. Here is a link to the lm-sensors page where the link can be found. http://www.lm-sensors.org/wiki/Devices. I'm going to post this in the system temp plugin thread too. Gary

I found a newer version of sensors-detect which found my super I/O chip correctly where the version in unRAID didn't. It might help those of you using the System Temp plugin on newer motherboards / chipsets. I just downloaded the file to my flash drive saving it as SD.sh and then ran it. You might have to set permissions to make it executable but I didn't. Here is a link to the lm-sensors page where the link can be found. http://www.lm-sensors.org/wiki/Devices. I'm going to post this in the system temp plugin thread too. Gary

I wanted to let you know that in the process of upgrading a drive and expanding the file system (Replacing a 2TB drive with a 3TB drive), I got a warning and an alert browser notification and emails. They aren't very descriptive yet, but I know it is still a work in progress. Thank you guys! Gary