[ovirt-users] Re: oVirt 4.3.7 + Gluster 6.6 unsynced entries
Not sure if this is what is needed, as I still cant find the virtual directory .gfid. [root@host1 ~]# getfattr -n glusterfs.gfid.string /mnt/vmstore/ef503f3c-d57f-457d-a7a6-6a195082fbd6 getfattr: Removing leading '/' from absolute path names # file: mnt/vmstore/ef503f3c-d57f-457d-a7a6-6a195082fbd6 glusterfs.gfid.string="cf395203-bb5a-4ca2-9641-78457b502ba8" Thanks, Adrian On Sat, Apr 18, 2020 at 2:51 PM Strahil Nikolov wrote: > On April 18, 2020 5:58:03 PM GMT+03:00, Adrian Quintero < > adrianquint...@gmail.com> wrote: > >ok I did that however I still dont see ".gfid", thoughts? > > > >[root@host1]# mount -t glusterfs -o aux-gfid-mount > >192.168.0.59:/vmstore > >/mnt/vmstore > > > > > >[root@host1]# getfattr -n trusted.glusterfs.pathinfo -e text > >/mnt/vmstore/ef503f3c-d57f-457d-a7a6-6a195082fbd6/ > >getfattr: Removing leading '/' from absolute path names > > > ># file: mnt/vmstore/ef503f3c-d57f-457d-a7a6-6a195082fbd6/ > >trusted.glusterfs.pathinfo="( > > > > > > > > >)" > > > > > >Thanks, > > > > > > > > > > > >On Sat, Apr 18, 2020 at 10:44 AM Adrian Quintero > > > >wrote: > > > >> ah ok.. > >> want me to do it on any of the hosts? > >> > >> On Sat, Apr 18, 2020 at 10:34 AM Strahil Nikolov > > > >> wrote: > >> > >>> On April 18, 2020 4:46:35 PM GMT+03:00, Adrian Quintero < > >>> adrianquint...@gmail.com> wrote: > >>> >Hi Strahil, > >>> >Here are my findings > >>> > > >>> > > >>> >1.- mount -t glusterfs -o aux-gfid-mount host1:vmstore /mnt/vmstore > >>> > > >>> >[root@host3]# mount -t glusterfs -o aux-gfid-mount > >>> >192.168.0.59:/vmstore > >>> >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore > >>> >/sbin/mount.glusterfs: according to mtab, GlusterFS is already > >mounted > >>> >on > >>> >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore > >>> > > >>> >[root@host2]# mount -t glusterfs -o aux-gfid-mount > >>> >192.168.0.59:/vmstore > >>> >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore > >>> >/sbin/mount.glusterfs: according to mtab, GlusterFS is already > >mounted > >>> >on > >>> >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore > >>> > > >>> >[root@host1]# mount -t glusterfs -o aux-gfid-mount > >>> >192.168.0.59:/vmstore > >>> >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore > >>> >/sbin/mount.glusterfs: according to mtab, GlusterFS is already > >mounted > >>> >on > >>> >/rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore > >>> > > >>> > > >>> >2.-getfattr -n trusted.glusterfs.pathinfo -e text > >>> >/mnt/vmstore/.gfid/5aeb168c-b8e3-4581-97f9-eafc33f2f318 > >>> >I am not to sure about this one as I cant find ".gfid" anywhere. > >>> > > >>> >3.-umount /mnt/vmstore > >>> > I did not try this one yet. > >>> > > >>> >Question? the umount was tobe tested on host3 ? > >>> > > >>> >glusterfs 6.6 > >>> > > >>> >Thanks you, > >>> > > >>> >Adrian > >>> > > >>> > > >>> > > >>> >On Sat, Apr 18, 2020 at 3:53 AM Strahil Nikolov > > > >>> >wrote: > >>> > > >>> >> On April 16, 2020 9:27:11 PM GMT+03:00, adrianquint...@gmail.com > >>> >wrote: > >>> >> >Hi Strahil, > >>> >> >This is what method 2 came up with: > >>> >> > > >>> >> >[root@host1 ~]# getfattr -n trusted.glusterfs.pathinfo -e text > >>> >> >/rhev/data-center/mnt/glusterSD/192.168.0.59\:_vmstore/ > >>> >> >getfattr: Removing leading '/' from absolute path names > >>> >> ># file: rhev/data-center/mnt/glusterSD/192.168.0.59:_vmstore/ > >>> >> >trusted.glusterfs.pathinfo="( > >>> >> > >>> >> > >>> > >>> > > >>> > >>> >> > >>> >> > >>> > >>> > > >>> > >>> >> > >>> >> > >>> > >>> > > >>>)" > >>> >> > > >>> >> > > >>> >> >I will try method 1, but just want to make sure I am running it > >>> >against > >>> >> >the correct file directory. > >>> >> >___ > >>> >> >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/7377A4JQ54AYWBIVGJ6XJLG5THCGETH3/ > >>> >> > >>> >> Hey Adrian, > >>> >> > >>> >> Can you provide the output of the following: > >>> >> > >>> >> mount -t glusterfs -o aux-gfid-mount host1:vmstore /mnt/vmstore > >>> >> > >>> >> > >>> >> getfattr -n trusted.glusterfs.pathinfo -e text > >>> >> /mnt/vmstore/.gfid/5aeb168c-b8e3-4581-97f9-eafc33f2f318 > >>> >> > >>> >> umount /mnt/vmstore > >>> >> > >>> >> Best Regards, > >>> >> Strahil Nikolov > >>> >> > >>> >> > >>> > >>> You can't remount gluster ... > >>> Juat mount it on /mnt just like my example. Once you mount it with > >that > >>> option , the '.gfid' will be exposed to you. > >>> > >>> Best Regards, > >>> Strahil Nikolov > >>> > >> > >> > >> -- > >> Adrian Quintero > >> > > '.gfid' is a virtual folder. > > You can try to 'stat' the folder from the previous output and give
[ovirt-users] Re: command line vm start/stop
According to https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html-single/rest_api_guide/index#services-vm trying to use curl --insecure -v -u admin@internal:password -H Content-type: application/xml -X POST https://FQDN/ovirt-engine/api/vms/VM_NAME/ACTION where ACTION start or stop Got following: * About to connect() to FQDN port 443 (#0) * Trying SERVER_IP... * Connected to FQDN (SERVER_IP) port 443 (#0) * Initializing NSS with certpath: sql:/etc/pki/nssdb * CAfile: /etc/pki/ovirt-engine/ca.pem CApath: none * SSL connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 * Server certificate: * subject: CN=FQDN * start date: Jan 22 06:12:15 2020 GMT * expire date: Dec 27 06:12:15 2024 GMT * common name: FQDN * issuer: CN=FQDN. * Server auth using Basic with user 'admin@internal' > POST /ovirt-engine/api/vms/VM_NAME/ACTION HTTP/1.1 > Authorization: Basic YWRtaW5AaW50ZXJuYWw6U3lzVGVhbTEzYw== > User-Agent: curl/7.29.0 > Host: FQDN > Accept: application/xml > < HTTP/1.1 404 Not Found < Date: Sun, 19 Apr 2020 00:20:04 GMT < Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips < Content-Length: 0 < Correlation-Id: 15e7a226-8982-47ff-9f68-7a2519705856 < * Connection #0 to host FQDN left intact -- tail -1000f /var/log/ovirt-engine/server.log: 2020-04-18 20:20:04,354-04 ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-385) RESTEASY002010: Failed to execute: javax.ws.rs.WebApplicationException: HTTP 404 Not Found at org.ovirt.engine.api.restapi.resource.AbstractBackendResource.asGuidOr404(AbstractBackendResource.java:355) [restapi-jaxrs.jar:] at org.ovirt.engine.api.restapi.resource.AbstractBackendSubResource.(AbstractBackendSubResource.java:26) [restapi-jaxrs.jar:] at org.ovirt.engine.api.restapi.resource.AbstractBackendActionableResource.(AbstractBackendActionableResource.java:39) [restapi-jaxrs.jar:] at org.ovirt.engine.api.restapi.resource.BackendVmResource.(BackendVmResource.java:114) [restapi-jaxrs.jar:] at org.ovirt.engine.api.restapi.resource.BackendVmsResource.getVmResource(BackendVmsResource.java:164) [restapi-jaxrs.jar:] at sun.reflect.GeneratedMethodAccessor1357.invoke(Unknown Source) [:1.8.0_232] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_232] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_232] at org.jboss.resteasy.core.ResourceLocatorInvoker.createResource(ResourceLocatorInvoker.java:69) [resteasy-jaxrs-3.7.0.Final.jar:3.7.0.Final] at org.jboss.resteasy.core.ResourceLocatorInvoker.invoke(ResourceLocatorInvoker.java:105) [resteasy-jaxrs-3.7.0.Final.jar:3.7.0.Final] at org.jboss.resteasy.core.ResourceLocatorInvoker.invokeOnTargetObject(ResourceLocatorInvoker.java:132) [resteasy-jaxrs-3.7.0.Final.jar:3.7.0.Final] at org.jboss.resteasy.core.ResourceLocatorInvoker.invoke(ResourceLocatorInvoker.java:100) [resteasy-jaxrs-3.7.0.Final.jar:3.7.0.Final] at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:440) [resteasy-jaxrs-3.7.0.Final.jar:3.7.0.Final] at org.jboss.resteasy.core.SynchronousDispatcher.lambda$invoke$4(SynchronousDispatcher.java:229) [resteasy-jaxrs-3.7.0.Final.jar:3.7.0.Final] at org.jboss.resteasy.core.SynchronousDispatcher.lambda$preprocess$0(SynchronousDispatcher.java:135) [resteasy-jaxrs-3.7.0.Final.jar:3.7.0.Final] at org.jboss.resteasy.core.interception.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:355) [resteasy-jaxrs-3.7.0.Final.jar:3.7.0.Final] at org.jboss.resteasy.core.SynchronousDispatcher.preprocess(SynchronousDispatcher.java:138) [resteasy-jaxrs-3.7.0.Final.jar:3.7.0.Final] at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:215) [resteasy-jaxrs-3.7.0.Final.jar:3.7.0.Final] at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:227) [resteasy-jaxrs-3.7.0.Final.jar:3.7.0.Final] at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.7.0.Final.jar:3.7.0.Final] at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.7.0.Final.jar:3.7.0.Final] at javax.servlet.http.HttpServlet.service(HttpServlet.java:791) [jboss-servlet-api_4.0_spec-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74) [undertow-servlet-2.0.21.Final.jar:2.0.21.Final] at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:81) [undertow-servlet-2.0.21.Final.jar:2.0.21.Final] at
[ovirt-users] ovirt 4.4 beta4 HCI single host problem unknown CPU feature: tsx-ctrl
Hello,
I'm trying what in subject as a nested environment.
Physical is oVirt 4.3.9
I configured the VM that has to be the hypervisor with cpu passthrough.
The local VM starts ok with these settings:
usr/libexec/qemu-kvm -name guest=HostedEngineLocal,debug-threads=on -S
-object
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-HostedEngineLocal/master-key.aes
-machine pc-q35-rhel8.1.0,accel=kvm,usb=off,dump-guest-core=off -cpu
Cascadelake-Server,ss=on,hypervisor=on,tsc-adjust=on,umip=on,pku=on,md-clear=on,stibp=on,arch-capabilities=on,ibpb=on,rdctl-no=on,ibrs-all=on,skip-l1dfl-vmentry=on,mds-no=on,kvmclock=on
When at final stage of deployment it tries to start the final engine VM it
goes down due to this in vdsm.log:
2020-04-19 15:09:48,962+0200 ERROR (vm/22082519) [virt.vm]
(vmId='22082519-70bb-476f-a373-45c2d402a870') The vm start process failed
(vm:871)
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 801, in
_startUnderlyingVm
self._run()
File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 2608, in
_run
dom.createWithFlags(flags)
File "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py",
line 131, in wrapper
ret = f(*args, **kwargs)
File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line 94,
in wrapper
return func(inst, *args, **kwargs)
File "/usr/lib64/python3.6/site-packages/libvirt.py", line 1166, in
createWithFlags
if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed',
dom=self)
libvirt.libvirtError: unsupported configuration: unknown CPU feature:
tsx-ctrl
2020-04-19 15:09:48,962+0200 INFO (vm/22082519) [virt.vm]
(vmId='22082519-70bb-476f-a373-45c2d402a870') Changed state to Down:
unsupported configuration: unknown CPU feature: tsx-ctrl (code=1) (vm:1629)
2020-04-19 15:09:48,965+0200 INFO (vm/22082519) [virt.vm]
(vmId='22082519-70bb-476f-a373-45c2d402a870') Stopping connection
(guestagent:441)
The xml it tries to activate is:
Cascadelake-Server
hvm
Similar nested env with 4.3.9 on the same physical hw completed ok and the
final engine VM had only:
-machine pc-i440fx-rhel7.6.0,accel=kvm,usb=off,dump-guest-core=off \
-cpu Skylake-Server,spec-ctrl=on,ssbd=on,md-clear=on \
The physical cpu is:
Model name:Intel(R) Xeon(R) Platinum 8260L CPU @ 2.40GHz
and between its flags I don't find tsx-ctrl:
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall
nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl
xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor
ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2
x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm
abm 3dnowprefetch epb cat_l3 cdp_l3 invpcid_single intel_pt ssbd mba ibrs
ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid fsgsbase
tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm mpx rdt_a avx512f
avx512dq rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl
xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local
dtherm ida arat pln pts hwp hwp_act_window hwp_epp hwp_pkg_req pku ospke
avx512_vnni md_clear spec_ctrl intel_stibp flush_l1d arch_capabilities
any help on how to proceed and test?
Thanks,
Gianluca
___
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/CR6XYIEYHT4N75UWEXMTJR2AKB3DYL6X/
[ovirt-users] ovrt node ng 4.4 different fs layout and error if changed
Hello,
In CentOS 7 default filesystem in anaconda was xfs, but in ovirt node ng
4.3.9 (based on CentOS 7) the default layout was set to ext4.
In CentOS 8 again the default is xfs and I see that ovirt node ng 4.4 beta4
(based on CentOS 8.1) has now xfs for all filesystems, excluded /boot that
is set to ext4.
In general I have a preference for ext4.
I notice that while in 4.3.9 I could somehow customize partition layout,
even if not recommended, in 4.4 I always get error if I don't accept
automatic partitioning.
What I sometimes do:
- select disk and custom layout
- click done and the storage page appears
- I click the button to create automatically and I get the automatic
partitioning layout
- and here I can change fs type and update settings button and/or change
size of some filesystems (eg for /var/log if using Gluster)
Even if I only set all filesystems automatically generated by installer to
ext4, without changing any size, in the final stage of installation I get
this error and installation aborts:
"
There was an error running the kickstart script at line 5. This is a fatal
error and installation will be aborted. The details of this error are:
2020-04-19 10:37:50,451 [INFO] (MainThread) Trying to create a manageable
base from '/'
2020-04-19 10:37:50,811 [ERROR] (MainThread) LVM Thin Provisioning
partitioning scheme is required.
For autoinstall via Kickstart with LVM Thin Provisioning check options:
--thinpool and --grow. Please consult documentation for details
Traceback (most recent call last):
File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/usr/lib/python3.6/site-packages/imgbased/__main__.py", line 53, in
CliApplication()
File "/usr/lib/python3.6/site-packages/imgbased/__init__.py", line 82, in
CliApplication
app.hooks.emit("post-arg-parse", args)
File "/usr/lib/python3.6/site-packages/imgbased/hooks.py", line 120, in
emit
cb(self.context, *args)
File "/usr/lib/python3.6/site-packages/imgbased/plugins/core.py", line
171, in post_argparse
layout.initialize(args.source, args.init_nvr)
File "/usr/lib/python3.6/site-packages/imgbased/plugins/core.py", line
215, in initialize
self.app.imgbase.init_layout_from(source, init_nvr)
File "/usr/lib/python3.6/site-packages/imgbased/imgbase.py", line 293, in
init_layout_from
self.init_tags_on(existing_lv)
File "/usr/lib/python3.6/site-packages/imgbased/imgbase.py", line 271, in
init_tags_on
pool = lv.thinpool()
File "/usr/lib/python3.6/site-packages/imgbased/lvm.py", line 305, in
thinpool
raise MissingLvmThinPool()
imgbased.lvm.MissingLvmThinPool
"
If I change nothing and choose automatic partitioning the installation
completes.
Tried different times with same results.
Is it expected? In this case instead of specifying "recommended" it should
be written sort of "mandatory"...
Gianluca
___
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/F5PD5LSQB5WNZCF2J7TDG3OKQL74WSXW/
[ovirt-users] Re: disk snapshot in illegal status
The f447cd4f-9ab3-489d-8c2a-b2e69456496f - "Auto-generated" snapshot should
be deleted.
After that, make sure the 5a58466b-1547-4346-a550-8590880b379e (Active VM)
snapshot has an active=true flag.
*Regards,*
*Shani Leviim*
On Thu, Apr 16, 2020 at 9:33 PM David David wrote:
> snapshots in UI:
>
> Disk Snapshot ID
> =
> 5a58466b-1547-4346-a550-8590880b379e - "Active VM" - has status "OK"
> f447cd4f-9ab3-489d-8c2a-b2e69456496f - "Auto-generated" - has status
> "Illegal"
> ==
> the "Disk Snapshot ID" with id 5a58466b-1547-4346-a550-8590880b379e
> actually not present in LV
>
> error screenshot attached
>
> чт, 16 апр. 2020 г. в 18:20, Shani Leviim :
>
>> Hi David,
>> Can you share a screenshot of the error you're getting?
>> And how the snapshots are presented on the ui?
>>
>>
>> *Regards,*
>>
>> *Shani Leviim*
>>
>>
>> On Thu, Apr 16, 2020 at 4:38 PM David David wrote:
>>
>>> hi
>>>
>>> attempt to remove snapshot from UI results in an error
>>>
>>> I looked the LV through the lvs and did't find active snapshot ID, only
>>> the base snapshot ID is present
>>>
>>> ovirt in database see 2 snapshots, but i have only one base image on
>>> storage
>>>
>>> so, i must remove the active snapshot ID from db not the base image Id ?
>>>
>>> чт, 16 апр. 2020 г. в 13:58, Shani Leviim :
>>>
Hi David,
Sorry for the late reply.
the volume_dump returned 1 occurrence of that image, while the query
returned 2 occurrences.
It seems that there's an image id with a description of 'Auto-generated
for Live Storage Migration' which wasn't removed from the DB.
Can you try to remove it from the UI?
(If you claimed to remove it, try to remove it from the DB).
*Regards,*
*Shani Leviim*
On Tue, Apr 7, 2020 at 7:45 PM David David wrote:
> vdsm-tool dump-volume-chains d17aa967-f7f7-4d9f-98e4-7022854da4f5
>
> engine=# select * from images_storage_domain_view where
> image_group_id='1844873e-45ef-4a2b-a991-2df6e92a3e2d';
>
> output attached
>
> вт, 7 апр. 2020 г. в 19:47, Shani Leviim :
>
>> Hi David,
>> First, we need to compare the chain as it is seen by the engine and
>> the host and see if there's a difference.
>> Can you please share the output of the following?
>>
>> On the host:
>> vdsm-tool dump-volume-chains
>>
>> On the engine:
>> SELECT *
>> FROM images_storage_domain_view images_storage_domain_view
>> WHERE image_group_id = ;
>>
>>
>> *Regards,*
>>
>> *Shani Leviim*
>>
>>
>> On Tue, Apr 7, 2020 at 5:28 PM David David
>> wrote:
>>
>>> hello
>>>
>>> after removing "auto generated" snapshot, the vm snapshot became to
>>> illegal status and in the "snapshot" tab also marked in illegal status
>>>
>>> now my vm is not booting
>>>
>>> but "vdsm-client Volume getInfo" shows the snapshot status is legal
>>>
>>> vdsm-client Volume getInfo \
>>> storagepoolID=---- \
>>> storagedomainID=d17aa967-f7f7-4d9f-98e4-7022854da4f5 \
>>> imageID=1844873e-45ef-4a2b-a991-2df6e92a3e2d \
>>> volumeID=f447cd4f-9ab3-489d-8c2a-b2e69456496f
>>>
>>> {
>>> "status": "OK",
>>> "lease": {
>>> "path": "/dev/d17aa967-f7f7-4d9f-98e4-7022854da4f5/leases",
>>> "owners": [],
>>> "version": null,
>>> "offset": 132120576
>>> },
>>> "domain": "d17aa967-f7f7-4d9f-98e4-7022854da4f5",
>>> "capacity": "21474836480",
>>> "voltype": "LEAF",
>>> "description": "None",
>>> "parent": "----",
>>> "format": "RAW",
>>> "generation": 1,
>>> "image": "1844873e-45ef-4a2b-a991-2df6e92a3e2d",
>>> "uuid": "f447cd4f-9ab3-489d-8c2a-b2e69456496f",
>>> "disktype": "DATA",
>>> "legality": "LEGAL",
>>> "mtime": "0",
>>> "apparentsize": "21474836480",
>>> "truesize": "21474836480",
>>> "type": "PREALLOCATED",
>>> "children": [],
>>> "pool": "",
>>> "ctime": "1530472945"
>>> }
>>>
>>> how to fix the 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/JSYMY4QG2HSPVITAX7QSVZDZ4HJDLN4W/
>>>
>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
[ovirt-users] Re: VM's in status unknown
I would start by querying the database with:
select vm_name, status, run_on_vds from vms where vm_name in ('', '');
Their status should be '7' in that case.
The more interesting part though is their 'run_on_vds' field -
If it's non-empty and points to the host the VMs ran on, it probably means
there's an issue in the communication between the engine and that host, so
restarting the engine/vdsm can solve it.
Otherwise, it would require a deeper look at the log to see why the engine
lost track of the host they run on.
On Fri, Apr 17, 2020 at 12:12 PM Staniforth, Paul <
p.stanifo...@leedsbeckett.ac.uk> wrote:
> I don't think the status is reported via the agent but vdsm on the host.
>
> Try restarting the engine service.
>
> use vdsm-client on the host to see if the VM running and shut it down if
> needed.
>
> https://www.ovirt.org/develop/developer-guide/vdsm/vdsm-client.html
>
> on the host restart vdsmd ( you may want to migrate other VMs first)
>
> systemctl restart vdsmd
>
> If this doesn't work alter the database
>
> Regards,
> Paul S.
>
> --
> *From:* Jayme
> *Sent:* 16 April 2020 19:07
> *To:* eev...@digitaldatatechs.com
> *Cc:* kim.karga...@noroff.no ; users <
> users@ovirt.org>
> *Subject:* [ovirt-users] Re: VM's in status unknown
>
>
> *Caution External Mail:* Do not click any links or open any attachments
> unless you trust the sender and know that the content is safe.
> Do you have the guest agent installed on the VMs?
>
> On Thu, Apr 16, 2020 at 2:55 PM wrote:
>
> Are you getting any errors in the engine log or
> /var/log/libvirt/qemu/.log?
> I have Windows 10 and haven't experienced that. You can't shut it down in
> the UI? Even after you try to shut it down inside Windows?
> I will assume you have the latest guest tools installed.
>
> Eric Evans
> Digital Data Services LLC.
> 304.660.9080
>
>
> -Original Message-
> From: kim.karga...@noroff.no
> Sent: Thursday, April 16, 2020 8:23 AM
> To: users@ovirt.org
> Subject: [ovirt-users] VM's in status unknown
>
> Hi,
>
> We have a few Windows 10 VM's running on our ovirt 4.3, where when you
> shutdown the VM from within Windows, that VM does not shut down but gets a
> status of unknown in ovirt and one cannot do anything to the machines
> within the web gui. This seems to specfically be related to that Windows 10
> template that we have created. Any ideas? Also, any ideas on how one can
> shut these machines down?
>
> Thanks
>
> Kim
> ___
> 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/UM26TABUTG373QVXEI4UJN3EAKANLWHL/
>
> ___
> 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/M4LITHLIZXJDTZACENZX4NLO7LSB6VAM/
>
