summaryrefslogtreecommitdiff
path: root/Documentation/VMware.md
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/VMware.md')
-rw-r--r--Documentation/VMware.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/VMware.md b/Documentation/VMware.md
index b985df573d..a0c0da334a 100644
--- a/Documentation/VMware.md
+++ b/Documentation/VMware.md
@@ -4,7 +4,7 @@
There are currently issues with running Serenity in VMware. Please refer to the [open issue](https://github.com/SerenityOS/serenity/issues/5716) for a list of currently known issues. Anything that doesn't currently work will be noted in this document.
## Creating the disk image
-Before creating a disk image that will work in VMware, you will need to create a GRUB image as described in the [Serenity installation guide](https://github.com/SerenityOS/serenity/blob/master/Documentation/INSTALL.md). Please skip the final step of that section, as that is only relevant for putting the image onto a real drive. You **cannot** use the same disk image created for QEMU. Using that image will halt immediately with the message ``FATAL: No bootable medium found! System halted.``
+Before creating a disk image that will work in VMware, you will need to create a GRUB image as described in the [Serenity installation guide](BareMetalInstallation.md). Please skip the final step of that section, as that is only relevant for putting the image onto a real drive. You **cannot** use the same disk image created for QEMU. Using that image will halt immediately with the message ``FATAL: No bootable medium found! System halted.``
The easiest way to convert the disk image is with QEMU: