Home / server / Questions / 875367
In Process
Mircea Vutcovici
Asked: 2017-09-26 06:42:00 +0800 CST

VM started, but it is not listed by virsh

  • 772

I have a VM started by TripleO setup script for OpenStack. I can connect to the VM console with vncviewer. The problem is that the VM is not listed by virsh.

$ sudo virsh list --all
 Id    Name                           State
----------------------------------------------------

$ ps -edf |grep qemu
stack     6451     1 30 Sep24 ?        04:29:15 /usr/libexec/qemu-kvm -name undercloud -S -machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off,dump-guest-core=off -cpu Opteron_G3,+vme,+ht,+mmxext,+fxsr_opt,+pdpe1gb,+3dnowext,+3dnow,+cmp_legacy,+extapic,+cr8legacy,+3dnowprefetch,+osvw,+ibs,+skinit,+wdt,+nodeid_msr,-avx,-avx2 -m 12288 -realtime mlock=off -smp 6,sockets=6,cores=1,threads=1 -uuid 7c9db9d9-846f-480a-aefd-608eb257c379 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/home/stack/.config/libvirt/qemu/lib/domain-1-undercloud/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -boot menu=off,strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/home/stack/pool/undercloud.qcow2,format=qcow2,if=none,id=drive-virtio-disk0 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=24,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:04:31:27:f2:40,bus=pci.0,addr=0x3 -netdev tap,fd=25,id=hostnet1 -device virtio-net-pci,netdev=hostnet1,id=net1,mac=00:04:31:27:f2:3e,bus=pci.0,addr=0x4 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:0 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on
root     10232 20111  0 10:32 pts/0    00:00:00 grep --color=auto qemu
$
linux

1 Answers

  1. I found in the logs written by ansible with journalctl -b, that ansible virt module was invoked with uri=qemu:///session. This means that the VM is started as stack user and it is visible and managed only by that user.

    The following link explains the differences between qemu:///system and qemu:///session URI: http://blog.wikichoon.com/2016/01/qemusystem-vs-qemusession.html

    To see the VM in my case I need to run:

    $ sudo -u stack -i virsh list --all
 Id    Name                           State
----------------------------------------------------
 1     undercloud                     running
 8     control_0                      running
 9     compute_0                      running

$
    • 3