kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pierre-Philipp Braun <pbraun@wda-fr.org>
To: <kvm@vger.kernel.org>
Subject: VIA Nano processor U2250 (1.6GHz           Capable)
Date: Mon, 30 Aug 2010 19:37:16 CEST
Date: Mon, 30 Aug 2010 19:35:36 +0200	[thread overview]
Message-ID: <30.08.2010.19.37.16.ocq6AT@mx2.nethence.com> (raw)
Message-ID: <3b3e5a73f75528e3c2551fabd3e2328b@localhost> (raw)


Hi,

I'm having a little issue starting a KVM guest.  Is that a known Issue on
VIA Nano vmx capable processors ?

# qemu-system-x86_64 -nographic -hda slack_disk.img -cdrom
slackware64-13.1-install-dvd.iso -boot d -m 512
KVM internal error. Suberror: 2
extra data[0]: 80000008
extra data[1]: 80000b0d
rax 0000000000301ffe rbx 00000000fb4b1fff rcx 0000000001070000 rdx
000000000107000e
rsi 00000000000f000f rdi 000000008990000e rsp 0000000000006ea8 rbp
00000000fff70000
r8  0000000000000000 r9  0000000000000000 r10 0000000000000000 r11
0000000000000000
r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15
0000000000000000
rip 000000000000f856 rflags 00010202
cs f000 (000f0000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
ds 1fff (0001fff0/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
es d977 (000d9770/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
ss 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
fs 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
gs 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
tr 0000 (feffd000/00002088 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
ldt 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0)
gdt f7a20/37
idt 0/3ff
cr0 10 cr2 0 cr3 0 cr4 0 cr8 0 efer 0
(stuck there...)

# cat /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         : 1596.008
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 pni monitor vmx est tm2 ssse3 cx16 xtpr rng rng_en
ace ace_en ace2 phe phe_en lahf_lm
bogomips        : 3192.01
clflush size    : 64
cache_alignment : 128
address sizes   : 36 bits physical, 48 bits virtual
power management:

Slackware64 13.1, qemu-kvm compiled from source,
# qemu-system-x86_64 -version
QEMU PC emulator version 0.12.5 (qemu-kvm-0.12.5), Copyright (c) 2003-2008
Fabrice Bellard
# lsmod | grep kvm
kvm_intel              42832  3
kvm                   265284  1 kvm_intel
# mount | grep shm
tmpfs on /dev/shm type tmpfs (rw)

Maybe there's something missing as it's my first KVM installation (I used
to play with XEN).  It's on a remote server which I would really like to
run KVM, with pv_ops.

Thanks !
//Pierre-Philipp

             reply	other threads:[~2010-08-30 17:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3b3e5a73f75528e3c2551fabd3e2328b@localhost>
2010-08-30 17:37 ` Pierre-Philipp Braun [this message]
2010-08-31 13:54   ` VIA Nano processor U2250 (1.6GHz Capable) Avi Kivity
2010-09-03 23:30   ` Rusty Burchfield
     [not found] ` <507d09425c13055782f5c620f4954565@localhost>
2010-08-30 17:37   ` Pierre-Philipp Braun

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=30.08.2010.19.37.16.ocq6AT@mx2.nethence.com \
    --to=pbraun@wda-fr.org \
    --cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).