Re: Cannot inquire Lease
by Strahil
Hm ... Removing it from the gluster but not inside oVirt can cause a lot of headaches.
Can you find that image in oVirt Storage -> Disks
Sadly , you got no other option and the optimal approach would be to take the deletion from oVirt UI/API before the storage gets full.
Ovirt has the option to notify you in advance.
Best Regards,
Strahil NikolovOn Jun 27, 2019 01:25, suporte(a)logicworks.pt wrote:
>
> I just empty a big image here
> /rhev/data-center/mnt/glusterSD/node2.abc.pt:_data/0a19a375-77cb-47e5-af12-7b5451e6fa53/images
>
> > dff87321-a18e-45a1-a4de-fb528403ebeb
>
> and everything looks like it's working again.
>
> ________________________________
> De: suporte(a)logicworks.pt
> Para: "users" <users(a)ovirt.org>
> Enviadas: Quarta-feira, 26 De Junho de 2019 22:20:13
> Assunto: [ovirt-users] Cannot inquire Lease
>
> Hi,
>
> The glusterfs domain disk data master is full and the volume is down.
> I have this error:
> VDSM NODE2 command SpmStatusVDS failed: Cannot inquire Lease(name='SDM', path=u'/rhev/data-center/mnt/glusterSD/node2.abc.pt:_data/0a19a375-77cb-47e5-af12-7b5451e6fa53/dom_md/leases', offset=1048576): (2, 'Sanlock get hosts failure', 'No such file or directory')
>
> Cannot delete de domain because is the data master.
> Version 4.3.4.3-1.el7
>
> What can I do?
>
>
> Thanks
>
> José
>
> --
> ________________________________
> Jose Ferradeira
> http://www.logicworks.pt
>
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)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/DHZ3BQ77SK3...
7 months
RDO integration with oVirt
by Strahil
Hey guys,
I know that RHV has a nice integration with Red Hat's openstack , but I was wondering if RDO - oVirt are having that integration.
I've read a nice post : http://www.chrisj.cloud/?q=node/8
and I was wondering if I can do it - as I'm thinking about learning openstack.
Bewt Regards,
Strahil Nikolov
7 months
VM IPsec network performance
by TranceWorldLogic .
Hi,
I have enable multi-queue feature on nic card and I am getting normal
throughput as 26 Gbps.
But when I am trying throughput test with IPsec I am getting only max
1.5Gbps. After looking at CPU usages, it is free more than 50%, I am not
getting why low throughput in ipsec case.
Below are my trial:
2nd, I tried to distribute multi-queue interrupt on mult-cpu but got same
result.
3rd, I tried nic passthrough and enable RSS, I got good throughput and CPU
usages.
Please help me to understand how to increase vnet performance for VM. And
also suggest me about ovirt setting.
I have also seen some presentation in google around virtio-crypto but as I
am using Guest and Host OS as centos 7.3, I can't use virtio-crypto device.
Thanks,
~Rohit
7 months
Re: Error virNetTLSContextLoadCertFromFile after upgrade from oVirt 4.2 to 4.3.4
by Strahil
What about setting the date and time manually somewhere at 2016 on all hosts and blockking ntp at all ?
Then the certs will be still valid and can be renewed ?
Just asking... Not sure what will be the outcome.
Best Regards,
Strahil NikolovOn Jun 25, 2019 12:31, Yedidyah Bar David <didi(a)redhat.com> wrote:
>
> On Tue, Jun 25, 2019 at 12:28 PM Stefano Danzi <s.danzi(a)hawai.it> wrote:
> >
> >
> >
> > Il 25/06/2019 10:08, Yedidyah Bar David ha scritto:
> > > On Tue, Jun 25, 2019 at 10:26 AM Stefano Danzi <s.danzi(a)hawai.it> wrote:
> > >>
> > >>
> > >> Il 25/06/2019 08:27, Yedidyah Bar David ha scritto:
> > >>> On Mon, Jun 24, 2019 at 7:56 PM Stefano Danzi <s.danzi(a)hawai.it> wrote:
> > >>>> I've found that this issue is related to:
> > >>>>
> > >>>> https://bugzilla.redhat.com/show_bug.cgi?id=1648190
> > >>> Are you sure?
> > >>>
> > >>> That bug is about an old cert, generated by an old version, likely
> > >>> before we fixed bug 1210486 (even though it's not mentioned in above
> > >>> bug).
> > >> Yes! Malformed "Not Before" date/time in certs
> > >>
> > >>>> But i've no idea how fix it....
> > >>>>
> > >>>> Il 24/06/2019 18:19, Stefano Danzi ha scritto:
> > >>>>> I've just upgraded my test environment from ovirt 4.2 to 4.3.4.
> > >>> Was it installed as 4.2, or upgraded? From which first version?
> > >> I don't remember the first installed version. Maybe 4.0... I always
> > >> upgraded the original installation.
> > >>
> > >>>>> System has only one host (Centos 7.6.1810) and run a self hosted engine.
> > >>>>>
> > >>>>> After upgrade I'm not able to run vdsmd (and so hosted engine....)
> > >>>>>
> > >>>>> Above the error in log:
> > >>>>>
> > >>>>> journalctl -xe
> > >>>>>
> > >>>>> -- L'unità libvirtd.service ha iniziato la fase di avvio.
> > >>>>> giu 24 18:09:17 ovirt01.hawai.lan libvirtd[8176]: 2019-06-24
> > >>>>> 16:09:17.006+0000: 8176: info : libvirt version: 4.5.0, package:
> > >>>>> 10.el7_6.12 (CentOS BuildSystem <http://bugs.centos.org>,
> > >>>>> 2019-06-20-15:01:15, x86-01.bsys.
> > >>>>> giu 24 18:09:17 ovirt01.hawai.lan libvirtd[8176]: 2019-06-24
> > >>>>> 16:09:17.006+0000: 8176: info : hostname: ovirt01.hawai.lan
> > >>>>> giu 24 18:09:17 ovirt01.hawai.lan libvirtd[8176]: 2019-06-24
> > >>>>> 16:09:17.006+0000: 8176: error : virNetTLSContextLoadCertFromFile:513
> > >>>>> : Unable to import server certificate /etc/pki/vdsm/certs/vdsmcert.pem
> > >>> Did you check this file? Does it exist?
> > >>>
> > >>> ls -l /etc/pki/vdsm/certs/vdsmcert.pem
> > >>>
> > >>> Can vdsm user read it?
> > >>>
> > >>> su - vdsm -s /bin/bash -c 'cat /etc/pki/vdsm/certs/vdsmcert.pem > /dev/null'
> > >>>
> > >>> Please check/share output of:
> > >>>
> > >>> openssl x509 -in /etc/pki/vdsm/certs/vdsmcert.pem -text
> > >>>
> > >>> Thanks and best regards,
> > >> vdsm can read vdsmcert. The problem is "Not Before" date:
> > >>
> > >> [root@ovirt01 ~]# su - vdsm -s /bin/bash -c 'openssl x509 -in
> > >> /etc/pki/vdsm/certs/vdsmcert.pem -text'
> > >> Certificate:
> > >> Data:
> > >> Version: 3 (0x2)
> > >> Serial Number: 4102 (0x1006)
> > >> Signature Algorithm: sha1WithRSAEncryption
> > >> Issuer: C=US, O=hawai.lan, CN=ovirtbk-sheng.hawai.lan.63272
> > >> Validity
> > >> Not Before: Feb 4 08:36:07 2015
> > >> Not After : Feb 4 08:36:07 2020 GMT
> > >> [CUT]
> > >>
> > >>
> > >> [root@ovirt01 ~]# su - vdsm -s /bin/bash -c 'openssl x509 -in
> > >> /etc/pki/vdsm/certs/cacert.pem -text'
> > >> Certificate:
> > >> Data:
> > >> Version: 3 (0x2)
> > >> Serial Number: 4096 (0x1000)
> > >> Signature Algorithm: sha1WithRSAEncryption
> > >> Issuer: C=US, O=hawai.lan, CN=ovirtbk-sheng.hawai.lan.63272
> > >> Validity
> > >> Not Before: Feb 4 00:06:25 2015
> > >> Not After : Feb 2 00:06:25 2025 GMT
> > >>
> > > OK :-(
> > >
> > > So it will be rather difficult to fix.
> > >
> > > You should have been prompted by engine-setup long ago to renew PKI,
> > > weren't you? And when you did, didn't you have to reinstall (or Re-
> > > Enroll Certificates, in later versions) all hosts?
> >
> > I don't remember to ever seen a question about this during engine-setup,
> > but it could be.
> > In /etc/pki/vdsm/certs/ I can see an old cert and ca with subjet:
> >
> > [root@ovirt01 ~]# su - vdsm -s /bin/bash -c 'openssl x509 -in
> > /etc/pki/vdsm/certs/cacert.pem.20150205093608 -text'
> > Certificate:
> > Data:
> > Version: 3 (0x2)
> > Serial Number: 1423056193 (0x54d21d41)
> > Signature Algorithm: sha256WithRSAEncryption
> > Issuer: CN=VDSM Certificate Authority
> > Validity
> > Not Before: Feb 4 13:23:13 2015 GMT
> > Not After : Feb 4 13:23:13 2016 GMT
> > Subject: CN=VDSM Certificate Authority
> > Subject Public Key Info:
> >
> > [CUT]
> >
> > [root@ovirt01 ~]# su - vdsm -s /bin/bash -c 'openssl x509 -in
> > /etc/pki/vdsm/certs/vdsmcert.pem.20150205093609 -text'
> > Certificate:
> > Data:
> > Version: 3 (0x2)
> > Serial Number: 1423056193 (0x54d21d41)
> > Signature Algorithm: sha256WithRSAEncryption
> > Issuer: CN=VDSM Certificate Authority
> > Validity
> > Not Before: Feb 4 13:23:13 2015 GMT
> > Not After : Feb 4 13:23:13 2016 GMT
> > Subject: CN=ovirt01.hawai.lan, O=VDSM Certificate
> > Subject Public Key Info:
> > Public Key Algorithm: rsaEncryption
> >
> >
> > I think that was certs made during first hosted engine installation.
> > Could it work if I manually create certs like this?
> > Just to start libvirtd, vdsm and hosted-engine.
>
> I think it's worth a try. Just create a self-signed CA, a keypair
> signed by it, and place them correctly, should work.
>
> The engine won't be able to talk with the host, but you can then more
> easily reinstall/re-enroll-certs.
>
> Good luck,
> --
> Didi
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)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/LBD33ESAF53...
7 months
Re: [ANN] oVirt 4.3.5 Third Release Candidate is now available for testing
by Strahil
Hi Sandro,
Thanks for the info.
I've just updated my lab (gluster v6.1 -> 6.3 ) and the only issue I have detected so far is that the Advanced Options in UI show no info for the replica bricks, while the arbiter is working.
So the situation is the same as before the upgrade.
Best Regards,
Strahil NikolovOn Jun 26, 2019 17:45, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote:
>
> The oVirt Project is pleased to announce the availability of the oVirt 4.3.5 Third Release Candidate for testing, as of June 26th, 2019.
>
> While testing this release candidate please consider deeper testing on gluster upgrade since with this release we are switching from Gluster 5 to Gluster 6.
>
> This update is a release candidate of the fifth in a series of stabilization updates to the 4.3 series.
> This is pre-release software. This pre-release should not to be used in production.
>
> This release is available now on x86_64 architecture for:
> * Red Hat Enterprise Linux 7.6 or later
> * CentOS Linux (or similar) 7.6 or later
>
> This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for:
> * Red Hat Enterprise Linux 7.6 or later
> * CentOS Linux (or similar) 7.6 or later
> * oVirt Node 4.3 (available for x86_64 only)
>
> See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed.
>
> Notes:
> - oVirt Appliance has not been updated due to a regression in the tooling we use for building it.[3]
> - oVirt Node is already available[2]
>
> Additional Resources:
> * Read more about the oVirt 4.3.5 release highlights:http://www.ovirt.org/release/4.3.5/
> * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
> * Check out the latest project news on the oVirt blog:http://www.ovirt.org/blog/
>
> [1] http://www.ovirt.org/release/4.3.5/
> [2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/
> [3] https://bugzilla.redhat.com/show_bug.cgi?id=1724076
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>
> Red Hat EMEA
>
> sbonazzo(a)redhat.com
7 months
Cannot inquire Lease
by suporte＠logicworks.pt
Hi,
The glusterfs domain disk data master is full and the volume is down.
I have this error:
VDSM NODE2 command SpmStatusVDS failed: Cannot inquire Lease(name='SDM', path=u'/rhev/data-center/mnt/glusterSD/node2.abc.pt:_data/0a19a375-77cb-47e5-af12-7b5451e6fa53/dom_md/leases', offset=1048576): (2, 'Sanlock get hosts failure', 'No such file or directory')
Cannot delete de domain because is the data master.
Version 4.3.4.3-1.el7
What can I do?
Thanks
José
--
Jose Ferradeira
http://www.logicworks.pt
7 months
Re: Issues when Creating a Gluster Brick with Cache
by Strahil
The cache will not take immediately into effect. It is designed to save your cache disk and to load only repetitive data.
Try to run your benchmark 20 times and you will notice slight improvement over reading the same object.
Of course , you can use lvm cache in writethrough mode, but then it is recommended to use 2 cache disks (raid1 or lvm mirroring) .
Best Regards,
Strahil NikolovOn Jun 26, 2019 17:44, Robert Crawford <robert.crawford4.14.10(a)gmail.com> wrote:
>
> So i created the brick without the cache an add the cache doing the commands below; but it appers it's not working because I see no improvement in the benchmarks.
>
> pvcreate /dev/md/VMStorageHot
> vgextend RHGS_vg_VMStorage /dev/md/VMStorageHot
> lvcreate -L 1500G -n lv_cache RHGS_vg_VMStorage /dev/md/VMStorageHot
> lvcreate -L 100M -n lv_cache_meta RHGS_vg_VMStorage /dev/md/VMStorageHot
> lvconvert --type cache-pool --cachemode writeback --poolmetadata RHGS_vg_VMStorage/lv_cache_meta RHGS_vg_VMStorage/lv_cache
> lvconvert --type cache --cachepool HGS_vg_VMStorage/lv_cache RHGS_vg_VMStorage/VMStorage_lv_pool
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)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/BQ4ZS245WZD...
7 months
vm unresponsive cpu soft lock on heavy operation
by Jayme
Basic setup notes: 3 node HCI running oVirt 4.3.3 using nodeNG for hosts.
Storage is SSD backed with 10Gb network dedicated to gluster with jumbo
frames enabled.
The ovirt management network (which also acts as VM network) is 1Gb network
Hosts are dell R720s w/ 256gb ram and E5-2690 procs
I have a VM configured with 16Gb ram and 6 virtual CPUs. When this VM does
a heavy operation (in this case it's dumping a large DB from a remote
server) the load spikes quickly. When this happens the VM becomes
unresponsive and in some cases I get cpu soft lock messages.
I'm trying to determine where the bottleneck here is and how I can prevent
the VM from becoming unresponsive when doing heavy tasks.
Here is info from syslog showing the soft lockup:
Jun 26 16:13:10 roble kernel: NMI watchdog: BUG: soft lockup - CPU#5 stuck
for 23s! [pg_dump:4025]
Jun 26 16:13:10 roble kernel: Modules linked in: binfmt_misc
rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache
sunrpc ppdev iosf_mbi crc32_pclmul ghash_clmulni_intel aesni_intel lrw
gf128mul glue_helper ablk_helper cryptd sg joydev parport_pc parport
virtio_rng i2c_piix4 pcspkr ip_tables xfs libcrc32c sd_mod crc_t10dif
crct10dif_generic sr_mod cdrom ata_generic virtio_console virtio_net
virtio_scsi pata_acpi crct10dif_pclmul crct10dif_common crc32c_intel qxl
drm_kms_helper syscopyarea sysfillrect sysimgblt serio_raw fb_sys_fops ttm
drm floppy ata_piix libata virtio_pci virtio_ring virtio
drm_panel_orientation_quirks dm_mirror dm_region_hash dm_log dm_mod
Jun 26 16:13:10 roble kernel: CPU: 5 PID: 4025 Comm: pg_dump Kdump: loaded
Not tainted 3.10.0-957.21.2.el7.x86_64 #1
Jun 26 16:13:10 roble kernel: Hardware name: oVirt oVirt Node, BIOS
1.11.0-2.el7 04/01/2014
Jun 26 16:13:10 roble kernel: task: ffffa01443499040 ti: ffffa014b24a4000
task.ti: ffffa014b24a4000
Jun 26 16:13:10 roble kernel: RIP: 0010:[<ffffffffaeb113ea>]
[<ffffffffaeb113ea>] generic_exec_single+0xfa/0x1b0
Jun 26 16:13:10 roble kernel: RSP: 0018:ffffa014b24a7c30 EFLAGS: 00000202
Jun 26 16:13:10 roble kernel: RAX: 0000000000000010 RBX: ffffa014b24a7c00
RCX: 0000000000000030
Jun 26 16:13:10 roble kernel: RDX: 000000000000ffff RSI: 0000000000000010
RDI: 0000000000000286
Jun 26 16:13:10 roble kernel: RBP: ffffa014b24a7c78 R08: ffffffffaf213640
R09: 000000018040003f
Jun 26 16:13:10 roble kernel: R10: 0000000000000001 R11: fffff83b8e91b540
R12: ffffa014b24a7bc0
Jun 26 16:13:10 roble kernel: R13: 0000000000000c9b R14: ffffa01477bf94e8
R15: ffffa01545074270
Jun 26 16:13:10 roble kernel: FS: 00007f9fefe89840(0000)
GS:ffffa0172f340000(0000) knlGS:0000000000000000
Jun 26 16:13:10 roble kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
Jun 26 16:13:10 roble kernel: CR2: 00007f9fef391e90 CR3: 000000014aa00000
CR4: 00000000000606e0
Jun 26 16:13:10 roble kernel: Call Trace:
Jun 26 16:13:10 roble kernel: [<ffffffffaea7a4e0>] ? leave_mm+0x110/0x110
Jun 26 16:13:10 roble kernel: [<ffffffffaea7a4e0>] ? leave_mm+0x110/0x110
Jun 26 16:13:10 roble kernel: [<ffffffffaea7a4e0>] ? leave_mm+0x110/0x110
Jun 26 16:13:10 roble kernel: [<ffffffffaeb114ff>]
smp_call_function_single+0x5f/0xa0
Jun 26 16:13:10 roble kernel: [<ffffffffaed75cd5>] ?
cpumask_next_and+0x35/0x50
Jun 26 16:13:10 roble kernel: [<ffffffffaeb11aab>]
smp_call_function_many+0x22b/0x270
Jun 26 16:13:10 roble kernel: [<ffffffffaea7a6a8>]
native_flush_tlb_others+0xb8/0xc0
Jun 26 16:13:10 roble kernel: [<ffffffffaea7a718>]
flush_tlb_mm_range+0x68/0x140
Jun 26 16:13:10 roble kernel: [<ffffffffaebe4687>]
tlb_flush_mmu.part.76+0x37/0xe0
Jun 26 16:13:10 roble kernel: [<ffffffffaebe5f85>] tlb_finish_mmu+0x55/0x60
Jun 26 16:13:10 roble kernel: [<ffffffffaebef624>] unmap_region+0xf4/0x140
Jun 26 16:13:10 roble kernel: [<ffffffffaecfc8d3>] ?
selinux_file_free_security+0x23/0x30
Jun 26 16:13:10 roble kernel: [<ffffffffaebefbe1>] ?
__vma_rb_erase+0x121/0x220
Jun 26 16:13:10 roble kernel: [<ffffffffaebf1c15>] do_munmap+0x2a5/0x480
Jun 26 16:13:10 roble kernel: [<ffffffffaebf1e55>] vm_munmap+0x65/0xb0
Jun 26 16:13:10 roble kernel: [<ffffffffaebf30e2>] SyS_munmap+0x22/0x30
Jun 26 16:13:10 roble kernel: [<ffffffffaf175ddb>]
system_call_fastpath+0x22/0x27
Jun 26 16:13:10 roble kernel: [<ffffffffaf175d21>] ?
system_call_after_swapgs+0xae/0x146
Jun 26 16:13:10 roble kernel: Code: 00 b7 01 00 48 89 de 48 03 14 c5 60 bc
74 af 48 89 df e8 4a b7 27 00 84 c0 75 46 45 85 ed 74 11 f6 43 20 01 74 0b
0f 1f 00 f3 90 <f6> 43 20 01 75 f8 31 c0 48 8b 7c 24 28 65 48 33 3c 25 28
00 00
Jun 26 16:13:14 roble kernel: NMI watchdog: BUG: soft lockup - CPU#4 stuck
for 27s! [kworker/4:3:16530]
Jun 26 16:13:14 roble kernel: Modules linked in: binfmt_misc
rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache
sunrpc ppdev iosf_mbi crc32_pclmul ghash_clmulni_intel aesni_intel lrw
gf128mul glue_helper ablk_helper cryptd sg joydev parport_pc parport
virtio_rng i2c_piix4 pcspkr ip_tables xfs libcrc32c sd_mod crc_t10dif
crct10dif_generic sr_mod cdrom ata_generic virtio_console virtio_net
virtio_scsi pata_acpi crct10dif_pclmul crct10dif_common crc32c_intel qxl
drm_kms_helper syscopyarea sysfillrect sysimgblt serio_raw fb_sys_fops ttm
drm floppy ata_piix libata virtio_pci virtio_ring virtio
drm_panel_orientation_quirks dm_mirror dm_region_hash dm_log dm_mod
Jun 26 16:13:14 roble kernel: CPU: 4 PID: 16530 Comm: kworker/4:3 Kdump:
loaded Tainted: G L ------------ 3.10.0-957.21.2.el7.x86_64 #1
Jun 26 16:13:14 roble kernel: Hardware name: oVirt oVirt Node, BIOS
1.11.0-2.el7 04/01/2014
Jun 26 16:13:14 roble kernel: Workqueue: events tsc_refine_calibration_work
Jun 26 16:13:14 roble kernel: task: ffffa016acf74100 ti: ffffa014f76a8000
task.ti: ffffa014f76a8000
Jun 26 16:13:14 roble kernel: RIP: 0010:[<ffffffffaefb97e0>]
[<ffffffffaefb97e0>] acpi_pm_read_verified+0x10/0x60
Jun 26 16:13:14 roble kernel: RSP: 0018:ffffa014f76abdb8 EFLAGS: 00000202
Jun 26 16:13:14 roble kernel: RAX: 00000000000addf6 RBX: 0000000000000086
RCX: 0000000000f16644
Jun 26 16:13:14 roble kernel: RDX: 0000000000000608 RSI: 00000000002aac00
RDI: ffffffffaf971901
Jun 26 16:13:14 roble kernel: RBP: ffffa014f76abdb8 R08: 00000000aff71901
R09: 0001427407e2e9e0
Jun 26 16:13:14 roble kernel: R10: 0001427407e2e9e0 R11: 0000000000000000
R12: 0000000000000004
Jun 26 16:13:14 roble kernel: R13: ffffa014f76abd38 R14: ffffffffaf62ea00
R15: ffffa0172f313900
Jun 26 16:13:14 roble kernel: FS: 0000000000000000(0000)
GS:ffffa0172f300000(0000) knlGS:0000000000000000
Jun 26 16:13:14 roble kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
Jun 26 16:13:14 roble kernel: CR2: 0000000000448d70 CR3: 000000017789a000
CR4: 00000000000606e0
Jun 26 16:13:14 roble kernel: Call Trace:
Jun 26 16:13:14 roble kernel: [<ffffffffaea3426d>] tsc_read_refs+0x8d/0xb0
Jun 26 16:13:14 roble kernel: [<ffffffffaea344b2>]
tsc_refine_calibration_work+0x1c2/0x220
Jun 26 16:13:14 roble kernel: [<ffffffffaeab9ebf>]
process_one_work+0x17f/0x440
Jun 26 16:13:14 roble kernel: [<ffffffffaeabaf56>] worker_thread+0x126/0x3c0
Jun 26 16:13:14 roble kernel: [<ffffffffaeabae30>] ?
manage_workers.isra.25+0x2a0/0x2a0
Jun 26 16:13:14 roble kernel: [<ffffffffaeac1da1>] kthread+0xd1/0xe0
Jun 26 16:13:14 roble kernel: [<ffffffffaeac1cd0>] ?
insert_kthread_work+0x40/0x40
Jun 26 16:13:14 roble kernel: [<ffffffffaf175c37>]
ret_from_fork_nospec_begin+0x21/0x21
Jun 26 16:13:14 roble kernel: [<ffffffffaeac1cd0>] ?
insert_kthread_work+0x40/0x40
Jun 26 16:13:14 roble kernel: Code: 43 ea 74 00 30 98 fb ae c7 05 81 ea 74
00 78 00 00 00 5d c3 0f 1f 80 00 00 00 00 66 66 66 66 90 8b 15 5d 74 7a 00
55 48 89 e5 ed <89> c6 81 e6 ff ff ff 00 ed 89 c1 81 e1 ff ff ff 00 ed 25
ff ff
7 months
VDI Brokering
by Ciro Iriarte
Hi!,
What's the usual way to implement VDI with oVirt?, is it usuallly
paired with a broker like UDS Enterprise / OpenUDS?, does it have
anything embedded that can solve the VM assignment for a group of
users?.
Regards.
CI.-
7 months
