KVM Guest Not Running But Cannot Stop Either

Home » CentOS » KVM Guest Not Running But Cannot Stop Either
CentOS 3 Comments

I am working with a cloned vm. In the process of (re-)adding an additional virtio disk I received a notice that the change could not be made to a running instance. Which was curious because I had shut that v down. Now I cannot get it to start from virt-manager, the run selection is greyed out. If I try and pause it from the graphical vm details interface then I get a message that the vm is not running.

I can start the vm from virsh but I cannot get a console, neither graphical nor serial. The thing looks hosed to me but before I blow it away I though that I would ask is there is anything I can do to recover it. I am concerned that this sort of thing is even possible.

3 thoughts on - KVM Guest Not Running But Cannot Stop Either

  • These are the messages that I get when trying to attach a virtio disk to or perform a shutdown of the problem vm guest.

    Add hardware

    This device could not be attached to the running machine. Would you like to make the device available after the next guest shutdown?

    Requested operation is not valid: cannot do live update a device on inactive domain

    Traceback (most recent call last):
    File “/usr/share/virt-manager/virtManager/addhardware.py”, line
    1095, in add_device
    self.vm.attach_device(self._dev)
    File “/usr/share/virt-manager/virtManager/domain.py”, line 756, in attach_device
    self._backend.attachDevice(devxml)
    File “/usr/lib64/python2.6/site-packages/libvirt.py”, line 403, in attachDevice
    if ret == -1: raise libvirtError (‘virDomainAttachDevice()
    failed’, dom=self)
    libvirtError: Requested operation is not valid: cannot do live update a device on inactive domain

    Shutdown domain:

    Error shutting down domain: Requested operation is not valid: domain is not running

    Traceback (most recent call last):
    File “/usr/share/virt-manager/virtManager/asyncjob.py”, line 44, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
    File “/usr/share/virt-manager/virtManager/asyncjob.py”, line 65, in tmpcb
    callback(*args, **kwargs)
    File “/usr/share/virt-manager/virtManager/domain.py”, line 1106, in shutdown
    self._backend.shutdown()
    File “/usr/lib64/python2.6/site-packages/libvirt.py”, line 1566, in shutdown
    if ret == -1: raise libvirtError (‘virDomainShutdown() failed’, dom=self)
    libvirtError: Requested operation is not valid: domain is not running

    They seem to be mutually exclusive and yet occur together nonetheless.