Anyway, there are some serious problems I face within it. If you have the features of SELinux enabled, just turn it off since it will produce an error messages said something like "/opt/VirtualBox-1.3.8/VirtualBox: error while loading shared libraries: /opt/VirtualBox-1.3.8/VBoxVMM.so: cannot restore segment prot after reloc: Permission denied". Another solution to solve the problem is trying to change the information security context file with the command below:
$>chcon -R -t texrel_shlib_t /opt/VirtualBox-1.3.8/*.soOther errors you might face, if the VirtualBox installation stage are getting corrupt, it will raise a "VirtualBox - Error" window containing the text "Failed to create new session" & "Callee RC: 0x80040154". This window appears in the final step while creating, modifying or running the virtual environment OS. To solve this, try to make a fresh install the VirtualBox setup package again.
From my couple days experience with Windows 98 running on VirtualBox, the USB storage devices are fully working without driver installed. As we know that it is so differ if we natively running Windows 98. It proved that the VirtualBox HAL (Hardware Abstraction Layer) specifically to the USB host bridging are successfully implemented. Unfortunately, when I tried to connects the Smart Link 56K internal modem, it giving me a great headache since there is no single one COM port detected. I don’t have any idea why it could be happened, while the Windows 98 native said it is OK.
By the chance, I would like to give a try with installing Windows 2000 on a same machine. First of all, I prepared the virtual disk with size of 1GB. The installation started with Windows 2000 boot setup CD from ASUS external DVD-RW drive.
Anyway, this virtual disk was formatted in NTFS format type.
The installations ~ somehow ~ are quite faster than Windows 98, also the boot sequences until the desktop shows up. Nothing serious problems happened anyway.
Got curious about the unavailable of COM port in Windows 98, I also tried on this fresh Windows 2000. Guess what? The detection has failed too! There are none of existing com port on the computer! What is going on with it?
I wondered why it could be happened. Is there any VirtualBox configuration files I missed? Or something is not done configured properly on the hardware side? One for sure, I couldn’t test the internet connection from modem yet. After having a some times searching over the VirtualBox website forum, finally I found a reason why it happened. According to the information on this link, VirtualBox is still doesn’t have ability to support the COM port yet! WTF! In this worsted scenario, the networking bridging become my last solution. It means that I have to provide a real virtual network connection shared from the proxy or gateway from other machine. Got to get this thing down or got my ass sited for a long long times. Fiuh!
Labels: My Works
PS: If you've benefit from this blog,
you can support it by making a small contribution.