On Wed, Jul 20, 2011 at 03:48:39PM +0530, Naresh Bhat wrote: > Hi Gleb, > > How can I differentiate or find out is it a production processor or not ? I don't know for sure but "model name" name from the output below does not look like something that comes from production CPU. Try on another CPU please.
> If it not a production based processor. If I upgrade the BIOS with > the latest suitable version will it work ? any idea ? > Have no idea. > root@Tux:~# cat /proc/cpuinfo > processor : 0 > vendor_id : GenuineIntel > cpu family : 6 > model : 26 > model name : Genuine Intel(R) CPU @ 0000 @ 2.93GHz > stepping : 2 > cpu MHz : 2933.739 > cache size : 8192 KB > physical id : 1 > siblings : 8 > core id : 0 > cpu cores : 4 > apicid : 16 > initial apicid : 16 > fpu : yes > fpu_exception : yes > cpuid level : 11 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov > pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx > rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology > nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 > cx16 xtpr pdcm dca sse4_1 sse4_2 x2apic popcnt lahf_lm ida tpr_shadow > vnmi flexpriority ept vpid > bogomips : 5867.47 > clflush size : 64 > cache_alignment : 64 > address sizes : 40 bits physical, 48 bits virtual > power management: > > processor : 1 > vendor_id : GenuineIntel > cpu family : 6 > model : 26 > model name : Genuine Intel(R) CPU @ 0000 @ 2.93GHz > stepping : 2 > cpu MHz : 2933.739 > cache size : 8192 KB > physical id : 1 > siblings : 8 > core id : 1 > cpu cores : 4 > apicid : 18 > initial apicid : 18 > fpu : yes > fpu_exception : yes > cpuid level : 11 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov > pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx > rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology > nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 > cx16 xtpr pdcm dca sse4_1 sse4_2 x2apic popcnt lahf_lm ida tpr_shadow > vnmi flexpriority ept vpid > bogomips : 5865.76 > clflush size : 64 > cache_alignment : 64 > address sizes : 40 bits physical, 48 bits virtual > power management: > .... > ............. > ....................... > > Thanks > -Naresh Bhat > > 2011/7/20 Gleb Natapov <[email protected]>: > > On Wed, Jul 20, 2011 at 03:02:59PM +0530, Naresh Bhat wrote: > >> Hi Gleb, > >> > >> Yes, I am always got this error message. I feel these messages are > >> from kernel. Till today I am not able to launch the with full > >> virtualization support. I am able to launch with the -no-kvm option > >> to the above command-line. But still I can see the same messages.I am > >> connected to the target with ssh. > >> > >> After connecting the monitor and modifying command line for > >> kernel(vga=0x) behavior qemu-kvm similar as below > >> > >> A black screen with "VGA Blank mode" message in the middle. > >> > >> I saw a message from Avi Kitty saying that "The guest runs the vga > >> vios and hangs. Please try with a production > >> processor" > >> > >> from the link > >> http://comments.gmane.org/gmane.comp.emulators.kvm.devel/45870 > >> > > And your cpu is production one? What "cat /proc/cpuinfo" on the hoest > > shows? > > > >> Thanks > >> -Naresh Bhat > >> > >> On Wed, Jul 20, 2011 at 2:41 PM, Gleb Natapov <[email protected]> wrote: > >> > On Wed, Jul 20, 2011 at 02:37:47PM +0530, Naresh Bhat wrote: > >> >> Hi Gleb, > >> >> > >> >> I am trying to launch with the following command. > >> >> > >> >> # qemu-kvm -kernel ./bzImage.bin -hda ./rootfs-vm.ext2 -append > >> >> "root=/dev/sda rw > >> >> ip=off" -curses > >> >> > >> > Are you always get this error when you are trying the command line above? > >> > > >> >> Thanks > >> >> -Naresh Bhat > >> >> > >> >> 2011/7/20 Gleb Natapov <[email protected]> > >> >> > >> >> > On Wed, Jul 20, 2011 at 02:15:10PM +0530, Naresh Bhat wrote: > >> >> > > Hi All, > >> >> > > > >> >> > > I am using > >> >> > > 1. Kernel Version - linux-2.6.32 > >> >> > > 2. The QEMU-KVM package version is qemu-kvm-0.13.0 > >> >> > > > >> >> > > on the below hardware.. > >> >> > > > >> >> > > ========================================================================= > >> >> > > Board info: > >> >> > > BIOS Revision Txx052.01_CRB > >> >> > > CSI RC Revision 01.03 RC1 > >> >> > > Memory RC Revision 01.03 RC4 > >> >> > > CSM Revision 02.54 > >> >> > > Platform GreenCity > >> >> > > Processor BSP Revision 106A2 - Nehalem B0 > >> >> > > Tylersburg Revision TylersBurg - B0 > >> >> > > ICH Revision ICH10: Consumer - A0 > >> >> > > ========================================================================= > >> >> > > > >> >> > > I am facing the following spammed error in dmesg. But Without kvm > >> >> > > support qemu manages to start. > >> >> > > > >> >> > > [ 213.729167] handle_exception: unexpected, vectoring info > >> >> > > 0x8000000d > >> >> > intr > >> >> > > info 0x80000b0d > >> >> > > [ 213.729169] handle_exception: unexpected, vectoring info > >> >> > > 0x8000000d > >> >> > intr > >> >> > > info 0x80000b0d > >> >> > > [ 213.729171] handle_exception: unexpected, vectoring info > >> >> > > 0x8000000d > >> >> > intr > >> >> > > info 0x80000b0d > >> >> > > > >> >> > > Any patches available for the above error message ? > >> >> > > > >> >> > And your command line is...? > >> >> > > >> >> > -- > >> >> > Gleb. > >> >> > > >> >> > >> >> > >> >> > >> >> -- > >> >> "For things to change, we must change" > >> >> -Naresh Bhat > >> > > >> > -- > >> > Gleb. > >> > > >> > >> > >> > >> -- > >> "For things to change, we must change" > >> -Naresh Bhat > > > > -- > > Gleb. > > -- Gleb. -- 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
