Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Valery Sedletski

Pages: 1 [2] 3 4 ... 9
Applications / Re: VirtualBox v5.0.51 Testing
« on: April 10, 2018, 12:37:57 am »
2Mark Szkolnicki:

> Regarding physical media support - I have not ran into any difficulties at all at this testing phase - all files and installations proceeded without any errors, and I can only report that all physical optical media has booted correctly and flawlessly, as of now, for the optical drives tested.

Yes, reading the attached media from within the VM is good, once booted. But if you try to boot from a physical floppy, or physical CD, you can encounter some problems (possibly, VM will crash).

> The VirtualBox package I downloaded was dated 22/3/2018 following the link Martin created. Might there be another package floating about or that you are using? Or perhaps a global setting that enables or disables this feature, causing what I have observed?

No newer version was released. so far. I'm not aware of any global version, which disables it for all VM's. Just disable it for every VM created for now. Possibly, I'll try to disable it globally if required features are missing on your kernel, in the future.

Regarding your P.S. question - The VBox topic has generated a lot of interest, based on the number of views.

I started the new thread as one of the big problems we always have in the OS/2 / eCS / ArcaOS community is getting people to test new items or contribute to the conversation. The focus should not only be on the problems which developers and the highly technical or experienced users discuss, but also how to use and test the software properly, to allow other useful or important feedback to be obtained.. Perhaps, with a little encouragement, especially with a lot of the new users coming on-board with the release of ArcaOS, We can get a lot more testing done, which would certainly help you and others advance development of what I personally consider an important piece of software that could help my business, as VirtualPC definitely needs a more robust and flexible follow-on for our community.

"Problems" in the title always get people to shy away from testing or even asking questions, thinking their questions may be dumb, untechnical or not pertinent. We will also seriously need some documentation for VirtualBox, as the solutions we are coming up with need to be captured to allow people to consistently install and use it successfully, especially if you or others coming up with new drops in future.

Hm, I don't think the word "Problems" will get people shy away from the thread. But indeed "Testing" is better name than "Problems", I agree.

PS: BTW, in the end of older thread I added some CONFIG.SYS options to try for you. You said that you had to close Seamonkey, to run VBox successfully. I'd suspect that if you try these options, you will be able to run both at the same time (if you'll make everything correctly)

Hi Valery!

I'm not sure how many in the community are using OS/4 consistently or not at the moment.

A big number, in fact.

I myself do not use it, and I suspect the majority of users here are using a version of the IBM kernel, especially with the ArcaOS release, so you may find many testing reports varying significantly from what you may see on OS/4.

I actually would like to test it (OS/4) at some point, but I suspect if something varies significantly from what you have experienced, testing on OS/4, the difference between kernels and structures is probably the culprit. (including the slowdowns I mentioned previously with AMD-V enabled on the IBM kernel or physical media being unstable).

That why wide testing could be very important, as this VirtualBox development continues.

Indeed, not so big difference. OS/4 kernels contain some enhancements. For example, consistent hi-res timer support, based on HPET timer; Special KEE's for consistently getting curent CPU number (no -1018 error), support for CPU rendez-vous (which allows to use HW virtualization, etc., etc.)

As I said in my previous post I think we in the community need some formalized "prototype" and "final" documentation to distribute out with the OS/2 VirtualBox even if it comes in two flavours - OS/2 / eCS / ArcaOS and another for OS/4, as YMMV.

I don't think that we need two separate documentation files. Only some special notes. I think, README.OS2 file is sufficient. It did not updated since version 5.0.6. It should be enhanced more, of course, and contain OS/2-specific notes. Otherwise, documentation from Sun/Oracle applies.

Applications / Re: VirtualBox v5.0.51 Testing
« on: April 09, 2018, 11:17:29 pm »
2Mark Szkolnicki:

Ah? Yes, just tried on an IBM kernel: It enables AMD-V/VT-x by default. Not sure why, but ok, just disable it for now.

Applications / Re: VirtualBox v5.0.51 Testing
« on: April 09, 2018, 10:38:43 pm »
> "PIIX3 cannot attach drive to Secondary Master VER_IO_NOT_READY".

Did you removed the CD from your CD/DVD drive? If so, insert it back, or detach from "Media" menu. Note that Physical media support is unstable, yet. For example, you can easily fail to boot from physical media.

> Also. as a test, created a VDI based Windows 2000 VM as I happened to have one lying around. The virtualization was extremely slow (took about 3 hours to install the OS, while I was doing other things. Again don't know if that is typical of installation on VBox or not, but worth noting.

You need to use HW virtualization, to run heavy-weight OS-es (but it currently does not work on IBM kernels, so OS/4 kernels only for now)

> It seems "enable VT-x / AMD-V" are enabled by default in the settings. I was not sure about that previously in my posts to Valery in the thread "VirtualBox Problems" as the original VM I had created (Windows XP) was done under Windows 7 and Windows VirtualBox v5.0.22, so I wasn't sure if I had fiddled with the settings at some point.

No, I just created the new VM from scratch, VT-x/AMD-V is disabled. In any case, disable it if it enabled, for some weird reason (unless you have one of the latest OS/4 kernels).

win2000 may run ok without VT-x enabled, but win7 or ubuntu are slow like hell, and work conveniently only with VT-x enabled

PS: Why did you created the second topic? Is not the previous one good enough?

Applications / Re: VirtualBox problems
« on: April 09, 2018, 09:54:17 pm »
2Dave Yeo:

> You can use to set (some) DLLs to load high and save on low memory. Works mostly well with the newest kernel included with ArcaOS. With SeaMonkey closed, try running himem -b *dll in the SM program directory and retest your shared memory use. Sometimes, especially with older kernels, your better to use himem -c to only load the code high. Run himem -? to see all options including how to unmark. Experiment, don't load system DLLs high and if things start crashing, unmark.

Yes, and I have a highmem.cmd script included in the VBox distribution, which starts highmem.exe whith required parameters, to load some segments into high memory. You can easily cause your system to hang, or some API's to fail if you try to load some DLL's both code and data segments to high memory, so, different DLL require different highmem.exe options.

For FireFox/Seamonkey it is sufficient to load only code segments of XUL.DLL high. No other DLL's are required to mark for SM/FF to be working ok.

Also, there is extpack.cmd which is useful to run if you need the VNC extpack to be working. OS/2 uses 8.3 DLL names, so, some DLL names should be shortened, that is what extpack.cmd is doing with VNC extpack DLL, and one more extpack, called DTrace.

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.


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:

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?

Applications / Re: VirtualBox problems
« on: April 03, 2018, 08:17:34 pm »
2 Mark Szkolnicki:

As mentioned last night, I was able to get a VBOX VM to open consistently after a 15 second delay after the program initially opens, or after closing the 1018 error windows. However, trying it this morning, I was having the same difficulties, even after a 15 second delay, until I realized I had Seamonkey already open in the background (Seamonkey 2.35).

After closing it, I was able to start a VM, and, keeping VBOX running, to download some Windows XP update files, and then reopen and use Seamonkey normally.

However, closing Seamonkey and restarting a second time with VBOX running and reopen Seamonkey it (Seamonkey) would not open until i shut down VBOX

So yes, these are some memory-related problems. Could you, please, show me your config.sys? Also, how many physical RAM is available to OS/2 on your machine? What does XCenter "sentinel memory monitor" show?

Applications / Re: VirtualBox problems
« on: April 03, 2018, 07:26:30 pm »
2Dave Yeo:

Thanks for the log! So, it works with SET LIBCX_HIGHMEM=2 for you? That's what I talked about. Leave it permanently in your config.sys then (or only in VBox environment). Unfortunately, it works fine on my machine, so I don't experience this, so I cannot play with it and see potential workarounds. VirtualBox.exe starts fine on my machine without SET LIBCX_HIGHMEM=1. Only VBoxSDL.exe crashes without it. So, I'd recommend for now to leave SET LIBCX_HIGHMEM=2 in CONFIG.SYS permanently.

Also, there can be problems with insufficient address space on your machine. How large is VIRTUALADDRESSLIMIT on your machine? Did you tried to load VBox DLL's high? There is highmem.cmd for that purpose (you need to have highmem.exe on PATH).

PS Unfortunantely, these problems are likely to happen on each memory-hungry program like VBox, Mozilla, Qt or OpenOffice. OS/2 is a 32-bit OS. Additionally, it has special address space layout with Private/Shared/High Private/High Shared arenas, limiting each other. So, you can easily run out of address space, so no wonder.

Applications / Re: VirtualBox problems
« on: April 03, 2018, 10:20:59 am »
@Mark Szkolnicki:

> error 1018

%define VERR_INVALID_CPU_ID    (-1018)

Are you sure it is 1018, not -1018?

This means that current CPU ID is invalid. Unfortunately, there is no reliable way to determine the current CPU ID for ring0 on IBM's kernels. Currently, LAPIC ID's are used to emulate getting the CPU ID, but they are not guaranteed to be consecutive, which is assumed. If your current CPU number gets into the "hole" between valid CPU numbers, this happens. So, you're unlucky. The only way to avoid this error is currently to use OS/4 kernel. Unlike IBM kernels, it has a consistent way of getting CPU ID's which are guaranteed to be consecutive (which is assumed in VBox). So, you can try using the OS/4 kernel (if you're experienced enough)

2Dave Yeo: Do you have SET NSPR_OS2_NO_HIRES_TIMER=1 in your config.sys? If so, could you repeat the test with it disabled (just set it to an empty line in OS/2 window before running the test)?

Applications / Re: VirtualBox problems
« on: April 03, 2018, 10:09:02 am »
2Mark Szkolnicki:

> Result Code: NS_ERROR_FAILURE (0x80004005)
> Component: MachineWrap
> Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

As I said above to Dave, you either have shared memory problems, or have some required DLL's missing. As you said that you sometimes started the VM sucvcessfully, I suspect that you have (shared) memory errors.

The log generated at the time in the VirtualBox \BIN directory is as Dave also describes (mine was slightly different, as sent to you previously):

Log created: 2018-04-03T00:38:20.588000000Z
K:\VPC\VirtualBox.exe kLIBC á--comment ámint á--startvm á43cabf9e-2003-43ea-a9e0-db4fa1156a6c á--no-startvm-errormsgbox

This log is not relevant. I asked about the VM log.

> At least for me, I can get the VM's to start up more consistently with LIBCX 0.6.0 installed than under the experimental LIBCX 0.6.2, but that may just be my experience, not others.

Yes, so use libcx 0.6.0, or, better, add LIBCX_HIGHMEM=2 to your environment, if you use libcx 0.6.2

> In regards to your other question, when the Windows XP VM has opened, when the AMD-V was enabled, rendering of the desktop was exceptionally slow (sometimes minutes for the desktop icons to appear) and clicking on folders to open also took sometimes minutes. After disabling that feature, the desktop seemed to open normally, and opening folders or other icons seemed to be a lot faster (seconds not minutes).

This has nothing to do with performance. You should just disable AMD-V/VT-x on your machine.

> Just an observation and first impression, Sir. If we can get some way to consistently start VM sessions, I will try boots with the setting enabled and then disabled, to see if what I am observing is correct or not.

As I said above, fix the (shared) memory problems on your machine. Boot with which setting disabled/enabled? Did I asked you to disable/enable any options?

Applications / Re: VirtualBox problems
« on: April 03, 2018, 09:52:32 am »
What I get on the first try is
Failed to open a session for the virtual machine mint.

The virtual machine 'mint' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

This means that either you have some required DLL's missing, or incorrect version, or having high memory problems. This is not a problem with VirtusalBox itself. Did you tried LIBCX_HIGHMEM=2 before starting VBox? I don't need this on my machine, I only need this to start VBoxSDL successfully, otherwise SDL crashes. Yes, some high memory related problems, not VBox-related.

Waiting a bit after this allows the virtual machine to start.
The log seems to use a different charset,

Log created: 2018-04-03T00:38:20.588000000Z
K:\VPC\VirtualBox.exe kLIBC á--comment ámint á--startvm á43cabf9e-2003-43ea-a9e0-db4fa1156a6c á--no-startvm-errormsgbox

Yes, there are some signs (probably, quotes, probably, in unicode) in command lines which VBox uses to start its processes. That's the way it works.

Applications / Re: VirtualBox problems
« on: April 03, 2018, 02:05:15 am »
2Dave Yeo: Thanks!

2Mark Szkolnicki:

> The Logs sent were before I switched off the AMD-VT. Now done. I did not see another log generated in the \LOG subdirectory but have seen a marked improvement in speed when I can get the WindowsXP VM to start.

Improvement in speed? Compared to what? AMD-V is disabled, so what improvement can be?

> So far, the start-up is still sporadic, but I have a couple of items I am looking into.

Sporadic? What do you mean? It starts only sometimes? What error? Any logs?

> Running a test start from an ArcaOS window session the VBOX window came up, but I noted no panic screen. Perhaps I'm misunderstanding what was being requested Valery if you could provide an example of what a panic screen should look like i will see if one comes up

I don't expect any panic screen. No panic screen, according to your log.

So, what do you mean by "sporadic" startup?

Applications / Re: VirtualBox problems
« on: April 02, 2018, 11:44:30 pm »
2Mark Szkolnicki:

Did you switched AMD-V/VT-x off? According to your log, it is enabled and it failed to initialize. (I see no Guru meditation, though, so this is not that case). That is what I suggested you above: switch off AMD-V/VT-x. Why did you enabled it? It was never supported by OS/2 port of VBox. Only last builds contain some support for that, and only on OS/4 kernels!

> In regard to "Guru Meditation" - from your description I assume that it would be seen if you attempt to start VirtualBox.exe from an OS/2 window, and the program will not start at all. As that has not been the problem I have been experiencing, I'm not sure if running that test would give you any added information, but could try it if you wish.

The program will wtart, but itt will show a panic screen. The test has no relation with "Guru meditation" error, I only need to know if they fixed a hi-res timer error in your version of ACPI.PSD. As you're the first user I know having this version.

> There are 4 VBox.log files in the Windows XP \LOG subdirectory which have been generated and which I've attached below.

Thanks, but I only need the last one.

> * timerTest.html (6.44 kB - downloaded 6 times.)

This is some trash with javascript code (look into the file you attached). Please attach the text file with the test output

Applications / Re: VirtualBox problems
« on: March 31, 2018, 01:37:06 pm »
2Mark Szkolnicki:

> Understood that 5.0.51 is a developmental release Valery.

Yes, it's a development version, but not less stable than 5.0.6. I planned to update the OS/2 VBox port to a newer version. 5.0.51 is not a final one, but some intermediate version. I'll probably try to update it to more newer version.

> I actually saw the notice about v5.0.51 that Martin posted here. (He should be a reporter, as he has a nose for news <smile>)

Yes, it's possibly, Martin is guilty for a leakage ;) But anyway it's good as it could gain more attention to the project, so it is ok.

> I am testing with ArcaOS v5.0.1 installed on this machine, with the kernel updated to 14.201_SMP. eCS v2.2 is also installed on this machine on a separate partition, but has not been used for the testing, as of yet. ACPI is at the latest released level (3.23.08) on both partitions.

AMD-V/VT-x is not supported on IBM kernels so far. You need an OS/4 kernel to use HW virtualization in VBox. PSD can be any, but note that newer ACPI.PSD are incompatible with OS/4 kernels (AN just disables all CPU cores. Any hacking with it won't help, so OS/4 devs gave up on patching ACPI.PSD for working on OS/4 kernel). So, you'll need os2apic.psd or os4apic.psd, or earlier versions of ACPI.PSD for use with OS/4 kernel.

Also, as you have "brand new" 3.23.08 ACPI.PSD, could you please run this test: (Please, redirect the output to file, we need about 200 iterations of this test. This is a high resolution timer test. It is interesting to know if they fixed a hi-res timer bug in 3.23.08. It is still present in 3.23.07.)

> In regards to "Guru Mediation" screen, I have no idea as to what you are referring to. I have included the screen that comes up with the Windows XP information presented. If I have some idea as to what your referring to, and how to get it, I will include that as well.

"Guru meditation" is a VBox panic error. It should write it to the console (if you start VBox from OS/2 window), and in VBox VM log. VBox stores the VM log in Logs\VBox.log in each VM subdirectory. Yes, as far as I can see, you have AMD-V/VT-x enabled in your VM. Why did you so? It is disabled by default, and displays a warning in case you enabled it and your system lacks required API's and features. So, disable it, and it should work.

> BTW AMD-V/VT-X is indicated as "enabled" by default (see attached). However, the "invalid setting detected" message at the bottom when moused over, indicates that the current kernel doesn't allow enablement of hardware virtualization.

Yes, that's what I meant above. VBox warns you that your configuration is incorrect. So, disable AMD-V/VT-x checkbox and it should work.


>>... The link just "leaked" from the bug tracker when I gave it to Pete for testing.

> Guilty as charged, my Apologies.

Yes, I did not planned to distribute this version, but no problem ;)

Web applications / Re: Chrome...
« on: March 30, 2018, 04:47:15 pm »
This is not QEMU :) 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: Unfortunately, original site is down.

Applications / Re: VirtualBox problems
« on: March 30, 2018, 07:49:37 am »
2Mark Szkolnicki:

> Both VM's are recognized by VirtualBox, but when I attempt to boot them, more times than not I get a message "Unknown error 1018 - during initialization of the runtime" (JPG attached). The detail screen comes up with a message that "The Virtual Machine WindowsXP has terminated unexpectedly during start-up with an exit code 1 (0x1) in Component "MachineWrap" (JPG attached).

Do you have AMD-V/VT-x enabled? What kernel are you using? IBM's or OS/4? Which PSD? (acpi.psd/os2apic.psd/os4apic.psd)? Did you saw a "Guru Meditation" screen? Can you show me VM log and the VM config?

PS: No special additions version is required for 5.0.51. 5.0.51 is just a bit newer version from 5.0.6 -- no big difference, so the same 5.0.x additions should work well. Additions don't enhance performance significantly. They are for user experience with the VM to be more comfortable, e.g., shared folders, clipboard sharing, mouse pointer integration etc.

PPS: 5.0.51 is a development version, not a release. That's because it did not have special additions version. Also, I did not "released" it officially. The link just "leaked" from the bug tracker when I gave it to Pete for testing.

Pages: 1 [2] 3 4 ... 9