Interesting Theory. IIRC in the past the balloon device was auto created by libvirt, and at some point vdsm started removing it. So if the migration is from an old version where the device is created to a new one which supports a balloon created by the engine, it may be missing some parameters. So indeed we need to understand more about the source vdsm and how its VMs were created.
----- Original Message ----- > From: "Assaf Muller" <amul...@redhat.com> > To: "Dan Kenigsberg" <dan...@redhat.com> > Cc: vdsm-devel@lists.fedorahosted.org > Sent: Thursday, May 30, 2013 10:00:49 AM > Subject: Re: [vdsm] Migration regression on master > > > > * We still need to see the vmCreate command used to learn more about the > issue > * We can always implement a hack that checks if the alias attribute > exists. However, there is probably a deeper issue at hand and this is a > good opportunity to find and solve it > * Dan has a theory that the issue is with migrating a VM from a 3.0 VDSM > version host to a 3.2 host. Perhaps the balloon device isn't created > properly at the source host > > From: "Dan Kenigsberg" <dan...@redhat.com> > To: "Peter V. Saveliev" <p...@redhat.com> > Cc: vdsm-devel@lists.fedorahosted.org > Sent: Wednesday, May 29, 2013 4:41:24 PM > Subject: Re: [vdsm] Migration regression on master > > On Wed, May 29, 2013 at 02:13:02PM +0200, Peter V. Saveliev wrote: > > On 05/29/2013 07:17 AM, Dan Kenigsberg wrote: > > >On Tue, May 28, 2013 at 11:54:45AM -0400, Giuseppe Vallarelli wrote: > > >> | ----- Original Message ----- > > > >>| | From: "Assaf Muller" <amul...@redhat.com> > > >>| | To: "Michal Skrivanek" <michal.skriva...@redhat.com> > > >>| | Cc: "vdsm-devel@lists.fedorahosted.org Development" > > >>| | <vdsm-devel@lists.fedorahosted.org> > > >>| | Sent: Thursday, May 23, 2013 2:12:47 PM > > >>| | Subject: Re: [vdsm] Migration regression on master > > >>| | > > >>| | As you can see in a previous patch set I checked if the alias > > >>| | attribute > > >>| | exists instead of assuming it exists. > > >>| | I then changed my mind with Dan's blessing, and decided to assume it > > >>| | does > > >>| | exist, exactly for cases like this. > > >>| | Even if we check if the alias exists, what do we do if we find out it > > >>| | doesn't? We're at a problem and need to understand why the alias > > >>| | doesn't > > >>| | exist because it should - For all devices. > > >>| | > > >>| | We definitely need to deal with this issue - Can you provide the > > >>| | domxml of > > >>| | the VM during creation, and during migration? > > >> > > >>Hi Assaf, Peter today has reproduced the same error and provided me > > >>the output log, you can find it here: > > >>http://etherpad.ovirt.org/p/migration-errors > > > > > >Would you add the original vmCreate line, and domxml, that was used to > > >create the VM at the source host? > > > > http://pastebin.test.redhat.com/144447 > > http://pastebin.test.redhat.com/144446 > > That's an internal pastebin instance. Could you simply inline the > answer? Hyperlinks makes a casual reader of the mailing list not > understand what's going on. > > Note that we need vmCreate command, the response is less > interesting, thow seeing the whole vdsm thread would not harm. > > Dan. > _______________________________________________ > vdsm-devel mailing list > vdsm-devel@lists.fedorahosted.org > https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel > > > _______________________________________________ > vdsm-devel mailing list > vdsm-devel@lists.fedorahosted.org > https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel > _______________________________________________ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
