Difference between revisions of "Libvirt error messages in journald"
Jump to navigation
Jump to search
(4 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | + | [[journalctl]] -r | grep [[libvirt]] | grep error | |
− | + | journalctl -r | grep [[libvirt-guests.sh]] | |
− | |||
Line 11: | Line 10: | ||
* internal error: | * internal error: | ||
** qemu unexpectedly closed the monitor | ** qemu unexpectedly closed the monitor | ||
− | ** End of file from qemu monitor | + | ** [[End of file from qemu monitor]] |
** connection closed due to keepalive timeout | ** connection closed due to keepalive timeout | ||
** process exited while connecting to monitor | ** process exited while connecting to monitor | ||
Line 21: | Line 20: | ||
* unknown procedure | * unknown procedure | ||
* Unable to read from monitor: Connection reset by peer | * Unable to read from monitor: Connection reset by peer | ||
+ | |||
+ | == Related pages == | ||
+ | * [[Journalctl -u libvirtd]] | ||
+ | |||
Latest revision as of 08:53, 29 September 2020
journalctl -r | grep libvirt | grep error journalctl -r | grep libvirt-guests.sh
Errors[edit]
- Cannot allocate memory
- No space left on device
- Failed to get shared "write" lock
- Operation failed: Storage source conflict with pool
- internal error:
- qemu unexpectedly closed the monitor
- End of file from qemu monitor
- connection closed due to keepalive timeout
- process exited while connecting to monitor
- End of file while reading data: Input/output error
- Failed to acquire pid file
- argument unsupported
- Operation not supported
- unknown procedure
- Unable to read from monitor: Connection reset by peer
Related pages[edit]
See also[edit]
Advertising: