Marking this fix released. Guests now by default have acpid installed.
If they do not, it is a bug in the client (as they leave no clean way
for libvirt to request a clean reboot).
** Changed in: libvirt (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification
0.9.3 libvirt has native qemu/kvm reboot support baked in now.
--
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/368962
Title:
Can't reboot kvm virtual machines using virsh
To manage
Yup, but unless you've installed acpid, it'll do exactly nothing. Just
FYI.
I'm honestly not sure whether Ubuntu server does that by default these
days.
Sent from my phone. Pardon my brevity.
Den 02/09/2011 17.27 skrev Neil Wilson n...@aldur.co.uk:
0.9.3 libvirt has native qemu/kvm reboot
As acpid is required in guest VMs for the Upstart pre-stop procedure to
work, I'd like to suggest that acpid be included by default in Ubuntu
Server virtual machine variants (or all Ubuntu Server default installs,
for that matter). This will enable this feature to automatically work as
expected in
Could someone point me to documentation on how to send an ACPI signal to
a vm so I can script my own solution as has been suggested?
Andrew: It appears that the xml already has room for this:
http://libvir.org/formatdomain.html#elementsFeatures
I have been able to shutdown by installing acpid
virsh shutdown sends an ACPI shutdown to the VM.
Or you can use the ruby/python bindings if you prefer.
On 5 January 2011 15:36, flickerfly josiah.ritc...@gmail.com wrote:
Could someone point me to documentation on how to send an ACPI signal to
a vm so I can script my own solution as has
This is a known missing feature in libvirt/KVM and as such should be
Wishlist.
** Changed in: libvirt (Ubuntu)
Importance: High = Wishlist
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Triaged
--
Can't reboot kvm virtual machines using virsh
I understand this isn't severe but in the interests of trying to solve a
problem would it be possible to define an element in the XML definition
which is equivalent to saying 'This domain supports ACPI'. If this flag
is set ( it can default to off) then those who know their domain
supports acpi
Which I consider a severe bug ;) (and I am affected as well)
--
Can't reboot kvm virtual machines using virsh
https://bugs.launchpad.net/bugs/368962
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
I really don't consider this High importance at all[1], and I doubt this
will get fixed any time soon, if ever. There's simply no portable way
(that I can think of, at least) to reboot a fully virtualised operating
system, and until there is, such a method cannot be exposed through the
libvirt
The severity is a matter opinion, but if several users feel it is severe
to them, it qualifies as High, as per the provided link.
As for 'no portable way...to reboot...', most (if not all) OS's respect
ACPI.
And, in a similar vein, if you can walk up to a physical machine, most
physical machines
Just to add, that concept of 'power down - reset' is apparently what was
suggested on the fedora side [1], it just hasnt been implemented.
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=496537#c5
--
Can't reboot kvm virtual machines using virsh
https://bugs.launchpad.net/bugs/368962
You
Power off via ACPI, if it powers off, power it back on again else
report 'refuse to respond to ACPI shutdown'.
Simples
On 25 April 2010 14:23, Soren Hansen so...@ubuntu.com wrote:
I really don't consider this High importance at all[1], and I doubt this
will get fixed any time soon, if ever.
On Sun, Apr 25, 2010 at 01:44:32PM -, Andrew Bolster wrote:
The severity is a matter opinion, but if several users feel it is severe
to them, it qualifies as High, as per the provided link.
To be perfectly honest, I have a hard time taking it seriously that it's
supposedly a severe
On Sun, Apr 25, 2010 at 02:00:11PM -, Neil Wilson wrote:
Power off via ACPI, if it powers off, power it back on again else
report 'refuse to respond to ACPI shutdown'.
So you would have the call hang for some amount of time until you decide
that by then it should have shut down and then
Oh, by the way, as for most OS's support ACPI, an Ubuntu Server
installation does not do so out of the box. I consider that a bug, by
the way, but nevertheless, that is the case and has been years.
So, if this feature depended on the guest OS handling ACPI events at
all, it'd sadly fail on
On 25 April 2010 16:20, Soren Hansen so...@ubuntu.com wrote:
So you would have the call hang for some amount of time until you decide
that by then it should have shut down and then return failure? How long
would you suggest? Remember, libvirt API calls are not asynchronous, so
Pick a number.
On Sun, Apr 25, 2010 at 04:35:25PM -, Neil Wilson wrote:
So you would have the call hang for some amount of time until you
decide that by then it should have shut down and then return failure?
How long would you suggest? Remember, libvirt API calls are not
asynchronous, so
Pick a number.
Per the redhat bug above, this is not a bug so much as a known missing
feature.
** Bug watch added: Red Hat Bugzilla #496537
https://bugzilla.redhat.com/show_bug.cgi?id=496537
** Also affects: libvirt (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=496537
Importance: Unknown
** Summary changed:
- [Jaunty] Can't reboot kvm virtual machines using virsh
+ Can't reboot kvm virtual machines using virsh
--
Can't reboot kvm virtual machines using virsh
https://bugs.launchpad.net/bugs/368962
You received this bug notification because you are a member of Ubuntu
Server Team,
20 matches
Mail list logo
