From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Jie Wang <wangjie88@huawei.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
"Zhangbo (Oscar)" <oscar.zhangbo@huawei.com>,
"Fangyi (C)" <eric.fangyi@huawei.com>
Subject: Re: [Qemu-devel] question： Does qemu-pr-helper have its own log files？
Date: Tue, 23 Apr 2019 10:42:17 +0100 [thread overview]
Message-ID: <20190423094217.GC6022@redhat.com> (raw)
In-Reply-To: <c47aea74-cec7-0369-591e-e1b1fdddc3e6@huawei.com>
On Tue, Apr 23, 2019 at 11:12:40AM +0800, Jie Wang wrote:
> Does qemu-pr-helper have its own log files？
When QEMU launches it, i think it just inherits stdout/err from
QEMU itself, so errors appear mixed into QEMU's stdout output.
When libvirt launches it, there stdout is connected to /dev/null
and stderr is connected to a pipe which libvirt closes almost
immediately. This means any errors are lost as any attempt to
write to stderr will get EPIPE :-(
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
WARNING: multiple messages have this Message-ID (diff)
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Jie Wang <wangjie88@huawei.com>
Cc: "Zhangbo \(Oscar\)" <oscar.zhangbo@huawei.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
"Fangyi \(C\)" <eric.fangyi@huawei.com>
Subject: Re: [Qemu-devel] question： Does qemu-pr-helper have its own log files？
Date: Tue, 23 Apr 2019 10:42:17 +0100 [thread overview]
Message-ID: <20190423094217.GC6022@redhat.com> (raw)
Message-ID: <20190423094217.W_4TDnxtNXR9K5GJeAOPNpawSpYBRQIhbpFj2dOZtrE@z> (raw)
In-Reply-To: <c47aea74-cec7-0369-591e-e1b1fdddc3e6@huawei.com>
On Tue, Apr 23, 2019 at 11:12:40AM +0800, Jie Wang wrote:
> Does qemu-pr-helper have its own log files？
When QEMU launches it, i think it just inherits stdout/err from
QEMU itself, so errors appear mixed into QEMU's stdout output.
When libvirt launches it, there stdout is connected to /dev/null
and stderr is connected to a pipe which libvirt closes almost
immediately. This means any errors are lost as any attempt to
write to stderr will get EPIPE :-(
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2019-04-23 9:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 3:12 [Qemu-devel] question： Does qemu-pr-helper have its own log files？ Jie Wang
2019-04-23 3:12 ` Jie Wang
2019-04-23 9:42 ` Daniel P. Berrangé [this message]
2019-04-23 9:42 ` Daniel P. Berrangé
2019-04-25 8:30 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2019-04-25 8:30 ` Stefan Hajnoczi
2019-04-23 13:56 ` Stefan Hajnoczi
2019-04-23 13:56 ` Stefan Hajnoczi
2019-04-24 2:37 ` Zhangbo (Oscar)
2019-04-24 2:37 ` Zhangbo (Oscar)
2019-04-25 8:32 ` Stefan Hajnoczi
2019-04-25 8:32 ` Stefan Hajnoczi
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=20190423094217.GC6022@redhat.com \
--to=berrange@redhat.com \
--cc=eric.fangyi@huawei.com \
--cc=oscar.zhangbo@huawei.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wangjie88@huawei.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.