On Thu, 2014-12-11 at 01:52 +, Mao Mingya wrote:
> >Yes, qemu can be used to provide PV backends for: disk (using qdisk),
> >framebuffer, kbd and mouse.
> Thank you for the detail explanation.
> What is the best pv backend on arch arm? qemu-upstream,
> qemu-xen-traditional, or anything else?
-- Original Message --
From: "Ian Campbell"
To: "Mao Mingya"
Cc: xen-devel@lists.xen.org
Sent: 10/12/2014 5:47:19 PM
Subject: Re: Re[2]: [Xen-devel] arch arm qemu compile erro
Please don't top post.
On Wed, 2014-12-10 at 07:09 +, Mao Mingya wrote:
Fro
Please don't top post.
On Wed, 2014-12-10 at 07:09 +, Mao Mingya wrote:
> From the the arch arm, since the stubdom is not supported now. Does the
> device to be shared between doms have to be pv front/backend structure.
Yes.
There is no equivalent to the x86 "hvm" type guest, i.e. one which
ject: Re: [Xen-devel] arch arm qemu compile erro
On Tue, 2014-12-09 at 10:04 +, Mao Mingya wrote:
While I tried to cross compile the qemu for xen with the following
command:
"make dist-stubdom CROSS_COMPILE=arm-linux-gnueabihf-
XEN_TARGET_ARCH=arm32"
I got an error complain abou
On Tue, 2014-12-09 at 10:04 +, Mao Mingya wrote:
> While I tried to cross compile the qemu for xen with the following
> command:
> "make dist-stubdom CROSS_COMPILE=arm-linux-gnueabihf-
> XEN_TARGET_ARCH=arm32"
>
> I got an error complain about the
> " ./extras/mini-os/arch/arm32/arch.mk: No s
While I tried to cross compile the qemu for xen with the following
command:
"make dist-stubdom CROSS_COMPILE=arm-linux-gnueabihf-
XEN_TARGET_ARCH=arm32"
I got an error complain about the " ./extras/mini-os/arch/arm32/arch.mk:
No such file or directory " is missing.
My xen source version is o
