virt June 2014

virt@lists.centos.org

38 participants
29 discussions

How to debug Ubuntu 8.04 LTS guest crash during install?
by Neil Aggarwal 04 Nov '25

04 Nov '25

Hello: I am using kvm on a CentOS 5.4 server. I am trying to install the TunkeyLinux Core appliance found here: http://www.turnkeylinux.org/core I downloaded the ISO file from the web site. Then, I used this command to intall it: virt-install -n tkl-core -r 512 --vcpus=1 --check-cpu --os-type=linux --os-variant=ubuntuhardy -v --accelerate -c /tmp/turnkey-core-2009.10-hardy-x86.iso -f /var/lib/libvirt/images/tkl-core.img -s 15 -b br0 --vnc noautoconsole When I connect to the VNC console, I get the Turnkey linux options screen. I select Install to hard disk from there and it seems to start the install but crashes during the installer startup. This is repeatable so there has to be a way to debug it. I tried turning on the debug option for virt-install but that did not give me any useful info. Any ideas how to debug this? Thanks, Neil -- Neil Aggarwal, (281)846-8957, http://UnmeteredVPS.net/cpanel cPanel/WHM preinstalled on a virtual server for only $40/month! No overage charges, 7 day free trial, PayPal, Google Checkout

3 4

KVM integrated network (user mode) dying after inactivity
by Timo Schöler 03 Aug '14

03 Aug '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi list, I searched the web for bug reports regarding this phenomenon I see on *multiple* machines of a customer, however, I didn't find an exact fit. So, I'd like to ask here whether anyone else has run into this. I have multiple CentOS 6 machines running using KVM to virtualize a bunch of machines on them (LVM-based). Software releases as following: [root@fe00 ~]# rpm -qa|egrep '(virt|kvm)' virt-viewer-0.5.6-8.el6_5.3.x86_64 libvirt-python-0.10.2-29.el6_5.7.x86_64 libvirt-client-0.10.2-29.el6_5.7.x86_64 qemu-kvm-0.12.1.2-2.415.el6_5.8.x86_64 libvirt-0.10.2-29.el6_5.7.x86_64 python-virtinst-0.600.0-18.el6.noarch [root@fe00 ~]# uname -r 2.6.32-431.17.1.el6.x86_64 The VMs (here: two) have the "default" connection provided by KVM (heading to the internet) as well as a bridged interface to connect to a high performance backbone, where sensitive data is kept and bandwidth is an issue (or better, not :), on a second interface within the VMs: [root@fe00 ~]# brctl show bridge name bridge id STP enabled interfaces br1 8000.001b21xxxxxx yes eth1 vnet1 vnet3 virbr0 8000.525400xxxxxx yes virbr0-nic vnet0 vnet2 br1 is the interface connected to the backbone, virbr0 KVM's user mode network. After some time of inactivity on the virbr0 interface, from *within* the VMs connection is *lost*. The interface(s) lose their IP; running dhclient(8) is not of any use. To get the machine back onto track, ``service libvirtd restart'' has to be issued: Vanished iptables rules show up again. (This, in contrast to an Ubuntu document [0], fixes it without shutting the VM(s) down.) Starting dhclient(8) within the VMs gets connectivity back. Just out of curiosity I let one of the VMs cause some ICMP traffic now and then hit the interface -- ``ping -i 10 some.nice.host'' is sufficient to keep that interface alive. The virbr0-headed interfaces are almost only being used to get updates etc -- management and load-balanced services are being served by the bridged interface. Is this a bug or a feature? Best, Timo [0] -- https://help.ubuntu.com/community/KVM/Networking#Network_Bridge_Losing_Conn… -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iF4EAREIAAYFAlOPaBgACgkQuSPmkPhAW0r9lgD/cgsDSxaOlD150DLbF+PIGjS7 3qSv3rob7NQEz4wJkUIA/1KfjLmCGm1y2LLroFsWbfckTnDfN3LSG1sUNvygLB/C =ZhOI -----END PGP SIGNATURE-----

4 4

[ Off Topic ] WorkShop Virtualização com Proxmox VE
by Gilberto Nunes 30 Jun '14

30 Jun '14

WorkShop Virtualização com Proxmox VE ------------------------------ <https://www.facebook.com/sharer/sharer.php?s=100&p[url]=http://blog.konnect…> Dia 12 de Julho, Sábado, a partir das 08hs00 acontecerá o WorkShop Virtualização com Proxmox VE. Venha conhecer uma das melhores ferramentas de Virtualização do Mercado. Com este treinamento, sua equipe de TI terá uma ótima ferramenta de virtualização. - O que é o Proxmox VE - Instalação e Configuração - Clusterização e Alta Disponibilidade de Virtual Machines - Backup de VM - Snapshot... - Desktop Virtual com Spice - Cluster e Alta Disponibilidade O evento acontecerá dia 21 de Julho de 2014, em Joinville - Santa Catarina. Será um Sábado, sendo que o horário o que segue abaixo: Início: 08hs00 Intervalo: 10hs00 Almoço: 12hs00 ( * ALMOÇO NÃO INCLUSO. ) Retorno: 13hs00 Encerramento: 16hs00 Será realizado nas dependências da Fundação Softville, cito no endereço abaixo: *R. Otto Boehm, 48 - América, Joinville - SC, 89201-700* Local do Evento <http://blog.konnectati.com.br/arquivos/1276> Rua Otto Boehm, 48 - América, Joinville - SC, República Federativa do Brasil Fundação Softville more >> <http://blog.konnectati.com.br/arquivos/1276> Aproveite! Facilidade de pagamento, certificado e apostila. Contato: gilberto.ferreira(a)konnectati.com.br (47) 9676-7530 Ementa do Treinamento: Clique aqui para ter acesso <http://www.konnectati.com.br/pasta/indica2.pdf>. Investimento: R$ 800,00 por pessoa. *Clique aqui e compre agora! <http://blog.konnectati.com.br/produto/treinamento-proxmox-ve>* ** Parcele em até 12 vezes nos cartões Visa, Master e American Express...* [image: WorkShop] <http://blog.konnectati.com.br/wp-content/uploads/treinamento-pve-softville.…> -- Gilberto Ferreira

1 0

Re: [CentOS-virt] MS-Win7 kvm guest gets dhcp from host bridge
by James B. Byrne 23 Jun '14

23 Jun '14

On Mon, June 23, 2014 00:29, Arun Khan wrote: > On Thu, Feb 20, 2014 at 3:36 AM, Dusty Mabe <dustymabe(a)gmail.com> wrote: >> >> On 02/19/2014 04:01 PM, James B. Byrne wrote: The root cause of the original problem was a change in the behaviour of libvirt (and the GUI of virt-manager) when creating new vms. The host system was already bridged and had other vms previously created and attached to the bridge without exhibiting this behaviour. I infer that at some point an update to libvirt altered the default configuration to always prefer NAT. A change that I failed to notice and was not conscious of given I had previous created vms without encountering this problem. Changing the configuration of the affected vms nic Source Device to 'Specify shared device name' and then specifying the Bridge Name fixed the problem. I have already commented elsewhere on the needlessly obtuse wording used for the Source Device when bridging is required. Why it does not say 'Specify bridge name' or 'Use named bridge' instead has not been plausibly explained by the maintainers. It is particularly vexatious given that when one selects 'Specify shared device name' the GUI immediately alters to display a text box labelled 'Bridge name:' Duhhh. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

MS-Win7 kvm guest gets dhcp from host bridge
by James B. Byrne 23 Jun '14

23 Jun '14

CentOS-6.5 i86_64 qemu-kvm-0.12.1.2-2.415.el6_5.4 MS-Windows v7proSP1 We have installed a MicroSoft Win7 system as a guest and have joined it to our MS AD domain. The system runs and has internet access. However, the IPv4 address it obtains and the gateway it is assigned are both sourced from the virtual machine host system and not from our AD DC DHCP server. To clarify, the virbr0 IP address is 192.168.122.1 and the Windows guest has that address as its gateway and an IP address in the 192.168.122.0/24 netblock. This is not as we desire as the internal addresses we regularly assign to MS workstations via DHCP are supposed to belong to a different netblock entirely. This permit filtering on incoming and outgoing traffic at the gateway. I realize that there is a DHCP service running on virbr0 for the purpose of provisioning guests with system control traffic but I do not know how to limit that to its intended purpose and allow another DHCP server to provide the IP address to the windows guests. I hope that problem description is not too confusing. Can anyone provide me with some guidance on the matter? Are kvm guests required to have either static ip addresses or dhcp addresses provided by the host system? Thanks in advance. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

4 3

Preferred method of provisioning VM images
by Lars Kurth 20 Jun '14

20 Jun '14

Hi all, following the discussion on about documentation, I was wondering whether we need to look at a standard way in which we recommend how to provision images for VMs. Am starting this with a Xen hat, but the discussion should not be specific to this. There are a number of options, but all have some trade-offs == #1 virt-install == Advantages: similar to KVM Disadvantages: may cause weird issues / confusion with people switching back to xl. The core issue is that with the current version of xen and libvirt, this only works with xm (when xl is used, this can create some undefined behavior). However as we have seen in some recent threads on this list, people tend to mix which can cause problems. == #2 xen-tools == Advantages: Very flexible. Many other distros use xen-tools, so we have lots of beginners docs that just need to be tweaked Disadvantages: needs porting/packaging for CentOS. Does not work for kvm. Says "xen". (Maybe that's an advantage.) We know that xen-tools works with Fedora (see http://blog.xen.org/index.php/2013/01/24/using-xen-tools-on-fedora/) so the porting effort may be small Unknowns: What would be needed to make it work for CentOS == #3 virt-builder (http://libguestfs.org/virt-builder.1.html) == Advantages: supports KVM, Xen and other VM inages. Seems easy to use. - if so, it would avoid xm / xl confusion. Unknowns: Not sure at which level virt-builder integrates with Xen and other hypervisors. It seems to operate at disk image format (similar to xen-tools) . I don't know whether virt-builder is restricted to some hypervisors in RHEL7. Disadvantages: may need porting/packaging for CentOS. It appears as if it will be in RHEL7, so it may just appear with CentOS 7. If not, some porting work may need to be done. == #4 Cloud Image from Cloud Image SIG == We could rely on pre-built cloud images from the Cloud Images SIG. People could just download the cloud image once it's done and customize it, rather than installing / building their own. Advantages: seems easy Disadvantages: coordination with Cloud Images SIG. May not be flexible enough I just wanted to start a discussion about this and ask for input. This topic which has come up a number of times in SIG meetings as a facgtor influencing libvirt and other package versions. Regards Lars

12 31

How to create an OpenVZ OS Template for CentOS 7 Public QA
by Scott Dowdle 17 Jun '14

17 Jun '14

Greetings, First start of by working on a physical system, virtual machine, or container that matches the OS Template you are wanting to build. I used my CentOS 7 Public QA OS OpenVZ container to build it. You must of course have a working yum. Once we are beyond Public QA and there is stuff in /etc/yum.repos.d/ this won't be a problem. One thing to note is that the --enablerepo= must refer to a repo your build host has and viewable via "yum repolist". That repo should point to the desired CentOS 7 build tree directory. A note about the package list. Yes, listed out every individual packcage is tedious. Perhaps some package groups could be used but they typically drag in a lot of unwanted additional packages. Suggestions welcome. Here is a simple script and please don't nag at me because I'm a scripting novice. I hope email client word wrapping and screen sizes don't butcher it too bad: - - - - - # To get a package list without version numbers from a target system # rpm -qa --qf "%{n} " > packages.txt # Put contents of packages.txt after "-y install \" line below mkdir /ostemplate yum \ --installroot /ostemplate \ --nogpg \ --releasever=7 \ --enablerepo=centos7pubqa \ -y install \ centos-release filesystem ncurses-base mailcap tzdata glibc-common xz-libs \ ncurses-libs pcre libselinux info libdb popt sed libcom_err libuuid expat \ libacl libgpg-error dbus-libs gawk lua libxml2 glib2 shared-mime-info apr cpio \ gmp p11-kit tcp_wrappers-libs perl-parent perl-podlators perl-Text-ParseWords \ perl-Pod-Escapes perl-libs perl-threads perl-constant perl-Filter \ perl-Time-Local perl-threads-shared perl-File-Path perl-Scalar-List-Utils \ perl-Getopt-Long libcap-ng nss-softokn libassuan libunistring diffutils gpm-libs \ libnfnetlink keyutils-libs gettext-libs p11-kit-trust nettle \ gobject-introspection vim-minimal pinentry make libselinux-utils ncurses \ libverto libsemanage krb5-libs openldap cracklib libmount systemd-libs libuser \ pam libblkid util-linux python-libs dhcp-libs libcurl python-urlgrabber rpm-libs \ dhcp-common libselinux-python python-iniparse python-chardet yum-metadata-parser \ python-backports-ssl_match_hostname newt-python pyxattr binutils logrotate \ procps-ng mariadb-libs fipscheck-lib openssh libmnl iptables json-c \ device-mapper cryptsetup-libs dbus iputils cronie-anacron crontabs libestr \ gnupg2 rpm-python pygpgme libnl3 yum-utils man-db dhclient audit openssh-server \ libgudev1 net-tools elinks python-pyudev policycoreutils python-configobj \ pygobject3-base sudo wget file tar which psmisc libpcap libsysfs libdaemon lzo \ libgcc setup basesystem kbd-misc bind-license nss-softokn-freebl glibc libstdc++ \ bash libsepol zlib audit-libs nspr chkconfig bzip2-libs nss-util grep libattr \ libcap elfutils-libelf libgcrypt readline libidn libffi pkgconfig sqlite \ groff-base file-libs libtasn1 slang gdbm perl-HTTP-Tiny perl-Pod-Perldoc \ perl-Encode perl-Pod-Usage perl-macros perl-Storable perl-Carp perl-Exporter \ perl-Socket perl-File-Temp perl-PathTools perl-Pod-Simple perl apr-util libcroco \ cyrus-sasl-lib libgomp kmod-libs libedit hostname js newt ca-certificates less \ dbus-glib acl libdb-utils findutils xz sysvinit-tools ustr nss-tools \ openssl-libs gzip cracklib-dicts nss libpwquality coreutils shadow-utils \ libutempter nss-sysinit python libssh2 python-pycurl curl rpm python-decorator \ python-slip dbus-python python-kitchen python-backports python-setuptools \ pyliblzma centos-logos kmod openssl nss_compat_ossl bind-libs-lite fipscheck \ httpd-tools libnetfilter_conntrack iproute qrencode-libs device-mapper-libs \ systemd systemd-sysv initscripts cronie libpipeline pth rpm-build-libs gpgme yum \ libnl3-cli rsyslog mlocate kbd postfix httpd ebtables openssh-clients authconfig \ python-slip-dbus mc gettext screen passwd gnutls elfutils-libs libss nano snappy \ libndp ethtool hardlink rootfiles ln -sf /proc/mounts /ostemplate/etc/mtab # I want Mountain time to be the default ln -sf /usr/share/zoneinfo/America/Denver /ostemplate/etc/localtime # Now compress that sucker cd /ostemplate ; tar -cvJf /root/centos-7-x86_64-viayum.tar.xz . ; cd ls -lh /root/centos-7-x86_64-viayum.tar.xz echo "Done building OS Template. Now test it." - - - - - TYL, -- Scott Dowdle 704 Church Street Belgrade, MT 59714 (406)388-0827 [home] (406)994-3931 [work]

1 0

Are xen and centos incompatible?
by lee 17 Jun '14

17 Jun '14

Hi, I'm trying to pass a physical network interface through to a domU. This seems to be impossible because the way xen wants to do it is incompatible with the way centos wants to do it. I followed documentation on http://www.xen-support.com/?p=151 and tried booting with 'pciback.permissive pciback.hide=(06:00.0)'. This gives a hint in dmesg "kernel: xen-pciback: backend is vpci", and the device is still visible in dom0. So this obviously doesn't work. Following http://wiki.xen.org/wiki/Xen_PCI_Passthrough: [root@heimdall ~]# xl pci-assignable-add 06:00.0 xend is running, which may cause unpredictable results when using this xl command. Please shut down xend before continuing. (This check can be overridden with the -f option.) [root@heimdall ~]# There doesn't seem to be any documentation about what xend does or is for and how to pass a physical network interface through with it. I'm starting to think that using centos for a server os is an extremely bad choice because nothing works. It's not like a Linux distribution but like a mess of pieces from several unrelated puzzles thrown together randomly. -- Knowledge is volatile and fluid. Software is power.

5 12

Centos 6.5 Xen Stock cannot run dom-u PCI: Fatal: - ipmi_si
by Periko Support 17 Jun '14

17 Jun '14

I had a supermicro server SuperServer 1027R-WRF4+ and a old Dell PowerEdge 2950. In both machines I setup centos 6.5, which is running 3.10.34-11.el6.centos.alt.x86_64. I follow Xen4Cen wiki to setup Xen, I had other servers running Centos 5.x without issues. Now, once I build my vm's dom-u centos 6.5/centos 5.9 both x64, I receive different erros, let me show u the message I receive in my console for centos 6.5 dum-u. xl console oerp-server PCI: Fatal: No config space access function found ipmi_si: Could not set up I/O space ipmi_si: Could not set up I/O space ipmi_si: Could not set up I/O space Something related to ipmi in my server which is enable by default? can be, now what happen is I try to boot xentos 5.9 x64 dom-u: Brought up 1 CPUs checking if image is initramfs... it is Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 65536 (order: 7, 524288 bytes) TCP established hash table entries: 262144 (order: 10, 4194304 bytes) TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) TCP: Hash tables configured (established 262144 bind 65536) TCP reno registered audit: initializing netlink socket (disabled) type=2000 audit(1402907331.494:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Initializing Cryptographic API alg: No test for crc32c (crc32c-generic) ksign: Installing public key data Loading keyring - Added public key 691B840A64868995 - User ID: CentOS (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones brd: module loaded Xen virtual console successfully installed as xvc0 Event-channel device installed. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx ide-floppy driver 0.99.newide usbcore: registered new driver hiddev usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 TCP bic registered Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 XENBUS: Device with no driver: device/console/0 Initalizing network drop monitor service Write protecting the kernel read-only data: 506k Red Hat nash version 5.1.19.6 starting Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Loading ehci-hcd.ko module Loading ohci-hcd.ko module Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 Loading jbd.ko module Loading ext3.ko module Loading xenblk.ko module XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 1) Loading dm-mod.ko module device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.11.6-ioctl (2011-02-18) initialised: dm-devel(a)redhat.com Loading dm-log.ko module Loading dm-mirror.ko module Loading dm-zero.ko module Loading dm-snapshot.ko module Loading dm-mem-cache.ko module Loading dm-region_hash.ko module Loading dm-message.ko module Loading dm-raid45.ko module device-mapper: dm-raid45: initialized v0.2594l Scanning and configuring dmraid supported devices Scanning logical volumes Reading all physical volumes. This may take a while... No volume groups found Activating logical volumes Volume group "VolGroup00" not found Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! Looks is not finding the dom-u disk. In both cases I'm using almost the same settings: name = "centos5" uuid = "5020979f-8dae-105d-df56-9fb28d377aa2" bootloader = "/usr/bin/pygrub" memory = 2048 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" disk = [ "tap:aio:/ext4/centos5/disk.img,xvda,w" ] vif = [ "mac=X:X:X:X:X:X,bridge=xenbr0,script=vif-bridge" ] The main line of centos stock without Xen continue using kernel 2.6.x, but Xen is using the new line 3.x. Anyone else with this issue? Thanks for your time.

3 14

Re: [CentOS-virt] [Xen-users] Can't get vnc connections to bind to 0.0.0.0
by Periko Support 17 Jun '14

17 Jun '14

On Tue, Jun 17, 2014 at 7:47 AM, Ian Campbell <Ian.Campbell(a)citrix.com> wrote: > On Tue, 2014-06-17 at 10:41 -0400, Phillip Susi wrote: >> On 6/17/2014 10:10 AM, Ian Campbell wrote: >> > Which toolstack. >> >> xl >> >> > This is a PVFB, not sure if they work for HVM or not. >> >> Seems to work just fine other than refusing to bind to 0.0.0.0 so I >> can access it from another machine on the network without setting up >> an ssh tunnel. >> >> > You probably want a toplevel vnclisten="0.0.0.0:0" to cause the >> > VNC associated with the emulated VGA to be bound to the address >> > which you want. >> >> "toplevel"? > > I mean literally write: > vnclisten="0.0.0.0:0" > in your configuration file, not wrapped in a vfg = []. > > Ian > > > _______________________________________________ > Xen-users mailing list > Xen-users(a)lists.xen.org > http://lists.xen.org/xen-users This is my settings: vfb = [ "type=vnc,vnclisten=192.168.2.27,vncpasswd=XXXXXX,vncdisplay=1,keymap=en-us" ] Hope this helps.

1 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt June 2014