Importing is done from UI (Admin portal) -> Storage -> Domains -> Newly Added
domain -> "Import VM" -> select Vm and you can import.
Keep in mind that it is easier to import if all VM disks are on the same storage domain
(I've opened a RFE for multi-domain import).
Best Regards,
Strahil Nikolov
В петък, 25 септември 2020 г., 21:41:45 Гринуич+3, penguin pages
<jeremey.wise(a)gmail.com> написа:
Thanks for reply.. It really is appreciated.
1) Note about VM import
-> Can you provide details / Example. For me I click on
oVirt-> Compute -> Virtual Machines -> Import
-> Source Option (only ones making any sense would be "Export Domain"
rest are unrelated and KVM one would need xml.. which is I think gone now) So.. if I
choose "Export Domain" the "path" is to what file to import VM?
2) note about import from live VM in .. When engine is gone.. this would be intersting to
try.. but as I reboot.. and re-installed engine.. I think this cleared any hope of getting
the libvirt xml files out
[root@medusa libvirt]# tree /var/run/libvirt/
.
├── hostdevmgr
├── interface
│ └── driver.pid
├── libvirt-admin-sock
├── libvirt-sock
├── libvirt-sock-ro
├── network
│ ├── autostarted
│ ├── driver.pid
│ ├── nwfilter.leases
│ ├── ;vdsmdummy;.xml
│ └── vdsm-ovirtmgmt.xml
├── nodedev
│ └── driver.pid
├── nwfilter
│ └── driver.pid
├── nwfilter-binding
│ └── vnet0.xml
├── qemu
│ ├── autostarted
│ ├── driver.pid
│ ├── HostedEngine.pid
│ ├── HostedEngine.xml
│ └── slirp
├── secrets
│ └── driver.pid
├── storage
│ ├── autostarted
│ └── driver.pid
├── virtlockd-sock
├── virtlogd-admin-sock
└── virtlogd-sock
10 directories, 22 files
[root@medusa libvirt]#
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement:
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VUXIOEH2V4S...