On Tue, 2015-01-27 at 10:24 +, Stefano Stabellini wrote:
> Please don't drop the mailing list from CC.
>
> On Tue, 27 Jan 2015, Mao Mingy wrote:
> > When I tried to set up the network in Dom0 using command:
> > xl network-attach 1
>
> xl network-attach is not to setup the network in dom0.
Please don't drop the mailing list from CC.
On Tue, 27 Jan 2015, Mao Mingy wrote:
> When I tried to set up the network in Dom0 using command:
> xl network-attach 1
xl network-attach is not to setup the network in dom0.
Please use "man xl"!
network-attach domain-id network-device
Creates
On Mon, 26 Jan 2015, Mao Mingy wrote:
> On 23/01/2015 18:56, Ian Campbell wrote:
>
> If you are trying to get the guest framebuffer onto a physical graphics
> device then PVFB is not what you need. Instead you need to do device
> passthrough of that device to the guest (which means denying it to
>
On 23/01/2015 18:56, Ian Campbell wrote:
If you are trying to get the guest framebuffer onto a physical graphics
device then PVFB is not what you need. Instead you need to do device
passthrough of that device to the guest (which means denying it to
dom0). Passthrough is still a work in progress
On Fri, 2015-01-23 at 21:13 +0800, Mao Mingya wrote:
> On a second though, What mode is the serial port working now on ARM
> arch? it is able to be shared by Dom0 and guest Dom
A given piece of hardware can only be accessed by one entity at a time.
Typically one serial port is given to Xen itsel
Thank you for the overall picture. a good lesson for me.
Will try to use the VNC next week.
On a second though, What mode is the serial port working now on ARM arch?
it is able to be shared by Dom0 and guest Dom
Regards,
Mao
On Fri, Jan 23, 2015 at 6:56 PM, Ian Campbell
wrote:
> On Fri, 2015-
On Fri, 2015-01-23 at 18:48 +0800, Mao Mingy wrote:
> On 23/01/2015 18:34, Ian Campbell wrote:
> > On Fri, 2015-01-23 at 18:23 +0800, Mao Mingy wrote:
> >> On 23/01/2015 18:11, Ian Campbell wrote:
> >>> On Fri, 2015-01-23 at 18:03 +0800, Mao Mingy wrote:
> I modified the "-xen-domid" and "-nam
On Fri, 23 Jan 2015, Mao Mingy wrote:
> On 23/01/2015 18:11, Ian Campbell wrote:
> > On Fri, 2015-01-23 at 18:03 +0800, Mao Mingy wrote:
> > > I modified the "-xen-domid" and "-name" of qemu-system-i386 to match
> > > the domain name and id of the guest Dom, the result is same.
> > Please just let
On 23/01/2015 18:34, Ian Campbell wrote:
On Fri, 2015-01-23 at 18:23 +0800, Mao Mingy wrote:
On 23/01/2015 18:11, Ian Campbell wrote:
On Fri, 2015-01-23 at 18:03 +0800, Mao Mingy wrote:
I modified the "-xen-domid" and "-name" of qemu-system-i386 to match
the domain name and id of the guest D
Please don't use HTML in emails.
On Fri, 23 Jan 2015, Mao Mingy wrote:
> On 22/01/2015 19:56, Stefano Stabellini wrote:
>
> On Thu, 22 Jan 2015, Mao Mingy wrote:
>
> On 21/01/2015 18:51, Stefano Stabellini wrote:
>
> On Wed, 21 Jan 2015, Mao Mingy wrote:
>
> I am trying to run the PVHVM guest
On Fri, 2015-01-23 at 18:23 +0800, Mao Mingy wrote:
> On 23/01/2015 18:11, Ian Campbell wrote:
> > On Fri, 2015-01-23 at 18:03 +0800, Mao Mingy wrote:
> >> I modified the "-xen-domid" and "-name" of qemu-system-i386 to match
> >> the domain name and id of the guest Dom, the result is same.
> > Ple
On 23/01/2015 18:11, Ian Campbell wrote:
On Fri, 2015-01-23 at 18:03 +0800, Mao Mingy wrote:
I modified the "-xen-domid" and "-name" of qemu-system-i386 to match
the domain name and id of the guest Dom, the result is same.
Please just let the toolstack launch qemu instead of doing it yourself
On Fri, 2015-01-23 at 18:03 +0800, Mao Mingy wrote:
> I modified the "-xen-domid" and "-name" of qemu-system-i386 to match
> the domain name and id of the guest Dom, the result is same.
Please just let the toolstack launch qemu instead of doing it yourself.
With Xen 4.5 you shouldn't need to be
On 23/01/2015 17:24, Ian Campbell wrote:
On Fri, 2015-01-23 at 17:14 +0800, Mao Mingy wrote:
1. QEMU's start up parameter, changed the original from Xen4.5
/usr/local/lib/xen/bin/qemu-system-i386 -xen-domid 0
Are you trying to use pvfb for dom0's own graphical output?
No. I got it wrong. Right
On Fri, 2015-01-23 at 17:14 +0800, Mao Mingy wrote:
> 1. QEMU's start up parameter, changed the original from Xen4.5
> /usr/local/lib/xen/bin/qemu-system-i386 -xen-domid 0
Are you trying to use pvfb for dom0's own graphical output?
This qemu process you quote here is running against dom0 in orde
On 22/01/2015 19:56, Stefano Stabellini wrote:
On Thu, 22 Jan 2015, Mao Mingy wrote:
On 21/01/2015 18:51, Stefano Stabellini wrote:
On Wed, 21 Jan 2015, Mao Mingy wrote:
I am trying to run the PVHVM guest on omap5 (arm arch) so that I can get
the
frame buffer shared by Domains. my setup are:
On Thu, 22 Jan 2015, Mao Mingy wrote:
> On 21/01/2015 18:51, Stefano Stabellini wrote:
> > On Wed, 21 Jan 2015, Mao Mingy wrote:
> > > I am trying to run the PVHVM guest on omap5 (arm arch) so that I can get
> > > the
> > > frame buffer shared by Domains. my setup are:
> > > 1. run xen4.5 after the
On 21/01/2015 18:51, Stefano Stabellini wrote:
On Wed, 21 Jan 2015, Mao Mingy wrote:
I am trying to run the PVHVM guest on omap5 (arm arch) so that I can get the
frame buffer shared by Domains. my setup are:
1. run xen4.5 after the u-boot.
2. start the dom0 (on linux kernel 3.12) on xen.
3.12
On Wed, 21 Jan 2015, Mao Mingy wrote:
> I am trying to run the PVHVM guest on omap5 (arm arch) so that I can get the
> frame buffer shared by Domains. my setup are:
> 1. run xen4.5 after the u-boot.
> 2. start the dom0 (on linux kernel 3.12) on xen.
3.12 is pretty old now
> 3. run the qemu (from
I am trying to run the PVHVM guest on omap5 (arm arch) so that I can get
the frame buffer shared by Domains. my setup are:
1. run xen4.5 after the u-boot.
2. start the dom0 (on linux kernel 3.12) on xen.
3. run the qemu (from xen 4.5) and HVM backend on xen.
4. run the guest domain as "Machine: D
20 matches
Mail list logo
