Forums

Resolved
2 votes
Because ClearOS has such a small footprint it actually makes quite a good VM server for various guest OS's.

There are threads on VMWare in the forum, and how to get that setup - so i'd thought i'd have a go with VirtualBox which also has a headerless function which can be viewed using standard Windows Remote Desktop. This makes it great for running remote OS's

The latest version of VirtualBox is 3.1.2 however this version made some config changes from 3.0.x to the way in which storage controllers and resources are called up (long story short to enable more than one DVD drive etc)...I had more success with the tried and tested 3.0.12 method so this Howto is based around that version. Hopefully in future we'll be able to update this with the newer version. Be careful when googling for info as the syntax changed between versions.

INSTALLATION
First up you will need the devel tools to enable the kernel modules to be compiled during install. If you are running the PAE kernel, replace with kernel-PAE-devel
yum groupinstall "Development Tools"
yum install kernel-devel


Download the RPM for RHEL5 i386
cd /var/tmp
wget http://download.virtualbox.org/virtualbox/3.0.12/VirtualBox-3.0.12_54655_rhel5-1.i386.rpm
yum localinstall VirtualBox-3.0.12_54655_rhel5-1.i386.rpm


Installation will create a group called vboxusers, we need to add a user to this group, or create a seperate vbox specific user. I went for the latter as I wanted to keep it separate from my other accounts. User is named 'vbox' for example, we also then add the user to the vboxusers group

/usr/sbin/useradd -r -m vbox
/usr/sbin/usermod -a -G vboxusers vbox


VirtualBox is not LDAP aware so these need to be system user / accounts, hence the -r flag for useradd. It should create a user with an SID < 500 so that it is not removed by the system at a later date.

This should confirm that you user has been created and associated with the group
cat /etc/passwd | grep vbox
cat /etc/group | grep vbox

CREATE AND CONFIGURE A VM
Now on to the fun bit...! Creating a VM ( I won't touch on importing your own *.vdi or *.ovf appliances here, have a read of the VirtualBox manual over here for clues http://www.virtualbox.org/manual/UserManual.html

First switch to the new user, then we will start to create the VM. Note using the GUI is so much easier but we don't want the overheads of the full X system so stick with it :) it will start to make some sense

Again NOTE sysntax has changed for the new 3.1.2 version, this applies to 3.0.12

Outline steps are:- switch to vbox user (all configuration is by default stored in /home/vbox/.VirtualBox/ subfolders
Create the VM name and register it, remember this or write it down, I called mine Windows XP

su vbox
VBoxManage createvm --name "WindowsXP" --ostype "WindowsXP" --register

This should return without error. The VM will be created under /home/vbox/.VirtualBox/Machines/...you can of course symlink this to another directory on the system if you wish

Now to setup some basic parameters for the VM. We are using 512MB, boot DVD first, use basic bridged connection with the LAN interface to give it internet access. You can also specifcy --nic2 etc...or --nic1 nat. See VBoxManage man page for full config details
VBoxManage modifyvm "WindowsXP" --memory "512MB" --acpi on --boot1 dvd --nic1 bridged --bridgeadapter1 eth0


Now to create the VM HD, set to 10GB, and stored under /home/vbox/.VirtualBox/HardDisks/. We then assign this HD to our VM as the primary HD device hda
VBoxManage createhd --filename "WinXP.vdi" --size 10000 --remember
VBoxManage modifyvm "WindowsXP" --hda "WinXP.vdi"


Next step to register our installation ISO with VirtualBox (this is akin to the media manager if you've used the GUI before). We then register this as the DVD drive associated with our VM. The ISO can live anywhere on your system as long as vbox can read it.
VBoxManage openmedium dvd /full/path/to/iso.iso
VBoxManage modifyvm "WindowsXP" --dvd /full/path/to/iso.iso


START YOUR VM
Thats it! a basic config that should now get a VM install running. To start our VM headerless we now run the following, and then connect remotely using Windows Remote Desktop to ClearOS (port 3389 is used by default). Note the & at the end, this will force it to run in the background, so you should ensure you shutdown the VM correctly or use VBoxManage to control / save the states on exit)
VBoxHeadless --startvm "WindowsXP" &


To detach the DVD iso (i.e. eject it) use the following
VBoxManage modifyvm "WindowsXP" --dvd none

You may also try - if the VM is running
VBoxManage controlvm "WindowsXP" dvdattach none


GUEST ADDITIONS
Now I found that the display and mouse did not correlate very well until I install the guest additions. So....register and attach the guest additons ISO, then boot your VM and run the installer from within the OS
VBoxManage openmedium dvd /usr/share/virtualbox/VBoxGuestAdditions.iso
VBoxManage modifyvm "WindowsXP" --dvd /usr/share/virtualbox/VBoxGuestAdditions.iso


Enjoy! :)
For more configuration options refer to http://www.virtualbox.org/manual/UserManual.html#vboxmanage-modifyvm Particularly for increasing the video card memory size, NIC options etc.

TIPS - To be completed....
Want to see a VM config? use VBoxManage showvminfo "WindowsXP"
Want to see HD config? use VBoxManage showhdinfo harddiskname.vdi
Want to change Video RAM allocated to VM? use VBoxManage modifyvm "WindowsXP" --vram 128MB
Want to enable USB and USB2.0? use VBoxManage modifyvm "WindowsXP" --usb on --usbehci on
Want to shutdown a VM? use VBoxManage controlvm "WindowsXP" acpipowerbutton (for instant off, use poweroff)
Need to press CTRL-ALT-DEL to login over RDP? it's locked solely to the local machine, so use CTRL-ALT-END instead ;)
Want to see other ostypes? use VBoxManage list ostypes
Wednesday, January 06 2010, 12:47 AM
Like
1
Share this post:
Responses (157)
  • Accepted Answer

    Robert
    Robert
    Offline
    Tuesday, May 09 2017, 08:16 PM - #Permalink
    Resolved
    0 votes
    Hi Wayland,

    the graphical user interface is not needed, just if you need 3D acceleration you need a graphical desktop. You also do not need to create the VMs on a desktop PC, everything can be done by command line - creating - modifying - starting - stopping .... .

    Best wishes,

    Robert
    The reply is currently minimized Show
  • Accepted Answer

    Monday, May 08 2017, 09:03 PM - #Permalink
    Resolved
    0 votes
    ClearOS 7 VirtualBox 5 implementation.

    I've got an old XP computer which we need to keep running. I have it virtualized using the Microsoft tool DISK2VHD.EXE in the physical PC. It makes sure the drivers are there in the VHD for VirtualBox to use. Now running in VirtualBox on Linux Mint 18. I've managed to launch it headless from the command line with the -vrde on option having used VBoxManage to set the VNC password as shown in an earlier post here. Then I can VNC to it provided I connect to the virtual machine's IP not my hosts IP. Probably worth setting it to bridged networking and setting a static IP.

    It seems to me unnecessary to have a graphical user interface on the ClearOS server and that all that's required is to create your Virtual Machine somewhere else before moving it to the ClearOS server. Am I correct or are the graphical bits required in the headless VirtualBox?
    The reply is currently minimized Show
  • Accepted Answer

    Robert
    Robert
    Offline
    Sunday, March 16 2014, 04:00 PM - #Permalink
    Resolved
    0 votes
    Hi,

    Thanks to Tim for the nice How to install virtualbox headless. I just wonder what I need to install to get the 3D acceleration working? I guess:

    - 3D graphic card (Nvidia)
    - X
    - Desktop?

    It is just strange to me, that the option 3D acceleration exists for the headless version, even it does not do anything.

    Thanks for the help.

    Best

    Robert
    The reply is currently minimized Show
  • Accepted Answer

    Scumbag
    Scumbag
    Offline
    Saturday, September 21 2013, 12:25 AM - #Permalink
    Resolved
    0 votes
    I've just managed to install VirtualBox on my ClearOS 6.4 machine. The steps in the earlier howto didn't work for me and I had to incorporate info from this thread and a number of other sources.

    So here's the definitive list of steps, starting from a clean, brand new 6.4 installation :


    yum install SDL kernel-devel kernel-headers dkms
    yum install gcc
    yum-config-manager --enable clearos-core clearos-developer
    yum --enablerepo=clearos-core,clearos-developer,clearos-epel install clearos-devel


    Then :

    uname -r
    ls /usr/src/kernels


    If the output of the last 2 commands is different :

    cd /usr/src/kernels/
    ln -s <insert your kernel kernel version - in my case 2.6.32-220.23.1.el6.x86_64> `uname -r`


    Then :

    cd /etc/yum.repos.d
    yum install wget
    wget http://download.virtualbox.org/virtualbox/rpm/rhel/virtualbox.repo
    yum search VirtualBox


    The last command will list the available versions. Mine listed the following :
    VirtualBox-3.2.x86_64 : Oracle VM VirtualBox
    VirtualBox-4.0.x86_64 : Oracle VM VirtualBox
    VirtualBox-4.1.x86_64 : Oracle VM VirtualBox
    VirtualBox-4.2.x86_64 : Oracle VM VirtualBox


    yum install VirtualBox-4.2
    /etc/init.d/vboxdrv setup


    Next, download Oracle_VM_VirtualBox_Extension_Pack-4.2.18-88780.vbox-extpack from http://www.virtualbox.org/wiki/Downloads and copy it to your ClearOS machine.

    Then :

    /usr/bin/VBoxManage extpack install ./Oracle_VM_VirtualBox_Extension_Pack-4.2.18-88780.vbox-extpack


    Now you're ready to create a VM. I installed Windows 7 Home Premium 32-bit. The commands below will create a Windows 7 machine with 1.5GB of RAM and a 20GB hard drive. In my case eth1 is the LAN NIC on my server.

    Note that in the modifyvm command below, the "--nictype1 82540EM" is needed for Vista and later versions of Windows as they phased out support for VirtualBox's default network adapter type, but not for XP and earlier.


    VBoxManage createvm --name "Win7" --register
    VBoxManage modifyvm "Win7" --memory 1536 --acpi on --boot1 dvd --nic1 bridged --bridgeadapter1 eth1 --nictype1 82540EM
    VBoxManage createhd --filename Win7.vdi --size 20000
    VBoxManage storagectl "Win7" --name "IDE Controller" --add ide
    VBoxManage storageattach "Win7" --storagectl "IDE Controller" --port 0 --device 0 --type hdd --medium Win7.vdi
    VBoxManage storageattach "Win7" --storagectl "IDE Controller" --port 1 --device 0 --type dvddrive --medium <path to ISO file of windows installer>
    VBoxHeadless --startvm "Win7" &


    You should now be able to connect to the virtual machine using Windows Remote Desktop at the LAN address of your server and drive Windows through the setup process. When that's finished, shut down the VM and attach the guest additions ISO as follows. Without these, your display and mouse (at the very least) won't work well.


    VBoxManage modifyvm "Win7" --dvd none
    VBoxManage storageattach "Win7" --storagectl "IDE Controller" --port 1 --device 0 --type dvddrive --medium /usr/share/virtualbox/VBoxGuestAdditions.iso
    VBoxHeadless --startvm "Win7" &


    Now attach to the VM again, install the guest additions from the virtual DVD drive and shut down.

    Now detach the guest additions ISO :
    VBoxManage modifyvm "Win7" --dvd none


    I wanted to set my VM up as a print server. Here's the steps (run these commands while the VM is shut down) :


    VBoxManage modifyvm "Win7" --usb on
    VBoxManage modifyvm "Win7" --usbehci on
    VBoxManage list usbhost


    The last command will list the USB devices connected to the ClearOS machine. The one I wanted is a Samsung 4521 printer, which was listed with vendor ID 0x04e8 and product ID 0x3419.
    VBoxManage usbfilter add 1 --target "Win7" --name Samsung_4521 --vendorid 0x04e8 --productid 0x3419


    Now power up the VM, install the printer driver and share it. You may need to install additional drivers if you're connecting 64-bit machines to the printer.

    That's it!
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, March 06 2013, 10:51 PM - #Permalink
    Resolved
    0 votes
    yum install kernel-devel kernel-headers

    Make sure they match your running kernel 'uname -r'

    They are required to rebuild the VirtualBox hardware modules
    The reply is currently minimized Show
  • Accepted Answer

    t1ck3ts
    t1ck3ts
    Offline
    Tuesday, March 05 2013, 07:52 PM - #Permalink
    Resolved
    0 votes
    Not sure what else needs to be done, but i have gone through all the pages in this thread to try and get it working
    This is the error i am getting:

    [root@system ~]# /etc/init.d/vboxdrv setup
    Stopping VirtualBox kernel modules [ OK ]
    Uninstalling old VirtualBox DKMS kernel modules [ OK ]
    Trying to register the VirtualBox kernel modules using DKMSError! echo
    Your kernel headers for kernel 2.6.32-279.19.1.v6.i686 cannot be found at
    /lib/modules/2.6.32-279.19.1.v6.i686/build or /lib/modules/2.6.32-279.19.1.v6.i686/source.
    [FAILED]
    (Failed, trying without DKMS)
    Recompiling VirtualBox kernel modules [FAILED]
    (Look at /var/log/vbox-install.log to find out what went wrong)
    [root@system ~]#
    The reply is currently minimized Show
  • Accepted Answer

    FLOURE
    FLOURE
    Offline
    Wednesday, June 20 2012, 04:45 PM - #Permalink
    Resolved
    0 votes
    Hi,

    I did follow all the steps with no errors. but at restart I had no visible virtualbox

    I i run manually vboxmanage startvm....
    then I've VRDE server is listenning on port 3389


    When I enter the IP of my host on a windows RDC i've no answer.

    How can i access my virtualized windows ?? Or did I miss something ?

    Thanks by advance

    Seb
    The reply is currently minimized Show
  • Accepted Answer

    Makc
    Makc
    Offline
    Friday, June 08 2012, 02:05 AM - #Permalink
    Resolved
    0 votes
    Fixed by updating samba, and copying the files over again.
    The reply is currently minimized Show
  • Accepted Answer

    Makc
    Makc
    Offline
    Thursday, June 07 2012, 04:35 AM - #Permalink
    Resolved
    0 votes
    Thanks for all who helped. I Finally got my guest os installed and working great. Phew, what a process. But again, thanks

    Im running into another issue though. I created a flexshare of files I have stored on the clearos box, and after mapping my share drives in my guest os, I opened a folder and to my surprise for some reason my unicode characters (russian characters) are appearing as under scores (______ ___ .mp3) only the tracks that have either numbers or english characters show up and work great.

    For example.

    If you navigate to
    z:\myfiles\mytracks\10______.mp3 I get my song (10______.mp3)

    But if I connect through FTP. I get
    ftp://myfiles/mytracks/10песня.mp3

    Seems some Unicode option needs to be selected in clear os or something. I have already enabled "Russian" in the regional language and settings on my guest os and restarted it.

    Thanks
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, June 06 2012, 02:31 PM - #Permalink
    Resolved
    0 votes
    @Nick,
    Thanks for the comments, I will address those repo so they don't break anything else. You are 100% correct. I seem to have lost sight of "standard practices in Linux" being "so overwhelmed" with getting this project to work. Thanks for bringing me back... :)

    *************************
    Makc wrote:
    After following post, I installed virtual box, but after i started the vm, windows xp loads all drivers during its setup, and then setip gets stuck on "setup is starting windows"

    What could that be? I have tried multuple iso's

    Thx


    @Makc
    Assuming that everything is working on the host, it will be in your guest's settings. My first thought is that it might have to do with ioacpi. Try turning ioacpi off and see if it makes a difference. Here's the command, change "vmname" to your guest's name.
    VBoxManage modifyvm "vmname"  --ioacpi off


    On my first attempt, my vm (windows 7 64) would start loading windows and just reboot. After some more tweeking to the guest, another attempt said that Windows 7 could not load because it was not a 64 bit environment (even though my host hardware meets all the requirements). I also had to change the guest network adapter type (once it actually booted up) so that my guest could find a network driver. They seem to have changed quite a few things in VirtualBox as far as the guest machine parameters. You will probably need to tinker with a few of the guest machine settings to figure out what will work for yours.

    Below is the VirtualBox Forum site. Research some of the guest parameters there and try them out. Worst case, you may need to "re-create" your vm a few times. There are quite a few discussions concerning 32bit vs 64bit using: apic, ioapic, PAE/NX, etc. Most of the posts refer to "using the GIU" to change guest settings but since your's is headless, the "VBoxManage modifyvm" command is probably going to be your best friend.
    virtualbox forums

    Hopefully that gives you a starting place...
    The reply is currently minimized Show
  • Accepted Answer

    Makc
    Makc
    Offline
    Wednesday, June 06 2012, 06:27 AM - #Permalink
    Resolved
    0 votes
    After following post, I installed virtual box, but after i started the vm, windows xp loads all drivers during its setup, and then setip gets stuck on "setup is starting windows"

    What could that be? I have tried multuple iso's

    Thx
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, June 02 2012, 06:16 AM - #Permalink
    Resolved
    0 votes
    Good write up. Thanks.

    A couple of comments. "Development Tools" no longer exist in 6.2 which is why you had to do the line after. The alternative is here

    If you are enabling repos generally disabled or adding external repos it is best to leave them disabled and then selectively enable them when required. So, when you enabled clearos-epel you may be better advised to add the "--enable-repo clearos-epel" to your yum commands. You may also want to change the "enabled=1" to "enabled=0" in virtualbox-repo and only selectively enable it. Then when you do an "yum install virtualbox" you enable both the clearos-devel and virtualbox repos. it *may* get round your dkms issue.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, June 02 2012, 01:22 AM - #Permalink
    Resolved
    0 votes
    Here is my write-up, hopefully it helps out. If you can make this into a script, that would be awesome <hint hint>

    I finally got this to work with ClearOS 6.2 and VirtualBox 4.1 running Windows 7 64 bit as the guest OS. Had a few challenges (including the kernel-devel and kernel-headers). I did not install the web interface for virtualbox, I found I did not need it for my particular install. There are probably some things that can be done easier, please comment when you see them. Thank you everyone for your posts, they helped to find answers to the issues. If you try this out, please remember post your findings as well, it may help the next person...

    I will mention one big lesson I learned the hard way, DO NOT do a “yum update” before you register your ClearOS system. It trips something that AUTO-UPGRADES you to the professional version and ELIMINATES THE OPTION OF COMMUNITY VERSION. I had to reload from scratch to register it properly as a community version. The good news is, because of this lesson, I was able to verify that the steps worked for me on the second time too!

    Here are the steps. I did everything using: SSH, Firefox and rdesktop on an Ubuntu box.
    First, REGISTER YOUR SYSTEM, then get to the command line.

    The following steps will update your system using yum, add a virtualbox repository from oracle to your system and install all the other misc stuff you'll need.

    ##update the system. If you haven't registered your system, do it before doing this update if you want to run the community version (last reminder, I promise).
    yum update -y 


    We need to change directories to where the repository files are stored . We are going to download a new repository here so yum will “automagically” find it the next time you update.
    cd /etc/yum.repos.d/ 

    Install wget so you can download the file for the new repository
    yum install wget -y 

    Download the repository file from virtualbox.
    wget http://download.virtualbox.org/virtualbox/rpm/rhel/virtualbox.repo 

    Change driectories back to the root directory so nothing else gets downloaded here by accident.
    cd /root

    Now that you have a new repository, it will need to be checked and updated.
    yum update -y 

    Get some dependencies
    yum groupinstall "Development Tools" -y 
    yum install php-soap gcc dkms kernel-devel -y

    This command came from Tim in another thread but seems to help virtualbox compile correctly because it uses the v6 kernel-headers as opposed the the el6 kernel-headers in the standard repository. See the thread for details... http://www.clearfoundation.com/component/option,com_kunena/Itemid,232/catid,37/func,view/id,40819/
    yum --enablerepo=clearos-dev install kernel-devel-`uname -r` kernel-headers-`uname -r` 

    Create a vbox system user with a home directory
    /usr/sbin/useradd -r -m vbox 

    Create group and add vbox to it
    /usr/sbin/usermod -a -G vboxusers vbox 

    Install VirtualBox 4.1 using yum virtualbox.org repository
    yum install VirtualBox-4.1.x86_64 -y 


    Now, this is the part that I forgot about BOTH times. I got errors with virtualbox, as noted in the posts previous to this one. Even though the command to install dkms is listed above (and I thought that it did install), virtualbox has issues with it. To fix it, I enabled the “clearos-epel” repository using the web GUI under “System” tab, “Software Repository”. With the new repo, you;ll need another update:
    yum update -y 

    Now you will need to install dkms (again?)
    yum install dkms -y

    Recompile virtualbox drivers with the new dkms. The recompile didn't have any errors this time.
    /etc/init.d/vboxdrv setup

    Also, in 4.1, there is an expansion pack that adds functionality into the machine like RDP. You will neeed to download it from virtualbox.org and install it. Go to the website https://www.virtualbox.org/wiki/Downloads look up the extension pack and update the address below to match your version. Here is the link for the one I used:
    wget http://download.virtualbox.org/virtualbox/4.1.16/Oracle_VM_VirtualBox_Extension_Pack-4.1.16-78094.vbox-extpack

    Use vboxmanage to install it.
    VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.1.16-78094.vbox-extpack


    So now I had it set up, I needed a machine. Here goes....

    First of all, create a new system user called vbox and a group for them.
    /usr/sbin/useradd -r -m vbox
    /usr/sbin/usermod -a -G vboxusers vbox

    I needed a Windows 7 iso file to load this thing so I converted the installation CD to an iso. Put the CD into your ClearOS machine. Don't worry, it doesn't really catch on fire when the “essence of pure evil” touches your machine. It may smolder though.. Anyway, here's the command to convert the CD to an ISO:
    dd if=/dev/cdrom of=/home/vbox/windows7.iso

    Change directories to where it was created and then change the ownership to vbox to avoid “issues”
    cd /home/vbox/
    chown vbox:vbox /home/vbox/windows7.iso

    You now need to change your user to vbox instead of root, so the rest of these commands are as the user vbox.
    su vbox 

    virtualbox creates it's working directory with a space in the name. Spaces can cause you some headaches if they are not escaped. Make a new working directory and and configure virtualbox to use it as the working directory to store virtual machines.
    Mkdir /home/vbox/vms
    VBoxManage setproperty machinefolder /home/vbox/vms/

    Create and register your new virtual machine. The new machine will be stored in the directory you just created.
    VBoxManage createvm --name "Windows7" –register 

    This one modifies the new vm and creates a lot of hardware. I set it with 2 gig of ram (2048) since it's not going to be really used heavily, just occasionally for remote access for a Windows user.
    First issue I had was it would not run saying something about not 64 bit. AMD FX 4-core “Unlocked” processor and seems to meet all the specs. Wound up being the “ioacpi” setting, it needed to be turned on.
    I also had some issues with Windows finding the nic driver at first too so I changed the nictype. There are a few different ones, this one seemed to work so...
    I tried using both bridged and nat connections. Ultimately, I didn't need a bridged network on this device so nat worked fine.
    Here is the initial command with all the stuff that made mine work:
    VBoxManage modifyvm "Windows7" --memory 2048 --cpus 1 --ioacpi on --acpi on --boot1 dvd --nic1 nat --nictype1 82545EM --ostype "Windows7_64" 

    This will create a 40 gig drive for your machine. If you want bigger, just change the 40960 to something higher. (multiples of 1024)
    VBoxManage createhd --filename "HDD-Windows7.vdi" --size 40960 --remember

    Now add a controller fot the hard drive
    VBoxManage storagectl "Windows7" --name "storage-ctrl" --add sata 

    Attach the new hard drive to the machine
    VBoxManage storageattach "Windows7" --storagectl "storage-ctrl" --port 0 --device 0 --type hdd --medium /home/vbox/vms/Windows7/HDD-Windows7.vdi 

    This changed the RPD port to 3389.
    VBoxManage modifyvm "Windows7" --vrde on --vrdeport 3389 

    Add the iso file to the machine as it's CDROM
    [codeVBoxManage storageattach "Windows7" --storagectl "storage-ctrl" --port 1 --device 0 --type dvddrive --medium /home/vbox/]windows7.iso[/code]
    This starts up the machine. Once it's started, use remote desktop or rdesktop to connect by pluggin in your clearos ip followed by the port. Example on Ubuntu: rdesktop 192.168.1.1:3389 and now install Windows 7 from the CD you attached using your RDP session.
    VBoxHeadless --startvm "Windows7" -vrde on -vrdeproperty TCP/Ports=3389 & 


    FINALLY, setup autostart. You will want to be root on this one. Type exit if you are still using the vbox user and you should be root again. You will need to add in the following line to the end of /etc/rc.d/rc.local. I used nano: Copy and paste the following at the bottom:
    /bin/su -l vbox -c '/usr/bin/VBoxHeadless --startvm Windows7 2>&1 &'
    Press CTRL + o to save and CTRL + x to exit when you are done.
    Nano /etc/rc.d/rc.local


    If all went well, when you restart your ClearOS system, the virtual machine will startup automagically as well. If the virtual machine is running whenyou want ot reboot, it is probably a good idea to log into it and shut it down before initiating a reboot. I have “LogMeIn” installed in the Windows 7 machine and it comes on-line a few minutes after the server boots up. At this point, the RDP session is pretty much just to check progress if it fails to show “on line” in LogMeIn.

    That's about it. If you find a better way, please post it. Thanks again for all the other posts that got it working.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, June 01 2012, 11:34 PM - #Permalink
    Resolved
    0 votes
    I had the same problem, it is a hitch between the 220.13 and 220.17 kernel.

    This solved the problem for me, quite posible not all thins is nessesary for you, since I messed it up quite a bit first.

    Will do a fresh install to check the right method.

    1. yum remove kernel-devel
    2. yum remove kernel-headers
    3. yum remove kernel-2.6.32-220.13.1.v6.x86_64 (Think this wil do it)
    4. yum update
    5. yum --enablerepo=* install kernel-devel
    5. yum --enablerepo=* install dkms
    6. cd /lib/modules/`uname -r`
    7. ls -l (The build is read since the kernel have once again changed. :-)
    8. rm -vf build
    9. ln -s /usr/src/kernels/2.6.32-220.17.1.v6.x86_64 build
    10. /etc/init.d/vboxdrv setup

    I had to install the extension pack once again to get the vrde -remote desktop to work again
    Should not, maybe I have reinstaled the vbox to try to get it running. :-)

    11. VBoxManage extpack install /path/th/your/extension/pach/Oracle_VM_VirtualBox_Extension_Pack-4.1.16-78094.vbox-extpack

    12. su vobx (the vbox users you have made)
    13. VBoxHeadless --startvm Win7 & (Change Win7 to your virtual os)

    Working. :-)
    The reply is currently minimized Show
  • Accepted Answer

    Friday, June 01 2012, 03:52 PM - #Permalink
    Resolved
    0 votes
    I had the same issue with dkms, I enabled the “clearos-epel” repository using the web GUI under “System” tab, “Software Repository”.
    Then I went back to the command line, did a "yum update" and "yum install dkms". After that, I did the /etc/init.d/vboxdrv setup and it recompiled without any errors. I will do a write up on all the steps I did this evening, I just got it working perfectly!
    The reply is currently minimized Show
  • Accepted Answer

    Mariano
    Mariano
    Offline
    Wednesday, May 23 2012, 02:44 AM - #Permalink
    Resolved
    0 votes
    Now, i already completed all the steps (I installed the newest version 4.1.16), and when i run either vboxwebserver or usr/bin/vboxwebsrv, i get the following:

    Oracle VM VirtualBox web service version 4.1.16
    (C) 2005-2012 Oracle Corporation
    All rights reserved.
    VirtualBox web service 4.1.16 r78094 linux.x86 (May 22 2012 17:19:45) release lo g
    00:00:00.000 main Log opened 2012-05-23T03:07:22.341025000Z
    00:00:00.000 main OS Product: Linux
    00:00:00.000 main OS Release: 2.6.32-220.17.1.el6.i686
    00:00:00.000 main OS Version: #1 SMP Tue May 15 17:45:22 MDT 2012
    00:00:00.000 main OS Service Pack: #1 SMP Tue May 15 17:45:22 MDT 2012
    00:00:00.000 main Executable: /usr/lib/virtualbox/vboxwebsrv
    00:00:00.000 main Process ID: 31529
    00:00:00.000 main Package type: LINUX_32BITS_RHEL_6
    00:00:00.189 SQPmp Socket connection successful: host = default (localhost), port = 18083, master socket = 8



    If i close the ssh shell, or if i just do ctrl+C, what will happen? Vritualbox will stop running? If so, should I install something like Screen or something to keep that running?


    Thanks in advance!


    EDIT 2:
    Now, I restarted my server, and when I try to run vboxwebserver (or /usr/bin/vboxwebsrv), i get the following:

    [root@gateway ~]# /usr/bin/vboxwebsrv
    WARNING: The vboxdrv kernel module is not loaded. Either there is no module
    available for the current kernel (2.6.32-220.17.1.v6.i686) or it failed to
    load. Please recompile the kernel module and install it by

    sudo /etc/init.d/vboxdrv setup

    You will not be able to start VMs until this problem is fixed.
    Oracle VM VirtualBox web service version 4.1.16


    If I run: sudo /etc/init.d/vboxdrv setup as it says there, i get the follwing:

    [root@gateway ~]# sudo /etc/init.d/vboxdrv setup
    Stopping VirtualBox kernel modules [ OK ]
    Uninstalling old VirtualBox DKMS kernel modules [ OK ]
    Trying to register the VirtualBox kernel modules using DKMS[FAILED]
    (Failed, trying without DKMS)
    Recompiling VirtualBox kernel modules [FAILED]
    (Look at /var/log/vbox-install.log to find out what went wrong


    Then I checked the vbox-install.log and I found the error to be:
    Makefile:172: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.  Stop.

    Then I run: export KERN_DIR=/usr/src/kernels/2.6.32-220.17.1....

    and finally run /etc/init.d/vboxdrv setup again, and now it says the following:

    [root@gateway ~]# /etc/init.d/vboxdrv setup
    Stopping VirtualBox kernel modules [ OK ]
    Uninstalling old VirtualBox DKMS kernel modules [ OK ]
    Removing old VirtualBox pci kernel module [ OK ]
    Removing old VirtualBox netadp kernel module [ OK ]
    Removing old VirtualBox netflt kernel module [ OK ]
    Removing old VirtualBox kernel module [ OK ]
    Trying to register the VirtualBox kernel modules using DKMS[FAILED]
    (Failed, trying without DKMS)
    Recompiling VirtualBox kernel modules [ OK ]
    Starting VirtualBox kernel modules [FAILED]
    (modprobe vboxnetflt failed. Please use 'dmesg' to find out why)


    When I run dmesg, hundreds of lines of errors appears.




    EDIT 3:
    Regarding to the phpvirtualbox. I created an user (vbox), asigned a usergroup (the one that says on the first page of this thread), and created a password to It.
    But when i try to login to phpvirtualbox, i receive the following error:

    Error logging in to vboxwebsrv.
    Details:
    Exception Object
    (
    [message:protected] => Error logging in to vboxwebsrv.
    [string:Exception:private] =>
    [code:protected] => 64
    [file:protected] => /var/www/html/vbox/lib/vboxconnector.php
    [line:protected] => 188
    [trace:Exception:private] => Array
    (
    [0] => Array
    (
    [file] => /var/www/html/vbox/lib/auth/Builtin.php
    [line] => 45
    [function] => connect
    [class] => vboxconnector
    [type] => ->
    [args] => Array
    (
    )

    )

    [1] => Array
    (
    [file] => /var/www/html/vbox/lib/ajax.php
    [line] => 119
    [function] => login
    [class] => phpvbAuthBuiltin
    [type] => ->
    [args] => Array
    (
    [0] => vbox
    [1] => ""vbox password"
    )

    )

    )

    [previous:Exception:private] =>
    )
    The reply is currently minimized Show
  • Accepted Answer

    sbn
    sbn
    Offline
    Tuesday, May 22 2012, 08:50 PM - #Permalink
    Resolved
    0 votes
    Mariano wrote:
    sorry for the extremely stupid question that that im gonna ask, that was somehow answered 2 posts ago:

    Im currently Running COS 6.2 Community. And I would like to have a CentOS Guest OS virtualized, fully dedicated to downloads.

    Which script should I run / install to install Virtual Box on my COS 6.2 box? The script on the first post of this thread?

    Thank you very much in advance!


    I didn't use any of the scripts.

    First do run "cat /proc/sys/kernel/osrelease" and you should see your kernel version. Mine is "2.6.32-220.17.1.v6.x86_64" so then I ran
    yum install kernel-devel-2.6.32-220.17.1.v6.x86_64.
    yum install glibc-common.x86_64 compat-glibc.x86_64 glibc.x86_64 glibc-devel.x86_64 glibc-headers.x86_64 glibc-static.x86_64 glibc-utils.x86_64
    yum install kernel-devel gcc-c++

    Wget is not installed by default, so install that;
    yum -y install wget.x86_64

    Needed to add a couple of repositories:
    rpm --import http://elrepo.org/RPM-GPG-KEY-elrepo.org
    rpm -Uvh http://elrepo.org/elrepo-release-6-4.el6.elrepo.noarch.rpm
    rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt
    wget http://pkgs.repoforge.org/rpmforge-release/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm
    rpm -i rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm

    Then download Virtualbox:
    wget http://download.virtualbox.org/virtualbox/4.1.14/VirtualBox-4.1-4.1.14_77440_rhel6-1.x86_64.rpm
    yum localinstall VirtualBox-4.1-4.1.14_77440_rhel6-1.x86_64.rpm

    export KERN_DIR=/usr/src/kernels/2.6.32-220.17.1.v6.x86_64/

    Then finally I ran:
    /etc/init.d/vboxdrv setup

    For phpvirtualbox:
    yum -y install php-soap.x86_64
    yum -y install unzip
    cd /var/www/html
    wget http://phpvirtualbox.googlecode.com/files/phpvirtualbox-4.1-7.zip
    unzip phpvirtualbox-4.1-7.zip

    Here is where the vboxwevsev just will not run, and still have not had time to determine the cause. I just run "/usr/bin/vboxwebsrv" at the command line through webmin and it works, phpvirtualbox that is. Be sure to follow the instructions about creating the vbox user and groups and giving that user account a password.
    The reply is currently minimized Show
  • Accepted Answer

    Mariano
    Mariano
    Offline
    Thursday, May 17 2012, 05:54 PM - #Permalink
    Resolved
    0 votes
    sorry for the extremely stupid question that that im gonna ask, that was somehow answered 2 posts ago:

    Im currently Running COS 6.2 Community. And I would like to have a CentOS Guest OS virtualized, fully dedicated to downloads.

    Which script should I run / install to install Virtual Box on my COS 6.2 box? The script on the first post of this thread?

    Thank you very much in advance!
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, May 17 2012, 08:58 AM - #Permalink
    Resolved
    0 votes
    This kernel-header and kernel-devel problem has been mentioned in a number of threads but it has not been picked up by the devs, so I have raised bug 615 to hopefully get it sorted once and for all.
    The reply is currently minimized Show
  • Accepted Answer

    sbn
    sbn
    Offline
    Thursday, May 17 2012, 02:26 AM - #Permalink
    Resolved
    0 votes
    dustin wrote:
    Has anyone installed vbox on 6.2? Should the install script provided earlier in the thread work for 6.2? Sorry if it should be obvious, my linux knowledge is still limited.


    Yes, just got it installed today along with phpvirtualbox. One problem I have not resolved is the vboxweb-service does not function properly. I can not use the init.d service, however if I simply run the command "/usr/bin/vboxwebsrv" it starts. Have not had time to resolve this, however I did get virtualbox working and did start the install of several VMs.

    One problem I did encounter, when I used yum to install kernel-headers what I got was "2.6.32-220.13.1.el6.x86_64" yet my kernel is in fact "2.6.32-220.13.1.v6.x86_64". So I then used yum to download the specific headers I needed and vbox was able to re-compile after initial install did not compile the modules. For that I ran /etc/init.d/vbox setup which re-compiled them after they were installed (if you have the correct headers already present this probably won't be necessary).

    When I have time I will post back if I get this websrv issue resolved to see if it is isolated to my *$&@ install or maybe common to 6.2
    The reply is currently minimized Show
  • Accepted Answer

    dustin
    dustin
    Offline
    Wednesday, May 16 2012, 04:18 AM - #Permalink
    Resolved
    0 votes
    Has anyone installed vbox on 6.2? Should the install script provided earlier in the thread work for 6.2? Sorry if it should be obvious, my linux knowledge is still limited.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, April 09 2012, 02:52 PM - #Permalink
    Resolved
    0 votes
    With luck this post indicates they could be made available tomorrow or Tuesday next week.
    The reply is currently minimized Show
  • Accepted Answer

    stassen
    stassen
    Offline
    Monday, April 09 2012, 02:40 PM - #Permalink
    Resolved
    0 votes
    I'm not in a hurry right now and it is good to know the workaround. As far as I'm aware of, I'm running this kernel already for months (assumed that my kernel is NOT affected by any yum upgrade, but I did not check this).

    What is holding up the horses to provide the dev-set ? Other priorities maybe ?

    Would be pleased to see it it resolved
    The reply is currently minimized Show
  • Accepted Answer

    Monday, April 09 2012, 10:37 AM - #Permalink
    Resolved
    0 votes
    Same theme as my post from a few days ago. The devs updated the kernel a few days ago but they did not release the kernel-headers or kernel-devel for this updated kernel. They really need to do that. If you can't wait until then, you should still have the 2.6.18-194.8.1.v5 PAE kernel installed so you can just remove the 2.6.18-308.1.1.v5PAE kernel and reboot or reboot and when you get the option select the old kernel to boot from.
    The reply is currently minimized Show
  • Accepted Answer

    stassen
    stassen
    Offline
    Monday, April 09 2012, 10:36 AM - #Permalink
    Resolved
    0 votes
    The only sources so far found are these: kernel-PAE-devel-2.6.18-308.el5.centos.plus.i686.rpm

    Before installing these, I would like to have any recommendation ;-)
    The reply is currently minimized Show
  • Accepted Answer

    stassen
    stassen
    Offline
    Monday, April 09 2012, 09:46 AM - #Permalink
    Resolved
    0 votes
    After a Yum upgrade my headless Vbox is not running anymore. My Vbox 4.1.10 was extremly stable before.

    Started to read and came to the following steps:

    - Upgrade to 4.1.12 via

    yum localinstall VirtualBox-4.1-4.1.12_77245_rhel5-1.i386.rpm
    VBoxManage extpack install --replace Oracle_VM_VirtualBox_Extension_Pack-4.1.12-77245.vbox-extpack

    But run in the following issue -> Trying to register the VirtualBox kernel modules using DKMS[FAILED]


    [root@system install]# uname -mr
    2.6.18-308.1.1.v5PAE i686
    [root@system install]# /etc/init.d/vboxdrv setup
    Stopping VirtualBox kernel modules [ OK ]
    Uninstalling old VirtualBox DKMS kernel modules [ OK ]
    Trying to register the VirtualBox kernel modules using DKMS[FAILED]
    (Failed, trying without DKMS)
    Recompiling VirtualBox kernel modules [FAILED]
    (Look at /var/log/vbox-install.log to find out what went wrong) -> Makefile:172: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.


    Does anyone had the same issue so far and what was your solution ?

    Thanks in advance
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, February 02 2012, 01:47 PM - #Permalink
    Resolved
    0 votes
    Thank you
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, February 02 2012, 01:41 PM - #Permalink
    Resolved
    0 votes
    My knowledge is only from posts I've seen before. I think I did it a few years ago but can't remember but I would have done it to the client as my VM host/server was Windoze.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, February 02 2012, 01:31 PM - #Permalink
    Resolved
    0 votes
    Thank you
    Would I do it to the server(clears) or client ( centos) ?
    Btw I did google and could not find the definite answer and it seem to be kernel dependent .....
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, February 02 2012, 12:38 PM - #Permalink
    Resolved
    0 votes
    Bearing in mind ClearOS is a CentOS derivative, you will find a lot of references if you google for "Centos vm clock" . It seems you need to add a parameter "divider=10" to the kernel line in menu.lst
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, February 02 2012, 06:38 AM - #Permalink
    Resolved
    0 votes
    Hi,
    I have a problem with time running too fast inside my centos 5.7 client.
    How do I fix it?
    I did a little digging and it does not look like there is a solution yet?
    Has anyone resolved it?
    Thanks
    The reply is currently minimized Show
  • Accepted Answer

    stassen
    stassen
    Offline
    Thursday, January 05 2012, 07:37 PM - #Permalink
    Resolved
    0 votes
    I upgraded to 4.1.8 on my clearos 5.2 up-to-date system. Works without any problem. Don't forget to install Oracle_VM_VirtualBox_Extension_Pack-4.1.8-75467.vbox-extpack to enable RDP services for headless operations.

    Still a question which maybe is resolved by someone. I'm running some headless XP machines and want to add an headless OSX 10.7 to it also. Everything is working with OSX 10.7 on my Clearos 5.2 host, except for the USB mouse. It is working but I have 2 cursors which of course are related to each other but not one. For Windows guest there is a Guest Additions to be installed to resolve audio, video and USB issues. Such an extension does not exists for OSX platforms. This complete setup is headless and the RDP sessions are running in a Windows environment.

    Is there a solution to get this mouse acting directly when using a headless setup ?
    The reply is currently minimized Show
  • Accepted Answer

    Fernando
    Fernando
    Offline
    Friday, December 02 2011, 08:22 PM - #Permalink
    Resolved
    0 votes
    I am unsure whether I have read this on this same topic or on another site, but I have been using VBoxTool to autostart VMs and never had a problem with it.

    It's easy to configure and also a good tool to manage a headless server if you do not want to install phpVirtualBox.

    http://vboxtool.sourceforge.net/
    The reply is currently minimized Show
  • Accepted Answer

    duncan
    duncan
    Offline
    Wednesday, November 30 2011, 02:38 AM - #Permalink
    Resolved
    0 votes
    This setup here provides a nice way of auto starting and stopping your vm's at boot time.

    http://www.kernelhardware.org/virtualbox-auto-start-vm-centos-fedora-redhat/

    you need to edit the script to reflect your user and password and I had to change a line from


    $SU "$VBOXMANAGE controlvm "$VM" acpipowerbutton"

    to

    $SU "$VBOXMANAGE controlvm "${VM%% *}" acpipowerbutton"

    You also need to make your script executable and make sure there are no white spaces in /etc/virtualbox/machines_enabled.
    The reply is currently minimized Show
  • Accepted Answer

    Robert
    Robert
    Offline
    Monday, November 28 2011, 07:02 AM - #Permalink
    Resolved
    0 votes
    Thanks Fernando. I'm glad to hear that my script works for other's especially since it was built with business use in-mind.
    I'm in the process of turning my Client's Full out servers and replacing them with ClearOS Replacing not only the server but their router too.

    This being Said I've not had an bridging issues on the internal nic card.


    Can you please explain the setup you have i will help as much as i can.
    The reply is currently minimized Show
  • Accepted Answer

    David Baty
    David Baty
    Offline
    Sunday, November 13 2011, 11:10 PM - #Permalink
    Resolved
    0 votes
    Thanks for the awesome script to install VirtualBox and phpVirtualBox - it worked perfectly on a new install of 5.2. I am having some issues, though. I want to run a few VMs and have them bridged to the internal interface while ClearOS is the host and is running in gateway mode. Bridging to the external interface works, but bridging to the internal interface doesn't. Anyone done this or know how I can get this working?

    Thanks.
    The reply is currently minimized Show
  • Accepted Answer

    Fernando
    Fernando
    Offline
    Monday, November 07 2011, 10:27 PM - #Permalink
    Resolved
    0 votes
    Hi Robert, I finally got round to uninstall VBox and reinstall using your script.

    RDP works now like a charm. Thank you for it!
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 28 2011, 02:07 PM - #Permalink
    Resolved
    0 votes
    Running ClearOS as a client inside a VirtualBox (tested also with Centos + Ubuntu + BLAG VirtualBox clients on Centos 5 + ClearOS 5.x hosts) I experienced the following symptoms. (both with hostonly and NAT adapters)

    - Slow http(s) browser access to the ClearOS (VirtualBox) machine
    - Failure to load web pages (even :81 and :83) for Windows XP clients and Vista clients (but not Linux?!) on Firefox, IE and chrome. Timeout or very slow for W7 30s to load Web Admin / Horde. Zarafa mail came up with zarafa layout css and logos but a blank screen inside.
    - openVPN connection instability

    It has turned out the problem is due to the default tx/rx offload setting for the adapter within the VM slowing tx and rx traffic through the vboxnet0 interface.

    TESTS
    Create a sizable file on the host and scp it to the VBox:

    [vboxuser@devcos tmp]$ scp 500mbfile root@192.168.56.51:/tmp/500mbfile
    100% 558MB 5.9MB/s 01:34
    [vboxuser@devcos tmp]$ scp root@192.168.56.51:/tmp/500mbfile 500mbfile
    0% 528KB 28.4KB/s 5:35:21 (i had to ctrl-break this one!)

    As you can see bandwidth for the rx from the ClearOS was terrible
    ssh into the VBox and run these commands from inside
    To check the current setting:

    ssh root@192.168.56.51
    root@COS:# ethtool -k eth0
    Offload parameters for eth0:
    rx-checksumming: on
    tx-checksumming: on
    scatter-gather: on
    tcp-segmentation-offload: on
    udp-fragmentation-offload: off
    generic-segmentation-offload: on
    generic-receive-offload: off
    large-receive-offload: off

    THE FIX

    root@COS:# ethtool -K eth0 tx off
    root@COS:# ethtool -K eth0 rx off

    Check the new settings:

    root@COS:# ethtool -k eth0
    Offload parameters for eth0:
    rx-checksumming: off
    tx-checksumming: off
    scatter-gather: off
    tcp-segmentation-offload: off
    udp-fragmentation-offload: off
    generic-segmentation-offload: on
    generic-receive-offload: off
    large-receive-offload: off

    And test the results:

    [vboxuser@devcos tmp]$ scp root@192.168.56.51:/tmp/500mbfile 500mbfile
    100% 558MB 7.3MB/s 01:16
    [vboxuser@devcos tmp]$ scp 500mbfile root@192.168.56.51:/tmp/500mbfile
    100% 558MB 8.3MB/s 01:07

    This is a test server so IO is slow but on the production server (Centos 5 x64bit) is giving between 15MB/s (rx) and 56MB/s (tx) throughput.

    NOW FOR THE WIERD BIT
    If I use ethtool -k to turn the offload back ON, the results do not change from when I turned it OFF. However rebooting the VM brings back the same low tx speeds..
    Now, to make it stick on reboot.. any ideas?
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, September 18 2011, 09:14 PM - #Permalink
    Resolved
    0 votes
    Robert,
    I have tried your script and have problem log in in.
    I get following:
    Exception Object
    (
    [message:protected] => Error logging in to vboxwebsrv.
    [string:private] =>
    [code:protected] => 64
    [file:protected] => /var/www/html/vbox/lib/vboxconnector.php
    [line:protected] => 108
    [trace:private] => Array
    (
    [0] => Array
    (
    [file] => /var/www/html/vbox/lib/vboxconnector.php
    [line] => 239
    [function] => __vboxwebsrvConnect
    [class] => vboxconnector
    [type] => ->
    [args] => Array
    (
    )

    )

    [1] => Array
    (
    [file] => /var/www/html/vbox/lib/auth/Builtin.php
    [line] => 21
    [function] => connect
    [class] => vboxconnector
    [type] => ->
    [args] => Array
    (
    )

    )

    [2] => Array
    (
    [file] => /var/www/html/vbox/lib/ajax.php
    [line] => 108
    [function] => login
    [class] => phpvbAuthBuiltin
    [type] => ->
    [args] => Array
    (
    [0] => admin
    [1] => admin
    )

    )

    )

    )
    Any idea why or how I would resolve it?
    The reply is currently minimized Show
  • Accepted Answer

    Robert
    Robert
    Offline
    Sunday, September 18 2011, 06:15 AM - #Permalink
    Resolved
    0 votes
    look to line 22 - 25 of my script I'm guessing the RDP extension is not installed or maybe not installed correctly.

    if it's not that then maybe a php version issue with you phpvirtualbox i've ran into that but the version downloaded in my script takes care of that issue you also need to make sure your trying to rdp vbox server ip/hostname not the guest os ip/hostname
    The reply is currently minimized Show
  • Accepted Answer

    Fernando
    Fernando
    Offline
    Saturday, September 17 2011, 09:34 PM - #Permalink
    Resolved
    0 votes
    Thank you Robert

    I will try your script when I get a chance to stop VMs and clean my previous VBox install (not now sadly).

    Looking at it, thought, it does not seem to be doing anything different from what I have done before, with the exception of the last steps where you install Java and set the RDP.html page as a defaut one in Firefox.

    Will post feedback after trying it out.

    Any ideas on what could be failing?
    The reply is currently minimized Show
  • Accepted Answer

    Robert
    Robert
    Offline
    Saturday, September 17 2011, 08:09 PM - #Permalink
    Resolved
    0 votes
    Duncan wrote:
    Robert wrote:
    This will help alot: PHP virtualBox
    if you have any issues getting it to run I have a script somewhere to install this as well.


    An install script for that would be very handy :)


    here is My personal Script

    wget http://www.whitacrecomputers.com/get-wfc-vbox.run
    sh ./get-wfc-vbox.run


    this script gives you the option to install a rdp client local to clearos gui interface and makes it appear as first tab and clearos console is second tab while haveing mouse monitor and keyboard attached.


    **** Script Has been updated to include the latest version of phpVirtualBox and files are no longer missing***

    Updated 04/02/2012
    The reply is currently minimized Show
  • Accepted Answer

    Robert
    Robert
    Offline
    Saturday, September 17 2011, 07:37 PM - #Permalink
    Resolved
    0 votes
    Try running my vbox install script posted above if it still don't work then there is some kind of issue I use that script on a regular basis for new installs and have absolutely no issues at all.


    Lan side of clearos firewall does not need ports opened up.
    The reply is currently minimized Show
  • Accepted Answer

    Fernando
    Fernando
    Offline
    Saturday, September 17 2011, 06:56 PM - #Permalink
    Resolved
    0 votes
    Hello,

    I have installed VBox on my ClearOS following Tim's intructions.
    I also installed phpVirtualBox to get a web interfase to create/manage the VMs.

    My problem is that regardless of what I do. it is impossible for me to access the VMs using rdesktop.

    I understand (believe) that is it not possible to use rdesktop from a console on the ClearOS because of its lack of a graphical environment. But, if I open port 3389 on the Incomming page of the ClearOS server I sould be able to user rdesktop from a remote machine on the same network running Ubuntu, right?

    I have copied the VM to my laptop (running Ubuntu and VBox) and had no problems accessing the VM there with rdesktop. So I am assuming that the problem is not with the VM configuration but with either Vbox (the one on the ClearOS) or ClearOS itself.

    I have done my research and try different things, but nothing seem to work, so, any ideas on what could be failing are welcome.

    Oracle VM VirtualBox Extension Pack fro VBox 4.1 is also installed.

    I am running:
    ClearOS 5.2 SP1
    Virtual Box 4.1.0 (73009)
    phpVirtualBox 4.1-1b

    Cheers,
    The reply is currently minimized Show
  • Accepted Answer

    Duncan
    Duncan
    Offline
    Saturday, September 17 2011, 03:45 PM - #Permalink
    Resolved
    0 votes
    Robert wrote:
    This will help alot: PHP virtualBox
    if you have any issues getting it to run I have a script somewhere to install this as well.


    An install script for that would be very handy :)
    The reply is currently minimized Show
  • Accepted Answer

    stassen
    stassen
    Offline
    Saturday, September 03 2011, 06:21 PM - #Permalink
    Resolved
    0 votes
    Due to the fact that I did not have a passw set for vbox, I ran into "Error logging in to vboxwebsrv.". After changing that via "passwd vbos" I was able to manage machines via a webbrowser.
    The reply is currently minimized Show
  • Accepted Answer

    Robert
    Robert
    Offline
    Saturday, September 03 2011, 01:48 PM - #Permalink
    Resolved
    0 votes
    the difference is that clonehd only clones the Hard Drive image. Clonevm Clones the entire thing hardware and all and makes the needed modifications to the config file for there to be no conflicts.
    The reply is currently minimized Show
  • Accepted Answer

    stassen
    stassen
    Offline
    Saturday, September 03 2011, 05:47 AM - #Permalink
    Resolved
    0 votes
    Can someone explain the functional difference between cloneHD and cloneVM. Although working on the PHP installation to eliminate the commandline actions, I would like to know how this is done. I did this previously by manual updating the xml file, but tried it this week by using cloneHD. This clones the HD into a new .vdi, but these are (ofcourse) not registered and therefore don't start.
    The reply is currently minimized Show
  • Accepted Answer

    stassen
    stassen
    Offline
    Saturday, September 03 2011, 05:39 AM - #Permalink
    Resolved
    0 votes
    Robert wrote:
    This will help alot: PHP virtualBox
    if you have any issues getting it to run I have a script somewhere to install this as well.


    Thanks for this great tip. Currently some issues with the configuration, but I did not have enough priority yet to resolve this in the past 24hrs. But weekend arrived ;-)
    The reply is currently minimized Show
  • Accepted Answer

    Robert
    Robert
    Offline
    Saturday, September 03 2011, 12:04 AM - #Permalink
    Resolved
    0 votes
    Yes.
    The reply is currently minimized Show
  • Accepted Answer

    Jimmy
    Jimmy
    Offline
    Saturday, September 03 2011, 12:01 AM - #Permalink
    Resolved
    0 votes
    stassen wrote:
    I have re-installed Vbox and a guest on my machine. I would like to "clone" this virtual machine into 6 new ones with different namens. Export and import does not seem to work, but what will work fast and good.

    It would be a handy thing to grab a clean disposable computer of the shelf ;-)




    I have not done this. but was wondering if this might be the way to do it

    http://www.virtualbox.org/manual/ch08.html#vboxmanage-clonevm
    The reply is currently minimized Show
  • Accepted Answer

    Robert
    Robert
    Offline
    Thursday, September 01 2011, 07:40 PM - #Permalink
    Resolved
    0 votes
    This will help alot: PHP virtualBox
    if you have any issues getting it to run I have a script somewhere to install this as well.
    The reply is currently minimized Show
  • Accepted Answer

    stassen
    stassen
    Offline
    Thursday, September 01 2011, 12:29 PM - #Permalink
    Resolved
    0 votes
    I have re-installed Vbox and a guest on my machine. I would like to "clone" this virtual machine into 6 new ones with different namens. Export and import does not seem to work, but what will work fast and good.

    It would be a handy thing to grab a clean disposable computer of the shelf ;-)
    The reply is currently minimized Show
  • Accepted Answer

    Jimmy
    Jimmy
    Offline
    Sunday, August 14 2011, 03:22 AM - #Permalink
    Resolved
    0 votes
    ***Windows XP***

    Not sure if this is the best way to do this. But I ran out of HDD space allocated 50G/73G so used the "shared folders" option

    Documentation can be found here to create another Drive that points to a directory on the clearos machine

    Stopped the VM, then used

    VBoxManage sharedfolder add "WindowsXP" --name "yoursharenamehere" --hostpath /a/path/on/clearos

    then mapped the drive in windowsxp so

    For me that means I have a C:(50G) and a E: (73G) (two 73G drives)

    if there is a better way to do this, I am interested. I guess this only affects people with small drives. --resize was not an option for me I don't think.

    forgot to mention I had to change the permission for vbox user to be able to write to the /a/path/on/clearos machine as well
    The reply is currently minimized Show
  • Accepted Answer

    Jimmy
    Jimmy
    Offline
    Wednesday, August 10 2011, 06:00 AM - #Permalink
    Resolved
    0 votes
    VBoxGuestAdditions_4.1.0.iso can be found @ VBoxGuestAdditions_4.1.0.iso
    The reply is currently minimized Show
  • Accepted Answer

    Jimmy
    Jimmy
    Offline
    Thursday, July 28 2011, 08:27 AM - #Permalink
    Resolved
    0 votes
    My humblest apol's , had trouble as I did not install the extension pack. I thought I did..... but upon re-doing it.... MUCH BETTER ;)


    Oracle VM VirtualBox Headless Interface 4.1.0
    (C) 2008-2011 Oracle Corporation
    All rights reserved.

    VRDE server is listening on port 3389.
    The reply is currently minimized Show
  • Accepted Answer

    Jimmy
    Jimmy
    Offline
    Thursday, July 28 2011, 03:58 AM - #Permalink
    Resolved
    0 votes
    ^---many thanks for this update

    I am having trouble with a LIVE linux iso (one of those linux turnkey dvds) have not spent enough time reading up. but I could not RDP once it started.

    Oracle VM VirtualBox Headless Interface 4.1.0
    (C) 2008-2011 Oracle Corporation
    All rights reserved.


    going to go to http://www.virtualbox.org/manual/UserManual.html#vboxmanage-modifyvm and see if I can make sense of it, might even install XP (as above) to make sure I understand. lack of experience/knowledge here I modified the above hoping it would work for my needs
    The reply is currently minimized Show
  • Accepted Answer

    Robert
    Robert
    Offline
    Friday, July 22 2011, 04:01 AM - #Permalink
    Resolved
    0 votes
    [file name=Vbox.txt size=1193]http://www.clearfoundation.com/media/kunena/attachments/legacy/files/Vbox.txt[/file] heres a script for the newest version of virtual box
    For Windows XP. settings can be changed to make other VMs

    #!/bin/bash
    PAE="`uname -r | grep PAE`"
    echo -e "Start Install of Development Tools"
    yum groupinstall "Development Tools"
    if [[ -n "$PAE" ]] ; then
    echo -e "PAE Kernel Installed\nInstalling kernel-PAE-devel"
    yum install kernel-PAE-devel
    else
    echo -e "PAE Kernel not Installed\nInstalling kernel-devel"
    yum install kernel-devel
    fi
    cd /var/tmp
    echo -e "Download Oracle GPG Key"
    wget -q http://download.virtualbox.org/virtualbox/debian/oracle_vbox.asc
    rpm --import oracle_vbox.asc
    echo -e "Download Oracle VirtualBox RPM"
    wget http://download.virtualbox.org/virtualbox/4.1.0/VirtualBox-4.1-4.1.0_73009_rhel5-1.i386.rpm
    echo -e "Start Install of VirtualBox"
    yum localinstall VirtualBox-4.1-4.1.0_73009_rhel5-1.i386.rpm
    echo -e "Download VirtualBox RDP extPack"
    wget http://download.virtualbox.org/virtualbox/4.1.0/Oracle_VM_VirtualBox_Extension_Pack-4.1.0-73009.vbox-extpack
    echo -e "Install VirtualBox RDP extPack "
    VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.1.0-73009.vbox-extpack
    echo "Adding user 'vbox' to vboxusers group"
    /usr/sbin/useradd -r -m vbox
    /usr/sbin/usermod -a -G vboxusers vbox
    cat /etc/passwd | grep vbox
    cat /etc/group | grep vbox
    echo "Install Finished"


    ok now to create a VM for Windows XP and start it.


    su - vbox
    VBoxManage createvm --name "WindowsXP" --ostype "WindowsXP" --register
    VBoxManage modifyvm "WindowsXP" --memory "512" --acpi on --boot1 dvd --nic1 bridged --bridgeadapter1 eth1
    VBoxManage createhd --filename "WinXP.vdi" --size 10000
    VBoxManage storagectl "WindowsXP" --name "IDE Controller" --add ide
    VBoxManage modifyvm "WindowsXP" --hda "WinXP.vdi"
    #Stop here be sure to change the iso location
    VBoxManage storageattach "WindowsXP" --storagectl "IDE Controller" --port 1 --device 0 --type dvddrive --medium /home/blindrain/MRI-5.0.4.0-SX-CRACKED.iso
    VBoxManage modifyvm "WindowsXP" --dvd /home/blindrain/MRI-5.0.4.0-SX-CRACKED.iso

    VBoxHeadless --startvm "WindowsXP"


    [file name=Vbox.txt size=1193]http://www.clearfoundation.com/media/kunena/attachments/legacy/files/Vbox.txt[/file]
    Attachments:
    The reply is currently minimized Show
  • Accepted Answer

    Duncan
    Duncan
    Offline
    Wednesday, March 30 2011, 11:21 PM - #Permalink
    Resolved
    0 votes
    yeah that sounds about right, on the host machine the divider line tags on the end of the kernel line in grub config I think, youll suss it, I think on this youre more in the know than I. Either that or the kernel could be rebuilt Ive heard, but this is a simpler and safer way.

    Apparently this issue mainly manifests on distros built with 1000mhz kernels, such as CentOS

    I was just running 1 XP Pro guest on my webserver and it really did drag it down quite severely at times. However that said, the XP VM on my Centos server runs extremely well, but I didnt run it before doing the grub divider so I couldnt say if the issue was there or not, I didnt have the time and inclination to test every single factor :)

    I work mobile, basically on any ship that requires maintenance, whenever and wherever the ship might happen to be, installation or repair of navigational equipment, sensors and associated systems, and other things. I used to do IT and work in offices for a long time, among other jobs Ive done, its just not for me. If Im in the office its not a sensible or productive place for me to be :)
    The reply is currently minimized Show
  • Accepted Answer

    organetic
    organetic
    Offline
    Wednesday, March 30 2011, 09:59 AM - #Permalink
    Resolved
    0 votes
    So, it seems we have to apply this at the host, in this case, the ClearOS machine.

    in /boot/grub/menu.lst

    divider=10

    right?

    Or should this be done at each CentOS guest too?

    I'm also at work... Were I have the time to address this issue :)

    I will test everything as our production server clone for 1 month.

    After that, I can tell my history.
    The reply is currently minimized Show
  • Accepted Answer

    Duncan
    Duncan
    Offline
    Wednesday, March 30 2011, 09:50 AM - #Permalink
    Resolved
    0 votes
    Hi, ok, undersatnd Im no expert :)

    I should point out Ive only seen this problem so far on a whm/cpanel box running centos 5.5 x64 but theres lots on the web about hitting similar probs, also you might search the vbox forums, lots there too. The problem seems to have been around for some time with vbox and the support for vbox seem to consider it a failing of centos not their software.

    It has to do with idle machines causing high load when idle on multi cpu systems, Ive read about setting CPU affinity, turning off nested paging, turning acpi on, the problem only existing with a single guest and having a second guest alleviating problem etc

    The gist of it seems to be to do with systems that have 1000mhz kernel, and setting a divider to change to 100mhz kernel

    http://steve-brown.id.au/linux/centos-5-in-virtualbox-high-cpu-usage.html

    http://forums.virtualbox.org/viewtopic.php?t=7022

    At work right now, ill try to post better links later.
    The reply is currently minimized Show
  • Accepted Answer

    organetic
    organetic
    Offline
    Wednesday, March 30 2011, 09:30 AM - #Permalink
    Resolved
    0 votes
    Could you please tell me more about the "kernel cpu timing" issue and how to fix it?

    I'm almost finishing my tutorial on how to enable both OpenVZ and Virtualbox at the very same machine. You can check it here:

    http://www.clearfoundation.com/component/option,com_kunena/Itemid,232/catid,40/func,view/id,26118/#26118

    and this will surely be a nice addition...
    The reply is currently minimized Show
  • Accepted Answer

    Duncan
    Duncan
    Offline
    Monday, March 28 2011, 06:40 PM - #Permalink
    Resolved
    0 votes
    Im running very latest, v4.x, I addressed the kernel cpu timing issue just in case and Im using a modded version of vboxtool as the command structure of virtualbox altered somewhere in v3

    http://www.clearfoundation.com/component/option,com_kunena/Itemid,232/catid,40/func,view/id,25566/

    Boots ok and plays well on a dual core atom 330 machine, just using it to run a small XP but it doesnt seem to trouble the host at all.
    The reply is currently minimized Show
  • Accepted Answer

    organetic
    organetic
    Offline
    Monday, March 28 2011, 05:33 PM - #Permalink
    Resolved
    0 votes
    After reading all the posts in this thread I'm still trying to find out the most stable version of VirtualBox to install and also the best method.

    I'm not worried with sound and any multimedia feature... I'm just worried with stability and network connections.

    Please advise me on this so that I can start installation ;)
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, February 19 2011, 05:16 AM - #Permalink
    Resolved
    0 votes
    I am trying to setup Virtualbox on clearos 5.2SP1 but if i configure the networking as either bridged or host (I really dont want to stuff around with NAT) the guest causes the host to lock-up, requiring a hard reset, after some period of up to half an hour. Using NAT seems to work (at least the system lasted a day or so with no issues).

    I have tried using Vbox versions 4.0.4, 4.0.2 and 3.2.12 and they all exhibit the same behavior.

    System is an E6600 on an nvidia motherboard (its a retired main system) with 4GB ram, network cards are the Nvidia standard (forcedeth drivers).

    I have attached what looks to me like a crash dump that was spat out on my SSH session once just before the system crashed, don't know if it is of any use though.

    Anyone have any ideas what's going on here? [file name=VboxError.txt size=118167]http://www.clearfoundation.com/media/kunena/attachments/legacy/files/VboxError.txt[/file]
    The reply is currently minimized Show
  • Accepted Answer

    stassen
    stassen
    Offline
    Sunday, January 30 2011, 01:46 PM - #Permalink
    Resolved
    0 votes
    After upgrading to 5.2 today I decided also to see if the 4.0 Vbox version would resolve my audio problem

    The upgrade was executed after removing the previous installation. I followed the notes on http://www.howtoforge.com/vboxheadless-running-virtual-machines-with-virtualbox-4.0-on-a-headless-fedora-14-server which did the job.

    Believe it or not -> Audio issue resolved. I'm not 100% sure that this is only related to Vbox, because I also reinstalled alsa drivers, mplayer and esound. I did not change anything in my virtual machine configuration BTW

    Vbox 4.0 is running fine now for 30 minutes, so let's hope it stays like that.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, January 17 2011, 02:42 PM - #Permalink
    Resolved
    0 votes
    Ah, a yum clean all sorted it.

    Thanks!
    The reply is currently minimized Show
  • Accepted Answer

    Monday, January 17 2011, 09:39 AM - #Permalink
    Resolved
    0 votes
    Temporary mirror glitch? the RPM's appear to be here and download ok manually
    http://download.clearfoundation.com/clearos/enterprise/5.2/System/RPMS/

    EDIT: Looks like it's trying to grab them from the console subdirectory - can you run 'yum clean all' first and then try again.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, January 16 2011, 10:43 AM - #Permalink
    Resolved
    0 votes
    Anyone managed to install the new 4.0 version?

    When I try I get the following errors from the ClearOS repositories:


    wget http://download.virtualbox.org/virtualbox/4.0.0/VirtualBox-4.0-4.0.0_69151_rhel5-1.i386.rpm
    yum localinstall VirtualBox-4.0-4.0.0_69151_rhel5-1.i386.rpm


    Are the mirrors OK? The dependencies resolve OK, but the download fails.


    Loading "kmod" plugin
    Loading "protect-packages" plugin
    Setting up Local Package Process
    Examining VirtualBox-4.0-4.0.0_69151_rhel5-1.i386.rpm: VirtualBox-4.0 - 4.0.0_69151_rhel5-1.i386
    Marking VirtualBox-4.0-4.0.0_69151_rhel5-1.i386.rpm to be installed
    Resolving Dependencies
    --> Running transaction check
    ---> Package VirtualBox-4.0.i386 0:4.0.0_69151_rhel5-1 set to be updated
    --> Processing Dependency: libGL.so.1 for package: VirtualBox-4.0
    --> Processing Dependency: libGLU.so.1 for package: VirtualBox-4.0
    --> Processing Dependency: libICE.so.6 for package: VirtualBox-4.0
    --> Processing Dependency: libSDL-1.2.so.0 for package: VirtualBox-4.0
    --> Processing Dependency: libSM.so.6 for package: VirtualBox-4.0
    --> Processing Dependency: libXcursor.so.1 for package: VirtualBox-4.0
    --> Processing Dependency: libXext.so.6 for package: VirtualBox-4.0
    --> Processing Dependency: libXi.so.6 for package: VirtualBox-4.0
    --> Processing Dependency: libXinerama.so.1 for package: VirtualBox-4.0
    --> Processing Dependency: libXmu.so.6 for package: VirtualBox-4.0
    --> Processing Dependency: libXrandr.so.2 for package: VirtualBox-4.0
    --> Processing Dependency: libXt.so.6 for package: VirtualBox-4.0
    --> Processing Dependency: libasound.so.2 for package: VirtualBox-4.0
    --> Running transaction check
    ---> Package libXmu.i386 0:1.0.2-5 set to be updated
    ---> Package libICE.i386 0:1.0.1-2.1 set to be updated
    ---> Package libXrandr.i386 0:1.1.1-3.3 set to be updated
    ---> Package mesa-libGLU.i386 0:6.5.1-7.8.el5 set to be updated
    ---> Package mesa-libGL.i386 0:6.5.1-7.8.el5 set to be updated
    --> Processing Dependency: libXxf86vm.so.1 for package: mesa-libGL
    --> Processing Dependency: libdrm.so.2 for package: mesa-libGL
    ---> Package libXinerama.i386 0:1.0.1-2.1 set to be updated
    ---> Package libXt.i386 0:1.0.2-3.2.el5 set to be updated
    ---> Package libXi.i386 0:1.0.1-4.el5_4 set to be updated
    ---> Package libSM.i386 0:1.0.1-3.1 set to be updated
    ---> Package libXcursor.i386 0:1.1.7-1.1 set to be updated
    --> Processing Dependency: libXfixes.so.3 for package: libXcursor
    ---> Package libXext.i386 0:1.0.1-2.1 set to be updated
    ---> Package SDL.i386 0:1.2.10-8.el5 set to be updated
    --> Processing Dependency: libesd.so.0 for package: SDL
    --> Processing Dependency: libaudiofile.so.0 for package: SDL
    ---> Package alsa-lib.i386 0:1.0.17-1.el5 set to be updated
    --> Running transaction check
    ---> Package libXfixes.i386 0:4.0.1-2.1 set to be updated
    ---> Package libdrm.i386 0:2.0.2-1.1 set to be updated
    ---> Package audiofile.i386 1:0.2.6-5 set to be updated
    ---> Package esound.i386 1:0.2.36-3 set to be updated
    ---> Package libXxf86vm.i386 0:1.0.1-3.1 set to be updated
    --> Finished Dependency Resolution

    Dependencies Resolved

    =============================================================================
    Package Arch Version Repository Size
    =============================================================================
    Installing:
    VirtualBox-4.0 i386 4.0.0_69151_rhel5-1 VirtualBox-4.0-4.0.0_69151_rhel5-1.i386.rpm 118 M
    Installing for dependencies:
    SDL i386 1.2.10-8.el5 clearcentos-os 233 k
    alsa-lib i386 1.0.17-1.el5 base-os 412 k
    audiofile i386 1:0.2.6-5 base-os 107 k
    esound i386 1:0.2.36-3 base-os 129 k
    libICE i386 1.0.1-2.1 base-os 54 k
    libSM i386 1.0.1-3.1 base-os 27 k
    libXcursor i386 1.1.7-1.1 base-os 32 k
    libXext i386 1.0.1-2.1 base-os 35 k
    libXfixes i386 4.0.1-2.1 base-os 14 k
    libXi i386 1.0.1-4.el5_4 base-os 25 k
    libXinerama i386 1.0.1-2.1 base-os 9.7 k
    libXmu i386 1.0.2-5 base-os 62 k
    libXrandr i386 1.1.1-3.3 base-os 15 k
    libXt i386 1.0.2-3.2.el5 base-os 173 k
    libXxf86vm i386 1.0.1-3.1 base-os 14 k
    libdrm i386 2.0.2-1.1 base-os 19 k
    mesa-libGL i386 6.5.1-7.8.el5 base-os 9.6 M
    mesa-libGLU i386 6.5.1-7.8.el5 clearcentos-os 225 k

    Transaction Summary
    =============================================================================
    Install 19 Package(s)
    Update 0 Package(s)
    Remove 0 Package(s)

    Total download size: 129 M
    Is this ok [y/N]: y
    Downloading Packages:
    http://download1.clearfoundation.com/clearos/enterprise/5.2/console/libXcursor-1.1.7-1.1.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download.clearfoundation.com/clearos/enterprise/5.2/console/libXcursor-1.1.7-1.1.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download3.clearfoundation.com/clearos/enterprise/5.2/console/libXcursor-1.1.7-1.1.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download4.clearfoundation.com/clearos/enterprise/5.2/console/libXcursor-1.1.7-1.1.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download2.clearfoundation.com/clearos/enterprise/5.2/console/libXcursor-1.1.7-1.1.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download1.clearfoundation.com/clearos/enterprise/5.2/console/libXi-1.0.1-4.el5_4.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download.clearfoundation.com/clearos/enterprise/5.2/console/libXi-1.0.1-4.el5_4.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download3.clearfoundation.com/clearos/enterprise/5.2/console/libXi-1.0.1-4.el5_4.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download4.clearfoundation.com/clearos/enterprise/5.2/console/libXi-1.0.1-4.el5_4.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download2.clearfoundation.com/clearos/enterprise/5.2/console/libXi-1.0.1-4.el5_4.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download1.clearfoundation.com/clearos/enterprise/5.2/console/libXinerama-1.0.1-2.1.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download.clearfoundation.com/clearos/enterprise/5.2/console/libXinerama-1.0.1-2.1.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download3.clearfoundation.com/clearos/enterprise/5.2/console/libXinerama-1.0.1-2.1.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download4.clearfoundation.com/clearos/enterprise/5.2/console/libXinerama-1.0.1-2.1.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download2.clearfoundation.com/clearos/enterprise/5.2/console/libXinerama-1.0.1-2.1.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download1.clearfoundation.com/clearos/enterprise/5.2/console/libXrandr-1.1.1-3.3.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download.clearfoundation.com/clearos/enterprise/5.2/console/libXrandr-1.1.1-3.3.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download3.clearfoundation.com/clearos/enterprise/5.2/console/libXrandr-1.1.1-3.3.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download4.clearfoundation.com/clearos/enterprise/5.2/console/libXrandr-1.1.1-3.3.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download2.clearfoundation.com/clearos/enterprise/5.2/console/libXrandr-1.1.1-3.3.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download1.clearfoundation.com/clearos/enterprise/5.2/console/libXfixes-4.0.1-2.1.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download.clearfoundation.com/clearos/enterprise/5.2/console/libXfixes-4.0.1-2.1.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download3.clearfoundation.com/clearos/enterprise/5.2/console/libXfixes-4.0.1-2.1.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download4.clearfoundation.com/clearos/enterprise/5.2/console/libXfixes-4.0.1-2.1.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.
    http://download2.clearfoundation.com/clearos/enterprise/5.2/console/libXfixes-4.0.1-2.1.i386.rpm: [Errno 9] Requested Range Not Satisfiable
    Trying other mirror.


    Error Downloading Packages:
    libXcursor - 1.1.7-1.1.i386: failure: console/libXcursor-1.1.7-1.1.i386.rpm from base-os: [Errno 256] No more mirrors to try.
    libXinerama - 1.0.1-2.1.i386: failure: console/libXinerama-1.0.1-2.1.i386.rpm from base-os: [Errno 256] No more mirrors to try.
    libXi - 1.0.1-4.el5_4.i386: failure: console/libXi-1.0.1-4.el5_4.i386.rpm from base-os: [Errno 256] No more mirrors to try.
    libXfixes - 4.0.1-2.1.i386: failure: console/libXfixes-4.0.1-2.1.i386.rpm from base-os: [Errno 256] No more mirrors to try.
    libXrandr - 1.1.1-3.3.i386: failure: console/libXrandr-1.1.1-3.3.i386.rpm from base-os: [Errno 256] No more mirrors to try.
    The reply is currently minimized Show
  • Accepted Answer

    stassen
    stassen
    Offline
    Sunday, January 09 2011, 11:29 AM - #Permalink
    Resolved
    0 votes
    My audio summary...

    After spending 4 trillion hrs to get my audio issues fixed, I found the problem (I think).

    My Windows XP has identified the PCI hardware as

    PCI\VEN_8086&DEV_2415&REV_01
    PCI\VEN_8086&DEV_2415
    PCI\VEN_8086&CC_040100
    PCI\VEN_8086&CC_0401
    PCI\VEN_8086
    PCI\CC_040100
    PCI\CC_0401

    and is looking for drivers for it (but can not be found).

    Googled and found a ticket/issue in the Vbox forum discussing the hardware emulation used in Vbox (which is pretty old already). Suggestion made there is to update the used "emulated hardware" in VirtualBox to a new standard.
    VirtualBox 4.0 has indeed newer hardware emulated, but then I have to upgrade my ClearOS install again.

    Anyone already succesful upgraded to verison 4.0 ?
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, January 08 2011, 03:47 AM - #Permalink
    Resolved
    0 votes
    Hi all

    I''ve tryed to install VBoxGuestAdditions in ububtu, but it fails..

    Did any one installed this with success ?

    Thx
    The reply is currently minimized Show
  • Accepted Answer

    stassen
    stassen
    Offline
    Wednesday, January 05 2011, 04:37 PM - #Permalink
    Resolved
    0 votes
    See my update post for the latest info and new question
    The reply is currently minimized Show
  • Accepted Answer

    stassen
    stassen
    Offline
    Sunday, January 02 2011, 11:39 AM - #Permalink
    Resolved
    0 votes
    Let see if I can finalize my pending solution -> Getting audio connection between Vbox and ClearOS. Previous Audio history

    So far playing music via ClearOS is not the issue anymore. Using "mplayer -ao oss *" plays any mp3 defined in the config.

    I defined a new machine with Vbox and set the audio specs to "VBoxManage modifyvm "WorkstationXP" --audio oss --audiocontroller sb16" assuming that this would solve my "clicking only sound" in my RDP session (Host OS: Windows XP Corporate dec 2010). After setting up my virtual machine I had to install the SB16 comp myself, because the "Hardware" was not recognized automatically.

    Result -> No improvement.

    Update 1:

    - Changed the audio settings of my Vbox to --audio oss -audiocontroller ac97
    - Any driver found on the internet for Intel 82801AA AC'97 audio in fora like Virtual Box, Ubuntu etc etc tried without succes
    - Also tried a "standard" realtek AC97 driver and HDA driver without any succes

    Question for people with working audio on XP prof SP3 :
    - Which audio card is defined in your Windows XP session and does it work
    - If it is an AC97, where did you obtain the driver and which version of Vbox are you running

    General Question in respect to Vbox: "Is it possible to emulate an SB16 card by defining this via VBoxManage ? " even your local HW is indeed AC97 "compatible" ? . I would appreciate if anybody with a Shuttle K45 which is running ClearOS 5.x or up AND a Vbox with working audio tells me that it is possible ;-) I'm starting to doubt ......
    The reply is currently minimized Show
  • Accepted Answer

    Khairun
    Khairun
    Offline
    Tuesday, November 02 2010, 02:48 PM - #Permalink
    Resolved
    0 votes
    Gosh.. you the man.. recompiling completed... thanks so much...
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, November 02 2010, 02:44 PM - #Permalink
    Resolved
    0 votes
    You don't need to reinstall VirtualBox...you just need to run as root:-
    /etc/init.d/vboxdrv setup
    The reply is currently minimized Show
  • Accepted Answer

    Khairun
    Khairun
    Offline
    Tuesday, November 02 2010, 02:01 PM - #Permalink
    Resolved
    0 votes
    Here's another info..


    [root@lod ~]# rpm -qa | grep -i VirtualBox
    VirtualBox-3.2-3.2.10_66523_rhel5-1

    [root@lod tmp]# rpm -e VirtualBox-3.2-3.2.10_66523_rhel5-1.i386.rpm
    error: package VirtualBox-3.2-3.2.10_66523_rhel5-1.i386.rpm is not installed

    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, November 02 2010, 01:58 PM - #Permalink
    Resolved
    0 votes
    Hi, correct that's not the PAE kernel. PAE is for systems with more than 4GB RAM
    The reply is currently minimized Show
  • Accepted Answer

    Khairun
    Khairun
    Offline
    Tuesday, November 02 2010, 01:56 PM - #Permalink
    Resolved
    0 votes
    I picked this one.. and seem it's accepted..
    kernel-devel-2.6.32.21-166.timb4.i686.rpm
    but when I tried to install
    yum localinstall VirtualBox-3.2-3.2.10_66523_rhel5-1.i386.rpm,

    it's said

    VirtualBox-3.2-3.2.10_66523_rhel5-1.i386.rpm: does not update installed package.
    Nothing to do

    thanks for your help and assistance
    The reply is currently minimized Show
  • Accepted Answer

    Khairun
    Khairun
    Offline
    Tuesday, November 02 2010, 01:39 PM - #Permalink
    Resolved
    0 votes
    Thanks, Tim.. but how can I tell which kernel that I'm using now? sorry noob question..

    [root@lod tmp]# uname -r
    2.6.32.21-166.timb4.i686

    It's meant that it's not PAE right? Sorry but I remember that I successfully install the PAE one using ClearOS default repository.. I guess.. sorry I left my logs copy at the office. I'm at home now...
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, November 02 2010, 01:13 PM - #Permalink
    Resolved
    0 votes
    You need to install the kernel-devel RPM for the newer kernel, so that VirtualBox can rebuild it's driver modules. Make sure you pick the right one if your using PAE or not...

    You can find it here
    http://download.clearfoundation.com/community/timb80/kernel/
    The reply is currently minimized Show
  • Accepted Answer

    Khairun
    Khairun
    Offline
    Tuesday, November 02 2010, 11:08 AM - #Permalink
    Resolved
    0 votes
    :P Hello All,

    Could you please look at on my configuration and setting below, I tried many diferrent way, first following the guide on this topic it self, I thin k that my problem is on this kernel that need source?

    2.6.32.21-166.timb4.i686

    Thanks everyone..


    [root@lod tmp]# uname -r
    2.6.32.21-166.timb4.i686
    [root@lod tmp]# rpm -qa | grep -i VirtualBox VirtualBox-3.0.12_54655_rhel5-1
    [root@lod tmp]rpm -e VirtualBox-3.0.12_54655_rhel5-1
    [root@lod tmp]# wget http://download.virtualbox.org/virtualbox/3.2.10/VirtualBox-3.2-3.2.10_66523_rhel5-1.i386.rpm
    --2010-11-02 06:31:55-- http://download.virtualbox.org/virtualbox/3.2.10/VirtualBox-3.2-3.2.10_66523_rhel5-1.i386.rpm
    Resolving download.virtualbox.org... 137.254.16.69
    Connecting to download.virtualbox.org|137.254.16.69|:80... connected.
    HTTP request sent, awaiting response... 302 Moved Temporarily
    Location: http://dlc.sun.com.edgesuite.net/virtualbox/3.2.10/VirtualBox-3.2-3.2.10_66523_rhel5-1.i386.rpm [following]
    --2010-11-02 06:31:56-- http://dlc.sun.com.edgesuite.net/virtualbox/3.2.10/VirtualBox-3.2-3.2.10_66523_rhel5-1.i386.rpm
    Resolving dlc.sun.com.edgesuite.net... 118.214.190.24, 118.214.190.91
    Connecting to dlc.sun.com.edgesuite.net|118.214.190.24|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 56230723 (54M) [application/x-redhat-package-manager]
    Saving to: `VirtualBox-3.2-3.2.10_66523_rhel5-1.i386.rpm'

    100%[======================================>] 56,230,723 44.3K/s in 21m 46s

    2010-11-02 06:53:47 (42.0 KB/s) - `VirtualBox-3.2-3.2.10_66523_rhel5-1.i386.rpm' saved [56230723/56230723]

    [root@lod tmp]# wget http://download.virtualbox.org/virtualbox/debian/oracle_vbox.asc
    --2010-11-02 06:58:06-- http://download.virtualbox.org/virtualbox/debian/oracle_vbox.asc
    Resolving download.virtualbox.org... 137.254.16.69
    Connecting to download.virtualbox.org|137.254.16.69|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 1734 (1.7K) [text/plain]
    Saving to: `oracle_vbox.asc'

    100%[======================================>] 1,734 --.-K/s in 0s

    2010-11-02 06:58:06 (12.0 MB/s) - `oracle_vbox.asc' saved [1734/1734]

    [root@lod tmp]# rpm --import oracle_vbox.asc
    [root@lod tmp]# yum localinstall VirtualBox-3.2-3.2.10_66523_rhel5-1.i386.rpm Loading "protect-packages" plugin
    Loading "kmod" plugin
    Setting up Local Package Process
    Examining VirtualBox-3.2-3.2.10_66523_rhel5-1.i386.rpm: VirtualBox-3.2 - 3.2.10_66523_rhel5-1.i386
    Marking VirtualBox-3.2-3.2.10_66523_rhel5-1.i386.rpm to be installed
    Resolving Dependencies
    --> Running transaction check
    ---> Package VirtualBox-3.2.i386 0:3.2.10_66523_rhel5-1 set to be updated
    --> Processing Dependency: libGLU.so.1 for package: VirtualBox-3.2
    --> Running transaction check
    ---> Package mesa-libGLU.i386 0:6.5.1-7.8.el5 set to be updated
    --> Finished Dependency Resolution

    Dependencies Resolved

    =============================================================================
    Package Arch Version Repository Size
    =============================================================================
    Installing:
    VirtualBox-3.2 i386 3.2.10_66523_rhel5-1 VirtualBox-3.2-3.2.10_66523_rhel5-1.i386.rpm 106 M
    Installing for dependencies:
    mesa-libGLU i386 6.5.1-7.8.el5 clearcentos-os 225 k

    Transaction Summary
    =============================================================================
    Install 2 Package(s)
    Update 0 Package(s)
    Remove 0 Package(s)

    Total download size: 106 M
    Is this ok [y/N]: y
    Downloading Packages:
    (1/1): mesa-libGLU-6.5.1-7.8.el5.i386.rpm | 225 kB 00:08
    Running rpm_check_debug
    Running Transaction Test
    Finished Transaction Test
    Transaction Test Succeeded
    Running Transaction
    Installing: mesa-libGLU ######################### [1/2]
    Installing: VirtualBox-3.2 ######################### [2/2]

    Creating group 'vboxusers'. VM users must be member of that group!

    No precompiled module for this kernel found -- trying to build one. Messages
    emitted during module compilation will be logged to /var/log/vbox-install.log.

    Stopping VirtualBox kernel modules [ OK ]
    Uninstalling old VirtualBox DKMS kernel modules [ OK ]
    Trying to register the VirtualBox kernel modules using DKMS [FAILED]
    (Failed, trying without DKMS)
    Recompiling VirtualBox kernel modules [FAILED]
    (Look at /var/log/vbox-install.log to find out what went wrong)

    Installed: VirtualBox-3.2.i386 0:3.2.10_66523_rhel5-1
    Dependency Installed: mesa-libGLU.i386 0:6.5.1-7.8.el5
    Complete!
    [root@lod tmp]#
    Makefile:159: *** Error: unable to find the sources of your current Linux kerne$
    The reply is currently minimized Show
  • Accepted Answer

    Monday, November 01 2010, 09:45 AM - #Permalink
    Resolved
    0 votes
    Or just create a symlink for the:-
    /home/vbox/.VirtualBox/machines
    /home/vbox/.VirtualBox/HardDisks

    folders to another location...i've used that successfully to hold VM's on an external USB :)

    Don't forget the ownership has to be read/write by the user 'vbox'
    The reply is currently minimized Show
  • Accepted Answer

    Moses
    Moses
    Offline
    Sunday, October 31 2010, 08:56 AM - #Permalink
    Resolved
    0 votes
    Not tried it, but this should work.

    Copy the Machines and HardDisk folders to new location
    vi /home/vbox/.VirtualBox/VirtualBox.xml

    Search for filepath= and adjust the entries
    The reply is currently minimized Show
  • Accepted Answer

    Duncan
    Duncan
    Offline
    Sunday, October 31 2010, 01:46 AM - #Permalink
    Resolved
    0 votes
    Got a question.

    Is there any way to control where virtualbox sets up to store its files etc?

    I created my server with an SSD for most of the OS, boot etc and 4 x 1TB drives partitioned for 2 array shares :

    md1 = /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1
    md2 = /dev/sdb2 /dev/sdc2 /dev/sdd2 /dev/sde2

    those shares are for /var/flexshare (thinking now should have made it /var/flexshare/shares) and /home

    Ive just set the drives up to spin down after 60 mins of no activity. If virtualbox runs off /home for a Windows XP VM Ive got in mind with a little web access this isnt conducive to letting the disks idle and spindown.

    The machine is built around an ITX board with Intel Atom CPU, the whole idea is to keep it as low power as possible.

    How might I set up for a single 10GB XP VM running somewhere in one of the other shares that reside on the SSD that is the boot drive (plenty space left, its 64GB)

    Hope this isnt nonsense Im talking :)
    The reply is currently minimized Show
  • Accepted Answer

    Chris_D
    Chris_D
    Offline
    Monday, October 25 2010, 07:48 PM - #Permalink
    Resolved
    0 votes
    For those interested I did exactly as recommended, I copied the .VirtualBox directory from the vbox user to somewhere else.

    Did a "yum remove VirtualBox.i386"
    Killed all Virtual box processes on the box
    And then finally "yum localinstall" with version 3.2.10

    Its worked like a dream and solved a couple of the issues I had been having with screen resolution.
    The reply is currently minimized Show
  • Accepted Answer

    Rohn
    Rohn
    Offline
    Monday, October 25 2010, 05:27 PM - #Permalink
    Resolved
    0 votes
    When I upgraded from 3.1 to 3.2 I backed up all my VMs to a different location & uninstalled 3.1. I'm not sure if you have to uninstall or not, but I did just to be on the safe side. I then installed the 3.x branch & updated the guest additions on all my VMs. Hope this is helpful.
    The reply is currently minimized Show
  • Accepted Answer

    Chris_D
    Chris_D
    Offline
    Monday, October 25 2010, 12:15 PM - #Permalink
    Resolved
    0 votes
    I did as suggested and installed the version 3.0.12 of VBox and it works fine, having issues with minor things but wanted to know how was the best way to upgrade this to 3.2.10?

    Anyone done it and wish to share?

    Thanks

    Chris
    The reply is currently minimized Show
  • Accepted Answer

    Rohn
    Rohn
    Offline
    Tuesday, September 07 2010, 07:49 PM - #Permalink
    Resolved
    0 votes
    Just an FYI, to make it a bit easier to install & update VirtualBox, they provide a repository which works fine with CentOS & has all 3 branches of VirtualBox available 3.0, 3.1, & 3.2. This page talks about it & links to the repo file at the bottom of the page: http://www.virtualbox.org/wiki/Linux_Downloads
    The reply is currently minimized Show
  • Accepted Answer

    Moses
    Moses
    Offline
    Friday, September 03 2010, 09:04 AM - #Permalink
    Resolved
    0 votes
    This will work

    Autostart a VM
    touch /etc/rc.d/start.vbox
    echo '#!/bin/bash' >> start.vbox
    echo "su vbox -c '/usr/bin/VBoxHeadless --startvm WinXP &'" >> start.vbox
    chmod +x /etc/rc.d/start.vbox
    echo '/etc/rc.d/start.vbox' >> /etc/rc.d/rc.local


    I will update the Howto
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, September 02 2010, 11:05 PM - #Permalink
    Resolved
    0 votes
    Ahhh I wonder if the problem is because the command is not telling vboxheadless to start as a background process, and that it is expecting .Virtualbox to be in the home user directory which is actually /root and not /home/vbox. Using the -l flag might help?

    /bin/su -l vbox -c '/usr/bin/VBoxHeadless --startvm myvmname 2>&1 &'


    You can always test this from your own command line first to see (unfortunately I don't access to my VM machines at the mo so I can't test)
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, September 02 2010, 07:27 PM - #Permalink
    Resolved
    0 votes
    guys, I have tried all the above and my VM cannot start automatically on system reboot, anymore ideas ?

    I visited this link
    http://vboxtool.sourceforge.net/


    It reads
    Autostart at host boot. When the host boots, all sessions registered in /etc/vboxtool/machines.conf will be started in the background, issuing a 'vboxtool autostart' command under the named vbox_user in /etc/vboxtool/vboxtool.conf.


    I have no idea how to install vboxtool in Clear OS, can someone please help

    Thank you
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, September 02 2010, 03:17 PM - #Permalink
    Resolved
    0 votes
    Hmm perhaps it should be:-
    /bin/su vbox -c '/usr/bin/VBoxHeadless --startvm myvmname'
    The reply is currently minimized Show
  • Accepted Answer

    Moses
    Moses
    Offline
    Thursday, September 02 2010, 07:27 AM - #Permalink
    Resolved
    0 votes
    Yes, because you are changing user from root to vbox to run the command in quotes
    su vbox -c '/usr/bin/VBoxHeadless --startvm myvmname'



    No, if you are running as user vbox
    su vbox
    /usr/bin/VBoxHeadless --startvm myvmname
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 01 2010, 10:09 PM - #Permalink
    Resolved
    0 votes
    I cant seem to get the VM to run automatically on server reboot or start by editing the /etc/rc.d/rc.local file, do I include the quotes '/usr/bin/VBoxHeadless --startvm WindowsXP'
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 01 2010, 09:54 PM - #Permalink
    Resolved
    0 votes
    Hi - /etc/rc.local is a (symlink) shortcut to the file at /etc/rc.d/rc.local :) they are one and the same
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 01 2010, 09:35 PM - #Permalink
    Resolved
    0 votes
    Tim Burgess wrote:
    I will amend the how to so that it uses yum, then it will pick up the libSDL dependancy, must already be on my system!

    You only need to install the relevant kernel-devel or kernel-PAE-devel rpm, as Carl posted above

    BSOD > To automate startup of a VM you can add the line to /etc/rc.local, but will need to pass user credentials so that it doesn't startup as root. Something like the following will run as user vbox
    su vbox -c '/usr/bin/VBoxHeadless --startvm myvmname'


    I added the above in /etc/rc.d since /etc/rc.local is a shortcut and the VM cant auto start on reboot, what am I missing?

    Thanks
    The reply is currently minimized Show
  • Accepted Answer

    Moses
    Moses
    Offline
    Wednesday, August 11 2010, 07:49 AM - #Permalink
    Resolved
    0 votes
    [vbox@server ~]$ VBoxManage storageattach WinXP --storagectl "IDE Controller" --port 1 --device 0 --type dvddrive --medium none
    The reply is currently minimized Show
  • Accepted Answer

    ernst
    ernst
    Offline
    Tuesday, August 10 2010, 07:30 PM - #Permalink
    Resolved
    0 votes
    Thanks iI have installed XP.
    i have tried to unmount the xp.iso nothing seems to work.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, August 10 2010, 02:42 PM - #Permalink
    Resolved
    0 votes
    Glad you have it running - You need to mount the XP ISO and attach it to the virtual DVD drive

    Steps below for VirtualBox 3.2.x (it differes a bit from the instructions on the first page of this thread for 3.0) Obviously change the path to the location of your XP ISO. You can then start the VM and boot from the ISO, run the install to your virtual hard drive, and then dettach the ISO afterwards
    Attach the .iso to the DVD
    [vbox@server ~]$ VBoxManage storageattach WinXP --storagectl "IDE Controller" --port 1 --device 0 --type dvddrive --medium /var/flexshare/shares/tftp/iso/WinXP.iso


    Refer to the docs for more details
    http://www.virtualbox.org/manual/ch08.html
    The reply is currently minimized Show
  • Accepted Answer

    ernst
    ernst
    Offline
    Tuesday, August 10 2010, 01:31 PM - #Permalink
    Resolved
    0 votes
    I RDP into the pc on the ip of eth1, I only get a blank screen, which tells me "fatal: No bootable medium found! System halted."

    How do I install XP PRO on the virtual pc.
    The reply is currently minimized Show
  • Accepted Answer

    ernst
    ernst
    Offline
    Tuesday, August 10 2010, 01:13 PM - #Permalink
    Resolved
    0 votes
    Thanks the reboot did it.
    I assume when it tells me listening on port 3389 everything went well.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, August 10 2010, 08:21 AM - #Permalink
    Resolved
    0 votes
    Did you check what kernel you are running? using 'uname -r'

    The kernel was upgraded during 5.2 but requires a reboot to get it running
    The reply is currently minimized Show
  • Accepted Answer

    ernst
    ernst
    Offline
    Tuesday, August 10 2010, 08:09 AM - #Permalink
    Resolved
    0 votes
    Package kernel-devel - 2.6.18-194.8.1.v5.i686 is already installed.
    Nothing to do

    This is the response i get after running yum.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, August 10 2010, 07:58 AM - #Permalink
    Resolved
    0 votes
    Hi Ernst you need to have installed the kernel-devel RPM for your running kernel so that it can build the virtualbox driver module

    To check your kernel version run 'uname -r'

    If your running the latest clearos kernel just run (if not you'll need to specify the specific version)
    yum install kernel-devel
    The reply is currently minimized Show
  • Accepted Answer

    ernst
    ernst
    Offline
    Tuesday, August 10 2010, 07:18 AM - #Permalink
    Resolved
    0 votes
    :S When i enter the following command
    yum localinstall -nogpgcheck VirtualBox-3.2-3.2.6_63112-rhel5-1.386.rpm
    i get a message to visit /var/log/vbox-install.log

    "error unable to find the source of your current Linux kernel.Specify KERN_DIR=<directory> and run Make again."

    after that i must run

    /etc/init.d/vboxdrv setup
    what did i miss or skipped
    The reply is currently minimized Show
  • Accepted Answer

    Monday, July 26 2010, 08:04 PM - #Permalink
    Resolved
    0 votes
    Nice! thanks for posting :) yeah it's been a while since i've revisited this howto for newer versions og VirtualBox
    The reply is currently minimized Show
  • Accepted Answer

    Moses
    Moses
    Offline
    Monday, July 26 2010, 06:21 PM - #Permalink
    Resolved
    0 votes
    Hi Tim,

    Maybe you can update the Howto
    Confirm working with the following
    No PAE
    Did not install "Development Tools"
    ClearOS 5.2
    VirtualBox 3.2.6

    Install dependicies
    yum install gcc
    yum install make
    yum install kernel-devel


    Download and install VirtualBox
    wget http://download.virtualbox.org/virtualbox/3.2.6/VirtualBox-3.2-3.2.6_63112_rhel5-1.i386.rpm -C /var/tmp
    yum localinstall --nogpgcheck /var/tmp/VirtualBox-3.2-3.2.6_63112_rhel5-1.i386.rpm


    Create a user "vbox" and add to the "vboxusers" group
    /usr/sbin/useradd -r -m vbox
    /usr/sbin/usermod -a -G vboxusers vbox


    All the following to be executed as user vbox
    su vbox


    Create a Virtual Machine and register it, eg WinXP
    VBoxManage createvm --name WinXP --ostype WindowsXP --register


    Set RAM to 512MB, boot DVD first, bridged connection with the LAN interface
    VBoxManage modifyvm WinXP --memory 512 --acpi on --boot1 dvd --nic1 bridged --bridgeadapter1 eth0


    Create the VM Hard Drive, set to 10GB
    VBoxManage createhd --filename WinXP.vdi --size 10000 --register


    Assign this HD to our VM as the primary HD device hda
    VBoxManage storagectl WinXP --name "IDE Controller" --add ide


    Attach the Virtual.vdi to the HDD
    VBoxManage storageattach WinXP --storagectl "IDE Controller" --port 0 --device 0 --type hdd --medium WinXP.vdi


    Attach the .iso to the DVD
    VBoxManage storageattach WinXP --storagectl "IDE Controller" --port 1 --device 0 --type dvddrive --medium /location/WinXP.iso


    Start the VM
    VBoxHeadless --startvm WinXP &


    Autostart the VM
    touch /etc/rc.d/start.vbox
    echo '#!/bin/bash' >> start.vbox
    echo "su vbox -c '/usr/bin/VBoxHeadless --startvm WinXP &'" >> start.vbox
    chmod +x /etc/rc.d/start.vbox
    echo '/etc/rc.d/start.vbox' >> /etc/rc.d/rc.local


    Detach the .iso
    VBoxManage storageattach WinXP --storagectl "IDE Controller" --port 1 --device 0 --type dvddrive --medium none
    The reply is currently minimized Show
  • Accepted Answer

    Monday, June 07 2010, 07:44 PM - #Permalink
    Resolved
    0 votes
    yeah security should be a priority. Anyways thanks for the great post. I will implement it.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, June 07 2010, 07:24 PM - #Permalink
    Resolved
    0 votes
    Hi, ClearOS does not ship with a full blown X environment so no there is no GUI for webconfig... although I did see on the wishlist a few wishes to create a webconfig VM 'manager' which could potentially use VirtualBox, or I believe it also has a web page management console similar to that of VMware

    If you open up the ports on the incoming webpage you can remote desktop from remote destinations, just be careful with security
    The reply is currently minimized Show
  • Accepted Answer

    Monday, June 07 2010, 06:53 PM - #Permalink
    Resolved
    0 votes
    Thanks Tim,

    I was looking for this type of thing. I want to install a VM that will host my Meta Trader Accounts 24/7. I will be using remote desktop connection from Windows. I hope I will also be able to access my Clear Box and the VM from remote locations.

    I will start working on it right now. Forgive me for asking but I am from Windows and am used to Pretty Icons ;) Can you get a GUI for this via Webconfig?

    Great Work!
    The reply is currently minimized Show
  • Accepted Answer

    stassen
    stassen
    Offline
    Sunday, March 21 2010, 06:48 PM - #Permalink
    Resolved
    0 votes
    Next challenge ;-) Audio.........

    Enabled audio in Vbox. Installed a player in the machine. Driver Intel AC97 driver installed. Mremote sound forwarded to RDP client... Only thing I hear is clicking of the speaker...

    a) Anyone has audio working (and with which rpd client) or
    b) Is this "the" known issue and do I need an upgrade to a newer Vbox version ?
    The reply is currently minimized Show
  • Accepted Answer

    Friday, March 12 2010, 01:29 PM - #Permalink
    Resolved
    0 votes
    Hi Stassen, thats a shame your cpu doesnt support Intel VT...

    http://ark.intel.com/Product.aspx?id=32242

    Im not too sure about the motherboard, but you can find that out easily by entering the bios.

    This will most likely be the cause of your issue.. :(
    The reply is currently minimized Show
  • Accepted Answer

    stassen
    stassen
    Offline
    Thursday, March 11 2010, 04:35 PM - #Permalink
    Resolved
    0 votes
    James Randal wrote:
    may also be a silly question but do you have a HW virtualisation compatible CPU and Motherboard (ie Intel VT) ?, also is HW virtualisation enabled in the BIOS??


    My HW is a shuttle K45. 4GB is in the mail

    Hardware Information
    Processors 2
    Model Intel(R) Core(TM)2 Duo CPU E4600 @ 2.40GHz @ 32°C
    CPU Speed 1.2 GHz
    Cache Size 2.00 MB
    System Bogomips 9612.69
    Currently 2GB.

    To be honest, I do understand your remark, but until you mentioned it, I never had heard of it. Will check.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, March 11 2010, 12:38 PM - #Permalink
    Resolved
    0 votes
    Yes VirtualBox assigns blocks of RAM (as configured) to each host as they are started, therefore you will need at least that much free ram prior to starting the guest. For information on how much is actually available, use 'top' command and subtract the cached amount from the total. Although you are at risk of using swap space which in turn will slow down your host (i.e. ClearOS)

    General rule of thumb is ClearOS will need approx 512MB to run correctly, although is reduced depending on the number of services running on the host. That leaves you with 1.5GB to apportion between your two guest OS.

    http://www.virtualbox.org/manual/ch03.html#settings-motherboard
    http://www.virtualbox.org/manual/ch01.html#gui-createvm

    If you want dynamic allocation of resources, then you'll need to use something much more advanced - I think VMWare possibly?
    http://www.vmware.com/support/esx21/doc/esx21admin_memresourcemanage.html
    The reply is currently minimized Show
  • Accepted Answer

    stassen
    stassen
    Offline
    Thursday, March 11 2010, 12:14 PM - #Permalink
    Resolved
    0 votes
    I'm 100% sure that if a virtual machine takes all memory as configured per machine, I'm running out of memory. Can someone confirm that ?

    I'm currently running on 1.7GB of RAM with Windows2000 active If WindowsXP is additionally started, this will grab (under the conditions above) another 1GB.
    Total configuration memory is only 2GB, so that would explain a lot.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, March 11 2010, 08:06 AM - #Permalink
    Resolved
    0 votes
    may also be a silly question but do you have a HW virtualisation compatible CPU and Motherboard (ie Intel VT) ?, also is HW virtualisation enabled in the BIOS??
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, March 10 2010, 09:47 PM - #Permalink
    Resolved
    0 votes
    This maybe a silly question but do you have enough system resources (i.e RAM) to run both? you also need some spare for ClearOS to run :)
    The reply is currently minimized Show
  • Accepted Answer

    stassen
    stassen
    Offline
    Wednesday, March 10 2010, 08:21 PM - #Permalink
    Resolved
    0 votes
    Thanks for helping me change the port on my config. Your Tip works fine.

    Running in a next problem.....

    Trying to run 2 session parallel. (individual there is no problem)
    Session 1 is Windows2000pro -> port 3398
    Session 2 is WindowsXP -> port 3390

    Using mRemote as a client for these machines

    When both started on a dual core machine (Shuttle K45 mainboard), I do get a 'system freeze'. Even ClarkConnect is not reacting anymore.

    a) Is it possible to run simulations server instances ?
    b) How to debug this ?

    Thanks again in advance
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, March 10 2010, 05:12 PM - #Permalink
    Resolved
    0 votes
    Hi, For one time only:-
    VBoxHeadless startvm myvmname --vrdpport 12345

    For permanent setting
    VBoxManage modifyvm myvmname --vrdpport 12345
    VBoxHeadless startvm myvmname


    More details here :)
    http://www.virtualbox.org/manual/ch08.html#vboxmanage-modifyvm-other
    The reply is currently minimized Show
  • Accepted Answer

    stassen
    stassen
    Offline
    Wednesday, March 10 2010, 04:52 PM - #Permalink
    Resolved
    0 votes
    I want to have a second machine running on a different RPD port. How do I configure this ? Looked in the configfiles, but no luck

    Tip: Use Mremote instead MS RPD client
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, March 07 2010, 06:55 PM - #Permalink
    Resolved
    0 votes
    Yeah sorry the last bit is you need to run the installer inside the Guest OS from the mounted GuestAdditions ISO which will appear as a mounted CDROM :)

    Glad you found it useful!
    The reply is currently minimized Show
  • Accepted Answer

    stassen
    stassen
    Offline
    Sunday, March 07 2010, 06:08 PM - #Permalink
    Resolved
    0 votes
    I use this setup to run a "Windows 2000" Setup. Everything is working fine but I still have the two issues mentioned in this text

    GUEST ADDITIONS
    Now I found that the display and mouse did not correlate very well until I install the guest additions. So....register and attach the guest additons ISO, then boot your VM and run the installer from within the OS
    Code:
    VBoxManage openmedium dvd /usr/share/virtualbox/VBoxGuestAdditions.iso
    VBoxManage modifyvm "ExquiseLab" --dvd /usr/share/virtualbox/VBoxGuestAdditions.iso


    I both executed these commands without errors. Restarting my virtual machine "ExquiseLab" did not help. Do I need to reinstall Windows 2000 ? If not, were can I find the instruction/documentation to solved my double mouse pointer and bad Video display

    Found the solution.... myself ;-)

    Go to -> my computer
    Diskdrive D was mounted with VBoxGuestAdditions -> Run setup & Reboot

    Maybe helpfull for others
    The reply is currently minimized Show
  • Accepted Answer

    stassen
    stassen
    Offline
    Sunday, March 07 2010, 06:01 PM - #Permalink
    Resolved
    0 votes
    I just found the command hidden between my other answer ;-) Thanks for your response
    The reply is currently minimized Show
  • Accepted Answer

    G_K
    G_K
    Offline
    Sunday, March 07 2010, 04:11 PM - #Permalink
    Resolved
    0 votes
    Guest shutdown: On the Host I think you should be able to use
    VBoxManage controlvm <vm_name> acpipowerbutton

    I am planning to incorporate this into the shutdown/reboot sequence, including the case where an APC UPS triggers a shutdown during a longer power-outage. Not yet sure how long a delay may be required to ensure complete shutdown of the Guest before the Host powers down (or reaches a critical run-level (Linux Host) in case of shares being in use).

    Don't know how this code is issued on a non-linux Host.
    The reply is currently minimized Show
  • Accepted Answer

    stassen
    stassen
    Offline
    Sunday, March 07 2010, 04:02 PM - #Permalink
    Resolved
    0 votes
    So far this made my day. Great guide and solution....


    Starting a VM configuration is not an issue, but how should a VM be shutdown correctly ?

    Thanks for the info....
    The reply is currently minimized Show
  • Accepted Answer

    G_K
    G_K
    Offline
    Friday, March 05 2010, 12:56 AM - #Permalink
    Resolved
    0 votes
    Update: ALRIGHT! B) Got something ... of course it breaks something. :ohmy:

    In THIS post linuxguy gives a valuable NewRule suggestion. It works (the one time I tried it so far). When I insert the flash memory stick it no longer shows up under "lsusb", meaning it's invisible to the host (i.e. it is not "claimed"). Using "VBoxManage list usbhost" shows the device as "Busy".

    And it also works the same way with the MagicJack device. But an additional "usbdetach" and "usbattach" is needed for it to "boot" (do its MagicJack thing). Then it trips up ... a third cycle is needed, then you can make phone calls. Yeah ! :woohoo:

    The downside is that this NewRule applies to all USB devices inserted to the host. I need to find a way around this. For now I don't mind that all USB devices become visible to the Guest only, but long term that's no good. May be the filtering mechanism or a more complicated rule will help. And that may fix the multiple attach/detach cycles required. For now I need to take a break on this.
    The reply is currently minimized Show
  • Accepted Answer

    G_K
    G_K
    Offline
    Friday, March 05 2010, 12:18 AM - #Permalink
    Resolved
    0 votes
    Yeah, it is "claimed" (rather than mounted) already by the host, as indicated with the status "Busy" or (in the case of a filtered device) "Unavailable" when doing a "VBoxManage list usbhost". That's one of the issues. But have not yet figured out how to "unclaim" it. (It's not actually auto-mounted like it might be in Ubuntu.)

    I did a COMPLETE re-install (new vm name & vdi) of the WinXP system overnight, then added the GuestAdditions first before activating the USB. And what do you know (but ONE TIME ONLY) I was able to see the flash memory stick in the freshly-installed Guest. But since then ... bupkes! Have tried many other things but will need to stop soon and resume over the weekend.

    Now messing with permissions (devgid and "10-vboxdrv.rules" and "50-udev.rules" in "/etc/udev/rules.d/").

    One of the troubles also is that I am no Linux guru. So much of the web advice that is particular to a specific distribution may not apply to CentOS.

    Thanks for listening and any more hints ...
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, March 04 2010, 01:28 PM - #Permalink
    Resolved
    0 votes
    *D'OH* flood protection deleted my reply,

    Anyhow - looks like you have tried most things - I don't use USB drives here so can't test. The filter concept seems a little complicated!

    One thing I do know you cannot mount the drive on the guest if already in use on the host. You may need to check it's not mounted already?
    The reply is currently minimized Show
  • Accepted Answer

    G_K
    G_K
    Offline
    Thursday, March 04 2010, 07:48 AM - #Permalink
    Resolved
    0 votes
    I have struggled for an entire day trying to get the USB function to work in the WindowsXP guest without success. Much searching the forums and googling. "lsusb" and "VBoxManage list usbhost" show the device (MagicJack) on the host. I've tried USB filters (and of course "--usb on" and "--usbehci on"). I've installed GuestAdditions. The guest, in general, works fairly well, and I've learned to use bridged networking so that the guest has access to the internal network ( I need to switch that later to the external one ), so that way RemoteDesktop is working well.

    I've also played with a usb memory stick (w/o filters, but usbattach instead) ... no success.

    In the guest, under Device Manager, the USB controller shows up (82801FB).

    When I try "VBoxManage controlvm "WindowsXP" usbattach /proc/bus/usb/002/002" while the guest is already up and running I get the error " USB device <XXXXX> with UUID {YYYYY} is being exclusively used by the host computer".

    In frustration I tried unplugging and re-plugging the device; on the host this causes the Device# to change, although it stays on the same bus#.

    SOOO ... any hints (better: full procedural instructions) to get the MagicJack USB device working inside the WinXP guest would be appreciated.

    TIA.
    The reply is currently minimized Show
  • Accepted Answer

    G_K
    G_K
    Offline
    Saturday, February 27 2010, 12:22 AM - #Permalink
    Resolved
    0 votes
    FAST!! reply ! Thanks.

    "uname -a" does not show "PAE" (not that I know what that means ...) ... but you might want to add that hint to the guide.

    AND !! :cheer: the "--nogpgcheck" flag did the trick ... thanks, AGAIN !

    Now I'm ready for the next step ...
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, February 27 2010, 12:18 AM - #Permalink
    Resolved
    0 votes
    To find out what kernel you are running, type 'uname -a' from the command line,

    The other error is because the RPM package isn't signed (or at least the key isn't installed)....use the --nogpgcheck flag to skip this bit
    The reply is currently minimized Show
  • Accepted Answer

    G_K
    G_K
    Offline
    Saturday, February 27 2010, 12:07 AM - #Permalink
    Resolved
    0 votes
    GREAT HowTo ! Thanks.

    One suggestion for newbie: how do I determine which kernel I am running ? (regular or PAE)

    And -- with a fresh install of ClearOS5.1 -- I ran into a problem when executing "yum localinstall Virtual...".
    Total download size: 96 M
    Is this ok [y/N]: y
    Downloading Packages:
    warning: rpmts_HdrFromFdno: Header V4 DSA signature: NOKEY, key ID 6dfbcbae


    Public key for VirtualBox-3.0.12_54655_rhel5-1.i386.rpm?e=1267227605&h=a9d6f71f94533a29522812450ecddb0e


    TIA for any help.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, February 25 2010, 07:10 PM - #Permalink
    Resolved
    0 votes
    VirtualBox is a pretty good solution, however there are a few caveats: it won't automatically start your VMs and it won't automatically save the state at shutdown. Also, support for W7 is still lacking. However the autostart you can solve by employing the following solution:

    http://vboxtool.sourceforge.net/

    Now since you will be running these services headless, you need to be extra cautious when you enable RDS, to add yourself as a remote user.

    Thanks.
    The reply is currently minimized Show
  • Accepted Answer

    BSoD
    BSoD
    Offline
    Tuesday, February 16 2010, 04:57 AM - #Permalink
    Resolved
    0 votes
    su vbox -c '/usr/bin/VBoxHeadless --startvm myvmname'


    Awesome.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, February 15 2010, 01:35 PM - #Permalink
    Resolved
    0 votes
    Thanks! good tip, missed that one
    The reply is currently minimized Show
  • Accepted Answer

    EasyBit
    EasyBit
    Offline
    Monday, February 15 2010, 12:01 AM - #Permalink
    Resolved
    0 votes
    Tim,

    /usr/sbin/useradd -r vbox


    should be

    /usr/sbin/useradd -r -m vbox


    so that a home folder gets created.

    Without the -m option the VM creation did not work as no
    home folder exists.
    The reply is currently minimized Show
  • Accepted Answer

    EasyBit
    EasyBit
    Offline
    Sunday, February 14 2010, 11:30 PM - #Permalink
    Resolved
    0 votes
    Carl

    yum install kernel-PAE-devel


    did the trick as I am indeed using the PAE kernel.

    Thanks.

    Now I need some time to continue along Tim's post.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, February 14 2010, 03:11 PM - #Permalink
    Resolved
    0 votes
    I will amend the how to so that it uses yum, then it will pick up the libSDL dependancy, must already be on my system!

    You only need to install the relevant kernel-devel or kernel-PAE-devel rpm, as Carl posted above

    BSOD > To automate startup of a VM you can add the line to /etc/rc.local, but will need to pass user credentials so that it doesn't startup as root. Something like the following will run as user vbox
    su vbox -c '/usr/bin/VBoxHeadless --startvm myvmname'
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, February 14 2010, 01:19 PM - #Permalink
    Resolved
    0 votes
    I´m using the PAE kernel.
    Are you using the PAE kernel?
    If so run:
    yum install kernel-PAE-devel
    The reply is currently minimized Show
  • Accepted Answer

    EasyBit
    EasyBit
    Offline
    Sunday, February 14 2010, 11:26 AM - #Permalink
    Resolved
    0 votes
    Tony,

    Of course - wrong spelling!

    I got the library installed and got further.
    Now the kernel sources can't be found.

    I will try to get this fixed.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, February 14 2010, 09:12 AM - #Permalink
    Resolved
    0 votes
    Don't you mean "libSDL-1.2.so.0" ? ("l" and "i" reversed)


    [root@via-epia ~]# rpm -q --whatprovides libSDL-1.2.so.0
    SDL-1.2.10-8.el5
    [root@via-epia ~]#


    If so, "yum install SDL" should fix that...
    The reply is currently minimized Show
  • Accepted Answer

    EasyBit
    EasyBit
    Offline
    Sunday, February 14 2010, 08:41 AM - #Permalink
    Resolved
    0 votes
    Great post Tim.

    Unfortunately

    rpm -ivh VirtualBox-3.0.12_54655_rhel5-1.i386.rpm


    fails with dependency:

    ilbSDL-1.2.so.0 is needed by VirtualBox-3.0.12_54655_rhel5-1.i386


    This is on a fresh install of ClearOS 5.1 (all modules and all available updates).
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, February 14 2010, 07:09 AM - #Permalink
    Resolved
    0 votes
    yum install "Development Tools"


    See the first post. It should be yum groupinstall "Development Tools"
    The reply is currently minimized Show
  • Accepted Answer

    BSoD
    BSoD
    Offline
    Sunday, February 14 2010, 05:21 AM - #Permalink
    Resolved
    0 votes
    Hello.

    Im new to ClearOS and VirtualBox. Ive googled around and havent been able to find out how to start a VM on boot of ClearOS. Any ideas?
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, February 13 2010, 12:53 PM - #Permalink
    Resolved
    0 votes
    You can't directly remove the whole group "development tools" but you can remove most of the RPM's it installs

    see the attached thread
    http://www.clearfoundation.com/index.php?option=com_kunena&Itemid=232&func=view&id=712&catid=40#712

    You can safely remove kernel-devel if you wish
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, February 13 2010, 07:56 AM - #Permalink
    Resolved
    0 votes
    Certainly not "Development tools". It will try to uninstall most of your system.

    I've no idea about kernel-devel.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, February 12 2010, 08:27 PM - #Permalink
    Resolved
    0 votes
    Great howto.
    Followed the instructions and now have Virtualbox up and running.
    VMware still crashes for me so finding this was perfect.
    Thanks Tim.

    Question.
    Can one remove the Development tools and kernel-devel.
    Is it safe?

    :)
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, February 04 2010, 08:34 PM - #Permalink
    Resolved
    0 votes
    Sorry my bad, typo. Fixed the post above
    yum groupinstall "Development Tools"
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, February 04 2010, 07:03 PM - #Permalink
    Resolved
    0 votes
    Why this happens ?!
    yum install "Development Tools"
    Loading "protect-packages" plugin
    Loading "kmod" plugin
    Setting up Install Process
    Parsing package install arguments
    No package Development Tools available.
    Nothing to do
    The reply is currently minimized Show
  • Accepted Answer

    Monday, January 18 2010, 03:05 PM - #Permalink
    Resolved
    0 votes
    Ahh ok thanks i'll amend the syntax above, as a general note you can remove the quotation marks for all items that don't include spaces :)

    For information, other permitted OS types are:-
    VBoxManage list ostypes | grep ID
    ID: Other
    ID: Windows31
    ID: Windows95
    ID: Windows98
    ID: WindowsMe
    ID: WindowsNT4
    ID: Windows2000
    ID: WindowsXP
    ID: WindowsXP_64
    ID: Windows2003
    ID: Windows2003_64
    ID: WindowsVista
    ID: WindowsVista_64
    ID: Windows2008
    ID: Windows2008_64
    ID: Windows7
    ID: Windows7_64
    ID: WindowsNT
    ID: Linux22
    ID: Linux24
    ID: Linux24_64
    ID: Linux26
    ID: Linux26_64
    ID: ArchLinux
    ID: ArchLinux_64
    ID: Debian
    ID: Debian_64
    ID: OpenSUSE
    ID: OpenSUSE_64
    ID: Fedora
    ID: Fedora_64
    ID: Gentoo
    ID: Gentoo_64
    ID: Mandriva
    ID: Mandriva_64
    ID: RedHat
    ID: RedHat_64
    ID: Turbolinux
    ID: Ubuntu
    ID: Ubuntu_64
    ID: Xandros
    ID: Xandros_64
    ID: Linux
    ID: Solaris
    ID: Solaris_64
    ID: OpenSolaris
    ID: OpenSolaris_64
    ID: FreeBSD
    ID: FreeBSD_64
    ID: OpenBSD
    ID: OpenBSD_64
    ID: NetBSD
    ID: NetBSD_64
    ID: OS2Warp3
    ID: OS2Warp4
    ID: OS2Warp45
    ID: OS2eCS
    ID: OS2
    ID: DOS
    ID: Netware
    ID: L4
    ID: QNX
    The reply is currently minimized Show
  • Accepted Answer

    Monday, January 18 2010, 02:27 PM - #Permalink
    Resolved
    0 votes
    Thanks for the lightning fast reply! The permissions hint made me realize that the vbox home directory had never existed to begin with. I just created it and now things work fine.

    One small detail though: instead of --ostype=WindowsXP I had to use --ostype "WindowsXP" or else the createvm command would throw an error.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, January 18 2010, 02:09 PM - #Permalink
    Resolved
    0 votes
    Hi Dominik, sounds like one of the files or directories (probably the Machines directory) has the wrong permissions within the /home/vbox/.VirtualBox folder

    You could check with 'ls -lap'. Mine are all owned by the vbox user, and allusers group
    The reply is currently minimized Show
  • Accepted Answer

    Monday, January 18 2010, 02:02 PM - #Permalink
    Resolved
    0 votes
    Many thanks for the instructions, this is exactly what I intend to do if our management lets me kick out the ageing Windows server in order to run the few Windows only services I can't replace with Linux alternatives (such as license servers).

    I have come across a problem trying to create a new VM as the underprivileged "vbox" user. I keep on getting the message "ERROR: failed to initialize COM!". As root I can create a VM without any problem, but I'd rather not. Any idea on how I can solve this?
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, January 07 2010, 07:51 PM - #Permalink
    Resolved
    0 votes
    I don't know if it will be possible to compare both

    This is my virtual OS


    Model AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
    CPU Speed 1 GHz
    Cache Size 512.00 KB
    System Bogomips 2004.84


    this is the ubuntu server


    Model AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
    CPU Speed 1 GHz
    Cache Size 512.00 KB
    System Bogomips 2004.84


    I have a dual core processor, but I'm planning to replace this machine for a Mac Mini (Low power consumption)

    I'm still using 3.04 for now, but will upgrade soon.

    Geert
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, January 07 2010, 07:30 PM - #Permalink
    Resolved
    0 votes
    Hi Geert, yes doing it the other way round is a good idea too. I wonder though which has the smaller footprint as a server OS, Ubuntu or ClearOS without any extra packages?

    Also, which version are you using? 3.1.2
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, January 07 2010, 06:32 PM - #Permalink
    Resolved
    0 votes
    Interesting,

    I run ClearOS as a Virtual Headless on a minimal installed Ubuntu Server.
    Makes a good move for backing up my ClearOs system, even on the fly migrate it to another computer, without rewriting all proper customisations I've done.
    It makes also a separation possible between my internal network and the "public" part.

    Geert
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, January 06 2010, 08:23 AM - #Permalink
    Resolved
    0 votes
    Tim,

    thanks for this howto! will be using this for sure.

    regards,
    Ruud.
    The reply is currently minimized Show
Your Reply