Russell Coker wrote: > Package: kvm > Version: 72+dfsg-5~lenny5 > Severity: normal > > 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. 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. 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. > Also the error message doesn't have an obvious meaning. Yes, this is a valid point, and I think I'll get it fixed. I'll close this bug if you don't have further points. 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. And thank you for bringing this option under my attention - I overlooked it somehow until you pointed me it. Very good thing! /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
