natty has seen the end of its life and is no longer receiving any
updates. Marking the natty task for this ticket as Won't Fix.
** Changed in: kvm (Ubuntu Natty)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Branch linked: lp:ubuntu/lucid-proposed/libvirt
** Branch linked: lp:ubuntu/maverick-updates/libvirt
** Branch linked: lp:ubuntu/natty-updates/libvirt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
This bug was fixed in the package libvirt - 0.8.3-1ubuntu19.4
---
libvirt (0.8.3-1ubuntu19.4) maverick-proposed; urgency=low
* New version of debian/patches/lxc-use-own-ptyfns.patch. Previous version
failed to build.
libvirt (0.8.3-1ubuntu19.3) maverick-proposed; urgency=low
This bug was fixed in the package libvirt - 0.8.8-1ubuntu6.7
---
libvirt (0.8.8-1ubuntu6.7) natty-proposed; urgency=low
* lxc_controller: use our own unlocpt+grantpt rather than glibc's, which
can't handle opening a pty in a devpts not mounted at /dev/pts.
(LP: #863629)
--
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kvm (Ubuntu Natty)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
In comment #104 Serge wrote that he did the verification on Maverick.
Based on that I'll update the tags.
** Tags removed: verification-needed
** Tags added: verification-done-maverick
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
nutznboltz, typically we require somebody who wasn't the developer
uploading the fix to verify it (Serge did the fix). However, with
maverick in its sunset ( 6 months of life left) I think we should
accept the fact the the surrounding releases, lucid and natty worked
fine with the same fix.
--
clint-fewbar, Thanks, I'll keep that in mind.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/350936
Title:
Should shut down domains on system shutdown
To manage notifications
Is anyone available to test this for natty and/or maverick?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/350936
Title:
Should shut down domains on system shutdown
To manage
I could test on Natty later today.
Adding link to pending SRU page for my convenience
http://people.canonical.com/~ubuntu-archive/pending-sru.html
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
Verified on maverick-proposed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/350936
Title:
Should shut down domains on system shutdown
To manage notifications about this bug go
Verified on natty-proposed.
$ dpkg -l | grep libvirt | awk '{print $2 $3}'
libvirt-bin 0.8.8-1ubuntu6.6
libvirt0 0.8.8-1ubuntu6.6
python-libvirt 0.8.8-1ubuntu6.6
$ lsb_release -ds
Ubuntu 11.04
$ uname -srvi
Linux 2.6.38-13-generic #52-Ubuntu SMP Tue Nov 8 16:53:51 UTC 2011 x86_64
$ cat
** Also affects: kvm (Ubuntu Natty)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Natty)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu Natty)
Status: New = Fix Committed
** Tags removed: verification-needed
** Tags added:
Resetting verification tags for missing maverick testing.
** Tags removed: verification-done verification-done-lucid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/350936
Title:
This bug was fixed in the package libvirt - 0.7.5-5ubuntu27.17
---
libvirt (0.7.5-5ubuntu27.17) lucid-proposed; urgency=low
* debian/libvirt-bin.upstart: add a pre-stop script to shut down running VMs
before the host shuts down. (LP: #350936)
* debian/libvirt-bin.default:
OK I've wrote something, that works on Lucid 10.04-3 without patching or
backporting
Just check the attachment!
Deshalb koennen Pinguine nicht fliegen. Was nicht fliegt kann nicht
abstuerzen.
have fun
** Attachment added: start-stop-script for vms running on Lucid amd6 KVM Host
sorry
the first one had errors!
here is a corrected version 1.0-1
** Attachment added: start-stop-script for vms running on Lucid amd64 KVM Host
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/350936/+attachment/2400328/+files/kvm-domains-1.0-1.tgz
--
You received this bug
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/350936
Title:
Should shut down domains on system shutdown
To manage notifications about this bug go
** Tags added: verification-done-lucid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/350936
Title:
Should shut down domains on system shutdown
To manage notifications about this
Hello exe, or anyone else affected,
Accepted libvirt into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
**
Tested on 10.04 64bit. Before installing the proposed package, guests'
/var/log/dmesg contained this after every time the host was shutdown (either
with shutdown command or by pressing power button):
[7.316252] EXT3-fs: INFO: recovery required on readonly filesystem.
[7.316256] EXT3-fs:
Hello exe, or anyone else affected,
Accepted libvirt into natty-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
**
** Description changed:
+ ===
+ SRU Justification
+ 1. Impact: libvirt VMs must be manually shut down before host shutdown, else
they will be corrupted.
+ 2. How bug was addressed: the libvirt upstart job will now try to shut down
all VMs before the host reboots or shuts
This bug was fixed in the package libvirt - 0.9.2-4ubuntu7
---
libvirt (0.9.2-4ubuntu7) oneiric; urgency=low
* libvirt-bin.upstart: add a pre-stop script to shut down running VMs
before the host shuts down. (LP: #350936)
-- Serge Hallyn serge.hal...@ubuntu.com Tue, 02 Aug
So is there any way the proper fix will make it into Lucid? Or has that
ship sailed?
In the meantime I have applied Sebastian Marsching's method which works
quite well. Thanks for that, Sebastian.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Also affects: kvm (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu Lucid)
Status: New = Triaged
** Changed in: libvirt (Ubuntu Lucid)
Importance: Undecided =
Andreas, yes, this should make it into lucid soon enough. We'll let
Serge's fix bake for about a week in oneiric, and then backport to
lucid. I don't know if we'll do the same for maverick and natty, though
its not out of the question (its just a matter of whether its important
enough to users).
Clint, great to hear, thanks. We have many Lucid servers in production,
but no Maverick or Natty, so the fix getting into Lucid is most
important for us. But if time and resources allow it, backporting the
fix to Maverick and Natty would certainly be nice.
--
You received this bug notification
** Changed in: libvirt (Ubuntu)
Importance: Medium = High
** Changed in: libvirt (Ubuntu)
Milestone: ubuntu-10.04.3 = ubuntu-11.10-beta-1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
** Changed in: libvirt (Ubuntu)
Assignee: Clint Byrum (clint-fewbar) = Serge Hallyn (serge-hallyn)
** Changed in: libvirt (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in
** Branch linked: lp:~serge-hallyn/ubuntu/oneiric/libvirt/fix-shutdown
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
https://bugs.launchpad.net/bugs/350936
Title:
Should shut down domains on system shutdown
To
Thanks to ossjunkie for your original script, most of which is in my
updated libvirt job.
I'm requesting a review by Spamaps for upstart oddities, but the script
in the linked tree is working for me.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Hello Guys,
I wanned to share my workarroud on this issue, Im using debian squeeze
as OS for a couple of virtualization hosts, each one of them holding a
number of vm's.
What I need is that when shuting down my virtualization host (from cli,
by cron, by ups low batt or by pressing the power
Here's my /etc/init.d/libvirt-bin file
** Attachment added: libvirt-bin
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/350936/+attachment/2248342/+files/libvirt-bin
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in
Is this fixed in ubuntu 10.04.3?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
https://bugs.launchpad.net/bugs/350936
Title:
Should shut down domains on system shutdown
To manage notifications about this bug go to:
Thank you, Sebastian, it works more awesome and came just in time.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
https://bugs.launchpad.net/bugs/350936
Title:
Should shut down domains on system shutdown
To manage
The problem of shutting down the virtual machines consists of two parts:
If a init-script is used, libvirtd might be killed, before the shutdown
command has been sent to the virtual machines. If the pre-stop script in
the libvirt-bin upstart job is used or a new upstart job starting on
stopping
This is really a show-stopper and spoils the otherwise solid solution to
use Ubuntu and KVM for virtualization.
Why did nobody propose yet to shut down the VMs by the qemu-kvm script?
I think stop qemu-kvm should try to shutdown all running kvms and kill
them after a timeout, independently of
Hi Clint,
Assigned this to you in the hopes you would reply to comment #79 :)
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) = Clint Byrum (clint-fewbar)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in
Shutdown is definitely on the radar for heavy testing this cycle, and I
hope to have a good solution for this bug soon. The bug in sendsigs
should hopefully become moot as we transition the shutdown to a more
upstart-aware solution.
** Tags added: upstart
--
You received this bug notification
** Changed in: libvirt (Ubuntu)
Importance: Low = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
https://bugs.launchpad.net/bugs/350936
Title:
Should shut down domains on system shutdown
--
Hi,
the proposed solution (patched sendsigs, libvirt-bin.conf, omit-kvm-vm-pids)
still does not work for me. I have done several tests with sendsigs and found
out that the corresponding pids of running virtuals are successfully included
in the omitpids array in sendsigs. Hovever, the virtuals
@Clint,
is there an open bug for sendsigs? Can you mark this bug as blocked on
that one?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.launchpad.net/bugs/350936
Title:
Should shut down domains on
Hi,
I have installed the latest mentioned files here (sendsigs, omit-kvm-vm-pid,
libvirt-bin.conf with 'break' command suggested by Martin Rusko) on our Lucid
64bit. servers, and it did not help. When doing a reboot, the system does not
wait for the domains to perform a clean shutdown...is
Hi Roman,
actually I ended up with molly-guard solution. It is suboptimal solution
because it stops your virtual machines only when shutdown/restart is
initiated manually (and only from remote ssh session). It won't apply if
UPS initiates shutdown or if power button is pressed shortly, etc.
In
On Fri, 2011-03-18 at 11:27 +, gollum53 wrote:
Hi,
I have installed the latest mentioned files here (sendsigs, omit-kvm-vm-pid,
libvirt-bin.conf with 'break' command suggested by Martin Rusko) on our Lucid
64bit. servers, and it did not help. When doing a reboot, the system does not
The problem with the upstart solution is that it doesn't work since
Upstart will kill the virsh instances that you spawn in
shutdown_guests.
So far the only somewhat satisfactory solution is molly-guard.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
On Fri, Mar 18, 2011 at 05:13:55PM -, Lars Hansson wrote:
The problem with the upstart solution is that it doesn't work since
Upstart will kill the virsh instances that you spawn in
shutdown_guests.
That's only the case if you don't follow the instructions to patch sendsigs
to avoid that
On Fri, 2011-03-18 at 17:13 +, Lars Hansson wrote:
The problem with the upstart solution is that it doesn't work since
Upstart will kill the virsh instances that you spawn in
shutdown_guests.
So far the only somewhat satisfactory solution is molly-guard.
Right, so you would need
** Changed in: libvirt (Ubuntu)
Milestone: ubuntu-10.04.2 = ubuntu-10.04.3
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.launchpad.net/bugs/350936
Title:
Should shut down domains on system
¿? Lenguage spanisch ??
Date: Wed, 2 Feb 2011 00:22:03 +
From: cl...@fewbar.com
To: jlguti...@hotmail.com
Subject: [Bug 350936] Re: Should shut down domains on system shutdown
Oops, just noticed, that should be $UPSTART_STOP_EVENTS
--
You received this bug
¿? LENGUAGE SPANISCH
Date: Tue, 1 Feb 2011 22:35:00 +
From: cl...@fewbar.com
To: jlguti...@hotmail.com
Subject: [Bug 350936] Re: Should shut down domains on system shutdown
Wow this one has been around a while.
The simplest way to run a script before
Orticio, this is an English-speaking forum. Please stop asking people to
speak Spanish.
Translated by Google:
Este es un foro de habla Inglés. Por favor, deje de pedir a la gente a
hablar español.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Wow this one has been around a while.
The simplest way to run a script before stopping, only on shutdown, but not on
restarts, is to use the UPSTART_EVENTS.
environment variable.
pre-stop script
if [ x$UPSTART_EVENTS = xrunlevel ] ; then
shutdown_guests
fi
end script
--
You received
Oops, just noticed, that should be $UPSTART_STOP_EVENTS
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in ubuntu.
https://bugs.launchpad.net/bugs/350936
Title:
Should shut down domains on system shutdown
--
Ubuntu-server-bugs
The same problem exist in 10.10 and John's posted workarounds are not working
there.
The only way I have managed to have the VM's shutdown is on halt/reboot is by
installing molly-guard. Not a wholly satisfactory solution but at least it
works.
--
You received this bug notification because
On John Morrissey's libvirt-bin.conf file ... there is construct like:
delay=$SHUTDOWN_TIMEOUT
while [ $delay -gt 0 ]; do
for uri in $URIS; do
if ! run_virsh -c $uri list | awk '$3 == running
{exit 1}'; then
Well placed 'break' command should make libvirt-bin.conf functioning
correctly.
** Patch added: libvirt-bin.conf.diff
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/350936/+attachment/1778008/+files/libvirt-bin.conf.diff
--
You received this bug notification because you are a member
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in ubuntu.
https://bugs.launchpad.net/bugs/350936
Title:
Should shut down domains on system shutdown
--
Ubuntu-server-bugs mailing list
I made the following changes to John's scripts for Lucid:
modified omit-kvm-vm-pids as follows:
changed directory: /lib/init/rw/sendsigs.omit.d to /var/run/sendsigs.omit.d
check for no qemu pids
modified sendsigs as follows:
changed directory: /lib/init/rw/sendsigs.omit.d to
revised omit-kvm-vm-pids
** Attachment added: omit-kvm-vm-pids
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/350936/+attachment/1762225/+files/omit-kvm-vm-pids
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in ubuntu.
Hmm. If libvirt shuts down the virtual machines it monitors, then these
virtual machines will also be shut down when updating libvirt.
--
Should shut down domains on system shutdown
https://bugs.launchpad.net/bugs/350936
You received this bug notification because you are a member of Ubuntu
Don't think so. It's part of the independence of libvirt from the the
actual virtualization technology (KVM, ...) to permit updates without
shutdown of guests.
2010/11/4 Valentijn Sessink valent...@sessink.nl:
Hmm. If libvirt shuts down the virtual machines it monitors, then these
virtual
The proposals in this report (mine, John Morrissey's) all have a pre-
stop shutdown of virtual machines in their Upstart conf-file.
When you update libvirt-bin, dpkg will stop libvirt-bin before
upgrading. As a result — if you have implemented the pre-stop shutdown —
your virtual machines will
On Thu, Nov 04, 2010 at 11:43:10AM -, Valentijn Sessink wrote:
The proposals in this report (mine, John Morrissey's) all have a pre-
stop shutdown of virtual machines in their Upstart conf-file.
When you update libvirt-bin, dpkg will stop libvirt-bin before
upgrading. As a result — if
On Sat, Oct 02, 2010 at 02:54:47AM -, Nathan Crawford wrote:
FWIW, you might want to mark /etc/default/libvirt-bin as a conffile in
the libvirt packaging.
I think it already is? (dpkg --status libvirt-bin says it is... but I've
been changing things all over the place so I might have
Sorry, I forgot to report back about the panics. They were caused by a
corrupted XFS filesystem on that server. I haven't had time to do any
further testing with my packages since then - I just hacked the shutdown
command to do what I needed until I have time to thoroughly test them.
--
Should
** Changed in: libvirt (Ubuntu)
Milestone: None = ubuntu-10.04.2
--
Should shut down domains on system shutdown
https://bugs.launchpad.net/bugs/350936
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
On Fri, Oct 01, 2010 at 03:47:07AM -, Nathan Crawford wrote:
@John Morrissey - Nice work on getting this working! I hope you don't
mind, I've taken the liberty of packaging all your changes and putting
them in a PPA for easier testing.
Thanks, and packaging the changes is no problem at
FWIW, you might want to mark /etc/default/libvirt-bin as a conffile in the
libvirt packaging.
I think it already is? (dpkg --status libvirt-bin says it is... but I've been
changing things all over the place so I might have confused it)
Also, it might make more sense to package
@John Morrissey - Nice work on getting this working! I hope you don't mind,
I've taken the liberty of packaging all your changes and putting them in a PPA
for easier testing.
One question on omit-kvm-vm-pids from #51, what does the '##*/' mean toward the
end of line 26?
--
Should shut down
Does anyone know what Canonical's *official* position on shutting down KVM VMs
on host shutdown with Upstart?
Does Canonical run Ubuntu 10.04 Server with KVM in production?
Do they shutdown VMs? How did this slip by for an LTS release?
Is this up to their standards as Production Quality?
Do
Clap! :)
2010/9/29 Andy a...@xillean.com:
It is a dismal situation when at this point there is still no official simple
way from Canonical to
gracefully shutdown KVM VMs if the host has to go down for any reason such as
a UPS issued shutdown command.
--
Should shut down domains on system
While there's many solutions now to shutdown VM's, here's my 2 cents. Instead
of a libvirt-bin.conf script, I made a separate script
(/usr/local/sbin/shutdown-libvirt-hosts.sh). This script waits 120 seconds for
all VM's to shut down. Then I'm running this script from two places; in
On Wed, Sep 22, 2010 at 09:47:47AM -, Valentijn Sessink wrote:
- if the shutdown script searches for the word running (like mine does,
- but John Morrissey's script is affected, too), it must set LANG=C at the
- top, otherwise virsh will run in the local language.
Good catch. I've updated
The attached file updates libvirt-bin's upstart job to gracefully shut
down VMs when the system shuts down. You can alter the shutdown timeout
(SHUTDOWN_TIMEOUT, default: 300s) and list of virsh(1) URIs to use
(URIS, default: qemu:///system) in /etc/default/libvirt-bin.
You'll also need the
** Attachment added: omit-kvm-vm-pids
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/350936/+attachment/1599117/+files/omit-kvm-vm-pids
--
Should shut down domains on system shutdown
https://bugs.launchpad.net/bugs/350936
You received this bug notification because you are a member
2010/9/17 John Morrissey j...@horde.net:
The attached file updates libvirt-bin's upstart job to gracefully shut
down VMs when the system shuts down. You can alter the shutdown timeout
(SHUTDOWN_TIMEOUT, default: 300s) and list of virsh(1) URIs to use
(URIS, default: qemu:///system) in
@francesco, #46
The packaging is cleaner and easier with the rc script running before sendsigs
(which is also an rc script). That way, the initscripts package/sendsigs
doesn't need to carry around special behavior for libvirt-bin and any other
packages that don't need this type of fix.
--
Er, s/don't need/need/
--
Should shut down domains on system shutdown
https://bugs.launchpad.net/bugs/350936
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing list
John (#44),
Thanks for your efforts. Looks like you really spent some time on this
and if it's working for you now, that's great.
I also banged my head on this - upstart, the conf, init, send-sigs etc.
and it's a real PITA :-) I couldn't get it working (guest FS always
needed an fsck for an
Sorry for not writing that long, there was lot to do at work.
My solution now for this problem is using a script that gets called by
molly-guard, as testing other script-stuff was really annoying! As Molly-Guard
installs it self as shutdown-command and executes each script inside
I've been banging my head on this for over a day, pretty sick of the
reboot/test cycle. Nothing seemed to work - and then I was pointed at
this bug on IRC in #ubuntu-server.
I think it is essential that a KVM host attempts a clean shutdown of any
guests on host reboot. It was quite disconcerting
Update**
In my comment #38 above step (2) I replaced the following modification in
/etc/init.d/sendsigs from.
while /bin/ls /var/run/libvirt/qemu/*.pid/dev/null 21 [
$kvm_shutdown_timeout -gt 0 ]
with:
while /usr/bin/pgrep -cx kvm /dev/null 21 [ $kvm_shutdown_timeout
-gt 0 ]
I have
Andy,
I didn't try your suggestion (yet), but is it really necessary to create
the kvmguests init script? Can't you just place the script inside the
pre-stop script section of /etc/init/libvirt-bin.conf?
Moreover, I've noticed that your kvmguests script uses upstart's 'start'
command to ensure
Reinhard, to answer you questions.
I created the init script first before I ran into this problem
The reason being was 1) to minimize modification of system files and 2) to be
able to shutdown guests on non-upstart versions of Linux. and 3) to enable
stopping all guests manually without
Ok I create a pre-stop script in /etc/init/libvirt-bin.conf
and it is running the script however its not waiting for the script to
complete.Everything shutsdown extremely fast in about 3 seconds and I am
back to the BIOS screen.
So the it starts shutting down the guest os but the host
Ok so I came up with a workaround that seems to be working for me. The
guests shutdown completely. Not sure what this breaks if anything.
There still needs to be a permanent fix for this bug but here is what I
did.
(1)
Edit /etc/init/libvirt-bin.conf
I added this under the pre-start script
So does this mean that KVM is not properly supported on Ubuntu 10.04
Server LTS? The ability to automatically shutdown VMs when someone logs
into a production host server and types /sbin/shutdown does not exist on
a server operating sytstem flagged LTS that is supposed to be for
production?
libvirt-bin gets shutdown by Upstart, so when you try to shutdown from
an init script, chances are that libvirt has shutdown already. So if you
want to do this, you need to change /etc/init/libvirt-bin.conf as well,
and have it wait for the VM's to shut down.
--
Should shut down domains on
This is implemented in libvirt 0.8.2:
https://bugzilla.redhat.com/show_bug.cgi?id=444273
** Bug watch added: Red Hat Bugzilla #444273
https://bugzilla.redhat.com/show_bug.cgi?id=444273
--
Should shut down domains on system shutdown
https://bugs.launchpad.net/bugs/350936
You received this
I'm still not sure, but doesn't the /etc/init.d/sendsigs script,
combined with the Ubuntu 10.04 /etc/init/rc.conf, make up for a giant
race condition? Where a shell script tries to find out which processes
it should not kill? This is, at least, what I'm making of it, when
running libvirt on a
I have seen the commit that implements this functionality and it's, as
usual, a sysvinit script. Unfortunately, I think this is a use case
where upstart can't do anything yet and the only solution (without
moving back to a sysvinit script) is doing an ugly workaround in
/etc/init.d/sendsigs. I've
~$ dpkg -S /etc/init/rc.conf
upstart: /etc/init/rc.conf
While rc.conf has nothing to do with shutting down virtual machines, it
does have the consequence of running the sendsigs script in parallel
with the upstart scripting. I'm not sure that is the right way to
proceed.
--
Should shut down
as i really needed a solution i did a dirty workaround for servers:
move /sbin/shutdown to /sbin/shutdown.real
place the attached script to /sbin/shutdown and make it executable
you can do the same for /sbin/reboot to have it run even on reboot,
halt, poweroff --force. you only need to change
i reworked the changes by tomcrus (thanks for the elegance ;) and
removed all reintroduced bashism. so here is the current of the core
logic to shutdown guests.
** Attachment added: libvirt-guest-shutdown-core
http://launchpadlibrarian.net/51116608/libvirt-guest-shutdown-core
--
Should shut
but i am still hanging on the upstart integration when using pre-stop in
libvirt-bin. while the condition regarding the runlevel by tomcrus works
great, it seems we are not able to simply delay the shutdown process
with a simple sleep. in my case i only managed to get the pre-stop
killed or make
instead of destroying vms, wouldn't be a more elegant solution to save
the state of the VM in a statefile?
On bootup, upstart would check for such statefiles and restore the
VMs. This would work even for VMs that don't react to ACPI events
properly and saves the VM's uptimes.
--
Should shut
Why are you not doing this in the pre-stop part of the libvirt-bin job,
by the way?
--
Should shut down domains on system shutdown
https://bugs.launchpad.net/bugs/350936
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
@soren: as i simple don't know how to trigger it only on shutdown, as
the premise was it should run on regular stop. but i know it may ease
the situation and would like to do so. do you know some solution here.
maybe we could do a simple condition that checks for an enviromental
stuff thats only
1 - 100 of 118 matches
Mail list logo
