Boris Derzhavets wrote: >> We have tried to submit it once upstream and it >> didn't get accepted initially. We need to try >> again or get the patch out so RedHat, SUSE can >> add it to their current distros. >> >> The bug doesn't exist in 3.2 due to a large change >> in the VT code. >> MRJ > Could it be a reason for rejection ? > http://fedoraproject.org/wiki/Features/XenFullvirtKernelBoot > Quote:- > In all prior Fedora releases fullyvirtualized Xen guests had to boot via the > QEMU BIOS. This means booting from a CDROM, harddisk, or Network PXE. > Paravirtualized guests could always boot directly from a kernel and initrd. > This allowed for fully automated guest installation since it allowed the > tools to pass arguments straight into anaconda. KVM fullyvirtualized guests > also support direct kernel booting. The support for Xen HVM was always there > in the underlying QEMU device model, however, it was disabled as it > conflicted with the way Xen boots HVM guests. > Recently patches were added to upstream Xen to work-around the limitations of > Xen's HVM boot process, so it is now possible to directly boot > fullyvirtualized Xen guests from a kernel and initrd, passing boot args.
No, these changes were so the Linux folks could boot a HVM kernel using a kernel image no on the domain. Personally, I don't think that's the right direction. MRJ _______________________________________________ xen-discuss mailing list [email protected]
