You can use a virt-install based deployment script to launch the Firewall Management Center Virtual.
Before you begin
Be aware that you can optimize performance by selecting the best guest caching mode for your environment. The cache mode in use will affect whether data loss occurs, and the cache mode can also affect disk performance.
Each KVM guest disk interface can have one of the following cache modes specified: writethrough, writeback, none, directsync, or unsafe. The writethrough mode provides read caching; writeback provides read and write caching; directsync bypasses the host page cache; unsafe may cache all content and ignore flush requests from the guest.
-
A cache=writethrough will help reduce file corruption on KVM guest machines when the host experiences abrupt losses of power. We recommend that you use writethrough mode.
-
However, cache=writethrough can also affect disk performance due to more disk I/O writes than cache=none.
-
If you remove the cache parameter on the --disk option, the default is writethrough.
-
Not specifying a cache option may also significantly reduce the time required for the VM creation. This is due to the fact that some older RAID controllers have poor disk caching capability. Hence, disabling disk caching (cache=none) and thus defaulting to writethrough, helps ensure data integrity.
Procedure
|
1. |
Create a virt-install script called “virt_install_fmc.sh”.
The name of the Firewall Management Center Virtual instance must be unique across all other virtual machines (VMs) on this KVM host. The Firewall Management Center Virtual can support one network interface. The virtual NIC must be Virtio.
Example:
virt-install \
--connect=qemu:///system \
--network network=default,model=virtio \
--name=fmcv \
--arch=x86_64 \
--cpu host \
--vcpus=4 \
--ram=28672 \
--os-type=generic \
--virt-type=kvm \
--import \
--watchdog i6300esb,action=reset \
--disk path=<fmc_filename>.qcow2,format=qcow2,device=disk,bus=virtio,cache=writethrough \
--disk path=<day0_filename>.iso,format=iso,device=cdrom \
--console pty,target_type=serial \
--serial tcp,host=127.0.0.1:<port>,mode=bind,protocol=telnet \
--force
Note
In the deployment script, ensure to set the value of the --os-type parameter to generic for the deployment process to correctly identify the platform on which the virtual instance is deployed.
|
|
2. |
Run the virt_install script:
Example:
/usr/bin/virt_install_fmc.sh
Starting install...
Creating domain...
A window appears displaying the console of the VM. You can see that the VM is booting. It takes a few minutes for the VM to boot. Once the VM stops booting you can issue CLI commands from the console screen.
|