On Tue, May 31, 2022 at 12:37 PM Andrei Verovski <andreil1@starlett.lv> wrote:
Hi, Arik,
Thanks for help.
su - postgres psql engine select vm_guid from vm_static where vm_name='WInServerTerminal-2022'; select status from vm_dynamic where vm_guid='7871067f-221c-48ed-a046-f49499ce9be4'; update vm_dynamic set status = 1 where vm_guid='7871067f-221c-48ed-a046-f49499ce9be4'; update vm_dynamic set run_on_vds='33453044-4139-5A43-3334-323638385838' where vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';
ERROR: insert or update on table "vm_dynamic" violates foreign key constraint "vds_static_vm_dynamic_r" DETAIL: Key (run_on_vds)=(33453044-4139-5a43-3334-323638385838) is not present in table "vds_static”.
Something is wrong with last query. '33453044-4139-5A43-3334-323638385838’ is node UUID from oVirt -> Hosts.
What is correct format with this query ?
It seems this host doesn't exist in the DB. You may check your hosts by running: select * from vds_static;
On 31 May 2022, at 11:33, Arik Hadas <ahadas@redhat.com> wrote:
On Mon, May 30, 2022 at 5:21 PM Andrei Verovski <andreil1@starlett.lv> wrote:
Hi,
Digging old notes, which unfortunately were not complete, I found also
this query, which was marked as necessary:
update vm_dynamic set run_on_vds='3c854f9c-2cdd-423e-bca0-37964ba76702'
where vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';
but I didn’t remember what is run_on_vds='3c854f9c-2cdd-423e-bca0-37964ba76702’
Is this UUID of the node problematic VM is running on?
Yes, it should be the UUID of the host that the VM runs on - but the issue this update can solve has been addressed and we didn't see it for quite a while since then, so unless run_on_vds is set to null I wouldn't go this way but rather check what happens within the guest and if there's anything unusual in the vdsm log
Thanks.
On 29 May 2022, at 18:44, Liran Rotenberg <lrotenbe@redhat.com> wrote:
On Thu, May 26, 2022 at 4:36 PM Andrei Verovski <andreil1@starlett.lv>
Hi,
engine=# update vm_dynamic set status = 1 where
vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';
UPDATE 1
Seems like success, but it is not.
After few seconds: engine=# select status from vm_dynamic where vm_guid='7871067f-221c-48ed-a046-f49499ce9be4'; status -------- 10 (1 row)
Looks like oVirt Engine itself checks something and changes status to “10” (Rebooting) again.
Is it possible this is somehow related to "virtio-win-0.1.217” I installed recently on this Windows Server 2022 VM?
Yes, the engine sets the VM status based on the report from VDSM. VDSM takes the report from the guest-agent, in this case - the one
Can you make sure it is installed? Also, try to look in vdsm.log if by searching QEMU you can see one message about getting new capabilities for
wrote: provided by virtio-win (for windows VMs). the VM?
Another option would be to try and check qemu-ga calls to the VM.
Thanks in advance for any suggestions.
On 26 May 2022, at 14:53, Liran Rotenberg <lrotenbe@redhat.com> wrote:
On Wed, May 25, 2022 at 5:52 PM Andrei Verovski <andreil1@starlett.lv>
wrote:
Hi,
I have VM which have restarted successfully yet in oVirt web it is
being shown with “Rebooting” status for a very long time.
I did:
su - postgres psql engine select vm_guid from vm_static where vm_name='WInServerTerminal-2022’; engine=# select status from vm_dynamic where
vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';
status -------- 10 (1 row)
How to properly correct status from "Rebooting”?
Hi Andrei, If you wish to change manually the VM status to 'UP' status you may use: # update vm_dynamic set status = 1 where vm_guid='7871067f-221c-48ed-a046-f49499ce9be4';
The statuses are the following (VMStatus ENUM): Unassigned(-1), Down(0), Up(1), PoweringUp(2), Paused(4), MigratingFrom(5), MigratingTo(6), Unknown(7), NotResponding(8), WaitForLaunch(9), RebootInProgress(10), SavingState(11), RestoringState(12), Suspended(13), ImageIllegal(14), ImageLocked(15), PoweringDown(16);
Regards, Liran
Thanks in advance Andrei _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/FSZZOMGVJACZHH...
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/SZRORWV6MIOVR3...
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/CRLYFHFGJNYXTQ...
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/7MZQEJUGROKRDY...