Bugs item #1906272, was opened at 2008-03-03 14:53
Message generated for change (Comment added) made by jessorensen
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1906272&group_id=180599
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
>Resolution: Duplicate
Priority: 5
Private: No
Submitted By: Technologov (technologov)
Assigned to: Nobody/Anonymous (nobody)
Summary: Debian 4 fails to boot on KVM-AMD
Initial Comment:
Host: AMD Barcelona K10, F7/x64, KVM-62.
Guest: Debian 4 (32-bit).
Problem: When installing Debian 4 (32-bit) on KVM-AMD host, it installs "k7"
kernel by default, and the resulting image is not bootable.
It can be booted only with "-no-kvm".
This problem can be avoided when installing on KVM-intel host, which uses
"i686" kernel for Debian guests.
This is because Debian's setup check for CPUID and setups the kernel, that best
matches the current CPU.
This kernel (i686) can be booted from kvm-intel or from kvm-amd without
problems.
Perhaps KVM-AMD doesn't emulate something K7 specific (3Dnow ?).
I don't know what is the best solution to this problem, but I think using
custom CPUID when installing Debian guests might do it.
Any ideas?
===================================================
(gdb) bt
#0 0x0000003dd02c9117 in ioctl () from /lib64/libc.so.6
#1 0x000000000051bb29 in kvm_run (kvm=0x2a9b040, vcpu=0) at libkvm.c:850
#2 0x00000000004fda86 in kvm_cpu_exec (env=<value optimized out>)
at /root/Linstall/kvm-62rc2/qemu/qemu-kvm.c:127
#3 0x00000000004fe5d5 in kvm_main_loop_cpu (env=0x2b82bb0)
at /root/Linstall/kvm-62rc2/qemu/qemu-kvm.c:307
#4 0x00000000004110fd in main (argc=44675488, argv=<value optimized out>)
at /root/Linstall/kvm-62rc2/qemu/vl.c:7862
===================================================
kvm statistics
efer_reload 0 0
exits 11387804 324872
fpu_reload 1340894 296
halt_exits 0 0
halt_wakeup 0 0
host_state_reload 1340931 295
hypercalls 0 0
insn_emulation 10053389 323534
insn_emulation_fail 10009814 323534
invlpg 0 0
io_exits 1334757 1004
irq_exits 0 0
irq_window 0 0
largepages 0 0
mmio_exits 27231 0
mmu_cache_miss 20 0
mmu_flooded 0 0
mmu_pde_zapped 0 0
mmu_pte_updated 0 0
mmu_pte_write 0 0
mmu_recycled 0 0
-Alexey, 3.3.2008.
----------------------------------------------------------------------
>Comment By: Jes Sorensen (jessorensen)
Date: 2011-03-03 16:06
Message:
Joerg moved this to https://bugzilla.kernel.org/show_bug.cgi?id=30402
----------------------------------------------------------------------
Comment By: Joerg Roedel (jroedel)
Date: 2008-03-03 17:54
Message:
Logged In: YES
user_id=2019182
Originator: NO
I was able to reproduce this problem. The instruction emulater lacks
support for mmx memory instructions. Needs to be fixed.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1906272&group_id=180599
--
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
