Building a SLED10 Dual Boot Workstation with VMware Player

@]

@]

@]

@]

@]

@]

@]

@]

@]

@]

(:title Building a SLED10 Dual Boot Workstation with VMware Player:)

Building a SLED10 Dual Boot Workstation with VMware Player

Why not use XEN?

Benefits of this solution

Problems that need to be overcome

Solution - Step by Step

Start with an Existing Windows Installation

Modify the Windows Installation to use Hardware profiles

Reboot and Install SLED10

Configuring VMware Player

Configure the Dual Boot Virtual Machine

Start the Virtual Machine

Modify the Virtual Machine

VMware Tools

Windows Disk Management

The mechanics of it

dualboot.vmdk

dualboot.vmx

vmware-dualboot

vmware-chmodgrp

dualboot

Other files

References

Referenced Articles

Related Articles

==Building a SLED10 Dual Boot Workstation with VMware Player== The objective of this project is to create a Dual Boot SLED workstation where the second Operating System (most likely Windows XP) can also be run within SLED as a virtual workstation. When companies try to migrate their workstations to SLED they run into a number of problems (both technical and political). However if the end-user were to have the option of “having your cake and eating it too” the migration would be much smoother. Being able to run both Windows and Linux at the same time would solve a nearly all of the technical and political issues surrounding the migration.

==Why not use XEN?== I have chosen VMware Player over XEN for two reasons:

1. One of the best eye-candy features of SLED (XGL) is still buggy when used with XEN.
2. To run Windows (or any non-hypervisor aware OS) special hardware is required. Older workstations will not have the necessary hardware to support it.

==Benefits of this solution==

1. Legacy applications which have not ported to Linux yet can be run in the VMware session. (if not Citrix)
2. Hard-core Windows users can still use Windows, but are exposed to the benefits of Linux!
3. Changes made to the VMware session of Windows are also present in the Physical session. (If chosen during boot.)
4. VMware Player is free!

==Problems that need to be overcome==

1. VMware Player is great if you are running the session as root, problem is that VMware Player has a nasty habit of changing the permissions of the files so normal users can not run it. And if you are in the situation where multiple users access the same workstation (i.e. shift users); forget about it!
2. VMware is unable to bridge wireless connections. The needs of Wireless LANs and Laptop users need to be addressed.
3. Different machines have different disk geometries and types. So we need a solution that is dynamic enough to account for these changes.
4. Since VMware is most likely using a partition from the boot disk it will default to the same GRUB menu presented during system start.
5. I am assuming that the majority of end-users are muppets and no smarter than a trained monkey, so this solution needs to be transparent to them.
6. Administrators needed to trust that Junior Administrators and Helpdesk staff could be able to install and troubleshoot the solution.

==Solution - Step by Step== There are a number of sites on the Internet that explain how to use different Virtualization products to run an OS from a partition rather than an image. However they all lack one thing, simplicity! These solutions are great if you are working on your own workstation, but if this solution is going to be rolled out to a large number of desktops, it is not feasible for the IT staff to spend a great deal of time on each workstation.

I have created a custom RPM to fix all these problems, which can be placed into your network repository and selected when building the SLED workstation. The RPMs (if anyone knows how to upload a RPM file to the wiki, please tell me!! :) ) are available for download and are licensed under GPL.

However there are a couple of points about this solution:

• Not that I want to sound elitist, but the audience this wiki is targeting are the higher level administrators, experienced with Linux, VMware and Windows. (i.e. I am not going to explain how to install SLED10 or Windows)
• The Window Virtual Machine will in a NAT environment. Because of this, some windows applications will not work. In short, if the workstation initiates the connect to a server the application most likely will work. If it is the server that initiates the connection, the application will most likely not work. This was a trade off I made since the environment I made this RPM for was largely wireless, however the RPM could be altered to use a Bridged connection. (I am planning on updating the scripts to allow for this in the future)
• (Temporary) I have the RPMs files and VMware Tools in a zip file but have not yet figured how to post them on the website. If you know or really need the files quickly email me at projects at brandt dot ie

===Start with an Existing Windows Installation=== It has been my experience that the majority of workstations will already have Windows installed. This is either because it is an existing workstation where the user has been using Windows for some time, with all their applications and data already on it. Or it is because a new workstation coming from the factory has already been loaded with the default factory image or a specified corporate image.

If this is the rare situation where the the workstation is blank, build it as you normally would, however I would recommend building the image small since, only loading the programs that are necessary and not found in SLED. Remember, one of the objectives is to allow users to use Windows but slowly show the the benefits of Linux!

If your company uses Ghost (or any of the other multitude of imaging programs) it is possible to just create an empty partition on the drive and continue on. I have found that it is possible to image the partition while in Linux running VMware Player! (I would only do this after you have some experience though)

===Modify the Windows Installation to use Hardware profiles===

The analogy to running Windows natively then running it through VMware is like removing a hard disk with a windows installation from a Dell to into an HP. The visible devices Windows will see will be completely different when running under VMware.

To fix this in Windows we setup different Hardware Profiles. In Windows XP, the location to do this is under "System Properties" | "Hardware" tab | "Hardware Profiles" button.

A dialog will open showing a single existing hardware profile. What I do is rename it to "Physical" and make a copy called "Virtual".

Before your done, make sure that the "Virtual" Hardware Profile is on top (which means it will be the default).

===Reboot and Install SLED10===

There are numerous ways of installing SLED and a near infinite number of ways to configure it. Because of this I will not give you a blow by blow instruction on how to do it, but I will tell you how I do it.

I have a network repository which not only has the SLED10sp1 media, but also mirrors repositories from the internet and has a custom repository (which is where I loaded the RPMs)

I perform the installation by booting the workstation into a PXE boot server and use an AutoYaST script which helps standardize every installation. VMware Player and are automatically selected by the AutoYaST script.

===Configuring VMware Player===

From a command line run the command: <code><pre>

1. vmware-config.pl

</pre></code>

Accept all the defaults. The order of the questions is fairly standard, the only difference is when setting up the Networking Components. Because every workstation is different, it is not practical to script this.

• When asked to bridge a network connection say "yes", and then you only want to bridge ETH0. Most workstations only have one wired ethernet adapter anyway.
• When asked if you want a NAT network connection say "yes". It will then ask you if you want VMware to probe for a free subnet. This is fine if you have a simple IP infrastructure, however I ran into a case where the network was 10.*.*.* based so VMware choose 192.168.1.0. This was fine until I took the laptop to a Internet Cafe.... So from now on I choose 172.254.254.0/24.
• When asked if you want a Host-Only network connection you can say "no". Since we are only running VMware Player, there is no need for Host-Only networking.

A bridged network connection is one that piggybacks on an existing network connection. In this way, VMware allows you to use the physical network connection for both your physical and virtual workstation.

A NAT network connection is a Host-Only connection (A connection that is only visible within the physical machine) but allows NATed communication to the outside world through any available network connection. The physical Operating System is acting like a router between the virtual NAT network and the physical connections.

Although we did setup a bridged network connection, we will only be using the NAT network connection. This is because VMware is unable to bridge Wireless networks.

===Configure the Dual Boot Virtual Machine===

From a command line run the command: <code><pre>

1. vmware-dualboot

</pre></code>

vmware-dualboot is a custom script that modifies the VMware Configuration Files and other scripts. I will automatically search the drives for the Windows Partition and ask you to verify the selections. It will looks something like: <code><pre>

1. vmware-dualboot

Which partition is Windows installed on? [/dev/sda1]:

Windows installed on #1 partition of /dev/sda (/dev/sda1) Adapter Type is scsi Total Sectors = 234441647 Cylinders = 14593 Heads = 255 Sectors = 63

Does this information look correct(y|n)? [n]: y

Modifying /home/vmware/dualboot/dualboot.vmdk `/home/vmware/dualboot/dualboot.vmdk' -> `/home/vmware/dualboot/dualboot.vmdk.orig'

1. Disk Descriptor File

version=1 CID=9c9136a6 parentCID=ffffffff createType="fullDevice"

1. Extent description

RW 63 FLAT "dualboot.mbr" 0 RW 234441584 FLAT "/dev/sda" 63

1. The Disk Data Base
2. DDB

ddb.adapterType = "scsi" ddb.virtualHWVersion = "4" ddb.geometry.sectors = "63" ddb.geometry.heads = "255" ddb.geometry.cylinders = "14593" </pre></code>

===Start the Virtual Machine===

The RPM comes with a custom made Application Icon named "Windows XP" which can be accessed via the Application Browser. You can also run the VMware session by running the command

<code><pre>

1. dualboot

</pre></code>

You might be able to run VMware session by using the command <code><pre>

1. vmplayer /home/vmware/dualboot/dualboot.vmx

</pre></code> Problem is that this does not address the permissions problems which the dualboot command does address.

While the Virtual Machine is booting up, watch to make sure that the correct hardware profile is selected and that there are no errors.

===Modify the Virtual Machine===

Once booted, the machine will start detecting all the new hardware that it sees. You will probably need to reboot the Virtual Machine a couple times.

====VMware Tools====

Once everything comes down, you should install VMware Tools. These drivers are custom made to allow the Virtual Machine to operate smoother and faster. I obtained these tools by creating an ISO of the virtual CD-ROM that is created within VMware Server and Workstation when you select "Install VMware Tools", but since this option is not available within VMware Player, I have created a ZIP file available for download.

====Windows Disk Management====

One problem with the solution is that the Windows VM has access to the entire disk, which of course includes the SLED installation. If a user is smart (i.e. dumb) enough, they could really create a mess!

To limit this possibility, go to the Disk Management applet ("Administrative Tools" | "Computer Management" | "Disk Management"). You should only see a C: drive on the Hard Drive, if there are more drive letters, remove ("Right-Click" | "Change Drive Letter and Paths.." | "Remove" Button)

My theory with users is, "What the monkey doesn't see he won't break"

==The mechanics of it==

===dualboot.vmdk===

The first part of the magic was to figure out how to format the VMware Configuration Files. The dualboot.vmdk file is the file that tells VMware how and where to find its virtual disks, in this case we are telling it to use the first 63 bytes of a file called dualboot.mbr and 64 byte and onward of the /dev/sdc device. Later on we will see how to create the dualboot.mbr file from the MBR of SDC and then how to manipulate it for our needs.

<code><pre>

1. Disk DescriptorFile

version=1 CID=9c9136a6 parentCID=ffffffff createType="fullDevice"

1. Extent description

RW 63 FLAT "dualboot.mbr" 0 RW 2004928 FLAT "/dev/sdc" 63

1. The Disk Data Base
2. DDB

ddb.adapterType = "scsi" ddb.virtualHWVersion = "4" ddb.geometry.sectors = "63" ddb.geometry.heads = "32" ddb.geometry.cylinders = "994" </pre></code>

===dualboot.vmx===

The is the VMware Script that all the VMware products use. As you can see, it references the dualboot.vmdk file above as well specifies the hardware component VMware should expose to the Virtual Machine.

<code><pre>

1. !/usr/bin/vmplayer

config.version = "8" virtualHW.version = "4"

uuid.location = "56 4d 4f b5 b8 76 6f e9-8a a4 70 51 05 0b 3f a8" uuid.bios = "56 4d 4f b5 b8 76 6f e9-8a a4 70 51 05 0b 3f a8"

uuid.action = "create" checkpoint.vmState = ""

displayName = "Dual Boot" annotation = "Created by Bob Brandt (projects@brandt.ie)" guestinfo.vmware.product.long = "" guestinfo.vmware.product.url = ""

guestOS = "winxppro" numvcpus = "1" memsize = "512" paevm = "TRUE" sched.mem.pshare.enable = "TRUE" MemAllowAutoScaleDown = "FALSE"

MemTrimRate = "-1" nvram = "dualboot.nvram" mks.enable3d = "FALSE" vmmouse.present = "FALSE" vmmouse.fileName = "auto detect"

tools.syncTime = "FALSE" tools.remindinstall = "FALSE" isolation.tools.hgfs.disable = "TRUE" isolation.tools.dnd.disable = "FALSE" isolation.tools.copy.enable = "TRUE" isolation.tools.paste.enabled = "TRUE" gui.restricted = "FALSE"

ethernet0.present = "TRUE" ethernet0.connectionType = "NAT"

usb.present = "TRUE" usb.generic.autoconnect = "FALSE"

sound.present = "FALSE" sound.virtualdev = "sb16"

ide0:0.present = "TRUE" ide0:0.fileName = "dualboot.vmdk" ide0:0.mode = "independent-persistent" ide0:0.deviceType = "rawDisk" ide0:0.redo = "" ide0:0.writeThrough = "FALSE" ide0:0.startConnected = "TRUE"

ide1:0.present = "TRUE" ide1:0.fileName = "/dev/cdrom" ide1:0.deviceType = "atapi-cdrom" ide1:0.writeThrough = "FALSE" ide1:0.startConnected = "TRUE"

floppy0.present = "TRUE" floppy0.startConnected = "FALSE" floppy0.autodetect = "TRUE"

serial0.present = "FALSE" serial1.present = "FALSE" parallel0.present = "FALSE"

virtualHW.productCompatibility = "hosted" tools.upgrade.policy = "manual"

priority.grabbed = "normal" priority.ungrabbed = "normal"

snapshot.disabled = "TRUE"

gui.exitOnCLIHLT = "TRUE"

usb.autoConnect.device0 = ""

floppy0.fileName = "/dev/fd0" extendedConfigFile = "dualboot.vmxf" </pre></code>

===vmware-dualboot===

Most of my scripts are pretty well documented (otherwise I woudl have no idea what is going on from one week to the next. But the jist of this script is to modify all the configuration files and the script files with the specific values for the machine it is running on.

• First it figures out which partition the Windows Installation is installed on.
• Then is gets the disk geometry for that disk.
• Using that information, it updates the VMDK file

This next part I am very proud of :)

• The script makes a copy of the exist MBR from the disk that the partition is located on.
• Then it changes the bytes within the file, making the illution that the specified Windows partition is marked active. This way we will not run into the same GRUB menu again and again!
• It saves this new MBR image file as dualboot.mbr (which is what the VMDK file will be looking for)

The before leaving

• The script modifies the sudoers file so that anyone can run the vmware-chmodgrp script as root without entering a password. (Yes I know this might be a security no-no, but the file is read-only and it is a necessary evil)
• The script modifies all of the script files with the proper location of the certian images and programs (just incase they are moved fromt he standard locations)
• Finally the script ensures that the permissions of all the files are correct.

<code><pre>

1. !/bin/bash

2. #
3. vmware-dualboot #
4. #
5. Details: Create custom VMWare Image files. #
6. #
7. This program was created to help administrators customize the vmdk file #
8. used by vmware player. #
9. #
10. Comments can be used but must be preceeded by a hash symbol (#) #
11. All Comments are to be preceded by a hash symbol (#) (Maximum of 78 chars) #
12. #
13. Created by Bob Brandt on 22 May 2007 #
14. Web - http://www.brandt.ie/ #
15. Email - projects@brandt.ie #
16. #
17. Licensed under GPL (just in case anyone askes) #
18. #

vmdkfile="dualboot.vmdk" vmxfile="dualboot.vmx" mbrfile="dualboot.mbr" filepath="/home/vmware/dualboot/" filedepth=`echo "$filepath" | sed 's/[^\/]//g'` filedepth=${#filedepth} filedepth=$((filedepth+1)) version="0.7"

1. Below is the code responsible for producing asking a question #
2. #
3. USAGE: userinput Question DefaultAnswer #
4. #

function userinput {

	echo -e -n "$1 [$2]: "
	read value
	if [ -z "$value" ]; then
		value=$2
	fi
	echo

}

1. Below is the code responsible for modifying the mbr file. This is #
2. necessary so the user will not need to manually select a boot option from #
3. the GRUB menu. If the user were to miss it, they boot the default OS #
4. again. (which is BAD) #

function changebyte {

	let byte=$1
	echo -en $2 | dd conv=notrunc of="$filepath$mbrfile" bs=1 count=1 seek=$byte > /dev/null 2>&1

} function modify_mbr {

	# Copy the existing MBR from the specified device
	dd if=$device of="$filepath$mbrfile" bs=512 count=63 > /dev/null 2>&1

	# Change all the Partition Active Flags to 0x00
	changebyte 0x1BE "\x00"
	changebyte 0x1CE "\x00"
	changebyte 0x1DE "\x00"
	changebyte 0x1EE "\x00"

	# Depending on the partition selected, mark the Partition Active Flag
	#  to 0x80
	case "$partitionnumber" in
		"2" )	changebyte 0x1CE "\x80"	;;
		"3" )	changebyte 0x1DE "\x80"	;;
		"4" )	changebyte 0x1EE "\x80"	;;
		*   )	changebyte 0x1BE "\x80"	;;
	esac

}

1. Below is the code responsible for modifying the vmdk file. #

function modify_vmdk {

	# Make a copy of the old file and create a new file.
	echo "Modifying $filepath$vmdkfile"
	cp -vf "$filepath$vmdkfile" "$filepath$vmdkfile.orig"
	echo -e "# Disk Descriptor File" > $filepath$vmdkfile
	echo -e "version=1" >> $filepath$vmdkfile
	echo -e "CID=9c9136a6" >> $filepath$vmdkfile
	echo -e "parentCID=ffffffff" >> $filepath$vmdkfile
	echo -e "createType=\"fullDevice\"\n" >> $filepath$vmdkfile
	echo -e "# Extent description" >> $filepath$vmdkfile
	echo -e "RW 63 FLAT \"$mbrfile\" 0" >> $filepath$vmdkfile
	echo -e "RW $((totalsectors-63)) FLAT \"$device\" 63\n" >> $filepath$vmdkfile
	echo -e "# The Disk Data Base" >> $filepath$vmdkfile
	echo -e "#DDB\n" >> $filepath$vmdkfile
	echo -e "ddb.adapterType = \"$adaptertype\"" >> $filepath$vmdkfile
	echo -e "ddb.virtualHWVersion = \"4\"" >> $filepath$vmdkfile
	echo -e "ddb.geometry.sectors = \"$sectors\"" >> $filepath$vmdkfile
	echo -e "ddb.geometry.heads = \"$heads\"" >> $filepath$vmdkfile
	echo -e "ddb.geometry.cylinders = \"$cylinders\"\n" >> $filepath$vmdkfile
	# Display the new file to the user.
	cat $filepath$vmdkfile

}

1. Below is the code responsible for modifying the sudoers file which will #
2. allow users to run the permissions script above as root. #

function modify_sudoers {

	# This line will allow all users to run the vmplayer as root without 
	#  entering a password.
	sudoersline="%users ALL= NOPASSWD: $filepath""vmware-chmodgrp, /usr/bin/vmware-chmodgrp"
	temp=`grep "^$sudoersline" /etc/sudoers`
	if [ -z "$temp" ]; then
		# We need to change the mod of the file so we can right to it.
		chmod 0666 /etc/sudoers
		echo -e "\n$sudoersline" >> /etc/sudoers
	fi
	# But before we leave we need to change the mod back to 0440.  If we 
	#  don't sudo won't work.
	chmod 0440 /etc/sudoers

}

1. Below is the code responsible for modifying the script that changes the #
2. permissions of the different files. #

function modify_vmware-chmodgrp_script {

	filename="$filepath"vmware-chmodgrp
	searchtext="^filepath=\".*\""
	replacetext="filepath=\"$filepath\""
	sed 's~'"$searchtext"'~'"$replacetext"'~g' "$filename" > "$filename".temp
	mv -f "$filename".temp "$filename"

	searchtext="^device=\".*\""
	replacetext="device=\"$device\""
	sed 's~'"$searchtext"'~'"$replacetext"'~g' "$filename" > "$filename".temp
	mv -f "$filename".temp "$filename"

}

1. Below is the code responsible for modifying the script that changes the #
2. permissions of the different files. #

function modify_dualboot_script {

	filename="$filepath"dualboot
	searchtext="^vmplayer .*"
	replacetext="vmplayer $filepath$vmxfile"
	sed 's~'"$searchtext"'~'"$replacetext"'~g' "$filename" > "$filename".temp
	mv -f "$filename".temp "$filename"

}

1. Below is the code responsible for verifing that the values are correct. #

function verify_values {

	# Get the total number of sectors on the specified device.
	temp=`parted $device unit s print | grep "Disk geometry for $device" | cut -d " " -f 7`
	totalsectors=`echo $temp | cut -d "s" -f 1`

	# Get the cylinder, head and sector information from the specified 
	#  device.
	temp=`parted $device unit cyl print | grep "BIOS cylinder,head,sector geometry:" | cut -d " " -f 4 | cut -d "." -f 1`
	cylinders=`echo $temp | cut -d "," -f 1`
	heads=`echo $temp | cut -d "," -f 2`
	sectors=`echo $temp | cut -d "," -f 3`

	# Figure out if the device is a SCSI, SATA or IDE device
	if [ -z "`echo $device | sed 's/^\/dev\/hd.*//'`" ]; then
		adaptertype="ide"
	else
		adaptertype="scsi"
	fi

	# From the Windows Partition variable, determine what the partition 
	#  number is.
	partitionnumber=`echo $windowspartition | sed 's/\/dev\/[h|s]da//'`

	# Display the information to the user so he can verify it.
	echo -e "\n\n\n\n"
	echo "Windows installed on #$partitionnumber partition of $device ($windowspartition)"
	echo "Adapter Type is $adaptertype"
	echo "Total Sectors = $totalsectors"
	echo "Cylinders     = $cylinders"
	echo "Heads         = $heads"
	echo "Sectors       = $sectors"
	userinput "\nDoes this information look correct(y|n)?" "n"
	if [ "$value" = "n" ]; then
		exit 1
	fi

}

1. Below is the code responsible for modifying the vmdk file. #

function execute {

	modify_mbr
	modify_vmdk
	modify_sudoers
	modify_vmware-chmodgrp_script
	modify_dualboot_script


	parentpath=`echo "$filepath" | sed 's|[^/]*/$||'`

	# The permissions of the device need to be set in order for non-roots to be 
	#  able to run the VM.
	chmod -R 666 "$device"

	# The permissions need to be changed on the files themselves to allow different 
	#  users to be able run the VM. I may have gone overboard, but tough!
	chgrp -R users "$parentpath"
	chmod -R 7777 "$parentpath"
	chmod -R 666 "$filepath"*
	chmod 555 "$filepath"dualboot "$filepath"vmware-chmodgrp "$filepath"vmware-dualboot

}

1. Below is the code responsible for displaying the help screen. #

function display_help {

	echo -e "\n    ${0##*/} [Optional Options]\n"
	echo -e "    Optional Options:"
	echo -e "     -p, --partition = the partition windows is installed on."
	echo -e "     -h, --help      = show this help."
	echo -e "     -v, --version   = output version.\n"
	exit 0

}

1. Below is the code responsible for displaying the version screen. #

function display_version {

	echo -e "\nGNU ${0##*/} $version\n"
	echo -e "This program is distributed in the hope that it will be useful,"
	echo -e "but WITHOUT ANY WARRANTY; without even the implied warranty of"
	echo -e "MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the"
	echo -e "GNU General Public License for more details.\n"
	echo -e "Originally written by Bob Brandt <projects@brandt.ie>.\n"
	exit 0

}

1. Everything below is the main code of the script, which processes the #
2. parameters and runs the functions above. #

windowspartition=

1. Process all the parameters. Since we do not know what order the parameters
2. will be given, we need to process all the parameters before we act upon
3. them.

while [ "$1" != "" ]; do

	case "$1" in
		"-p" | "--partition" )
			shift
			windowspartition="$1"
		;;
		"-m" | "--mbr-file" )
			shift
			mbrfile="$1"
		;;
		"/?" | "/h" | "-?" | "-h" | "--help" )
			display_help
			exit 0
		;;
		"/v" | "-v" | "--version" )
			display_version
			exit 0
		;;
		* )
			echo "Options Error: option $1 not recognized."
			display_help
			exit 1
		;;
	esac
	shift

done

1. Before anything is done, be sure to verify that the user is root.

if [ "`id -u`" != "0" ]; then

	echo "You must be root to run this script" 2>&1
	exit 1

fi

1. Also make sure that the vmdk file is present and writeable.

if [ ! -w "$filepath$vmdkfile" ]; then

	echo "$filepath$vmdkfile is not present or writeable" 2>&1
	exit 1

fi

1. If not specified, retrieve the windows partition from the user.

if [ -z "$windowspartition" ]; then

	windowspartition=`fdisk -l 2>/dev/null | awk '/(HPFS|NTFS|FAT|W95)/{print $1}' | head -n 1`
	userinput "Which partition is Windows installed on?" "$windowspartition"
	windowspartition=`echo $value | awk '/^\/dev\/[s|h]d[a-z][0-9]*/'`

fi if [ -z "$windowspartition" ]; then

	echo "$value is not in a valid partition syntax. Try again" 2>&1
	exit 1	

fi

1. Also specify the device based on the partition.

device=`echo $windowspartition | sed 's/[0-9]*$//'` if [ -z "`fdisk -l 2>/dev/null | grep $device`" ]; then

	echo "$windowspartition is not on a valid device. Try again" 2>&1
	exit 1

fi

1. Now that we have verified that all the parameters are correct, modify the
2. vmdk file.

verify_values && execute exit 0 </pre></code>

===vmware-chmodgrp===

The vmware-chmodgrp script is very basic. All it does is make sure that the necessary permissions are set on all the necessary files and scripts. Again the file is well documented.

<code><pre>

1. !/bin/bash

2. #
3. vmware-chmodgrp #
4. #
5. Details: Change the group membership and mod of the VMWare Image files. #
6. #
7. There is an ongoing issue with VMWare Player changing the permissions of #
8. the relevent files so non-root users are unable to run image. this script #
9. makes sure that the relevent files have the correct permissions for a #
10. non-root user to run the Dualboot image from disk. #
11. #
12. Comments can be used but must be preceeded by a hash symbol (#) #
13. All Comments are to be preceded by a hash symbol (#) (Maximum of 78 chars) #
14. #
15. Created by Bob Brandt on 22 May 2007 #
16. Web - http://www.brandt.ie/ #
17. Email - projects@brandt.ie #
18. #
19. Licensed under GPL (just in case anyone askes) #
20. #
21. These variables will be modified by the vmware-dualboot script

filepath="/home/vmware/dualboot/" device="/dev/sda"

1. Before anything is done, be sure to verify that the user is root.

if [ "`id -u`" != "0" ]; then

	echo "You must be root to run this script" 2>&1
	exit 1

fi

1. Below is the code responsible for modifying the permissions of the #
2. different files. #

parentpath=`echo "$filepath" | sed 's|[^/]*/$||'`

1. The permissions of the device need to be set in order for non-roots to be
2. able to run the VM.

chmod -R 666 "$device"

1. The permissions need to be changed on the files themselves to allow different
2. users to be able run the VM. I may have gone overboard, but tough!

chgrp -R users "$parentpath" chmod -R 7777 "$parentpath" chmod -R 666 "$filepath"* chmod 555 "$filepath"dualboot "$filepath"vmware-chmodgrp "$filepath"vmware-dualboot

exit 0 </pre></code>

===dualboot===

The dulboot script is also very basic. All it does is launch the vmware-chmodgrp script using sudo, then it launches the vmplayer with the specified VMX file so the user is asked for absolutely NO imput whatsoever!

<code><pre>

1. !/bin/bash

2. #
3. dualboot #
4. #
5. Details: Launch a VMWare Player Dualboot VM Image #
6. #
7. All Comments are to be preceded by a hash symbol (#) #
8. Because of screen width limits, comments should be a Maximum of 78 chars #
9. #
10. #
11. Created by Bob Brandt on 22 May 2007 #
12. Web - http://www.brandt.ie/ #
13. Email - projects@brandt.ie #
14. #
15. Licensed under GPL (just in case anyone askes) #
16. #
17. Modify the permissions on the files since VMWare has a habit of changing
18. them so they only work with root

sudo /usr/bin/vmware-chmodgrp

1. Run the VMWare Image

vmplayer /path/to/vmware/file.vmx

exit 0 </pre></code>

===Other files===

Other than the files above, the RPM installes

• Icon files
• Application Desktop Icons
• Symbolic links

==References== ===Referenced Articles=== http://www.advicesource.org/ubuntu/Run_Existing_Windows_Instalation_On_Ubuntu_With_Vmware_player.html ===Related Articles=== http://www.novell.com/coolsolutions/appnote/19835.html

http://www.novell.com/coolsolutions/feature/19711.html

===Contact or Questions===

I created a Wiki page rather than a standard Cool Solutions feature/appnote because I am hoping others will will add their two cents. By if you want you can contact me at projects at brandt dot ie