On 12/01/2011 03:50 PM, Sasha Levin wrote: > On Thu, 2011-12-01 at 15:48 +0200, Avi Kivity wrote: > > On 12/01/2011 03:37 PM, Daniele Carollo wrote: > > > Hi, > > > my name's Daniele and I'm using the native linux kvm tool. > > > If I try to execute it in this way ./kvm run -d ~/linux-0.2.img I get > > > a kernel panic like this: http://paste.org/41673 > > > Only using the addictional option -p "idle=halt" I can run a virtual > > > machine. > > > Printing cat /proc/cpuinfo on the host i get http://paste.org/41663 > > > and on the guest http://paste.org/41664 > > > Sashal from the native linux kvm tool team noticed that there is the > > > monitor cpu flag even on the guest. > > > > > > > from cpuid.c: > > > > /* cpuid 1.ecx */ > > const u32 kvm_supported_word4_x86_features = > > F(XMM3) | F(PCLMULQDQ) | 0 /* DTES64, MONITOR */ | > > > > so either the masking later on is subtly wrong, or kvm tool doesn't pass > > it on correctly, or Linux ignores it. > > > > Please run the attached program on the host and post its output. > > > > Avi, > > We tested it with qemu where Daniele has reported that monitor is also > visible in the cpuid there. >
Not here (3.2). Maybe it's another manifestation of the -E2BIG cpuid bug. -- error compiling committee.c: too many arguments to function -- 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
