Mailinglist Archive: opensuse (4053 mails)

< Previous Next >
Re: [SLE] VMWare, Win4Lin, and SuSE 7.2
  • From: Nick Webb <nickw@xxxxxxxxxx>
  • Date: Tue, 21 Aug 2001 09:37:44 -0700
  • Message-id: <3B828E58.F0BF9827@xxxxxxxxxx>
Thanks for the information. I think I'm gonna try VMW. You say that you are
running the 2.4.8 kernel with some kind of source patch, where can I get the
patch? I haven't seen anything on their site . . .

Thanks again!
_Nick

Bruce Marshall wrote:

> On Tuesday 21 August 2001 10:47, Nick Webb wrote:
> > Are you running VMWare express, or the workstation version?
> >
>
> The workstation version.
>
> Since I run SCSI drives, I wanted to additional capabilities of SCSI. You
> may want to seriously consider the differences between the workstation and
> express versions.
>
> In installing WIn98SE (and I don't believe that Win2000 or NT will run
> faster) I had to boot from a floppy at times (the Windows startup diskette)
> which also worked just fine. Not sure the express version can do that.
>
> I have a fairly large home LAN (printers, about 5 machines, webcam, etc) and
> am quite familiar configuring LAN's but I spent considerable time configuring
> VMWare. Problem: Knowing the difference between their host-only and bridge
> networking definitions.
>
> Bridge - means your VMWare machine will look to your LAN just like any other
> machine on your LAN. Host-only - means VMWare will only talk to your host
> linux machine.
>
> I wanted bridge but didn't know the difference and spent a lot of time
> diddling with host-only. Once I learned what I really wanted, configuring
> VMWare configuration is almost easier than adding a Win machine to the LAN.
> It's easy.
>
> VMWare also has three kinds of 'disks' that can be used. Virtual, plain and
> raw.
>
> Virtual - a HD that is defined as a file on your linux file system. Max
> size - 2GB Easy to set up. You can set it for 2GB and it will only use as
> much space as you currently 'fill' with your windows software. I.e., if you
> only have 1GB of Windows + apps, it will only use 1GB but can grow to 2GB.
>
> Plain - a HD that is defined as one or more files on your Linux system. Max
> size - ?? probably unlimited. (I'm using 4GB now) Only slightly more
> difficult to set up but it also USES all 4GB at setup time by formatting the
> space. I have mine on a separate partition so using the space isn't really a
> problem.
>
> raw - using an actual partition in its raw state such as a partition that
> already had windows loaded on it. Since I use SCSI disks, I haven't tried
> this yet as they are still working on the boot facilties for SCSI raw
> partitions.
>
> They also provide 'vmtools' for windows which helps with video setup and
> mouse usage. These are very desirable tools so before making your decision,
> load those tools.
>
> For example, the mouse handling is very nice once the tools are in place. If
> you click within the VMware window, the mouse is given over to VMW and the OS
> running under it. To get the mouse back to linux (or to move to another KDE
> desktop) you can either a) press clt-alt-esc while it is in the windows
> mode, or b) move the cursor off an edge of the VMW windows. Meaning you
> move the cursor to the edge of your Windows area. This works well of the
> tools are in place. Actually keyboard and mouse handling are excellent
> between VMW and linux.
>
> Here's an example of a Win4Lin problem that is still outstanding. For work,
> I need to run a VPN interface under Windows. This is a package you install
> and when installed, there is a driver file for a 'virtual' network card and
> the VPN then talks to that special network 'card'. Works fine under real
> windows, works fine under VMW.
>
> When I installed it under Win4Lin... the driver got installed fine, and the
> VPN worked fine as long as I didn't do a COLD shutdown. If I restarted (warm
> start) the driver would remain installed and things would still work. But if
> I did a complete Windows shutdown, the driver install would be lost. I could
> go through all the hoops of 'update driver' and it would find the driver I
> pointed to and install it... and that install would be good until I did
> another complete shutdown.
>
> Now *that's* flakey... and I finally got Netraverse to reproduce it (I think
> very highly of their support) and iafter two months it is still unresolved.
> Since that was my major use of Windows on a day-to-day basis, I stopped using
> Win4Lin. I also found that Win4Lin would only run for about 24 to 48 hours
> before something within Windows would get messed up and Windows would crash.
> I got to the point of shutting it down every 24 hours to clean things up.
> This also prevented me from using VPN.
>
> I am currently running:
>
> SuSE 7..2 Pro
> Kernel 2.4.8 (straight from kernel.org)
> KDE 2.2 (straight from kde.org)
> VMW 2.0.4 (with some source required for anything above kernel 2.4.7)
>
> The VMWare configuration is really very simple and I know where everything
> is. I've changed to a new kernel several times and had no problems. Windows
> within VMW has been rock solid and I have seen no evidence of any problems
> due to the use of VMW. Although I haven't been using long (3 weeks), the
> person who gave me the original hints to get things working right says he has
> never had Windows crash under VMW.
>
> The only problem I have seen with VMW is the use of VMW's version of Samba
> that they use as a go between between the Win guest and the linux host. If I
> try to copy a lot of files at once (more than 20 it seems) using file
> sharing, the entire VMW task will die. But I can do the same thing (copy a
> lot of files) to a real Windows machine without problems. I have reported
> this and they are working on the problem. In the meantime, I use Windows ftp
> to move files back and forth... (or if I really had to, I could move the
> files to a real Win machine and then use samba/linux to move the files to
> Linux. This hasn't been a problem for me.
>
> As another example of how robust the virtual environment is, I originally
> started out with a 1.4GB virtual disk and soon realized that was the wrong
> choice. (I should have at least made it a 2GB virtual disk and let it grow)
> To fix this, I defined another 'plain disk' using a different partition (4GB)
> and shutdown the Windows machine. I booted the Windows startup floppy,
> formatted the new D: drive, and copied (using the COPY command) the entire
> Windows C: drive over to the new D: drive. Ran SYS D: and rebooted after
> removing the C: drive from the config. Just like a real machine.
>
> Anyway, did I mention that I am a real VMW convert??????
>
> +----------------------------------------------------------------------------+
> + Bruce S. Marshall bmarsh@xxxxxxxxxx Bellaire, MI 08/21/01 11:17 +
> +----------------------------------------------------------------------------+
> "Anticipated events never live up to expectations."

--
Nick Webb
ITS Lab Software



< Previous Next >