graphic: 0.854
other: 0.849
device: 0.793
socket: 0.723
KVM: 0.691
performance: 0.684
network: 0.674
PID: 0.640
debug: 0.638
files: 0.529
permissions: 0.521
semantic: 0.388
vnc: 0.386
boot: 0.326

can not run vm with a serial port

environment:
server: centOS 6.5, 3.14.19, x86_64
qemu-kvm: QEMU PC emulator version 0.12.1 (qemu-kvm-0.12.1.2), Copyright (c) 2003-2008 Fabrice Bellard
qemu-system-x86_64 :QEMU emulator version 1.2.0 (qemu-kvm-1.2.0), Copyright (c) 2003-2008 Fabrice Bellard
virt-manager: 0.9.0

VM: centOS 6.5, 3.12.30, x86_64

reproduce step:
1. add serial device
2. select device type: unix socket
                 device parameters: path=/dev/ttyS0
                                                       mode=client mode(connect)
3. run the VM

phenomenon:
Error starting domain: internal error process exited while connecting to monitor: qemu-kvm: -chardev socket,id=charserial0,path=/dev/ttyS0,server,nowait: socket bind failed: Address already in use
qemu-kvm: -chardev socket,id=charserial0,path=/dev/ttyS0,server,nowait: chardev: opening backend "socket" failed


Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 44, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/domain.py", line 1114, in startup
    self._backend.create()
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 678, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error process exited while connecting to monitor: qemu-kvm: -chardev socket,id=charserial0,path=/dev/ttyS0,server,nowait: socket bind failed: Address already in use
qemu-kvm: -chardev socket,id=charserial0,path=/dev/ttyS0,server,nowait: chardev: opening backend "socket" failed

Opening a socket with the name of a device file can not work, you've got to specify a different name for a unix socket instead. So this is not a bug.

(or if you just wanted to complain about the rather ugly traceback instead of a nice error message: Please file a bug against virt-manager instead. Thanks!)