Confirmed users
699
edits
mNo edit summary |
|||
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. | |||
= Troubleshooting = | = Troubleshooting = |