Re: Can't get Virtual Network Setup in KVM

2010-05-04 Thread Jerry Feldman
On 05/03/2010 06:02 PM, Jim wrote: > 1. Installing KVM, In these instructions under # 1 have been completed, > Network setup is problem. > > Fedora 12 KVM Host: > > First check if your CPU supports hardware virtualization - if this is > the case, the command > egrep '(vmx|svm)' --color=always /p

Re: Can't get Virtual Network Setup in KVM

2010-05-03 Thread Jim
On 05/03/2010 07:08 PM, Tom Horsley wrote: > On Mon, 03 May 2010 18:57:23 -0400 > Jim wrote: > > >> Whereis Virt Manager ? >> I look for it but could not find. >> > I's /usr/bin/virt-manager on my system, perhaps you don't > have the entire virtualization program group installed? > > Also

Re: Can't get Virtual Network Setup in KVM

2010-05-03 Thread Tom Horsley
On Mon, 03 May 2010 18:57:23 -0400 Jim wrote: > Whereis Virt Manager ? > I look for it but could not find. I's /usr/bin/virt-manager on my system, perhaps you don't have the entire virtualization program group installed? Also, the name virbr0 may be out of date. I just looked on my system, (wher

Re: Can't get Virtual Network Setup in KVM

2010-05-03 Thread Jim
On 05/03/2010 06:10 PM, Tom Horsley wrote: > On Mon, 03 May 2010 18:02:45 -0400 > Jim wrote: > > >> But i'm not getting a; >> >> virbr0 >> > If you use virt-manager to install your VMs, you need > to look in the ">Advanced" area of the final wizard > screen and select bridge networking. I

Re: Can't get Virtual Network Setup in KVM

2010-05-03 Thread Tom Horsley
On Mon, 03 May 2010 18:02:45 -0400 Jim wrote: > But i'm not getting a; > > virbr0 If you use virt-manager to install your VMs, you need to look in the ">Advanced" area of the final wizard screen and select bridge networking. I don't think it will create the virbr0 till some machine actually need

Can't get Virtual Network Setup in KVM

2010-05-03 Thread Jim
1. Installing KVM, In these instructions under # 1 have been completed, Network setup is problem. Fedora 12 KVM Host: First check if your CPU supports hardware virtualization - if this is the case, the command egrep '(vmx|svm)' --color=always /proc/cpuinfo should display something, e.g. like t