Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When I try to start an existing virtual machine I get this error:
Error starting domain: internal error: process exited while connecting to monitor: ((null):10592): Spice-Warning **: reds.c:3066:reds_init_socket: reds_init_socket: binding socket to 127.0.0.1:5900 failed
qemu-kvm: failed to initialize spice server
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 100, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 122, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1220, in startup
self._backend.create()
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 698, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error: process exited while connecting to monitor: ((null):10592): Spice-Warning **: reds.c:3066:reds_init_socket: reds_init_socket: binding socket to 127.0.0.1:5900 failed
qemu-kvm: failed to initialize spice server
Version-Release number of selected component (if applicable):
virt-manager-0.10.0-7.el7.noarch
How reproducible:
100%
Steps to Reproduce:
1. run virt-manager
2. try to run a virt-machine
Actual results:
error
Expected results:
running virt machine
Additional info:
Comment 1Martin Kletzander
2013-11-26 15:37:25 UTC
Any reason for the description to be private?
What is the configuration of the machine, did you change anything? Can you add libvirt, spice and qemu versions? Also please attach the xml of that domain (obtainable by virsh dumpxml <domain>. Thanks.
No special reason for private, i have private as a default and I forgot to un-check it.
No configuration changes since it was working. Only updates. But I was not using it for a few weeks.
libvirt-1.1.1-13.el7.x86_64
qemu-kvm-1.5.3-19.el7.x86_64
spice-server-0.12.4-3.el7.x86_64
my virt machines are on QEMU. I have 3 of them 2 rhel 7 and 1 rhel 6.5.
i can see no domain in virsh list
# virsh list
Id Name State
----------------------------------------------------
but i can see my machines in virt-manager in > localost(QEMU)
libvirtd is running
# service libvirtd status
Redirecting to /bin/systemctl status libvirtd.service
libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled)
Active: active (running) since Wed 2013-11-27 08:52:50 CET; 11min ago
Main PID: 4701 (libvirtd)
CGroup: /system.slice/libvirtd.service
├─2647 /sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/network1.conf
├─4701 /usr/sbin/libvirtd
└─4857 /sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf
It is possible that I'm doing something wrong. I'm just user beginner of virtualization tools
Description of problem: When I try to start an existing virtual machine I get this error: Error starting domain: internal error: process exited while connecting to monitor: ((null):10592): Spice-Warning **: reds.c:3066:reds_init_socket: reds_init_socket: binding socket to 127.0.0.1:5900 failed qemu-kvm: failed to initialize spice server Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 100, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 122, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1220, in startup self._backend.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 698, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: internal error: process exited while connecting to monitor: ((null):10592): Spice-Warning **: reds.c:3066:reds_init_socket: reds_init_socket: binding socket to 127.0.0.1:5900 failed qemu-kvm: failed to initialize spice server Version-Release number of selected component (if applicable): virt-manager-0.10.0-7.el7.noarch How reproducible: 100% Steps to Reproduce: 1. run virt-manager 2. try to run a virt-machine Actual results: error Expected results: running virt machine Additional info: