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
When connecting to VNC installation message is shown:
"There isn't enough memory to create a ramdisk device"
Without rescue-64 pro:
in other tries "qemu-system-x86_64: Invalid parameter -localtime" at the end. (used the pull request and solved that error).
From Ubuntu using putty I'm able to initiate windows installation but in drives list I'm getting:
Drive 0 Unallocated Space 4.0 MB
Drive 1 Unallocated Space 4.0 MB
Showing "This partition is too small..." error.
As I have many distros options can you tell me if there is any better to make it work?
The server also supports rescue mode rescue-64 pro, do you recommend to use it?
on Raid Disc, Windows installation may not bot work.
About the RAM issue, edit the script to spare 1GB Free RAM for the system.
Currently it is sparing only 200 or 500MB ram
Четверг, 18 июня 2020, 0:03 +03:00 от luidiva ***@***.***>:
Installed through rescue-64 pro:
When connecting to VNC installation message is shown:
"There isn't enough memory to create a ramdisk device"
32gb
500gb nvme soft raid
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub , or unsubscribe .
Installed through rescue-64 pro:
When connecting to VNC installation message is shown:
"There isn't enough memory to create a ramdisk device"
Without rescue-64 pro:
in other tries "qemu-system-x86_64: Invalid parameter -localtime" at the end. (used the pull request and solved that error).
From Ubuntu using putty I'm able to initiate windows installation but in drives list I'm getting:
Showing "This partition is too small..." error.
As I have many distros options can you tell me if there is any better to make it work?
The server also supports rescue mode rescue-64 pro, do you recommend to use it?
32gb
500gb nvme soft raid
Thank you
@mediabots
The text was updated successfully, but these errors were encountered: