* Re: Via Nano fails and completely crashes on kvm
[not found] <CALL1ybn2scmOyKom3cphHu+kzJyGv+4OGPmrwJN60GU1QhFTyA@mail.gmail.com>
@ 2014-11-08 10:59 ` Borislav Petkov
0 siblings, 0 replies; only message in thread
From: Borislav Petkov @ 2014-11-08 10:59 UTC (permalink / raw)
To: Timothy McDaniel; +Cc: linux-kernel, kvm
On Fri, Nov 07, 2014 at 10:18:32PM -0500, Timothy McDaniel wrote:
> Via Nano fails and completely crashes on kvm
>
> here is my /proc/cpuinfo
>
> processor : 0
> vendor_id : CentaurHauls
> cpu family : 6
> model : 15
> model name : VIA Nano processor U2250 (1.6GHz Capable)
> stepping : 3
> cpu MHz : 800.000
> cache size : 1024 KB
> fpu : yes
> fpu_exception : yes
> cpuid level : 10
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat clflush acpi mmx fxsr sse sse2 ss tm pbe syscall nx lm
> constant_tsc up rep_good nopl pni monitor vmx est tm2 ssse3 cx16 xtpr
> rng rng_en ace ace_en ace2 phe phe_en lahf_lm
> bogomips : 3191.62
> clflush size : 64
> cache_alignment : 128
> address sizes : 36 bits physical, 48 bits virtual
> power management:
>
> also here is my uname -mrs
> Linux 3.2.0-4-amd64 x86_64
>
> here is uname -a
> Linux sd-24793 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u1 x86_64 GNU/Linux
>
> please tell me if you need anymore info on helping me get kvm to work.
[ Quoting the whole mail for reference. ]
Yes, please try a newer kernel first, say 3.17, for example. Then, if
it still crashes, catch everything from the crash and add it here as a
reply to this mail.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-11-08 10:59 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CALL1ybn2scmOyKom3cphHu+kzJyGv+4OGPmrwJN60GU1QhFTyA@mail.gmail.com>
2014-11-08 10:59 ` Via Nano fails and completely crashes on kvm Borislav Petkov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox