Confirmed users
3,990
edits
ReferencePlatforms/Linux-Public: Difference between revisions
ReferencePlatforms/Linux-Public (view source)
Revision as of 21:51, 16 February 2010
, 16 February 2010→Troubleshooting
mNo edit summary |
|||
| (2 intermediate revisions by one other user not shown) | |||
| Line 34: | Line 34: | ||
= Running under VirtualBox = | = Running under VirtualBox = | ||
* Download the machine image as usual, and decompress it to $img | |||
* Import the $img/CentOS-5.0-ref-tools-vm.vmdk (hereafter "hda") and $img/CentOS-5.0-ref-tools-vm_1.vmdk (hereafter "hdb") disk images into your VirtualBox media manager | |||
* Create a new VirtualBox machine that has the disks "hda" and "hdb", in that order (IDE0 master and slave, respectively) | |||
* Edit the VirtualBox machine config to taste: recommendations include adding more RAM and VRAM. Be sure to restart the VirtualBox master process if you edit a machine config. | |||
* Here we de-VMWare the image. The "big difference" is that VMWare uses virtual SCSI devices while VirtualBox uses virtual IDE devices. | |||
*# su root [ see password below ] | |||
*# cd /etc | |||
*# mv vmware-tools bak.vmware-tools | |||
*# mv fstab bak.fstab | |||
*# cp fstab.BeforeVMWareToolsInstall fstab | |||
*# Append the line | |||
/dev/hdb1 /builds/ ext3 defaults 1 2 | |||
to /etc/fstab, using your favorite text editor. Format to taste. | |||
*# Reboot (it's normal to see errors from VMWare during init, since it was mostly disabled) | |||
*# Your image works ...? | |||
These steps can trigger an fsck of /dev/hdb1. This is useful and fast, let it happen. | |||
If you want a graphical environment, be sure to change your runlevel as described above. When you first reboot into a graphical environment, X will fail to start because the xorg.conf is VMWare-specific. In the error dialogs that appear, choosing the option to let X "repair itself" will result in a usable 800x600 display. | |||
= Troubleshooting = | = Troubleshooting = | ||
| Line 40: | Line 60: | ||
* If vmware tools doesn't install/upgrade correctly, try running vmware-config-tools.pl as root. | * If vmware tools doesn't install/upgrade correctly, try running vmware-config-tools.pl as root. | ||
* Bridged Network does not seem to work when using that image in VMWare Server (1.0x), NAT seems to work fine | * Bridged Network does not seem to work when using that image in VMWare Server (1.0x), NAT seems to work fine | ||
* The /builds partition might not get added properly add this to /etc/fstab: | |||
/dev/sdb1 /builds ext3 defaults 0 0 | |||