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.
Created attachment 670778[details]
logs
Description of problem:
Can not run vm
Thread-2800::ERROR::2012-12-31 03:56:39,811::vm::680::vm.Vm::(_startUnderlyingVm) vmId=`dd710948-2286-475b-8bc1-d6ac7b490cf1`::The vm start process failed
Traceback (most recent call last):
File "/usr/share/vdsm/vm.py", line 642, in _startUnderlyingVm
self._run()
File "/usr/share/vdsm/libvirtvm.py", line 1469, in _run
self._connection.createXML(domxml, flags),
File "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line 83, in wrapper
ret = f(*args, **kwargs)
File "/usr/lib64/python2.6/site-packages/libvirt.py", line 2645, in createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self)
Version-Release number of selected component (if applicable):
libvirt-0.10.2-13.el6.x86_64
vdsm-4.10.2-2.0.el6.x86_64
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
would you upgrade qemu from this 6.3 release to a fresh one from 6.4?
Note that the behavior is different from bug 890033, now itAnswering myself: it is something else, related to storage. Faulty udev rule, maybe?
libvirtError: internal error process exited while connecting to monitor: char device redirected to /dev/pts/0
qemu-kvm: -drive file=/rhev/data-center/a79e8adf-0dfd-43f7-aefa-2602f379dc72/fa0b80b0-3f76-4e91-afe7-75871a8d05b3/images/a1319efb-48ff-48dc-bc3e-82a439e2e35f/33082139-f3b5-4e09-8338-ea8af1c4bc7e,if=none,id=drive-ide0-0-0,format=qcow2,serial=a1319efb-48ff-48dc-bc3e-82a439e2e35f,cache=none,werror=stop,rerror=stop,aio=native: could not open disk image /rhev/data-center/a79e8adf-0dfd-43f7-aefa-2602f379dc72/fa0b80b0-3f76-4e91-afe7-75871a8d05b3/images/a1319efb-48ff-48dc-bc3e-82a439e2e35f/33082139-f3b5-4e09-8338-ea8af1c4bc7e: Operation not permitted
(In reply to comment #6)
> would you upgrade qemu from this 6.3 release to a fresh one from 6.4?
>
> Note that the behavior is different from bug 890033, now itAnswering myself:
> it is something else, related to storage. Faulty udev rule, maybe?
>
> libvirtError: internal error process exited while connecting to monitor:
> char device redirected to /dev/pts/0
> qemu-kvm: -drive
> file=/rhev/data-center/a79e8adf-0dfd-43f7-aefa-2602f379dc72/fa0b80b0-3f76-
> 4e91-afe7-75871a8d05b3/images/a1319efb-48ff-48dc-bc3e-82a439e2e35f/33082139-
> f3b5-4e09-8338-ea8af1c4bc7e,if=none,id=drive-ide0-0-0,format=qcow2,
> serial=a1319efb-48ff-48dc-bc3e-82a439e2e35f,cache=none,werror=stop,
> rerror=stop,aio=native: could not open disk image
> /rhev/data-center/a79e8adf-0dfd-43f7-aefa-2602f379dc72/fa0b80b0-3f76-4e91-
> afe7-75871a8d05b3/images/a1319efb-48ff-48dc-bc3e-82a439e2e35f/33082139-f3b5-
> 4e09-8338-ea8af1c4bc7e: Operation not permitted
My bad, host is rhel6.3 with the following versions:
vdsm-4.9.6-44.2.el6_3.x86_64
libvirt-0.9.10-21.el6_3.7.x86_64
qemu-kvm-rhev-0.12.1.2-2.295.el6_3.10.x86_64
qemu is reporting it cannot open the disk:
2012-12-31 01:56:39.810+0000: 21888: error : virNetClientProgramDispatchError:174 : internal error process exited while connecting to monitor: char device redirected to /dev/pts/0
qemu-kvm: -drive file=/rhev/data-center/a79e8adf-0dfd-43f7-aefa-2602f379dc72/fa0b80b0-3f76-4e91-afe7-75871a8d05b3/images/a1319efb-48ff-48dc-bc3e-82a439e2e35f/33082139-f3b5-4e09-8338-ea8af1c4bc7e,if=none,id=drive-ide0-0-0,format=qcow2,serial=a1319efb-48ff-48dc-bc3e-82a439e2e35f,cache=none,werror=stop,rerror=stop,aio=native: could not open disk image /rhev/data-center/a79e8adf-0dfd-43f7-aefa-2602f379dc72/fa0b80b0-3f76-4e91-afe7-75871a8d05b3/images/a1319efb-48ff-48dc-bc3e-82a439e2e35f/33082139-f3b5-4e09-8338-ea8af1c4bc7e: Operation not permitted
I can't see this problem anymore in the job. Maybe it was some dirty env. on the host.
Closing the bz and will reopen it if the issue will happen once again.
Comment 15Eduardo Warszawski
2013-02-20 14:00:49 UTC
*** Bug 906768 has been marked as a duplicate of this bug. ***
Created attachment 670778 [details] logs Description of problem: Can not run vm Thread-2800::ERROR::2012-12-31 03:56:39,811::vm::680::vm.Vm::(_startUnderlyingVm) vmId=`dd710948-2286-475b-8bc1-d6ac7b490cf1`::The vm start process failed Traceback (most recent call last): File "/usr/share/vdsm/vm.py", line 642, in _startUnderlyingVm self._run() File "/usr/share/vdsm/libvirtvm.py", line 1469, in _run self._connection.createXML(domxml, flags), File "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line 83, in wrapper ret = f(*args, **kwargs) File "/usr/lib64/python2.6/site-packages/libvirt.py", line 2645, in createXML if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self) Version-Release number of selected component (if applicable): libvirt-0.10.2-13.el6.x86_64 vdsm-4.10.2-2.0.el6.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: