libvirt users - Jul 2013 - Re: guests not shutting down when host shuts down

Michal wrote:
> -----Original Message-----
> From: Michal Privoznik [mailto:mprivozn@redhat.com]
> Sent: Wednesday, July 10, 2013 12:45 PM
> To: Lentes, Bernd
> Cc: libvirt-ML (libvirt-users@redhat.com)
> Subject: Re: [libvirt-users] guests not shutting down when
> host shuts down
>
> On 10.07.2013 11:37, Lentes, Bernd wrote:
> > Hi,
> >
> > i have a SLES 11 SP2 64bit host with three guests:
> > - Windows XP 32
> > - Ubuntu 12.04 LTS 64bit
> > - SLES 11 SP2 64bit
> >
> > The SLES guest shuts down with the host shutdown. The
> others not. When i shutdown these two guests with the
> virt-manager, they shutdown fine.
> > ACPI is activated in virt-manager for both of them. Acpid
> is running in the Ubuntu Client.
> > When the host shuts down, the two guests get a signal
> (excerpt from the log of the host:)
> >
> > ==========================================================> >
2013-07-07 16:39:51.674: starting up
> > LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/
> QEMU_AUDIO_DRV=none /usr/bin/qemu-kvm -S -M pc-0.15
> -enable-kvm -m 1025 -smp 1,sockets=1,cores=1,threads=1 -name
> greensql_2 -uuid 2cfbac9c-dbb2-c4bf-4aba-2d18dc49d18e
> -nodefconfig -nodefaults -chardev
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/greensql_2.mo
> nitor,server,nowait -mon
> chardev=charmonitor,id=monitor,mode=control -rtc base=utc
> -no-shutdown -drive
> file=/var/lib/kvm/images/greensql_2/disk0.raw,if=none,id=drive
> -ide0-0-0,format=raw -device
> ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bo
> otindex=1 -drive
> if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw
> -device
> ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0
> -netdev tap,fd=17,id=hostnet0,vhost=on,vhostfd=20 -device
> virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:37:92:a9,b
> us=pci.0,addr=0x3 -usb -vnc 127.0.0.1:2 -vga cirrus -device
> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4
> > Domain id=3 is tainted: high-privileges
> >
> > qemu: terminating on signal 15 from pid 24958
> >
> > 2013-07-08 13:58:29.651: starting up
> > =========================================================> >
> > I'm a bit astonished about "no-shutdown" in the
> commandline, but the sles guest also has it in its
> commandline, so it should not bother.
> >
> > I'm using kvm-0.15.1-0.23.1, libvirt-client-0.9.6-0.23.1,
> libvirt-0.9.6-0.23.1 and virt-manager-0.9.0-3.19.1 in the host.
> >
> > Thanks for any help.
> >
> >
> > Bernd
> >
>
> What's the LIBVIRTD_KVM_SHUTDOWN value (on my system it's in
> /etc/conf.d/libvirtd)? You want it to be 'shutdown'.
>
> Michal
>
Hi Michal,

i have neither this variable nor that file.
But i have /etc/syconfig/libvirt-guests:

=======================================================pc59093:/var/log/libvirt/qemu
# cat /etc/sysconfig/libvirt-guests
## Path: System/Virtualization/libvirt
## Type: string
## Default: default
# URIs to check for running guests
# example: URIS='default xen:/// vbox+tcp://host/system lxc:///'
URIS=default

## Type: string
## Default: start
# action taken on host boot
# - start   all guests which were running on shutdown are started on boot
#           regardless on their autostart settings
# - ignore  libvirt-guests init script won't start any guest on boot,
however,
#           guests marked as autostart will still be automatically started by
#           libvirtd
ON_BOOT=start

## Type: integer
## Default: 0
# number of seconds to wait between each guest start
START_DELAY=0

## Type: string
## Default: suspend
# action taken on host shutdown
# - suspend   all running guests are suspended using virsh managedsave
# - shutdown  all running guests are asked to shutdown. Please be careful with
#             this settings since there is no way to distinguish between a
#             guest which is stuck or ignores shutdown requests and a guest
#             which just needs a long time to shutdown. When setting
#             ON_SHUTDOWN=shutdown, you must also set SHUTDOWN_TIMEOUT to a
#             value suitable for your guests.
ON_SHUTDOWN=shutdown
====================================================
I changed "ON_SHUTDOWN" already from suspend to shutdown. I think this
should be the same.


Bernd



Helmholtz Zentrum München
Deutsches Forschungszentrum für Gesundheit und Umwelt (GmbH)
Ingolstädter Landstr. 1
85764 Neuherberg
www.helmholtz-muenchen.de
Aufsichtsratsvorsitzende: MinDir´in Bärbel Brumme-Bothe
Geschäftsführer: Prof. Dr. Günther Wess Dr. Nikolaus Blum Dr. Alfons Enhsen
Registergericht: Amtsgericht München HRB 6466
USt-IdNr: DE 129521671

Bernd wrote:
> >
> > What's the LIBVIRTD_KVM_SHUTDOWN value (on my system it's in
> > /etc/conf.d/libvirtd)? You want it to be 'shutdown'.
> >
> > Michal
> >
>
> Hi Michal,
>
> i have neither this variable nor that file.
> But i have /etc/syconfig/libvirt-guests:
>
> =======================================================>
pc59093:/var/log/libvirt/qemu # cat /etc/sysconfig/libvirt-guests
> ## Path: System/Virtualization/libvirt
> ## Type: string
> ## Default: default
> # URIs to check for running guests
> # example: URIS='default xen:/// vbox+tcp://host/system lxc:///'
> URIS=default
>
> ## Type: string
> ## Default: start
> # action taken on host boot
> # - start   all guests which were running on shutdown are
> started on boot
> #           regardless on their autostart settings
> # - ignore  libvirt-guests init script won't start any guest
> on boot, however,
> #           guests marked as autostart will still be
> automatically started by
> #           libvirtd
> ON_BOOT=start
>
> ## Type: integer
> ## Default: 0
> # number of seconds to wait between each guest start
> START_DELAY=0
>
> ## Type: string
> ## Default: suspend
> # action taken on host shutdown
> # - suspend   all running guests are suspended using virsh managedsave
> # - shutdown  all running guests are asked to shutdown.
> Please be careful with
> #             this settings since there is no way to
> distinguish between a
> #             guest which is stuck or ignores shutdown
> requests and a guest
> #             which just needs a long time to shutdown. When setting
> #             ON_SHUTDOWN=shutdown, you must also set
> SHUTDOWN_TIMEOUT to a
> #             value suitable for your guests.
> ON_SHUTDOWN=shutdown
> ====================================================>
> I changed "ON_SHUTDOWN" already from suspend to shutdown. I
> think this should be the same.
>
>
> Bernd
>
Hi,

for the Ubuntu guest i found a solution:

http://ubuntuforums.org/showthread.php?t=1972464


Bernd

Helmholtz Zentrum München
Deutsches Forschungszentrum für Gesundheit und Umwelt (GmbH)
Ingolstädter Landstr. 1
85764 Neuherberg
www.helmholtz-muenchen.de
Aufsichtsratsvorsitzende: MinDir´in Bärbel Brumme-Bothe
Geschäftsführer: Prof. Dr. Günther Wess Dr. Nikolaus Blum Dr. Alfons Enhsen
Registergericht: Amtsgericht München HRB 6466
USt-IdNr: DE 129521671

> >
> Hi,
>
> for the Ubuntu guest i found a solution:
>
> http://ubuntuforums.org/showthread.php?t=1972464
>
>
> Bernd
>
The windows guest didn't shutdown because i had a remotedesktop seesion on
it. After finishing it windows shut down properly.


Bernd

Helmholtz Zentrum München
Deutsches Forschungszentrum für Gesundheit und Umwelt (GmbH)
Ingolstädter Landstr. 1
85764 Neuherberg
www.helmholtz-muenchen.de
Aufsichtsratsvorsitzende: MinDir´in Bärbel Brumme-Bothe
Geschäftsführer: Prof. Dr. Günther Wess Dr. Nikolaus Blum Dr. Alfons Enhsen
Registergericht: Amtsgericht München HRB 6466
USt-IdNr: DE 129521671