@olivier said in KVM vs XenServer:

@scottalanmiller said in KVM vs XenServer:

@kuyaz said in KVM vs XenServer:

Can memory be shared also between VM?

That depends on the hypervisor. VMware ESXi can do this. It's an extremely limited feature and of little value. It's neat and good for things like VDI, typically, but not very useful for servers and there is a reason most platforms don't work towards adding it.

I concur. For most workloads, it's more a pain than a solution.

yes I just realize that my question is stupid for the RAM part 😄

== solved ==

I was looking at 2 different systems, CentOS-7 & Fedora 25.
Bridge networking behavior at the GUI is not the same on both.
F25 required some manual config. to add "br1"
0_1496255974864_nonic2.PNG

@msff-amman-Itofficer said in KVM Virtual Machine Manager: no keyboard:

@FATeknollogee

I mean password-less SSH login between the Virtt-Manager and the KVM host, but maybe you are using both on the same machine i guess, right ?

If that is the case this disregard passwordless SSH stuff

Yes, for now, same machine

Here is the option:

Thx, I will take a look at "Display Spice".

@scottalanmiller said in HTML5 management interface for KVM:

Calligra was always okay. Not great, but certainly not bad.

0_1495832467386_Screenshot from 2017-05-26 16-00-50.png

That is atrocious

@JaredBusch said in SELinux with KVM?:

@NerdyDad said in SELinux with KVM?:

@EddieJennings said in SELinux with KVM?:

@NerdyDad said in SELinux with KVM?:

Would you deploy ClamAV on the host of KVM?
Would you deploy SELinux on the host of KVM?

What little I've learned of SELinux, I thought it was something baked into CentOS. At least it seems to be for me.

It is but needs to be setup.

Umm, no. SELinux is installed and working by default. The only setup you do is for things that need more permissions than SELinux provides by default.

Right. SELinux is installed by default. Some tools aren't (like policycoreutils). Svirt by default handles MLS labels for KVM guests. You shouldnt have to do any work to get all of that functionality.

Factory Reset, Setup, Disable Hardware Checksum Offloading, Works Prefect.

@JaredBusch said in How do you setup KVM networking on a desktop or laptop:

@FATeknollogee said in How do you setup KVM networking on a desktop or laptop:

Any further updates here?

What is the "cleanest" method available so vm's can "talk" to the host?

I ended up just staying on macvtap. I never did any further troubleshooting.

0_1496240731940_upload-24668984-2bad-47a6-ad88-1a74591f736a

I only use this Windows 10 VM for occasional power email sessions in Outlook when organizing 5 accounts worth of email. Usually once a week.

You'll get better performance if you install the VirtIO drivers and use that instead of rtl8139. Whether you will notice it or not for that VM, idk.

But you learned something along the way. 😄

Registered.

KVM Networking was set to NAT not Routed 😞

I guess I am learning?........

First step - determine what it is that you want to be learning.

KVM with Virtmanager.
Centos latest is my preferred KVM host.
And Fedora LXDE Spin is my preferred Virt-Manager choice, I use it from inside Windows using Virtualbox.

Cause it resembles the old ESXi Philosophy with Vsphere C# client
And you can do whatever you want with it, and for free. Especially when you use virt IO drivers for network and disk, you get nearly identical bare metal speeds.

But sadly its lacking other tools to allow users to connect and use the VM, you will have to do this from inside the VM like RDP and VNC.

@scottalanmiller said in Best tool to manage Centos KVM ? + Guide:

@msff-amman-Itofficer said in Best tool to manage Centos KVM ? + Guide:

but in Windows environment (virt-viewer) they dont have ssh... so how can I resolve it?

Windows has had SSH for a while now. Both OpenSSH as a server and OpenSSH as a client, plus tools like Putty, too.

That doesn't help with virt-viewer though unless you're making a tunnel. I've never used virt-viewer on windows so I don't know if it has an option for keys.

We are using this, by the way. Just deployed one this past week or so.

A common option for small environments would be to simply include the driver package on a Windows SMB file share in a centrally accessible, read only folder that can be seen from each VM. Then just log into each VM and double click to update! Easy Peasy.

For larger environments, Group Policy will be the most common approach.