Anthony Liguori wrote: > Izik Eidus wrote: >> Anthony Liguori wrote: >>> Avi Kivity wrote: >>>> Andi Kleen wrote: >>>> >>>>> When I try my 64bit kernel with -kernel ... on kvm-59 I get before >>>>> the kernel outputs anything: >>>>> >>>>> >>>> >>>> Yes, I think -kernel is broken. >>>> >>> >>> If you are using a guest with more than 3.75GB or so. The >>> load_kernel function uses phys_ram_base + addr and that assumption >>> is violated in KVM with guests > ~3.75GB of memory. We either need >>> to allocate memory for the hole and never touch it or change >>> load_kernel to use cpu_physical_memory_rw. I know we discussed this >>> before but I don't remember if we came to a consensus about what the >>> correct fix is? >>> >> we can do munmap on the pci hole memory area, >> btw Anthony virtio will need this too right? > > Yup. I don't think you want to munmap memory allocated by glibc. i was thinking about allocate the memory with mmap instead of the qemu qemu_malloc... > > I think a better thing to do would be to madvise(MADV_DONTNEED) > although I don't think it's strictly needed. If you never touch the > memory, then does it really matter? why to keep the virtual address size of a program 300mb larger than it really is? > > Regards, > > Anthony Liguori > >>> Regards, >>> >>> Anthony Liguori >>>> Izik? >>>> >>>> >>> >> >
------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
