If you would like some help, don't hesitate like also to update procedure to setup cloudstack using vagrant.
On Fri, Nov 23, 2012 at 6:33 PM, Rohit Yadav <[email protected]> wrote: > Charles, I've figured out the issues and fixes and template using Debian > Wheezy and xen/xapi which works with VirtualBox using the new networking > model. The vagrant scripts will probably need fixing. > For some reason, because of incompatible Linux kernel version, xend/xapi > plugin and VirtualBox network adapter card (this was hard to debug); it > does not work with Ubuntu but works with Wheezy (testing). There are few > more modification and optimizations like console proxy is not started > (saves us 1G of ram) and using non-LVM partitioning, network routing so > both host-only and NAT can work for both dom0 and domU, and dom0 memory > constraints. (probably with this, one can run DevCloud with as minimum as > 1G ram). The only issue I'm facing now is that systemvm is not reachable > when it starts (pingable but not ssh-able, probably not a blocker, I only > hope :) > Will post a new image soon. > > Regards. > ________________________________________ > From: Charles Moulliard [[email protected]] > Sent: Friday, November 23, 2012 10:49 PM > To: cloudstack-dev > Subject: CloudStack 4.1-SNAPSHOT + Vagrant > > Hi, > > Does anybody has blogged somewhere how to setup using vagrant cloudstack > 4.1-SNAPSHOT ? > > Regards, > > -- > Charles Moulliard > Apache Committer / Sr. Enterprise Architect (RedHat) > Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com > -- Charles Moulliard Apache Committer / Sr. Enterprise Architect (RedHat) Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
