March 20, 201610 yr After upgrading to the new beta (and checking over all of the changes/warnings) the status in VM manager says disabled. I've changed some settings in advance mode to match where the files are located and it stayed that way. Turning it off and then on didn't solve it either. Is there something I can do to fix this otherwise I looks like it's back to 6.1.9? Pictures on request since I don't know what'd be relevant to everyone here. Thank you. ground-diagnostics-20160320-1047.zip
March 20, 201610 yr After upgrading to the new beta (and checking over all of the changes/warnings) the status in VM manager says disabled. I've changed some settings in advance mode to match where the files are located and it stayed that way. Turning it off and then on didn't solve it either. Is there something I can do to fix this otherwise I looks like it's back to 6.1.9? Pictures on request since I don't know what'd be relevant to everyone here. Thank you. Perhaps you should post a screenshot of where it says disabled? As far as I could see there was nowhere in VM Manager that displays that - the closest was whether Enable VM's was set to Yes or No - is that what you meant? Obviously to be able to run VMs this needs to be set to Yes.
March 20, 201610 yr Author Attached will be the screenshot of what I see. All of the file paths should be right with the status in the top right. My array is started I just took the picture before it was. After checking it didn't make a difference whether it was or not as the status still said disabled either way.
March 20, 201610 yr I changed the iso and vm image locations but I left the libvirt location unchanged and set as mnt/user/system/libvirt/libvirt.img (which ends up on the cache disk as the 'system' share is set as cache only. It might be worth leaving yours at that to see if it makes a difference. I think the VM settings from 6.1.9 are auto-migrated to that location.
March 20, 201610 yr If I remember correctly, jonp said that libvirt.img has to be in the path or else it will not work. Was somewhere in the beta threads.
March 20, 201610 yr Author Tried a few new things though nothing's working. Where can I download the libvirt.img as I can't find it anywhere? Also I have two virtIO isos in my folder after downloading and cannot see them in explorer even with hidden files enabled. They show up in unRaid's GUI, though.
March 20, 201610 yr Tried a few new things though nothing's working. Where can I download the libvirt.img as I can't find it anywhere? Also I have two virtIO isos in my folder after downloading and cannot see them in explorer even with hidden files enabled. They show up in unRaid's GUI, though. IT should be created by unraid. You did try to put libvirt.img in the path?
March 20, 201610 yr Author Tried a few new things though nothing's working. Where can I download the libvirt.img as I can't find it anywhere? Also I have two virtIO isos in my folder after downloading and cannot see them in explorer even with hidden files enabled. They show up in unRaid's GUI, though. IT should be created by unraid. You did try to put libvirt.img in the path? Yes, that was one of the new things I tried earlier.
March 21, 201610 yr Author Fixed it. libvirt.img cannot be anywhere other than /mnt/cache/libvirt.img even if you put it in a folder that /is/ the cache drive. It must specifically be that exact path. Once I make it /mnt/cache/libvirt.img the status changes.
March 21, 201610 yr Fixed it. libvirt.img cannot be anywhere other than /mnt/cache/libvirt.img even if you put it in a folder that /is/ the cache drive. It must specifically be that exact path. Once I make it /mnt/cache/libvirt.img the status changes. Well mine is at /mnt/user/system/libvirt/libvirt.img which is where the upgrade process put it and that works fine for me. Since the 'system' share is set as cache only that is a the same as /mnt/cache/system/libvirt/libvirt.img
March 21, 201610 yr Author Fixed it. libvirt.img cannot be anywhere other than /mnt/cache/libvirt.img even if you put it in a folder that /is/ the cache drive. It must specifically be that exact path. Once I make it /mnt/cache/libvirt.img the status changes. Well mine is at /mnt/user/system/libvirt/libvirt.img which is where the upgrade process put it and that works fine for me. Since the 'system' share is set as cache only that is a the same as /mnt/cache/system/libvirt/libvirt.img /mnt/user/Virtual Machines/libvirt.img is also cache only and didn't work for me so it's strange you had better luck than me. At least future users upgrading can look into this thread in case they run into similar and use what we've both experienced.
March 21, 201610 yr Fixed it. libvirt.img cannot be anywhere other than /mnt/cache/libvirt.img even if you put it in a folder that /is/ the cache drive. It must specifically be that exact path. Once I make it /mnt/cache/libvirt.img the status changes. Well mine is at /mnt/user/system/libvirt/libvirt.img which is where the upgrade process put it and that works fine for me. Since the 'system' share is set as cache only that is a the same as /mnt/cache/system/libvirt/libvirt.img /mnt/user/Virtual Machines/libvirt.img is also cache only and didn't work for me so it's strange you had better luck than me. At least future users upgrading can look into this thread in case they run into similar and use what we've both experienced. It is probably the space in the folder name that was the fault. I guess you only tried with a folder that contained a space? If that is the case you should post it in the beta thread so limetech is aware of the bug.
September 22, 20169 yr itimpi or others, should some advice from this thread be put into the Additional Upgrade Advice? If so, how should it be worded? (I haven't created a VM yet)
September 22, 20169 yr Author itimpi or others, should some advice from this thread be put into the Additional Upgrade Advice? If so, how should it be worded? (I haven't created a VM yet) Thanks for the link. I'll save it and reference it in the future.
September 22, 20169 yr Can someone help me with a problem similar to that. I can access to VM (and one vm is up and running) but I CAN'T do anything. I can't STOP, SHUTDOWN, EDIT XML, etc... I simply does nothing when I click on the VM icon. I was on 6.1.9 after changing some parameters. Update to 6.1.2 without luck, the problem persists. Here you have images and explanation: http://lime-technology.com/forum/index.php?topic=52100.0 Thankyou Gus
September 22, 20169 yr Author Can someone help me with a problem similar to that. I can access to VM (and one vm is up and running) but I CAN'T do anything. I can't STOP, SHUTDOWN, EDIT XML, etc... I simply does nothing when I click on the VM icon. I was on 6.1.9 after changing some parameters. Update to 6.1.2 without luck, the problem persists. Here you have images and explanation: http://lime-technology.com/forum/index.php?topic=52100.0 Thankyou Gus Please create your own thread since this one has been solved.
September 22, 20169 yr Please create your own thread since this one has been solved. Sorry @krone6 I did it, but thought it was similar to this one and perhaps someone could give me a clue. I didn't find any thread similar to my problem and haven't had any answer to my "particular" problem. 2 days without been able to use VMs. Thankyou Gus
October 10, 20169 yr ... Please create your own thread since this one has been solved. I am sorry, but was the resolution to choose a cache drive? Because i upgraded to 6.2.1 and can`t use VMs anymore as well. And i don`t have a cache drive. So do i need to buy a new drive just for my VMs?
October 10, 20169 yr Author itimpi or others, should some advice from this thread be put into the Additional Upgrade Advice? If so, how should it be worded? (I haven't created a VM yet) Thanks for the link. I'll save it and reference it in the future. I forgot and for some reason didn't update my original post with the resolution. Since then I've upgraded to each new release as it gets updated so whatever the latest version is is the one I'm on now and the VMs work fine, though they're still super picky sometimes.
Archived
This topic is now archived and is closed to further replies.