On Tue, 2007-08-14 at 10:09 -0500, Ryan Harper wrote: > * Izik Eidus <[EMAIL PROTECTED]> [2007-08-14 01:29]: > > Hey Ryan, > > thanks for the testing, i hope you didnt have too much problems to get it > > working. > > Sure, it wasn't too much trouble. > > > anyway as far as i can tell it wont have problem to drive up to 256 + 3.75 > > giga ram for guest. > > if we want it to drive systems with even more ram we have two options ( > > both very easily applied ): > > we can add another cmos byte to a "future reserved" byte, or we can use the > > 3 cmos bytes that i already added and say that > > we store memory in the above bios memory at multiplier of 1 MB. > > it is important we decide now how we want to store the memory, that in the > > future when 256 + 3.75 giga of ram wont be enough > > we wouldn't have to change bochs bios again. > > Yeah, I think we want to settle on a single method which gets us the > most memory as possible. I think rather than doing the "future reserve" > we should go head an move over to 1MB multiplier. > well this sound like a smart idea, but what we have to think about is: first in this way we have just 64 gigabyte of ram (unless we work with the extra cmos memory bytes) plus if we change the way we use the "normal cmos bytes", we arent breaking compatibility with really old stuff that check the cmos directly without doing bios interrupt? (i mean by ports)
> > i am working for fixes to the patch from comments that Anthony and > > Luca gave me, so i hope to send a better patch to the list soon. > > Great! Look forward to seeing the new patchset. > > i already sent the list new patchs before i saw this mail, so the cmos problem will be handled in the next time. thanks ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/kvm-devel
