I'm investigating how to setup KVM so I can run VMs without having to use VirtualBox or VMware, or etc.
All the HOWTOs I see tell you to disable NM.
I use NM to manage VPN clients that I use for remote access to my office, among other places.
How would I manage those VPN clients if I didn't use NM? I haven't found any commands that appear to be suited to that purpose.
thanks!
On 28.10.2013 17:52, Fred Smith wrote:
I'm investigating how to setup KVM so I can run VMs without having to use VirtualBox or VMware, or etc.
All the HOWTOs I see tell you to disable NM.
I use NM to manage VPN clients that I use for remote access to my office, among other places.
How would I manage those VPN clients if I didn't use NM? I haven't found any commands that appear to be suited to that purpose.
thanks!
Hi,
KVM/libvirt works just fine with NM enabled here. Never had a problem. Just "yum install qemu-kvm libvirt virt-manager", start libvirtd and fire-up virt-manager, you're set!
HTH Lucian
On Mon, Oct 28, 2013 at 11:05 AM, Nux! nux@li.nux.ro wrote:
On 28.10.2013 17:52, Fred Smith wrote:
I'm investigating how to setup KVM so I can run VMs without having to use VirtualBox or VMware, or etc.
All the HOWTOs I see tell you to disable NM.
I use NM to manage VPN clients that I use for remote access to my office, among other places.
How would I manage those VPN clients if I didn't use NM? I haven't found any commands that appear to be suited to that purpose.
thanks!
Hi,
KVM/libvirt works just fine with NM enabled here. Never had a problem. Just "yum install qemu-kvm libvirt virt-manager", start libvirtd and fire-up virt-manager, you're set!
If you are going to use bridged network, please see:
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/...
Akemi
On Mon, Oct 28, 2013 at 11:16:18AM -0700, Akemi Yagi wrote:
On Mon, Oct 28, 2013 at 11:05 AM, Nux! nux@li.nux.ro wrote:
On 28.10.2013 17:52, Fred Smith wrote:
I'm investigating how to setup KVM so I can run VMs without having to use VirtualBox or VMware, or etc.
All the HOWTOs I see tell you to disable NM.
I use NM to manage VPN clients that I use for remote access to my office, among other places.
How would I manage those VPN clients if I didn't use NM? I haven't found any commands that appear to be suited to that purpose.
thanks!
Hi,
KVM/libvirt works just fine with NM enabled here. Never had a problem. Just "yum install qemu-kvm libvirt virt-manager", start libvirtd and fire-up virt-manager, you're set!
If you are going to use bridged network, please see:
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/...
thanks, I'll go take a look. As far as I can tell from all the aforementioned HOWTOs, bridged is the way to do it?? none of 'em says anything about doing it any other way. what am I overlooking in my ignorance?
On 10/28/2013 11:23 AM, Fred Smith wrote:
thanks, I'll go take a look. As far as I can tell from all the aforementioned HOWTOs, bridged is the way to do it?? none of 'em says anything about doing it any other way. what am I overlooking in my ignorance?
bridged is appropriate if you want to see your VM's virtual NIC's appear on your local network such that the VM's get their own IP addresses that are reachable by other LAN hosts.
On 28.10.2013 18:23, Fred Smith wrote:
thanks, I'll go take a look. As far as I can tell from all the aforementioned HOWTOs, bridged is the way to do it?? none of 'em says anything about doing it any other way. what am I overlooking in my ignorance?
If all you want is just to have a local VM and no special requirements, libvirt provides you with a virtual bridge (virbr0) that is NAT-ed to your public uplink. All VMs are by default connected to this virtual bridge, unless you specify otherwise and given an IP from the 192.168.122.0/24 range; your host machine will be 192.168.122.1.
All of the above happens autmagically once you start libvirtd. If you want to have the VM on the same public network as the host then indeed you need to configure a bridge manully and connect both your public interface (eth0) and your virtual machine's interface (vnetX) to it.
HTH
On Mon, Oct 28, 2013 at 2:05 PM, Nux! nux@li.nux.ro wrote:
On 28.10.2013 17:52, Fred Smith wrote:
I'm investigating how to setup KVM so I can run VMs without having to use VirtualBox or VMware, or etc.
All the HOWTOs I see tell you to disable NM.
There is no reason to disable NM entirely.
But you can disable NM per interface with: NM_CONTROLLED="no"
I use NM to manage VPN clients that I use for remote access to my office, among other places.
How would I manage those VPN clients if I didn't use NM? I haven't found any commands that appear to be suited to that purpose.
thanks!
Hi,
KVM/libvirt works just fine with NM enabled here. Never had a problem.
I've seen it is common practice to disable NM on bridge and other interfaces at times.
I expect this excerpt from [0] is why I've seen NM disabled "per interface" in various write-ups. And in my case I never needed or wanted NM fiddling with most interfaces on my headless servers. ;)
- The NM_CONTROLLED=no should be added to the Ethernet interface to prevent *NetworkManager* from altering the file. It can also be added to the bridge configuration file in case future versions of *NetworkManager* support bridge configuration.
[0] https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/...
Just "yum install qemu-kvm libvirt virt-manager", start libvirtd and fire-up virt-manager, you're set!
HTH Lucian
-- Sent from the Delta quadrant using Borg technology!
Nux! www.nux.ro _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Mon, Oct 28, 2013 at 07:41:59PM -0400, SilverTip257 wrote:
On Mon, Oct 28, 2013 at 2:05 PM, Nux! nux@li.nux.ro wrote:
On 28.10.2013 17:52, Fred Smith wrote:
I'm investigating how to setup KVM so I can run VMs without having to use VirtualBox or VMware, or etc.
All the HOWTOs I see tell you to disable NM.
There is no reason to disable NM entirely.
But you can disable NM per interface with: NM_CONTROLLED="no"
Yes, so I've learned today. thanks for the tip though.
I've seen it is common practice to disable NM on bridge and other interfaces at times.
I expect this excerpt from [0] is why I've seen NM disabled "per interface" in various write-ups. And in my case I never needed or wanted NM fiddling with most interfaces on my headless servers. ;)
Sure. makes sense. But I'm hoping to use this on my main (home) desktop machine, so I need to still have desktop-likke services available.
- The NM_CONTROLLED=no should be added to the Ethernet interface to
prevent *NetworkManager* from altering the file. It can also be added to the bridge configuration file in case future versions of *NetworkManager* support bridge configuration.
thanks for the info!
-
Akemi Yagi -
Fred Smith -
John R Pierce -
Nux! -
SilverTip257