From: Avi Kivity <avi@qumranet.com>
To: Charles Duffy <Charles_Duffy@messageone.com>
Cc: kvm@vger.kernel.org
Subject: Re: [ANNOUNCE] kvm-74 release
Date: Mon, 01 Sep 2008 13:36:11 +0300 [thread overview]
Message-ID: <48BBC59B.5020102@qumranet.com> (raw)
In-Reply-To: <g9860i$jo1$1@ger.gmane.org>
Charles Duffy wrote:
> A few quick notes:
>
> - The extboot.bin regression from kvm-71 (SCSI drives being
> unavailable after reboot) is still outstanding.
>
Now fixed.
> - kvm (and presumably qemu) doesn't check for fd= parameters pointing
> to file descriptor numbers which are not, in fact, open; this results
> in select() spinning on -EBADF, and associated Bad Things Happening.
Seems a minor issue; but worth reporting to qemu-devel.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-09-01 10:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 10:02 [ANNOUNCE] kvm-74 release Avi Kivity
2008-08-29 0:05 ` Iain Paton
2008-09-01 10:35 ` Avi Kivity
2008-09-01 18:21 ` Iain Paton
2008-08-29 6:46 ` Charles Duffy
2008-09-01 10:36 ` Avi Kivity [this message]
2008-09-02 10:24 ` Henrik Holst
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=48BBC59B.5020102@qumranet.com \
--to=avi@qumranet.com \
--cc=Charles_Duffy@messageone.com \
--cc=kvm@vger.kernel.org \
/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