UPDATE as of 03/12/2020
Please be aware of some issues (bare metal)
on Penryn CPU's
https://bugs.launchpad.net/qemu/+bug/1866870
At least on Haswell's boxes bug doesn't show up.
END UPDATE
Performance appraisal has been done via attempt to set up Ubuntu 20.04 as KVM virtualization host installing Qemu && Libvirt per
https://computingforgeeks.com/install-kvm-hypervisor-on-ubuntu-focal-fossa/
at L1 and L2 levels. L2-Ubuntu 20.04 Guest is starting up Fedora 31 Server domain at Level 3. L1 and L2 guests got their XML profiles updated with <cpu mode='host-passthrough'> in virsh console of parent domains. Advanced system administration via virsh CLI is also shown on the last three snapshots. Following below is the set commands setting up KVM Hypervisor on Ubuntu 20.04 :-
$ sudo apt -y install qemu-kvm \
libvirt-daemon bridge-utils \
virtinst libvirt-daemon-system
$ sudo apt -y install virt-top libguestfs-tools \
libosinfo-bin qemu-system virt-manager
$ sudo modprobe vhost_net
$ lsmod | grep vhost
vhost_net 24576 0
tun 49152 1 vhost_net
vhost 49152 1 vhost_net
tap 28672 1 vhost_net
$ echo vhost_net | sudo tee -a /etc/modules
$ sudo shutdown -r now
At this point default network appears to be created
Shutdown L1 Guest Ubuntu 20.04 and update it's XML - profile via virsh console replacing 'host-model' by 'host-passthrough' afterwards restart Ubuntu 20.04 Guest via virsh console either via Virt-Manager. Notice that at L1 level Ubuntu creates libvirt's default network 192.168.123.0/24.
L1 - level Ubuntu 20.04 and every guest
in chain is configured in "virtio"mode for storage and network
L2 - level Ubuntu 20.04
Notice that at L2 level Ubuntu creates libvirt's default network 192.168.122.0/24, reverting back to traditional RH's format
L3 - level Fedora 31 Server
Advanced system administration via virsh console
Virsh CLI is clearly shown on snapshots below
Please be aware of some issues (bare metal)
on Penryn CPU's
https://bugs.launchpad.net/qemu/+bug/1866870
At least on Haswell's boxes bug doesn't show up.
END UPDATE
Performance appraisal has been done via attempt to set up Ubuntu 20.04 as KVM virtualization host installing Qemu && Libvirt per
https://computingforgeeks.com/install-kvm-hypervisor-on-ubuntu-focal-fossa/
at L1 and L2 levels. L2-Ubuntu 20.04 Guest is starting up Fedora 31 Server domain at Level 3. L1 and L2 guests got their XML profiles updated with <cpu mode='host-passthrough'> in virsh console of parent domains. Advanced system administration via virsh CLI is also shown on the last three snapshots. Following below is the set commands setting up KVM Hypervisor on Ubuntu 20.04 :-
$ sudo apt -y install qemu-kvm \
libvirt-daemon bridge-utils \
virtinst libvirt-daemon-system
$ sudo apt -y install virt-top libguestfs-tools \
libosinfo-bin qemu-system virt-manager
$ sudo modprobe vhost_net
$ lsmod | grep vhost
vhost_net 24576 0
tun 49152 1 vhost_net
vhost 49152 1 vhost_net
tap 28672 1 vhost_net
$ echo vhost_net | sudo tee -a /etc/modules
$ sudo shutdown -r now
At this point default network appears to be created
Shutdown L1 Guest Ubuntu 20.04 and update it's XML - profile via virsh console replacing 'host-model' by 'host-passthrough' afterwards restart Ubuntu 20.04 Guest via virsh console either via Virt-Manager. Notice that at L1 level Ubuntu creates libvirt's default network 192.168.123.0/24.
L1 - level Ubuntu 20.04 and every guest
in chain is configured in "virtio"mode for storage and network
L2 - level Ubuntu 20.04
Notice that at L2 level Ubuntu creates libvirt's default network 192.168.122.0/24, reverting back to traditional RH's format
L3 - level Fedora 31 Server
Advanced system administration via virsh console
Virsh CLI is clearly shown on snapshots below
No comments:
Post a Comment