All of lore.kernel.org
 help / color / mirror / Atom feed
From: tadomeit <tadomeit-Crc3fnV8OO0Aey3BTtE3dg@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: guest reboot hanging - kvm: unhandled wrmsr: 0xc0000083
Date: Fri, 27 Jul 2007 13:18:02 +0200	[thread overview]
Message-ID: <46A9D46A.8050003@compuserve.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1537 bytes --]

Hi,

I've installed the latest version kvm-33 on my PC. All guests (tested
with several knoppix version and SuSE 10.1 install dvd image) hanging on
reboot. In the host syslog I found a lot of messages (>1000): "kernel:
kvm: unhandled wrmsr: 0xc0000083"

I've tested with the original kernel kvm modules and with the modules
delivered with kvm-33, I tried the version kvm-32 - no success - every
time the same behaviour!

My startup command (without problems if using using the -no-kvm option):
qemu-system-x86_64 -boot d -m 384 -cdrom
/data/temp/SUSE-Linux-10.1-GM-DVD-i386.iso

My box:
fritz:~ # uname -a
Linux fritz 2.6.22.1-default #3 SMP Fri Jul 27 12:22:16 CEST 2007 i686
athlon i386 GNU/Linux

fritz:~ # cat /proc/cpuinfo
processor       : 0 (same for core 1)
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 75
model name      : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
stepping        : 2
cpu MHz         : 1000.000
cache size      : 512 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 ht s
yscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow pni cx16 lahf_lm
cmp_legacy svm extapic cr8legacy ts fid vid ttp tm s
tc
bogomips        : 2005.81
clflush size    : 64


Best regards
Tom

[-- Attachment #2: .config --]
[-- Type: application/x-config, Size: 40502 bytes --]

[-- Attachment #3: Type: text/plain, Size: 315 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

[-- Attachment #4: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

             reply	other threads:[~2007-07-27 11:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27 11:18 tadomeit [this message]
     [not found] ` <46A9D46A.8050003-Crc3fnV8OO0Aey3BTtE3dg@public.gmane.org>
2007-07-31 16:15   ` guest reboot hanging - kvm: unhandled wrmsr: 0xc0000083 Avi Kivity
     [not found]     ` <46AF6018.3060108-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-31 20:34       ` tadomeit

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46A9D46A.8050003@compuserve.de \
    --to=tadomeit-crc3fnv8oo0aey3btte3dg@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.