Re: [Xen-devel] arch arm qemu compile erro
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? There is no one pv backend, it is a per device type thing. For disk, blkback (in backend kernel driver) is best if your guest disks are backed by raw disks (e.g. lvm volumes in the backend), qdisk (from qemu-upstream) is best if your guest disks are backed by something more complex, like a qcow2 file. For network netback (in kernel backend driver) is best. For PVFB, PVKBD and PVMOUSE qemu-upstream is the best (only?) backend. There is no qemu-xen-trad on ARM, I don't expect anyone to port it and I wouldn't expect those patches to be accepted anyway. > Is there any guild doc to get it work on arch arm? I'm not sure what "it" refers to here. PV backends generally are part of all the docs on the wiki explaining how to get Xen to work, there is not generally a separate guide for them since they are part of the core concept. qemu-upstream is built along with Xen on ARM for a while (not 4.4, 4.5-rcN should be fine), the in kernel backends have been available for longer than Xen on ARM has been. Ian. ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] arch arm qemu compile erro
-- 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: 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 looks to the guest like a real system, in the ARM version of Xen. On x86 stub-qemu is primarily about providing these emulated system devices in a sandboxed environment. There are no emulated devices on ARM hence no need for qemu for this purpose, hence no stubdomains. qemu has a "second hat" when in a Xen system, which is that it can provide certain PV backends, we do use it for this purpose on ARM. To run the Linux on Dom0 and DomU. Could the qemu and pv backend run in the Dom0 at the same time? Yes. For example: for network, block device, serial console, the pv backend provides the device drive for DomU linux while qemu provides all other devices driver for DomU linux. 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? Is there any guild doc to get it work on arch arm? Ian. ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] arch arm qemu compile erro
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 looks to the guest like a real system, in the ARM version of Xen. On x86 stub-qemu is primarily about providing these emulated system devices in a sandboxed environment. There are no emulated devices on ARM hence no need for qemu for this purpose, hence no stubdomains. qemu has a "second hat" when in a Xen system, which is that it can provide certain PV backends, we do use it for this purpose on ARM. > To run the Linux on Dom0 and DomU. Could the qemu and pv backend run in > the Dom0 at the same time? Yes. > For example: for network, block device, serial console, the pv > backend provides the device drive for DomU linux > while qemu provides all other devices driver for DomU linux. Yes, qemu can be used to provide PV backends for: disk (using qdisk), framebuffer, kbd and mouse. Ian. ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Re: [Xen-devel] arch arm qemu compile erro
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. To run the Linux on Dom0 and DomU. Could the qemu and pv backend run in the Dom0 at the same time? For example: for network, block device, serial console, the pv backend provides the device drive for DomU linux while qemu provides all other devices driver for DomU linux. Regards, Mao -- Original Message -- From: "Ian Campbell" To: "Mao Mingya" Cc: xen-devel@lists.xen.org Sent: 9/12/2014 6:32:48 PM Subject: 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 about the " ./extras/mini-os/arch/arm32/arch.mk: No such file or directory " is missing. My xen source version is on "Xen-4.5.0-rc3" Is the build process for xen broken? or some ./configure needed? stubdoms are not supported on ARM right now. Ian. ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
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 about the > " ./extras/mini-os/arch/arm32/arch.mk: No such file or directory " is > missing. > > My xen source version is on "Xen-4.5.0-rc3" > > Is the build process for xen broken? or some ./configure needed? stubdoms are not supported on ARM right now. Ian. ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
[Xen-devel] arch arm qemu compile erro
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 on "Xen-4.5.0-rc3" Is the build process for xen broken? or some ./configure needed? Regards, Mao ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
