[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Test for osstest, features used in Qubes OS
On Thu, May 17, 2018 at 01:26:30PM +0100, Ian Jackson wrote: > Marek Marczykowski-Górecki writes ("Test for osstest, features used in Qubes > OS"): > > 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)? > > I guess this should be a new > ts-host-suspend-test > script. > > Is it likely that this will depend on non-buggy host firmware ? If so > then we need to make arrangements to test it and only do it on hosts > which are not buggy. In practice this probably means wiring it up to > the automatic host examiner. Yes, probably. > > 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...). > > I doubt any of our x86 machines have sound cards. ... Just looked at > one and it says > 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core > Processor HD Audio Controller (rev 06) > which is obviously mad. > > I'm pretty sure they all have usb controllers. Almost all of them > have multiple NICs, often on different pci devices, although it is > difficult to tell if a NIC not connected to anything is working. > > Eg, > > 02:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network > Connection (rev 03) > > 03:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network > Connection (rev 03) > > Is there some kind of cheap USB HID, that is interactable-with, which > we could plug into each machine's USB port ? I'm slightly concerned > that plugging in a storage device, or connecting the other NIC, might > interfere with booting. I use mass storage for tests... But if you use network boot, it shouldn't really interfere, no? > If you want to get pci passthrough tests working I would suggest > testing it with non-stubdom first. I assume the config etc. is the > same, so having got that working, osstest would be able to test it for > the stubdom tests too. Oh, I though there are already tests for that... Yes, good idea. -- 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:
signature.asc _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |