This is installed on the live CD as /etc/init.d/p2v, and it causes the
live CD to boot into the P2V configuration tool (see next).
-virt-p2v.sh
+virt-p2v.ml
- This is the virt-p2v.sh P2V configuration tool itself. It is
- installed on the live CD as /usr/bin/virt-p2v.sh and runs after the
+ This is the virt-p2v.ml P2V configuration tool itself. It is
+ installed on the live CD as /usr/bin/virt-p2v.ml and runs after the
live CD has booted. All the P2V stuff happens from this script. It
uses the 'dialog' program to ask questions.
+inittab
+
+ Replacement /etc/inittab.
+
General implementation plan
----------------------------------------------------------------------
For (b) we can simply use 'dd' and 'ssh'. The general plan is to do
this:
- dd if=/dev/disk | gzip | ssh xenhost 'cat > /var/lib/xen/images/disk.img'
+ dd if=/dev/disk | ssh -C xenhost 'cat > /var/lib/xen/images/disk.img'
If the user doesn't have sshd installed on the Xen host, then they can
also opt for a pure TCP transport:
- dd if=/dev/disk | gzip | nc xenhost port
+ dd if=/dev/disk | nc xenhost port
and on the remote host they do:
- nc -l -p port > /var/lib/xen/images/disk.img
+ nc -kl port > /var/lib/xen/images/disks
For (c) we can use device-mapper snapshots to mount a ramdisk above
the disks themselves. This allows us to make non-destructive changes
to files, and still see the "modified" block device (d). A hairy
-shell script looks for candidate files to modify.
+script looks for candidate files to modify.
Non-generic virt-p2v
----------------------------------------------------------------------
The above describes the generic virt-p2v, which asks users questions
after boot. It is also possible to build your own live CD, based on
-virt-p2v which has various settings compiled in, so it runs
-automatically.
\ No newline at end of file
+virt-p2v, which has various settings compiled in so it runs
+automatically.
git.annexia.org / virt-p2v.git / blobdiff