16.2.7 zlib License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428 16.2.8 Apache License v2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428 16.2.9 OpenSSL License disaster recovery. Once installed, a virtual machine and its virtual hard disks can be considered a container that can be arbitrarily frozen, woken up, copied, backed up, and transported between hosts. On iSCSI target directly without the extra overhead that is required for virtualizing hard disks in container files. See chapter 5.10, iSCSI Servers, page 104. – PXE Network boot. The integrated virtual network

17.2.7 zlib License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456 17.2.8 Apache License v2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456 17.2.9 OpenSSL License disaster recovery. Once installed, a virtual machine and its virtual hard disks can be considered a container that can be arbitrarily frozen, woken up, copied, backed up, and transported between hosts. Using iSCSI target directly without the extra overhead that is required for virtualizing hard disks in container files. See chapter 6.10, iSCSI Servers, page 124. – PXE Network boot. The integrated virtual network

16.2.7 zlib License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 16.2.8 Apache License v2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 16.2.9 OpenSSL License disaster recovery. Once installed, a virtual machine and its virtual hard disks can be considered a container that can be arbitrarily frozen, woken up, copied, backed up, and transported between hosts. Using iSCSI target directly without the extra overhead that is required for virtualizing hard disks in container files. See chapter 5.10, iSCSI Servers, page 124. – PXE Network boot. The integrated virtual network

17.2.7 zlib License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 17.2.8 Apache License v2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 17.2.9 OpenSSL License disaster recovery. Once installed, a virtual machine and its virtual hard disks can be considered a container that can be arbitrarily frozen, woken up, copied, backed up, and transported between hosts. Using iSCSI target directly without the extra overhead that is required for virtualizing hard disks in container files. See chapter 6.10, iSCSI Servers, page 124. – PXE Network boot. The integrated virtual network

17.2.7 zlib License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 17.2.8 Apache License v2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 17.2.9 OpenSSL License disaster recovery. Once installed, a virtual machine and its virtual hard disks can be considered a container that can be arbitrarily frozen, woken up, copied, backed up, and transported between hosts. Using iSCSI target directly without the extra overhead that is required for virtualizing hard disks in container files. See chapter 6.10, iSCSI Servers, page 124. – PXE Network boot. The integrated virtual network

16.2.7 zlib License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 16.2.8 Apache License v2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 16.2.9 OpenSSL License disaster recovery. Once installed, a virtual machine and its virtual hard disks can be considered a container that can be arbitrarily frozen, woken up, copied, backed up, and transported between hosts. Using iSCSI target directly without the extra overhead that is required for virtualizing hard disks in container files. See chapter 5.10, iSCSI Servers, page 124. – PXE Network boot. The integrated virtual network

16.2.7 zlib License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 16.2.8 Apache License v2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 16.2.9 OpenSSL License disaster recovery. Once installed, a virtual machine and its virtual hard disks can be considered a container that can be arbitrarily frozen, woken up, copied, backed up, and transported between hosts. Using iSCSI target directly without the extra overhead that is required for virtualizing hard disks in container files. See chapter 5.10, iSCSI Servers, page 124. – PXE Network boot. The integrated virtual network

disaster recovery. Once installed, a virtual machine and its virtual hard disks can be considered a container that can be arbitrarily frozen, woken up, copied, backed up, and transported between hosts. On iSCSI target directly without the extra overhead that is required for virtualizing hard disks in container files. See chapter 5.10, iSCSI Servers, page 100. – PXE Network boot. The integrated virtual network It should be possible to use Oracle VM VirtualBox on most systems based on Linux kernel 2.6, 3.x, 4.x or 5.x using either the Oracle VM VirtualBox installer or by doing a manual installation. See chapter

disaster recovery. Once installed, a virtual machine and its virtual hard disks can be considered a container that can be arbitrarily frozen, woken up, copied, backed up, and transported between hosts. On mem- ory the VM should have, what hard disks Oracle VM VirtualBox should virtualize through which container files, what CDs are mounted. They also include state information, such as: whether the VM is currently iSCSI target directly without the extra overhead that is required for virtualizing hard disks in container files. See chapter 5.10, iSCSI Servers, page 96. – PXE Network boot. The integrated virtual network

disaster recovery. Once installed, a virtual machine and its virtual hard disks can be considered a container that can be arbitrarily frozen, woken up, copied, backed up, and transported between hosts. On iSCSI target directly without the extra overhead that is required for virtualizing hard disks in container files. See chapter 5.10, iSCSI Servers, page 104. – PXE Network boot. The integrated virtual network It should be possible to use Oracle VM VirtualBox on most systems based on Linux kernel 2.6, 3.x, 4.x or 5.x using either the Oracle VM VirtualBox installer or by doing a manual installation. See chapter