Your message dated Sat, 12 Dec 2009 16:25:45 +0100
with message-id <[email protected]>
and subject line Works with kvm 88
has caused the Debian Bug report #537569,
regarding kvm: -no-shutdown exits KVM on guest shutdown
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
537569: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537569
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: kvm
Version: 85+dfsg-4
Severity: critical
Justification: causes serious data loss
The kvm program is described in its manpage and everywhere else as
being based on QEMU. kvm(1) points to kvm-qemu(1) for instructions on
invocation. kvm-qemu(1) says:
-no-shutdown
Don’t exit QEMU on guest shutdown, but instead only stop
the emulation. This allows for instance switching to
monitor to commit changes to the disk image.
On my system, this does not seem to actually do anything.
Test set of arguments:
$ kvm -drive media=disk,index=0,format=qcow2,file=foo.qcow \
-boot c -m 256 -no-shutdown -snapshot
with foo.qcow, in my case, being a bootable image of Debian lenny for
AMD64 architecture (same as my host architecture). Creating some
files inside the guest, and then running shutdown -h from the guest,
causes KVM to exit without giving me any chance to commit the disk
changes as the manual page said it would. The disk changes are now
apparently gone forever; starting the virtual machine again does not
show them.
My original command line contained some additional arguments for kvm,
namely << -no-quit -monitor stdio -net nic,vlan=0 -net user,vlan=0 >>,
but this does not appear to affect the results. Switching the order
of the -snapshot and -no-shutdown arguments does not appear to affect
the results.
I believe that causing written pieces of a virtual disk to disappear
when the user expects to be able to input a commit command next
constitutes serious loss of user data, which justifies the critical
severity at which I am reporting this.
Thanks in advance for any attention.
---> Drake Wilson
-- Package-specific info:
selected information from lshal(1):
/proc/cpuinfo:
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 75
model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
stepping : 2
cpu MHz : 2209.855
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm
3dnowext 3dnow rep_good pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy
bogomips : 4419.71
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc
processor : 1
vendor_id : AuthenticAMD
cpu family : 15
model : 75
model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
stepping : 2
cpu MHz : 2209.855
cache size : 512 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm
3dnowext 3dnow rep_good pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy
bogomips : 4420.30
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.29-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages kvm depends on:
ii adduser 3.110 add and remove users and groups
ii bridge-utils 1.4-5 Utilities for configuring the Linu
ii iproute 20090324-1 networking and traffic control too
ii libasound2 1.0.20-2 shared library for ALSA applicatio
ii libbluetooth3 4.42-2 Library to use the BlueZ Linux Blu
ii libbrlapi0.5 4.0-6 braille display access via BRLTTY
ii libc6 2.9-13 GNU C Library: Shared libraries
ii libgnutls26 2.6.6-1 the GNU TLS library - runtime libr
ii libncurses5 5.7+20090607-1 shared libraries for terminal hand
ii libpci3 1:3.1.3-1 Linux PCI Utilities (shared librar
ii libpulse0 0.9.15-4 PulseAudio client libraries
ii libsdl1.2debian 1.2.13-4+b1 Simple DirectMedia Layer
ii libvdeplug2 2.2.2-3 Virtual Distributed Ethernet - Plu
ii libx11-6 2:1.2.1-1 X11 client-side library
ii python 2.5.4-2 An interactive high-level object-o
ii zlib1g 1:1.2.3.3.dfsg-14 compression library - runtime
Versions of packages kvm recommends:
ii linux-image-2.6.27.1 [linux-i drache.1.0 Linux kernel binary image for vers
ii linux-image-2.6.29-1-amd64 [l 2.6.29-3 Linux 2.6.29 image on AMD64
Versions of packages kvm suggests:
ii debootstrap 1.0.13 Bootstrap a basic Debian system
ii hal 0.5.12~git20090406.46dc48-2 Hardware Abstraction Layer
pn kvm-source <none> (no description available)
pn samba <none> (no description available)
ii vde2 2.2.2-3 Virtual Distributed Ethernet
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 88+dfsg-2
Package: kvm
Hi,
this works for me with kvm 88.
Cheers,
-- Guido
--- End Message ---
