Your message dated Fri, 29 Nov 2013 01:27:32 +0400 with message-id <[email protected]> and subject line Re: Bug#452235: qemu: silent data loss on 'savevm' has caused the Debian Bug report #452235, regarding qemu: silent data loss on 'savevm' 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.) -- 452235: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=452235 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: qemu Version: 0.9.0+20070816-1 Severity: important If an error happens during 'savevm', there is no error message of any kind. For example, if there are insufficient permissions to save the machine's state (very likely as -daemonize silently chdirs to /), there is visual feedback in the form of a long pause (failed open would fail immediately) and absolutely no information that an error occured. The state being saved often carries quite a lot of, possibly important, data or at least quite a time's worth of work in progress, often hard to save in other ways -- thus there's no excuse for not telling the user the save failed. Because of the discussion in #419929 I'm filing this as "important" even though the policy says this is a "serious" bug. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.18-5-vserver-686 (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 qemu depends on: ii bochsbios 2.3+20070705-2 BIOS for the Bochs emulator ii libasound2 1.0.15-2 ALSA library ii libc6 2.7-0exp8 GNU C Library: Shared libraries ii libncurses5 5.6+20071103-1 Shared libraries for terminal hand ii libsdl1.2debian 1.2.12-1 Simple DirectMedia Layer ii openbios-sparc 1.0~alpha2+20070816-1 SPARC Open Firmware ii openhackware 0.4.1-2 OpenFirmware emulator for PowerPC ii proll 18-2 JavaStation PROM 2.x compatible re ii vgabios 0.6a-3 VGA BIOS software for the Bochs an ii zlib1g 1:1.2.3.3.dfsg-7 compression library - runtime Versions of packages qemu recommends: ii debootstrap 1.0.7 Bootstrap a basic Debian system ii sharutils 1:4.6.3-1 shar, unshar, uuencode, uudecode ii vde2 2.1.6+r154-1+b1 Virtual Distributed Ethernet -- no debconf information
--- End Message ---
--- Begin Message ---Version: 1.1.2+dfsg-1 [Replying to an old bugreport] 21.11.2007 11:30, Adam Borowski wrote: > Package: qemu > Version: 0.9.0+20070816-1 > Severity: important > > If an error happens during 'savevm', there is no error message of any kind. > For example, if there are insufficient permissions to save the machine's > state (very likely as -daemonize silently chdirs to /), there is visual > feedback in the form of a long pause (failed open would fail immediately) > and absolutely no information that an error occured. > > The state being saved often carries quite a lot of, possibly important, data > or at least quite a time's worth of work in progress, often hard to save in > other ways -- thus there's no excuse for not telling the user the save > failed. Lots of changes has been made since version 0.9 of qemu. Actually, at least _some_ error handling has been there since the day one, when Fabrice added multiple snapshots support -- when something goes wrong during savevm, you should see on the monitor: term_printf("Error %d while writing VM\n", ret); This was in the commit which _introduced_ snapshots to start with: commit faea38e7863a6e29f110063388eb93840fcd475c Author: bellard <bellard@c046a42c-6fe2-441c-8c8c-71466251a162> Date: Sat Aug 5 21:31:00 2006 +0000 Maube not all places actually reported error conditions properly at that time, that very well could be the case. However, since that time, as I already mentioned, lots of things changed. I verified wheezy qemu - it looks like it handles i/o errors during snapshot creation (and other qcow2 manipulations) correctly now. So I'm closing this bugreport with wheezy version. Thanks, /mjt
--- End Message ---
