virt

virt@lists.centos.org

2 participants
1613 discussions

spice server and GSSAPI
by Ranbir 30 Dec '17

30 Dec '17

Hello, Does anyone have spice server for KVM Linux guests working with GSSAPI authentication? I've been trying for a while and I simply can't get it to work. I don't know what I'm doing wrong. I wouldn't be surprised if I've misunderstood something. I followed this guide: https://www.freeipa.org/page/Libvirt_with_VNC_Consoles Yes, the above is for VNC consoles. I just adapted that write up for spice. When I try to connect to a console from either virt-manager or with virt-viewer, I'm prompted to enter a password (though I shouldn't be). When I type in my freeipa domain password, it gets rejected. libvirtd with Kerberos and GSSAPI is working perfectly. I can use virt-manager from my Fedora 26 desktop with the below URI: qemu+tcp://ranbir@kvmhost01/system virt-manager connects, I get a list of all the running KVMs and I can work with them like I would if I was running virt-manager over ssh with X forwarding. The only that doesn't work is viewing the consoles. Details: - my host is a fully updated CentOS 7 system - libvirtd is set to listen for tcp connections - I added the service spice/kvmhost01.theinside.rnr - I created a keytab for the above and put it on kvmhost01 in /etc/qemu-kvm/krb5.tab - the above file has owner:group set to qemu:root with perms 600 - I have the following in /etc/sasl2/qemu-kvm.conf mech_list: gssapi keytab: /etc/qemu-kvm/krb5.tab - I have the following in /etc/libvirt/qemu.conf spice_listen = "0.0.0.0" spice_tls = 0 spice_sasl = 1 spice_sasl_dir = "/etc/sasl2/" - the first time I try to view a console, I get the kerberos tickets I expect to: Ticket cache: KEYRING:persistent:625400004:krb_ccache_7rtJmh8 Default principal: ranbir(a)THEINSIDE.RNR Valid starting Expires Service principal 2017-12-29 18:37:45 2017-12-30 18:01:40 spice/kvmhost01.theinside.rnr(a)THEINSIDE.RNR 2017-12-29 18:37:40 2017-12-30 18:01:40 libvirt/kvmhost01.theinside.rnr(a)THEINSIDE.RNR 2017-12-29 18:01:40 2017-12-30 18:01:40 krbtgt/THEINSIDE.RNR(a)THEINSIDE.RNR I'm surprised there isn't more info available about this online. That's why I'm now here asking for assistance. Does anyone have any suggestions/advice? Thanks in advance! -- Ranbir

1 1

Xen PV DomU running Kernel 4.14.5-1.el7.elrepo.x86_64: xl -v vcpu-set <domU> <val> triggers domU kernel WARNING, then domU becomes unresponsive
by Adi Pircalabu 20 Dec '17

20 Dec '17

Has anyone seen this recently? I couldn't replicate it on: - CentOS 6 running kernel-2.6.32-696.16.1.el6.x86_64, kernel-lt-4.4.105-1.el6.elrepo.x86_64 - CentOS 7 running 4.9.67-1.el7.centos.x86_64 But I can replicate it consistently running "xl -v vcpu-set <domU> <val>" on: - CentOS 6 running 4.14.5-1.el6.elrepo.x86_64 - CentOS 7 running 4.14.5-1.el7.elrepo.x86_64 dom0 versions tested with similar results in the domU: - 4.6.6-6.el7 on kernel 4.9.63-29.el7.x86_64 - 4.6.3-15.el6 on kernel 4.9.37-29.el6.x86_64 Noticed behaviour: - These commands stall: top ls -l /var/tmp ls -l /tmp - Stuck in D state on the CentOS 7 domU: root 5 0.0 0.0 0 0 ? D 11:20 0:00 [kworker/u8:0] root 316 0.0 0.0 0 0 ? D 11:20 0:00 [jbd2/xvda1-8] root 1145 0.0 0.2 116636 4776 ? Ds 11:20 0:00 -bash root 1289 0.0 0.1 25852 2420 ? Ds 11:35 0:00 /usr/bin/systemd-tmpfiles --clean root 1290 0.0 0.1 125248 2696 pts/1 D+ 11:44 0:00 ls --color=auto -l /tmp/ root 1293 0.0 0.1 125248 2568 pts/2 D+ 11:44 0:00 ls --color=auto -l /var/tmp root 1296 0.0 0.2 116636 4908 pts/3 Ds+ 11:44 0:00 -bash root 1358 0.0 0.1 125248 2612 pts/4 D+ 11:47 0:00 ls --color=auto -l /var/tmp At a first glance it appears the issue is in 4.14.5 kernel. Stack traces follow: -----CentOS 6 kernel-ml-4.14.5-1.el6.elrepo.x86_64 start here----- ------------[ cut here ]------------ WARNING: CPU: 4 PID: 60 at block/blk-mq.c:1144 __blk_mq_run_hw_queue+0x9e/0xc0 Modules linked in: intel_cstate(-) ipt_REJECT nf_reject_ipv4 nf_conntrack_ipv4 nf_defrag_ipv4 xt_multiport iptable_filter ip_tables ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack libcrc32c ip6table_filter ip6_tables dm_mod dax xen_netfront crc32_pclmul crct10dif_pclmul ghash_clmulni_intel crc32c_intel pcbc aesni_intel glue_helper crypto_simd cryptd aes_x86_64 coretemp hwmon x86_pkg_temp_thermal sb_edac intel_rapl_perf pcspkr ext4 jbd2 mbcache xen_blkfront CPU: 4 PID: 60 Comm: kworker/4:1H Not tainted 4.14.5-1.el6.elrepo.x86_64 #1 Workqueue: kblockd blk_mq_run_work_fn task: ffff8802711a2780 task.stack: ffffc90041af4000 RIP: e030:__blk_mq_run_hw_queue+0x9e/0xc0 RSP: e02b:ffffc90041af7c48 EFLAGS: 00010202 RAX: 0000000000000001 RBX: ffff88027117fa80 RCX: 0000000000000001 RDX: ffff88026b053ee0 RSI: ffff88027351bca0 RDI: ffff88026b072800 RBP: ffffc90041af7c68 R08: ffffc90041af7eb8 R09: ffff8802711a2810 R10: 0000000000007ff0 R11: 0000000000000001 R12: ffff88026b072800 R13: ffffe8ffffd04d00 R14: 0000000000000000 R15: ffffe8ffffd04d05 FS: 00002b7b7c89b700(0000) GS:ffff880273500000(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffffff600400 CR3: 000000026d953000 CR4: 0000000000042660 Call Trace: blk_mq_run_work_fn+0x31/0x40 process_one_work+0x174/0x440 ? xen_mc_flush+0xad/0x1b0 ? schedule+0x3a/0xa0 worker_thread+0x6b/0x410 ? default_wake_function+0x12/0x20 ? __wake_up_common+0x84/0x130 ? maybe_create_worker+0x120/0x120 ? schedule+0x3a/0xa0 ? _raw_spin_unlock_irqrestore+0x16/0x20 ? maybe_create_worker+0x120/0x120 kthread+0x111/0x150 ? __kthread_init_worker+0x40/0x40 ret_from_fork+0x25/0x30 Code: 89 df e8 06 2f d9 ff 4c 89 e7 41 89 c5 e8 0b 6e 00 00 44 89 ee 48 89 df e8 20 2f d9 ff 48 8b 5d e8 4c 8b 65 f0 4c 8b 6d f8 c9 c3 <0f> ff eb aa 4c 89 e7 e8 e6 6d 00 00 48 8b 5d e8 4c 8b 65 f0 4c ---[ end trace fe2aaf4e723042fd ]--- -----CentOS 6 kernel-ml-4.14.5-1.el6.elrepo.x86_64 end here----- -----CentOS 7 kernel-ml-4.14.5-1.el7.elrepo.x86_64 start here----- [ 116.528885] ------------[ cut here ]------------ [ 116.528894] WARNING: CPU: 3 PID: 38 at block/blk-mq.c:1144 __blk_mq_run_hw_queue+0x89/0xa0 [ 116.528898] Modules linked in: intel_cstate(-) ip_set_hash_ip ip_set nfnetlink x86_pkg_temp_thermal coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel crypto_simd glue_helper cryptd intel_rapl_perf pcspkr nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables ext4 mbcache jbd2 xen_netfront xen_blkfront crc32c_intel [ 116.528919] CPU: 3 PID: 38 Comm: kworker/3:1H Not tainted 4.14.5-1.el7.elrepo.x86_64 #1 [ 116.529007] Code: 00 e8 7c c5 45 00 4c 89 e7 e8 14 4b d7 ff 48 89 df 41 89 c5 e8 19 66 00 00 44 89 ee 4c 89 e7 e8 2e 4b d7 ff 5b 41 5c 41 5d 5d c3 <0f> ff eb b4 48 89 df e8 fb 65 00 00 5b 41 5c 41 5d 5d c3 0f ff [ 116.529034] ---[ end trace a7814e3ec9a330c6 ]--- [ 147.424117] ------------[ cut here ]------------ [ 147.424150] WARNING: CPU: 2 PID: 24 at block/blk-mq.c:1144 __blk_mq_run_hw_queue+0x89/0xa0 [ 147.424160] Modules linked in: ip_set_hash_ip ip_set nfnetlink x86_pkg_temp_thermal coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel crypto_simd glue_helper cryptd intel_rapl_perf pcspkr nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables ext4 mbcache jbd2 xen_netfront xen_blkfront crc32c_intel [ 147.424222] CPU: 2 PID: 24 Comm: kworker/2:0H Tainted: G W 4.14.5-1.el7.elrepo.x86_64 #1 [ 147.424238] Workqueue: kblockd blk_mq_run_work_fn [ 147.424247] task: ffff88007c539840 task.stack: ffffc900403e4000 [ 147.424259] RIP: e030:__blk_mq_run_hw_queue+0x89/0xa0 [ 147.424270] RSP: e02b:ffffc900403e7e30 EFLAGS: 00010202 [ 147.424279] RAX: 0000000000000001 RBX: ffff880003b83800 RCX: ffff88007d11bca0 [ 147.424288] RDX: ffff88007c656c88 RSI: 00000000000000a0 RDI: ffff880003b83800 [ 147.424298] RBP: ffffc900403e7e48 R08: 0000000000000000 R09: 0000000000000000 [ 147.424309] R10: 0000000000007ff0 R11: 00000000000074e5 R12: ffff88007c436900 [ 147.424319] R13: ffff88007d11bc80 R14: ffff88007d121b00 R15: ffff880003b83848 [ 147.424340] FS: 0000000000000000(0000) GS:ffff88007d100000(0000) knlGS:ffff88007d100000 [ 147.424350] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 147.424359] CR2: 00007f504f19a700 CR3: 0000000079bed000 CR4: 0000000000042660 [ 147.424370] Call Trace: [ 147.424384] blk_mq_run_work_fn+0x2c/0x30 [ 147.424400] process_one_work+0x149/0x360 [ 147.424411] worker_thread+0x4d/0x3e0 [ 147.424421] kthread+0x109/0x140 [ 147.424432] ? rescuer_thread+0x380/0x380 [ 147.424441] ? kthread_park+0x60/0x60 [ 147.424455] ret_from_fork+0x25/0x30 [ 147.424463] Code: 00 e8 7c c5 45 00 4c 89 e7 e8 14 4b d7 ff 48 89 df 41 89 c5 e8 19 66 00 00 44 89 ee 4c 89 e7 e8 2e 4b d7 ff 5b 41 5c 41 5d 5d c3 <0f> ff eb b4 48 89 df e8 fb 65 00 00 5b 41 5c 41 5d 5d c3 0f ff [ 147.424554] ---[ end trace a7814e3ec9a330c7 ]--- -----CentOS 7 kernel-ml-4.14.5-1.el7.elrepo.x86_64 end here----- -- Adi Pircalabu

4 7

Proposal to CANCEL: 2017-12-26 Virt SIG meeting
by Sandro Bonazzola 19 Dec '17

19 Dec '17

Hi folks, I'm proposing to cancel the Virt SIG meeting on December 26th due to Holidays. If you're aware of anything important we have to discuss next week, please do reply to this mail. Thanks! -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

2 1

katello-agent is available for testing in CentOS Virt SIG
by Sandro Bonazzola 15 Dec '17

15 Dec '17

Hi, for those willing to use katello for monitoring oVirt hosts upgrade status, we added katello-agent to CentOS Virt SIG testing repo. If no negative feedback is provided, I'll tag it for release on December 20th. In order to install it: # yum install centos-release-ovirt41 # yum-config-manager --enable centos-ovirt41-testing --save # yum install katello-agent Note that oly the agent/client part has been included in Virt SIG, in order to install foreman with katello plugin follow katello website instructions. For more info about katello: https://www.theforeman.org/plugins/katello/ Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

Xen 4.6.6-8 in virt-testing
by George Dunlap 13 Dec '17

13 Dec '17

Xen 4.6.6-8 has been tagged in virt-testing. It contains XSAs 248-251, as well as an additional fix to XSA 240. Please test it if you get a chance and report any bugs; I'll probably push it to mirrors tomorrow if I don't hear anything. Peace, -George

2 2

ANNOUNCE: Upstream libvirt{, -python} releases built for CentOS
by Jiri Denemark 12 Dec '17

12 Dec '17

Hi all, Apparently some folks use CentOS for developing and/or testing software on top of libvirt (e.g., oVirt), which may be a bit troublesome since the version of libvirt released with CentOS is usually quite old compared to upstream. Using the downstream releases of libvirt for developing new features can introduce several months of delay, which may not be acceptable. So to make the development easier for folks who want to stick with CentOS I started to built upstream libvirt releases for Virt-SIG. The builds are not just a result of "make rpm", they are proper rebased versions of the released CentOS builds. In other words, all required downstream changes are ported to the new libvirt release. Regular CentOS builds essentially use one of these rebased builds as a base. You can expect both libvirt and libvirt-python CentOS builds within a few days after they are released upstream, unless I'm on vacation or CBS is not cooperating. The official repository for these build is http://mirror.centos.org/centos-7/7/virt/x86_64/libvirt-latest/ If you want packages for other architectures (there's no virt directory in http://mirror.centos.org/altarch/7/) you can use https://buildlogs.centos.org/centos/7/virt/$basearch/libvirt-latest/ or specifically https://buildlogs.centos.org/centos/7/virt/ppc64le/libvirt-latest/ https://buildlogs.centos.org/centos/7/virt/aarch64/libvirt-latest/ https://buildlogs.centos.org/centos/7/virt/x86_64/libvirt-latest/ Happy hacking. Jirka

1 0

Re: [CentOS-virt] [ovirt-users] qemu-kvm-ev-2.9.0-16.el7_4.11.1 now available for testing
by Sandro Bonazzola 12 Dec '17

12 Dec '17

2017-12-11 18:11 GMT+01:00 Markus Stockhausen <stockhausen(a)collogia.de>: > Hi Sandro, > > I'm wondering if BZ1513362 (AIO stuck fixed in qemu-kvm-rhev-2.9.0-16.el7_ > 4.12) > will be worth to give the newer version a try. > Above version is not yet released, can't see it on ftp://ftp.redhat.com/pub/redhat/linux/enterprise/7Server/en/RHEV/SRPMS/ > > Best regards. > > Markus > > --------------------- > *Von:* users-bounces(a)ovirt.org [users-bounces(a)ovirt.org]" im Auftrag von > "Sandro Bonazzola [sbonazzo(a)redhat.com] > *Gesendet:* Montag, 11. Dezember 2017 17:43 > *An:* Discussion about the virtualization on CentOS; devel; users > *Betreff:* [ovirt-users] qemu-kvm-ev-2.9.0-16.el7_4.11.1 now available > for testing > > Hi, qemu-kvm-ev-2.9.0-16.el7_4.11.1 > <https://cbs.centos.org/koji/buildinfo?buildID=21003> is now available > for testing. > If no negative feedback will be reported, I'm going to push to release on > Thursday, December 14th. > > Here's the changelog: > > * Mon Dec 11 2017 Sandro Bonazzola <sbonazzo(a)redhat.com> - > ev-2.9.0-16.el7_4.11.1 - Removing RH branding from package name * Mon Nov > 13 2017 Miroslav Rezanina <mrezanin(a)redhat.com> - rhev-2.9.0-16.el7_4.11 > - kvm-exec-use-qemu_ram_ptr_length-to-access-guest-ram.patch [bz#1472185] > - kvm-multiboot-validate-multiboot-header-address-values.patch > [bz#1501123] - Resolves: bz#1472185 (CVE-2017-11334 qemu-kvm-rhev: Qemu: > exec: oob access during dma operation [rhel-7.4.z]) - Resolves: bz#1501123 > (CVE-2017-14167 qemu-kvm-rhev: Qemu: i386: multiboot OOB access while > loading kernel image [rhel-7.4.z]) * Mon Oct 23 2017 Miroslav Rezanina < > mrezanin(a)redhat.com> - rhev-2.9.0-16.el7_4.10 - > kvm-vga-stop-passing-pointers-to-vga_draw_line-functions.patch > [bz#1501300] - kvm-vga-drop-line_offset-variable.patch [bz#1501300] - > kvm-vga-handle-cirrus-vbe-mode-wraparounds.patch [bz#1501300] - > kvm-cirrus-fix-oob-access-in-mode4and5-write-functions.patch [bz#1501300] > - Resolves: bz#1501300 (CVE-2017-15289 qemu-kvm-rhev: Qemu: cirrus: OOB > access issue in mode4and5 write functions [rhel-7.4.z]) * Mon Oct 09 2017 > Miroslav Rezanina <mrezanin(a)redhat.com> - rhev-2.9.0-16.el7_4.9 - > kvm-nbd-client-Fix-regression-when-server-sends-garbage.patch > [bz#1495474] - kvm-fix-build-failure-in-nbd_read_reply_entry.patch > [bz#1495474] - kvm-nbd-client-avoid-spurious-qio_channel_yield-re-entry.patch > [bz#1495474] - kvm-nbd-client-avoid-read_reply_co-entry-if-send-failed.patch > [bz#1495474] - kvm-qemu-iotests-improve-nbd-fault-injector.py-startup-p.patch > [bz#1495474] - kvm-qemu-iotests-test-NBD-over-UNIX-domain-sockets-in-08.patch > [bz#1495474] - kvm-block-nbd-client-nbd_co_send_request-fix-return-code.patch > [bz#1495474] - Resolves: bz#1495474 (Fail to quit source qemu when do live > migration after mirroring guest to NBD server [rhel-7.4.z]) > > <https://cbs.centos.org/koji/buildinfo?buildID=21003>-- > > SANDRO BONAZZOLA > > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > > -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

qemu-kvm-ev-2.9.0-16.el7_4.11.1 now available for testing
by Sandro Bonazzola 11 Dec '17

11 Dec '17

Hi, qemu-kvm-ev-2.9.0-16.el7_4.11.1 <https://cbs.centos.org/koji/buildinfo?buildID=21003> is now available for testing. If no negative feedback will be reported, I'm going to push to release on Thursday, December 14th. Here's the changelog: * Mon Dec 11 2017 Sandro Bonazzola <sbonazzo(a)redhat.com> - ev-2.9.0-16.el7_4.11.1 - Removing RH branding from package name * Mon Nov 13 2017 Miroslav Rezanina <mrezanin(a)redhat.com> - rhev-2.9.0-16.el7_4.11 - kvm-exec-use-qemu_ram_ptr_length-to-access-guest-ram.patch [bz#1472185] - kvm-multiboot-validate-multiboot-header-address-values.patch [bz#1501123] - Resolves: bz#1472185 (CVE-2017-11334 qemu-kvm-rhev: Qemu: exec: oob access during dma operation [rhel-7.4.z]) - Resolves: bz#1501123 (CVE-2017-14167 qemu-kvm-rhev: Qemu: i386: multiboot OOB access while loading kernel image [rhel-7.4.z]) * Mon Oct 23 2017 Miroslav Rezanina <mrezanin(a)redhat.com> - rhev-2.9.0-16.el7_4.10 - kvm-vga-stop-passing-pointers-to-vga_draw_line-functions.patch [bz#1501300] - kvm-vga-drop-line_offset-variable.patch [bz#1501300] - kvm-vga-handle-cirrus-vbe-mode-wraparounds.patch [bz#1501300] - kvm-cirrus-fix-oob-access-in-mode4and5-write-functions.patch [bz#1501300] - Resolves: bz#1501300 (CVE-2017-15289 qemu-kvm-rhev: Qemu: cirrus: OOB access issue in mode4and5 write functions [rhel-7.4.z]) * Mon Oct 09 2017 Miroslav Rezanina <mrezanin(a)redhat.com> - rhev-2.9.0-16.el7_4.9 - kvm-nbd-client-Fix-regression-when-server-sends-garbage.patch [bz#1495474] - kvm-fix-build-failure-in-nbd_read_reply_entry.patch [bz#1495474] - kvm-nbd-client-avoid-spurious-qio_channel_yield-re-entry.patch [bz#1495474] - kvm-nbd-client-avoid-read_reply_co-entry-if-send-failed.patch [bz#1495474] - kvm-qemu-iotests-improve-nbd-fault-injector.py-startup-p.patch [bz#1495474] - kvm-qemu-iotests-test-NBD-over-UNIX-domain-sockets-in-08.patch [bz#1495474] - kvm-block-nbd-client-nbd_co_send_request-fix-return-code.patch [bz#1495474] - Resolves: bz#1495474 (Fail to quit source qemu when do live migration after mirroring guest to NBD server [rhel-7.4.z]) <https://cbs.centos.org/koji/buildinfo?buildID=21003>-- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

4.4.4-26 with XSA-226, 227, 230 in centos-virt-testing
by Kevin Stange 28 Nov '17

28 Nov '17

Xen 4.4.4 along with kernel 4.9.44 containing patches for XSAs (226 - 230) from August 15th are now available in centos-virt-testing. If possible, please test and provide feedback here so we can move these to release soon. XSA-228 did not affect Xen 4.4 XSA-229 only applies to the kernel XSA-235 disclosed today only affects ARM and isn't going to be added to these packages. Thanks. -- Kevin Stange Chief Technology Officer Steadfast | Managed Infrastructure, Datacenter and Cloud Services 800 S Wells, Suite 190 | Chicago, IL 60607 312.602.2689 X203 | Fax: 312.602.2688 kevin(a)steadfast.net | www.steadfast.net

3 4

Xen 4.6.6-7 packages in virt-testing
by George Dunlap 28 Nov '17

28 Nov '17

I've tagged the 4.6.6-7, which contain XSAs 246 and 247, in testing; they should show up in virt-testing soon. Please report any issues; I'll probably tag for release tomorrow (to show up Thursday). -George

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt