Your message dated Wed, 17 Jan 2007 23:08:01 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug closed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: kvm
Version: 7-1
Severity: grave
Justification: renders package unusable
The version of kvm currently in testing, kvm-7, has many known stability bugs
that have
been fixed in later upstream versions. These cause the guest operating system
to crash,
possibly causing data loss etc. The following Google search provides a brief
overview of
the number of patches and severity of these bugs, of which none is entered in
the Debian
BTS:
http://www.google.com/search?q=linux-kernel+PATCH+KVM+%22Avi+Kivity%22+site%3Alkml.org
Another factor is that the current maintainer is currently sick. I have been
in touch with
him and prepared an upgraded package [1] based on the current upstream kvm-11,
which could
in theory be used for Etch, but Etch is of course frozen. The amount of changes
in
upstream is big by release standards.
I see two solutions (both are fine with me):
1) Remove kvm-7 from Etch
or 2) Upgrade kvm to kvm-11, if okayed by the release team and pending
sponsoring
(While not really a factor in the decision, kvm-11 also includes major
performance
improvements, the MMU optimization, described as "the difference between a
working proof
of concept and a generally usable system" [2] The last patch set [3] fixes the
known
problems exposed by the MMU optimization and is included in kvm-11, although
not yet
applied in Linux-2.6.20-rc5.)
[1] My kvm-11 package will be uploaded to mentors.debian.net today or tomorrow
for
review and sponsoring.
[2] http://lkml.org/lkml/2007/1/4/175
[3] http://lkml.org/lkml/2007/1/11/51
--- End Message ---
--- Begin Message ---
Version: 11-1
kvm (11-1) unstable; urgency=high
* New upstream version. Closes #406800, #406275, #404075.
* This version fixes many stability issues in earlier versions of KVM.
* Automatically create group kvm on installation of package kvm
* Added udev support to automatically set group kvm on /dev/kvm
* Added reportbug script (/usr/share/bug/kvm) so some info that
might be relevant gets included automatically.
* Tell module-assistant about the kvm-source package, so it shows up
in the module selection menu.
* Add information on building the modules using module-assistant.
* Add /etc/kvm/kvm-ifup script (conffile) to bring up the network for
the VM in a simpler way, see the manual page for kvm for description.
This used to be /etc/qemu-ifup, as installed by the qemu package.
* Depend on iproute, bridge-utils, used by kvm-ifup and the upcoming
/etc/init.d script.
* Remove non-x86 bios images - KVM is only meaningful for x86 guests.
* Keep KVM bios files in /usr/share/kvm, rather than sharing them with
other packages as the KVM bios is different (also avoids unexpected
bios updates).
* Don't depend on qemu, as we now keep our own bios.
* Recommend kvm-source, qemu (mostly for qemu-img), vde2 and linux-image-2.6.
* Suggest sudo and debootstrap.
* For kvm-source, depend on linux-headers-2.6 | linux-source-2.6,
recommend linux-image-2.6 and suggest module-assistant and
kernel-package.
* Use quilt to handle patches.
* More detailed package description for kvm, added Homepage:.
-- Leonard Norrgard <[EMAIL PROTECTED]> Sun, 14 Jan 2007 07:11:03 +0200
--- End Message ---
