[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [virt-tools-list] Why virsh shutdown does not work?



Hi,

So a VM with "<acpi/> " in it's xml, running linux, with kacpid running, will shutdown "gracefully" if I use virsh shutdown, right?

In all my ubuntu VMs, I only found a process called kacpid, with a very low PID. Yesterday I tried to shutdown one of them, and it didn't work. But in my debian VM, witch was shutdown yesterday too and in it's case the "virsh shutdown VM" worked fine, I found 2 running processes, as shown here:

debianldap:~# ps aux | grep acpid
root        41  0.0  0.0      0     0 ?        S<   May12   0:00 [kacpid]
root      1590  0.0  0.9   1768   572 ?        Ss   May12   0:00 /usr/sbin/acpid

Got it, my ubuntu VMs have no acpi support installed/running. Does anyone knows how can I enable that?

Thanks again. ;D
2011/5/13 Decker, Schorschi <schorschi decker bankofamerica com>
That is a major no-go from a security perspective, enabling that feature.

Schorschi Decker

VP; Sr. Consultant Engineer
ET&D Emerging Technologies / Virtualization Platform Engineering Team
Bank of America

Office 213-345-4714



-----Original Message-----
From: virt-tools-list-bounces redhat com [mailto:virt-tools-list-bounces redhat com] On Behalf Of Kenneth Armstrong
Sent: Friday, 13 May, 2011 08:55
To: Laurent Léonard
Cc: virt-tools-list redhat com
Subject: Re: [virt-tools-list] Why virsh shutdown does not work?

Are you having this problem on Windows or Linux VMs?  I don't have this issue with Linux VMs (provided I installed them with the virtio drivers).  However, on a Windows VM there is an extra step that I do to make it work:

Start>Run: gpedit.msc

Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Shutdown: Allow system to be shut down without having to log on

-Kenny

2011/5/13 Laurent Léonard <laurent open-minds org>:
> Le vendredi 13 mai 2011 13:33:54, Bruno Lamps a écrit :
>> Hi,
>>
>> As you may have noticed, I'm writing some simple backup scripts to my
>> KVM vms. Because my production server runs libvirt 0.7.5, I'm not
>> able to use virsh save, there's some sort of bug that make the VM to
>> not always shutdown.
>> So I do my backups shuting down the systems and then copying que raw
>> image and the .xml file. To do so, I run "virsh shutdown VMname". For
>> some reason, it doesn't works all the time, so my script currently
>> waits 10 mintues to run "virsh destroy VMname", to be sure that the
>> VM isn't running and then copy it's files.
>>
>> Why "virsh shutdown" isn't working for me everytime? Is there any VM
>> log where I can discover the reason? =]
>
> "virsh shutdown" sends an ACPI shutdown call to the virtual machine.
> If it never worked for one or more virtual machines, check that the
> guest systems correctly handle ACPI shutdown calls.
>
>> Can "virsh destroy" damage VMs easily?
>
> Avoid it if you can, it has the same effect as if you unplug the power
> cord for a physical machine...
>
> --
> Laurent Léonard
>
> _______________________________________________
> virt-tools-list mailing list
> virt-tools-list redhat com
> https://www.redhat.com/mailman/listinfo/virt-tools-list
>

_______________________________________________
virt-tools-list mailing list
virt-tools-list redhat com
https://www.redhat.com/mailman/listinfo/virt-tools-list

----------------------------------------------------------------------
This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited.
Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law.
The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses.

References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link:
http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing.

_______________________________________________
virt-tools-list mailing list
virt-tools-list redhat com
https://www.redhat.com/mailman/listinfo/virt-tools-list


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]