I've been unable to solve this problem for a few weeks now, so i'll try posting it to my blog – maybe someone out there knows the answer. Would very much appreciate a clue on this one.
I've got a VM on a citrix xenserver 5.0.0 machine that won't start. it was running fine until it was rebooted on a Fri afternoon, a few weeks ago.
Starting it from the (windows-only) xencenter GUI results in:
"This VM cannot be started, as its network interfaces could not be connected. One of the NICs is in use elsewhere."
Starting it from the command line results in:
# xe vm-start uuid=88915b63-d794-e021-4f78-b03f46e352b0 Cannot plug VIF VIF: 5dfd3886-8b48-20e5-4231-30284d7b185d
anyone seen this before? know how to fix?
I've tried deleting and re-creating the network interface for the VM. I've also tried booting the VM without any network interface at all. I've tried "xe vif-unplug –force uuid=5dfd3886-8b48-20e5-4231-30284d7b185d" (doesn't work, expects the VM to be running, not halted). In fact, I've lost track of all the things i've tried doing that haven't worked.
I haven't rebooted the xen server and *really* don't want to have to do that. I'd rather create a new VM and copy the OS (debian, fortunately so relatively easy to do) than reboot the server (NOTE: Tried that, didn't work).
Since the initial problem, I now have a total of three VMs that won't restart (with the same error message), and I can't even create a new VM. So it looks like a problem with the host rather than the guest. I think i'm going to have to migrate all the VMs off this machine to another box, then rebuild this server. maybe with a newer Xen (on debian, rather than proprietary citrix junk), or maybe as a KVM box.
The (absence of) this kind of crap is one of the main reasons why i prefer KVM to Xen….and if i have to rebuild the server anyway, I may as well rebuild it as a KVM server