Date: Sat, 10 Sep 2005 13:23:31 -0400 From: Matt Kosht <matt.kosht@gmail.com> To: Gleb Kozyrev <gkozyrev@ukr.net> Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD6.0 and VMWare 5.0.. No go Message-ID: <a87eda32050910102376f02c1a@mail.gmail.com> In-Reply-To: <000a01c5b5e6$5d974f30$0130a8c0@Gleb> References: <8b6eae9605090106151a81174d@mail.gmail.com> <bcsvh1pbn07me39npkl17qe0qftepqed7a@4ax.com> <a87eda32050909124016956bb9@mail.gmail.com> <000a01c5b5e6$5d974f30$0130a8c0@Gleb>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/10/05, Gleb Kozyrev <gkozyrev@ukr.net> wrote: >=20 > At loader set hint.apic.0.disabled=3D1 That worked thanks! >=20 > But it won't help you because 6.0 can't see the virtual disk. > After I boot from install CD the SCSI controller is recognized > (bt0 for vmxbuslogic or mpt0 for vmxlsilogic) but no HDD is found. > If I go to FixIt shell and issue an > camcontrol devlist -v > I see that the HDD is there with no device node assigned to it. > After I do > camcontrol rescan 0:0:0 > The drive is found and maybe setup could partition it, though I > didn't try because after reboot the disk won't be seen anyway. >=20 > 5.4 sees the disk on vmxlsilogic controller but shows lots > of SCSI errors on console while working. http://www.vmware.com/community/thread.jspa?forumID=3D21&threadID=3D4023&me= ssageID=3D20120#20120 I read this thread. Not familiar enough with VMWare yet to know where/what this config file is, but I'll give it a whirl. Sounds like it worked for 5.2.1 and 5.3 (which I couldn't get to work either) >=20 > It seems that only 4.x can be run on ESX and they aren't going > to support any newver versions. >=20 :( Maybe if we all complained/offered help to debug issue to VMWare about this they would fix it. They only officially support 4.9 as a guest running on ESX.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a87eda32050910102376f02c1a>