On 29.08.2013 08:02, Martin Kletzander wrote: > On 08/29/2013 12:07 AM, Vadim Bartko wrote: >> hi, >> >> >> I am trying to run Virt Manager and every time during VM creation i get >> these two errors: >> >> 1. (for kvm): >> >> libvirtError: Unable to read from monitor: Connection reset by peer >> >> 2. (for qemu): >> >> Unable to complete install: 'internal error process exited while connecting >> to monitor: char device redirected to /dev/pts/2 (label charserial0) >> Could not read keymap file: 'en-us >> > > These both just mean that qemu died while libvirt was trying to > communicate with it. > > What are your libvirt/qemu versions? Can you check > /var/log/libvirt/<machine_name>.log file to see what's in there? If In fact, the path is /var/log/libvirt/<hypervisor>/<machine_name>.log Since in this specific case hypervisor = "qemu", the path would be: /var/log/libvirt/qemu/<machine_name>.log > there's nothing relevant, I suggest enabling debugging [1], reproducing > and going through the logs again. > > Martin > > [1] http://libvirt.org/logging.html Or http://wiki.libvirt.org/page/DebugLogs Michal _______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
