* Izik Eidus <[EMAIL PROTECTED]> [2007-08-12 14:27]:
> this is a request for comment for patchs that allow kvm to run with more than 
> 2 giga.
> there are 4 patchs.
> the first patch(biospatch): is for the bios:now the bios know how to map 
> memory about the 0xf0000000-0xffffffff hole.
> 
> the second  patch(qemu_change_types_patch):is for qemu ram_size types:it 
> change the variables that hold the ram_size to unsigned long,
> and it is based on patch from the qemu-devel list that targeted sparc.
> 
> the third patch(kvm_userspace_memmap):is for kvm and add to it another memory 
> slot that hold the new memory region.
> 
> the last patch(kvm_new_slot_patch):is for kvmctl, and make it use the new 
> memory region and map memory above 4giga to it.
> 
> i added compiled bios for to make it easy to run it.
> 
> (kvm was tested with 14giga of ram and had no problem to drive win3k and 
> fedora 6 + x ,please note that i tryed in the patch to add support to the 
> qemu emulator to run with above 4 giga as well,
> it work without svga, need some work to do there)

I can confirm the patches working against kvm-33 with up to 14G guests,
tested 32-bit Feisty guest, and 64-bit feisty guest.  Both working
fine.  I'm trying to get on a box with more ram so I can test larger
guests.

--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
[EMAIL PROTECTED]

-------------------------------------------------------------------------
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
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Reply via email to