[Ovirt-devel] poweroff in vm causes the host to become unavailable

Justin Clacherty justin at redfish-group.com
Tue Jul 28 05:40:53 UTC 2009


Ian Main wrote:
> On Thu, 09 Jul 2009 10:50:15 +1000
> Justin Clacherty <justin at redfish-group.com> wrote:
>
>   
>> If  I ssh to a vm running Centos and then execute "poweroff" from within 
>> the vm, the vm shuts down as expected but the host in the admin ui 
>> becomes unavailable.  Is anyone else experiencing this?  I haven't 
>> checked to see if other guest OS's do the same thing yet.
>>     
>
> The host becomes unreachable when the QMF libvirt object representing the
> host is not available or the agent backing that object stops sending 
> heartbeats.
>
> Can you run:
>
> # ruby /usr/share/ovirt-server/qmf-libvirt-example.rb
>
> And see if the host object in question shows up?

Hi Ian,

I've had this happen again.  When I run the ruby script it shows the 
host which is unavailable and also shows all the unreachable VMs (some 
of the output is below).  How do I get the GUI to recognise the node is 
there so I can manage things again (without restarting)?  I'd rather not 
have to restart everything as then I have to deal with the iSCSI 
wierdness which is going on.

Is there anything else you'd like me to check while it's in this state?

Cheers,
Justin.


[root at management ~]# ruby /usr/share/ovirt-server/qmf-libvirt-example.rb
Connecting to amqp://management.ovirt.priv:5672..
node: node91.ovirt.priv
  property: hostname, node91.ovirt.priv
  property: uri, qemu:///system
  property: libvirtVersion, 0.6.3
  property: apiVersion, 0.6.3
  property: hypervisorVersion, 0.9.1
  property: hypervisorType, QEMU
  property: model, x86_64
  property: memory, 8195028
  property: cpus, 4
  property: mhz, 2666
  property: nodes, 1
  property: sockets, 1
  property: cores, 4
  property: threads, 1
getXMLDesc() status: 0
getXMLDesc() status: OK
xml length: 1087
  domain: Trixbox, state: running, id: 1
    property: uuid, 815ad1a6-95c3-fb43-710f-dca6441476a8
    property: name, Trixbox
    property: id, 1
    property: node, 0-1-1-29-1
    property: state, running
    property: numVcpus, 1
    property: active, true
getXMLDesc() status: 0
getXMLDesc() status: OK
xml length: 1039
  domain: Alfresco, state: running, id: 2
    property: uuid, b028e774-67fe-8d4d-69be-45e081d8fb01
    property: name, Alfresco
    property: id, 2
    property: node, 0-1-1-29-1
    property: state, running
    property: numVcpus, 1
    property: active, true
getXMLDesc() status: 0
getXMLDesc() status: OK
xml length: 1086
  domain: Ontime, state: running, id: 3
    property: uuid, 1e3692a3-3166-8070-908a-e8a1f8d168c2
    property: name, Ontime
    property: id, 3
    property: node, 0-1-1-29-1
    property: state, running
    property: numVcpus, 1
    property: active, true
getXMLDesc() status: 0
getXMLDesc() status: OK
xml length: 1086
  domain: Services, state: running, id: 6
    property: uuid, 23a47161-3004-495e-da6a-28ec494a6960
    property: name, Services
    property: id, 6
    property: node, 0-1-1-29-1
    property: state, running
    property: numVcpus, 1
    property: active, true
getXMLDesc() status: 0
getXMLDesc() status: OK
xml length: 1096
  domain: Kernel Dev, state: running, id: 14
    property: uuid, 935f781d-9aad-a75d-b546-4478ebbe94e6
    property: name, Kernel Dev
    property: id, 14
    property: node, 0-1-1-29-1
    property: state, running
    property: numVcpus, 2
    property: active, true
getXMLDesc() status: 0
getXMLDesc() status: OK
xml length: 1279
  domain: Repositories, state: running, id: 17
    property: uuid, 9017129d-0a66-cfc7-328c-0ccf827c966b
    property: name, Repositories
    property: id, 17
    property: node, 0-1-1-29-1
    property: state, running
    property: numVcpus, 1
    property: active, true




More information about the ovirt-devel mailing list