From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Fjellstrom Subject: Re: FreeBSD guest hogs cpu after disk delay? Date: Mon, 4 Jan 2010 08:06:15 -0700 Message-ID: <201001040806.15359.tfjellstrom@shaw.ca> References: <201001030131.46953.tfjellstrom@shaw.ca> <201001030143.52244.tfjellstrom@shaw.ca> Reply-To: tfjellstrom@shaw.ca Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit To: kvm@vger.kernel.org Return-path: Received: from idcmail-mo1so.shaw.ca ([24.71.223.10]:60404 "EHLO idcmail-mo1so.shaw.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753073Ab0ADPGU (ORCPT ); Mon, 4 Jan 2010 10:06:20 -0500 In-Reply-To: <201001030143.52244.tfjellstrom@shaw.ca> Sender: kvm-owner@vger.kernel.org List-ID: On Sun January 3 2010, Thomas Fjellstrom wrote: > On Sun January 3 2010, Thomas Fjellstrom wrote: > > I have a strange issue, one of my free bsd guests started using up 100% > > cpu and wouldnt respond in the console after a md-raid check started > > on the raid1 volume the vm has its lvm volumes on. About the only thing > > I could do was force the vm off, and restart it. In the guests console > > there was some kind of DMA warning/error related to the guest's disk > > saying it would retry, but it seems it never got that far. > > I forgot to mention, the host is running debian sid with kernel 2.6.31-1- > amd64, and kvm --version reports: > > QEMU PC emulator version 0.10.50 (qemu-kvm-devel-88) > > the hosts / and the vm volumes all sit on a lvm volume group, ontop of a > md- raid1 mirror of two Seagate 7200.12 500GB SATAII drives. > > The host is running 7 other guest which all seem to be running smoothly, > except both freebsd (pfSense) based guests which seemed to have locked up > after this message: > > ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=16183439 > > Though the second freebsd guest didn't seem to use up nearly as much cpu, > but it uses up far lower resources than the first. > No one have an idea whats going wrong? All of my virtio based linux guests stayed alive. But both of my FreeBSD guests using whatever "ide" in the - drive option sets locked up solid. -- Thomas Fjellstrom tfjellstrom@shaw.ca