Re: [ovirt-users] VM Migration Fails (Network thoughts)
Annnddd here I am again being 'that guy'. I apologize for all the traffic, but I wanted to note that migrations appears to be working even over the migration IP network once short name resolution was working fine. The first attempt did fail after changes, but since then, they are working fine, it seems. So, I'm down to only a simple question now: If I edit the resolv.conf on a RHEV-H/ovirt node (7.2) host, does it REALLY get replaced on reboot? And if so, how do I work around this since I need those name resolutions to work? Would /etc/hosts file entries be sufficient for just the primary hostnames and IPs (or would they also get over-written on reboot)? Again, sorry for unnecessary posts, but I'm just trying to understand the pieces as much as possible since I'm going to be supporting this for a very long time. On Fri, Mar 4, 2016 at 3:42 PM, Christopher Young wrote: > So, I'm self-replying, but I was able to confirm that changing > /etc/resolv.conf so that the short hostnames work allow migration, but > ONLY when the migration network is set to the main management > interface (and thus the primary hostname of the system). I'm > wondering how this could work with separate IP networks for VM > Migration when hostname resolutions would generally always return the > primary IP address of a system. > > I obviously still have reading to do, but any help and feedback would > be greatly appreciated. > > > > On Fri, Mar 4, 2016 at 3:31 PM, Christopher Young > wrote: >> So, I'm attempting to understand something fully. My setup might not >> be ideal, so please provide me whatever education I may need. >> >> RE: https://access.redhat.com/solutions/202823 >> >> Quick background: >> >> I have (3) RHEV-H (ovirt node) Hypervisors with a hosted-engine. VM >> Migrations currently are not working and I have the following errors >> in the vdsm.log: >> >> --- >> "[RHEV]Failed to migrate VM between hypervisor with error "gaierror: >> [Errno -2] Name or service not known" in vdsm.log" >> --- >> >> Reading the RedHat article leads me to believe that this is a name >> resolution issue (for the FQDNs), but that leads to another question >> which I'll get to. First, a little more about the setup: >> >> I have separate IP networks for Management (ovirtmgmt), Storage, and >> VM Migration. These are all on unique IP ranges. I'll make up some >> for my purposes here: >> >> MGMT_VLAN: 10.25.250.x/24 >> STORAGE_VLAN: 10.26.3.x/24 >> MIGRATE_VLAN: 10.26.5.x/24 >> >> In anticipation for setting all of this up, I assigned hostnames/IPs >> for each role on each node/hypervisor, like so: >> >> vnode01 >> vnode01-sto (storage) >> vnode01-vmm >> >> vnode02 >> vnode02-sto >> vnode02-vmm >> >> etc., etc. >> >> So, I'm trying to understand what my best procedure for setting up a >> separate migration network and what IP/hostname settings are necessary >> to ensure that this works properly and wouldn't affect other things. >> >> I'm going to do some more reading right now, but at least I feel like >> I'm on the right path to getting migrations working. >> >> Please help lol >> >> Thanks as always, >> >> -- Chris ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] VM Migration Fails (Network thoughts)
So, I'm self-replying, but I was able to confirm that changing /etc/resolv.conf so that the short hostnames work allow migration, but ONLY when the migration network is set to the main management interface (and thus the primary hostname of the system). I'm wondering how this could work with separate IP networks for VM Migration when hostname resolutions would generally always return the primary IP address of a system. I obviously still have reading to do, but any help and feedback would be greatly appreciated. On Fri, Mar 4, 2016 at 3:31 PM, Christopher Young wrote: > So, I'm attempting to understand something fully. My setup might not > be ideal, so please provide me whatever education I may need. > > RE: https://access.redhat.com/solutions/202823 > > Quick background: > > I have (3) RHEV-H (ovirt node) Hypervisors with a hosted-engine. VM > Migrations currently are not working and I have the following errors > in the vdsm.log: > > --- > "[RHEV]Failed to migrate VM between hypervisor with error "gaierror: > [Errno -2] Name or service not known" in vdsm.log" > --- > > Reading the RedHat article leads me to believe that this is a name > resolution issue (for the FQDNs), but that leads to another question > which I'll get to. First, a little more about the setup: > > I have separate IP networks for Management (ovirtmgmt), Storage, and > VM Migration. These are all on unique IP ranges. I'll make up some > for my purposes here: > > MGMT_VLAN: 10.25.250.x/24 > STORAGE_VLAN: 10.26.3.x/24 > MIGRATE_VLAN: 10.26.5.x/24 > > In anticipation for setting all of this up, I assigned hostnames/IPs > for each role on each node/hypervisor, like so: > > vnode01 > vnode01-sto (storage) > vnode01-vmm > > vnode02 > vnode02-sto > vnode02-vmm > > etc., etc. > > So, I'm trying to understand what my best procedure for setting up a > separate migration network and what IP/hostname settings are necessary > to ensure that this works properly and wouldn't affect other things. > > I'm going to do some more reading right now, but at least I feel like > I'm on the right path to getting migrations working. > > Please help lol > > Thanks as always, > > -- Chris ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] VM Migration Fails (Network thoughts)
So, I'm attempting to understand something fully. My setup might not be ideal, so please provide me whatever education I may need. RE: https://access.redhat.com/solutions/202823 Quick background: I have (3) RHEV-H (ovirt node) Hypervisors with a hosted-engine. VM Migrations currently are not working and I have the following errors in the vdsm.log: --- "[RHEV]Failed to migrate VM between hypervisor with error "gaierror: [Errno -2] Name or service not known" in vdsm.log" --- Reading the RedHat article leads me to believe that this is a name resolution issue (for the FQDNs), but that leads to another question which I'll get to. First, a little more about the setup: I have separate IP networks for Management (ovirtmgmt), Storage, and VM Migration. These are all on unique IP ranges. I'll make up some for my purposes here: MGMT_VLAN: 10.25.250.x/24 STORAGE_VLAN: 10.26.3.x/24 MIGRATE_VLAN: 10.26.5.x/24 In anticipation for setting all of this up, I assigned hostnames/IPs for each role on each node/hypervisor, like so: vnode01 vnode01-sto (storage) vnode01-vmm vnode02 vnode02-sto vnode02-vmm etc., etc. So, I'm trying to understand what my best procedure for setting up a separate migration network and what IP/hostname settings are necessary to ensure that this works properly and wouldn't affect other things. I'm going to do some more reading right now, but at least I feel like I'm on the right path to getting migrations working. Please help lol Thanks as always, -- Chris ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] VM migration fails when hardware node fails
We are testing our new ovirt installation. We notice that if I shutdown a hardware node that the VM's do not migrate off and don't start up after the node is restarted. Its a 3 node cluster with the ovirt-engine on a 4th host. centos 7.1.1503 ovirt-engine-3.6.0.3-1.el7.centos.noarch glusterfs-3.7.5-1.el7.x86_64 High Availability box is checked, Priority = High. 2015-12-10 11:43:34,251 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-8-thread-42) [5f8883ec] Correlation ID: 5d94dbf7, Job ID: 83159d5a-0ab9-4f1b-afbc-e5c2fcbb6e04, Call Stack: null, Custom Event ID: -1, Message: Failed to migrate VM billjov2.test.j2noc.com to Host ovirt3.test.j2noc.com . Trying to migrate to another Host. ... 2015-12-10 11:43:49,137 INFO [org.ovirt.engine.core.vdsbroker.VmAnalyzer] (DefaultQuartzScheduler_Worker-87) [5f8883ec] VM 'f67a4f38-bb4b-460f-81ea-10ecae60edcc'(billjov2.test.j2noc.com) moved from 'MigratingFrom' --> 'Up' 2015-12-10 11:43:49,518 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-8-thread-4) [5f8883ec] Correlation ID: 5d94dbf7, Job ID: 83159d5a-0ab9-4f1b-afbc-e5c2fcbb6e04, Call Stack: null, Custom Event ID: -1, Message: Failed to migrate VM billjov2.test.j2noc.com to Host ovirt1.test.j2noc.com . Trying to migrate to another Host. Migrating live works just fine. I haven't found anywhere where it says why it failed when node is down. Any ideas on why it is failing? And why VM's don't start when node is up? Cloud Services for Business www.j2.com j2 | eFax | eVoice | FuseMail | Campaigner | KeepItSafe | Onebox This email, its contents and attachments contain information from j2 Global, Inc. and/or its affiliates which may be privileged, confidential or otherwise protected from disclosure. The information is intended to be for the addressee(s) only. If you are not an addressee, any disclosure, copy, distribution, or use of the contents of this message is prohibited. If you have received this email in error please notify the sender by reply e-mail and delete the original message and any copies. (c) 2015 j2 Global, Inc. All rights reserved. eFax, eVoice, Campaigner, FuseMail, KeepItSafe, and Onebox are registered trademarks of j2 Global, Inc. and its affiliates. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] VM Migration Fails
OK, I was just wondering. I'm glad to see you got it fixed. On Aug 3, 2015 6:07 PM, "s k" wrote: > Because it breaks other custom configuration (non-oVirt related). > > > I will probably try SELinux in enforcing mode when migrating to CentOS 7 > hosts. > > -- > Date: Mon, 3 Aug 2015 13:21:48 -0400 > Subject: RE: [ovirt-users] VM Migration Fails > From: do...@cloudspin.me > To: sokratis1...@outlook.com > CC: users@ovirt.org > > Is there any reason that you have SE Linux in permissive. oVirt will run > with SE Linux in enforcing > On Aug 3, 2015 1:09 PM, "s k" wrote: > > I checked the vdsm.log and the source host was throwing this error: > > libvirtError: unsupported configuration: Unable to find security driver > for label selinux > > > I fixed it by disabling selinux (it was running in permissive mode before) > and rebooting the host since selinux was also disabled on the other host. > > > ------ > Date: Mon, 3 Aug 2015 12:41:57 -0400 > Subject: Re: [ovirt-users] VM Migration Fails > From: do...@cloudspin.me > To: sokratis1...@outlook.com > CC: users@ovirt.org > > Can you send the log from each node > > /var/log/vdsm/vdsm.log > On Aug 3, 2015 12:39 PM, "s k" wrote: > > Hi, > > > I'm having trouble migrating VMs in a 2-node cluster. VMs can start > normally on both nodes if they are shutdown first but live migration fails > and the following is thrown in the engine.log: > > > > 2015-08-03 19:28:28,566 ERROR > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > (DefaultQuartzScheduler_Worker-42) [46f46347] Rerun vm > 2ceb9c65-1920-49fe-9db1-6c9470e50a65. Called from vds ovirt-srv-02 > 2015-08-03 19:28:28,615 ERROR > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > (org.ovirt.thread.pool-8-thread-38) [46f46347] Failed in MigrateStatusVDS > method > 2015-08-03 19:28:28,617 ERROR > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > (org.ovirt.thread.pool-8-thread-38) [46f46347] Command > MigrateStatusVDSCommand(HostName = ovirt-srv-02, HostId = > be3da0c4-f898-4aa4-89c7-239282a03959, > vmId=2ceb9c65-1920-49fe-9db1-6c9470e50a65) execution failed. Exception: > VDSErrorException: VDSGenericException: VDSErrorException: Failed to > MigrateStatusVDS, error = Fatal error during migration, code = 12 > 2015-08-03 19:28:28,623 ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (org.ovirt.thread.pool-8-thread-38) [46f46347] Correlation ID: 43b38529, > Job ID: 21468e21-c78c-41ea-bc99-c56ff4526820, Call Stack: null, Custom > Event ID: -1, Message: Migration failed due to Error: Fatal error during > migration. Trying to migrate to another Host (VM: testvm01, Source: > ovirt-srv-02, Destination: ovirt-srv-03). > > > Both nodes run on CentOS 6.6 with the following versions: > > > OS Version: *RHEL - 6 - 6.el6.centos.12.2* > Kernel Version: *2.6.32 - 504.30.3.el6.x86_64* > KVM Version: *0.12.1.2 - 2.448.el6_6.4* > LIBVIRT Version: *libvirt-0.10.2-46.el6_6.6* > VDSM Version: *vdsm-4.16.20-1.git3a90f62.el6* > > > Any thoughts? > > > Thanks, > > > Sokratis > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] VM Migration Fails
Because it breaks other custom configuration (non-oVirt related). I will probably try SELinux in enforcing mode when migrating to CentOS 7 hosts. Date: Mon, 3 Aug 2015 13:21:48 -0400 Subject: RE: [ovirt-users] VM Migration Fails From: do...@cloudspin.me To: sokratis1...@outlook.com CC: users@ovirt.org Is there any reason that you have SE Linux in permissive. oVirt will run with SE Linux in enforcing On Aug 3, 2015 1:09 PM, "s k" wrote: I checked the vdsm.log and the source host was throwing this error: libvirtError: unsupported configuration: Unable to find security driver for label selinux I fixed it by disabling selinux (it was running in permissive mode before) and rebooting the host since selinux was also disabled on the other host. Date: Mon, 3 Aug 2015 12:41:57 -0400 Subject: Re: [ovirt-users] VM Migration Fails From: do...@cloudspin.me To: sokratis1...@outlook.com CC: users@ovirt.org Can you send the log from each node /var/log/vdsm/vdsm.log On Aug 3, 2015 12:39 PM, "s k" wrote: Hi, I'm having trouble migrating VMs in a 2-node cluster. VMs can start normally on both nodes if they are shutdown first but live migration fails and the following is thrown in the engine.log: 2015-08-03 19:28:28,566 ERROR [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-42) [46f46347] Rerun vm 2ceb9c65-1920-49fe-9db1-6c9470e50a65. Called from vds ovirt-srv-022015-08-03 19:28:28,615 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (org.ovirt.thread.pool-8-thread-38) [46f46347] Failed in MigrateStatusVDS method2015-08-03 19:28:28,617 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (org.ovirt.thread.pool-8-thread-38) [46f46347] Command MigrateStatusVDSCommand(HostName = ovirt-srv-02, HostId = be3da0c4-f898-4aa4-89c7-239282a03959, vmId=2ceb9c65-1920-49fe-9db1-6c9470e50a65) execution failed. Exception: VDSErrorException: VDSGenericException: VDSErrorException: Failed to MigrateStatusVDS, error = Fatal error during migration, code = 122015-08-03 19:28:28,623 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-8-thread-38) [46f46347] Correlation ID: 43b38529, Job ID: 21468e21-c78c-41ea-bc99-c56ff4526820, Call Stack: null, Custom Event ID: -1, Message: Migration failed due to Error: Fatal error during migration. Trying to migrate to another Host (VM: testvm01, Source: ovirt-srv-02, Destination: ovirt-srv-03). Both nodes run on CentOS 6.6 with the following versions: OS Version: RHEL - 6 - 6.el6.centos.12.2Kernel Version: 2.6.32 - 504.30.3.el6.x86_64KVM Version: 0.12.1.2 - 2.448.el6_6.4LIBVIRT Version: libvirt-0.10.2-46.el6_6.6VDSM Version: vdsm-4.16.20-1.git3a90f62.el6 Any thoughts? Thanks, Sokratis ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] VM Migration Fails
Is there any reason that you have SE Linux in permissive. oVirt will run with SE Linux in enforcing On Aug 3, 2015 1:09 PM, "s k" wrote: > I checked the vdsm.log and the source host was throwing this error: > > libvirtError: unsupported configuration: Unable to find security driver > for label selinux > > > I fixed it by disabling selinux (it was running in permissive mode before) > and rebooting the host since selinux was also disabled on the other host. > > > -- > Date: Mon, 3 Aug 2015 12:41:57 -0400 > Subject: Re: [ovirt-users] VM Migration Fails > From: do...@cloudspin.me > To: sokratis1...@outlook.com > CC: users@ovirt.org > > Can you send the log from each node > > /var/log/vdsm/vdsm.log > On Aug 3, 2015 12:39 PM, "s k" wrote: > > Hi, > > > I'm having trouble migrating VMs in a 2-node cluster. VMs can start > normally on both nodes if they are shutdown first but live migration fails > and the following is thrown in the engine.log: > > > > 2015-08-03 19:28:28,566 ERROR > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > (DefaultQuartzScheduler_Worker-42) [46f46347] Rerun vm > 2ceb9c65-1920-49fe-9db1-6c9470e50a65. Called from vds ovirt-srv-02 > 2015-08-03 19:28:28,615 ERROR > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > (org.ovirt.thread.pool-8-thread-38) [46f46347] Failed in MigrateStatusVDS > method > 2015-08-03 19:28:28,617 ERROR > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > (org.ovirt.thread.pool-8-thread-38) [46f46347] Command > MigrateStatusVDSCommand(HostName = ovirt-srv-02, HostId = > be3da0c4-f898-4aa4-89c7-239282a03959, > vmId=2ceb9c65-1920-49fe-9db1-6c9470e50a65) execution failed. Exception: > VDSErrorException: VDSGenericException: VDSErrorException: Failed to > MigrateStatusVDS, error = Fatal error during migration, code = 12 > 2015-08-03 19:28:28,623 ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (org.ovirt.thread.pool-8-thread-38) [46f46347] Correlation ID: 43b38529, > Job ID: 21468e21-c78c-41ea-bc99-c56ff4526820, Call Stack: null, Custom > Event ID: -1, Message: Migration failed due to Error: Fatal error during > migration. Trying to migrate to another Host (VM: testvm01, Source: > ovirt-srv-02, Destination: ovirt-srv-03). > > > Both nodes run on CentOS 6.6 with the following versions: > > > OS Version: *RHEL - 6 - 6.el6.centos.12.2* > Kernel Version: *2.6.32 - 504.30.3.el6.x86_64* > KVM Version: *0.12.1.2 - 2.448.el6_6.4* > LIBVIRT Version: *libvirt-0.10.2-46.el6_6.6* > VDSM Version: *vdsm-4.16.20-1.git3a90f62.el6* > > > Any thoughts? > > > Thanks, > > > Sokratis > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] VM Migration Fails
I checked the vdsm.log and the source host was throwing this error: libvirtError: unsupported configuration: Unable to find security driver for label selinux I fixed it by disabling selinux (it was running in permissive mode before) and rebooting the host since selinux was also disabled on the other host. Date: Mon, 3 Aug 2015 12:41:57 -0400 Subject: Re: [ovirt-users] VM Migration Fails From: do...@cloudspin.me To: sokratis1...@outlook.com CC: users@ovirt.org Can you send the log from each node /var/log/vdsm/vdsm.log On Aug 3, 2015 12:39 PM, "s k" wrote: Hi, I'm having trouble migrating VMs in a 2-node cluster. VMs can start normally on both nodes if they are shutdown first but live migration fails and the following is thrown in the engine.log: 2015-08-03 19:28:28,566 ERROR [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-42) [46f46347] Rerun vm 2ceb9c65-1920-49fe-9db1-6c9470e50a65. Called from vds ovirt-srv-022015-08-03 19:28:28,615 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (org.ovirt.thread.pool-8-thread-38) [46f46347] Failed in MigrateStatusVDS method2015-08-03 19:28:28,617 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (org.ovirt.thread.pool-8-thread-38) [46f46347] Command MigrateStatusVDSCommand(HostName = ovirt-srv-02, HostId = be3da0c4-f898-4aa4-89c7-239282a03959, vmId=2ceb9c65-1920-49fe-9db1-6c9470e50a65) execution failed. Exception: VDSErrorException: VDSGenericException: VDSErrorException: Failed to MigrateStatusVDS, error = Fatal error during migration, code = 122015-08-03 19:28:28,623 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-8-thread-38) [46f46347] Correlation ID: 43b38529, Job ID: 21468e21-c78c-41ea-bc99-c56ff4526820, Call Stack: null, Custom Event ID: -1, Message: Migration failed due to Error: Fatal error during migration. Trying to migrate to another Host (VM: testvm01, Source: ovirt-srv-02, Destination: ovirt-srv-03). Both nodes run on CentOS 6.6 with the following versions: OS Version: RHEL - 6 - 6.el6.centos.12.2Kernel Version: 2.6.32 - 504.30.3.el6.x86_64KVM Version: 0.12.1.2 - 2.448.el6_6.4LIBVIRT Version: libvirt-0.10.2-46.el6_6.6VDSM Version: vdsm-4.16.20-1.git3a90f62.el6 Any thoughts? Thanks, Sokratis ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] VM Migration Fails
Can you send the log from each node /var/log/vdsm/vdsm.log On Aug 3, 2015 12:39 PM, "s k" wrote: > Hi, > > > I'm having trouble migrating VMs in a 2-node cluster. VMs can start > normally on both nodes if they are shutdown first but live migration fails > and the following is thrown in the engine.log: > > > > 2015-08-03 19:28:28,566 ERROR > [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] > (DefaultQuartzScheduler_Worker-42) [46f46347] Rerun vm > 2ceb9c65-1920-49fe-9db1-6c9470e50a65. Called from vds ovirt-srv-02 > 2015-08-03 19:28:28,615 ERROR > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > (org.ovirt.thread.pool-8-thread-38) [46f46347] Failed in MigrateStatusVDS > method > 2015-08-03 19:28:28,617 ERROR > [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] > (org.ovirt.thread.pool-8-thread-38) [46f46347] Command > MigrateStatusVDSCommand(HostName = ovirt-srv-02, HostId = > be3da0c4-f898-4aa4-89c7-239282a03959, > vmId=2ceb9c65-1920-49fe-9db1-6c9470e50a65) execution failed. Exception: > VDSErrorException: VDSGenericException: VDSErrorException: Failed to > MigrateStatusVDS, error = Fatal error during migration, code = 12 > 2015-08-03 19:28:28,623 ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (org.ovirt.thread.pool-8-thread-38) [46f46347] Correlation ID: 43b38529, > Job ID: 21468e21-c78c-41ea-bc99-c56ff4526820, Call Stack: null, Custom > Event ID: -1, Message: Migration failed due to Error: Fatal error during > migration. Trying to migrate to another Host (VM: testvm01, Source: > ovirt-srv-02, Destination: ovirt-srv-03). > > > Both nodes run on CentOS 6.6 with the following versions: > > > OS Version: *RHEL - 6 - 6.el6.centos.12.2* > Kernel Version: *2.6.32 - 504.30.3.el6.x86_64* > KVM Version: *0.12.1.2 - 2.448.el6_6.4* > LIBVIRT Version: *libvirt-0.10.2-46.el6_6.6* > VDSM Version: *vdsm-4.16.20-1.git3a90f62.el6* > > > Any thoughts? > > > Thanks, > > > Sokratis > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] VM Migration Fails
Hi, I'm having trouble migrating VMs in a 2-node cluster. VMs can start normally on both nodes if they are shutdown first but live migration fails and the following is thrown in the engine.log: 2015-08-03 19:28:28,566 ERROR [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-42) [46f46347] Rerun vm 2ceb9c65-1920-49fe-9db1-6c9470e50a65. Called from vds ovirt-srv-022015-08-03 19:28:28,615 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (org.ovirt.thread.pool-8-thread-38) [46f46347] Failed in MigrateStatusVDS method2015-08-03 19:28:28,617 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (org.ovirt.thread.pool-8-thread-38) [46f46347] Command MigrateStatusVDSCommand(HostName = ovirt-srv-02, HostId = be3da0c4-f898-4aa4-89c7-239282a03959, vmId=2ceb9c65-1920-49fe-9db1-6c9470e50a65) execution failed. Exception: VDSErrorException: VDSGenericException: VDSErrorException: Failed to MigrateStatusVDS, error = Fatal error during migration, code = 122015-08-03 19:28:28,623 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-8-thread-38) [46f46347] Correlation ID: 43b38529, Job ID: 21468e21-c78c-41ea-bc99-c56ff4526820, Call Stack: null, Custom Event ID: -1, Message: Migration failed due to Error: Fatal error during migration. Trying to migrate to another Host (VM: testvm01, Source: ovirt-srv-02, Destination: ovirt-srv-03). Both nodes run on CentOS 6.6 with the following versions: OS Version: RHEL - 6 - 6.el6.centos.12.2Kernel Version: 2.6.32 - 504.30.3.el6.x86_64KVM Version: 0.12.1.2 - 2.448.el6_6.4LIBVIRT Version: libvirt-0.10.2-46.el6_6.6VDSM Version: vdsm-4.16.20-1.git3a90f62.el6 Any thoughts? Thanks, Sokratis ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
