From: Eduardo Habkost <ehabkost@redhat.com>
To: Lucas Meneghel Rodrigues <lmr@redhat.com>
Cc: autotest@test.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM test: Unattended install - Give Linux VMs time to shutdown cleanly
Date: Wed, 13 Apr 2011 13:16:13 -0300 [thread overview]
Message-ID: <20110413161613.GC27651@otherpad.lan.raisama.net> (raw)
In-Reply-To: <1302647295-24257-1-git-send-email-lmr@redhat.com>
On Tue, Apr 12, 2011 at 07:28:15PM -0300, Lucas Meneghel Rodrigues wrote:
> During unattended install, right after we receive the ACK from the guest
> the test is deemed to be finished, and as shutdown_vm = yes, it'll try
> to end the vm issuing a shutdown command to it. However, on virtually
> all Linux guests an SSH server is not available at the end of install,
> so KVM autotest will end the VM forcefully, which is not really safe,
> although it has served us well so far.
>
> We did not fix this 'problem' so far because on RHEL3, a supported
> guest, the anaconda syntax does not support the 'poweroff' directive,
> only 'reboot', so if we don't finish the VM right after the ACK from
> guest we really can't prevent it from starting the install again,
> getting an infinite loop.
On the other hand, RHEL 3 supports 'reboot'[1], so we could simply run
the install-finished notification on first boot (it's the method we use
for Windows guests, right?), and simply shut down the machine cleanly
using ssh or the virtual power button.
[1] http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/s1-kickstart2-options.html
--
Eduardo
next prev parent reply other threads:[~2011-04-13 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 22:28 [PATCH] KVM test: Unattended install - Give Linux VMs time to shutdown cleanly Lucas Meneghel Rodrigues
2011-04-13 16:16 ` Eduardo Habkost [this message]
2011-04-13 16:35 ` Lucas Meneghel Rodrigues
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110413161613.GC27651@otherpad.lan.raisama.net \
--to=ehabkost@redhat.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=lmr@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox