[ovirt-users] Re: Error exporting into ova
BTW: This is the message I get on the import:
VDSM nucvirt command HSMGetAllTasksStatusesVDS failed: value=low level Image
copy failed: ("Command ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none',
'-T', 'none', '-f', 'qcow2',
'/rhev/data-center/mnt/petitcent.mtk.hoberg.net:_flash_export/fe9fb0db-2743-457a-80f0-9a4edc509e9d/images/3be7c1bb-377c-4d5e-b4f6-1a6574b8a52b/845cdd93-def8-4d84-9a08-f8c991f89fe3',
'-O', 'raw',
'/rhev/data-center/mnt/glusterSD/nucvirt.mtk.hoberg.net:_vmstore/ba410e27-458d-4b32-969c-ad0c37edaceb/images/3be7c1bb-377c-4d5e-b4f6-1a6574b8a52b/845cdd93-def8-4d84-9a08-f8c991f89fe3']
failed with rc=1 out=b'' err=bytearray(b'qemu-img: error while writing sector
9566208: No such file or directory\\n')",) abortedcode=261
8/29/2011:41:21 AM
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/QRZ5FQVWLMIJ2LBQC7ZLZ4XGWKRMLBQY/
[ovirt-users] Re: Error exporting into ova
> On Fri, Aug 28, 2020 at 2:31 AM > You should really try the attach/detach storage domain, this is the > recommended way to move > vms from one ovirt system to another. > > You could detach the entire domain with all vms from the old system, > and connect it to the new > system, without copying even one bit. > > I guess you cannot do this because you don't use shared storage? > These are all HCI setups with GlusterFS, so storage is shared in a way... I am also experimenting with a backup (not export) domain on NFS and/or removable media (just temp local storage, exported via NFS), but the handling is very odd, to say the least (see my other post for the full story). Basically the documentation says you move all VM disks to the backup domain after cloning the VM. And then it says nothing more... (how does the VM definition get carried over? Can I then destroy the remaing clone VM? Do I need to re-create a similar VM at the target? etc.) The in-place upgrade producedure in the docs for the HCI case has far too many tersly described steps that can go wrong with someone like me doing it: I even manage to fail a green-field setup many times somehow And even if I were to do the upgrade as described, I do need to know that the export/clean-migration/import is still a viable option, should something go wrong. > ... > > Using ovirt 4.3 when 4.4 was released is going to be painful, don't do this. > That's why I am migrating, but for that I need to prove a working plan B > ... > > You are hitting https://bugzilla.redhat.com/1854888 > Unfortunately the description doesn't tell if the failure of the silent qemu-img was on the export side, resulting a corrupted image: I am assuming that qemu-img is used in both export and import. The failure on the import is not silent, just doesn't seem to make a lot of sense, because qemu-img is reporting a write error at the local single node HCI gluster target, which has plenty of space and is essentially a loopback in 1nHCI. > ... > > No, export domain is using qemu-img, which is the best tool for copying > images. > This is how all disks are copied in oVirt in all flows. There are no > issues like ignored > errors or silent failures in storage code. My problem is getting errors and now understanding what's causing them. Qemu-img on the target HCI single node Gluster is reporting a write error at varying block numbers, often after dozens of gigabytes have already been transferred. There is plenty of space on the Gluster, an SSD with VDO underneath so the higher risk is actually the source, which is the NFS mount from the export domain. I've tried uploading the image using imageio and your Python sample from the SDK, but just as I had done that (with 50MB/s at 1/6 of the performance of the qemu-img transfer), I managed to kill the 4.4 cluster by downgrading the machine type of the hosted-engine, when I was really trying to make a successfully restored VM work with renamed Ethernet devices... The upload via imageio completed fully, I hadn't tested the disk image with a machine yet to see if it would boot. > > ... > > There are no timeouts in storage code, e.g. attach/detach domain, or > export to export > domain. > > Nir Well, that was almost my last hope, because I don't know what could make the qemu-img import transfer fail on a write, when the very same image works with imageio... Actually, the big difference there is that the resulting disk, which is logically configured at 500GB is actually logically consuming 500GB in the domain, while sparse images that make it successfully through qemu-img, retain their much smaller actual size. VDO is still underneath so it may not matter, and I didn't have a chance to try sparsify before I killed the target cluster. I have also prepared a USB3 disk to act as export domain, which I'll physically move, just to ensure the NFS pipe in the qemu-img job isn't the real culprit. And I guess I'll try the export again, to see if I overlooked some error there. > > > Nir ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/VDKIOFLJSEGSXV64FJ6BHZVGKS5LYHWH/
[ovirt-users] Re: How to Backup a VM
Struggling with bugs and issues on OVA export/import (my clear favorite otherwise, especially when moving VMs between different types of hypervisors), I've tried pretty much everything else, too. Export domains are deprecated and require quite a bit of manual handling. Unfortunately the buttons for the various operations are all over the place e.g. the activation and maintenance toggles are in different pages. In the end the mechanisms underneath (qemu-img) seem very much the same and suffer from the same issues (I have larger VMs that keep failing on imports). So far the only fool-proof method has been to use the imageio daemon to upload and download disk images, either via the Python API or the Web-GUI. Transfer times are terrible though, 50MB/s is quite low when the network below is 2.5-10Gbit and SSDs all around. Obviously with Python as everybody's favorite GUI these days, you can also copy and transfer the VMs complete definition, but I am one of those old guys, who might even prefer a real GUI to mouse clicks on a browser. The documentation on backup domains is terrible. What's missing behind the 404 link in oVirt becomes a very terse section in the RHV manuals, where you're basically just told that after cloning the VM, you should then move its disks to the backup domain... What you are then supposed to do with the cloned VM, if it's ok to simplay throw it away, because the definition is silently copied to the OVF_STORE on the backup... none of that is explained or mentioned. There is also no procedure for restoring a machine from a backup domain, when really a cloning process that allows a target domain would be pretty much what I'd vote for. Redhat really wants you to buy the professional product there, or use the Python GUI. I've sadly found the OVA files generated by oVirt (QEMU, really) to be incompatible with both VMware Workstation 15.5 and VirtualBox 6.12. No idea who's fault this is, but both sides are obviously not doing plug-fests every other week and I'm pretty sure this could be fixed manually when needed. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/IHTKTQJ6CWD27NOPUQTU3NOEMPPHDPNI/
[ovirt-users] Re: Hosted Engine stuck in Firmware
Thanks for diving into that mess first, because it allowed me to understand what I had done as well... In my case the issue was a VM moved from 4.3 to 4.4 seemed to be silently upgraded from "default" (whatever was default on 4.3) to "Q35", which seems to be the new default of 4.4. But that had it lose the network, because udev was now renaming the NIC in yet another manner, when few VMs ever need anything beyond eth0 anyway. So I went ahead and changed the cluster default to those of the 4.3 cluster (including Nehalem CPUs, because I also use J5005 Atom systems). BTW, that was initially impossible as the edit-button for the cluster ways always greyed out. But on a browser refresh, it suddenly was enabled... What I don't remember is if the cluster had a BIOS default (it doesn't on 4.3), or if I changed that in the default template, which is mentioned somewhere here as being rather distructive. I was about to re-import the machine from an export domain, when I did a scheduled reboot of the single node HCI cluster after OS updates. Those HCI reboots always require a bit ot twiddling on 4.3 and 4.4 for the hosted-engine to start, evidently because of some race conditions (requiring restarts of glusterd/ovirt-ha-broker/ovirt-ha-agent/vdsmd to fix), but this time the SHE simply didn't want to start at all, complaining about missing PCI devices at boot after some digging through log files. With my 4.4. instance currently dead I don't remember if the BIOS or PCI vs PCIe machine type is a cluster attribute or part of the template but I do seem to remember that the hosted-engine is a bit special here, especially when it comes to picking up the base CPU type. What is a bit astonishing is the fall-through processing that seems to go on here, when an existing VM should have its hardware nailed down when it was shut down. It then realized that I might have killed the hosted-engine right there. And no, /var/run/ovirt...vm.cfg is long gone and I guess it's time for a re-install. For me one issue remains unclear: How identical do machines remain as they are moved from a 4.3 host to a 4.4 host? In my view a hypervisor's most basic social contract is to turn a machine into a file and the file back into the very same machine, hopefully even for decades. Upgrade of the virtual hardware should be possible, but under controll of the user/orchestrator. I am afraid that oVirt's dynamic reconstruction of the machine from database data doesn't always respect that social contract and that needs at least documentation, if not fixing. The 4.3 to 4.4 migration is far from seamless already, this does not help. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/ANWFNF6WW53FADMBW5WZR4C3QCV5L765/
[ovirt-users] Re: How to Backup a VM
Interesting I’ve not hit that issue myself. I’d think it must somehow be related to getting the event status. Is it happening to the same vms every time? Is there anything different about the vm names or anything that would set them apart from the others that work? On Sun, Aug 30, 2020 at 11:56 AM Stefan Wolf wrote: > OK, > > > > I ve run the backup three times . > > I still have two machines, where it still fails on TASK [Wait for export] > > I think the Problem is not the timeout, in oVirt engine the export has > already finished : " > > Exporting VM VMName as an OVA to /home/backup/in_progress/VMName.ova on > Host kvm360" > > But [Wait for export] still counts to 1 exit with error and move on to the > next task > > > > bye shb > > ___ > > Users mailing list -- users@ovirt.org > > To unsubscribe send an email to users-le...@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/W65G6ZUL6C6UJAJI627WVGITGIUUJ2XZ/ > > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/CEC5GLU5JF7S7JEMAPSWEJ675UEXR6PT/
[ovirt-users] Re: How to Backup a VM
OK, I ve run the backup three times . I still have two machines, where it still fails on TASK [Wait for export] I think the Problem is not the timeout, in oVirt engine the export has already finished : " Exporting VM VMName as an OVA to /home/backup/in_progress/VMName.ova on Host kvm360" But [Wait for export] still counts to 1 exit with error and move on to the next task bye shb ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/W65G6ZUL6C6UJAJI627WVGITGIUUJ2XZ/
[ovirt-users] Re: deprecating export domain?
While I am trying to prepare a migration from 4.3 to 4.4 with the base OS switch, I am exploring all variants of moving VMs. OVA export/import and export domains have issues and failures so now I am trying backup domains and fail to understand how they are to be used and the sparse documentation does not help. It says: 1. create a clone VM 2. move the cloned VM's disks to the backup domain and then moves on to the next topic What I find missing: 1. How do I move the cloned VM (basically whatever configuration data is not inside the disk) away from the active domain? 2. Can I just delete it, because 'magically' the OVF store on the backup domain will contain all VM data for any VM that has disk images there? 3. A matching reovery/restore procdure: Is it really just as simple as moving the disk back (with the OVF/XML definition silently following)? In terms of usability I'd really love a clone where I can specify the storage domain target... ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/XOXKJAONF2EF5GCFHC7FX2IDHTPGX35Q/
[ovirt-users] Re: How to Backup a VM
yes you are right, I ve already found. But this was not realy my problem. It causes from the HostedEngine. Long time ago I ve decreased the memory. It seems that this was the problem. now it is seems to be working pretty well. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/KVTFZHUV7URK6GBEEO5OE2BDYIFPRJ5F/
[ovirt-users] Re: How to Backup a VM
Also if you look at the blog post linked on github page it has info about increasing the ansible timeout on ovirt engine machine. This will be necessary when dealing with large vms that take over 2 hours to export On Sun, Aug 30, 2020 at 8:52 AM Jayme wrote: > You should be able to fix by increasing the timeout variable in main.yml. > I think the default is pretty low around @ 600 seconds (10 minutes). I have > mine set for a few hours since I’m dealing with large vms. I’d also > increase poll interval as well so it’s not checking for completion every 10 > seconds. I set my poll interval to 5 minutes. > > I backup many large vms (over 1tb) with this playbook for the past several > months and never had a problem with it not completing. > > On Sun, Aug 30, 2020 at 3:39 AM Stefan Wolf wrote: > >> Hello, >> >> >> >> >https://github.com/silverorange/ovirt_ansible_backup >> >> I am also still using 4.3. >> >> In my opinion this is by far the best and easiest solution for disaster >> recovery. No need to install an appliance, and if there is a need to >> recover, you can import the ova in every hypervisor - no databases, no >> dependency. >> >> >> >> Sometimes I ve issues with "TASK [Wait for export] " sometime it takes to >> long to export the ova. an I also had the problem, that the export already >> finished, but it was not realized by the script. In ovirt the export was >> finished and the filename was renamed from *.tmp to *.ova >> >> >> >> maybe you have an idea for me. >> >> >> >> thanks bye >> >> ___ >> >> Users mailing list -- users@ovirt.org >> >> To unsubscribe send an email to users-le...@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/Q7TKVK5TL6HT7DQZCY354ICK5J3JRDH4/ >> >> > > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/UN2U3U3UD7ZRTJASWLQCAF34ELQSOJFN/
[ovirt-users] Re: How to Backup a VM
You should be able to fix by increasing the timeout variable in main.yml. I think the default is pretty low around @ 600 seconds (10 minutes). I have mine set for a few hours since I’m dealing with large vms. I’d also increase poll interval as well so it’s not checking for completion every 10 seconds. I set my poll interval to 5 minutes. I backup many large vms (over 1tb) with this playbook for the past several months and never had a problem with it not completing. On Sun, Aug 30, 2020 at 3:39 AM Stefan Wolf wrote: > Hello, > > > > >https://github.com/silverorange/ovirt_ansible_backup > > I am also still using 4.3. > > In my opinion this is by far the best and easiest solution for disaster > recovery. No need to install an appliance, and if there is a need to > recover, you can import the ova in every hypervisor - no databases, no > dependency. > > > > Sometimes I ve issues with "TASK [Wait for export] " sometime it takes to > long to export the ova. an I also had the problem, that the export already > finished, but it was not realized by the script. In ovirt the export was > finished and the filename was renamed from *.tmp to *.ova > > > > maybe you have an idea for me. > > > > thanks bye > > ___ > > Users mailing list -- users@ovirt.org > > To unsubscribe send an email to users-le...@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/Q7TKVK5TL6HT7DQZCY354ICK5J3JRDH4/ > > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/FSD7CVYYHG2LLOJGBJFYSMY2DXOFGBUZ/
[ovirt-users] Re: Error exporting into ova
On Fri, Aug 28, 2020 at 2:31 AM wrote: > > I am testing the migration from CentOS7/oVirt 4.3 to CentOS8/oVirt 4.4. > > Exporting all VMs to OVAs, and re-importing them on a new cluster built from > scratch seems the safest and best method, because in the step-by-step > migration, there is simply far too many things that can go wrong and no easy > way to fail-back after each step. You should really try the attach/detach storage domain, this is the recommended way to move vms from one ovirt system to another. You could detach the entire domain with all vms from the old system, and connect it to the new system, without copying even one bit. I guess you cannot do this because you don't use shared storage? ... > So I have manually put the single-line fix in, which settles udev to ensure > that disks are not exported as zeros. That's the bug which renders the final > release oVirt 4.3 forever unfit, 4 years before the end of maintenance of > CentOS7, because it won't be fixed there. Using ovirt 4.3 when 4.4 was released is going to be painful, don't do this. ... > But just as I was exporting not one of the trivial machines, that I have been > using for testing, but one of the bigger ones, that actually contain a > significant amout of data, I find myself hitting this timeout bug. > > The disks for both the trival and less-trivial are defined at 500GB, thinly > allocated. The trivial is the naked OS at something like 7GB actually > allocated, the 'real' has 113GB allocated. In both cases the OVA export file > to a local SSD xfs partition is 500GB, with lots of zeros and sparse > allocation in the case of the first one. > > The second came to 72GB of 500GB actually allocated, which didn't seem like a > good sign already, but perhaps there was some compression involved? > > Still the export finished without error or incident and the import on the > other side went just as well. The machine even boots and runs, it was only > once I started using it, that I suddenly had all types of file system > errors... it turns out 113-73GB were actually really cut off and missing from > the OVA export, and there is nobody and nothing checking for that. You are hitting https://bugzilla.redhat.com/1854888 ... > I have the export domain backup running right now, but I'm not sure it's not > using the same mechanism under the cover with potentially similar results. No, export domain is using qemu-img, which is the best tool for copying images. This is how all disks are copied in oVirt in all flows. There are no issues like ignored errors or silent failures in storage code. ... > P.P.S. So just where (and on which machine) do I need to change the timeout? There are no timeouts in storage code, e.g. attach/detach domain, or export to export domain. Nir Nir ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/Z5BMSR6OGW7I4AU363QH562MY7HJ57NV/
[ovirt-users] Re: shutdown virtual machine did not display in the list when using virsh list --all and virsh list --state-shutoff
On Sun, Aug 30, 2020 at 11:49 AM Arik Hadas wrote: > > > > On Sun, Aug 30, 2020 at 10:26 AM Yedidyah Bar David wrote: >> >> Hi, >> >> On Sun, Aug 30, 2020 at 9:55 AM Kyre wrote: >> > >> > Hello, I am using ovirt 4.3.8. I want to use the virsh command to boot the >> > shutdown virtual machine, but when using virsh list --all and virsh list >> > --state-shutoff, the shutdown virtual machine did not display in the list. >> > What is the cause of this, and how can I display the shutdown virtual >> > machine. >> >> You can't. >> >> All oVirt-managed VMs are, in libvirt terms, transient. The meta-data >> about them is kept in the engine's database, not in libvirt. > > > This is no longer the case - in 2017 we switched to persistent domains > (https://gerrit.ovirt.org/c/78046) > When the engine issues a 'destroy' call, VDSM undefines the VM Which makes the VM transient. I think the reason we switched to "persistent" VM was to use VM metadata, and use more common code paths that are less likely to break. Even if we keep the VMs defined, you may not be able to start them later since the storage required by the VM may not be available on the host at the point you start the VM later (.e.g. after reboot). If the storage is available, starting a VM behind engine back may lead a split brain since the VM may be running on another host. The right way to manage oVirt VMs is using engine API. Since we removed the oVirt shell, there is no easy way like virsh, but one can script this using the SDK. Nir >> If you want this to plan for (or already are in) a case where the >> engine is dead/unavailable, then you should make sure you keep regular >> engine backups, so that you can restore it, and/or check about DR. >> >> Best regards, >> >> > >> > virsh # list --all >> > Please enter your authentication name: root >> > Please enter your password: >> > IdName State >> > >> > 4 win10E2 running >> > >> > virsh # list --state-shutoff >> > IdName State >> > >> > >> > >> > ___ >> > Users mailing list -- users@ovirt.org >> > To unsubscribe send an email to users-le...@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/JGFSRX5YF3GK5DBI6EVQBSEJ34VUM66E/ >> >> >> >> -- >> Didi >> ___ >> Users mailing list -- users@ovirt.org >> To unsubscribe send an email to users-le...@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/PD6Y4LWKVVNI4NPQBBJEPQEWROF7ZPYQ/ > > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@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/KXV3XVLZZQ7627VWPA2VAUA4S5YSPG3M/ ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/OSAI7XPC6V2RMISYVJJVYCYI7PR6LKPB/
[ovirt-users] Re: How to Backup a VM
Checking the timestamp (diff between now and timestamp) of the exportfile could also an option to verify if the export is still ongoing instead of using the ovirt_event_info. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/2PUIMPYCMKROW3R3DPAWP7I5M4J4LK3O/
[ovirt-users] Re: shutdown virtual machine did not display in the list when using virsh list --all and virsh list --state-shutoff
On Sun, Aug 30, 2020 at 10:26 AM Yedidyah Bar David wrote: > Hi, > > On Sun, Aug 30, 2020 at 9:55 AM Kyre wrote: > > > > Hello, I am using ovirt 4.3.8. I want to use the virsh command to boot > the shutdown virtual machine, but when using virsh list --all and virsh > list --state-shutoff, the shutdown virtual machine did not display in the > list. What is the cause of this, and how can I display the shutdown virtual > machine. > > You can't. > > All oVirt-managed VMs are, in libvirt terms, transient. The meta-data > about them is kept in the engine's database, not in libvirt. > This is no longer the case - in 2017 we switched to persistent domains ( https://gerrit.ovirt.org/c/78046) When the engine issues a 'destroy' call, VDSM undefines the VM > > If you want this to plan for (or already are in) a case where the > engine is dead/unavailable, then you should make sure you keep regular > engine backups, so that you can restore it, and/or check about DR. > > Best regards, > > > > > virsh # list --all > > Please enter your authentication name: root > > Please enter your password: > > IdName State > > > > 4 win10E2 running > > > > virsh # list --state-shutoff > > IdName State > > > > > > > > ___ > > Users mailing list -- users@ovirt.org > > To unsubscribe send an email to users-le...@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/JGFSRX5YF3GK5DBI6EVQBSEJ34VUM66E/ > > > > -- > Didi > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@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/PD6Y4LWKVVNI4NPQBBJEPQEWROF7ZPYQ/ > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/KXV3XVLZZQ7627VWPA2VAUA4S5YSPG3M/
[ovirt-users] Re: shutdown virtual machine did not display in the list when using virsh list --all and virsh list --state-shutoff
Hi, On Sun, Aug 30, 2020 at 9:55 AM Kyre wrote: > > Hello, I am using ovirt 4.3.8. I want to use the virsh command to boot the > shutdown virtual machine, but when using virsh list --all and virsh list > --state-shutoff, the shutdown virtual machine did not display in the list. > What is the cause of this, and how can I display the shutdown virtual machine. You can't. All oVirt-managed VMs are, in libvirt terms, transient. The meta-data about them is kept in the engine's database, not in libvirt. If you want this to plan for (or already are in) a case where the engine is dead/unavailable, then you should make sure you keep regular engine backups, so that you can restore it, and/or check about DR. Best regards, > > virsh # list --all > Please enter your authentication name: root > Please enter your password: > IdName State > > 4 win10E2 running > > virsh # list --state-shutoff > IdName State > > > > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@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/JGFSRX5YF3GK5DBI6EVQBSEJ34VUM66E/ -- Didi ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/PD6Y4LWKVVNI4NPQBBJEPQEWROF7ZPYQ/
[ovirt-users] shutdown virtual machine did not display in the list when using virsh list --all and virsh list --state-shutoff
Hello, I am using ovirt 4.3.8. I want to use the virsh command to boot the shutdown virtual machine, but when using virsh list --all and virsh list --state-shutoff, the shutdown virtual machine did not display in the list. What is the cause of this, and how can I display the shutdown virtual machine. virsh # list --all Please enter your authentication name: root Please enter your password: Id Name State 4 win10E2 running virsh # list --state-shutoff Id Name State ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/JGFSRX5YF3GK5DBI6EVQBSEJ34VUM66E/
[ovirt-users] Re: How to Backup a VM
Hello, >https://github.com/silverorange/ovirt_ansible_backup I am also still using 4.3. In my opinion this is by far the best and easiest solution for disaster recovery. No need to install an appliance, and if there is a need to recover, you can import the ova in every hypervisor - no databases, no dependency. Sometimes I ve issues with "TASK [Wait for export] " sometime it takes to long to export the ova. an I also had the problem, that the export already finished, but it was not realized by the script. In ovirt the export was finished and the filename was renamed from *.tmp to *.ova maybe you have an idea for me. thanks bye ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/Q7TKVK5TL6HT7DQZCY354ICK5J3JRDH4/
