[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] domU migration from Xen 4.8 HyperVisor to Xen 4.4
On Mon, Aug 20, 2018 at 12:17:46PM +0200, Alessandro Tugnoli wrote: > Thank you, i supposed that. > I've asked about migration from older to newer version of hypervisor because > I'm doing an upgrade of my two Xen Hypervisor hosts from xen 4.4 to 4.8 by > moving all the VM on the other host before upgrade to avoid services > downtime. > So, to be clear, I started with both hosts with Xen 4.4 and some VM on host1 > and some on host2, so I "live" moved all the VM of host1 to host2 then I've > upgraded host1 to xen 4.8 (of course host2 still have xen 4.4) and, after > upgrade I would to move back my VM on host1 in order to proceed to the > upgrade of host2 but I've encountered the problem of migration from older > version to a newer of Xen :( > > Hope this clarify > > So what's the best way to upgrade a cluster with 2 Xen Host without services > downtime ? If both hosts are using the same Xen version you should move everything to one host, update the now empty host, move all DomUs to the newly updated host and finally update the remaining host. > thanks in advance > best regards > alex > > > Il 20/08/2018 10:57, Roger Pau Monné ha scritto: > > On Fri, Aug 17, 2018 at 03:24:03PM +0200, Alessandro Tugnoli wrote: > > > Hi all > > > > > > I've just upgraded my hypervisor (let be "host1") to Debian 9 "Stretch" > > > with > > > Xen 4.8 (before upgrade I had Debian 8 "jessie" with Xen 4.4 Hypervisor) > > > and > > > DRBD for High Availability > > > > > > Everithing works well and I'm able to run all my domU in the hypervisor > > > just > > > updated but, when I try to migrate one domU to another Host (let be > > > "host2", > > > that has Debian 8 Jessie and Xen 4.4 Hypervisor and of course DRBD for > > > High > > > Availability) > > > > > > it gives me an error: > > > > > > host1# xl migrate domU host2 > > > > > > usr/lib/xen-4.4/bin/xl: invalid option -- 't' > > > unknown global option > > > libxl: error: libxl_utils.c:508:libxl_read_exactly: file/stream truncated > > > reading banner from migration receiver stream > > > libxl: info: libxl_exec.c:118:libxl_report_child_exitstatus: migration > > > transport process [13772] exited with error status 2 > > > > > > > > > If I try the migration from host2 to host1 I get instad: > > > > > > host2# xl migrate domU host1 > > > > > > migration target: Ready to receive domain. > > > Saving to migration stream new xl format (info 0x0/0x0/1003) > > > Loading new save file <incoming migration stream> (new xl fmt info > > > 0x0/0x0/1003) > > > Savefile contains xl domain config > > > Parsing config from <saved> > > > Traceback (most recent call last): > > > File "/usr/lib/xen-4.8/bin/convert-legacy-stream", line 15, in <module> > > > from xen.migration import legacy, public, libxc, libxl, xl > > > ImportError: No module named xen.migration Can you check that you have /usr/lib/xen-4.8/lib/python/ in your PYTHONPATH? You might need something like: export PYTHONPATH=$PYTHONPATH:/usr/lib/xen-4.8/lib/python/ But I'm no expert on Python. Roger. _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |