VM Settings "disappeared" ???

I was making some changes in the amount of ram of my VM and after that I'm unable to change any properties.

I'm unable to STOP, EDIT, SHUTDOWN, etc, it simply doesn't appear the menu.

I'm also unable to create a new VM, the button does nothing.

 

The VM is running, I can access to it.

 

I have tried stopping the array and shutting down the computer without luck.

 

What can I try?

(I'm still in 6.1.9)

 

Thankyou

Gus

 

Updated to 6.2 but the error persist.

Nothing happens when I clic on the icon to start/stop/etc the VM.

 

 

Add diagnostics files to see if someone can help me.

 

Thankyou

Gus

tower-diagnostics-20160922-1129.zip

Looking at your diagnostics, this is the only thing jumping out at me in your syslog:

 

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000022

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000023

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000024

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000025

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000026

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000027

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000028

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000029

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x4000002a

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x4000002b

 

Unfortunately I don't see a lot of details on this message, but my first thought would be to try disabling Hyper-V for the Windows VM.  Can you navigate to other tabs in the webGui while it's in this state?  Can you try stopping the array?  Can you connect via putty to your system?  Try this command:

 

virsh destroy "Windows 10 unRaid"

 

That should force shutdown the VM.

@jonp

 

but my first thought would be to try disabling Hyper-V for the Windows VM.

I can't edit the xml (if there's the option to disable Hyper-V)

 

Can you navigate to other tabs in the webGui while it's in this state?

Yes, no problem with the whole system except VM's.

 

Can you try stopping the array?

Yes, no problem also. I have stoped, rebooted. (My VM is set to autostart, I have un-check it but when rebooted autostart is enabled and vm up and running)

 

Can you connect via putty to your system?  Try this command: virsh destroy "Windows 10 unRaid"

Yes. I have done it and has killed the VM, but after a reboot all the same. The VM up and running. No way to edit any VM.

 

I have tried SETTING / VM MANAGER / DISABLE VM... rebooted... ENABLE VM and the same.

 

I don't know what can happen.

 

Referent to "Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000022" errors you saw they only can be related to an error in the xml. I don't know why but a mistake was done while editing the xml in ? (textedit/notepad) .I din't remember the editor I used to copy and save the xml but replaced the ' key in <vcpupin vcpu='1' cpuset='3'/> for another key. I don't know if this can be related.

 

What else can I try?

 

I'm a noob user and dind't have any problem since now, I was only editing the xml I can't explain how can I have done this mess and how the system let me do that.

 

Is there any way to delete those vm's and try to recreate a new ones if there's no solution?

 

Thankyou

Gus

 

 

 

 

Looking at your diagnostics, this is the only thing jumping out at me in your syslog:

 

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000022

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000023

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000024

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000025

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000026

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000027

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000028

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000029

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x4000002a

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x4000002b

 

Unfortunately I don't see a lot of details on this message, but my first thought would be to try disabling Hyper-V for the Windows VM.  Can you navigate to other tabs in the webGui while it's in this state?  Can you try stopping the array?  Can you connect via putty to your system?  Try this command:

 

virsh destroy "Windows 10 unRaid"

 

That should force shutdown the VM.

@jonp

 

but my first thought would be to try disabling Hyper-V for the Windows VM.

I can't edit the xml (if there's the option to disable Hyper-V

 

Can you navigate to other tabs in the webGui while it's in this state?

Yes, no problem with the whole system except VM's.

 

Can you try stopping the array?

Yes, no problem also. I have stoped, rebooted. (My VM is set to autostart, I have un-check it but when rebooted autostart is enabled and vm up and running)

 

Can you connect via putty to your system?  Try this command: virsh destroy "Windows 10 unRaid"

Yes. I have done it and has killed the VM, but after a reboot all the same. The VM up and running. No way to edit any VM.

 

I have tried SETTING / VM MANAGER / DISABLE VM... rebooted... ENABLE VM and the same.

 

I don't know what can happen.

 

Referent to "Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000022" errors you saw they only can be related to an error in the xml. I don't know why but a mistake was done while editing the xml in ? (textedit/notepad) .I din't remember the editor I used to copy and save the xml but replaced the ' key in <vcpupin vcpu='1' cpuset='3'/> for another key. I don't know if this can be related.

 

What else can I try?

 

I'm a noob user and dind't have any problem since now, I was only editing the xml I can't explain how can I have done this mess and how the system let me do that.

 

Is there any way to delete those vm's and try to recreate a new ones if there's no solution?

 

Thankyou

Gus

 

 

 

 

Looking at your diagnostics, this is the only thing jumping out at me in your syslog:

 

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000022

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000023

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000024

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000025

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000026

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000027

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000028

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x40000029

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x4000002a

Sep 22 00:44:04 Tower kernel: kvm [16111]: vcpu3 Hyper-V unhandled rdmsr: 0x4000002b

 

Unfortunately I don't see a lot of details on this message, but my first thought would be to try disabling Hyper-V for the Windows VM.  Can you navigate to other tabs in the webGui while it's in this state?  Can you try stopping the array?  Can you connect via putty to your system?  Try this command:

 

virsh destroy "Windows 10 unRaid"

 

That should force shutdown the VM.

 

If you disable auto-start for the VM, then start the array, can you still not edit the VM?

@jonp

 

If you disable auto-start for the VM, then start the array, can you still not edit the VM?

 

Disable vm autostart, stop the array, start the array, go to VM tab and windows 10 vm is up and running. No matter I have un-checked autostart.

 

If I un-check autostart, change to another label (docker, plugins, etc) and return to vm, it's checked again also.

 

Here you have the windows 10 vm log if help:

 

2016-09-22 19:45:17.683+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Tower

Domain id=1 is tainted: high-privileges

Domain id=1 is tainted: host-cpu

char device redirected to /dev/pts/0 (label charserial0)

2016-09-22T21:17:53.476943Z qemu-system-x86_64: terminating on signal 15 from pid 15776

2016-09-22 21:17:53.533+0000: shutting down

2016-09-22 21:20:40.575+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Tower

Domain id=1 is tainted: high-privileges

Domain id=1 is tainted: host-cpu

char device redirected to /dev/pts/0 (label charserial0)

 

Thankyou

Gus

 

@jonp

 

If you disable auto-start for the VM, then start the array, can you still not edit the VM?

 

Disable vm autostart, stop the array, start the array, go to VM tab and windows 10 vm is up and running. No matter I have un-checked autostart.

 

If I un-check autostart, change to another label (docker, plugins, etc) and return to vm, it's checked again also.

 

Here you have the windows 10 vm log if help:

 

2016-09-22 19:45:17.683+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Tower

Domain id=1 is tainted: high-privileges

Domain id=1 is tainted: host-cpu

char device redirected to /dev/pts/0 (label charserial0)

2016-09-22T21:17:53.476943Z qemu-system-x86_64: terminating on signal 15 from pid 15776

2016-09-22 21:17:53.533+0000: shutting down

2016-09-22 21:20:40.575+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Tower

Domain id=1 is tainted: high-privileges

Domain id=1 is tainted: host-cpu

char device redirected to /dev/pts/0 (label charserial0)

 

Thankyou

Gus

 

The Windows 10 VM log is not showing anything unusual.  the "tainted" message isn't an error and is absolutely normal.  Your issue is very odd though that nothing you do seems to impact things.  So if you do a virsh destroy command from command line and go back to the VMs tab, you still see the VM running and cannot edit it?

Can you try using another web browser instead of what you're using just to see if it's browser related?

@jonp

 

So if you do a virsh destroy command from command line and go back to the VMs tab, you still see the VM running and cannot edit it?

No, the virsh command destroy/stop the VM but I can't edit nor start, etc. I can't do anything. When I click on the icon where I must get the menu nothing happens.

 

Can you try using another web browser instead of what you're using just to see if it's browser related?

Was the first I tried thinking that it could be related to flash or similar. Tried on my mac under OS X with safari, chrome and firefox and under windows (also on my mac bootcamp) with firefox. Also tried inside windows 10vm with firefox.

 

 

 

 

 

Jon is not there an option to delete all and start fresh with VM's? (not the whole system as I have some dockers and configurations I would like not to re-configure again)

 

Otherwise is a problem that can happen to other people because as a "basic" user I was only modifying the xml properties of the OS X vm when I make some mistakes in the config that "blocked" all the VM section.

 

*** I have created an openelec vm to test without problems, but still the same, once created impossible to do anything else. It does nothing when I click over the icon. At the right of each icon there's a label with the name of the VM, if it helps it points to 192.168.1.168/VMs#

 

*** How is created this "contextual" menu when you click over the vm icon? Is there any other icon on the gui in any section that behaves equal to try?

 

Thankyou

Gus

 

If there's NO solution to my problem, what would be the best way to start fresh?

 

Can I delete the flash disk, copy a fresh 6.2, re-assign all the drives as before and start the array?

Would the shares/users be re-created?

 

Then I would have to configure al the dockers and VMs I have.

 

Thankyou

Gus

If there's NO solution to my problem, what would be the best way to start fresh?

 

Can I delete the flash disk, copy a fresh 6.2, re-assign all the drives as before and start the array?

Would the shares/users be re-created?

 

Then I would have to configure al the dockers and VMs I have.

 

You are welcome to use the Starting Over wiki, same page discusses many of the files on the flash drive.  However I have no VM experience, and have not added any mention of VM specific files.  Happy too if someone is willing to help with that.

Thankyou @RobJ @jonp

 

Is not there an option to flush/wipe only the part related to VM's

 

You are welcome to use the Starting Over wiki, same page discusses many of the files on the flash drive.  However I have no VM experience, and have not added any mention of VM specific files.  Happy too if someone is willing to help with that.

 

I have read the wiki but I don't clearly see any section in the wiki that's related to VM's on the flash drive.

 

I could try to make a fresh install and recover:

-Network

-Drive Assigments

-Drive Settings

-Share Settings

-User / passwords

 

About dockers I think that for the 3 or 4 I have, I could simply write the settings and start over.

I suppose I have to delete/disable the dockers and delete the content of appdata from cache drive, right?

The only "problematic" docker will be crashplan, I also suppose if I delete the docker all my data in crashplan cloud will stay there?

 

Thankyou

Gus

 

About dockers I think that for the 3 or 4 I have, I could simply write the settings and start over.

I suppose I have to delete/disable the dockers and delete the content of appdata from cache drive, right?

You only need to toast the appdata if you're having problems with the dockers.  If not, then no point in doing so.

 

But, if you're formatting the cache drive or something and have zero problems with your docker apps, then make a backup of it using CA's backup / restore module, format the drive, and then restore it.

 

Haven't looked at the "starting over guide", but if you're wiping the flash drive, then save the contents of /config/plugins/dockerMan/templates-user and then restore them onto the flash drive after you're done.  That way CA and its previous apps section can take care of reinstalling the apps with the exact same settings as before

 

Before doing anything more drastic this should delete all things VM related:

 

Settings -> VM Manager -> Disable VMs

 

On the same page check the box to delete image file and apply

 

Re-enable VMs

 

All your VMs will be gone, try to create a new one, you can re-use your vdisks if needed.

 

 

@johnnie.black

 

Before doing anything more drastic this should delete all things VM related:

 

Settings -> VM Manager -> Disable VMs

 

On the same page check the box to delete image file and apply

 

Re-enable VMs

 

All your VMs will be gone, try to create a new one, you can re-use your vdisks if needed.

 

Settings / VM Manager / Enable VMs to NO -> Apply

 

On the same page check the box to delete image file and apply

I suppose you are referring to :

Libvirt store location "/mnt/user/system/libvirt/libvirt.img  --> Delete Image File

Click on delete image file and Delete button and done.

 

Re-enable VMs and tachan, they are still there.

 

No matter what I do once re-enabled I have the same vm's.

I see that has deleted the openelec vm I create after the problem, but the win & mac vm's I had are still there.

 

Gus

 

 

I see that has deleted the openelec vm I create after the problem, but the win & mac vm's I had are still there.

 

That is strange  , don't have more ideas, maybe time to format your flash drive and start from the beginning.

 

 

I see that has deleted the openelec vm I create after the problem, but the win & mac vm's I had are still there.

 

That is strange  , don't have more ideas, maybe time to format your flash drive and start from the beginning.

 

Thankyou all the people that has tried to help me.

At last there has been no solution and I have done a fresh install.

I has been a hard way to teach me how to restore the system and vm's.

 

Only to say that vm's are working now as expected but I have lost a little confidence in the system.

 

Thankyou

Gus

 

Not a big VM guy, but what about deleting /config/plugins/dynamix.kvm.manager/domains.img on the flash drive

Not a big VM guy, but what about deleting /config/plugins/dynamix.kvm.manager/domains.img on the flash drive

 

too late !!! I have reinstalled all.

 

Thankyou @squid I'll try it next time if there's next time !!!

 

Gus