Bugs item #2219447, was opened at 2008-11-03 20:32 Message generated for change (Comment added) made by glommer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2219447&group_id=180599
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: intel Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Torsten Wohlfarth (towo2099) Assigned to: Nobody/Anonymous (nobody) Summary: kvm_run: Cannot allocate memory Initial Comment: Since i testet kernel 2.6.28-rc2 and rc3, kvm quit running wit the following error: kvm -hda vdisk_xp.qcow -m 1024 -smp 2 -soundhw ac97 kvm_run: Cannot allocate memory kvm_run returned -12 It does not matter, if the gues is a linux or xp. kvm version is kvm-78 system is Linux Defiant 2.6.28-rc3-towo-1 #1 SMP PREEMPT Mon Nov 3 16:46:41 CET 2008 i686 GNU/Linux cpu is Intel Core2 Quad Q6700 @ 4096 KB cache flags( sse3 nx lm vmx ) the no-kvm-switches does not help Booting in kernel 2.6.27.4 let kvm running fine. ---------------------------------------------------------------------- Comment By: Glauber de Oliveira Costa (glommer) Date: 2008-11-08 00:37 Message: No, using that parameter won't work. I just got the fix for it today. It's not in any tree yet, but since you're using git, I'll assume you're confortable with applying a patch in your tree ;-) You can download it from http://glommer.net/0003-restart-search-at-beggining-of-vmalloc-address.patch ---------------------------------------------------------------------- Comment By: walt (w41ter) Date: 2008-11-07 21:07 Message: FWIW this seems to be a 32-bit-only problem for me. I track Linus.git and kvm-userspace.git in 32-bit and 64-bit linux installations on one machine, and the 64-bit kvm works perfectly. Only the 32-bit kvm has this error. Can I work around the problem with vmalloc=<size>? If yes, where do I use that vmalloc flag? Thanks. ---------------------------------------------------------------------- Comment By: Torsten Wohlfarth (towo2099) Date: 2008-11-03 21:13 Message: Yeah, there are many messages about vmalloc: http://rafb.net/p/4RvqBX81.html ---------------------------------------------------------------------- Comment By: Glauber de Oliveira Costa (glommer) Date: 2008-11-03 21:08 Message: check your dmesg in the host. If there's any message about vmalloc failing, so this is a known issue. I have a band aid patch that helps it, but we're still not sure what the proper fix is. I'm working on it right now. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2219447&group_id=180599 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
