Russell Coker wrote:
On Tue, 16 Mar 2010, Michael Tokarev m...@tls.msk.ru wrote:
Or kvm could use syslog or some other mechanism for logging such things.
Where the error message will not be noticed either. With current
form it at least has a chance to be noticed after the guest exits.
On Thu, 18 Mar 2010, Michael Tokarev m...@tls.msk.ru wrote:
I see 3 issues here:
1) bad error message _text_. It's fixed (only partially, -- I've looked
at the thing again and see more cases where it'll throw as useful
error messages as this one -- I'll add/send more patches for
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
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 Coker wrote:
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
On Tue, 16 Mar 2010, Michael Tokarev m...@tls.msk.ru wrote:
Or kvm could use syslog or some other mechanism for logging such things.
Where the error message will not be noticed either. With current
form it at least has a chance to be noticed after the guest exits.
There is no requirement
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.
Also the error
7 matches
Mail list logo
