From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: xen-devel@lists.xen.org
Subject: libxl backport request for 4.5/4.4/4.3/4.2
Date: Sat, 21 Feb 2015 15:56:40 +0100 [thread overview]
Message-ID: <20150221145640.GD4679@mail-itl> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 999 bytes --]
I'd like to have below two commits in stable release - without them
libvirtd crashes while trying to start a HVM domain (with about 50%
probability on my system). I've tested this only on 4.4.1, but looks
like the same problem exists there since 4.2. I wonder why it wasn't
spotted earlier... Maybe it only happens when qemu is in stubdomain
(which isn't supported in vanilla libvirt)?
commit 93699882d98cce9736d6e871db303275df1138a2
Author: Ian Jackson <ian.jackson@eu.citrix.com>
Date: Mon Feb 9 15:18:30 2015 +0000
libxl: event handling: Break out ao_work_outstanding
commit f1335f0d7b2402e94e0c6e8a905dc309edaafcfb
Author: Ian Jackson <ian.jackson@eu.citrix.com>
Date: Mon Feb 9 15:20:32 2015 +0000
libxl: event handling: ao_inprogress does waits while reports
outstanding
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #1.2: Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2015-02-21 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-21 14:56 Marek Marczykowski-Górecki [this message]
2015-02-23 9:36 ` libxl backport request for 4.5/4.4/4.3/4.2 Ian Campbell
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=20150221145640.GD4679@mail-itl \
--to=marmarek@invisiblethingslab.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 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.