Hi folks.
Im having some troubles and hopefully someone can advise.
First heres where I'm at.
Ive installed virtualbox as per original guide at http://www.clearfoundation.com/component/option,com_kunena/Itemid,232/catid,40/func,view/id,24611/#24611 but ive made some updates (problem was present originally and still persists).
I have updated virtualbox up to 4.0.4 - note that as of version 4 you have to install the extension pack seperately, Ive installed VirtualBox 4.0.4 Oracle VM VirtualBox Extension Pack
Ive also installed vboxtool 0.4, note that the official vboxtool doesnt cope with command changes in virtualbox somewhere around v3. Theres an unofficial hack that works well.
vboxtool - http://vboxtool.sourceforge.net/
vboxtool hack - http://rankkihovi.rautakanki.net/~sampo/vboxtool/
One thing differs during installing vboxtool, you can follow the official instructions until you get to :
instead for Centos 5 this seems to work for autostarting guest vm's on boot :
Ive set up vboxtool to start my WindowsXP guest with vrdp port 3389 and the vm is bridged to ppp0
In my firewall I already have a link to pc on my network for RDP but I dont want it easily found so I moved it up to port 3390, the Windows XP vm is now set up in the firewall and for port forwarding to allow 3389 and port forward 3389 to 192.168.1.1:3389
Now to my problem.
I cannot achieve communication with my vm via either the wan port dynamic ip or via the domain name I have attributed to my server via dyndns and ddclient (domain works fine as does rdp to pc in lan) - I also tried bridging to eth0 and accessing via lan to vm machine name but that did not work either. "vboxtool show" displays the vm running happily and not overloading the host as I added the alterations to grub config to stop the known fault of guest vms overloading the host on centos due to the kernel timer issue of CentOS.
Any ideas how I can get communication via ppp0?
Incidentally, much the same setup has worked for me elsewhere on a Centos 5.5 x64 webserver but that only had the one eth port and apf firewall.
Im having some troubles and hopefully someone can advise.
First heres where I'm at.
Ive installed virtualbox as per original guide at http://www.clearfoundation.com/component/option,com_kunena/Itemid,232/catid,40/func,view/id,24611/#24611 but ive made some updates (problem was present originally and still persists).
I have updated virtualbox up to 4.0.4 - note that as of version 4 you have to install the extension pack seperately, Ive installed VirtualBox 4.0.4 Oracle VM VirtualBox Extension Pack
cd /var/tmp
wget http://download.virtualbox.org/virtualbox/4.0.4/VirtualBox-4.0-4.0.4_70112_rhel5-1.i386.rpm
yum localinstall --nogpgcheck VirtualBox-4.0-4.0.4_70112_rhel5-1.i386.rpm
wget http://download.virtualbox.org/virtualbox/4.0.4/Oracle_VM_VirtualBox_Extension_Pack-4.0.4-70112.vbox-extpack
VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.0.4-70112.vbox-extpack
Ive also installed vboxtool 0.4, note that the official vboxtool doesnt cope with command changes in virtualbox somewhere around v3. Theres an unofficial hack that works well.
vboxtool - http://vboxtool.sourceforge.net/
vboxtool hack - http://rankkihovi.rautakanki.net/~sampo/vboxtool/
One thing differs during installing vboxtool, you can follow the official instructions until you get to :
* Activate the init script vboxtoolinit:
update-rc.d vboxtoolinit defaults 99 10
instead for Centos 5 this seems to work for autostarting guest vm's on boot :
chkconfig --add vboxtoolinit
chkconfig --levels 2345 vboxtoolinit on
Ive set up vboxtool to start my WindowsXP guest with vrdp port 3389 and the vm is bridged to ppp0
In my firewall I already have a link to pc on my network for RDP but I dont want it easily found so I moved it up to port 3390, the Windows XP vm is now set up in the firewall and for port forwarding to allow 3389 and port forward 3389 to 192.168.1.1:3389
Now to my problem.
I cannot achieve communication with my vm via either the wan port dynamic ip or via the domain name I have attributed to my server via dyndns and ddclient (domain works fine as does rdp to pc in lan) - I also tried bridging to eth0 and accessing via lan to vm machine name but that did not work either. "vboxtool show" displays the vm running happily and not overloading the host as I added the alterations to grub config to stop the known fault of guest vms overloading the host on centos due to the kernel timer issue of CentOS.
Any ideas how I can get communication via ppp0?
Incidentally, much the same setup has worked for me elsewhere on a Centos 5.5 x64 webserver but that only had the one eth port and apf firewall.
Share this post:
Responses (6)
-
Accepted Answer
bah, you spend ages drudging away at these things and no sooner than you give up and ask for help it makes a fool of you.
I modified my vm as I remembered I had to try a couple of options to stop system overload on centos and Id forgotten to add them, so I redid some of the vm options such :
VBoxManage modifyvm "WindowsXP" --memory 256 --acpi on --pae on --nestedpaging off --boot1 dvd --nic1 bridged --bridgeadapter1 ppp0
No sooner than that was done and the machine restarted rdp over ppp0 has come good. I may have to come back and ask some more questions but I'll see how I get on. -
Accepted Answer
I must be tired, wherever it says ppp0 above it should read eth0
Working good now, got XP going nice with RDP from web ok, autostarting on boot nicely with modified vboxtool, internet ok and no sign of it causing undue load on cpu's so result.
In case it helps anyone, the timer issue im referring to is detailed here, I used it just to be on the safe side :
https://www.centos.org/modules/newbb/viewtopic.php?viewmode=flat&topic_id=21969&forum=37
On my Centos 5.5 x64 webserver Im having massive problems with an identical vm XP guest like this one running up massive cpu load until it desabilises the system, it is not proving as simple to get right as doing this on ClearOS has. -
Accepted Answer
-
Accepted Answer
Not yet but I am aware of it, havent really run enough vm's side by side to think it necessary to put the effort into trying it yet. Up until recently I mainly used vbox to run on my laptops to try new os out or run older OS to give access to software thats work related. It would be very nice if vbox and phpvbox were available or integrated with clearos somehow, that would be a major value added feature
Although having said that, I believe Ive read its possible to add in some build in virtualization component to a CentOS server but I dont really know much about that.
I did read about virtualboxphp and perhaps I'm mistaken but isnt it only adviseable to use phpvbox locally atm, its not secure enough for safe web access.
This is just a zotac itx-g-synergy twin core ion 330 HT clocked up to 2 ghz with 4gb of 800mhz ram, its already using softraid 5 with 4 sata2 disks and acting as gateway and firewall, its only dealing with 2 or 3 users but I reckon a couple off small vm's is about all thats adviseable to add to its tasks
It copes admirably though because I used a sata2 SSD for the boot, root and swap partitions B)
If I was building it now itd be one of the new AMD Zacate based setups, but whether they are fully capable with ClearOS yet is a question for another thread. I had some trouble with the nvidia network chip performance on this system until I used the alternative amd driver. Fortunately Im using a usb nic for the wan that behaves itself perfectly. -
Accepted Answer
Hi Tim
I've been reading this thread for a little while now, and am wondering if the solution will dovetail into what ClearOS 6 will be doing. i.e. will the VM's built in this solution work when migration to 6 becomes available? I don't want to create additional work for the customer to pay for. This solution is interesting to me as a solution to run Windows 2008 server. A couple of customers have a need for sql on 2008 and so I hope I could do this and provide consistency going forward.
I would then include your other how to for backup... backuppc but that also brings to mind a question of how to backup the VM's?
I appreciate your and the others efforts, and find this very fascinating . RT. -
Accepted Answer
Been a while since I revisited this.
Having an irritating problem. Sometime ago the setup stopped starting virtual machines on system startup. Everything still works if theyre started manually.
Ive tried repeating the commands including setting the following :
chkconfig --add vboxtoolinit
chkconfig --levels 2345 vboxtoolinit on
But no luck.
any suggestions?
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »