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 496032[details]
logs
Description of problem:
disabling ido domain during guest migration will cause the below error
Thread-27::ERROR::2011-05-01 10:36:01,001::utils::526::vm.Vm::(collect) vmId=`684441d6-cfc2-4e11-86b3-4cac418f7a18`::Stats function failed: <AdvancedStatsFunction _highWrite at
0x1a7ca08>
Version-Release number of selected component (if applicable):
ic114
root@blond-vdsg vdsm]# rpm -qa |grep vdsm
vdsm-4.9-63.el6.x86_64
vdsm-debug-plugin-4.9-63.el6.x86_64
vdsm-cli-4.9-63.el6.x86_64
vdsm-debuginfo-4.9-63.el6.x86_64
[root@blond-vdsg vdsm]# rpm -qa |grep libvirt
libvirt-0.8.7-18.el6.x86_64
libvirt-client-0.8.7-18.el6.x86_64
libvirt-python-0.8.7-18.el6.x86_64
libvirt-debuginfo-0.8.7-18.el6.x86_64
libvirt-devel-0.8.7-18.el6.x86_64
[root@blond-vdsg vdsm]# rpm -qa |grep qemu
gpxe-roms-qemu-0.9.7-6.7.el6.noarch
qemu-kvm-0.12.1.2-2.152.el6.x86_64
qemu-img-0.12.1.2-2.152.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. create guest with cd attached in boot
2. run VM
3. migrate VM
4. put ISO domain in maintenance while VM is migrating
Actual results:
we will get an error from vdsm:
Thread-27::ERROR::2011-05-01 10:36:01,001::utils::526::vm.Vm::(collect) vmId=`684441d6-cfc2-4e11-86b3-4cac418f7a18`::Stats function failed: <AdvancedStatsFunction _highWrite at
0x1a7ca08>
Expected results:
deactivating ISO domain should have no effect in rhev
Additional info:logs
to add user experience:
I tested on 3 VM's: 1 migrated with no errors, one was put in pause and I tried to start it became non-responsive and the third failed migration
Note that the source shows all kinds of errors, due to bug 701106.
Federico, any idea why vdsm/utils:526 does not log any backtrace?
Comment 3Federico Simoncelli
2011-05-04 14:05:46 UTC
Dan, I suppose the problem is in the SimpleLogAdapter (logUtils.py:5).
The backtrace is back if in vdsm/vm.py:492 you comment out:
self.log = SimpleLogAdapter(self.log, {"vmId" : self.conf['vmId']})
On Sun, May 15, 2011 at 09:58:53AM +0300, Dafna Ron wrote:
> can you put this on_QA + build?
> I just have a lot of bugs so I don't want this to fall between the cracks.
Done, thanks.
verified on vdsm-4.9-67.el6.x86_64
error is:
Thread-21302::ERROR::2011-05-18 19:29:55,929::guestIF::300::vm.Vm::(run) vmId=`55e2084c-e9de-489e-991d-eb402b7b5f2f`::Unexpected exception: Traceback (most recent call last):
4c815194-f3e2-4572-ba77-d69b68d99ede::ERROR::2011-05-18 19:30:00,141::vm::1541::vm.Vm::(cont) vmId=`55e2084c-e9de-489e-991d-eb402b7b5f2f`::cannot cont while Down
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHEA-2011-1782.html
Created attachment 496032 [details] logs Description of problem: disabling ido domain during guest migration will cause the below error Thread-27::ERROR::2011-05-01 10:36:01,001::utils::526::vm.Vm::(collect) vmId=`684441d6-cfc2-4e11-86b3-4cac418f7a18`::Stats function failed: <AdvancedStatsFunction _highWrite at 0x1a7ca08> Version-Release number of selected component (if applicable): ic114 root@blond-vdsg vdsm]# rpm -qa |grep vdsm vdsm-4.9-63.el6.x86_64 vdsm-debug-plugin-4.9-63.el6.x86_64 vdsm-cli-4.9-63.el6.x86_64 vdsm-debuginfo-4.9-63.el6.x86_64 [root@blond-vdsg vdsm]# rpm -qa |grep libvirt libvirt-0.8.7-18.el6.x86_64 libvirt-client-0.8.7-18.el6.x86_64 libvirt-python-0.8.7-18.el6.x86_64 libvirt-debuginfo-0.8.7-18.el6.x86_64 libvirt-devel-0.8.7-18.el6.x86_64 [root@blond-vdsg vdsm]# rpm -qa |grep qemu gpxe-roms-qemu-0.9.7-6.7.el6.noarch qemu-kvm-0.12.1.2-2.152.el6.x86_64 qemu-img-0.12.1.2-2.152.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. create guest with cd attached in boot 2. run VM 3. migrate VM 4. put ISO domain in maintenance while VM is migrating Actual results: we will get an error from vdsm: Thread-27::ERROR::2011-05-01 10:36:01,001::utils::526::vm.Vm::(collect) vmId=`684441d6-cfc2-4e11-86b3-4cac418f7a18`::Stats function failed: <AdvancedStatsFunction _highWrite at 0x1a7ca08> Expected results: deactivating ISO domain should have no effect in rhev Additional info:logs