Closed djs55 closed 9 years ago
Not entirely perfect yet, but it is now running mirage-www on my cubie@home. The future is here!
This is really wonderful, thank you!
I'm wondering what the best way to merge this is. Should be have an alternate build with XenServer, or just bite the bullet and not support a non-XS image on ARM? There's a lot of benefit in just having the nice storage and XML-RPC APIs, particularly with a view to monitoring and building a distributed ARM cloud in the future.
On 11 Feb 2015 11:02, "Anil Madhavapeddy" notifications@github.com wrote:
I'm wondering what the best way to merge this is. Should be have an alternate build with XenServer, or just bite the bullet and not support a non-XS image on ARM? There's a lot of benefit in just having the nice storage and XML-RPC APIs, particularly with a view to monitoring and building a distributed ARM cloud in the future.
I believe that it's still possible to manage your VMs manually with xl/libxl or with libvirt -- this change gives you an extra option. Xapi will manage its VMs only; libvirt will manage its VMs only; and, well xl/libxl just shows you everything (expert user mode?)
The only downside that I can think of is that the image is slightly bigger.
As a separate issue there are probably still some silly bugs in the .debs I've built. Now that I'm routinely using this I should be able to squash those and update my binary repo.
Cheers, Dave
— Reply to this email directly or view it on GitHub https://github.com/mirage/xen-arm-builder/pull/51#issuecomment-73864307.
Thanks, I'll merge this in after I try it on my cubie at home!
xe
mirage
-generated .xe file worksxcp-rrdd
ezlvm
xcp-networkd
xenbr0
rather thanbr0
Note that Xapi runs in parallel with other 'toolstacks' so it is still possible to use
xl
orlibvirt
.Signed-off-by: David Scott dave.scott@citrix.com