I have orphaned disks on my fiber channel that I need to remove, so I was trying to find a way to definitively identify the disk LVM ids so that I can remove the LVMs from the fiber channel manually. Since oVirt does not account for them for me.
Basically it all started when I wanted to import/move some vms
before a migration. I exported some VMs to an iscsi storage, then
I migrated my fiber channel to a new oVirt environment that I
connected that iscsi storage to as well. This created a problem as
I now had a duplicate disk on the Fibre channel and the iscsi, so
I could not simply move the disk back. Anyway I am in a situation
now where I have some disks I want to remove, however there is no
longer a VM tied to them. But before I remove the iscsi version of
the VM I do have a chance to recover the lvm ID.
That is what I am trying to do, reliably get a VMs complete list
of LVM ids.
On Thu, Dec 20, 2018 at 6:28 PM Jacob Green <jgreen@aasteel.com> wrote:
What if you cannot run the VM, so its not running on any specific host. But you want the XML to identify the <disk> information.
Thank you.
On 12/20/2018 09:10 AM, Benny Zlotnik wrote:
You can run `virsh -r dumpxml <vm name> ` on the relevant host
On Thu, Dec 20, 2018, 16:17 Jacob Green <jgreen@aasteel.com wrote:
How does one get an XML dump of a VM from ovirt? I have seen ovirt
do it in the engine.log, but not sure how to force it to generate one
when I need it.
oVirt doesn't store the domain xml internally.The domain xml is generated only when trying to start the vm (that's the output you've seen in engine.log).I'm afraid there is no other trigger to force generating that xml at the moment.But the generation of the xml is mostly 1:1 mapping of some configuration that is stored differently in oVirt and can be found via the ui/rest-api. What do you look for exactly?_______________________________________________
Thank you.
--
Jacob Green
Systems Admin
American Alloy Steel
713-300-5690
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/YV7K4GQZID2UC2SPS3PNDEKQUDZ5HLGV/
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/LNQTWNT3HLXPXOPZOUMBYTV4HOORAQ75/
-- Jacob Green Systems Admin American Alloy Steel 713-300-5690
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/JH4K6SH2DB7EB52KKE2CTD43PJFUMMVX/
-- Jacob Green Systems Admin American Alloy Steel 713-300-5690