FreeBSD 4.10-RELEASE-p16 on ESX Server 2.5.1

Colin Farley Colin.Farley at ecarecenters.com
Sat Sep 24 14:51:20 PDT 2005


Thanks for your help, adding the two lines that you mentioned below fixed
the problem.

Thanks again,
Colin

-----owner-freebsd-stable at freebsd.org wrote: -----


To: Colin Farley <Colin.Farley at ecarecenters.com>
From: Tom Pepper <tom at blorp.com>
Sent by: owner-freebsd-stable at freebsd.org
Date: 09/23/2005 05:27PM
cc: freebsd-stable at freebsd.org
Subject: Re: FreeBSD 4.10-RELEASE-p16 on ESX Server 2.5.1

vmware's virtual implementation of acpi collides with freebsd.  best
practice is to disable acpi altogether in the actual config file on
the host o/s for the VM by manually placing:

acpi.present = "false"
monitor_control.disable_apic = "TRUE"

in the whatever.vmx config file, and restarting the virtual machine.
read up on the vmware forums for some more information from yours
truly on trying to beat freebsd into running on ESX.  there's
additional problems you'll run into w/r/t crappy smbfs performance,
agent support, and some esoteric problems like nanosleep() calls
eating CPU instead of actually idling.

-t

On Sep 23, 2005, at 2:08 PM, Colin Farley wrote:

>
> I'm having a problem with my FreeBSD virtual machines on the
> production HP
> DL360 G4p servers we are using.  In test I used a weaker ESX box
> and never
> had the issue.  The problem is when rebooting the virtual machine
> it will
> sometimes hang at "Waiting 15 seconds for SCSI devices to settle".
> This
> never happened on the test box and I have never encountered it before.
> Furthermore, if I use Vmotion (to move the virtual machine to a
> different
> ESX host) and bring the virtual machine up on another ESX server
> everything
> is fine and the virtual machine boots normally.  Because of this I
> figured
> that it was an ESX problem and decided to put a support ticket in with
> them.  They replied with this:
>
> "The particular "Waiting 15 seconds for SCSI devices to settle"
> message you
> are getting with FreeBSD is a known issue with the FreeBSD system that
> occurs
> on physical systems as well.
>
> The work around for it is to edit your kernel config file with
> 'OPTIONS
> SCSI_DELAY=1000' and to
> rebuild and install the new kernel"
>
> To me this doesn't sound right, can anyone confirm?
>
> Thanks,
> Colin
>
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-
> unsubscribe at freebsd.org"
>

_______________________________________________
freebsd-stable at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"



More information about the freebsd-stable mailing list