OS2 World Community Forum

OS/2, eCS & ArcaOS - Technical => Applications => Topic started by: Martin Iturbide on November 10, 2016, 06:34:54 pm

Title: VirtualBox 5.0.6 First Impressions
Post by: Martin Iturbide on November 10, 2016, 06:34:54 pm
Hi.

Please post your first impressions about the VirtualBox 5.0.6 beta port.

Screenshots and any tricks you are using are also welcome.

Remember also that the bugs goes to the SVN ticketing system: http://trac.netlabs.org/vbox/report

Regards
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Greggory Shaw on November 10, 2016, 07:41:01 pm
Had to move vboxdrv.sys  to x:\OS2\BOOT for it to load.

Pmdll shows virtualbox.exe is missing aio.dll and won't start, where do you get this dll ?

Nevermind on aio.dll use:

Code: [Select]
yum install libaio
How do you set VBOX_USER_HOME ?

And can't get DVD to boot install disk only iso so far (any tips) ?  - Ticket #45 only iso so far.





Greggory
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 10, 2016, 09:08:50 pm
2Gregory Shaw: Please, Install rpm packages listed at Netlabs VBox project first: http://trac.netlabs.org/vbox/. No need in VBOX_USER_HOME, no such variable needed. And, ISO's should work, as well as physical CD's/DVD's (Indeed, physical harddisk, CD's and floppies are supported. But floppy access is not very stable atm). You need to capture the CD/DVD from VBox menu: Devices->Optrical disks->Drive X:. Though, booting from a CD may not work as this feature is not very stable, yet. Also, you may try Direct Access/Passthrough option in CD properties (Media page in VM properties), maybe, it will help.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Greggory Shaw on November 10, 2016, 09:27:27 pm
2Gregory Shaw: Please, Install rpm packages listed at Netlabs VBox project first: http://trac.netlabs.org/vbox/. No need in VBOX_USER_HOME, no such variable needed.

I was thinking that would move the 'Default Machine Folder', but that option in under File => Preferences => General

Quote

 And, ISO's should work, as well as physical CD's/DVD's (Indeed, physical harddisk, CD's and floppies are supported. But floppy access is not very stable atm). You need to capture the CD/DVD from VBox menu: Devices->Optrical disks->Drive X:. Though, booting from a CD may not work as this feature is not very stable, yet. Also, you may try Direct Access/Passthrough option in CD properties (Media page in VM properties), maybe, it will help.

Booting from DVD Windows isn't working, but just tested installing Ubuntu-12.04.5 Server from ISO is good so far !

So, what's the message that OS/2 will not work ?


Thx Valery for the info !
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 10, 2016, 09:31:34 pm
There seems to be some read errors when reading the boot CD, but checking/unchecking the "Passthrough" checkbox may help, as it switches between different disk access methods, one of which may work better.

Quote
So, what's the message that OS/2 will not work ?

what do you mean?
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Greggory Shaw on November 10, 2016, 09:44:26 pm
There seems to be some read errors when reading the boot CD, but checking/unchecking the "Passthrough" checkbox may help, as it switches between different disk access methods, one of which may work better.

Quote
So, what's the message that OS/2 will not work ?

what do you mean?

Sorry, never mind forgot my CPU does have VT/x acceleration.  I'll check the Passthrough option as soon as Ubuntu is finished installing.

Also, it must have just been the DVD.  I tried both a Bootable Linux CD and Windows DVD, and they both worked !
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 10, 2016, 10:04:10 pm
But VT-x/AMD-V is not supported on OS/2 host atm, as some required features are missing from OS/2 kernel. So, still no way to start OS/2 guest on OS/2 host, as it requires hardware virtualization. Though, maybe, software virtualization will be enhanced, but it requires a lot of work.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Greggory Shaw on November 10, 2016, 10:11:52 pm
So, still no way to start OS/2 guest on OS/2 host, as it requires hardware virtualization...

Thank you, I still have VPC/2 so I'm good !
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Andi B. on November 11, 2016, 09:00:10 am
How is the quality/reliability of the network stuff in this beta? Stable and fast?

Our old VBOX does have some issues. AFAIR no ping/tracerte/... and problems with multicast packets. Also bridged network mode did not work.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: R.M. Klippstein on November 11, 2016, 03:05:07 pm
Hi Andi B. I've been using r-141 for about 2 months now and it is a definite step up from the 1.6.x series-- however it is a beta and has quite a few problems to overcome but valerius is well aware of whats needed and will resolve them in the future, I'm sure. Currently its at r-143.

klipp
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 11, 2016, 05:10:16 pm
2Andi B.: Network is just the same as it was in older version. NAT just works, as previously. But TAPOS2 is broken -- needs to be repaired. Ping/tracerte not working -- yes. But I suspect it is the same as on Windows an Linux hosts.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Doug Bissett on November 11, 2016, 08:23:54 pm
My first attempt wasn't very successful.

I can get to the first screen. I can define a new guest machine. However, when I try to start that machine (new VDI, and pointing to the real DVD drive, with a WinXP PRO CD) It complains, immediately, and says to check the log. Okay, the log says it failed to find some files, in my old VirtualBox directory (which is just left over from before, the old VBOX was not installed). I have no idea where it is getting that stuff from. I don't think it even gets far enough to think about using the DVD drive.

It also appears that the VBOX_USER_HOME environment variable is used in some places, but ignored in others (I HATE using that %HOME% directory). However, that isn't what is causing the problem. I deleted the whole directory from the old VBOX setup, and it still wants to use it. More work to be done there.

Quote
2Andi B.: Network is just the same as it was in older version. NAT just works, as previously. But TAPOS2 is broken -- needs to be repaired. Ping/tracerte not working -- yes.

TAP has been badly broken, forever. It worked, with the old VBox but killed machine (host and guest) network performance. NAT worked fine.

Quote
But I suspect it is the same as on Windows an Linux hosts.

I don't understand what you mean by this. TAP is not used with windows, or Linux (AFAIK). There is Bridged network support, which works fine (in windows host, at least).
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Martin Iturbide on November 11, 2016, 11:55:44 pm
Hi

Once I installed the dependencies with ANPM (seems like there is a different package called "SDL" and "sdl" that makes some conflicts), and I set the driver on the config.sys, VirtualBox was working ok here.

I installed a Windows XP image just to try. I need to keep testing it.

Regards
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 12, 2016, 02:36:31 am
2Doug Bissett:

Quote
It also appears that the VBOX_USER_HOME environment variable is used in some places, but ignored in others (I HATE using that %HOME% directory). However, that isn't what is causing the problem. I deleted the whole directory from the old VBOX setup, and it still wants to use it. More work to be done there.

I don't know what is the VBOX_USER_HOME variable. Never used it. VBox global config is in %HOME%/.config/VirtualBox. Also, older VBox versions used %HOME%/.VirtualBox for that. New VBox can take the older VBox config directory, if it sees it. Also note that the format of XML files has changed, since the old version. And Vbox may convert them to the new format, so then older VBox will not understand them. Virtual machines are located by default in the %HOME%/VirtualBox VMs. Probably, you have left references to old VM dir in global config. You may try to delete the global config, change the path to a VMs dir in it, or change the VM's path in File->Settings->General->Folder for VMs by default.

Quote
Quote
    2Andi B.: Network is just the same as it was in older version. NAT just works, as previously. But TAPOS2 is broken -- needs to be repaired. Ping/tracerte not working -- yes.

TAP has been badly broken, forever. It worked, with the old VBox but killed machine (host and guest) network performance. NAT worked fine.

As I tried TAP in older VBox, it just worked. Never tested its performance, but yes, people said it was very bad. But now it does not work at all.

Quote
Quote
    But I suspect it is the same as on Windows an Linux hosts.

I don't understand what you mean by this. TAP is not used with windows, or Linux (AFAIK). There is Bridged network support, which works fine (in windows host, at least).

I mean that ping/tracerte doesn't work as it is in windows or linux. I did not changed anythying specifically for OS/2 host to break it, compared to Linux/Windows. Network code is the same.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 12, 2016, 02:49:56 am
2Martin: "sdl" is older incorrect package. Please, remove it. The correct and newer package name is "SDL".
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 12, 2016, 03:01:51 am
PS: Searched for "VBOX_USER_HOME" string in sources, it looks that it is used only to override the %HOME%/.config/VirtualBox, not the VM's directory.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Doug Bissett on November 12, 2016, 04:46:20 am
Quote
2Doug Bissett:

Quote
    It also appears that the VBOX_USER_HOME environment variable is used in some places, but ignored in others (I HATE using that %HOME% directory). However, that isn't what is causing the problem. I deleted the whole directory from the old VBOX setup, and it still wants to use it. More work to be done there.

I don't know what is the VBOX_USER_HOME variable. Never used it. VBox global config is in %HOME%/.config/VirtualBox. Also, older VBox versions used %HOME%/.VirtualBox for that. New VBox can take the older VBox config directory, if it sees it. Also note that the format of XML files has changed, since the old version. And Vbox may convert them to the new format, so then older VBox will not understand them. Virtual machines are located by default in the %HOME%/VirtualBox VMs. Probably, you have left references to old VM dir in global config. You may try to delete the global config, change the path to a VMs dir in it, or change the VM's path in File->Settings->General->Folder for VMs by default.

From the Readme-OS2.txt file:
Code: [Select]
6. Note that by default VirtualBox stores all user data in the
   %HOME%\.VirtualBox directory. If %HOME% is not set, it will use
   the <boot_drive>:\.VirtualBox directory. In either case, you may
   overwrite the location of this directory using the VBOX_USER_HOME
   environment variable.
This would indicate that I can move the user home location. It seems to partly do it.

It also seems that if I store the code in a directory:  W:\APPS\VBOX-506 it still wants to mess with W:\APPS\VirtualBox (which happened to contain the old VBox 1.6.1 until I deleted it). This is probably from the windows way of doing things, which seems to be to put the file wherever it feels like it, at the time it does it (terribly messy).

Quote
My first attempt wasn't very successful.

I can get to the first screen. I can define a new guest machine. However, when I try to start that machine (new VDI, and pointing to the real DVD drive, with a WinXP PRO CD) It complains, immediately, and says to check the log. Okay, the log says it failed to find some files, in my old VirtualBox directory (which is just left over from before, the old VBOX was not installed). I have no idea where it is getting that stuff from. I don't think it even gets far enough to think about using the DVD drive.

Well, after clearing out every trace of both the old, and new, VBox, and installing the new one in W:\APPS\VirtualBox (where the old one was), I still had the same startup problem. Having noted a previous post about problems with Virtual assist (which works fine with VBox 1.6.1), I disabled that in the configuration (it is on by default). Now, I can start the WinXP install (which I cancelled).

I need to find more time to play with this. Not a bad start, but there is a long way to go.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 12, 2016, 11:23:30 am
2Doug Bissett: I reread your last post several times, nothing understood.

Quote
I can get to the first screen. I can define a new guest machine. However, when I try to start that machine (new VDI, and pointing to the real DVD drive, with a WinXP PRO CD) It complains, immediately, and says to check the log. I can get to the first screen. I can define a new guest machine. However, when I try to start that machine (new VDI, and pointing to the real DVD drive, with a WinXP PRO CD) It complains, immediately, and says to check the log.

Would you like to be more specific?

Quote
Well, after clearing out every trace of both the old, and new, VBox, and installing the new one in W:\APPS\VirtualBox (where the old one was), I still had the same startup problem.

Which one?

Quote
Having noted a previous post about problems with Virtual assist (which works fine with VBox 1.6.1), I disabled that in the configuration (it is on by default). Now, I can start the WinXP install (which I cancelled).

Virtual assist? I don't understand. Or, my english is too bad.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Dariusz Piatkowski on November 12, 2016, 03:46:47 pm
2Martin: "sdl" is older incorrect package. Please, remove it. The correct and newer package name is "SDL".

Just a heads-up to those who need to install the SDL package...I've been unable to do so with the ANPM interface...CLI on the other hand seems to do fine...I've got a ticket out there, see => https://mantis.arcanoae.com/view.php?id=571 (https://mantis.arcanoae.com/view.php?id=571), but the progress somewhat stalled over the past couple of weeks.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Doug Bissett on November 12, 2016, 06:30:10 pm
2Doug Bissett: I reread your last post several times, nothing understood.

Sorry, it seems to be self evident to me, but I will try again.

Quote
Quote
I can get to the first screen. I can define a new guest machine. However, when I try to start that machine (new VDI, and pointing to the real DVD drive, with a WinXP PRO CD) It complains, immediately, and says to check the log. I can get to the first screen. I can define a new guest machine. However, when I try to start that machine (new VDI, and pointing to the real DVD drive, with a WinXP PRO CD) It complains, immediately, and says to check the log.

Would you like to be more specific?

I made a new machine, with a new VDI, and tried to install WinXP. When I open the guest, I get a popup that says it failed, and to check the log. The log complains that it can't find a couple of files, that don't exist (and I can see no reason why they would exist), and goes on forever with stuff that I don't understand. It doesn't even get to the initial BIOS screen of the virtual machine.

Quote
Quote
Well, after clearing out every trace of both the old, and new, VBox, and installing the new one in W:\APPS\VirtualBox (where the old one was), I still had the same startup problem.

Which one?

The one mentioned above.

Quote
Quote
Having noted a previous post about problems with Virtual assist (which works fine with VBox 1.6.1), I disabled that in the configuration (it is on by default). Now, I can start the WinXP install (which I cancelled).

Virtual assist? I don't understand. Or, my english is too bad.

Virtual Machine Assist. VT-x/AMD-V.

Quote
Just a heads-up to those who need to install the SDL package...I've been unable to do so with the ANPM interface

ANPM will do it, but you need to uninstall the sdl package (which also takes out ffmpeg and something else). If you try to install the ffmpeg package, it will put back sdl, ffmpeg and the other one. If you first install SDL, that is all that it does, then you need to install ffmpeg, which leaves SDL alone, and installs ffmpeg and the other package.

BTW, this is NOT a problem with ANPM, it is a packaging problem with RPM.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: ivan on November 12, 2016, 07:02:07 pm
Doug, I get exactly the same response on a machine that we put together just to test this.

The initial setup screens appear to work but when we try to run anything we get the attached screen grab and a rather large log file.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 12, 2016, 07:25:26 pm
2ivan: Please attach the VM log here. It is very strange, because I install WinXP without problems.

2Doug Bissett:
Quote
I made a new machine, with a new VDI, and tried to install WinXP. When I open the guest, I get a popup that says it failed, and to check the log. The log complains that it can't find a couple of files, that don't exist (and I can see no reason why they would exist), and goes on forever with stuff that I don't understand. It doesn't even get to the initial BIOS screen of the virtual machine.
What says the popup, what is in the log? You provide too little information.

Quote
Virtual Machine Assist. VT-x/AMD-V.
Ah, hardware-assisted virtualization. You should disable it, as it is not supported on OS/2 host.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: ivan on November 12, 2016, 08:27:37 pm
Attached the log from the XP install
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 12, 2016, 09:25:10 pm
2ivan: I see "AMD-V Enabled" in the log. Did you see the VM Settings->System->Acceleration->(VT-x/AMD-V,Nested paging) checkboxes checked?
If so, you must do the same I said to Doug: uncheck them.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: roberto on November 12, 2016, 11:26:18 pm
My first impressions with Vbox:
After installing it, I install win-xp, and during the installation I have problems with the keyboard,
To confirm the first installation screens of xp, having to unplug the usb-mouse and plug it in again, so that
The options will be confirmed, until with the mouse I can finish the installation.

The network works for me, the sound does not.
Firefox was good.
But if I run the OpenScad program on win-xp 32, the program crashes and I have to unplug plug the usb-mouse,
To continue.

On the other hand I have downloaded the VboxAdditions506.iso, but I will not install it, if anyone can help me to install it ?.
 I have read the readme C: \ OS2Additions \ OS2 \ readme.txt but it does not make sense what it says, or it is wrong, or I do not understand it.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Doug Bissett on November 12, 2016, 11:42:22 pm
Quote
Ah, hardware-assisted virtualization. You should disable it, as it is not supported on OS/2 host.

That is ridiculous.  VBox 1.6.1 esr works well, with Warp4, and eCS, guests (using hardware-assisted virtualization), but they are missing a few things that would be nice to have (sound, USB, shared folders that work with SAMBA - they do work with netbios over TCP/IP). Why doesn't it work now?

Without hardware-assisted virtualization, I would say that the new VBox is about 10% useful, and the performance is terrible.

Quote
What says the popup, what is in the log? You provide too little information.

Ivan seems to have found the time to do that (yes, it is the same problem). If hardware-assisted virtualization is not supported, the options should be disabled by default, and the README should say that. We aren't mind readers.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 12, 2016, 11:53:11 pm
My first impressions with Vbox:
After installing it, I install win-xp, and during the installation I have problems with the keyboard,
To confirm the first installation screens of xp, having to unplug the usb-mouse and plug it in again, so that
The options will be confirmed, until with the mouse I can finish the installation.
What are problems with keyboard and why are you need to unplug USB mouse?

Quote
The network works for me, the sound does not.
Sound is not implemented, since the older VBox version.

Quote
Firefox was good.
But if I run the OpenScad program on win-xp 32, the program crashes and I have to unplug plug the usb-mouse,
To continue.

Does it crash on windoze VBox version? Didn't understood about the USB mouse.

Quote
On the other hand I have downloaded the VboxAdditions506.iso, but I will not install it, if anyone can help me to install it ?.
 I have read the readme C: \ OS2Additions \ OS2 \ readme.txt but it does not make sense what it says, or it is wrong, or I do not understand it.

What is the problem with additions? Why it does not make sense what readme says? What is the problem? You don't understand english or never used OS/2? And where are you trying to install OS/2 additions? If you install WinXP, you'll need the windows additions.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 12, 2016, 11:57:54 pm
2Doug Bissett: You are wrong. OS/2 version of VBox 1.6.x never supported VT-x/AMD-V. (because of missing features in OS/2 kernel). It only worked on other platforms. And, Readme mentions that VMX is not supported, so you must know if you have read readme.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Dariusz Piatkowski on November 13, 2016, 03:40:08 am
Hi Doug!


Quote
Just a heads-up to those who need to install the SDL package...I've been unable to do so with the ANPM interface

ANPM will do it, but you need to uninstall the sdl package (which also takes out ffmpeg and something else). If you try to install the ffmpeg package, it will put back sdl, ffmpeg and the other one. If you first install SDL, that is all that it does, then you need to install ffmpeg, which leaves SDL alone, and installs ffmpeg and the other package.

BTW, this is NOT a problem with ANPM, it is a packaging problem with RPM.

So this is what I suppose makes it a tough "nut" to crack in my case, I do not have sdl nor ffmpeg installed...and attempting to install SDL or sdl for that matter fail. Anyways, since CLI install works (as we proved out in my ticket on this) there is something else at play..may be RPM package...not sure.

It could also be the case that the non-YUM/RPM SDL install (the previous releases, last of which in my machine came from the SDL-1.2.15-20160209.zip file) is somehow causing ANPM/YUM/RPM a problem.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Martin Iturbide on November 13, 2016, 01:15:54 pm
Hi Roberto

On the other hand I have downloaded the VboxAdditions506.iso, but I will not install it, if anyone can help me to install it ?.
 I have read the readme C: \ OS2Additions \ OS2 \ readme.txt but it does not make sense what it says, or it is wrong, or I do not understand it.

Run the WinXP guest and mount the ISO as a CD drive.
For the WinXP Addons you need to install "VBoxWindowsAdditions.exe" from the VboxAdditions506.iso inside the Window XP Guest.

Regards
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Martin Iturbide on November 13, 2016, 02:08:32 pm
Hi.

Ubuntu 16.10 desktop 32bits ISO install boot is giving me this error.

Regards
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: roberto on November 13, 2016, 05:19:43 pm
Run the WinXP guest and mount the ISO as a CD drive.
For the WinXP Addons you need to install "VBoxWindowsAdditions.exe" from the VboxAdditions506.iso inside the Window XP Guest.
Thanks, Martin. This help me very much, for install additions.
The ironic thing of this, is that after installing the additions, the resolution of the screen had it in 1024x768 in vm-win-xp, then with additions, the screen resolution is 800x600.
The advantage is that I can access the disk drives, but in my case I almost prefer to lose the disk drives, having a shared NAS drive.
Saludos
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 13, 2016, 05:26:14 pm
2Martin: Try to enable PAE/NX in VBox settings. BTW, I tried Ubuntu 15.10, and it worked fine. Only 1200 MB of RAM was too little for it, so it was that hell slow. But it is only with default "Unity" GUI. With LXDE it is almost acceptable. For LXDE, it is better to use Xubuntu, not plain Ubuntu. And, Knoppix LiveCD was quite fast.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 13, 2016, 05:29:17 pm
2roberto: just change the screen resolution in screen properties. I have 1440x900 in guest OS just fine. Disk drives? Do you mean the shared folders? Shared folders should work in guests. NAS should work too, either with ftp or SMB shares.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: roberto on November 13, 2016, 05:50:33 pm
What are problems with keyboard and why are you need to unplug USB mouse?
At the beginning of the installation, the system asks me if I want to install press enter, exit = F3, etc ... The mouse stays fixed at a point. I pulse intro, and everything is blocked. I unplug the usb-mouse, plug it in, and the program continues with the last keyboard instruction that was intro.
Quote
Quote
But if I run the OpenScad program on win-xp 32, the program crashes and I have to unplug plug the usb-mouse,
To continue.
Does it crash on windoze VBox version? Didn't understood about the USB mouse.
This problem is resolved as follows.
In config.sys I have this:
SET VBOX_USER_HOME = Y: \ VBOXBETA
And change in Configuration - General - Advanced - Instant Folder to this folder Y: \ VBOXBETA

 
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 13, 2016, 06:12:19 pm
This does not make clear, what it does with USB mouse. (I have USB mouse and all works fine) What do you mean by "intro"? Are you installing WinXP or what? As I remember, WinXP does nothing with mouse, it is keyboard-driven. Does this OpenScad trap with Windows host? What does VBOX_USER_HOME with USB mouse? Nothing understood.

PS: Probably, you have problems with USB mouse on your host system. But this does nothing to do with VBox. I have USB mouse not moving on boot on my bootable OS/2 flash, and it works when I replug it. This is amouse problem with my mouse. Maybe, with yours, too. But this does nothing to do with VBox.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: roberto on November 13, 2016, 07:29:07 pm
This does not make clear, what it does with USB mouse. (I have USB mouse and all works fine)
The mouse work fine in my laptoop too.
Quote
What do you mean by "intro"? Are you installing WinXP or what? As I remember, WinXP does nothing with mouse, it is keyboard-driven.
Yes, I am install a win-xp and in the first, only is need the keyboard, but for any reason the keyboard is block, only unblock when unplug the mouse.
Quote
Does this OpenScad trap with Windows host? What does VBOX_USER_HOME with USB mouse? Nothing understood.
???

I finaly resize the window to 1272x722, the trick is disassemble additions, resize the framework of vm to maximum size, and restore.
All is ok now, you can see
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 13, 2016, 08:26:10 pm
2roberto: Very strange.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Doug Bissett on November 13, 2016, 09:19:50 pm
2Doug Bissett: You are wrong. OS/2 version of VBox 1.6.x never supported VT-x/AMD-V. (because of missing features in OS/2 kernel). It only worked on other platforms. And, Readme mentions that VMX is not supported, so you must know if you have read readme.

Hmmm. There isn't much of a README, but it seems that you are right. My Warp4 guest has Virtual Machine Assist enabled, and it does boot, at least up to the boot logo, then it seems to hang.

My WinXP guest also has that enabled, and it seems to work fine (don't know if it actually uses that stuff).

More work to do, when I find the time...

Quote
It could also be the case that the non-YUM/RPM SDL install (the previous releases, last of which in my machine came from the SDL-1.2.15-20160209.zip file) is somehow causing ANPM/YUM/RPM a problem.

If you have installed ANPM (YUM) managed packages in any other way, at any time in the past, you really should install them using ANPM (you may need to ignore a warning message that they are already installed, but be sure to reboot if that happens), and eliminate whatever was installed previously. If you don't do that, you can have problems. Whether that is what caused your current problem, or not, I can't say. I do know that RPM packages can be, and have been, built incorrectly, and that causes problems for ANPM (and YUM from the command line). In this case, it appears that the ffmpeg package (and possibly others) are calling for sdl, which happens to exist, for some reason, so it gets installed. Later, SDL was released, but it is not recognized as being an update to sdl, so it doesn't get updated.

As I have said before, RPM/YUM is a terrible way to do things, but if you want to use modern software, you need to use it. ANPM is simply a front end processor that runs YUM for you, but it can't detect, or correct, every problem that bad packages create.

It seems that once you get the sdl package uninstalled, and the SDL package installed, you should have no more problems with that (until they screw it up again).
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Andreas Schnellbacher on November 13, 2016, 09:57:49 pm
As I have said before, RPM/YUM is a terrible way to do things,
If you want use ported software, you have to install the required DLLs. In most cases that leads to a subset of a POSIX system. The installation system to reach that really doesn't matter, because the subsystem is huge. WarpIN packages can't help here, if you mean that.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Doug Bissett on November 14, 2016, 07:03:25 am
Quote
If you want use ported software, you have to install the required DLLs. In most cases that leads to a subset of a POSIX system. The installation system to reach that really doesn't matter, because the subsystem is huge.

I mean that most Linux distros have abandoned RPM/YUM in favor of something better. I agree that the average user needs a LOT of help to get all of that stuff installed properly. Unfortunately, RPM/YUM, even with ANPM, does not do it properly. There is nothing to clean up the mess (stuff that was installed in other ways) that is left behind, and that is causing trouble. It is further complicated by users who attempt to outsmart the RPM/YUM system, and end up with an even worse mess.

The good news is, that there is a project under way to do the cleanup, but that is about all that I know about it.

Quote
WarpIN packages can't help here, if you mean that.

WarpIn, in it's current form, is almost able to do the job. The biggest problem is trying to cross reference what gets installed in all of the different ways that are available, but automatic download is a nice feature. I think it would have been much easier to fix Warpin, than to port, and fix, RPM/YUM. However, I can see where developers can take a bunch of porting shortcuts when using the POSIX setup that RPM/YUM creates. That probably means that it is quicker, and easier, to get new software to the user. I still think it is far from the best way to do it though.

FWIW, WarpIn also has a lot of incorrectly, and badly, packaged packages, which also causes problems, but that could have been fixed too (with a lot of work).
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Andi B. on November 14, 2016, 09:24:05 am
...NAT just works, as previously. But TAPOS2 is broken -- needs to be repaired. ...
Is TAPOS2 part of VBOX? Who can fix it?
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: ivan on November 14, 2016, 02:42:52 pm
Does anyone know how to get rid of the 'mouse pointer integration' notice bar that is at the top of the guest program window?  clicking on any of the icons on the right does nothing (the X and /) and if I try to click on a program icon under it it just fill up more screen space.

Other than that and a slightly less jumping mouse in win7 it appears to be working.

I have had a couple of OS/2 crashes with problems in kernel sockets.

Is vbox supposed to support more than one processor core?  The test machine we built has a 2 core processor but I get an error if I try and use more that one core (most of our machines have 4 core processors as do our clients).
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Herwig Bauernfeind on November 14, 2016, 04:22:50 pm
Revised ReadMe-OS2.txt
VirtualBox for OS/2 OSE Edition BETA
====================================

Version 5.0.6_OSE r141

14.11.2016

This is a build of VirtualBox 5.0.6_OSE_r141 Edition for OS/2.

bww bitwise works GmbH. undertook the effort to provide an updated
version of VirtualBox for OS/2. Please note, that this version is not
supported by Oracle Corporation.

DO NOT CONTACT ORACLE Corp. REGARDING THE OS/2 VERSION OF VIRTUALBOX
NO MATTER WHAT YOUR QUESTION IS ABOUT! THANK YOU FOR UNDERSTANDING.

How to "Install" and Run
------------------------

1. Run the following lines in order to install all required rpm/yum packages

   yum install libc libgcc1 libcx libstdc++6 libstdc++
   yum install libsupc++6 libsupc++ libgcc-fwd
   yum install gettext libxml2 libxslt openssl libcurl zlib
   yum install libidl libvncserver libaio SDL glib2
   yum install libqt4 pthread libvpx libpng libjpeg
   yum install urpo yum install expat curl mmap

2. Unpack this archive somewhere.

3. Make sure you have a dot (.) in your LIBPATH statement in CONFIG.SYS.

4. Put the following line at the beginning of your CONFIG.SYS
   and reboot:

     DEVICE=<somewhere>\VBoxDrv.sys

5. Go to <somewhere> and run VirtualBox.exe (Qt GUI frontend).

6. Note that by default VirtualBox stores all user data in the
   %HOME%\.VirtualBox directory. If %HOME% is not set, it will use
   the <boot_drive>:\.VirtualBox directory. In either case, you may
   overwrite the location of this directory using the VBOX_USER_HOME
   environment variable.

7. For best performance, it is recommended to install the VirtualBox
   Guest Additions to the guest OS. The archive containing the ISO
   image with Guest Additions for supported guest OSes (Windows,
   Linux, OS/2) is named

     VBoxGuestAdditions_5.0.6.iso

   where 5.0.6 is the version number (it's best if it matches the version
   number of this VirtualBox package).
   
   In case the ISO is missing from the archive it can be downloaded from
   http://download.virtualbox.org/virtualbox/5.0.6/
   

   Download this ZIP from the same location you took this archive from
   and unpack the contents to the directory containing VirtualBox.exe.
   After that, you can mount the Additions ISO in the Qt GUI by selecting
   Devices -> Install Guest Additions... from the menu.


Documentation and Support
-------------------------

Please visit http://www.virtualbox.org where you can find a lot of useful
information about VirtualBox. There is a Community section where you can
try to request some help from other OS/2 users of VirtualBox.

You can download the User Manual for the latest official release of
VirtualBox using this URL:

  http://www.virtualbox.org/download/UserManual.pdf


OS/2 Specific Features
----------------------

This section describes the features that are specific to the OS/2 version
of VirtualBox and may be absent in versions for other platforms.

1. System key combinations such as Alt+Tab, Ctrl+Esc are currently always
   grabbed by the host and never reach the guest even when the keyboard
   is captured. In order to send these combinations to the guest OS, use
   the following shortcuts (where Host is the host key defined in the
   global settings dialog):

   Host+` (Tilde/Backquote)  =>  Ctrl+Esc
   Host+1                    =>  Alt+Tab
   Host+2                    =>  Alt+Shift+Tab

2. If you use two or more keyboard layouts on the OS/2 host (e.g. English
   and Russian), make sure that the keyboard is switched to the English
   layer when you work in the VirtualBox VM console window. Otherwise, some
   shortcuts that involve the Host key (in particluar, all Host+<latin_letter>
   shortcuts like Host+Q) may not work. Please note that the guest keyboard
   layout has nothing to do with the host layout so you will still be able to
   switch layouts in the guest using its own means.

3. Make sure you do not do 'set LIBPATHSTRICT=T' in the environment you start
   VirtualBox from: it will make the VirtualBox keyboard hook screw up your
   host desktop (a workaround is to be found).
   
4. AMD-V/VTx is not supported on OS/2 host (and never was). Hardware-assisted
   virtualization is not supported, because some features are missing from
   OS/2 kernel.

5. The PAE/NX setting which is required by certain Linux distributions in
   order to work, is available and workable.
   
6. Best experience with RAM hungry guests such as Windows currently can be
   achieved by using the unofficial OS/4 Kernel and setting VALIMIT to 3072.



Current Issues / TODOs
----------------------

* FE/Qt (Qt GUI frontend):

  - Seamless mode (no top-level window transparency on OS/2).
  - Keyboard driver to intercept system key combinations
    (Alt+Tab etc.)

* Devices:

  - Audio.
  - Host interface networking.
  - Internal networking.
  - USB proxying.

* Misc:

  - Shared clipboard.
  - Installer.
  - Very slow Resume after Pause in real mode guest applications.

Title: Re: VirtualBox 5.0.6 First Impressions
Post by: R.M. Klippstein on November 14, 2016, 05:36:51 pm
Hey ivan, For now only one processor is supported, as for the problem with the mouse pointer intergration notice try, click on the x to close it (which seemingly does nothing) then click on the mini icon in the upper right corner of the screen that changes screen from full screen to windowed (or vice versa) and that should get rid of it.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 14, 2016, 06:22:09 pm
2AndiB:

Quote
Is TAPOS2 part of VBOX? Who can fix it?

It is not the part of VBox. It was just allowed to use with VBox by GenMac author. TapOS2 support in VBox is now broken, not TapOS2 itself. It was removed from official VBox sources, for some reason, since some version, but I tried to return it back, with no success, yet. I did something wrong. Need to repair in next VBox builds.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 14, 2016, 06:28:14 pm
Does anyone know how to get rid of the 'mouse pointer integration' notice bar that is at the top of the guest program window?  clicking on any of the icons on the right does nothing (the X and /) and if I try to click on a program icon under it it just fill up more screen space.

You can click on a "Do not show this message again" button at right of the message itself.

Quote
Is vbox supposed to support more than one processor core?  The test machine we built has a 2 core processor but I get an error if I try and use more that one core (most of our machines have 4 core processors as do our clients).

No, AFAIK, for using more than one processor, you need the hardware virtualization enabled, which is not supported on OS/2 host atm.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: ivan on November 14, 2016, 08:19:11 pm
Valery, I tried that and neither of the buttons on the right of the message do anything even after a restart of the VM.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 15, 2016, 12:04:57 am
2ivan: I don't know -- maybe, you pressed another button -- there are two buttons at the right side of each notice.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: ivan on November 15, 2016, 04:44:01 pm
Agreed, there are two buttons.  One is the X, which I assume is supposed to close the bar, and the other is the / over something that looks like a folder which you say represents the 'do not show this again'.

The problem is that neither one does anything.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: roberto on November 15, 2016, 08:25:29 pm
Overall I really like this beta. I am using OS / 2 host and xp as guest.
Important problem: During the optimization tests, I had to kill the virtualbox, and the memory I had in use at the time in the Vbox, it has been locked in OS2, preventing me from restarting xp, until restarting OS / 2 .
Other small problems:
The mouse notepad.exe gets almost transparent and in other similar windows, and changing the icon does not solve the problem.
During the installation of Java 8 ..., the printer, and some other program I have seen small graphical errors, that have not affected for its operation.
If I access a JFS drive it works fine. But if I access a FAT32 drive, the performance is very very slow, but it works !!!
In my case the best balance of memory and screen, have been 768mb of 4gb and 74mb of 128mb screen.
Saludos
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: R.M. Klippstein on November 15, 2016, 08:57:58 pm
ivan, you are right, neither button does anything (so it seems!) but after doing that,  go up to the full screen/windowed screen icon and change the screen from what ever state you were using in and then change it back and that will clear the bar, at least it does so here.

klipp
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 15, 2016, 09:32:41 pm
2ivan, rklipp: yes, I see the notice not disappearing from the screen, but after some clicking on "do not show this again" the message does not any more appear on further boots. This is working for me, at least. Maybe, you need some more attempts.

2roberto: So, what's the result? VBox hanged? -- Try to kill it with watchcat. Did not understood about mouse notepad and changing the icon.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: roberto on November 15, 2016, 11:43:19 pm
2roberto: So, what's the result? VBox hanged?
No hang, I start with a ram aprox. 1400mb, and display a title box Vbox Guru... but I lost the graphic display, and the control over the program, and decide to kill it.
Quote
-- Try to kill it with watchcat.
I do not know this program, but go to test it.
Quote
Did not understood about mouse notepad and changing the icon.
The problem is that in a  white whidow, the mouse is white too, and I lost it to my eyes. In this capture the mouse is black (similar a I leter over the second L in hello), but repeat I see white. See photo.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: nyao on November 16, 2016, 01:37:26 am
Hi.
I had try to install or run the OS, the system crashes.
eComStation 2.1(non SMP,),Panorama v1.06(1600x900) with i3 Onboard graphic.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Greggory Shaw on November 16, 2016, 07:51:06 am
Hi.
I had try to install or run the OS, the system crashes.
eComStation 2.1(non SMP,),Panorama v1.06(1600x900) with i3 Onboard graphic.

Are you trying to install eCom 2.1 as a guest ?

http://www.os2world.com/forum/index.php/topic,1189.msg11222.html#msg11222
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: nyao on November 16, 2016, 10:09:52 am
Greggory Shaw、Thank you.
I did not know that eComStation is useless.
However, the system crashed also in Windows XP.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Andi B. on November 16, 2016, 11:53:27 am
I've tried running my WinXP guest .vdis which I used with the older vbox1.6 for years on a new box with the new vbox5.0x beta. But on that machine I see a weird window refreshing problem. Very often a window in the XP guest is not refreshed (repainted) when opened or some content changes. F.i. starting an application very often do not draw the window correctly. Sometimes only parts are drawn (menus or some content of a subwindow).

When I move over a host window over the guest (f.i. 4os2 window) then the guest graphic is correctly repainted. Is this a know issue? Maybe in conjunction with Panorama? On this test machine I use Panorama while on my regular system which works with vbox1.6 correctly I'm using SNAP.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: ivan on November 16, 2016, 02:10:42 pm
nayo, why would you want to run a copy of the host operating system as a virtual machine guest on that host? 

A virtual machine will seldom run as well as the host mainly because the host is running on real hardware and the guest has to run on virtualised hardware.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: ivan on November 16, 2016, 03:21:47 pm
Andi, I just copied our XP.vdi over to the test machine we are using for testing this version of vbox and it runs without any problems.  The test machine uses SNAP for video.

That leads to the conclusion that the Panorama video drivers may be the problem.  We can't test that as we don't have the Panorama drivers to play with.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: ak120 on November 16, 2016, 06:19:20 pm
Andi, I just copied our XP.vdi over to the test machine we are using for testing this version of vbox and it runs without any problems.

This procedure only works mostly for hosts with the same cpu. By changing from Intel to AMD and vice versa it can cause trouble which leads to non working guest images.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: roberto on November 16, 2016, 08:43:28 pm
Quote
-- Try to kill it with watchcat.
I do not know this program, but go to test it.

This watchcat program is very interesting. But after trying it, I had to remove it, as it is incompatible with my external USB drive in OS / 2.
And with the Vbox, it slows me down a lot, to the point of not working well.
It is uninstalled.
Saludos
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 17, 2016, 12:29:00 am
2Andi B: Yes, it is a known problem. There could be the guest window not refreshed if the selector window present. This is some GUI lags. For now, to prevent this, you could try starting the VM without a selector window:

Quote
VirtualBox.exe --startvm <VM name>

Panorama is irrelevant here. I have this with SNAP too.

Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 17, 2016, 12:35:12 am
2roberto: Why do you think it is incompatible with an USB drive? I have no problems with this. You are, obviously, wrong.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 17, 2016, 12:44:12 am
2Andreas Kohl: It depends on the OS in the VM. Some OS'es setup, like OS/2, don't depend on the host processor, but some of them do (WinXP installs a HAL and kernel based on current CPU). Knoppix (a Debian Linux live CD) is not independent of the current CPU too. I copied VM's with OS/2 and ReactOS between OS/2/Linux/WinXP without any problems.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: roberto on November 18, 2016, 08:22:36 pm
2roberto: Why do you think it is incompatible with an USB drive? I have no problems with this. You are, obviously, wrong.
With this line in the config.sys plus the program Watchcat
DEVICE = C: \ OS2 \ BOOT \ USBMOUSE.SYS / DEVICE: 1
With Lars 10.210 USB Drivers
After starting the pc, the usb with an external memory unit with fat32, works well. But after running the VirtualBox with xp, and closing it. The usb no longer works, even if you run the lvm / rediscoverprm.

With this one in the config.sys plus the program Watcat
DEVICE = C: \ OS2 \ BOOT \ USBMOUSE.SYS
With Lars 10.210 USB Drivers
Sometimes everything is fine, sometimes it fails, but not always.

I have not tested it with the usb11.14
Saludos
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: Valery Sedletski on November 19, 2016, 02:06:03 am
2roberto: And? What this has to do with Watchcat? And what this has to do with VBox?
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: roberto on November 19, 2016, 02:47:41 pm
2roberto: And? What this has to do with Watchcat? And what this has to do with VBox?
It seems that nothing, after installing the new Xworplace, and installing the Watchcat again, after Xwokplace I do not have the problem.
Title: Re: VirtualBox 5.0.6 First Impressions
Post by: roberto on November 20, 2016, 10:57:12 pm
Sorry for the misconduct you may have caused with my usb notes, but I discovered a virus in the fat32