[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-discuss] failed to start qemu after system restart

From: Jakob Bohm
Subject: Re: [Qemu-discuss] failed to start qemu after system restart
Date: Fri, 8 Apr 2016 08:09:50 +0200
User-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2

On 08/04/2016 07:52, Mahmood Naderan wrote:
 >In your list of modules the only thing I can see that
 >looks suspicious is that you seem to have a number of
 >virtualbox modules and some other strange virtualization
 >drivers loaded that makes me suspect that there is
 >another virtualization program interfering with kvm use
 >of the CPU's virtualization features.

Actually I have installed vmware workstation and virtualbox!

May or may not be the reason.

What does the system logs say about kernel messages when booting,
starting the first qemu --enable-kvm after boot and/or doing

# modprobe kvm_amd

Maybe there is an error message about why it won't load.

If I remove the -enable-kvm option then the guest runs normally but it
is pretty slow as you may guess.

About the cpuinfo, I see these flags

flags           : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt
pdpe1gb rdtscp lm constant_tsc rep_good nonstop_tsc extd_apicid amd_dcm
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes
xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce
nodeid_msr tbm topoext perfctr_core cpb npt lbrv svm_lock nrip_save
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold bmi1

I am guessing this is some unspecified recent AMD chip?


Jakob Bohm, CIO, Partner, WiseMo A/S.  https://www.wisemo.com
Transformervej 29, 2860 Søborg, Denmark.  Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded

reply via email to

[Prev in Thread] Current Thread [Next in Thread]