[ovirt-users] New install
I have an issue with new installation. The server name is changing all the time and it keep disconnecting me. Plus it is impossible to log in as admin. The install went through without any issues, but it seems something is wrong. Server: engine01..com Log in with your server user account. Server: node01..com Log in with your server user account. ___ 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/UHVDOCWPYAFT4BRKNO2GBYM3IQTG6H2O/
[ovirt-users] Re: How to discover why a VM is getting suspended without recovery possibility?
Hi, sorry to bump the thread. But I still with this issue on the VM. This crashes are still happening, and I really don’t know what to do. Since there’s nothing on logs, except from that message on `dmesg` of the host machine I started changing setting to see if anything changes or if I at least I get a pattern. What I’ve tried: 1. Disabled I/O Threading on VM. 2. Increased I/O Threading to 2 form 1. 3. Disabled Memory Balooning. 4. Reduced VM resources form 10 CPU’s and 48GB of RAM to 6 CPU’s and 24GB of RAM. 5. Moved the VM to another host. 6. Dedicated a host specific to this VM. 7. Check on the storage system to see if there’s any resource starvation, but everything seems to be fine. 8. Checked both iSCSI switches to see if there’s something wrong with the fabrics: 0 errors. I’m really running out of ideas. The VM was working normally and suddenly this started. Thanks, PS: When I was typing this message it crashed again: [427483.126725] *** Guest State *** [427483.127661] CR0: actual=0x00050032, shadow=0x00050032, gh_mask=fff7 [427483.128505] CR4: actual=0x2050, shadow=0x, gh_mask=f871 [427483.129342] CR3 = 0x0001849ff002 [427483.130177] RSP = 0xb10186b0 RIP = 0x8000 [427483.131014] RFLAGS=0x0002 DR7 = 0x0400 [427483.131859] Sysenter RSP= CS:RIP=: [427483.132708] CS: sel=0x9b00, attr=0x08093, limit=0x, base=0x7ff9b000 [427483.133559] DS: sel=0x, attr=0x08093, limit=0x, base=0x [427483.134413] SS: sel=0x, attr=0x08093, limit=0x, base=0x [427483.135237] ES: sel=0x, attr=0x08093, limit=0x, base=0x [427483.136040] FS: sel=0x, attr=0x08093, limit=0x, base=0x [427483.136842] GS: sel=0x, attr=0x08093, limit=0x, base=0x [427483.137629] GDTR: limit=0x0057, base=0xb10186eb4fb0 [427483.138409] LDTR: sel=0x, attr=0x1, limit=0x000f, base=0x [427483.139202] IDTR: limit=0x, base=0x [427483.139998] TR: sel=0x0040, attr=0x0008b, limit=0x0067, base=0xb10186eb3000 [427483.140816] EFER = 0x PAT = 0x0007010600070106 [427483.141650] DebugCtl = 0x DebugExceptions = 0x [427483.142503] Interruptibility = 0009 ActivityState = [427483.143353] *** Host State *** [427483.144194] RIP = 0xc0c65024 RSP = 0x9253c0b9bc90 [427483.145043] CS=0010 SS=0018 DS= ES= FS= GS= TR=0040 [427483.145903] FSBase=7fcc13816700 GSBase=925adf24 TRBase=925adf244000 [427483.146766] GDTBase=925adf24c000 IDTBase=ff528000 [427483.147630] CR0=80050033 CR3=0010597b6000 CR4=001627e0 [427483.148498] Sysenter RSP= CS:RIP=0010:8f196cc0 [427483.149365] EFER = 0x0d01 PAT = 0x0007050600070106 [427483.150231] *** Control State *** [427483.151077] PinBased=003f CPUBased=b6a1edfa SecondaryExec=0ceb [427483.151942] EntryControls=d1ff ExitControls=002fefff [427483.152800] ExceptionBitmap=00060042 PFECmask= PFECmatch= [427483.153661] VMEntry: intr_info= errcode=0006 ilen= [427483.154521] VMExit: intr_info= errcode= ilen=0004 [427483.155376] reason=8021 qualification= [427483.156230] IDTVectoring: info= errcode= [427483.157068] TSC Offset = 0xfffccfc261506dd9 [427483.157905] TPR Threshold = 0x0d [427483.158728] EPT pointer = 0x0009b437701e [427483.159550] PLE Gap=0080 Window=0008 [427483.160370] Virtual processor ID = 0x0004 > On 16 Sep 2020, at 17:11, Vinícius Ferrão wrote: > > Hello, > > I’m an Exchange Server VM that’s going down to suspend without possibility of > recovery. I need to click on shutdown and them power on. I can’t find > anything useful on the logs, except on “dmesg” of the host: > > [47807.747606] *** Guest State *** > [47807.747633] CR0: actual=0x00050032, shadow=0x00050032, > gh_mask=fff7 > [47807.747671] CR4: actual=0x2050, shadow=0x, > gh_mask=f871 > [47807.747721] CR3 = 0x001ad002 > [47807.747739] RSP = 0xc20904fa3770 RIP = 0x8000 > [47807.747766] RFLAGS=0x0002 DR7 = 0x0400 > [47807.747792] Sysenter RSP= CS:RIP=: > [47807.747821] CS: sel=0x9100, attr=0x08093, limit=0x, > base=0x7ff91000 > [47807.747855] DS: sel=0x, attr=0x08093, limit=0x, > base=0x > [47807.747889] SS: sel=0x, attr=0x08093, limit=0x, > base=0x > [47807.747923] ES: sel=0x,
[ovirt-users] Re: hosted engine migration
so strange! After I set global maintenance, powered off and started H The cpu of HE became 'Westmere'(did not change anything). But HE still could not be migrated. HE xml: Westmere host capabilities: Westmere cluster cpu type (UI): host cpu type (UI): HE cpu type (UI): 在 2020-09-19 13:27:35，"Strahil Nikolov" 写道： >Hm... interesting. > >The VM is using 'Haswell-noTSX' while the host is 'Westmere'. > >In my case I got no difference: > >[root@ovirt1 ~]# virsh dumpxml HostedEngine | grep Opteron > Opteron_G5 >[root@ovirt1 ~]# virsh capabilities | grep Opteron > Opteron_G5 > >Did you update the cluster holding the Hosted Engine ? > > >I guess you can try to: > >- Set global maintenance >- Power off the HostedEngine VM >- virsh dumpxml HostedEngine > /root/HE.xml >- use virsh edit to change the cpu of the HE (non-permanent) change >- try to power on the modified HE > >If it powers on , you can try to migrate it and if it succeeds - then you >should make it permanent. > > > > > >Best Regards, >Strahil Nikolov > >В петък, 18 септември 2020 г., 04:40:39 Гринуич+3, ddqlo >написа: > > > > > >HE: > > > HostedEngine > b4e805ff-556d-42bd-a6df-02f5902fd01c > http://ovirt.org/vm/tune/1.0; > xmlns:ovirt-vm="http://ovirt.org/vm/1.0;> > >http://ovirt.org/vm/1.0;> >4.3 >False >false >1024 > type="int">1024 >auto_resume >1600307555.19 > >external > >4 > > > >ovirtmgmt > >4 > > > > > c17c1934-332f-464c-8f89-ad72463c00b3 >/dev/vda2 > > 8eca143a-4535-4421-bd35-9f5764d67d70 >---- >exclusive > > ae961104-c3b3-4a43-9f46-7fa6bdc2ac33 > >1 > > > > > c17c1934-332f-464c-8f89-ad72463c00b3 > > 8eca143a-4535-4421-bd35-9f5764d67d70 > type="int">108003328 > > /dev/c17c1934-332f-464c-8f89-ad72463c00b3/leases > > /rhev/data-center/mnt/blockSD/c17c1934-332f-464c-8f89-ad72463c00b3/images/8eca143a-4535-4421-bd35-9f5764d67d70/ae961104-c3b3-4a43-9f46-7fa6bdc2ac33 > > ae961104-c3b3-4a43-9f46-7fa6bdc2ac33 > > > > > > > 67108864 > 16777216 > 16777216 > 64 > 1 > >/machine > > > > oVirt > oVirt Node > 7-5.1804.el7.centos > ----0CC47A6B3160 > b4e805ff-556d-42bd-a6df-02f5902fd01c > > > >hvm > > > > > > > > >Haswell-noTSX > > > > > > > > > > > > > > > > > > destroy > destroy > destroy > > > > > >/usr/libexec/qemu-kvm > > > > > > > > > > io='native' iothread='1'/> > dev='/var/run/vdsm/storage/c17c1934-332f-464c-8f89-ad72463c00b3/8eca143a-4535-4421-bd35-9f5764d67d70/ae961104-c3b3-4a43-9f46-7fa6bdc2ac33'> > > > > > 8eca143a-4535-4421-bd35-9f5764d67d70 > > function='0x0'/> > > > > > function='0x0'/> > > > > function='0x1'/> > > > > function='0x0'/> > > > > function='0x2'/> > > > > > > c17c1934-332f-464c-8f89-ad72463c00b3 > ae961104-c3b3-4a43-9f46-7fa6bdc2ac33 > offset='108003328'/> > > > > > > > > > > > > function='0x0'/> > > > > > > > > > > > > function='0x0'/> > > > path='/var/run/ovirt-vmconsole-console/b4e805ff-556d-42bd-a6df-02f5902fd01c.sock'/> > > > > > > > path='/var/run/ovirt-vmconsole-console/b4e805ff-556d-42bd-a6df-02f5902fd01c.sock'/> > > > > > path='/var/lib/libvirt/qemu/channels/b4e805ff-556d-42bd-a6df-02f5902fd01c.ovirt-guest-agent.0'/> > > > > > > path='/var/lib/libvirt/qemu/channels/b4e805ff-556d-42bd-a6df-02f5902fd01c.org.qemu.guest_agent.0'/> > > > > > > > > > > > path='/var/lib/libvirt/qemu/channels/b4e805ff-556d-42bd-a6df-02f5902fd01c.org.ovirt.hosted-engine-setup.0'/> > state='disconnected'/> > > > > > > > > > > > > > > keymap='en-us' passwdValidTo='1970-01-01T00:00:01'> > > > listen='192.168.1.22' passwdValidTo='1970-01-01T00:00:01'> > > > > > > > > > > > > > function='0x0'/> > > > primary='yes'/> > > function='0x0'/> > > > > > function='0x0'/> >
[ovirt-users] Re: in ovirt-engine all host show the status at "non-responsive"
is it any other cert i also need to renew?? please help me, i am very green on the ovirt, and all the ovirt environment is build up by the predecessor ___ 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/QXD4EXJW546KTIAPBDP7YASOOVMSFZOW/
[ovirt-users] in ovirt-engine all host show the status at "non-responsive"
hello everyone, I apologize for asking what is probably a very basic question. i have 4 hosts running on the ovirt-engine, but on the last week the alert show all the hosts status has gone to non responsive like the following statement Host 1 became non responsive. It has no power management configured. Please check the host status, manually reboot it, and click "Confirm Host Has Been Rebooted" all the storage, vm, cannot detect on the ovirt-engine, does anyone face this before? and also the alert also show ""Engine's certification has expired at 2020-08-18. Please renew the engine's certification"" is it related to the hosts become non-responsive??? i have already regenerate the ovirt-engine cert from the previous post: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/ZI5WNU6OB6FZMQNWAG5E4J2VGNDWMABZ/ Yours Sincerely, school it ___ 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/MG6TV6JUZ5PSD65BXS74X7N6USLHNZHU/
[ovirt-users] Re: i cannot access to ovirt-engine with this error"sun.security.validator.validatorexception: pkix path validation failed: java.security.cert.certpathvalidatorexception: timestamp check
thanks for your suggestion, i was solve the problem by the following steps
# cp -a /etc/pki/ovirt-engine "/etc/pki/ovirt-engine.$(date "+%Y%m%d")"
# SUBJECT="$(openssl x509 -subject -noout -in
/etc/pki/ovirt-engine/certs/apache.cer | sed 's/subject= //')"
# /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh --name=apache
--password="@PASSWORD@" --subject="${SUBJECT}"
# openssl pkcs12 -passin "pass:@PASSWORD@" -nokeys -in
/etc/pki/ovirt-engine/keys/apache.p12 > /etc/pki/ovirt-engine/certs/apache.cer
# openssl pkcs12 -passin "pass:@PASSWORD@" -nocerts -nodes -in
/etc/pki/ovirt-engine/keys/apache.p12 >
/etc/pki/ovirt-engine/keys/apache.key.nopass
# chmod 0600 /etc/pki/ovirt-engine/keys/apache.key.nopass
https://lists.ovirt.org/pipermail/users/2014-April/023402.html
i hope can help anyone who face the same problem.
___
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/Z6EMMINNC5ZI2Z6W5C6KAP2GJO2YTK3L/
[ovirt-users] Re: VM stuck in "reboot in progress" ("virtual machine XXX should be running in a host but it isn't.").
Ah , host is treated as operational (Active)... I guess you can check the status of the VM in the engine , but keep in mind that direct manipulation of the DB is highly not recommended (but desperate people require desperate measures). Usually I ssh to the HE as root: ssh root@HE su - postgres source /opt/rh/rh-postgresql10/enable psql engine List the tables: \dt Then you have to search where the status of the VM is. Best Regards, Strahil Nikolov В неделя, 20 септември 2020 г., 11:59:53 Гринуич+3, Gilboa Davara написа: On Sat, Sep 19, 2020 at 5:07 PM Strahil Nikolov wrote:> > You have rebooted the host where the VM was previously running , right ? > If oVirt doesn't detect that the host was rebooted , you can mark it as such : > UI -> Hosts -> select the Host -> the 3 dots -> "Confirm 'Host has been > rebooted'" > > Best Regards, > Strahil Nikolov > "Confirm host was rebooted" fails when host is up. The error message is: '"Error while executing action: Cannot confirm 'Host has been rebooted' Host. Valid Host statuses are "Non operational", "Maintenance" or "Connecting"'. - Gilboa ___ 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/6NUVSN3UFBRWWPTPRTEMLOYD2FZ4/ ___ 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/DP3WYZO5CTRPL52GTUMO4E42U67BIKSE/
[ovirt-users] Re: VM stuck in "reboot in progress" ("virtual machine XXX should be running in a host but it isn't.").
On Sat, Sep 19, 2020 at 5:07 PM Strahil Nikolov wrote:> > You have rebooted the host where the VM was previously running , right ? > If oVirt doesn't detect that the host was rebooted , you can mark it as such : > UI -> Hosts -> select the Host -> the 3 dots -> "Confirm 'Host has been > rebooted'" > > Best Regards, > Strahil Nikolov > "Confirm host was rebooted" fails when host is up. The error message is: '"Error while executing action: Cannot confirm 'Host has been rebooted' Host. Valid Host statuses are "Non operational", "Maintenance" or "Connecting"'. - Gilboa ___ 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/6NUVSN3UFBRWWPTPRTEMLOYD2FZ4/
[ovirt-users] Re: VM stuck in "reboot in progress" ("virtual machine XXX should be running in a host but it isn't.").
On Sat, Sep 19, 2020 at 7:44 PM Arik Hadas wrote: > > > > On Fri, Sep 18, 2020 at 8:27 AM Gilboa Davara wrote: >> >> Hello all (and happy new year), >> >> (Note: Also reported as https://bugzilla.redhat.com/show_bug.cgi?id=1880251) >> >> Self hosted engine, single node, NFS. >> Attempted to install CentOS over an existing Fedora VM with one host >> device (USB printer). >> Reboot failed, trying to boot from a non-existent CDROM. >> Tried shutting the VM down, failed. >> Tried powering off the VM, failed. >> Dropped cluster to global maintenance, reboot host + engine (was >> planning to upgrade it anyhow...), VM still stuck. >> >> When trying to power off the VM, the following message can be found >> the in engine.log: >> 2020-09-18 07:58:51,439+03 INFO >> [org.ovirt.engine.core.bll.StopVmCommand] >> (EE-ManagedThreadFactory-engine-Thread-42) >> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] Running command: StopVmCommand >> internal: false. Entities affected : ID: >> b411e573-bcda-4689-b61f-1811c6f03ad5 Type: VMAction group STOP_VM with >> role type USER >> 2020-09-18 07:58:51,441+03 WARN >> [org.ovirt.engine.core.bll.StopVmCommand] >> (EE-ManagedThreadFactory-engine-Thread-42) >> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] Strange, according to the >> status 'RebootInProgress' virtual machine >> 'b411e573-bcda-4689-b61f-1811c6f03ad5' should be running in a host but >> it isn't. >> 2020-09-18 07:58:51,594+03 ERROR >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] >> (EE-ManagedThreadFactory-engine-Thread-42) >> [7bc4ac71-f0b2-4af7-b081-100dc99b6123] EVENT_ID: >> USER_FAILED_STOP_VM(56), Failed to power off VM kids-home-srv (Host: >> , User: gilboa@internal-authz). >> >> My question is simple: Pending a solution to the bug, can I somehow >> drop the state of the VM? It's currently holding a sizable disk image >> and a USB device I need (printer). > > > It would be best to modify the VM as if it should still be running on the > host and let the system discover that it's not running there and update the > VM accordingly. > > You can do it by changing the database with: > update vm_dynamic set run_on_vds='82f92946-9130-4dbd-8663-1ac0b50668a1' where > vm_guid='b411e573-bcda-4689-b61f-1811c6f03ad5'; > > >> >> >> As it's my private VM cluster, I have no problem dropping the site >> completely for maintenance. >> >> Thanks, >> >> Gilboa Hello, Thanks for the prompt answer. Edward, Full reboot of both engine and host didn't help. Most likely there's a consistency problem in the oVirt DB. Arik, To which DB I should connect and as which user? E.g. psql -U user db_name Thanks again, - Gilboa ___ 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/XUFMFHGE5U4ICTBMSBN4TRW74KRGDIIS/
