From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Test for osstest, features used in Qubes OS
Date: Wed, 16 May 2018 23:54:25 +0200 [thread overview]
Message-ID: <20180516215425.GB11683@mail-itl> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1409 bytes --]
Hi,
As discussed some time ago, I'd like to help with adding tests for some
features we use in Qubes OS.
IMO the easiest thing to test is host suspend. You just need to execute
"rtcwake -s 30 -m mem", and see if the host is back to live after ~30s.
Right now I know it works on Xen 4.8, but supposedly is broken on
staging (haven't tested the most recent version).
Next step would be the same while having some domains running.
How the test should look like (where to add this? etc)?
Next things would be mostly related to PCI passthrough:
- PCI passthrough with qemu in stubdomain
- the same as above, but with Linux-based stubdomain (we need cleanup
and send patches for that first, probably 4.12 material)
- guest suspend (recently added libxl_domain_suspend_only), for
different guest types (PV, PVH, HVM), also with/without PCI device
For this, the machine obviously need to have IOMMU (I assume at least
some of the hardware used in test lab have it), and some spare PCI
device. I use sound card for some of such tests. But testing on USB
controllers would be more useful (from out experience, one of the most
problematic devices for suspend, sadly also lacking FLR or such...).
--
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: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2018-05-16 21:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 21:54 Marek Marczykowski-Górecki [this message]
2018-05-17 12:26 ` Test for osstest, features used in Qubes OS Ian Jackson
2018-05-17 14:59 ` Marek Marczykowski-Górecki
2018-05-17 15:12 ` Ian Jackson
2018-05-17 18:00 ` Sander Eikelenboom
2018-05-18 15:44 ` Marek Marczykowski-Górecki
2018-05-18 15:33 ` Marek Marczykowski-Górecki
2018-05-18 15:54 ` Jan Beulich
2018-05-18 16:19 ` Marek Marczykowski
2018-05-21 15:48 ` George Dunlap
2018-05-21 16:17 ` Andrew Cooper
2018-05-21 16:28 ` George Dunlap
2018-05-21 17:18 ` George Dunlap
2018-05-22 22:21 ` Simon Gaiser
2018-05-24 13:15 ` Jan Beulich
2018-05-24 13:39 ` Simon Gaiser
2018-05-21 11:04 ` George Dunlap
2018-05-21 11:52 ` Dario Faggioli
2018-05-21 13:57 ` Ian Jackson
2018-05-21 14:11 ` George Dunlap
2018-05-22 7:51 ` Dario Faggioli
2018-05-21 11:49 ` Dario Faggioli
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=20180516215425.GB11683@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=ian.jackson@eu.citrix.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).