From: George Dunlap <george.dunlap@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Lars Kurth <lars.kurth.xen@gmail.com>,
George Dunlap <George.Dunlap@citrix.com>,
Alex Bligh <alex@alex.org.uk>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Hackathon Minutes] Xen 4.4 Planning
Date: Fri, 14 Jun 2013 12:19:52 +0100 [thread overview]
Message-ID: <51BAFC58.1050508@eu.citrix.com> (raw)
In-Reply-To: <51BB108002000078000DE528@nat28.tlf.novell.com>
On 14/06/13 11:45, Jan Beulich wrote:
>>>> On 14.06.13 at 11:59, Lars Kurth <lars.kurth.xen@gmail.com> wrote:
>> I also wanted to add to the point that Alex has made on serious bugs in xen
>> vs. kvm : this gets raised regularly by Xen users when I attend
>> conferences. And I also heard a few times now that we appear to focus more
>> on sexy features rather than the basics. This is relatively new though: the
>> first time I noticed was towards the end of last year. Which does not mean
>> that this is new: it may just mean that top issues/concerns that were
>> frequently raised before (mainly trust in the future of the project) have
>> disappeared.
> I'd really like to see examples of this - there ought to be quite a
> few according to what you write, yet I don't seem to recall any
> that got plainly ignored. Of course there are always bugs which
> take longer than others to figure out and fix.
Well one example was that from the beginning of time until the 4.3
release, you could only specify a single USB device in the config file
for an HVM domain.
Another one is the qemu one we're discussing right now -- it was
reported back in February I think, but it's only recently actually
getting the attention that it needs to be sorted out. The root cause
was known by March, at which point there would have been plenty of time
for a "proper fix".
And there's random things like cd-eject or cd-insert not working in
certain circumstances (namely, when blktap was available). It's
something basic, but something we don't really use very much, and never
got flagged up. So it was broken in the 4.2 release.
I don't really know if this is the kind of thing that users are talking
about, but if I used a release of a (supposedly) mature product, and
something as basic as "insert a CD" crashed, I wouldn't be very impressed.
-George
next prev parent reply other threads:[~2013-06-14 11:19 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 14:00 [Hackathon Minutes] Xen 4.4 Planning Lars Kurth
2013-06-13 14:22 ` Jan Beulich
2013-06-13 15:11 ` George Dunlap
2013-06-13 15:30 ` Jan Beulich
2013-06-13 15:39 ` Ian Campbell
2013-06-17 8:27 ` Fabio Fantoni
2013-06-17 9:52 ` Ian Campbell
2013-06-13 14:31 ` Ian Campbell
2013-06-13 14:52 ` George Dunlap
2013-06-13 15:06 ` Ian Campbell
2013-06-14 17:41 ` Konrad Rzeszutek Wilk
2013-06-13 14:43 ` George Dunlap
2013-06-13 17:09 ` Ben Guthro
2013-06-13 18:07 ` Pasi Kärkkäinen
2013-06-13 21:03 ` Alex Bligh
2013-06-13 23:56 ` Ian Murray
2013-06-14 7:01 ` Alex Bligh
2013-06-14 9:46 ` Ian Murray
2013-06-14 11:53 ` Alex Bligh
2013-06-14 12:32 ` Ian Murray
2013-06-14 12:49 ` Alex Bligh
2013-06-14 13:34 ` Ian Murray
2013-06-14 13:55 ` Ian Campbell
2013-06-14 14:44 ` Ian Murray
2013-06-14 14:55 ` Gordan Bobic
2013-06-14 15:00 ` George Dunlap
2013-06-14 15:09 ` Ian Campbell
2013-06-14 15:43 ` Alex Bligh
2013-06-14 21:05 ` Ian Murray
2013-06-19 21:22 ` Alex Bligh
2013-06-14 15:44 ` Alex Bligh
2013-06-14 17:25 ` Konrad Rzeszutek Wilk
2013-06-14 8:15 ` Jan Beulich
2013-06-14 9:47 ` George Dunlap
2013-06-14 9:59 ` Lars Kurth
2013-06-14 10:45 ` Jan Beulich
2013-06-14 11:19 ` George Dunlap [this message]
2013-06-14 11:30 ` Gordan Bobic
2013-06-14 12:10 ` Sander Eikelenboom
2013-06-14 10:44 ` George Dunlap
-- strict thread matches above, loose matches on Subject: below --
2013-06-14 11:46 Alex Bligh
2013-06-14 12:26 ` Jan Beulich
2013-06-14 12:45 ` Alex Bligh
2013-06-14 18:55 Alex Bligh
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=51BAFC58.1050508@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=George.Dunlap@citrix.com \
--cc=JBeulich@suse.com \
--cc=alex@alex.org.uk \
--cc=lars.kurth.xen@gmail.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).