Virt-install Examples: Difference between revisions
Line 9: | Line 9: | ||
Make sure the ISO image file ( /archive/rhel-server-7.3-x86_64-dvd.iso in this example) can be read by the user "qemu". | Make sure the ISO image file ( /archive/rhel-server-7.3-x86_64-dvd.iso in this example) can be read by the user "qemu". | ||
The following example assumes that the virtual machine image storage does not exist and it has to be created. The size of the image will be 4 GB and the image format will be by default "qcow2". The example also assumes that the virtualization host [[Linux_Virtualization_Concepts#Storage_Pool|storage pool]] is active and deployed in /main-storage-pool. The virtual machine will get [[Linux_Virtualization_Concepts#Networking_and_KVM_Virtualization|"default" networking]]. | The following example assumes that the virtual machine image storage does not exist and it has to be created. The size of the image will be 4 GB and the image format will be by default "qcow2". The example also assumes that the virtualization host [[Linux_Virtualization_Concepts#Storage_Pool|storage pool]] is active and deployed in /main-storage-pool. It is recommended practice to follow the [[Linux_Virtualization_Naming_Conventions#Virtual_Machine_Image_Naming_Convention|virtual machine image name convention]] when naming the media to use for storing the virtual machine image. | ||
The virtual machine will get [[Linux_Virtualization_Concepts#Networking_and_KVM_Virtualization|"default" networking]]. | |||
<pre> | <pre> |
Revision as of 21:12, 28 June 2017
Internal
Examples
Text-Based Anaconda Guest Installation
Make sure the ISO image file ( /archive/rhel-server-7.3-x86_64-dvd.iso in this example) can be read by the user "qemu".
The following example assumes that the virtual machine image storage does not exist and it has to be created. The size of the image will be 4 GB and the image format will be by default "qcow2". The example also assumes that the virtualization host storage pool is active and deployed in /main-storage-pool. It is recommended practice to follow the virtual machine image name convention when naming the media to use for storing the virtual machine image.
The virtual machine will get "default" networking.
virt-install --name testvm-01 --memory 1024 --vcpus 2 --os-type=linux --os-variant=rhel7.3 \ --location /archive/rhel-server-7.3-x86_64-dvd.iso --extra-args="console=tty0 console=ttyS0,115200n8" --disk=/archive/rhel-server-7.3-x86_64-dvd.iso,device=cdrom \ --disk=/main-storage-pool/testvm-01.img,size=4 \ --network=default \ --graphics none
Organizatorium
NAT (TO TEST):
virt-install --network=default --name=rhel7-machine --ram=756 --vcpus=4 --os-type=linux --os-variant=rhel7
External DHCP server (TO TEST):
virt-install --network=br0 \ --name=rhel7-machine --ram=756 --vcpus=4 \ --os-type=linux --os-variant=rhel7
Static IPV4 Address (TO TEST):
virt-install \ --network=br0 \ --name=rhel7-machine --ram=756 --vcpus=4 \ --os-type=linux --os-variant=rhel7 \ --extra-args="ip=192.168.1.2::192.168.1.1:255.255.255.0:test.example.com:eth0:n one
The arguments of the --extra-args parameter specify the static network setting, using the following structure:
ip=[ip]::[gateway]:[netmask]:[hostname]:[interface]:[autoconf]