Hi xen folks,
I just closed the virt@fedora list. See the discussion here where we decided
to close it:
TLDR: it doesn't serve a compelling purpose nowadays, and questions are better
directed to upstream lists or general fedora lists.
How do folks feel about the xen list? Kinda strange timing since we just had a
useful thread regarding my Xen-on-KVM issue, but that could have been a bug
report too. But prior to that discussion, there hadn't been any mail here for
over six months...
If yall decide you want to leave the list open, that's fine with me. But then
I'd like to hand off admin list access to someone else
On 09/18/2015 03:04 PM, Borislav Petkov wrote:
> On Fri, Sep 18, 2015 at 08:20:46AM -0700, Andy Lutomirski wrote:
>> Given that we can handle fixups in the decompressor, surely it
>> wouldn't be so hard to make early GPF fixups work in the main kernel.
> Frankly, I still am wondering what a sensible use case of running xen
> hypervisor/dom0 as a kvm guest would be.
Testing libvirt + virt-manager xen support without requiring a physical
machine running xen.
Anyone know how to get fedora + xen running in a KVM VM? I'd like to be able
to do basic xen/libxl/libvirt testing without needed to reboot a physical machine.
Trying with F23 AMD host, F22+xen L1, trying to boot into xen in the L1 VM
just reboots very soon after trying to boot the kernel. Tried disabling all
virtio for L1 VM, disabling virt extensions for the L1 VM, but it didn't seem
to change anything. Unfortunately the messages scroll by so quickly I can't
tell what's happening right before it reboots, and all efforts to convince it
to print more debugging haven't worked.
FWIW this does work with rhel5+xen L1, but that's a world away at this point.
So anyone know if it's even possible? Is there a trick to it? If not,
suggestions on getting more debug output from xen + grub2?