Note that disk controller must be SATA not SCSI. (#424)
The image hang on startup on the SCSI controller, which is the default controller type for custom VMs in VMWare Fusion.
This commit is contained in:
committed by
Pascal Vizeli
parent
e7da2e0779
commit
08fac89fb0
@@ -4,6 +4,7 @@ Using this VMDK in a virtual machine requires the following:
|
|||||||
|
|
||||||
- Operating system: Other 4.x or later Linux (64-bit)
|
- Operating system: Other 4.x or later Linux (64-bit)
|
||||||
- Enabled support for UEFI boot
|
- Enabled support for UEFI boot
|
||||||
|
- SATA disk controller
|
||||||
- Minimal of 1GB RAM
|
- Minimal of 1GB RAM
|
||||||
- At least 2x vCPU
|
- At least 2x vCPU
|
||||||
- An assigned network
|
- An assigned network
|
||||||
@@ -14,6 +15,4 @@ Currently, we only publish a VMDK virtual disk, due to issues with our previous
|
|||||||
|
|
||||||
- HyperV
|
- HyperV
|
||||||
- VirtualBox
|
- VirtualBox
|
||||||
- VMware
|
- VMware
|
||||||
|
|
||||||
You might need to convert the VMDK into a different format that is accepted by your virtualization platform of choice.
|
|
||||||
Reference in New Issue
Block a user