1396
Comment: Link to threads.
|
1394
formatting fix
|
Deletions are marked like this. | Additions are marked like this. |
Line 36: | Line 36: |
See also this email thread about [[https://lists.launchpad.net/launchpad-dev/msg03456.html|running Launchpad in a virtual machine]], and this [[https://lists.launchpad.net/launchpad-dev/msg03454.html|discussion of the differences]] between running in a [[[[Running/Schroot|chroot]] environment and running a VM. | See also this email thread about [[https://lists.launchpad.net/launchpad-dev/msg03456.html|running Launchpad in a virtual machine]], and this [[https://lists.launchpad.net/launchpad-dev/msg03454.html|discussion of the differences]] between running in a [[Running/Schroot|chroot]] environment and running a VM. |
This page explains how to set up and run Launchpad (for development) inside a VM.
Why?
Launchpad development setup makes numerous changes to your machine; its nice to be unaffected by those except when you are actually doing such development.
Also, launchpad has limitations on concurrent testing per-machine and so forth - multiple VM's can be used to work around this.
Make a VM image
- Install KVM
% sudo apt-get install virt-manager
- Download the Lucid server ISO
- Run virt-manager.
- Double click on localhost(QEMU)
- click on the New virtual machine icon
- follow your nose here, using the ISO as the install media, and allocating no less than 2G of disk and 1G of memory. I suggest 4G if you can spare it.
After its installed, connect to the image and install acpid and openssh-server
- Use ssh-copy-id to copy your public key into the VM.
ssh -A <vm IP address> to connect to the VM. You can now follow the getting-started on LP instructions.
References
See also this email thread about running Launchpad in a virtual machine, and this discussion of the differences between running in a chroot environment and running a VM.