[Bug 213155] possible kernel regression when running 11.x-RELEASE on KVM on AMD Opterons

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Oct 10 18:08:17 UTC 2017


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213155

Torfinn Ingolfsen <tingox+freebsd at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tingox+freebsd at gmail.com

--- Comment #19 from Torfinn Ingolfsen <tingox+freebsd at gmail.com> ---
(In reply to Martin Waschbüsch from comment #18)
I can confirm that FreeBSD 10.4-release (and FreeBSD 10.4-stable) is also
affected.
For reference, a FreeBSD 10.3-release guest boots fine with
virt-install --connect qemu:///system --name kvm1 --memory 512 --cpu host
--vcpus 1 --cdrom
/home/tingo/dl/bsd/fbsd/10.3/FreeBSD-10.3-RELEASE-amd64-disc1.iso
--os-variant=freebsd10.3 --disk size=6 --virt-type=kvm --network=default 
--console pty,target_type=virtio

for a FreeBSD 10.4 guest, I need --cpu kvm64 or --cpu Opteron_G3 to get it to
boot. If I use --cpu host, --cpu Opteron_G5 or --cpu Opteron_G4 it just hangs
after loading the kernel, just as the screenshot shows.
The host machine is running Debian 9.1:
tingo at kg-vm4:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 9.1 (stretch)
Release:        9.1
Codename:       stretch
tingo at kg-vm4:~$ uname -a
Linux kg-vm4 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19) x86_64
GNU/Linux

the host cpu is a A10-6700T
tingo at kg-vm4:~$ lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    2
Core(s) per socket:    2
Socket(s):             1
NUMA node(s):          1
Vendor ID:             AuthenticAMD
CPU family:            21
Model:                 19
Model name:            AMD A10-6700T APU with Radeon(tm) HD Graphics
Stepping:              1
CPU MHz:               1400.000
CPU max MHz:           2500.0000
CPU min MHz:           1400.0000
BogoMIPS:              4990.55
Virtualization:        AMD-V
L1d cache:             16K
L1i cache:             64K
L2 cache:              2048K
NUMA node0 CPU(s):     0-3
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb
rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf
eagerfpu 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 perfctr_nb cpb hw_pstate vmmcall bmi1 arat npt lbrv svm_lock
nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter
pfthreshold

FWIW, setting hw.use_xsave=0 in the guest before booting doesn't help, it still
hangs.

Also, If I install a FreeBSD 10.3-release guest and upgrade it to FreeBSD
10.4-stable (source, make world procedure) it hangs too (unsurprising, but
still).

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list