To: bsd-dk@bsd-dk.dk Subject: Re: FreeBSD 5.2.1 under VMware? From: Klaus Harbo <none@klaus--harbo.net.lh.bsd-dk.dk> Date: Fri, 25 Jun 2004 15:07:06 +0200
"Gorm J. Siiger" <none@gjs--sonnit.dk.lh.bsd-dk.dk> writes:
> From: "Gorm J. Siiger" <none@gjs--sonnit.dk.lh.bsd-dk.dk>
> Subject: Re: FreeBSD 5.2.1 under VMware?
> To: bsd-dk@bsd-dk.dk
> Date: Fri, 25 Jun 2004 13:56:53 +0200
> Reply-To: bsd-dk@bsd-dk.dk
>
> Jeg har ikke testet i GSX, men prøv at køre uden ACPI.
>
> Det er først i 4.5x jeg fik 5.2.1 til at virke.
Jeg har researchet lidt via nntp://news.vmware.com hvor jeg fandt en
posting (som jeg tænker også kunne have listens interesse, se da
nedenfor) som antyder at der _er_ problemer med VMware 3 og FreeBSD
5.2 - sådan som Gorm også konkluderer overfor.
De suspend/ problemer Makoto beskriver kunne meget vel være
ACPI-relaterede, og jeg tænker derfor at jeg foreløbig er bedst
stillet med v4.10 fremfor noget 5.x (jeg forsøgte også at boote fra
kern.flp fra 5.1 - samme symptom/ingen boot).
Jeg har lige bootet uden problemer fra kern.flp fra 4.10 - så det ser
lovende ud.
Er der nogen som kan sige om jeg kan forvente at kunne lave en
nogenlund smooth upgrade når jeg skal fra 4.10 til 5.x, eller bliver
'start fra scratch' igen-igen til sin tid? Erfaringer?
Tak for hjælpen!
-K.
----------
From: Makoto Matsushita <none@matusita--matatabi.or.jp.lh.bsd-dk.dk>
Subject: Re: Trouble installing FreeBSD 5.2 on VMWare 3.2
Newsgroups: vmware.guest.misc
Date: 14 Mar 2004 18:52:40 +0900
Organization: Group MATATABI
tuntto> Hi, I am having trouble installing FreeBSD 5.2 on VMWare 3.2.
The short answers are:
1) Upgrade to VMware 4.
2) Use custom FreeBSD kernel for installation.
3) Cycle "Suspend & Resume" as many as you required.
These are very well-known issue (if there's FAQ list, it must be an
item for that), try googling to understand more.
***
Long answers:
Solution 1)
VMware 4.0.5 with
tuntto> I have put the line:" monitor_control.disable_apic="TRUE"" in my .vmx file
is confirmed to work. Please note that it is _NOT_ for VMware 3.x.
If you don't like such hack, wait next VMware 4 is released (it'll be
released as 4.5.0); it works with no problems.
Solution 2)
The default kernel for FreeBSD installation doesn't have special
kernel option, CPU_DISABLE_CMPXCHG. If you have any other FreeBSD
machines, compile custom kernel with this option, gzip it, put it on
kern.flp, then boot with the new floppy. Please note that this only
replaces "the kernel for installation" not "installed FreeBSD"; you
have to recompile your own kernel after installing FreeBSD.
Solution 3)
If your VM seems freezed, suspend it, then resume again. If you're
lucky, your VM works again. Unfortunately, your VM freezes again and
again... each time the VM suspends, you have to cycle suspend&resume
VM. Easy to do, but very troublesome way.
-- -
Makoto `MAR' Matsushita
This archive was generated by hypermail 2b30 : Wed 15 Nov 2006 - 18:24:41 CET