vmware 3.20 in FreeBSD5
coolerb
recently I installed FreeBSD5.0 release in vmware workstation
It starts installation very well until installing DOC in / directory
but the CPU utilization reach 100 % and doesn't go further.
and I failed installing FreeBSD 5.0
So my question is
1) anyone had experiences which I had ?
2) Do i have to wait unti next version of vmware comes out.?
3) is there any other ways installing FreeBSD5 ?
thanks in advance.
Paul Holbrook
Yep, I've had essentially the same experience. To elaborate:
I'm running VMWare 3.2 under Window 2k. I used the Freebsd 5.0
release mini iso image, and booted a VMWare virtual PC using that
image.
I did a standard user install. Reading from the virtual CD ROM
started around 425 K/bytes,sec; by the end of the 'base' install
phase, it was done to 130Kb/sec. During the Docs phase it was down to
50kb/sec. (By contrast, a FreeBSD 4.7 install using the same
procedure zips along at 600-700kb/sec.
I switched into the holographic shell that FreeBSD starts on virtual
terminal 4; once the doc install was running, I was able to run top.
I wasn't able to see anything usual; from the FreeBSD virtual
machine's point of view, it was loafing along: the cpio that was
reading from the install media was taking about 30% CPU.
I tried a number of combinations: I burned the image to a CD and used
that, I mounted the CD on a 4.7 instance running on the same machine
and did the 5.0 install over NFS.
One of the installs left enough of a FreeBSD 5.0 running that I tried
to copy the contents of the CD onto into the local file system. The
copy started out at a reasonable speed, but slowed down again; at this
point, I ran top, but found that "(swi 6 ...(don't remember) tty" was
taking up almost 100% of the CPU.
I saw another message on the one of the FreeBSD USENET group saying
that they had the same problem with 5.0 RC3, so there's clearly
something not working correctly here.
It's all rather annoying; I wasn't able to get 4.6 installed under
VMWare. 4.7 worked, which was great, but with 5.0, we're back to no
dice with FreeBSD.
-- Paul Holbrook
Paul Holbrook
Following up on my post about FreeBSD 5.0 on VMWare 3.2. Instead of
repeating the old stuff, I'll just hit the high points:
* Installing FreeBSD 5.0 under VMWare 3.2 for Windows hangs up during
the install. Actually, the install never really hangs, it just starts
going slower, and slower, and ...
I've learned a few new things since yesterday.
First, I can complete a minimal install. It runs to completion. If,
however, I run sysinstall after I reboot, I get into the same
problems: the copy from the CD (or the virtual CD, in this case) runs
slower and slower.
I have found several things that I think might be part of the problem.
First, just after the initial F1 loader starts, I see the following:
BTX Loader 1.0 BTX version is 1.01
Console: internal video/keyboard
BIOS drive A: is disk0
BIOS drive C: is disk1
BIOS 638kB/64512kB available memory
acpi: bad RSDP checksum (199)
I think that last line is critical. It comes from
src/sys/boot/i386/libi386/biosacpi.c I think it indicates that
FreeBSD hasn't been able to access some critical BIOS information.
Annother important clue: after I was able to get the minimal BSD up, I
took a ps. Here's what I got:
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
root 11 73.0 0.0 0 12 ?? RL 31Dec69 3:20.74 (idle)
root 10 0.0 0.0 0 12 ?? DL 31Dec69 0:00.00 (ktrace)
root 1 0.0 0.6 712 368 ?? ILs 31Dec69 0:00.12
/sbin/init --
root 12 0.0 0.0 0 12 ?? WL 31Dec69 0:01.17 (swi6:
tty:sio clock)
root 14 0.0 0.0 0 12 ?? WL 31Dec69 0:00.02 (swi1:
net)
root 2 0.0 0.0 0 12 ?? DL 31Dec69 0:00.06
(g_event)
root 3 0.0 0.0 0 12 ?? DL 31Dec69 0:00.12 (g_up)
root 4 0.0 0.0 0 12 ?? DL 31Dec69 0:00.49 (g_down)
root 15 0.0 0.0 0 12 ?? DL 31Dec69 0:00.06 (random)
root 20 0.0 0.0 0 12 ?? WL 31Dec69 0:00.30 (irq14:
ata0)
root 21 0.0 0.0 0 12 ?? WL 31Dec69 0:00.00 (irq15:
ata1)
root 22 0.0 0.0 0 12 ?? WL 31Dec69 0:00.05 (irq9:
lnc0 uhci0)
root 23 0.0 0.0 0 12 ?? DL 31Dec69 0:00.00 (usb0)
root 24 0.0 0.0 0 12 ?? DL 31Dec69 0:00.00
(usbtask)
root 25 0.1 0.0 0 12 ?? WL 31Dec69 0:00.05 (irq1:
atkbd0)
root 27 0.0 0.0 0 12 ?? WL 31Dec69 0:00.00 (irq6:
fdc0)
root 5 0.0 0.0 0 12 ?? DL 31Dec69 0:00.00
(pagedaemon)
root 6 0.0 0.0 0 12 ?? DL 31Dec69 0:00.00
(vmdaemon)
root 7 0.0 0.0 0 12 ?? DL 31Dec69 0:00.68
(pagezero)
root 8 0.0 0.0 0 12 ?? DL 31Dec69 0:00.00
(bufdaemon)
root 9 0.0 0.0 0 12 ?? DL 31Dec69 0:00.02 (syncer)
root 33 0.0 0.0 0 12 ?? DL 31Dec69 0:00.00 (vnlru)
root 34 0.0 0.0 0 12 ?? IL 31Dec69 0:00.00 (nfsiod
0)
root 35 0.0 0.0 0 12 ?? IL 31Dec69 0:00.00 (nfsiod
1)
root 36 0.0 0.0 0 12 ?? IL 31Dec69 0:00.00 (nfsiod
2)
root 37 0.0 0.0 0 12 ?? IL 31Dec69 0:00.00 (nfsiod
3)
root 114 0.0 0.2 220 108 ?? Is 2:09AM 0:00.00 adjkerntz
-i
root 186 0.0 1.4 1160 808 ?? Is 7:09AM 0:00.01
/sbin/dhclient lnc0
root 236 0.0 1.2 1172 716 ?? Is 7:09AM 0:00.12
/usr/sbin/syslogd -s
root 330 0.0 1.1 1144 656 ?? Is 7:09AM 0:00.00
/usr/sbin/usbd
root 387 0.0 3.4 2628 2036 ?? Is 7:09AM 0:00.19
/usr/sbin/sshd
root 392 0.0 4.2 3120 2528 ?? Ss 7:09AM 0:00.03 sendmail:
accepting connections (
sendmail)
smmsp 395 0.0 4.1 2996 2472 ?? Is 7:09AM 0:00.01 sendmail:
Queue runner@00:30:00 f
or /var/spool/clientmqueue (sendmail)
root 422 0.0 1.6 1324 968 ?? Is 7:09AM 0:00.01
/usr/sbin/inetd -wW
root 434 0.0 1.6 1236 956 ?? Ss 7:09AM 0:00.02
/usr/sbin/cron
root 443 0.0 2.2 1532 1304 v0 Is 7:09AM 0:00.23 login
[pam] (login)
root 444 0.0 1.4 1184 864 v1 Is+ 7:09AM 0:00.02
/usr/libexec/getty Pc ttyv1
root 445 0.0 1.4 1184 864 v2 Is+ 7:09AM 0:00.02
/usr/libexec/getty Pc ttyv2
root 446 0.0 1.4 1184 864 v3 Is+ 7:09AM 0:00.02
/usr/libexec/getty Pc ttyv3
root 447 0.0 1.4 1184 864 v4 Is+ 7:09AM 0:00.02
/usr/libexec/getty Pc ttyv4
root 448 0.0 1.4 1184 864 v5 Is+ 7:09AM 0:00.02
/usr/libexec/getty Pc ttyv5
root 449 0.0 1.4 1184 864 v6 Is+ 7:09AM 0:00.02
/usr/libexec/getty Pc ttyv6
root 450 0.0 1.4 1184 864 v7 Is+ 7:09AM 0:00.02
/usr/libexec/getty Pc ttyv7
root 456 0.0 1.8 1492 1076 v0 S 7:10AM 0:00.11 -csh
(csh)
root 0 0.0 0.0 0 12 ?? DLs 31Dec69 0:00.02
(swapper)
root 469 0.0 0.8 652 480 v0 R+ 7:13AM 0:00.00 ps auxww
Note all the processes that were started 31Dec69; my hunch is that
because FreeBSD wasn't able to get the BIOS info, it wasn't able to
get a a clock time as well. Notice that some processes, though, had
current times: by the time the system boots fully, it has managed to
get a current time from somewhere. And I'm guessing that the
disparity between 31Dec69 and the current time of 30+ years later is
driving some processes nuts, and making everything run slowly.
I also note that when I do a ps on a 4.7 system, I never see swi or
irq items. Those could be new with FreeBSD 5.0, though.
-- Paul Holbrook