From: Paolo Bonzini <pbonzini@redhat.com>
To: Seiji Aguchi <seiji.aguchi@hds.com>
Cc: "kwolf@redhat.com" <kwolf@redhat.com>,
"peter.maydell@linaro.org" <peter.maydell@linaro.org>,
"aliguori@us.ibm.com" <aliguori@us.ibm.com>,
"mst@redhat.com" <mst@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"dle-develop@lists.sourceforge.net"
<dle-develop@lists.sourceforge.net>,
"hdegoede@redhat.com" <hdegoede@redhat.com>,
"kraxel@redhat.com" <kraxel@redhat.com>,
Tomoki Sekiyama <tomoki.sekiyama@hds.com>,
"afaerber@suse.de" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH] Make guest OS bootable when hardware failure happens in log disk
Date: Fri, 29 Mar 2013 00:45:08 +0100 [thread overview]
Message-ID: <5154D604.4000600@redhat.com> (raw)
In-Reply-To: <A5ED84D3BB3A384992CBB9C77DEDA4D41AF7CF2C@USINDEM103.corp.hds.com>
Il 28/03/2013 20:43, Seiji Aguchi ha scritto:
> [Problem]
> Currently, guest OS's messages can be logged to a local disk of host OS by creating chadevs with options below.
> -chardev file,id=charserial0,path=<log file's path> -device isa-serial,chardev=chardevserial0,id=serial0
>
> When a hardware failure happens in the disk, qemu-kvm can't create the chardevs.
> In this case, guest OS doesn't boot up.
>
> Actually, there are users who don't desire that guest OS goes down due to a hardware failure of a log disk only.
> Therefore, qemu should offer some way to boot guest OS up even if the log disk is broken.
>
> [Solution]
> This patch skips error checks in case where opening a log file and creating chardev fail.
This kind of policy does not belong in QEMU. QEMU should always fail if
it sees a problem.
Your management tool should just open the file outside QEMU, and then
use either /dev/fd/NN or /dev/null as the destination.
Paolo
prev parent reply other threads:[~2013-03-28 23:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 19:43 [Qemu-devel] [PATCH] Make guest OS bootable when hardware failure happens in log disk Seiji Aguchi
2013-03-28 23:45 ` Paolo Bonzini [this message]
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=5154D604.4000600@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=hdegoede@redhat.com \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=seiji.aguchi@hds.com \
--cc=tomoki.sekiyama@hds.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.