similar to: guest state "in shutdown"

Hi all, I've got a weird issue, and I'm trying to confirm if it's a bug, and if so, if there is a workaround until it is fixed. The situation is this: If I virsh reboot <domain> --mode acpi, it will actually reboot the domain cleanly (watching from the console allows me to see the full shutdown messages, followed by a bootup). However, after this point, virsh domstate

On Tue, Jul 05, 2016 at 02:50:25PM +0200, Roland Everaert wrote: > Hello, > > We are currently facing a strange situation. One of our VM is shown by > 'virsh list' as in state "in shutdown" but there is no more a qemu-kvm > process linked to it. > > So we have a few questions: > > 1. What does means the state in shutdown (I have not found much

Hello, We are currently facing a strange situation. One of our VM is shown by 'virsh list' as in state "in shutdown" but there is no more a qemu-kvm process linked to it. So we have a few questions: 1. What does means the state in shutdown (I have not found much information about it)? 2. How to cleanly "shutdown" the vm, or more correctly, clean the status in

On Wed, Aug 26, 2020 at 10:35:22PM +0200, Milan Zamazal wrote: > Hi, > > we have a problem in oVirt that highly available VMs don't restart after > host poweroff because Vdsm identifies the case as a user initiated > shutdown (https://bugzilla.redhat.com/1800966). > > When poweroff is run on the host, libvirt-guests service takes an > action. If oVirt is initiating a

"Daniel P. Berrange" <dan@berrange.com> writes: > On Wed, Aug 26, 2020 at 10:35:22PM +0200, Milan Zamazal wrote: >> Hi, >> > >> we have a problem in oVirt that highly available VMs don't restart after >> host poweroff because Vdsm identifies the case as a user initiated >> shutdown (https://bugzilla.redhat.com/1800966). >> >>

Hi, we have a problem in oVirt that highly available VMs don't restart after host poweroff because Vdsm identifies the case as a user initiated shutdown (https://bugzilla.redhat.com/1800966). When poweroff is run on the host, libvirt-guests service takes an action. `virsh shutdown' is run on the VM, the guest OS is shut down cleanly and libvirt reports a shutdown event with

Restarting libvirtd doesn't change the situation. But looking into the logs I see the following: - Last lines in /var/log/libvirt/libvirtd.log: 2016-07-05 13:26:42.792+0000: 24552: warning : qemuProcessKill:4419 : Timed out waiting after SIGKILL to process 48301 2016-07-05 13:26:42.792+0000: 24552: error : qemuDomainDestroyFlags:2120 : operation failed: failed to kill qemu process with

At Fri, 11 Jul 2014 05:27:46 +0000, Michael D wrote: > > I am currently running LibVirt with Qemu on Debian Wheezy: > > Versions: > > - libvirtd (libvirt) 1.2.4 > - qemu-x86_64 version 2.0.0 (Debian 2.0.0+dfsg-4~bpo70+1), Copyright (c) > 2003-2008 Fabrice Bellard > > It's all working perfectly, including ACPI: virsh shutdown guest. However > when I

Description of problem: libvirt 3.9 on CentOS Linux release 7.4.1708 (kernel 3.10.0-693.21.1.el7.x86_64) on Qemu version 2.10.0 I’m currently facing a strange situation. Sometimes my vm is shown by ‘virsh list’ as in state “in shutdown” but there is no qemu-kvm process linked to it. Libvirt log when “in shutdown” state occur is as follows: “d470c3b284425b9bacb34d3b5f3845fe” is vm’s name,

How do I "enable" qemu-ga on a guest to be able to (I think this means have a success-response:true) for: guest-suspend-hybrid; guest-suspend-ram; guest-suspend-disk; and guest-shutdown? At least I think that's my question. http://wiki.stoney-cloud.org/wiki/Qemu_Guest_Agent_Integration shows these same 4 as false, so I'm not sure if they're always supposed to be that way.

I've been trying to get "virsh shutdown" to work against an XP-Pro guest with no luck so far. It seems to have no effect - I have to run "virsh destroy" instead which is less than desirable. I have enabled <acpi> in the domain xml so I think the problem is on the guest side. A couple of questions: 1) How can I confirm whether the XP guest has ACPI enabled. I actually

On 03/29/2014 06:21 AM, Pasquale Dir wrote: > I am looking at the shutdown method, but if the guest system is a desktop > system, like for example ubuntu, it just has the effect to show a box > prompting the user for a shutdown/reboot/ and such. > > I could enter the guest and change this default behaviour and it actually > works..but I'd like for a way to send a shutdown

hi guys I have just two guest after which libvirt looks and when I shutdown those guests: $ virsh shutdown $_dom that domain takes little time to power down, as expected one would say(~20sec) But! I reboot the hosts and I have in my: /etc/sysconfig/libvirt-guests : ON_SHUTDOWN=shutdown PARALLEL_SHUTDOWN=1 SHUTDOWN_TIMEOUT=300 I see libvirtd service shut down takes minutes, a few good

Hello, I am unable to do a graceful shutdown or reboot of SLES 10 SP4 virtual machines (Kernel version: 2.6.16.60-0.85.1-default) with virsh shutdown or virsh reboot commands. (e.g virsh shutdown "vmname" ). On issuing these commands there is no impact on the VM. Also unable to perform the shutdown or reboot operations from the menu options available on the console when accessing the

Yes, you are right. Listen, as the documentation is not very exaustive, can you explain briefly to me how a guest agent works? After installing it via the apt-get on the hypervisor (I am using ubuntu as host system) how can I create a script which would do this? That is waiting for an acpi signal and actually shut down the guest. And what other operation can you actually do with a guest agent? I

I am currently running LibVirt with Qemu on Debian Wheezy: Versions: - libvirtd (libvirt) 1.2.4 - qemu-x86_64 version 2.0.0 (Debian 2.0.0+dfsg-4~bpo70+1), Copyright (c) 2003-2008 Fabrice Bellard It's all working perfectly, including ACPI: virsh shutdown guest. However when I issue "halt" from the guest, the guest stops but libvirt thinks it is still running: (virsh list

hi guys I have just two guest after which libvirt looks and when I shutdown those guests: $ virsh shutdown $_dom that domain takes little time to power down, as expected one would say(~20sec) But! I reboot the hosts and I have in my: /etc/sysconfig/libvirt-guests : ON_SHUTDOWN=shutdown PARALLEL_SHUTDOWN=1 SHUTDOWN_TIMEOUT=300 I see libvirtd service shut down takes minutes, a few good

On 26.09.2014 09:46, ustermann78@web.de wrote: > hello, > > if i start a transient guest doamin via "virsh create abcd.xml" i see an additional libvirt thread and also some open files: > > pstree -h `pgrep libvirtd` > libvirtd───11*[{libvirtd}] > > libvirtd 3016 root 21w REG 253,0 6044 1052094 /var/log/libvirt/libxl/abcd.log > libvirtd

On Tue, Dec 11, 2018 at 14:39:40 +0000, Peter Kukla wrote: > Hello, > I have a CentOS 7 client running on a CentOS 7 server.  "virsh --version" reports that 3.9.0 is being used. > I'm issuing a "virsh shutdown" command to shutdown the client.  I then confirm that the client has actually shutdown using "virsh list --all". > Lately I've been seeing

I am in the middle of a rather confusing situation. At the moment I am unable to shutdown a KVM guest machine. Nor am I presently able to open a virt-manager session on the host. I am not exactly sure what has happened but the problem with the vm guest is that issuing a "virsh shutdown 1" from the root console has no effect. # virsh list Id Name State