X-Git-Url: http://git.annexia.org/?a=blobdiff_plain;f=virt-p2v.1.html;h=579808fcdf7202a4009b1aa19afd77d37dd476f6;hb=4dfd0e1afd05220c647e8c1dfe5c8743b067daa8;hp=a795e866f67b457017ba8e044b99ef8c623aaa02;hpb=65b46ce56a110e798c9a21f99eb7969f5ca073e3;p=virt-p2v.git diff --git a/virt-p2v.1.html b/virt-p2v.1.html index a795e86..579808f 100644 --- a/virt-p2v.1.html +++ b/virt-p2v.1.html @@ -38,8 +38,10 @@
  • ISO ATTACHMENTS
    • -
  • BOOTING FROM A USB KEY INSTEAD OF A CD
    • +
  • PXE BOOTING
    • +
  • BOOTING FROM A USB KEY
  • TESTING AN ISO UNDER QEMU OR KVM
    • +
  • MAILING LIST
  • SEE ALSO
  • AUTHORS
  • COPYRIGHT
    • @@ -76,12 +78,15 @@ CUSTOM LIVE CD section below.

    machine over the network to the virtualization host machine over ssh. Therefore sshd must be running on the virtualization host, and must be accessible to that host. See SERVER REQUIREMENTS section below.

    -

    The virt-p2v script must only be run from the live CD. It isn't -designed to run outside this environment and could do Bad Things to -your machine if you try it. The script contains some checks to try to -stop you from doing this.

    +

    The virt-p2v script must only be run from the live CD environment. +It isn't designed to run outside this environment and could do Bad +Things to your machine if you try it. The script contains some checks +to try to stop you from doing this.

    Virt-p2v does not modify the physical machine, its disks, configuration etc.

    +

    USB key and PXE boot options are also available. See sections +PXE BOOTING and BOOTING FROM A USB KEY +below.

    @@ -143,6 +148,13 @@ from the physical machine's root filesystem. You should probably try this method even though occasionally it does not work.

    +
    Ask for fixed IP address and gateway + +
    +

    In this mode the live CD will ask you for a fixed IP address and +gateway address, and will configure your chosen interface with these.

    +
    +
    Configure from the shell
    @@ -164,6 +176,14 @@ interface would be:

    gateway.

    +
    QEMU user network + +
    +

    This option configures the network for use inside a QEMU user network +(http://fabrice.bellard.free.fr/qemu/qemu-doc.html#SEC30). It +should only be used by developers.

    +
    +
    Devices @@ -262,6 +282,21 @@ chance that they could coincide, which would leave a guest unable to access the virtual network.

    +
    Compression + +
    +

    Choose whether to enable or disable compression on disk images as they +are copied across the network.

    +
    +
    +

    If enabled, the -C option is passed to ssh(1). On fast networks +this can sometimes be slower.

    +
    +
    +

    NB: The disk image is still stored uncompressed on the remote host +however this option is set.

    +
    +
    Verify and proceed
    @@ -460,9 +495,44 @@ For example, Some ["sda"; "sdb"].

    network
    -

    Set this to the choice for network setup. Use either Some Auto or -Some Shell for auto-configuration or shell (manual) configuration -respectively.

    +

    Set this to the choice for network setup. Use one of:

    +
    +
    +
    Some Auto + +
    +

    for auto-configuration

    +
    + +
    Some Static + +
    +

    to specify the interface, address, netmask and gateway statically

    +
    + +
    Some Shell + +
    +

    to launch a shell

    +
    + +
    Some QEMUUserNet + +
    +

    to use a QEMU user network (developers only)

    +
    + +
    +
    static_network_config + +
    +

    This setting only applies if network is set to Some Static, +in which case you should set this to the static network settings, +a tuple of (interface, address, netmask, gateway, nameserver):

    +
    +
    +
    + Some ("eth0", "192.168.2.5", "255.255.255.0", "192.168.2.1", "192.168.2.1")
    hypervisor @@ -514,6 +584,13 @@ uniqueness so there is a very small chance that they could coincide, which would leave a guest unable to access the virtual network.

    +
    compression + +
    +

    Set this to Some false to disable compression, or Some true to +enable compression, or None to ask the user.

    +
    +

    @@ -528,12 +605,27 @@ built an existing virt-p2v-*.iso, you can just do:

    or the equivalent manual command:

      ./iso-attach virt-p2v-VERSION.iso virt-p2v
    +

    Note that ISO attachments only work with real (and emulated) CD-Rs, +not with other methods of booting such as USB keys and PXE.

    +

    +

    +
    +

    PXE BOOTING

    +

    If you wish to boot over the network using PXE, use the +livecd-iso-to-pxeboot script (part of livecd-tools).

    +
    + livecd-iso-to-pxeboot virt-p2v-$VERSION.iso
    +

    then copy the generated subdirectory tftpboot/ to the +right place for your PXE configuration.

    +

    Pre-built PXE boot images are also available on the website.

    +

    General configuration of DHCP, TFTP and PXE for network booting are +outside the scope of this document.

    -

    BOOTING FROM A USB KEY INSTEAD OF A CD

    -

    If you wish to boot from a USB keydrive, use the livecd-iso-to-disk -tool:

    +

    BOOTING FROM A USB KEY

    +

    If you wish to boot from a USB keydrive, use the livecd-iso-to-disk +script (part of livecd-tools):

      livecd-iso-to-disk virt-p2v-$VERSION.iso /dev/sdX1

    (Replace /dev/sdX1 with the actual USB device).

    @@ -555,6 +647,13 @@ you can test the P2V conversion process on the guest.

    +

    MAILING LIST

    +

    Please direct questions to the et-mgmt-tools mailing list +http://www.redhat.com/mailman/listinfo/et-mgmt-tools +<et-mgmt-tools @ redhat . com>

    +

    +

    +

    SEE ALSO

    virsh(1), http://www.libvirt.org/ocaml/,