Fedora Core 2 on VMware Workstation 4.5.2

Submitted by keithmo
on July 5, 2004 - 4:17pm

This is a followup to my previous post. Running Fedora Core 2 (final) under VMware Workstation 4.5.2 is a little simpler now. Here are some hints to get it running.

Host Configuration:

  • Unchanged from previous post.

Guest Configuration:

  • Fedora Core 2 (final). Everything else identical to the previous post.

Installation:

  • Booting with "vdso=0" is no longer required.
  • Install as usual.
  • At the first boot, add a "3" to the boot command line to enter runlevel 3 (so you don't waste time waiting for the X server to fail to start).
  • Extract the VMware tools tar archive, cd to the vmware-tools-distrib directory, then execute "patch -Np1 -i vmware-4.5.2-fedora-core2.patch" to tweak the install script.
  • Install VMware tools. Use the defaults for all questions, except say NO when asked if you want to compile a vmhgfs module. It doesn't seem compile with the 2.6 kernel headers.
  • Reboot, and enjoy.

Notes:

  • The notes from the previous post still apply, especially the one about the slowness of FC2. See this entry for some tips on improving FC2 performance under VMware 4.5.2.
  • When booting FC2, if the VM doesn't have focus when the keyboard is initialized, the keyboard not be detected properly. If you try to login and the keyboard is unresponsive, press the left shift key twice. This will cause the kernel to reinitialize the keyboard.

vmware-4.5.2-fedora-core2.patch

diff -ur vmware-tools-distrib-orig/bin/vmware-config-tools.pl vmware-tools-distrib/bin/vmware-config-tools.pl
--- vmware-tools-distrib-orig/bin/vmware-config-tools.pl	2004-06-11 02:52:10.000000000 +0200
+++ vmware-tools-distrib/bin/vmware-config-tools.pl	2004-07-05 20:35:27.084636944 +0200
@@ -2849,7 +2849,7 @@
 }
 
 sub xserver4 {
-  return xserver_bin() . '/XFree86';
+  return xserver_bin() . '/Xorg';
 }
 
 sub xserver3 {
@@ -3052,7 +3052,7 @@
   # string. Maybe it will once it settles down.
   if ($xversionAll eq "0.0.0") {
       $xversionAll = direct_command(shell_string(xserver4()) . ' -version 2>&1') =~
-	  /X.org Foundation/ ? '4.4.0' : '0.0.0';
+	  /X.org Foundation/ ? '4.3.0' : '4.3.0';
   }
 
   # This search order is issued from the XF86Config man page.
@@ -3063,6 +3063,8 @@
            file_name_exist('/usr/X11R6/etc/X11/' . $ENV{'XF86CONFIG'})) {
     $xconfig_path = '/usr/X11R6/etc/X11';
     $xconfig_file_name = $ENV{'XF86CONFIG'};
+  } elsif (file_name_exist($xconfig_path . '/xorg.conf')) {
+    $xconfig_file_name = 'xorg.conf';
   } elsif (file_name_exist($xconfig_path . '/XF86Config-4')) {
     $xconfig_file_name = 'XF86Config-4';
   } elsif (file_name_exist($xconfig_path . '/XF86Config')) {
@@ -3568,6 +3570,7 @@
     if ($major == 4 && $minor >= 2 &&
         file_name_exist($cX4MouseDriverFile)) {
       $line =~ s/%MOUSE_DRIVER%/vmmouse/g;
+      $line =~ s-/dev/mouse-/dev/input/mice-;
     } else {
       $line =~ s/%MOUSE_DRIVER%/mouse/g;
     }

yes, it works ...

Anonymous
on
July 8, 2004 - 3:46pm

Would like to thank you for your notice, the patch works for me (under the conditions: vmware 4.5.2 on xp home, sp1, and fc2 guest). Just wondering, does one dare to take the fedora updates on a working fc2 guest when X issues seem so delicate ...? And why do you get an smp kernel when installing the workstation, is there any deeper meaning behind that? Installing the workstation option on previous distros (without vmware) I didn't recall getting that as a boot option.

Once again, many thanks ...

/Magnus

After much effort I gave up - then I found your BLOG - THANKS!

Anonymous
on
July 8, 2004 - 7:48pm

This worked great for me!!

I had given up on Fedora Core 2 on VMWare 4.5.2 with Windows XP as Host.

Thanks for documenting your successes so others can leverage it.

re: yes, it works ...

on
July 8, 2004 - 10:19pm

FWIW: I've been allowing FC2 to mostly update everything as necessary. The only exception is the kernel -- I run a 2.6.7 kernel with Con Kolivas's scheduler patches. This seems to work well, but the FC2 updater tends to get whiney about my "nonstandard" kernel.

Anyway, I haven't seen FC2 try to update any of the X binaries yet, but I agree - this could get "interesting". Luckly, most of the FC2-on-VMware issues have been with the X11 configuration file. I don't really expect FC2's update mechanism to attempt to update a config file, but I suppose everything is possible.

Installing Fedora Core 2

Anonymous
on
August 27, 2004 - 11:00am

Hi,

I have tried entering 3 on first boot but this didn't work, the 'X server has failed' message still appears. Any ideas?

Thanks

Worked!

Anonymous
on
September 14, 2004 - 7:39am

Worked for me too! Thanx a lot! :)

VMWare Tools and Fedora C2

Anonymous
on
July 9, 2004 - 5:52am

THANKS a million - your patch worked just fine for me.

didn't work 4 me

Anonymous
on
July 13, 2004 - 2:23pm

xp sp2 "rc2" as host FC2 guest. I get (EE) No drivers available. fatal server error no screens found

Works great, thanks!

Anonymous
on
July 18, 2004 - 11:22pm

Thanks a lot for posting this. It helped me get FC2 on VMWare going straight away.

download

on
July 20, 2004 - 9:04am

hi,

Where can i download the patch ?

the patch...

Anonymous
on
September 11, 2004 - 1:30pm

I couldn't find it either, so instead I used the diff results he posts up there to make the changes manually by editing the file with vim. It was like 3 rather easy changes, then I reran the install script and rebooted

Things STILL didn't work, but it resolved everything but my mouse. I went into xorg.xonf and found that it was still using /dev/mouse for some reason and simply changed that to /dev/input/mice and everything worked.

This was a great find for me. Thanks for putting it up here!

Where to get the patch?

Anonymous
on
September 15, 2004 - 5:23pm

Copy and paste into a text file, then copy it to a floppy, and then copy it to the system.

Hope this helps!

Need more clarifying here...

Anonymous
on
July 22, 2004 - 4:46pm

How does one extract the VMware tools tar archive? I'm assuming you are doing this at the Fedora console after the installation. Does this mean that I ignore the 'Install VMware Tools' from the VMware window menubar?

X doesn't start

Anonymous
on
July 23, 2004 - 3:53pm

Hi there. Your information was helpful. I had Fedora Core 2 installed and working on VMware 4.0.5 for Windows. I upgraded to VMware 4.5.2, and now I cannot get X to start properly. It attempts to start, brings up a blank black screen and then returns to the terminal login prompt. It keeps making attempts to start after about 5 seconds.

I ran the patch on vmware-tools-config.pl, even tried to use vdso=0 appended to the boot line, and tried messing with the DefaultDepth or DefaultColorDepth lines and some different resolutions with no success.

Another funny note, is that when Fedora boots, it shows the boot progress in graphic mode, but when done booting it cannot restart X !? Any suggestions

Patch

Anonymous
on
July 23, 2004 - 11:05pm

Sweet. You are the man. Thanks for this patch, I have been scratching my head over this, but your patch worked like a charm!

FC2Final on 4.5.1

Anonymous
on
July 24, 2004 - 12:16pm

I was installing FC2Final on vmware 4.5.1 and found that i had to modify the script as follows:

diff -ur vmware-tools-distrib-orig/bin/vmware-config-tools.pl vmware-tools-distrib/bin/vmware-config-tools.pl
--- vmware-tools-distrib-orig/bin/vmware-config-tools.pl 2004-06-11 02:52:10.000000000 +0200
+++ vmware-tools-distrib/bin/vmware-config-tools.pl 2004-07-05 20:35:27.084636944 +0200
@@ -2788,7 +2788,7 @@
}

sub xserver4 {
- return xserver_bin() . '/XFree86';
+ return xserver_bin() . '/Xorg';
}

sub xserver3 {
@@ -2984,7 +2984,7 @@
my $sub;

$xversionAll = direct_command(shell_string(xserver4()) . ' -version 2>&1') =~
- /XFree86 Version (\d+\.\d+\.?\d*)/ ? $1: '0.0.0';
+ /XFree86 Version (\d+\.\d+\.?\d*)/ ? $1: '4.3.0';

# This search order is issued from the XF86Config man page.
if (defined $ENV{'XF86CONFIG'} && file_name_exist($xconfig_path . '/' .
@@ -2994,6 +2994,8 @@
file_name_exist('/usr/X11R6/etc/X11/' . $ENV{'XF86CONFIG'})) {
$xconfig_path = '/usr/X11R6/etc/X11';
$xconfig_file_name = $ENV{'XF86CONFIG'};
+ } elsif (file_name_exist($xconfig_path . '/xorg.conf')) {
+ $xconfig_file_name = 'xorg.conf';
} elsif (file_name_exist($xconfig_path . '/XF86Config-4')) {
$xconfig_file_name = 'XF86Config-4';
} elsif (file_name_exist($xconfig_path . '/XF86Config')) {
@@ -3501,6 +3503,7 @@
if ($major == 4 && $minor >= 2 &&
file_name_exist($cX4MouseDriverFile)) {
$line =~ s/%MOUSE_DRIVER%/vmmouse/g;
+ $line =~ s-/dev/mouse-/dev/input/mice-;
} else {
$line =~ s/%MOUSE_DRIVER%/mouse/g;
}

Pathc

Anonymous
on
July 25, 2004 - 1:50am

Thanks a MILLION, wish i could have found this sooner, great work.

thanks!

Anonymous
on
July 25, 2004 - 7:01am

i was in a flat panic when i upgraded form fedora core1 to core2 and x would not start. thanks a million for sharing your fix.

need help please

Anonymous
on
July 25, 2004 - 3:52pm

it might seem stupid for me asking this but where can i get the "VMware tools tar archive"
as you might have guessed im fairly new to linux, any help would be GREATLY appreciated

uhhhh

Anonymous
on
July 25, 2004 - 4:39pm

sorry fixed my last problem, stupid me, now i have ANOTHER question
when i type
execute "patch -Np1 -i vmware-4.5.2-fedora-core2.patch"
it gives me an error and says patch doesnt exist (yes im in the right directory)

you have to download the patch first

Anonymous
on
July 30, 2004 - 1:12pm

The patch file is included at the end of the original article above. You need to save it to your machine, then you can run the command.

It works, I love it!

Anonymous
on
August 1, 2004 - 2:20am

It works! I love it! I tried Vmware Tools first without the patch, no go, after the patch ... it seems to warn because you haven't compile vmhgfs thing, but shutdown -r now, and on reboot X is up!!! Thank You Thank You Thank You.

Btw. Fedora Core 2 doesn't seem to work with Vmware version 4.0.0, but it does with the new version 4.5.2-8848. It came right up, where in 4.0.0 I was getting a Kernel Panic on finding the root filesystem.

---
Alan S.

It works for Fedora Core 3 Test 1 as well

Anonymous
on
August 4, 2004 - 2:36am

I installed everything
and can actually compile vmhgfs module without any problem
the kernel is 2.6.7-1.478

How do you compile the vmhgfs

Cagen (not verified)
on
February 8, 2005 - 6:16am

How do you compile the vmhgfs module?

hgfs

Anonymous
on
August 11, 2004 - 2:54pm

I just installed Fedora Core 2 (from a disk picked up at the RedHat booth at OSCON a few weeks ago) using the patch on VMWare 4.5.2 and hgfs compiled and worked for me.

Not for me

Anonymous
on
August 19, 2004 - 7:35am

Hunk #2 at 3052
patch unexpectedly ends in middle of line
Help!Thanks a lot!

I got a similar error: "pa

Anonymous
on
October 24, 2004 - 7:32am

I got a similar error:

"patch unexpectedly ends in middle of line
Hunk #4 succeeded at 3570 with fuzz 1."

This can't be right, can it? So what's the problem with this?

Same to me

Anonymous
on
November 8, 2004 - 12:33pm

what's the solution?

Peter

...also same error occurs!

Anonymous
on
December 5, 2004 - 2:17pm

patch replies with:

patching file bin/vmware-config-tools.pl
Hunk #2 FAILED at 3052.
patch unexpectedly ends in middle of line
Hunk #4 succeeded at 3570 with fuzz 1.
1 out of 4 hunks FAILED -- saving rejects to file bin/vmware-config-tools.pl.rej

could anyone help ?

Many thanks......Chris

Installing Fedora Core 2

Anonymous
on
August 27, 2004 - 11:15am

Hi,

I have tried entering 3 on first boot (well i've tried a few times now), but the 'X server has failed' message still appears. Any ideas?

Thanks

X not working after using procedure above

Anonymous
on
August 29, 2004 - 10:05am

I found I had to modify the pointer section of xorg.conf to make it work. By default vmware set it up to use /dev/mouse, when it really should be /dev/input/mice. Once I made this change everything worked like a charm :)

Compiling/Applying this patch???

Anonymous
on
September 11, 2004 - 5:28am

How exactly do you compile this patch, so that you can apply it? Thanks in advance.

Eric

h00k

Anonymous
on
September 15, 2004 - 5:15pm

Rock Solid! The code patched, up and running! You DA man!!

-h00k

Getting Fedora Core 2 working perfectly on VMWare 4.5.2

Anonymous
on
September 17, 2004 - 7:00am

Getting Fedora Core 2 working perfectly on VMWare Workstation 4.5.2
Keithmo's Blog works for me.
Here are some extra tips:

Create a new Virtual machine with 10GB of hard disk space.
Install Fedora Core 2 as a "Custom" install, but at the Packages Selection screen, scroll down and select "Everything". (Everything allows the compile step in ./vmware-install.pl to actually work later).
Skip Xconfigurator.
For everything else during the install you can use the installation defaults.
Finish the Linux install.
Reboot Linux. Fedora will probably come up in Text mode. If not, boot Linux to text mode.

Under the VMWare window menu, select Snapshot -> Save Snapshot
If any of the steps below fail, revert to this snapshot and try again.

Logon to Linux as root.

To Share files from a Windows partition to Vmware Linux:
First we will list the shares that Linux can see by running:
smbclient -L \\WINDOWSCOMPUTERNAME -U userid
e.g.: smbclient -L \\MYWINPC -U administrator
If you get a list of shares, confirm that C$ is in the list and proceed. If this doesn't work you need to configure Windows to share files and possibly customize your Windows XP firewall. If you can't get this working, don't worry about it - just skip ahead to Install VMWare Tools.
On Linux run the commands below: (replacing the computername and administrator with real names)
Here we are mounting the entire Windows C: drive as /c in Linux.
mkdir /c
smbmount //WINCOMPUTERNAME/c$ /c -o username=administrator
cd /c
ls (you should see a list of Windows C: files)

Install VMware tools:
In the VMWare window menu, choose VM > Install VMware Tools.

Execute all the following commands:
cd /
mount /dev/cdrom /mnt
cp /mnt/vmware-linux-tools.tar.gz /tmp
umount /dev/cdrom
cd /tmp
ls
(You should now see a file in /tmp named: vmware-linux-tools.tar.gz)
tar zxvf vmware-linux-tools.tar.gz
cd /tmp/vmware-tools-distrib

Copy the vmware-4.5.2-fedora-core2.patch
from http://kerneltrap.org/node/view/3408
Save this script to a txt file called:
/tmp/vmware-tools-distrib/vmware-4.5.2-fedora-core2.patch
You can use the Windows sharing instructions above to get the patch from Internet Explorer into Linux. Or, use a CD, a diskette, or a USB memory stick.

Back at the Linux command prompt, run:
patch -Np1 -i vmware-4.5.2-fedora-core2.patch
./vmware-install.pl
(press Enter many times to accept the defaults and choose
a Screen resolution that is one step lower than your Windows XP resolution, e.g. 800x600).
startx

The Linux GUI should start. If not, reboot Linux again using the reboot command.

Make vmware tools run in the correct runlevels, run:
chkconfig --level 345 vmware-tools on

Turn off all unnecessary linux services using:
ntsysv --level 12345
Use the arrow keys and spacebar to deselect all the unnecessary services.
I disabled everything except: (run system-config-services for help)
readahead_early
readahead
xinetd
network
nfslock
syslog
cpuspeed
rhnsd
microcode_ctl
random
kudzu
rpcidmapd
irqbalance
rpcgssd
autofs
cups
xfs
sysstat
atd
netfs
messagebus
crond
anacron
rpcsvcgssd
vmware-tools

Reboot to make sure everything restarts okay.

Other good things to do:
In Gnome select:
Main menu > Preferences > Screensaver, Mode: Disable Screen Saver.
Preferences > Desktop Background, set No Wallpaper and Desktop Colors: Solid Color. Pick a darker blue as the desktop color.

Note: To release the mouse from Linux back to Windows XP, press the following hot key combination:
Ctrl+Alt
Note that you will need to click the mouse pointer once inside the Linux window to activate the mouse within Linux.

The mouse should move freely in and out of the Vmware window now (if not, try rebooting).

Good Luck!
Richard G

Virtual floppy image

Anonymous
on
November 13, 2004 - 4:39am

If you happen to fark up (liek I did) and not install little things like, oh, links, or are unable to access the net (odd, but ok?) A Virtual Floppy is priceless.

But, to be able to add anything onto said "floppy" you have to have a windows pc withing vmware too. (otherwise you can't add data to the floppy and this all ends up being moot :)

Emulating a windows pc within another seems pointless, but oh well.

(..onto trying out a slipstream of sp2.. weeeee..)

spamto:triconda@earthlink.net

Thanks!!!

Anonymous
on
September 23, 2004 - 8:48pm

Great patch...Thanks for posting!

I was a bit shocked to find out that the vmware people have chosen not to support Fedora Core as a standard OS install. Thanks again!

Sweet Patch

Anonymous
on
September 29, 2004 - 12:15pm

Excellent patch, works like a charm and the instructions were great. Cheers

THAKS! I got it to work with

Anonymous
on
October 14, 2004 - 11:23am

THAKS! I got it to work with FC2 as guest under a XP Pro host (without SP2). I had to reply yes to building the hgfs stuff, though.

Please keep up the strong work!

-KLF

fc2...major problem

Anonymous
on
October 20, 2004 - 8:43am

i have successfully installed fc2.
now when i boot the system, i see the dell startup screen and then a blinkig cursor.it blinks for an infinitessimal amt of time.
i cannot do anything ebyond tht.i have installed grub.i do hve a monitor which is not detected,as in it does hve a driver disk.
i use a dell inspiron 7000 with an intel celeron.

somebody explain what to do???

Also works for me

Anonymous
on
October 23, 2004 - 10:27pm

I too would like to say thank you for your patch.
I also have Windows XP SP2, VMWare Workstation 4.5.2 with
Fedora Core 2.
One minor problem, not compiling vmhgfs will prevent shared folders from working. But not a big deal since FC2 has SSHD running be default.
I just use PUTTY's version of sftp. Works great.

The patch worked great here t

Anonymous
on
October 25, 2004 - 12:55pm

The patch worked great here too. I used ifconfig to get the IP Fedora was using then used PuTTy to SSH into the box. I did it this was because I wanted to copy/paste the patch straight from the webpage to a nano window. Tip: use the -w switch on nano so you don't get line wrapping errors.

Those of you who can't find the vmware tools, read the post a few above this one that spell out where they are and how to get to them...or you could read the vmware help file which walks you thru mounting the iso file.

One error and one fatal error

Anonymous
on
October 26, 2004 - 9:45pm

Hi,

Hulk #1 - 3 failed, but 4 updated successfully. I ran the install and followed your instructions. I'm not very good at troubleshooting yet with Linux, because it has been a while. I had one error relating to the XServer's security policy, and one fatal error because the application cannot open mouse because there is no such directory. I checked and found files in /dev/input formice and mouse. I feel like I'm on the cusp of figuring this out.
Originally I thought it was something I did, because I typed the entire segment of code. I didn't find the final thread stating how to do the windows file share. I doubled checked and I copied it verbatim. It just doesn't make sense because the installation GUI allowed me to use the mouse.

Please help,
Jon Van Luik

Just edit /etc/X11/xorg.conf ! No need for VMware-tools

Anonymous
on
October 27, 2004 - 7:37am

Dear friend,

I haven't tried the patch because I simply can't use VMware tools.

One can still fix the X by editing /etc/X11/xorg.conf. Search the line DefaultDepth 16 and change the value to DefaultDepth 24

reference: [http://tinyurl.com/4rqd4] or [http://dotnetjunkies.com/WebLog/demiliani/archive/2004/06/28/17731.aspx]

# use vi (or similar) to edit the X-Server configuration file (/etc/X11/xorg.conf )
# go to the "Screen" section, search the line DefaultDepth 16 and change the value to DefaultDepth 24

Regards,
Fabio Fagundes
Rio de Janeiro - Brazil

fixing X server problem of fedora on vmware

uniquestar (not verified)
on
May 15, 2005 - 6:15am

Thank you a lot, it was very simple and and useful. I editted xorg.conf and my linux gui came up !

Patch error on FC3

Anonymous (not verified)
on
December 13, 2004 - 3:24pm

I'm getting the following error when running the patch;

Patch: **** malformed patch at line 11: sub xserver4 {

I'm running this on Fedora Core 3. Should this patch be OK with FC3?

Cheers
MBS

Patch: **** malformed patch at line 11: sub xserver4 {

j (not verified)
on
December 19, 2004 - 12:18am

I am getting the same error too:

Patch: **** malformed patch at line 11: sub xserver4 {

I running FC2 on vmware4.5.2

Please let me know how to apply this patch

Thank you very much in advance...
J

malformed patch

on
December 19, 2004 - 11:22am

Ensure the patch file is copied exactly from the web page. Pay particular attention to leading spaces. For example, on line 11 (the one the patch command is whining about) there should be exactly one space before "sub xserver4 {".

malformed patch

Anonymous (not verified)
on
December 20, 2004 - 6:36pm

Ok, I'm getting an error on line 11 but it's not the same and I copied it with the right spaces and all:

patch: ****malformed patch at line 11: @@ -3052,7 +3052,7 @@

I vi'd the file and that error is what resolves at line 11. I checked all the spaces and they are correct. Help please.

Hmmm... One other thing to ch

on
December 20, 2004 - 8:35pm

Hmmm... One other thing to check -- make sure the patch file has the proper Unix-style 0x0A line terminators and *not* the DOS/Windows-style 0x0D 0x0A terminators. If you created the patch file under Windows then copied it to your Linux VM, you'll need to run dos2unix on the file before giving it the patch command.

Tried it and that doesn't wor

on
December 21, 2004 - 2:32am

Tried it and that doesn't work either, still get the same error. Any other suggestions?

post patch _file_ somewhere?

Anonymous (not verified)
on
December 30, 2004 - 10:52am

Could someone please post a clean version of this patch file on a web site somewhere and let us know the URL here?

I'm also getting the "malformed patch" result.

Thanks

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.