I am able to power on vms on newly upgraded host, But not able to migrate VMs
from other hosts to new host or newly upgraded hosts to other hosts. This was
worked fine before upgraded.
i see below logs
Unable to read from monitor: Connection reset by peer
internal error: qemu unexpectedly close
I need to migrate running VMs from one host in our cluster to another
however the task keeps failing any time I start a migration. The engine
logs show a few different errors as follows.
2019-07-10 09:53:19,440-04 ERROR
[org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
(ForkJoinPool-1-worke
Hi,
After upgrade to 4.3.3 from 4.3.2, VM migrations are failing with
"No available host to migrate VMs to"
Interestingly, this happens in one of our clusters, not on the
other. Both on the same datacenter, both in 4.3 compatibility version.
This are the relevant lines from /var/log
On Fri, Feb 08, 2013 at 01:40:59PM -0600, Dead Horse wrote:
> Current master does resolve the issue. However in order to test it the
> zombie reaper patch from the ovirt-3.2 branch must be applied to avoid that
> issue.
> - DHC
I tend to agree that keeping vdsm's master branch broken for too long
Current master does resolve the issue. However in order to test it the
zombie reaper patch from the ovirt-3.2 branch must be applied to avoid that
issue.
- DHC
On Fri, Feb 8, 2013 at 2:08 AM, Vinzenz Feenstra wrote:
> On 02/05/2013 10:57 PM, Dead Horse wrote:
>
> Confirmed ovirt-3.2 branch of
On 02/05/2013 10:57 PM, Dead Horse wrote:
Confirmed ovirt-3.2 branch of vdsm does work with migrations.
So there is a difference between it and master as pertains to the
migration logic.
- DHC
Hi,
could you please retry it with the current master? We have fixed the
issue which caused this re
Confirmed ovirt-3.2 branch of vdsm does work with migrations.
So there is a difference between it and master as pertains to the migration
logic.
- DHC
On Tue, Feb 5, 2013 at 2:26 PM, Dead Horse wrote:
> Dan,
> Building and testing it now.
> - DHC
>
>
> On Tue, Feb 5, 2013 at 2:39 AM, Dan Kenigsb
Dan,
Building and testing it now.
- DHC
On Tue, Feb 5, 2013 at 2:39 AM, Dan Kenigsberg wrote:
> On Mon, Feb 04, 2013 at 10:38:16AM -0600, Dead Horse wrote:
> > VDSM built from commit: c343e1833f7b6e5428dd90f14f7807dca1baa0b4 works
> > Current VDSM built from master does not work.
> >
> > I coul
On Mon, Feb 04, 2013 at 10:38:16AM -0600, Dead Horse wrote:
> VDSM built from commit: c343e1833f7b6e5428dd90f14f7807dca1baa0b4 works
> Current VDSM built from master does not work.
>
> I could try spending some time trying to bisect and find out where the
> breakage occurred I suppose.
Would you
VDSM built from commit: c343e1833f7b6e5428dd90f14f7807dca1baa0b4 works
Current VDSM built from master does not work.
I could try spending some time trying to bisect and find out where the
breakage occurred I suppose.
- DHC
On Sun, Feb 3, 2013 at 10:13 AM, Martin Kletzander wrote:
> On 02/03/201
On 02/03/2013 08:40 AM, Dan Kenigsberg wrote:
> On Fri, Feb 01, 2013 at 11:44:08PM +0100, Martin Kletzander wrote:
>> On 02/01/2013 09:29 PM, Dead Horse wrote:
>>> To test further I loaded up two more identical servers with EL 6.3 and the
>>> same package versions originally indicated. The differen
On Fri, Feb 01, 2013 at 11:44:08PM +0100, Martin Kletzander wrote:
> On 02/01/2013 09:29 PM, Dead Horse wrote:
> > To test further I loaded up two more identical servers with EL 6.3 and the
> > same package versions originally indicated. The difference here is that I
> > did not turn these into ovi
On 02/01/2013 09:29 PM, Dead Horse wrote:
> To test further I loaded up two more identical servers with EL 6.3 and the
> same package versions originally indicated. The difference here is that I
> did not turn these into ovirt nodes. EG: installing VDSM.
>
> - All configurations were left at defau
To test further I loaded up two more identical servers with EL 6.3 and the
same package versions originally indicated. The difference here is that I
did not turn these into ovirt nodes. EG: installing VDSM.
- All configurations were left at defaults on both servers
- iptables and selinux disabled
Both nodes are identical and can fully communicate with each other.
Since the normal non p2p live migration works both hosts can reach each
other via the connection URI.
Perhaps I am missing something here?
- DHC
___
Users mailing list
Users@ovirt.org
htt
On 01/31/2013 07:07 PM, Dead Horse wrote:
> Here is the content exceprt from libvirtd.log for the command: virsh #
> migrate --p2p sl63 qemu+ssh://192.168.1.2/system
>
Thanks for testing this. However, this is another problem. When
migrating p2p, the destination URI must be reachable from the s
Here is the content exceprt from libvirtd.log for the command: virsh #
migrate --p2p sl63 qemu+ssh://192.168.1.2/system
2013-01-31 18:02:53.740+: 2832: debug : virDomainFree:2313 :
dom=0x7f4f88000c80, (VM: name=sl63,
uuid=887d764a-f835-4112-9eda-836a772ea5eb)
2013-01-31 18:02:53.743+: 2831
note ignore the IP diff in the ssh host auth --> copy/paste fail ;)
- DHC
On Thu, Jan 31, 2013 at 11:25 AM, Dead Horse
wrote:
> Doh, brain fart VDSM is not involved here for the purposed of the needed
> test.
> Here is my initial whack at it:
>
> Source Node:
>
> virsh # list
> IdName
Doh, brain fart VDSM is not involved here for the purposed of the needed
test.
Here is my initial whack at it:
Source Node:
virsh # list
IdName State
1 sl63 running
virsh # migrate
Shu,
I build oVirt Engine and vdsm from source myself. The commits I indicated
are what I built from.I run the engine under FC17 and my nodes are running
EL6.x respectively.
Dan,
I reverted VDSM on my two test nodes to an earlier build of VDSM (commit:
c343e1833f7b6e5428dd90f14f7807dca1baa0b4)
VDS
On 01/31/2013 11:56 AM, Dan Kenigsberg wrote:
> On Thu, Jan 31, 2013 at 11:08:58AM +0100, Martin Kletzander wrote:
>> On 01/31/2013 10:25 AM, Dan Kenigsberg wrote:
>>> On Thu, Jan 31, 2013 at 09:43:44AM +0100, Martin Kletzander wrote:
On 01/30/2013 08:40 PM, Dead Horse wrote:
> The nodes a
On Thu, Jan 31, 2013 at 11:08:58AM +0100, Martin Kletzander wrote:
> On 01/31/2013 10:25 AM, Dan Kenigsberg wrote:
> > On Thu, Jan 31, 2013 at 09:43:44AM +0100, Martin Kletzander wrote:
> >> On 01/30/2013 08:40 PM, Dead Horse wrote:
> >>> The nodes are EL6.3 based.
> >>>
> >>> Currently installed l
On Thu, Jan 31, 2013 at 09:43:44AM +0100, Martin Kletzander wrote:
> On 01/30/2013 08:40 PM, Dead Horse wrote:
> > 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-2
On 01/31/2013 10:25 AM, Dan Kenigsberg wrote:
> On Thu, Jan 31, 2013 at 09:43:44AM +0100, Martin Kletzander wrote:
>> On 01/30/2013 08:40 PM, Dead Horse wrote:
>>> The nodes are EL6.3 based.
>>>
>>> Currently installed libvirt packages:
>>>
>>> libvirt-lock-sanlock-0.9.10-21.el6_3.8.x86_64
>>> libv
On 01/30/2013 08:40 PM, Dead Horse wrote:
> 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-
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.
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.29
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
> [or
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_Worke
29 matches
Mail list logo
