This content has been marked as final. Show 2 replies
I don't see any issues with that, although there's no point-and-click way in OVMM to do that. However, you can always shutdown the guest on the current host and just copy the virtual disk file over to the older OVM and re-setup the guest there again. In the end, it's always the virtual disks that matter, as the vm config can be easily be recreated in the manager gui.
I think that OVM 2.2.1 would just "import" new objects, even if they have been copied onto the SR, when performing a SR scan, but you can also go the standard route and put the virtual disk from the OVM 3.2.1 SR on some http server and import it using the the repo controls in OVM 2.x. However, you might want to change the file name of the virtual disk you copied before you do that since it then will be much easier to spot after importing.
Simple ad hoc HTTP server on OVM 3.2.3,
[root@ovm323 ISOs]# cat /etc/ovs-release
Oracle VM server release 3.2.3
[root@ovm323 ISOs]# python -V
[root@ovm323 ISOs]# pwd
[root@ovm323 ISOs]# python -m SimpleHTTPServer 8000
Serving HTTP on 0.0.0.0 port 8000 ...
localhost.localdomain - - [13/May/2013 10:51:39] "GET / HTTP/1.1" 200 -
[root@ovm323 ~]# curl http://localhost:8000
<#title>Directory listing for /</title>
<#h2>Directory listing for /</h2>