256
Applications / Re: VirtualBox problems
« on: April 09, 2018, 09:33:27 pm »
2Mark Szkolnicki:
> First in regard to one of your previous questions the 1018 error could be "-1018" (See attached JPG). When I saw a "dash" after "Unknown error", I normally assume in english it was a pause between two phrases, not a "minus" mark.
So yes, it is -1018, which means VERR_INVALID_CPU_ID, that is what I suggested. Probably, it will be some workaround for that in the future, but now only this way, until your LAPIC ID's are consecutive.
> VIRTUALADDRESSLIMIT=2560
It's too little! I have VIRTUALADDRESSLIMIT=3072 on all my three machines, and everything is working. Please try to change VIRTUALADDRESSLIMIT to 3072, and THREADS to 511, PROCESSES to 128 explicitly. Also, it is desirable to change JFS cache to some lesser explicit value, like:
VIRTUALADDRESSLIMIT=3072
THREADS=511
PROCESSES=156
ifs=d:\os2\jfs.ifs /autocheck:* /cache:128000 /lazy:8,60,5 /p1
-- Here, JFS cache is limited to 128 MB, threads is limited to 511 threads in the system, PROCESSES are limited to 156 processes max. THREADS and PROCESSES eat up some structures per each thread/process, and they consume some hundreds of MB in the system arena, which could be too much. JFS cache is limited to 20% of available RAM, which could be too much too. (20% from 3 GB is 614 MB, which is a large % from 1 GB of kernel memory, if VIRTUALADDRESSLIMIT=3072, so JFS cache should be decreased to say, 128 MB. The exact number should be determined in Theseus). THREADS/PROCESSES/JFS cache consume memory above VIRTUALADDRESS limit (kernel memory), while VBox consumes memory below it. So, if you have too little VIRTUALADDRESSLIMIT, it can be not sufficient for VBOX. If you have VIRTUALADDRESSLIMIT near to 3072, then only 1024 MB above it is available for kernel and drivers. So, if THREADS/PROCESSES/JFS cache are not limited explicitly, you can easily run out of kernel memory.
PS: How much memory you assigned to your VM? 330 MB?
> First in regard to one of your previous questions the 1018 error could be "-1018" (See attached JPG). When I saw a "dash" after "Unknown error", I normally assume in english it was a pause between two phrases, not a "minus" mark.
So yes, it is -1018, which means VERR_INVALID_CPU_ID, that is what I suggested. Probably, it will be some workaround for that in the future, but now only this way, until your LAPIC ID's are consecutive.
> VIRTUALADDRESSLIMIT=2560
It's too little! I have VIRTUALADDRESSLIMIT=3072 on all my three machines, and everything is working. Please try to change VIRTUALADDRESSLIMIT to 3072, and THREADS to 511, PROCESSES to 128 explicitly. Also, it is desirable to change JFS cache to some lesser explicit value, like:
VIRTUALADDRESSLIMIT=3072
THREADS=511
PROCESSES=156
ifs=d:\os2\jfs.ifs /autocheck:* /cache:128000 /lazy:8,60,5 /p1
-- Here, JFS cache is limited to 128 MB, threads is limited to 511 threads in the system, PROCESSES are limited to 156 processes max. THREADS and PROCESSES eat up some structures per each thread/process, and they consume some hundreds of MB in the system arena, which could be too much. JFS cache is limited to 20% of available RAM, which could be too much too. (20% from 3 GB is 614 MB, which is a large % from 1 GB of kernel memory, if VIRTUALADDRESSLIMIT=3072, so JFS cache should be decreased to say, 128 MB. The exact number should be determined in Theseus). THREADS/PROCESSES/JFS cache consume memory above VIRTUALADDRESS limit (kernel memory), while VBox consumes memory below it. So, if you have too little VIRTUALADDRESSLIMIT, it can be not sufficient for VBOX. If you have VIRTUALADDRESSLIMIT near to 3072, then only 1024 MB above it is available for kernel and drivers. So, if THREADS/PROCESSES/JFS cache are not limited explicitly, you can easily run out of kernel memory.
PS: How much memory you assigned to your VM? 330 MB?
But anyway it's good as it could gain more attention to the project, so it is ok.
Though, there is QEMU 0.11.0 ported to OS/2 by Sawataishi Jun from Japan in 2009. It works fine on my machine, there are i386 and x86_64 versions available. I have it on my ftp: