Page 1 of 2
which virtualiser ?
Posted: 2019/05/21 09:41:09
by GioMBG
Hi All,
I state that it is the first time that I try to set this type of configuration.
I have to virtualize on a machine with 64 Gbytes of RAM and with a hard disk SSD about 25 linux operating systems, if possible...
questions:
which virtualizer should I have to install ?
once the virtualizer and operating systems are installed and configured I need to be able to enter each virtualized system through some program ( which I don't know ) that gives me the possibility to graphically see the virtualized desk tops in order to operate as if I were on my stand alone desktop.
thanks
Gio
Re: which virtualiser ?
Posted: 2019/05/21 12:15:51
by jlehtone
Code: Select all
yum groups install virtualization-host-environment
should install most packages for libvirt that allows KVM virtualization with relative ease.
Re: which virtualiser ?
Posted: 2019/05/21 16:34:11
by hunter86_bg
Also, in order to manage you can use cockpit .
Re: which virtualiser ?
Posted: 2019/05/21 21:50:06
by GioMBG
really thanks 2 All
I will return once installed / tested all
thanks again
Gio
Re: which virtualiser ?
Posted: 2019/06/17 12:11:45
by GioMBG
Hi All,
returned for KVM support.
I've found this guide to install KVM on my CentOS :
https://www.cyberciti.biz/faq/how-to-in ... ss-server/
in this guide at the section :
Step 3: Configure bridged networking
Code: Select all
[root@swinger network-scripts]# brctl show
bridge name bridge id STP enabled interfaces
virbr0 8000.525400118de5 yes virbr0-nic
Code: Select all
[root@swinger network-scripts]# virsh net-list
Nome Stato Avvio automatico Persistent
----------------------------------------------------------
default attivo yes yes
Code: Select all
[root@swinger network-scripts]# virsh net-dumpxml default
<network>
<name>default</name>
<uuid>54b3dc54-71fa-4a80-a440-5f29da9a3f76</uuid>
<forward mode='nat'>
<nat>
<port start='1024' end='65535'/>
</nat>
</forward>
<bridge name='virbr0' stp='on' delay='0'/>
<mac address='52:54:00:11:8d:e5'/>
<ip address='192.168.122.1' netmask='255.255.255.0'>
<dhcp>
<range start='192.168.122.2' end='192.168.122.254'/>
</dhcp>
</ip>
</network>
[root@swinger network-scripts]#
so If you want your VMs avilable to other servers on your LAN, setup a a network bridge on the server that connected to the your LAN. Update your nic config file such as ifcfg-enp3s0 or em1:
but if I try to :
Code: Select all
cat /etc/sysconfig/network-scripts/enp3s0
I don't found any file to make VMs avilable to other servers on my LAN...
suggestions ?
thanks
Gio
Re: which virtualiser ?
Posted: 2019/06/18 03:48:46
by hunter86_bg
Hi Gio,
I guess you are using NetworkManager.service
Just run the following to get you NIC's settings.
You can use the following link if you need more info:
https://access.redhat.com/documentation ... uide/index
Re: which virtualiser ?
Posted: 2019/06/18 17:09:37
by GioMBG
Hi hunter86_bg,
Code: Select all
[root@CentOS-76-64-minimal boot]# nmcli con show virbr0
connection.id: virbr0
connection.uuid: 82eeae77-9615-4004-8b2f-8ba868130022
connection.stable-id: --
connection.type: bridge
connection.interface-name: virbr0
connection.autoconnect: no
connection.autoconnect-priority: 0
connection.autoconnect-retries: -1 (default)
connection.auth-retries: -1
connection.timestamp: 1560877103
connection.read-only: no
connection.permissions: --
connection.zone: --
connection.master: --
connection.slave-type: --
connection.autoconnect-slaves: -1 (default)
connection.secondaries: --
connection.gateway-ping-timeout: 0
connection.metered: sconosciuto
connection.lldp: default
connection.mdns: -1 (default)
ipv4.method: manual
ipv4.dns: --
ipv4.dns-search: --
ipv4.dns-options: ""
ipv4.dns-priority: 100
ipv4.addresses: 192.168.122.1/24
ipv4.gateway: --
ipv4.routes: --
ipv4.route-metric: -1
ipv4.route-table: 0 (unspec)
ipv4.ignore-auto-routes: no
ipv4.ignore-auto-dns: no
ipv4.dhcp-client-id: --
ipv4.dhcp-timeout: 0 (default)
ipv4.dhcp-send-hostname: sì
ipv4.dhcp-hostname: --
ipv4.dhcp-fqdn: --
ipv4.never-default: no
ipv4.may-fail: sì
ipv4.dad-timeout: -1 (default)
ipv6.method: ignore
ipv6.dns: --
ipv6.dns-search: --
ipv6.dns-options: ""
ipv6.dns-priority: 100
ipv6.addresses: --
ipv6.gateway: --
ipv6.routes: --
ipv6.route-metric: -1
ipv6.route-table: 0 (unspec)
ipv6.ignore-auto-routes: no
ipv6.ignore-auto-dns: no
ipv6.never-default: no
ipv6.may-fail: sì
ipv6.ip6-privacy: -1 (unknown)
ipv6.addr-gen-mode: stable-privacy
ipv6.dhcp-duid: --
ipv6.dhcp-send-hostname: sì
ipv6.dhcp-hostname: --
ipv6.token: --
bridge.mac-address: --
bridge.stp: sì
bridge.priority: 32768
bridge.forward-delay: 2
bridge.hello-time: 2
bridge.max-age: 20
bridge.ageing-time: 300
bridge.group-forward-mask: 0
bridge.multicast-snooping: sì
proxy.method: none
proxy.browser-only: no
proxy.pac-url: --
proxy.pac-script: --
GENERAL.NAME: virbr0
GENERAL.UUID: 82eeae77-9615-4004-8b2f-8ba868130022
GENERAL.DEVICES: virbr0
GENERAL.STATE: attivata
GENERAL.DEFAULT: no
GENERAL.DEFAULT6: no
GENERAL.SPEC-OBJECT: --
GENERAL.VPN: no
GENERAL.DBUS-PATH: /org/freedesktop/NetworkManager/ActiveConnection/2
GENERAL.CON-PATH: /org/freedesktop/NetworkManager/Settings/2
GENERAL.ZONE: --
GENERAL.MASTER-PATH: --
IP4.ADDRESS[1]: 192.168.122.1/24
IP4.GATEWAY: --
IP4.ROUTE[1]: dst = 192.168.122.0/24, nh = 0.0.0.0, mt = 0
IP6.GATEWAY: --
lines 49-90/90 (END)
Code: Select all
[root@CentOS-76-64-minimal boot]# brctl show
bridge name bridge id STP enabled interfaces
virbr0 8000.52540007fd99 yes virbr0-nic
vnet0
vnet1
Code: Select all
[root@CentOS-76-64-minimal boot]# virsh net-list
Nome Stato Avvio automatico Persistent
----------------------------------------------------------
default attivo yes yes
Code: Select all
[root@CentOS-76-64-minimal boot]# virsh list
Id Nome Stato
----------------------------------------------------
6 centos7 in esecuzione
7 centos71 in esecuzione
When I try to make a new Virtual Machine I receive :
Code: Select all
WARNING Grafica richiesta, ma DISPLAY non impostato. virt-viewer non in esecuzione.
WARNING Nessuna console da avviare per il guest. Per impostazione predefinita --wait -1
suggestions ?
thanks
Gio
Re: which virtualiser ?
Posted: 2019/06/18 22:02:00
by hunter86_bg
Your network will:
1. Not start on boot
connection.autoconnect: no
2. No DNS server set, nor a search directive:
ipv4.dns: --
ipv4.dns-search: --
3. Also, no gateway is available - so you will never reach the outside world:
ipv4.gateway: --
ipv4.routes: --
Why don't you let libvirt control your connectivity ?
Also, check the situation in cockpit - it' a graphical tool that is way easier than the cli.
Re: which virtualiser ?
Posted: 2019/06/18 23:58:12
by GioMBG
Hi hunter86_bg,
first THANKS and look that I'm newbie in KVM and tools around...
I agree 100% that all my virtual machine have :
- to start on boot,
- need to have a DNS server set and maybe a search directive,
- an available gateway,
- also if you suggest that libvirt control my connectivity I would do so...
How I can fix these 4 points ?
cockpit installed on this test machine but where is user full ?
in this "KVM" ( not standalone ) hetzner machine or in my desktop ( standalone ) Fedora to manage the KVM ?
thanks again
Gio
Re: which virtualiser ?
Posted: 2019/06/19 04:12:36
by hunter86_bg
Cockpit was just a recommendation from a colleague.
I personally use virt-manager , but this package is only available in linux distributions - no windows variant.
In you position I would use KVM, allow it to create a bridge which then can be used for VMs to access the outside world.
This approach has drawbacks -> only host is allowed to access the VMs directly.
Another option is to make a bridge yourself (you have completed this step) and then configure it.
As the bridge is named virbr0, I suspect it was creates by libvirt - right?
Still, if you have experience with VmWare or Virtualbox - they both have a version for linux and you can go that way . It will be way simpler than preparing the KVM host.