Date: Mon, 7 May 2007 17:18:56 -0700 (PDT) From: Gore Jarold <gore_jarold@yahoo.com> To: jahnke@sonatabio.com Cc: freebsd-emulation@freebsd.org Subject: Re: vmware3 on FreeBSD 6.2 - minor (?) svga problem ... more #2 Message-ID: <828430.50438.qm@web63013.mail.re1.yahoo.com> In-Reply-To: <1178579952.938.164.camel@pinot.fmjassoc.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--- Frank Jahnke <jahnke@sonatabio.com> wrote: > On Mon, 2007-05-07 at 16:07 -0700, Gore Jarold > wrote: > > > > > > > I did device.hints, sysctl and linprocfs. I > assume by > > the install script, you mean 001.vmware.sh ? > > Yes -- what is does is pretty much all in the > background. Ok, well then I definitely ran it. I did NOT run it prior to my first attempts (but I also didn't have the apic hint in place either). But I have since run the install script and created new VMs since running it, and they all do the same thing. > > I then started vmware manually, and it immediately > ran > > the wizard for me and I created a VM. > > Did the VM boot at the end of the install? Or did > you get the error > message you cite? It should have booted at the end. No. No VM has ever booted in any way. It did not run after creation, and did not run after subsequent "power on" attempts. It shows that SVGA error and nothing else happens. I checked the log from the VM when I just recently attempted to run it, and I see: Feb 16 17:26:57: VMX|Using unified VGA. Feb 16 17:26:57: VMX|SVGA frame buffer address 0x7efc0000 Feb 16 17:26:57: MKS|SVGA changing width from 2364 to 5760 Feb 16 17:26:57: MKS|SVGA changing height from 1773 to 1200 Feb 16 17:26:57: MKS|The host frame buffer is too big (27648000 > 16777216). Feb 16 17:26:57: VMX|Msg_Post: Error Feb 16 17:26:57: VMX|[msg.svga.powerOnFailed] Failed to initialize SVGA device. Feb 16 17:26:57: VMX|---------------------------------------- Feb 16 17:26:57: VMX|Disk: Open(winXPPro.vmdk) flags=0x0=. Feb 16 17:26:57: VMX|BigCOWDisk_OpenFromParent: Big Cow Disk winXPPro.vmdk Feb 16 17:26:57: VMX|BigCOWDisk_OpenFromParent: COWDisk is Big capable Feb 16 17:26:57: VMX|COWDisk_OpenFromP(winXPPro.vmdk) flags 0x0= diskNum=0 Feb 16 17:26:57: VMX|FILEIO: Reverting to buffered IO for file winXPPro.vmdk Feb 16 17:26:57: VMX|COWDISK: Disk winXPPro.vmdk Granularity = 128 Feb 16 17:26:57: VMX|COWDISK: Open: winXPPro.vmdk has Generation number 190634281. Feb 16 17:26:57: VMX|COWDisk_OpenFromP(winXPPro-02.vmdk) flags 0x0= diskNum=1 Feb 16 17:26:57: VMX|FILEIO: Reverting to buffered IO for file winXPPro-02.vmdk Feb 16 17:26:57: VMX|COWDISK: Disk winXPPro-02.vmdk Granularity = 128 Feb 16 17:26:57: VMX|COWDISK: Open: winXPPro-02.vmdk has Generation number 190634281. Feb 16 17:26:57: VMX|COWDisk_OpenFromP(winXPPro-03.vmdk) flags 0x0= diskNum=2 Feb 16 17:26:57: VMX|FILEIO: Reverting to buffered IO for file winXPPro-03.vmdk Feb 16 17:26:57: VMX|COWDISK: Disk winXPPro-03.vmdk Granularity = 128 Feb 16 17:26:57: VMX|COWDISK: Open: winXPPro-03.vmdk has Generation number 190634281. Feb 16 17:26:57: VMX|COWDisk_OpenFromP(winXPPro-04.vmdk) flags 0x0= diskNum=3 Feb 16 17:26:57: VMX|FILEIO: Reverting to buffered IO for file winXPPro-04.vmdk Feb 16 17:26:57: VMX|COWDISK: Disk winXPPro-04.vmdk Granularity = 128 Feb 16 17:26:57: VMX|COWDISK: Open: winXPPro-04.vmdk has Generation number 190634281. Feb 16 17:26:57: VMX|BigCOWDisk_Close: closing 4 disks of BigCowDisk winXPPro.vmdk Feb 16 17:26:57: UI|VMX(UI): changing state 0 from 1870 to 1871, nesting 0 Feb 16 17:26:57: UI|VMX(UI): changing state 1 from 1873 to 1873, nesting 0 That is what appears when I power on, then I see the SVGA error message inside the vmware GUI, and if I click OK, the logs end with: Feb 16 17:28:35: VMX|Module SVGA power on failed. Feb 16 17:28:35: VMX|VMX_PowerOn: ModuleTable_PowerOn = 0 That line: Feb 16 17:30:41: MKS|The host frame buffer is too big (27648000 > 16777216). is suspicious ... does this mean I should bump down to 16 million colors in my X config ? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?828430.50438.qm>