From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tokarev Subject: Re: Debian 5.0 host, qemu-kvm 0.12.4, unable to use -smp > 1 Date: Wed, 11 Aug 2010 23:47:48 +0400 Message-ID: <4C62FE64.2090207@msgid.tls.msk.ru> References: <20100811163226.GA12613@redhat.com> <4C62E0E3.3060108@msgid.tls.msk.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Thomas Mueller Return-path: Received: from isrv.corpit.ru ([86.62.121.231]:48597 "EHLO isrv.corpit.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756279Ab0HKTry (ORCPT ); Wed, 11 Aug 2010 15:47:54 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: 11.08.2010 21:43, Thomas Mueller wrote: > Am Wed, 11 Aug 2010 21:41:55 +0400 schrieb Michael Tokarev: >> Please, pretty pretty please already, forget about kvm-NN releases. >> They're dead long time ago. bpo provides 0.12.4 now, and used to have >> 0.11 when it was current. Note the subject says the same thing... > > why not ad a "Conflicts: kvm-source" to qemu-kvm ? Because it's not qemu-kvm who conflicts with old kvm-source (kernel module). It is kvm-source that breaks _kernel_, not qemu-kvm. Because one may install kvm-source, upgrade to new kernel (kvm-source will break it by replacing kvm modules with older, non-functional ones), and later install qemu-kvm. The kernel is already broken, even if kvm-source is removed during qemu-kvm install. So it should be the kernel to conflict with kvm-source. Note that even lenny's kernel modules are more recent than kvm-72. In any way, it's Debian-specific issue, not very interesting to most readers of kvm@vger. Thanks! /mjt