[root@kvm2 bin]# seq 3 | while read i; do echo $i; done 1 2 3 [root@kvm2 bin]# seq 3 | while read i; do echo $i ; ssh kvm1 date ; done 1 Wed Sep 13 15:55:46 CEST 2017 [root@kvm2 bin]# for i in $(seq 3) ; do echo $i ; ssh kvm1 date ; done 1 Wed Sep 13 15:55:54 CEST 2017 2 Wed Sep 13 15:55:54 CEST 2017 3 Wed Sep 13 15:55:54 CEST 2017 [root@kvm2 bin]# for i in $(seq 3) ; do echo $i ; ssh -n kvm1 date ; done 1 Wed Sep 13 15:56:03 CEST 2017 2 Wed Sep 13 15:56:04 CEST 2017 3 Wed Sep 13 15:56:04 CEST 2017
cdrecord is not the state of art anymore :-)
yum install dvd+rw-tools growisofs -speed=1 -dvd-compat -Z /dev/sr0=CentOS-7-x86_64-DVD.iso
Not that easy as with linux, but also not that hard
fdisk /dev/sdh # create partition as shown below fdisk -l /dev/sdh Device Boot Start End Blocks Id System /dev/sdh1 2048 7864319 3931136 7 HPFS/NTFS/exFAT mkfs.ntfs -f /dev/sdh1 if=/usr/lib/syslinux/bios/mbr.bin of=/dev/sdh # use mbr.bin from syslinux package mkdir /tmp/iso /tmp/usb mount SW_DVD5_Win_Pro_7_64BIT.ISO /tmp/iso/ mount /dev/sdh1 /tmp/usb/ cp -rv /tmp/iso/* /tmp/usb/ umount /tmp/iso umount /tmp/usb
This is a nice web-ui for single kvm virt-hosts
I tried a lot of UIs, but this is so far the best opensource kvm web-ui, which is using libvirt for management.
Why is libvirt important?
It keeps your host open to integrate/migrate from/to other virt solutions, it is the one and only standard so far.
If you do not use libvirt, you have the alternative to use pure-qemu to run your VMs, which isn't really an alternative.
Proxmox is using pure qemu comands with own management solution and this is the reason that no-one ever has ever built a Proxmox management integration.
Good for Proxmox business, bad for comunity, so better go the libvirt way.
I am missing the integration of multiple KVM hosts, but hopefully this is not the latest realease of kimchi !
Thanks Kimchi Team to build this web-ui !!!
yum -y install epel-release deltarpm chronyd wget yum makecache yum -y update yum install libvirt-python libvirt libvirt-daemon-config-network qemu-kvm python-ethtool sos \ python-ipaddr nfs-utils iscsi-initiator-utils pyparted python-libguestfs libguestfs-tools novnc \ spice-html5 python-configobj python-magic python-paramiko python-pillow virt-top systemctl enable chronyd systemctl restart chronyd # firefox https://github.com/kimchi-project/kimchi/releases/latest yum -y install http://kimchi-project.github.io/gingerbase/downloads/latest/ginger-base.el7.centos.noarch.rpm \ http://kimchi-project.github.io/ginger/downloads/latest/ginger.el7.centos.noarch.rpm \ https://github.com/kimchi-project/wok/releases/download/2.5.0/wok-2.5.0-0.el7.centos.noarch.rpm \ https://github.com/kimchi-project/kimchi/releases/download/2.5.0/kimchi-2.5.0-0.el7.centos.noarch.rpm firewall-cmd --add-port 8001/tcp --permanent systemctl enable wokd nginx systemctl restart wokd nginx firewalld
Now you can reach the KVM virt UI at:
I searched for and did not find a answer, so here is how I did.
In vCAC6, BG-Manager were able to do this.
In vRA7, it has to be done on deployment level and you will need to entitle the "deployment action" in order to get that working.
Below you find my notes to install collectd on CentOS 7
yum install epel-release yum install -y collectd collectd-rrdtool rrdtool collectd-web httpd yum search collectd yum -y install collectd-disk collectd-virt # you may skip that step systemctl enable httpd collectd cat /etc/httpd/conf.d/collectd.conf sed -i 's/# Require all granted/Require all granted/g;s/Require local/# Require local/g' /etc/httpd/conf.d/collectd.conf systemctl restart httpd collectd
Now, you can access collectd by pointing to: http://servername/collectd/bin/index.cgi