<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>openATTIC (Posts about acpid)</title><link>/</link><description></description><atom:link href="https://openattic.org/categories/acpid.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Thu, 22 Aug 2019 20:00:52 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>KVM guest with acpid installed will not shutdown</title><link>https://openattic.org/posts/kvm-guest-with-acpid-installed-will-not-shutdown/</link><dc:creator>Kai Wagner</dc:creator><description>&lt;div&gt;&lt;p&gt;Yesterday a colleague migrated a physical machine into a kvm vm. Afterwards we wanted to manage the vm within virt-manager.&lt;/p&gt;
&lt;p&gt;Acpid was installed, but nothing happend if we tried to shutdown or reboot the vm via acpi requests.&lt;/p&gt;
&lt;p&gt;The problem was, that the migrated kvm vm still tought that it is a hardware instead of a vm. Therefore I changed the entry within the acpi events.&lt;/p&gt;
&lt;blockquote&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;Edit /etc/acpi/events/powerbtn to contain action=/sbin/poweroff&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;p&gt;As an alternative you could purge and reinstall the acpid package.&lt;/p&gt;
&lt;blockquote&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;apt-get purge acpid&lt;/li&gt;
&lt;li&gt;apt-get install acpid&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;p&gt;Sometimes it's that easy :-)&lt;/p&gt;&lt;/div&gt;</description><category>acpid</category><category>config</category><category>kvm</category><guid>https://openattic.org/posts/kvm-guest-with-acpid-installed-will-not-shutdown/</guid><pubDate>Tue, 30 Aug 2016 14:17:42 GMT</pubDate></item></channel></rss>