[clug] Seeking FOSS Hypervisor and Management GUI

[George at Clug]

    Sam, thanks for your comments. If I suspect that I will need more
disk space later, then I use LVM too, especially for VMs where
everything is virtual anyway.

One day I would like to learn what happens to a physical drive LVM
configuration if one of the drives die. Do you loose the lot, or
somehow only loose the data that is on the dead drive, but how does
that affect the directory listings, files, etc.  How do you know what
was lost and what was not?

As I am currently still using/trailing KVM with Virt-Manager and
command line snapshots (until CentOS or Debian have packages for
Virt-Manager versions that support snapshots) for my virtualisation
host, last night I investigated Windows 10 as a VM on KVM.  This
worked surprisingly well. After installation (over the top of a
previous Win8 Enterprise trial that I used to test Windows VM on KVM)
I used RDP to access the image from a Windows 7 PC that has three
monitors. Windows 10 (via RDP) instantly had three screens,
performance was quite good. I could not watch full screen video from
youtube on a 24" monitor but watching video in its original screen
size worked very well, including sound.

Soon I will get back to testing command line snapshots further.

If you are using Virtualisation or containers, what Guest OS's or
processes and purpose do you use virtualisation for.  File,
Minecraft, Mail, video conferencing, and web server are the tasks that
my servers perform.



At Thursday, 02-10-2014 on 21:00 Sam Couter wrote:


I use LVM when partitioning virtual or physical servers so I can grow
them on demand. Or even shrink them on occasion.


Partitioning is definitely a subject all of its own. You will find
plenty of proponents of the "one big disk" approach you have taken.
It's easily the simplest approach. If it works for you, stick with it.