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 (how much memory the VM should have, what hard disks VirtualBox should virtualize through which container files, what CDs are mounted etc.) as well as state information (whether the VM is currently running iSCSI target directly without the extra overhead that is required for virtualizing hard disks in container files. For details, see chapter 5.10, iSCSI servers, page 98. – PXE Network boot. The integrated

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 supports the following types of disk image files: • VDI. Normally, Oracle VM VirtualBox uses its own container format for guest hard disks. This is called a Virtual Disk Image (VDI) file. This format is used

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 (how much memory the VM should have, what hard disks VirtualBox should virtualize through which container files, what CDs are mounted etc.) as well as state information (whether the VM is currently running iSCSI target directly without the extra overhead that is required for virtu- alizing hard disks in container files. For details, see chapter 5.10, iSCSI servers, page 80. – PXE Network boot. The integrated

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 (how much memory the VM should have, what hard disks VirtualBox should virtualize through which container files, what CDs are mounted etc.) as well as state information (whether the VM is currently running iSCSI target directly without the extra overhead that is required for virtu- alizing hard disks in container files. For details, see chapter 5.10, iSCSI servers, page 82. – PXE Network boot. The integrated

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 (how much memory the VM should have, what hard disks VirtualBox should virtualize through which container files, what CDs are mounted etc.) as well as state information (whether the VM is currently running iSCSI target directly without the extra overhead that is required for virtu- alizing hard disks in container files. For details, see chapter 5.10, iSCSI servers, page 83. – PXE Network boot. The integrated

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 (how much memory the VM should have, what hard disks VirtualBox should virtualize through which container files, what CDs are mounted etc.) as well as state information (whether the VM is currently running iSCSI target directly without the extra overhead that is required for virtu- alizing hard disks in container files. For details, see chapter 5.10, iSCSI servers, page 82. – PXE Network boot. The integrated

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 supports the following types of disk image files: • VDI. Normally, Oracle VM VirtualBox uses its own container format for guest hard disks. This is called a Virtual Disk Image (VDI) file. This format is used

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 supports the following types of disk image files: • VDI. Normally, Oracle VM VirtualBox uses its own container format for guest hard disks. This is called a Virtual Disk Image (VDI) file. This format is used

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 supports the following types of disk image files: • VDI. Normally, Oracle VM VirtualBox uses its own container format for guest hard disks. This is called a Virtual Disk Image (VDI) file. This format is used

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 supports the following types of disk image files: • VDI. Normally, Oracle VM VirtualBox uses its own container format for guest hard disks. This is called a Virtual Disk Image (VDI) file. This format is used