David Woodhouse <dw...@infradead.org> writes:
> I hadn't got round to getting the PV shim running yet; I thought it would
> need work on the multiboot loader. Turns out it doesn't. I *did* need to
> fix a couple of brown-paper-bag bugs in the per-vCPU upcall vector support,
> and implement Xen console support though. Now I can test PV guests:
>
> $ qemu-system-x86_64 --accel kvm,xen-version=0x40011,kernel-irqchip=split \
> -chardev stdio,mux=on,id=char0 -device xen-console,chardev=char0 \
> -drive file=${GUEST_IMAGE},if=xen -display none -m 1G \
> -kernel ~/git/xen/xen/xen -initrd ~/git/linux/arch/x86/boot/bzImage
> \
So this is a KVM guest running the Xen hypervisor (via -kernel) and a
Dom0 Linux guest (via -initrd)?
Should this work for any Xen architecture or is this x86 specific? Does
the -M machine model matter?
Would it be possible to have some sort of overview document in our
manual for how Xen guests are supported under KVM?
> -append "loglvl=all -- console=hvc0 root=/dev/xvda1"
>
<snip>
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
