From: Michael Tokarev <mjt@tls.msk.ru>
To: Thomas Mueller <thomas@chaschperli.ch>
Cc: kvm@vger.kernel.org
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 [thread overview]
Message-ID: <4C62FE64.2090207@msgid.tls.msk.ru> (raw)
In-Reply-To: <i3ungt$gdc$3@dough.gmane.org>
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
next prev parent reply other threads:[~2010-08-11 19:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 14:29 Debian 5.0 host, qemu-kvm 0.12.4, unable to use -smp > 1 Freddie Cash
2010-08-11 14:52 ` Freddie Cash
2010-08-11 16:32 ` Gleb Natapov
2010-08-11 17:18 ` Freddie Cash
2010-08-11 17:34 ` Thomas Mueller
2010-08-11 17:41 ` Michael Tokarev
2010-08-11 17:43 ` Thomas Mueller
2010-08-11 19:47 ` Michael Tokarev [this message]
2010-08-11 18:39 ` Michael Tokarev
2010-08-11 18:46 ` Freddie Cash
2010-08-11 19:23 ` Freddie Cash
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C62FE64.2090207@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=kvm@vger.kernel.org \
--cc=thomas@chaschperli.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox