Bug#560853: #560853: qemu-kvm: embeds qemu and kvm

2009-12-30 Thread Michael Gilbert
On Thu, 31 Dec 2009 00:54:21 +0300 Michael Tokarev wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Michael,
> 
> You states that "your package embeds source code from
> both qemu and kvm".  This is wrong.  Kvm *is* qemu, just
> another variant of it, modifications to qemu to support
> native CPU execution on CPUs with virtualization extensions.
> 
> The two projects, while very close to each other, are
> separate.  Kvm pushes changes back to qemu, but currently
> acts like "staging area" for the kvm-related features,
> before they're pushed to qemu.
> 
> The end goal is to have only one project, qemu.  But as
> of now, it isn't the case.
> 
> So we've 3 choices in Debian:
> 
>  a) do not provide kvm(*) at all.  This is wrong, since
>   the project is very useful (qemu in its current form
>   does not work as well).  Note that first goal of
>   Debian is its users.
> 
>  b) do not provide qemu but package only kvm.  This does
>   not work right, since kvm version does not care that
>   much about other architectures, focusing only on kvm-
>   related features and often breaking other things,
>   including running on x86 without kvm enabled.  Yes
>   that's bugs, but they're of lower priority for kvm.
> 
>  c) package both and wait till either the two projects
>   merges or when b) will be more appropriate than now.
> 
> (*) By "kvm" here and everywhere I mean either "kvm" or
> "qemu-kvm" which is the same thing but one is development
> snapshots and another is stable series.
> 
> I think we're doing the best thing possible at this time --
> providing both and letting the user to choose which one
> works best for him: if he wants native virtualisation
> here's kvm, if he wants to emulate other architecture,
> it's qemu.
> 
> But in any way, saying that the project "embeds both
> qemu and kvm" is wrong, since, again, kvm *is* qemu.

right, the intention for submitting this bug was to track the fact that
code from both projects exists in this package.  it is ok for it to be
that way, but it is also good to track that fact.  it is nice to hear
that there is some work being done to merge the code, and this bug can
be closed when that is finally the case.

mike



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#560853: #560853: qemu-kvm: embeds qemu and kvm

2009-12-30 Thread Michael Tokarev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Michael,

You states that "your package embeds source code from
both qemu and kvm".  This is wrong.  Kvm *is* qemu, just
another variant of it, modifications to qemu to support
native CPU execution on CPUs with virtualization extensions.

The two projects, while very close to each other, are
separate.  Kvm pushes changes back to qemu, but currently
acts like "staging area" for the kvm-related features,
before they're pushed to qemu.

The end goal is to have only one project, qemu.  But as
of now, it isn't the case.

So we've 3 choices in Debian:

 a) do not provide kvm(*) at all.  This is wrong, since
  the project is very useful (qemu in its current form
  does not work as well).  Note that first goal of
  Debian is its users.

 b) do not provide qemu but package only kvm.  This does
  not work right, since kvm version does not care that
  much about other architectures, focusing only on kvm-
  related features and often breaking other things,
  including running on x86 without kvm enabled.  Yes
  that's bugs, but they're of lower priority for kvm.

 c) package both and wait till either the two projects
  merges or when b) will be more appropriate than now.

(*) By "kvm" here and everywhere I mean either "kvm" or
"qemu-kvm" which is the same thing but one is development
snapshots and another is stable series.

I think we're doing the best thing possible at this time --
providing both and letting the user to choose which one
works best for him: if he wants native virtualisation
here's kvm, if he wants to emulate other architecture,
it's qemu.

But in any way, saying that the project "embeds both
qemu and kvm" is wrong, since, again, kvm *is* qemu.

Thanks.

/mjt
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iJwEAQECAAYFAks7zA0ACgkQUlPFrXTwyDhsVQP8DNAcJmwD9LPtunvioCuamQog
5e8inrRzj/zLaXlsb2SsV2Np2Em35Fv9laznO7JmkTlCfsPjAExRzf1hlmCdBD1r
zGhgtmQJLgBfE+CThHjvUN5QJg2t3La7Fg7bPOcTxuc/cOx/Ff+nrYpyuI+9ISYL
/Q5QW0PpzVcmIkeVDXU=
=G/Z6
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org