On Thu, 2011-09-08 at 13:14 -0400, John Dulaney wrote: > > Subject: Release criteria: virtualization tweak > > From: awilliam@xxxxxxxxxx > > To: test@xxxxxxxxxxxxxxxxxxxxxxx > > Date: Wed, 7 Sep 2011 18:20:20 -0700 > > CC: pjones@xxxxxxxxxx > > > > Hey, all. pjones pointed out at a recent blocker review meeting that the > > Beta virt criterion: > > > > "The release must boot successfully as a virtual guest in a situation > > where the virtual host is running the same release (using Fedora's > > current preferred virtualization technology)" > > > > doesn't really imply that virtual host functionality must work; only > > that _if_ virtual host functionality is working, then virtual guest > > functionality must work. This was not really our intent with the > > criterion, we intended to require both to work at Beta stage. So here's > > a proposed improvement: > > > > "The release must be able to self-host using Fedora's current preferred > > virtualization technology: that is, the release must be able to act as a > > virtual host, and must also successfully install and boot as a virtual > > guest when running on a host which is also running the release" > > > > I'm still not super happy with the wording, but I guess it's clearer. > > Any better ideas? > > Are we assuming that this is on CPUs that support Fedora's preferred > virt technology? I do believe that KVM doesn't do so well on older > CPUs. Good point. I'm not sure if it's worthwhile to add a 'assuming capable hardware' rider or just leave it as an assumption? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test