NOTE -- I've added a new blog entry detailing the steps necessary to run Fedora Core 2 (final) under VMware Workstation 4.5.2
After a bit of tweaking this evening, I got Fedora Core 2 Test 3 running under VMware 4.5.1. Here's how.
Host Configuration:
Guest VM Configuration:
Installation
Notes:
vmware-fc2t3.patch:
--- vmware-config-tools.pl.before 2004-05-11 19:51:19.608817712 +0200
+++ vmware-config-tools.pl 2004-05-11 20:55:42.508567688 +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')) {
@@ -3146,6 +3148,18 @@
$xversionAll);
}
+sub fix_gpm_file {
+ my $gpm_file = '/etc/sysconfig/gpm';
+ if (file_name_exist($gpm_file)) {
+ my %p;
+ undef %p;
+ backup_file_to_restore($gpm_file, 'GPM_FILE');
+ print "Fixing " . $gpm_file . "\n";
+ $p{'^MOUSETYPE="exps2"$'} = 'MOUSETYPE="ms"';
+ internal_sed($gpm_file . $cBackupExtension, $gpm_file, 0, \%p);
+ }
+}
+
sub fix_mouse_file {
my $mouse_file = '/etc/sysconfig/mouse';
#
@@ -3179,6 +3193,8 @@
}
}
}
+ system('touch ' . $mouse_file);
+ fix_gpm_file();
return $enableXImps2;
}
@@ -3499,6 +3515,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;
}
| types of kernel | 1 hour ago | Linux kernel |
| magical mounts | 17 hours ago | Linux kernel |
| Problem in scim in Fedora 9 | 18 hours ago | Linux general |
| The new Western Digital power saving drives | 18 hours ago | Hardware |
| Battery Maximizer Software | 1 day ago | Linux kernel |
| windows folder creation surprise | 1 day ago | Windows |
| Firewall | 2 days ago | OpenBSD |
| IP layer send packet | 2 days ago | Linux kernel |
| dtrace for linux available | 3 days ago | Linux kernel |
| Unable to mount ramdisk image using UBoot while upgrading to 2.6.15 kernel for a MPC8540 based target | 3 days ago | Linux kernel |
thank`s
saw the post to me on lwn.net, as you say: "I've never seen this with other guest OS's, only FC2T3". and that goes for alot in this distro
VMware 4.0 - Fedora Core 1 and Windows XP on Laptop
Hello All:
Just thought I give my 2cents. I am running Windows XP on a Toshiba satellite 1415-s173 laptop with a 30 GB hard drive and 512 ram. I have installed VMware 4.0 on the host XP System and loaded Fedora Core Linux 1 and Windows XP on this laptop. Both Fedora and XP are running just fine in addition I have loaded security tools on Fedora Core (Nmap, Nikto, iptables, Nessus, ethereal) all are running just fine.
In addition, prior to doing this vmware install my laptop was a duel booting system between XP and Linux 9. I have not upgraded Redhat 9 other the other partition to Fedora Core yet. I just might not upgrade it but keep it just for comparisons or for using it in a situation where I feel it will run more efficiently.
If someone duplicates this installation be careful about allocation of Ram. Fedora is real ram intensive surprisingly XP is a little better.
Blank Screen After Patch Command
I'm trying to get the patch to work, but seem to be running into a problem. I've successfully installed VMWare tools and followed all the instructions that were posted throughout this post. When I try to apply the patch, I get a blank line that doesn't do anything. I've verified that all the files are in the current directory. The command I run is:
patch -p0 vmware-config-tools.pl > vmware_patch.patch (the file I copied from above)
Any help is appreciated.
You guys ROCK
Thanks a lot for the info on getting Fedora up and running on VMWare 4.5. I would have never been able to figure this out on my own.
It's working great now!!!
Core 2
This patch did it for me on the final core 2 release as well.
Many thanks.
Yeti.
It works
Yup with latest vmware (4.5.1)
on xp the patch works great
Thanks alot
!!!
Hmmm.....
It seems a bit odd that someone would be running linux on top of windows.....I can understand why it's so slow (see as how windows is such a clumsy, unstable OS)
JimQ
In fact, Fedora Core 1 runs very well on Windows XP. I use it a lot, and dont find either OS to be "clumsy" or "unstable"
The post that you are replying to was referring to the fact the Fedora Core 2 runs a lot slower that Fedora Core 1 as a guest OS.
I think that you are the only person in this thread who finds running such a configuration to be "odd". I dont think that carte blanche Microsoft bashing is going to do you any favours in this thread. Maybe you shoudl try slashdot?
Stability
Yes, Windows XP is very stable - for the first 3 months.
Then, format and reinstall, and have a happy OS again.
Repeat ad libitum...
re: Stability
FWIW: My Toshiba laptop is about 2 years old. It came with XP Home, which I quickly replaced with XP Pro. I have not had to reinstall since. The system is very reliable. The only thing adversely affecting my "up time" is the occassional BSOD caused by the drivers that I am writing.
Of course, your mileage may vary...
Works nice here too for Fedor
Works nice here too for Fedora Core 2 Final, though it is indeed a lot slower than the Core 1 release.
Running it on VMWare 4.5.1 build 7568, full screen 1600x1200 with an AMD Athlon Thunderbird 1.4Ghz on Windows 2000 Professional with 512 MB DDR333.
Thanks!
VMware patch for FC2T3
I need some help !!!
What command do I use to apply vmware-fc2t3 to vmware-configtools.pl ?
Thanks.
patch command
patch -p0 vmware-configtools.pl <vmware-fc2t3
error installing patch
I guess I'm special.
patch gives me an error message
"hunk #2 FAILED at 2984.
patch: **** malformed patch at line 29: @@ -3146,6 +3148,18 @@"
Also, the vmhgfs module failed to compile.
Worked great on my system...many, many Thanks!
I just copied the text into notepad, saved it into my ftp directory and ftp'd it directly into the /tmp directory and applied it. Everything booted perfectly the first time I rebooted! Great work! I also notice that the speed of FC2 is much slower than FC1. I'm running XP Professional on a 1.8 Ghz P4 with 1.5 GB RAM and allocating 512MB to Vmware 4.51. I have my X Windows set to 1024x768. One observation...X Windows running through the Vncserver and using the VNC client on the same windows machine that is hosting Vmware is much more responsive than the native X Windows client on the Fedora OS inside Vmware.
Can I get some help with this patch? lol
I am totally new to Linux and decided to start with Fedora.
I am in the same situation...WinXP host, VMware 4.5.1. Installation of Fed Core 2 was a nightmare. I got through it but I am still getting XKB configuration errors among other problems.
I want to try a new install and using this patch.
Can someone please tell me step by step exactly how to create the patch and how to install it?
My Fed is already up and running on one VM...can I just run the patch from a terminal window once I learn how to create it, etc. to get rid of my current problems or does it have to be done from a fresh install?
Many thanks....
Brian - NJ
re: error installing patch
I had a similar error in hunk #2 but I'm not sure that it was the same error you saw (I am a raw newbie when it comes to 'patch'). I just changed the '0.0.0' to a '4.3.0' manually in vmware-config-tools.pl, and everything seemed to work fine.
The section was at about line 3049 in the file.
$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';
I had the same problem at hun
I had the same problem at hunk 2 and that solved it for me too. Thanks a bunch!
-fitz
I added vdso=0 and still get a kernel panic
I get:
-- any suggestions?
Richard
upgrade ur vmware to 4.5.1 fi
upgrade ur vmware to 4.5.1 first :D
I get this on 4.52 too
Installed the patch ok - hand editing the file was simpler.
But I get the cannot allocate resource region 4 of device 0000:00:07.1 too.
Everythings runs ok but it bugs me. I've Googled but got to this page so if anyone knows about it it would help folks out when they Google it too ;)
Error at line 16: 2>&1') =~
patch: **** malformed patch at line 16: 2>&1') =~
I tried this patch and it worked for me the first time, but the next couple of tries on NEW VM machines I get this patch error message.
Any ideas or solutions?
way too slow !!
Hello all,
Thanks for the nice blog. I just installed FC2 (final) and used vdso=0 at install time and boot time as stated in the official release notes (it was no secret) and here. I have *not* installed vmware tools as i didnt add any X support; i'm using it in console only (text mode).
Does anyone experience a huge slowdown from all other distros? It seems like it pauses for about 1-2 seconds after you hit enter on any command, even on " --help". Am I the only one experiencing this? Could it be the scsi drives in vmware? anyone installed with ide and working ok?
Thanks for any reply.
Cheers,
Bogdan
Fedora Core 2 final on VMware GSX 3.0
I successfully completed this install, using some tips here, and some guesses and trial/error.
I don't know the best place to post this to help others, but if somebody else has ideas on re-posting it, feel free. I suppose it would be nice if my name stayed on the notes, but I'm not going to stress over it.
Harold Kraus
-------------------
To install the VMware Tools:
From VMware:
"Help, User's Manual..."
Using VMware Tools
Installing VMware Tools
Installing VMware Tools in a Linux or FreeBSD machine
--------------------
--------------------
Install Fedora Core 2 under VMware GSX Server.
During the Fedora graphical install, select "Generic LCD, 1024x768".
Click reboot, but power off during BIOS screen.
Set the VM to independent, non-persistent (if you want to test).
Make sure the VM has focus during boot, or the keyboard may not work in the VM.
For a single-CPU machine (uniprocessor):
Choose the "Fedora Core-up" entry (the smp is for symmetric-multi-processor).
Run kudzu when asked by hitting any key.
Login as root.
-------------------
In VMware main window: go to menu - "VM, Install VMware Tools".
--> run install sequence (use Help, Manual, VMware Tools instructions):
mount /dev/cdrom /mnt
cd /tmp
tar zxf /mnt/vmware-linux-tools.tar.gz
umount /mnt
--> now run the install:
cd vmware-tools-distrib
./vmware-install.pl
--> just hit "Enter" for all questions (8 times), until it asks about running:
"/usr/bin/vmware-config-tools.pl", then say "no".
(the text in the brackets [] are the default answers if you hit "Enter")
--> solution from the kerneltrap.org blog:
Copy and past the solution script from http://kerneltrap.org/node/view/3097
Save it in a plaintext file named anything (here I used vmware-fc2t3.patch).
Burn it on a CDROM.
Insert the CDROM with the script update.
In VMware main window: go to menu - "VM, Install VMware Tools". Then "Cancel".
mount /dev/cdrom /mnt
cp /mnt/vmware-fc2t3.patch /usr/bin
umount /mnt
cd /usr/bin
patch -p0 vmware-config-tools.pl < vmware-fc2t3.patch
--> end of solution
vmware-config-tools.pl
(when asked about vmhgfs module build, say "no", for next question press "Enter")
exit (then login as different user, or just go to next command if root is OK)
startx
--> after X is started:
Go to Start button (RedHat), "System Tools, Terminal", launch the VMware Tools in background:
vmware-toolbox &
--> Note: You can run VMware Tools as root or as a normal user. To shrink virtual disks, you
must run VMware Tools as root (su -).
------------------------------
------------------------------
To have VMware Tools start automatically:
For example, in a Red Hat Linux 7.1 guest using GNOME, follow these steps.
Note by HKraus: this doesn't work under Fedora Core 2. Couldn't find the applet to configure
sessions, just command-line info under Help.
------------
Open the Startup Programs panel in the GNOME Control Center.
Main Menu (click the foot icon in the lower left corner of the screen) > Programs > Settings >
Session > Startup Programs
Click Add.
In the Startup Command field, enter vmware-toolbox.
Click OK, click OK again, then close the GNOME Control Center.
The next time you start X, VMware Tools starts automatically.
Use vmware-tools kernel service
Thanks for the excellent information and I was able to install FC2 on a Windows XP host.
The installation script also creates a VMWare Tools service in /etc/init.d/vmware-tools. You can enable it either via System Settings > Server Settings > Services, or use sysntv commnad in terminal mode, or manually edit the entries in /etc/rc.d.
I believe this is a better approach as it solves the clock synchronization problem with the host operating system after power on or resume.
It also helps to disable smartd S.M.A.R.T. monitor service while changing the service configuration. The service always fails with VMWare GSX 3.0 no matter how /etc/smartd.conf is configured.
Cheers,
Calvin
Thanks all of you
As a real noob in setting up X on lnx machines it is anyway nice too look at. I always used textmode lnx hosts mostly as dedicated gaming servers and it is a quite powerful serverplatform.
Now i were curious on Feodora and wanted to look at graphical interfaces ( something should have been improved over the time ) but in a careful way Vm-ware wer just the way doing it i thought....
Got stuck in the VM-djungle, nothing to do with Feodora, hm..
But then you guys helped me throu this blog. Thanks again.
The patch script together with the 3049 hunk tip mad me go live.
Never seen this forum earlier but i will be a freakwently visitor from now on.
Thanks.
/IceDizzy
I have a problem in my notebook
I have a Aspire 2023WLMI and windows XP sp2 and VMware workstation 4.5.2.
After installation the Fedora core 2, the OS don't detect screen, and go to stop in localhost. In the configure of fedora i had select the generic lcd 1024*768. My resolution in XP (1280*800), but i think, this not disturb.
Sory my english, i have portugueses and not speak very english.
Thanks.
how is change windows start batn
how is change windows start batn pleas reaply emidetly.I am wating for you.
VMWare Patch Error
Great Article!!
But I hit an error after applying the patch.
# patch unexpectedly ends in middle of line.
# Hunk #6 succeeded at 3499 with fuzz 1.
What does the above means? Anyone?
Update from Core 1 to Core 2
The steps for upgrading from core 1 to core 2 refer following URL.
http://linux.duke.edu/%7Eskvidal/misc/fc1-fc2-yum-hints.txt
After upgarding with the instructions, xorg.conf file will not be created in /etc/X11 directory. So, you should do symbolic link xorg.conf file to XF86Free-4. ex) ln -s /etc/X11/XF86Free-4 /etc/X11/xorg.conf.
Run the patch for vmware-config-tool.pl and run vmware install script.
Good luck
Why am I not getting this?
I keep getting
'Hunk #1 FAILED at 2788.
Hunk #2 FAILED at 2984.
Hunk #3 FAILED at 2994.
Hunk #4 succeeded at 3234 with fuzz 1 (offset 86 lines).
Hunk #5 FAILED at 3279.
Hunk #6 FAILED at 3601.
5 out of 6 hunks FAILED'
I followed the directions accordingly, what am I missing?
Thank's
Mine does not require "vdso=0" to install and run the FC2 (tettnang), however the patch is important to bring the X server running correctly. And the speed isn't very slow and acceptable to me.
I'm not sure whether related to my hardware (Athlon XP).
What if...
What if I didn't see the part about the vdso=0 and I've already installed FC2 on VMWare latest version and now I'm getting this:
Uncompressing Linux... Ok, booting the kernel.
PCI: Cannot allocate resource region 4 of device 0000:00:07.1
audit(1086963632.4294967195:): initialized
(running in test mode)
(running in test mode)
Red Hat nash version 3.5.22 starting
Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
I have not installed VMware Tools because I have not successfully booted into the OS yet. I tried adding the vdso=0 line to the boot options but still get the same error. Please feel free to dumb down any responses!
Thanks in advance,
Josh
Thought I should post this...
I followed all these instructions and still I was unable to start X. The error I was getting was 'no screens found'. It turns out that there were some wrong settings in my xorg.conf file. VMware was trying to load a Depth of 16 instead of 24, and this seemed to annoy X.
If this is happening to you, go into your xorg.conf file and look for "DefaultDepth" in 'Section "Screen"' and change the value 16 to 24. Then in SubSection "Display" change the "Depth" value from 16 to 24. (The mode I am using is 1024x768)
I dont know why any of this works (I'm still relatively new to Linux), but I figured I'd post it incase anyone had the same problem.
where exactly do i have to ap
where exactly do i have to append 3 in order to fix the xserverwontstart-problem?
with which options do i have
with which options do i have to untar the tarball?
i tried tar -x vmwar* and that made the system hang forever
now i have replaced 16 with 2
now i have replaced 16 with 24 two times in the xorg.conf file and that makes the xserver start but the keyboard doesnt work at all.
how can i get back to command line mode and aplly the patch ??
re: where exactly do i have to ap
you have to append 3 to the kernel boot line. this is in addition to the vsdo=0. you do this by pressing 'a' when grub is giving you the choice of which kernel to load. pressing 'a' lets you append options to the kernel start command. simply enter
vsdo=0 3
at the end of the line where your cursor will be. and then press Enter to load the kernel. the kernel image will then boot but not go into X mode.
xorg.config for display
This is partally correct advice!
Change your file xorg.conf file settings by deleting any values associated with DefaultDepth and Depth. FC2 will pass this smoothly based on settings of your Host machine.
You should not provide any settings for Depth and DefaultDepth - this assures that once someone will change host sreen color settings guest will start correctly. If any mismatch would occur X server will not start.
Thanks
Yup, it solved my problem, thank you!
I forgot to set vdso=0
Hello,
I forgot to set vdso=0. Now, I get the system blocked at kernel parameters configuration.
Please, is there a way to recover the system ?
Thanks a lot in advance,
Best regards
NB: I am using a fedora core 3
Works just fine
Hello,
i did apply the vmware patch, i had to chande the vmware-configtools.pl around line 3049 from 0.0.0 to 4.3.0.
It still had an error at hunk 2, but after startx the xserver finally run. Thy, a very, very, !!! lot. I have vmware 4.5.2, and athlon xp 1800.
What am I to just see this patch, and however u did know that??????
I am a year linux user, from RH9 to Suse8.2/9, back to FC2, but i never would have been able to script this kinda patch!!!!
Just how much experience do u have?? in years??? 10 or 15???? Im just interested!! whoaaaw. :)
patch
the tool 'patch' is very old. its brother is 'diff' which will create the input for patch by comparing the file before and after your edit. so you create a patch file with the diff tool. patching is basically a coding practice that has existed for a long time so that coders can exchange snippets of code. later on the term patch has been used to discribe an update to binary software - but that is a corruption of the original term which describes what you find here.
VMWare 4.5.2 release
FC2 is very very slow on VMWare 4.5.1, its that better on 4.5.2?
VMware v4.5.2 and FC2
Hello!
vmware-config-tools.pl changed to some extent with this release, however, problems with installing Fedora Core 2 Final remain.
It is impossible to directly apply patch vmware-fc2t3.patch - section 2 is not resolved correctly - one has to do some hand editing (no experince on writing patches so far - however seems to be easy).
xorg.conf file contains hard coded settings for Depth and DefaultDepth for display and drivers which prevent X server from starting correctly - settings should be blank - do it by hand - see my other comments in this thread on that subject.
And than comes mouse - system cannot find it - /dev/input/mice not found - and after reporting fatal error fails to start X server.
Running any setup utilities for mouse does not fix it. Could not fix it by changing device to /dev/paux either.
Any ides how to fix this last step?
PS working patch for VMware v4.5.2 would be very wellcomed!
Would be nice woudn't it...
I can't get past the kernel panic while trying to INSTALL Fedora core 2 on a windows xp pro host. Using .iso file and even an emulated CD from the ISO mountd as the 'E' drive... both ways result in a kernel panic, which restarts the vmware machine.
Debug log didn't give any further information ...
Ideas?
Would be nice woudn't it...
try setting at boot the following kernel parameter "vdso=0" - at GRUB prompt and in GRUB config file.
I do not have any problems without using vdso=0 (but have others), so it seems it depends on machine.
Cheers
Fedora Core 2 final + VMWare 4.5.2 on WinXp
First off I was initially using vmware 3.2 which just wont work. Get the latest version of 4.5.2. The good news is that they appear to have totally changed the vmware-config-tools.pl script so that it does not need patching to get X running. This is what worked for me:
mount /dev/cdrom /mnt ;
cd /tmp ;
tar zxf /mnt/vmware-linux-tools.tar.gz ;
umount /mnt ;
cd vmware-tools-distrib ;
./vmware-install.pl ;
When things come up you will see an error message "Error activating XKB configuration. Lots of people have reported seeing this for unusual hardware such as laptops and vmware :-) but this appears to be harmless. Some news postings say to use /etc/X11/xorg.conf rather than /etc/XF86free to fix this. I have not figured out how do do this. People say to symlink XF86free to xorg.conf but this did not work for me. People also said to me to just rename XF86free so it will not be used and x will then load xorg.conf but this does not worked for me. See this thread for more infomation.
FC2 Final under VMware 4.5.2
FYI: I just posted a new blog entry that details how to get FC2 final running under VMware Workstation 4.5.2. It's a little simpler now. For example vdso=0 is no longer required when booting. I also included a new patch, as the vmware-config-tools.pl script changed between 4.5.1 and 4.5.2.
Enjoy!
I tried your fix but I can't
I tried your fix but I can't get it to work. I entered 3 and booted to command line prompt. From there I could not vmware perl script. What am I doing wrong?