This is a multi-part message in MIME format.
--------------040706080902050106070109
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hi,
Just curiously, did you install oVirt packages from
http://resources.ovirt.org/releases/nightly/rpm/EL/6/noarch/ ?
And there is no stable oVirt release 3.1/3.2 for RHEL.
Dead Horse:
The nodes are EL6.3 based.
Currently installed libvirt packages:
libvirt-lock-sanlock-0.9.10-21.el6_3.8.x86_64
libvirt-cim-0.6.1-3.el6.x86_64
libvirt-0.9.10-21.el6_3.8.x86_64
libvirt-python-0.9.10-21.el6_3.8.x86_64
libvirt-client-0.9.10-21.el6_3.8.x86_64
and qemu packages:
qemu-kvm-0.12.1.2-2.295.el6_3.10.x86_64
qemu-kvm-tools-0.12.1.2-2.295.el6_3.10.x86_64
qemu-img-0.12.1.2-2.295.el6_3.10.x86_64
Thus my presumption here given the above is that
virDomainMigrateToURI2 has not yet been patched and/or back-ported
into the EL6.x libvirt/qemu?
virDomainMigrateToURI2() is supported in libvirt-0.9.10, I am not sure
if qemu-kvm-0.12.1.2 supports it.
/var/log/libvirtd.log may help to verify this assumption
- DHC
On Wed, Jan 30, 2013 at 1:28 PM, Dan Kenigsberg <danken(a)redhat.com
<mailto:danken@redhat.com>> wrote:
On Wed, Jan 30, 2013 at 11:04:00AM -0600, Dead Horse wrote:
> Engine Build --> Commit: 82bdc46dfdb46b000f67f0cd4e51fc39665bf13b
> VDSM Build: --> Commit: da89a27492cc7d5a84e4bb87652569ca8e0fb20e
+ patch
> -->
http://gerrit.ovirt.org/#/c/11492/
>
> Engine Side:
> 2013-01-30 10:56:38,439 ERROR
> [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo]
> (QuartzScheduler_Worker-70) Rerun vm
887d764a-f835-4112-9eda-836a772ea5eb.
> Called from vds lostisles
> 2013-01-30 10:56:38,506 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand]
> (pool-3-thread-49) START, MigrateStatusVDSCommand(HostName =
lostisles,
> HostId = e042b03b-dd4e-414c-be1a-b2c65ac000f5,
> vmId=887d764a-f835-4112-9eda-836a772ea5eb), log id: 6556e75b
> 2013-01-30 10:56:38,510 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand]
> (pool-3-thread-49) Failed in MigrateStatusVDS method
> 2013-01-30 10:56:38,510 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand]
> (pool-3-thread-49) Error code migrateErr and error message
> VDSGenericException: VDSErrorException: Failed to
MigrateStatusVDS, error =
> Fatal error during migration
> 2013-01-30 10:56:38,511 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand]
> (pool-3-thread-49) Command
>
org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand
return
> value
> StatusOnlyReturnForXmlRpc [mStatus=StatusForXmlRpc [mCode=12,
> mMessage=Fatal error during migration]]
>
>
> VDSM Side:
> Thread-43670::ERROR::2013-01-30
10:56:37,052::vm::200::vm.Vm::(_recover)
> vmId=`887d764a-f835-4112-9eda-836a772ea5eb`::this function is
not supported
> by the connection driver: virDomainMigrateToURI2
> Thread-43670::ERROR::2013-01-30 10:56:37,513::vm::288::vm.Vm::(run)
> vmId=`887d764a-f835-4112-9eda-836a772ea5eb`::Failed to migrate
> Traceback (most recent call last):
> File "/usr/share/vdsm/vm.py", line 273, in run
> self._startUnderlyingMigration()
> File "/usr/share/vdsm/libvirtvm.py", line 504, in
> _startUnderlyingMigration
> None, maxBandwidth)
> File "/usr/share/vdsm/libvirtvm.py", line 540, in f
> ret = attr(*args, **kwargs)
> File
"/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line
> 111, in wrapper
> ret = f(*args, **kwargs)
> File "/usr/lib64/python2.6/site-packages/libvirt.py", line
1103, in
> migrateToURI2
> if ret == -1: raise libvirtError ('virDomainMigrateToURI2()
failed',
> dom=self)
> libvirtError: this function is not supported by the connection
driver:
> virDomainMigrateToURI2
Could it be that you are using an ancient libvirt with no
virDomainMigrateToURI2? What are your libvirt and qemu-kvm
versions (on
both machines)?
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
---
?? Shu Ming
Open Virtualization Engineerning; CSTL, IBM Corp.
Tel: 86-10-82451626 Tieline: 9051626 E-mail: shuming(a)cn.ibm.com or
shuming(a)linux.vnet.ibm.com
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193,
PRC
--------------040706080902050106070109
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi,<br>
<br>
Just curiously, did you install oVirt packages from
<a class="moz-txt-link-freetext"
href="http://resources.ovirt.org/releases/nightly/rpm/EL/6/noarch/&q...;
?<br>
And there is no stable oVirt release 3.1/3.2 for RHEL. <br>
<br>
Dead Horse:<br>
</div>
<blockquote
cite="mid:CAEWPe=p8TOpwr66DMcWyLmJ+UK5ky5vVSCVFRJBzOqRgEeqxeQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>The nodes are EL6.3 based.<br>
<br>
Currently installed libvirt packages:<br>
<br>
libvirt-lock-sanlock-0.9.10-21.el6_3.8.x86_64<br>
libvirt-cim-0.6.1-3.el6.x86_64<br>
libvirt-0.9.10-21.el6_3.8.x86_64<br>
libvirt-python-0.9.10-21.el6_3.8.x86_64<br>
libvirt-client-0.9.10-21.el6_3.8.x86_64<br>
<br>
and qemu packages:<br>
qemu-kvm-0.12.1.2-2.295.el6_3.10.x86_64<br>
qemu-kvm-tools-0.12.1.2-2.295.el6_3.10.x86_64<br>
qemu-img-0.12.1.2-2.295.el6_3.10.x86_64<br>
<br>
</div>
<div>Thus my presumption here given the above is that
virDomainMigrateToURI2 has not yet been patched and/or
back-ported into the EL6.x libvirt/qemu?<br>
</div>
</div>
</blockquote>
<br>
virDomainMigrateToURI2() is supported in libvirt-0.9.10, I am not
sure if qemu-kvm-0.12.1.2 supports it.<br>
/var/log/libvirtd.log may help to verify this assumption<br>
<br>
<blockquote
cite="mid:CAEWPe=p8TOpwr66DMcWyLmJ+UK5ky5vVSCVFRJBzOqRgEeqxeQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
</div>
<div><br>
</div>
- DHC<br>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Wed, Jan 30, 2013 at 1:28 PM, Dan
Kenigsberg <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:danken@redhat.com"
target="_blank">danken(a)redhat.com</a>&gt;</span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb">
<div class="h5">On Wed, Jan 30, 2013 at 11:04:00AM -0600,
Dead Horse wrote:<br>
> Engine Build --> Commit:
82bdc46dfdb46b000f67f0cd4e51fc39665bf13b<br>
> VDSM Build: --> Commit:
da89a27492cc7d5a84e4bb87652569ca8e0fb20e + patch<br>
> --> <a moz-do-not-send="true"
href="http://gerrit.ovirt.org/#/c/11492/"
target="_blank">http://gerrit.ovirt.org/#/c/11492/</a>...
><br>
> Engine Side:<br>
> 2013-01-30 10:56:38,439 ERROR<br>
>
[org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo]<br>
> (QuartzScheduler_Worker-70) Rerun vm
887d764a-f835-4112-9eda-836a772ea5eb.<br>
> Called from vds lostisles<br>
> 2013-01-30 10:56:38,506 INFO<br>
>
[org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand]<br>
> (pool-3-thread-49) START,
MigrateStatusVDSCommand(HostName = lostisles,<br>
> HostId = e042b03b-dd4e-414c-be1a-b2c65ac000f5,<br>
> vmId=887d764a-f835-4112-9eda-836a772ea5eb), log id:
6556e75b<br>
> 2013-01-30 10:56:38,510 ERROR<br>
>
[org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand]<br>
> (pool-3-thread-49) Failed in MigrateStatusVDS
method<br>
> 2013-01-30 10:56:38,510 ERROR<br>
>
[org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand]<br>
> (pool-3-thread-49) Error code migrateErr and error
message<br>
> VDSGenericException: VDSErrorException: Failed to
MigrateStatusVDS, error =<br>
> Fatal error during migration<br>
> 2013-01-30 10:56:38,511 INFO<br>
>
[org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand]<br>
> (pool-3-thread-49) Command<br>
>
org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand
return<br>
> value<br>
> StatusOnlyReturnForXmlRpc [mStatus=StatusForXmlRpc
[mCode=12,<br>
> mMessage=Fatal error during migration]]<br>
><br>
><br>
> VDSM Side:<br>
> Thread-43670::ERROR::2013-01-30
10:56:37,052::vm::200::vm.Vm::(_recover)<br>
> vmId=`887d764a-f835-4112-9eda-836a772ea5eb`::this
function is not supported<br>
> by the connection driver: virDomainMigrateToURI2<br>
> Thread-43670::ERROR::2013-01-30
10:56:37,513::vm::288::vm.Vm::(run)<br>
> vmId=`887d764a-f835-4112-9eda-836a772ea5eb`::Failed
to migrate<br>
> Traceback (most recent call last):<br>
> File "/usr/share/vdsm/vm.py", line 273, in
run<br>
> self._startUnderlyingMigration()<br>
> File "/usr/share/vdsm/libvirtvm.py", line
504, in<br>
> _startUnderlyingMigration<br>
> None, maxBandwidth)<br>
> File "/usr/share/vdsm/libvirtvm.py", line
540, in
f<br>
> ret = attr(*args, **kwargs)<br>
> File
"/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py",
line<br>
> 111, in wrapper<br>
> ret = f(*args, **kwargs)<br>
> File
"/usr/lib64/python2.6/site-packages/libvirt.py", line
1103, in<br>
> migrateToURI2<br>
> if ret == -1: raise libvirtError
('virDomainMigrateToURI2() failed',<br>
> dom=self)<br>
> libvirtError: this function is not supported by the
connection driver:<br>
> virDomainMigrateToURI2<br>
<br>
</div>
</div>
Could it be that you are using an ancient libvirt with no<br>
virDomainMigrateToURI2? What are your libvirt and qemu-kvm
versions (on<br>
both machines)?<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated"
href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a class="moz-txt-link-freetext"
href="http://lists.ovirt.org/mailman/listinfo/users">http://...
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
---
舒明 Shu Ming
Open Virtualization Engineerning; CSTL, IBM Corp.
Tel: 86-10-82451626 Tieline: 9051626 E-mail: <a
class="moz-txt-link-abbreviated"
href="mailto:shuming@cn.ibm.com">shuming@cn.ibm.com</a> or <a
class="moz-txt-link-abbreviated"
href="mailto:shuming@linux.vnet.ibm.com">shuming@linux.vnet.ibm.com</a>
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193,
PRC</pre>
</body>
</html>
--------------040706080902050106070109--