Author Topic: VirtualBox 5.0.6 First Impressions  (Read 47213 times)

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4711
  • Karma: +41/-1
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Re: VirtualBox 5.0.6 First Impressions
« Reply #30 on: November 13, 2016, 02:08:32 pm »
Hi.

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

Regards
Martin Iturbide
OS2World NewsMaster
... just share the dream.

roberto

  • Hero Member
  • *****
  • Posts: 810
  • Karma: +3/-6
    • View Profile
Re: VirtualBox 5.0.6 First Impressions
« Reply #31 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

Valery Sedletski

  • Sr. Member
  • ****
  • Posts: 368
  • Karma: +2/-0
    • View Profile
Re: VirtualBox 5.0.6 First Impressions
« Reply #32 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.

Valery Sedletski

  • Sr. Member
  • ****
  • Posts: 368
  • Karma: +2/-0
    • View Profile
Re: VirtualBox 5.0.6 First Impressions
« Reply #33 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.
« Last Edit: November 13, 2016, 05:33:49 pm by Valery Sedletski »

roberto

  • Hero Member
  • *****
  • Posts: 810
  • Karma: +3/-6
    • View Profile
Re: VirtualBox 5.0.6 First Impressions
« Reply #34 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

 

Valery Sedletski

  • Sr. Member
  • ****
  • Posts: 368
  • Karma: +2/-0
    • View Profile
Re: VirtualBox 5.0.6 First Impressions
« Reply #35 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.
« Last Edit: November 13, 2016, 06:17:55 pm by Valery Sedletski »

roberto

  • Hero Member
  • *****
  • Posts: 810
  • Karma: +3/-6
    • View Profile
Re: VirtualBox 5.0.6 First Impressions
« Reply #36 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

Valery Sedletski

  • Sr. Member
  • ****
  • Posts: 368
  • Karma: +2/-0
    • View Profile
Re: VirtualBox 5.0.6 First Impressions
« Reply #37 on: November 13, 2016, 08:26:10 pm »
2roberto: Very strange.

Doug Bissett

  • Hero Member
  • *****
  • Posts: 1593
  • Karma: +4/-2
    • View Profile
Re: VirtualBox 5.0.6 First Impressions
« Reply #38 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).

Andreas Schnellbacher

  • Hero Member
  • *****
  • Posts: 827
  • Karma: +14/-0
    • View Profile
Re: VirtualBox 5.0.6 First Impressions
« Reply #39 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.

Doug Bissett

  • Hero Member
  • *****
  • Posts: 1593
  • Karma: +4/-2
    • View Profile
Re: VirtualBox 5.0.6 First Impressions
« Reply #40 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).

Andi B.

  • Hero Member
  • *****
  • Posts: 811
  • Karma: +11/-2
    • View Profile
Re: VirtualBox 5.0.6 First Impressions
« Reply #41 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?

ivan

  • Hero Member
  • *****
  • Posts: 1557
  • Karma: +17/-0
    • View Profile
Re: VirtualBox 5.0.6 First Impressions
« Reply #42 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).

Herwig Bauernfeind

  • Newbie
  • *
  • Posts: 39
  • Karma: +2/-0
    • View Profile
Re: VirtualBox 5.0.6 First Impressions
« Reply #43 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.


R.M. Klippstein

  • Sr. Member
  • ****
  • Posts: 313
  • Karma: +3/-0
    • View Profile
Re: VirtualBox 5.0.6 First Impressions
« Reply #44 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.