On Fri, Jun 25, 2010 at 10:32:07AM -, ossjunkie wrote:
@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
As I'm currently setting up an intranet mail-server for my company
(based on lucid / ebox) in some kvm-guests and there for have exactly
the same problem. Reading all previous posts - and because I need kvm-
guest shutdown as well - I will use something like this:
Add following lines in
On Thu, Jun 24, 2010 at 08:04:48PM -, Francesco Pretto wrote:
why does libvirt-bin still stop before the libvirt-shutdown-guests
job has finished the script?
Good question. Upstart shouldn't be killing it, but something else
might. I can't imagine what, though.
I'm not sure Upstart isn't
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
@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
On Fri, Jun 25, 2010 at 10:32:07AM -, ossjunkie wrote:
@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
As I'm currently setting up an intranet mail-server for my company
(based on lucid / ebox) in some kvm-guests and there for have exactly
the same problem. Reading all previous posts - and because I need kvm-
guest shutdown as well - I will use something like this:
Add following lines in
thanks for the hint, but after trying i found that start on (runlevel
[06] and stopping libvirt-bin) should do the trick. but i still got
problems as i can use libvirt at first in the upstart job, but when
testing the timeout loop it seems that libvirt-bin still stopped before
the script finished.
On Thu, Jun 24, 2010 at 01:38:04PM -, ossjunkie wrote:
thanks for the hint, but after trying i found that start on (runlevel
[06] and stopping libvirt-bin) should do the trick. but i still got
problems as i can use libvirt at first in the upstart job, but when
testing the timeout loop it
2010/6/24 Soren Hansen so...@ubuntu.com:
why does libvirt-bin still stop before the libvirt-shutdown-guests job
has finished the script?
Good question. Upstart shouldn't be killing it, but something else
might. I can't imagine what, though.
I'm not sure Upstart isn't supposed to kill them.
thanks for the hint, but after trying i found that start on (runlevel
[06] and stopping libvirt-bin) should do the trick. but i still got
problems as i can use libvirt at first in the upstart job, but when
testing the timeout loop it seems that libvirt-bin still stopped before
the script finished.
On Thu, Jun 24, 2010 at 01:38:04PM -, ossjunkie wrote:
thanks for the hint, but after trying i found that start on (runlevel
[06] and stopping libvirt-bin) should do the trick. but i still got
problems as i can use libvirt at first in the upstart job, but when
testing the timeout loop it
2010/6/24 ossjunkie ossjun...@gmail.com:
why does libvirt-bin still stop before the libvirt-shutdown-guests job has
finished the script?
Because kvm guests processes aren't tracked by the upstart job and
they are killed immediately by /etc/init.d/sendsings. This approach
have pros
2010/6/24 Soren Hansen so...@ubuntu.com:
why does libvirt-bin still stop before the libvirt-shutdown-guests job
has finished the script?
Good question. Upstart shouldn't be killing it, but something else
might. I can't imagine what, though.
I'm not sure Upstart isn't supposed to kill them.
as this bug can corrupt guests i did an old school init script for my
server, but that doesn't work as libvirt-bin got always stopped before
(even at S01). so i removed all bashism like arrays and tried to create
an upstart script. the core logic is done, but i need some help
regarding upstart
On Wed, Jun 23, 2010 at 03:53:18PM -, ossjunkie wrote:
-how can we ensure in upstart that the script got run on shutdown
reboots but always before libvirt-bin and qemu-kvm got stopped?
I /think/ this should do the trick:
start on shutdown and stopping libvirt-bin
IIUIC, libvirt-bin will
as this bug can corrupt guests i did an old school init script for my
server, but that doesn't work as libvirt-bin got always stopped before
(even at S01). so i removed all bashism like arrays and tried to create
an upstart script. the core logic is done, but i need some help
regarding upstart
On Wed, Jun 23, 2010 at 03:53:18PM -, ossjunkie wrote:
-how can we ensure in upstart that the script got run on shutdown
reboots but always before libvirt-bin and qemu-kvm got stopped?
I /think/ this should do the trick:
start on shutdown and stopping libvirt-bin
IIUIC, libvirt-bin will
How about adding a pre-stop script to /etc/init/libvirt-bin.conf that
uses /usr/bin/virsh to iterate over all running guests to shut them
down? Probably this should be done a) in parallel and b) supervised by
reasonable timeouts. So technically, it might make sense to implement
that pre-stop
ignore my previous comment, I should have read the whole thread in more
detail.
--
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.
--
How about adding a pre-stop script to /etc/init/libvirt-bin.conf that
uses /usr/bin/virsh to iterate over all running guests to shut them
down? Probably this should be done a) in parallel and b) supervised by
reasonable timeouts. So technically, it might make sense to implement
that pre-stop
ignore my previous comment, I should have read the whole thread in more
detail.
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This is a very important issue for server virtualization. If Ubuntu
wants to be en par with Xen on other Distributions this bug has to be
fixed!
--
Should shut down domains on system shutdown
https://bugs.launchpad.net/bugs/350936
You received this bug notification because you are a member of
Note to anyone implementing this (maybe I'll get around to it myself,
but not right now):
It's important to remember that libvirt intentionally does not kill VM's
on termination. This enables us to upgrade libvirt without interruping
running VM's, so we want to only conditionally shut down VM's.
** Changed in: libvirt (Ubuntu)
Assignee: Dustin Kirkland (kirkland) = (unassigned)
--
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
2010/5/5 Soren Hansen so...@ubuntu.com:
It's important to remember that libvirt intentionally does not kill VM's
on termination. This enables us to upgrade libvirt without interruping
running VM's, so we want to only conditionally shut down VM's.
Correct.
What I've
done on one of my Hardy
This is a very important issue for server virtualization. If Ubuntu
wants to be en par with Xen on other Distributions this bug has to be
fixed!
--
Should shut down domains on system shutdown
https://bugs.launchpad.net/bugs/350936
You received this bug notification because you are a member of
Note to anyone implementing this (maybe I'll get around to it myself,
but not right now):
It's important to remember that libvirt intentionally does not kill VM's
on termination. This enables us to upgrade libvirt without interruping
running VM's, so we want to only conditionally shut down VM's.
** Changed in: libvirt (Ubuntu)
Assignee: Dustin Kirkland (kirkland) = (unassigned)
--
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
Bugs, which is subscribed to Ubuntu.
--
2010/5/5 Soren Hansen so...@ubuntu.com:
It's important to remember that libvirt intentionally does not kill VM's
on termination. This enables us to upgrade libvirt without interruping
running VM's, so we want to only conditionally shut down VM's.
Correct.
What I've
done on one of my Hardy
I'm not sure it can be done hacking upstart job. When libvirt was a
sysvinit script in ubuntu 9.10, I used this [1] script adding it in
stop function. In Lucid, if I add the same script to /etc/init
/libvirt-bin.conf with the stanza:
pre-stop exec shut-guests.sh 21 /var/log/shut-guests.log
This
Workaround:
Add the lines:
/usr/local/bin/shut-guests.sh 21 /var/log/shut-guests.log
/sbin/initctl emit guests-shutted
just after do_stop() { in /etc/init.d/sendsings
*and* changing the line:
stop on (runlevel [!2345])
on file /etc/init/libvirt-bin.conf to:
stop on
I'm not sure it can be done hacking upstart job. When libvirt was a
sysvinit script in ubuntu 9.10, I used this [1] script adding it in
stop function. In Lucid, if I add the same script to /etc/init
/libvirt-bin.conf with the stanza:
pre-stop exec shut-guests.sh 21 /var/log/shut-guests.log
This
Workaround:
Add the lines:
/usr/local/bin/shut-guests.sh 21 /var/log/shut-guests.log
/sbin/initctl emit guests-shutted
just after do_stop() { in /etc/init.d/sendsings
*and* changing the line:
stop on (runlevel [!2345])
on file /etc/init/libvirt-bin.conf to:
stop on
Hi
Any news for this bug? I want to convert my xen server to libvirt+kvm
but this bug it's really serious for me, it's not possible to automate
shutdown (ups or time based) or simply press power button to clean
shutdown without important modification to libvirt upstart script. Any
chance to
Hi
Any news for this bug? I want to convert my xen server to libvirt+kvm
but this bug it's really serious for me, it's not possible to automate
shutdown (ups or time based) or simply press power button to clean
shutdown without important modification to libvirt upstart script. Any
chance to
I think 5 minutes is very long for servers... I suggest two minutes.
--
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.
--
I think 5 minutes is very long for servers... I suggest two minutes.
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Summary changed:
- kvm stop rc
+ Should shut down domains on system shutdown
--
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.
--
** Summary changed:
- kvm stop rc
+ Should shut down domains on system shutdown
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
201 - 240 of 240 matches
Mail list logo
