On Tue, 2026-07-07 at 11:39 +0100, Daniel P. Berrangé wrote: > We appreciate the intent not to flood projects ! Feel free to > drip-feed issues to us, a handful at a time though over days > or weeks if there will be alot to process. > > We recently switched our security disclosure process over to using > our regular GitLab issue tracker, so would prefer any bugs to be > filed there, rather than emailing people directly: > > https://www.qemu.org/contribute/security-process/
Perfect, that makes it easy. I will file on the GitLab tracker and send them in small batches over the next couple of weeks rather than all at once. For the ones with a host side impact, a guest triggered hang or use after free, I will tick the confidential box and let triage decide whether it stays that way. > We also have tests/functional/ in QEMU where we boot real guest OS > disk images and/or kernel/initrd pairs. The minimal initramfs > approach would probably fit in nicely with that, and indeed I have > long wanted us to replace some of our full-fat disk images with > minimal self contained initramfs images to speed up smoke testing. That sounds like a clean fit. The harness already boots a kernel plus a tiny initramfs with a single static init and no full OS, so it should slot into tests/functional/ with little friction. Each test finishes in under a second when passing, since there is no full VM boot involved, which makes it suitable for smoke testing too. Would it be useful to have these wired in there directly, or is there a different shape that would work better for you? Thanks Anatol
