user-level: 0.831
graphic: 0.820
network: 0.820
permissions: 0.818
architecture: 0.813
semantic: 0.804
risc-v: 0.794
peripherals: 0.793
debug: 0.787
kernel: 0.778
KVM: 0.770
PID: 0.762
vnc: 0.762
device: 0.760
register: 0.751
virtual: 0.750
performance: 0.749
mistranslation: 0.746
socket: 0.733
assembly: 0.729
arm: 0.725
ppc: 0.725
x86: 0.717
hypervisor: 0.701
TCG: 0.700
VMM: 0.697
boot: 0.638
files: 0.633
i386: 0.632

kvm smb server hogs cpu guest freeze

Binary package hint: qemu-kvm

kvm hogs the CPU reproducibly. I installed an Ubuntu using KVM. I run the machine with -net nic,model=rtl8139,macaddr=f0:00:BA:12:34:56 -net user,hostfwd=tcp::2223-:22,smb=/tmp/share, sshed into the machine and typed "telnet 10.0.2.4 139" to try whether the SMB server works. KVM then hogs the CPU.

ProblemType: Bug
Architecture: amd64
Date: Thu Nov  5 01:23:09 2009
DistroRelease: Ubuntu 9.10
KvmCmdLine: Error: command ['ps', '-C', 'kvm', '-F'] failed with exit code 1: UID        PID  PPID  C    SZ   RSS PSR STIME TTY          TIME CMD
MachineType: LENOVO 766636G
Package: kvm 1:84+dfsg-0ubuntu16+0.11.0+0ubuntu6.3
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=/dev/mapper/cryptroot source=UUID=9c3d5596-27c6-4fd5-bfcd-fa8eef6f1230 ro quiet splash  crashkernel=384M-2G:64M,2G-:128M
SourcePackage: qemu-kvm
Uname: Linux 2.6.32-999-generic x86_64
dmi.bios.date: 07/01/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 7NETB6WW (2.16 )
dmi.board.name: 766636G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7NETB6WW(2.16):bd07/01/2008:svnLENOVO:pn766636G:pvrThinkPadX61s:rvnLENOVO:rn766636G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 766636G
dmi.product.version: ThinkPad X61s
dmi.sys.vendor: LENOVO



Thanks for your bug report and for your contribution to ubuntu. Does kvm hogs the CPU if you're not connecting to the smb server? How much memory is allocated to the guest?

No it does not hog the CPU if I'm not triggering it the way I described. I run the machine with 512 megs.

I was able to reproduce this in the way described, marking confirmed.

I'm totally not familiar with the smb option, having never used it.  I'm lowering the priority from Medium -> Low, since smb is not one of the most critical kvm features.

I'm also forwarding the bug upstream.  Anthony, this bug is totally reproducible on qemu-kvm 0.12.3, as described in the initial report.  Can you confirm it against upstream code?  Are the invocations/options correct?  Is this expected to work?

Triaging old bug tickets... Can you still reproduce this behavior with the latest version, or has the problem been fixed now?

There hasn't been a reply to my question in the last comment within months, so I assume nobody cares about this anymore. So I'm closing this ticket now...

Clearing old bugs: No more occurring in any of my recent KVMs, setting this old bug to incomplete.

[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60 days.]