On Tue, 16 Mar 2010, Michael Tokarev <m...@tls.msk.ru> wrote: > > When the path specified by -mem-path isn't writable the error message > > "mkstemp: Permission denied" is displayed on stderr - which means that it > > can't be seen until after the kvm session is ended when using the -curses > > option. > > Russell, it's the same thing as #574063 again. If you redirected stderr > to /dev/null, please don't complain that you see no useful error message.
But when an application redirects it's own output to /dev/null it's something that needs to be fixed - I've filed Debian bug reports about that before. > With -curses the current terminal is used for entirely different purpose > (guest output), and if you at the same time want to see stderr, redirect > it to a file or a pipe, or use some management software. Or kvm could use syslog or some other mechanism for logging such things. > Generally, and it applies to #574063 too, kvm lacks control over "failure > reaction": here when it is unable to allocate hugepages, and in #574063, > when it can't initialize /dev/kvm, and in some other cases, it currently > continues, but sometimes it is useful to stop here with error. There is > no way currently to tell kvm to turn such "warning" messages into fatal > errors. The lack of a way to turn warnings into fatal errors is a bug. Think of -Werror for C compilation. > By the way, 0-72 version as shipped in Lenny is a joke nowadays. It is > not a bad development snapshot, but it is still a development snapshot, > just like all other kvm-NN "releases" were. If you intend to play or > even use kvm, grab it from backports (it's called qemu-kvm there) - this > version is a bit closer to released software than kvm-72 in lenny. I for > one will not try to support it in any way, unless the same problem exists > in qemu-kvm-0.12. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574060 My first attempt at reporting such bugs involved reproducing some of them on Unstable, but unfortunately they got lost (see the above reportbug bug). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
