... | ... | @@ -18,7 +18,7 @@ Note that we no longer support 32-bit OS images. If you have 32-bit only machine |
|
|
|
|
|
When we talk about images, we are referring to images created with Emulab's [Frisbee disk imaging system](http://www.cs.utah.edu/flux/papers/frisbee-usenix03-base.html). By (our) convention, these files end in *.ndz*. There are two basic types of images: _whole-disk_ and _partition_.
|
|
|
|
|
|
_Whole-disk images_ include an x86 DOS-style Master Boot Record (MBR) which includes a _partition table_ describing one or more partitions on the disk. Each partition has a type, offset and size. The type is used by the imaging system to determine what OS is in the partition. These images are no longer supported.
|
|
|
_Whole-disk images_ include an x86 DOS-style Master Boot Record (MBR) which includes a _partition table_ describing one or more partitions on the disk. Each partition has a type, offset and size. The type is used by the imaging system to determine what OS is in the partition. **These images are no longer supported**.
|
|
|
|
|
|
_Partition images_ include the contents of a single DOS partition. The important thing to understand here is that a partition image cannot be properly restored to a disk unless the disk already has a valid MBR which defines the partitions.
|
|
|
|
... | ... | @@ -29,7 +29,7 @@ and one 3GB partition for swap. You can download this MBR from the Utah |
|
|
downloads directory at
|
|
|
[http://www.emulab.net/downloads/emulab-mbr3.dd](http://www.emulab.net/downloads/emulab-mbr3.dd)
|
|
|
|
|
|
Note that at this time, booting with GPT partitions is not supported. Since we only support MBR on the boot disk, you will not be able to use more that 2TB of that disk.
|
|
|
Note that at this time, **booting with GPT partitions is not supported**. Since we only support MBR on the boot disk, **you will not be able to use more that 2TB of the boot disk**.
|
|
|
|
|
|
### Images in the database
|
|
|
|
... | ... | |