Skip to main content

VM stuck in an invalid state

NOTE: this information is not my own experience and was resolved by other people, but I found it interesting and it exists on a site that is not easy to search and I may not always have access to. (Honestly: the whole thing doesn't make much sense to me at this point, but it has some pretty stellar troubleshooting bits in there...)

The user had an issue with a VM being unavailable and this was the resolution.


2012-02-21 16:55:59,524 INFO  [org.ovirt.engine.core.bll.StopVmCommand] (pool-12-thread-49) Running command: StopVmCommand internal: false. Entities affected :  ID: a55532fa-066b-4329-a551-07b1bce6d577 Type: VM
2012-02-21 16:55:59,527 WARN  [org.ovirt.engine.core.bll.VmOperationCommandBase] (pool-12-thread-49) Strange, according to the status "NotResponding" virtual machine "a55532fa-066b-4329-a551-07b1bce6d577" should be running in a host but it isnt.
2012-02-21 16:55:59,558 ERROR [org.ovirt.engine.core.bll.StopVmCommand] (pool-12-thread-49) Transaction rolled-back for command: org.ovirt.engine.core.bll.StopVmCommand.

If I try to force-remove the VM - since no important content is on it, here is what I get back :

[root@rhevm ~]# curl -X DELETE -H "Accept: application/xml" -H "Content-type: application/xml" -u admin@internal:[] --cacert /root/ca.crt -d "<action><force>true</force></action>"  https://[]:8443/api/vms/a55532fa-066b-4329-a551-07b1bce6d577

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><fault><reason>Operation Failed</reason><detail>[Cannot remove VM. VM is running.]</detail></fault>




[root@rhevm ~] # yum info rhevm
Name        : rhevm
Arch        : x86_64
Version     : 3.0.2_0001
Release     : 2.el6

[root@rhevm ~] #  rhn-channel --list
jbappplatform-5-x86_64-server-6-rpm
rhel-x86_64-server-6
rhel-x86_64-server-6-rhevm-3
rhel-x86_64-server-supplementary-6

ssh to RHEV-M host as root
[root@rhevm ~] # service jbossas stop 
[root@rhevm ~] # psql -U rhevm  rhevm
  rhevm=# update vm_dynamic set status = 0 where vm_guid = 'a55532fa-066b-4329-a551-07b1bce6d577' ;  
  rhevm=# \q
[root@rhevm ~] # 
Labels:

Comments

Post a Comment

Popular posts from this blog

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...
1 comment
Read more

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...
1 comment
Read more

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.
Post a Comment
Read more