You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
QEMU cannot read the provided VMDK. This happens when the OS tries to read the system.ini file, failing by saying the file does not exist. VMDK works fine on VMware.
To Reproduce
Steps to reproduce the behavior:
Boot DogOS with the following command: qemu-system-i386 -cdrom DogOS.iso -hda Filesystem.vmdk -boot d -m 2G
OS throws error saying file does not exist.
Expected behavior
DogOS should boot into the shell with no errors, loading the system.ini and users.ini file.
Screenshots Screenshot from Kold
DogOS Info
DogOS Version: 0.0.1
DogOS Branch: main
Additional context
Problem reproduced on my Windows 11 machine with the latest QEMU version and new OS files.
The text was updated successfully, but these errors were encountered:
Describe the bug
QEMU cannot read the provided VMDK. This happens when the OS tries to read the
system.ini
file, failing by saying the file does not exist. VMDK works fine on VMware.To Reproduce
Steps to reproduce the behavior:
qemu-system-i386 -cdrom DogOS.iso -hda Filesystem.vmdk -boot d -m 2G
Expected behavior
DogOS should boot into the shell with no errors, loading the
system.ini
andusers.ini
file.Screenshots
![image](https://user-images.githubusercontent.com/48397556/164943278-b3ca13ab-7df7-47cc-b1eb-20ee7444d912.png)
Screenshot from Kold
DogOS Info
Additional context
Problem reproduced on my Windows 11 machine with the latest QEMU version and new OS files.
The text was updated successfully, but these errors were encountered: