Jan 11 04:03:59 XS03 SM: File "/opt/xensource/sm/LVMoISCSISR", line 535, in scan Jan 11 04:03:59 XS03 SM: File "/opt/xensource/sm/SRCommand.py", line 159, in _run_locked Jan 11 04:03:59 XS03 SM: File "/opt/xensource/sm/SRCommand.py", line 110, in run Jan 11 04:03:59 XS03 SM: ***** generic exception: sr_scan: EXCEPTION, The VDI is not available Jan 11 04:03:59 XS03 SM: Raising exception ] Jan 11 04:03:58 XS03 SM: LVMCache: refreshing When trying to "SR rescan" on this SR we get error "VDI is not available" in XenCenter. Some days later more and more VMs state "The snapshot chain is too long" and no new snapshots can be created from VMs using VDIs residing on that problematic SR. But it seems that this broken VDI still is available *somewhere* and may be there are more problems within the SR. After that we deleted the original VM including the broken VDI. Creating a new VM from the 2nd newest snapshot worked and new VM is up and running. Reverting to the latest snapshot did not work because it seems broken. After shutting down this VM it did not restart with error "VDI is not available". I'm not a XenServer veteran, so any help, correction, or request for clarification is greatly appreciated.Between dec, 27th and 28th *something* happend to our XenServer 7.6 system (3 hosts) with multipath attached iSCSI-StorageRepositories.Īs we encountered hanging VMs we restarted the master host and everything seemed fine.īut later we realized that scheduled snapshots of ONE VM are not created anymore. Other VMs that were not shutdown with destroy_domain may move freely to and from this server. It looks like an issue with the destroy_domain command I issued above. The production VM is CentOS, so I don't think I'm experiencing anything operating system specific.
Xen server vdi not available windows 7#
I discovered this issue on one of our production VM servers, but these tests are being performed on a throw-away Windows 7 Enterprise VM. Unfortunately, the VM can still not be migrated and produces the same errors above. If I force shut-down the VM, I may then re-start it. In addition, XenCenter pops up a dialog saying "Error starting VM", with an error for each server in the pool saying "Object has been deleted.VDI:OpaqueRef:NULL. There were no servers available to complete the specified operation. Attempting to resume it (still on the original server, since it couldn't move) produces the following error in the server event log:
Attempting to migrate the VM to another host in the pool via XenCenter produces the following error after about 30-40 seconds: Migrating VM 'Cleanup 7' from XenBlade5 to XenBlade 6:Įrror: Internal error: file "xapi_xenops.ml", line 1740, characters 3-9: Assertion Failed. I have found though that attempting to migrate the VM to any other server in the pool though.
It worked, and I was able to start up the VM without issue.
Xen server vdi not available full#
A different article pointed me to the full path at /opt/xensource/debug/xenops destroy_domain -domid x With the exception that my command line didn't seem to have the destroy_domain command. Recently, I had to force a shutdown of a VM by destroying the domain via these instructions: HA is normally used, but is currently turned off for this operation. I have a three XenServer 6.1 servers in a pool.
0 kommentar(er)
