Re: [CentOS-virt] Preferred method of provisioning VM images
Lars Kurth writes: > Hi all, > > following the discussion on about documentation, I was wondering whether > we need to look at a standard way in which we recommend how to provision > images for VMs. Am starting this with a Xen hat, but the discussion > should not be specific to this. There are a number of options, but all > have some trade-offs Let me wear the hat of the user. The major hurdles were network setup, installing something in a vm, and the chaotic state the documentation is in. I knew before I started that network setup would be a PITA because years ago, I set up a VM for someone who didn't have a 64bit system to compile a 64bit version of some software. The network setup being so ridiculously difficult has kept me from touching VMs ever again for years. It's just too difficult and not worth the effort unless you're really forced to do it. As a user, I'm used to get an ISO of an installer or of a life system, put that into a DVD drive or write it to an USB stick and to boot from that to do the installation. Why can't I do that with xen? > == #1 virt-install == > == #2 xen-tools == > == #3 virt-builder (http://libguestfs.org/virt-builder.1.html) == > == #4 Cloud Image from Cloud Image SIG == I wouldn't want #4. I want to be able to just use the installer of whatever distribution I'm installing in a VM and a simple way of saying "run this in a VM and let me install". Or perhaps I merely want to run a life system in a VM to try it out, with network access. What easy way is there to do that? I haven't heared of #3. #2 and #1 lead to total confusion. Xen doesn't have any way to use an installer ISO to install a VM. The documentation is confusing because it lacks clarity and refers to many versions of xen at the same time which suggest to do things differently so that you don't know how you are supposed to do something. There is no documentation for centos about how to set up a VM. #2 and #1 use different ways and different formats of configuration files, and apparently #1 doesn't support everything #2 does and brings about an undesirable overhead while apparently being a good choice for users who also use other things than xen and don't want to learn different ways of managing VMs. When I use xen, I do not need #1, and it seems to make more sense to me to stick with #2. #2 needs clarity of documentation. I've got an installer ISO. The documentation needs to tell me straightforwardly what I need to do to get a VM running with this installer ISO. I don't care about #1--4 at that point. It's that simple. More details can be learned over time. Insofar the documentation needs to deal with different versions of xen, just split the documentation entirely. When I use version X, I do not want to read the documentation for versions A, B, C or Z. That's confusing and I have to ask myself all the time which part of what I'm reading might apply to the software I'm using, and that makes reading the documentation very painful. It's like you buy a new TV and it comes with 5 pages of documentation because the manufacturer of the TV mentions everything for every model of TV they ever manufactured, rather than documenting no more than the TV you actually bought. Trying to figure out how to switch to a different channel or how to increase the volume takes at least two days each. For example: http://wiki.xen.org/wiki/Credit_Scheduler: "It is now the default scheduler in the xen-unstable trunk." So is it the default in the version I'm using or what? "The SEDF and BVT schedulers are still optionally available but the plan of record is for them to be phased out and eventually removed." What are those and have they been removed in the version I'm using? But then, it probably doesn't matter what they are because they might have been removed anyway. So what is this information supposed to tell me?? "A domain with a weight of 512 will get twice as much CPU as a domain with a weight of 256 on a contended host. Legal weights range from 1 to 65535 and the default is 256." Where would I change this default? What happens when I set a weight of 100 or of 33? I can only guess that it might be rounded up or down to something like 128 or 64 or 32 or 64. Or perhaps actually floating point math is employed to compute the relations of the different weights? Probably not ... "Schedule Rate Limiting (added in Xen 4.2)" That doesn't belong there. It needs to go into the documentation for that particular version of xen. "Timeslice (added in Xen 4.2) [...] # xl sched-credit -t [n]" dito "Usage The xm sched-credit command may be used to tune the per VM guest scheduler parameters." So what am I supposed to use? xm or xl? Or something else, maybe virsh? I always admire the documentation exim has ... As to your original question: > I was wondering whether we need to look at a standard way in which we > recommend how to provision images for VMs. I'd suggest to start with splittin
Re: [CentOS-virt] Are xen and centos incompatible?
Konrad Rzeszutek Wilk writes: > On Tue, Jun 10, 2014 at 06:47:20PM +0200, lee wrote: >> Konrad Rzeszutek Wilk writes: >> >> > On Tue, Jun 10, 2014 at 04:44:23AM +0200, lee wrote: >> >>> Konrad Rzeszutek Wilk writes: >> >> > >> >> > The device should be visible in the dom0 - even when it is for >> >> > passthrough. >> >> >> >> Why should it be visible when it's hidden? >> > >> > The 'hide' part is to hide it from the device drivers in the initial >> > domain - dom0. That is so that they will not try to use it - as we >> > plan to pass them to a guest. We need it in the dom0 to do admin type >> > work - FLR it, etc. >> >> With Debian, it's not visible in dom0 when the passthrough works. >> That's how I found out that it does work to begin with, and it makes >> sense to me. > > That is a surprise. If you do 'lspci' in your dom0 do you see > the device (06:00.0)? Lspci still shows it, and the device (eth1) is invisible. >> What does FLR mean? And how do you do something with a device for which >> no drivers are loaded? I'd find it rather unusual to have a device >> without drivers and even be able to use it; such devices usually don't >> show up. > > Function Level Reset. > > You pass the device to a guest so it can load the drivers and the initial > domain (dom0) won't use it. Hm, xen kinda makes the cpus and their power management invisible, too: root@heimdall:~# xenpm get-cpufreq-para [CPU0] failed to get cpufreq parameter [...] root@heimdall:~# xenpm get-cpufreq-states root@heimdall:~# So I guess it could as well make it so that lspci doesn't show passed-out devices. BTW, getting some info in dmesg might be nice, like a message saying "xen-pciback: device 06:00.0 can be passed through to guests". We could actually see right away if it did work or not. That a device disappears isn't too great as indication, especially not when lspci still lists it. Of course, you could use the command (which I don't remember) to show devices that can be passed through. But that may just work as well as 'xenpm get-cpufreq-states': Apparently, there aren't any CPUs ... -- Knowledge is volatile and fluid. Software is power. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Finally switching from Xen to KVM - question about networking
On 6/11/2014 7:27 PM, Steve Campbell wrote: > On 6/11/2014 1:15 PM, Steve Campbell wrote: >> On 6/11/2014 10:56 AM, Zoltan Frombach wrote: >>> On 6/11/2014 4:44 PM, Steve Campbell wrote: On 6/11/2014 10:13 AM, Zoltan Frombach wrote: > On 6/11/2014 4:10 PM, Steve Campbell wrote: >> On 6/11/2014 10:03 AM, Zoltan Frombach wrote: >>> On 6/11/2014 3:50 PM, Steve Campbell wrote: On 6/10/2014 4:00 PM, Zoltan Frombach wrote: > On 6/10/2014 9:51 PM, Steve Campbell wrote: >> On 6/10/2014 3:38 PM, Zoltan Frombach wrote: >>> On 6/10/2014 9:27 PM, Steve Campbell wrote: On 6/10/2014 3:09 PM, Zoltan Frombach wrote: > Steve, > > Try the following config. > > On your host: > > /etc/sysconfig/network-scripts/ifcfg-eth0: > > DEVICE=eth0 > BOOTPROTO=none > ONBOOT=yes > NM_CONTROLLED=no > TYPE=Ethernet > HWADDR=xx:xx:xx:xx:xx:xx<- put your physical NIC's MAC > address > here > BRIDGE=br0 > USERCTL=no > IPV6INIT=no > IPV6_AUTOCONF=no > > > /etc/sysconfig/network-scripts/ifcfg-br0: > > DEVICE=br0 > BOOTPROTO=static > ONBOOT=yes > NM_CONTROLLED=no > TYPE=Bridge > IPADDR=10.0.5.16 > NETMASK=255.255.255.0 <- you may need to adjust this to your > network > GATEWAY=10.0.5.1 > DNS1=8.8.8.8 > DNS2=8.8.4.4 > PEERDNS=yes > DELAY=0 > STP=off > USERCTL=no > IPV6INIT=no > IPV6_AUTOCONF=no > > > Restart networking on the host. > > Then inside you VM: > > /etc/sysconfig/network-scripts/ifcfg-eth0: > > DEVICE=eth0 > BOOTPROTO=static > ONBOOT=yes > NM_CONTROLLED=no > TYPE=Ethernet > HWADDR=xx:xx:xx:xx:xx:xx<- it must be a unique MAC address > for > your VM > IPADDR=10.0.5.17 > NETMASK=255.255.255.0 <- you may need to adjust this to > your > network > GATEWAY=10.0.5.1 > DNS1=8.8.8.8 > DNS2=8.8.4.4 > PEERDNS=yes > USERCTL=no > IPV6INIT=no > IPV6_AUTOCONF=no > > > Then in Virtual Machine Manager make sure that your VM's NIC is > connected to the br0 bridge, like this: > > Network Source: Specify shared device name > Bridge Name: br0 > > > > On 6/10/2014 8:16 PM, Steve Campbell wrote: >> On 6/10/2014 12:43 PM, Digimer wrote: >>> On 10/06/14 12:38 PM, Steve Campbell wrote: On 6/10/2014 12:05 PM, Digimer wrote: > On 10/06/14 11:46 AM, Steve Campbell wrote: >> On 6/10/2014 10:46 AM, Digimer wrote: >>> On 10/06/14 10:03 AM, Steve Campbell wrote: I had so much trouble putting Centos 6 guest VMs on a Centos 5 host that I finally switched to a Centos 6 host. I've not needed more that test VMs, so I've used Virtual Machine Manager on the old system, which worked pretty well, so I decided to create my first KVM guest machine. I noticed when I created it, I only had the options of NAT for my network interface, so I used that (obvious). Well, after starting the VM, I find I don't have connectivity with that interface. Reading, I find examples where I need to create bridges perhaps. Xen did most of this for me, so it's a little new to me. Can anyone throw me a clue, please? steve campbell >>> Setting up a bridge is not that hard, and it will give >>> your VMs >>> direct >>> access to the outside world, and host <-> VM access just >>> fine as >>> well. >>> >>
Re: [CentOS-virt] Finally switching from Xen to KVM - question about networking
On 6/11/2014 1:15 PM, Steve Campbell wrote: > On 6/11/2014 10:56 AM, Zoltan Frombach wrote: >> On 6/11/2014 4:44 PM, Steve Campbell wrote: >>> On 6/11/2014 10:13 AM, Zoltan Frombach wrote: On 6/11/2014 4:10 PM, Steve Campbell wrote: > On 6/11/2014 10:03 AM, Zoltan Frombach wrote: >> On 6/11/2014 3:50 PM, Steve Campbell wrote: >>> On 6/10/2014 4:00 PM, Zoltan Frombach wrote: On 6/10/2014 9:51 PM, Steve Campbell wrote: > On 6/10/2014 3:38 PM, Zoltan Frombach wrote: >> On 6/10/2014 9:27 PM, Steve Campbell wrote: >>> On 6/10/2014 3:09 PM, Zoltan Frombach wrote: Steve, Try the following config. On your host: /etc/sysconfig/network-scripts/ifcfg-eth0: DEVICE=eth0 BOOTPROTO=none ONBOOT=yes NM_CONTROLLED=no TYPE=Ethernet HWADDR=xx:xx:xx:xx:xx:xx<- put your physical NIC's MAC address here BRIDGE=br0 USERCTL=no IPV6INIT=no IPV6_AUTOCONF=no /etc/sysconfig/network-scripts/ifcfg-br0: DEVICE=br0 BOOTPROTO=static ONBOOT=yes NM_CONTROLLED=no TYPE=Bridge IPADDR=10.0.5.16 NETMASK=255.255.255.0 <- you may need to adjust this to your network GATEWAY=10.0.5.1 DNS1=8.8.8.8 DNS2=8.8.4.4 PEERDNS=yes DELAY=0 STP=off USERCTL=no IPV6INIT=no IPV6_AUTOCONF=no Restart networking on the host. Then inside you VM: /etc/sysconfig/network-scripts/ifcfg-eth0: DEVICE=eth0 BOOTPROTO=static ONBOOT=yes NM_CONTROLLED=no TYPE=Ethernet HWADDR=xx:xx:xx:xx:xx:xx<- it must be a unique MAC address for your VM IPADDR=10.0.5.17 NETMASK=255.255.255.0 <- you may need to adjust this to your network GATEWAY=10.0.5.1 DNS1=8.8.8.8 DNS2=8.8.4.4 PEERDNS=yes USERCTL=no IPV6INIT=no IPV6_AUTOCONF=no Then in Virtual Machine Manager make sure that your VM's NIC is connected to the br0 bridge, like this: Network Source: Specify shared device name Bridge Name: br0 On 6/10/2014 8:16 PM, Steve Campbell wrote: > On 6/10/2014 12:43 PM, Digimer wrote: >> On 10/06/14 12:38 PM, Steve Campbell wrote: >>> On 6/10/2014 12:05 PM, Digimer wrote: On 10/06/14 11:46 AM, Steve Campbell wrote: > On 6/10/2014 10:46 AM, Digimer wrote: >> On 10/06/14 10:03 AM, Steve Campbell wrote: >>> I had so much trouble putting Centos 6 guest VMs on a >>> Centos 5 >>> host >>> that >>> I finally switched to a Centos 6 host. >>> >>> I've not needed more that test VMs, so I've used Virtual >>> Machine >>> Manager >>> on the old system, which worked pretty well, so I >>> decided to >>> create my >>> first KVM guest machine. I noticed when I created it, I >>> only >>> had the >>> options of NAT for my network interface, so I used that >>> (obvious). >>> >>> Well, after starting the VM, I find I don't have >>> connectivity >>> with >>> that >>> interface. Reading, I find examples where I need to >>> create >>> bridges >>> perhaps. Xen did most of this for me, so it's a little >>> new to >>> me. >>> >>> Can anyone throw me a clue, please? >>> >>> steve campbell >> Setting up a bridge is not that hard, and it will give >> your VMs >> direct >> access to the outside world, and host <-> VM access just >> fine as >> well. >> >> Here is a link showing how to setup a bridge connected >> to a >> bond >> device. Ignore the bond and pretend it is a straight ethX >
Re: [CentOS-virt] Finally switching from Xen to KVM - question about networking
On 6/11/2014 10:56 AM, Zoltan Frombach wrote: > > On 6/11/2014 4:44 PM, Steve Campbell wrote: >> On 6/11/2014 10:13 AM, Zoltan Frombach wrote: >>> On 6/11/2014 4:10 PM, Steve Campbell wrote: On 6/11/2014 10:03 AM, Zoltan Frombach wrote: > On 6/11/2014 3:50 PM, Steve Campbell wrote: >> On 6/10/2014 4:00 PM, Zoltan Frombach wrote: >>> On 6/10/2014 9:51 PM, Steve Campbell wrote: On 6/10/2014 3:38 PM, Zoltan Frombach wrote: > On 6/10/2014 9:27 PM, Steve Campbell wrote: >> On 6/10/2014 3:09 PM, Zoltan Frombach wrote: >>> Steve, >>> >>> Try the following config. >>> >>> On your host: >>> >>> /etc/sysconfig/network-scripts/ifcfg-eth0: >>> >>> DEVICE=eth0 >>> BOOTPROTO=none >>> ONBOOT=yes >>> NM_CONTROLLED=no >>> TYPE=Ethernet >>> HWADDR=xx:xx:xx:xx:xx:xx<- put your physical NIC's MAC >>> address >>> here >>> BRIDGE=br0 >>> USERCTL=no >>> IPV6INIT=no >>> IPV6_AUTOCONF=no >>> >>> >>> /etc/sysconfig/network-scripts/ifcfg-br0: >>> >>> DEVICE=br0 >>> BOOTPROTO=static >>> ONBOOT=yes >>> NM_CONTROLLED=no >>> TYPE=Bridge >>> IPADDR=10.0.5.16 >>> NETMASK=255.255.255.0 <- you may need to adjust this to your >>> network >>> GATEWAY=10.0.5.1 >>> DNS1=8.8.8.8 >>> DNS2=8.8.4.4 >>> PEERDNS=yes >>> DELAY=0 >>> STP=off >>> USERCTL=no >>> IPV6INIT=no >>> IPV6_AUTOCONF=no >>> >>> >>> Restart networking on the host. >>> >>> Then inside you VM: >>> >>> /etc/sysconfig/network-scripts/ifcfg-eth0: >>> >>> DEVICE=eth0 >>> BOOTPROTO=static >>> ONBOOT=yes >>> NM_CONTROLLED=no >>> TYPE=Ethernet >>> HWADDR=xx:xx:xx:xx:xx:xx<- it must be a unique MAC address >>> for >>> your VM >>> IPADDR=10.0.5.17 >>> NETMASK=255.255.255.0 <- you may need to adjust this to >>> your >>> network >>> GATEWAY=10.0.5.1 >>> DNS1=8.8.8.8 >>> DNS2=8.8.4.4 >>> PEERDNS=yes >>> USERCTL=no >>> IPV6INIT=no >>> IPV6_AUTOCONF=no >>> >>> >>> Then in Virtual Machine Manager make sure that your VM's NIC is >>> connected to the br0 bridge, like this: >>> >>> Network Source: Specify shared device name >>>Bridge Name: br0 >>> >>> >>> >>> On 6/10/2014 8:16 PM, Steve Campbell wrote: On 6/10/2014 12:43 PM, Digimer wrote: > On 10/06/14 12:38 PM, Steve Campbell wrote: >> On 6/10/2014 12:05 PM, Digimer wrote: >>> On 10/06/14 11:46 AM, Steve Campbell wrote: On 6/10/2014 10:46 AM, Digimer wrote: > On 10/06/14 10:03 AM, Steve Campbell wrote: >> I had so much trouble putting Centos 6 guest VMs on a >> Centos 5 >> host >> that >> I finally switched to a Centos 6 host. >> >> I've not needed more that test VMs, so I've used Virtual >> Machine >> Manager >> on the old system, which worked pretty well, so I >> decided to >> create my >> first KVM guest machine. I noticed when I created it, I >> only >> had the >> options of NAT for my network interface, so I used that >> (obvious). >> >> Well, after starting the VM, I find I don't have >> connectivity >> with >> that >> interface. Reading, I find examples where I need to >> create >> bridges >> perhaps. Xen did most of this for me, so it's a little >> new to >> me. >> >> Can anyone throw me a clue, please? >> >> steve campbell > Setting up a bridge is not that hard, and it will give > your VMs > direct > access to the outside world, and host <-> VM access just > fine as > well. > > Here is a link showing how to setup a bridge connected > to a > bond > device. Ignore the bond and pretend it is a straight ethX > device: > > https://alteeve.ca/w/AN!Cluster_Tutorial_2#Configuring_our_Bridge.2C_Bonds_and_Interfaces > >
Re: [CentOS-virt] Finally switching from Xen to KVM - question about networking
On 6/11/2014 4:44 PM, Steve Campbell wrote: > On 6/11/2014 10:13 AM, Zoltan Frombach wrote: >> On 6/11/2014 4:10 PM, Steve Campbell wrote: >>> On 6/11/2014 10:03 AM, Zoltan Frombach wrote: On 6/11/2014 3:50 PM, Steve Campbell wrote: > On 6/10/2014 4:00 PM, Zoltan Frombach wrote: >> On 6/10/2014 9:51 PM, Steve Campbell wrote: >>> On 6/10/2014 3:38 PM, Zoltan Frombach wrote: On 6/10/2014 9:27 PM, Steve Campbell wrote: > On 6/10/2014 3:09 PM, Zoltan Frombach wrote: >> Steve, >> >> Try the following config. >> >> On your host: >> >> /etc/sysconfig/network-scripts/ifcfg-eth0: >> >> DEVICE=eth0 >> BOOTPROTO=none >> ONBOOT=yes >> NM_CONTROLLED=no >> TYPE=Ethernet >> HWADDR=xx:xx:xx:xx:xx:xx<- put your physical NIC's MAC >> address >> here >> BRIDGE=br0 >> USERCTL=no >> IPV6INIT=no >> IPV6_AUTOCONF=no >> >> >> /etc/sysconfig/network-scripts/ifcfg-br0: >> >> DEVICE=br0 >> BOOTPROTO=static >> ONBOOT=yes >> NM_CONTROLLED=no >> TYPE=Bridge >> IPADDR=10.0.5.16 >> NETMASK=255.255.255.0 <- you may need to adjust this to your >> network >> GATEWAY=10.0.5.1 >> DNS1=8.8.8.8 >> DNS2=8.8.4.4 >> PEERDNS=yes >> DELAY=0 >> STP=off >> USERCTL=no >> IPV6INIT=no >> IPV6_AUTOCONF=no >> >> >> Restart networking on the host. >> >> Then inside you VM: >> >> /etc/sysconfig/network-scripts/ifcfg-eth0: >> >> DEVICE=eth0 >> BOOTPROTO=static >> ONBOOT=yes >> NM_CONTROLLED=no >> TYPE=Ethernet >> HWADDR=xx:xx:xx:xx:xx:xx<- it must be a unique MAC address >> for >> your VM >> IPADDR=10.0.5.17 >> NETMASK=255.255.255.0 <- you may need to adjust this to your >> network >> GATEWAY=10.0.5.1 >> DNS1=8.8.8.8 >> DNS2=8.8.4.4 >> PEERDNS=yes >> USERCTL=no >> IPV6INIT=no >> IPV6_AUTOCONF=no >> >> >> Then in Virtual Machine Manager make sure that your VM's NIC is >> connected to the br0 bridge, like this: >> >> Network Source: Specify shared device name >>Bridge Name: br0 >> >> >> >> On 6/10/2014 8:16 PM, Steve Campbell wrote: >>> On 6/10/2014 12:43 PM, Digimer wrote: On 10/06/14 12:38 PM, Steve Campbell wrote: > On 6/10/2014 12:05 PM, Digimer wrote: >> On 10/06/14 11:46 AM, Steve Campbell wrote: >>> On 6/10/2014 10:46 AM, Digimer wrote: On 10/06/14 10:03 AM, Steve Campbell wrote: > I had so much trouble putting Centos 6 guest VMs on a > Centos 5 > host > that > I finally switched to a Centos 6 host. > > I've not needed more that test VMs, so I've used Virtual > Machine > Manager > on the old system, which worked pretty well, so I > decided to > create my > first KVM guest machine. I noticed when I created it, I > only > had the > options of NAT for my network interface, so I used that > (obvious). > > Well, after starting the VM, I find I don't have > connectivity > with > that > interface. Reading, I find examples where I need to create > bridges > perhaps. Xen did most of this for me, so it's a little > new to > me. > > Can anyone throw me a clue, please? > > steve campbell Setting up a bridge is not that hard, and it will give your VMs direct access to the outside world, and host <-> VM access just fine as well. Here is a link showing how to setup a bridge connected to a bond device. Ignore the bond and pretend it is a straight ethX device: https://alteeve.ca/w/AN!Cluster_Tutorial_2#Configuring_our_Bridge.2C_Bonds_and_Interfaces >>> The host has a device named virbr0 that is installed during >>> system
Re: [CentOS-virt] Finally switching from Xen to KVM - question about networking
On 6/11/2014 10:13 AM, Zoltan Frombach wrote: > > On 6/11/2014 4:10 PM, Steve Campbell wrote: >> On 6/11/2014 10:03 AM, Zoltan Frombach wrote: >>> On 6/11/2014 3:50 PM, Steve Campbell wrote: On 6/10/2014 4:00 PM, Zoltan Frombach wrote: > On 6/10/2014 9:51 PM, Steve Campbell wrote: >> On 6/10/2014 3:38 PM, Zoltan Frombach wrote: >>> On 6/10/2014 9:27 PM, Steve Campbell wrote: On 6/10/2014 3:09 PM, Zoltan Frombach wrote: > Steve, > > Try the following config. > > On your host: > > /etc/sysconfig/network-scripts/ifcfg-eth0: > > DEVICE=eth0 > BOOTPROTO=none > ONBOOT=yes > NM_CONTROLLED=no > TYPE=Ethernet > HWADDR=xx:xx:xx:xx:xx:xx<- put your physical NIC's MAC > address > here > BRIDGE=br0 > USERCTL=no > IPV6INIT=no > IPV6_AUTOCONF=no > > > /etc/sysconfig/network-scripts/ifcfg-br0: > > DEVICE=br0 > BOOTPROTO=static > ONBOOT=yes > NM_CONTROLLED=no > TYPE=Bridge > IPADDR=10.0.5.16 > NETMASK=255.255.255.0 <- you may need to adjust this to your > network > GATEWAY=10.0.5.1 > DNS1=8.8.8.8 > DNS2=8.8.4.4 > PEERDNS=yes > DELAY=0 > STP=off > USERCTL=no > IPV6INIT=no > IPV6_AUTOCONF=no > > > Restart networking on the host. > > Then inside you VM: > > /etc/sysconfig/network-scripts/ifcfg-eth0: > > DEVICE=eth0 > BOOTPROTO=static > ONBOOT=yes > NM_CONTROLLED=no > TYPE=Ethernet > HWADDR=xx:xx:xx:xx:xx:xx<- it must be a unique MAC address > for > your VM > IPADDR=10.0.5.17 > NETMASK=255.255.255.0 <- you may need to adjust this to your > network > GATEWAY=10.0.5.1 > DNS1=8.8.8.8 > DNS2=8.8.4.4 > PEERDNS=yes > USERCTL=no > IPV6INIT=no > IPV6_AUTOCONF=no > > > Then in Virtual Machine Manager make sure that your VM's NIC is > connected to the br0 bridge, like this: > > Network Source: Specify shared device name > Bridge Name: br0 > > > > On 6/10/2014 8:16 PM, Steve Campbell wrote: >> On 6/10/2014 12:43 PM, Digimer wrote: >>> On 10/06/14 12:38 PM, Steve Campbell wrote: On 6/10/2014 12:05 PM, Digimer wrote: > On 10/06/14 11:46 AM, Steve Campbell wrote: >> On 6/10/2014 10:46 AM, Digimer wrote: >>> On 10/06/14 10:03 AM, Steve Campbell wrote: I had so much trouble putting Centos 6 guest VMs on a Centos 5 host that I finally switched to a Centos 6 host. I've not needed more that test VMs, so I've used Virtual Machine Manager on the old system, which worked pretty well, so I decided to create my first KVM guest machine. I noticed when I created it, I only had the options of NAT for my network interface, so I used that (obvious). Well, after starting the VM, I find I don't have connectivity with that interface. Reading, I find examples where I need to create bridges perhaps. Xen did most of this for me, so it's a little new to me. Can anyone throw me a clue, please? steve campbell >>> Setting up a bridge is not that hard, and it will give >>> your VMs >>> direct >>> access to the outside world, and host <-> VM access just >>> fine as >>> well. >>> >>> Here is a link showing how to setup a bridge connected to a >>> bond >>> device. Ignore the bond and pretend it is a straight ethX >>> device: >>> >>> https://alteeve.ca/w/AN!Cluster_Tutorial_2#Configuring_our_Bridge.2C_Bonds_and_Interfaces >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >> The host has a device named virbr0 that is installed during >> system >> installation. It also has a network device vnet0. There >> are no >> files in >> /etc/sysconfig/network-scripts for th
Re: [CentOS-virt] Finally switching from Xen to KVM - question about networking
On 6/11/2014 4:10 PM, Steve Campbell wrote: > On 6/11/2014 10:03 AM, Zoltan Frombach wrote: >> On 6/11/2014 3:50 PM, Steve Campbell wrote: >>> On 6/10/2014 4:00 PM, Zoltan Frombach wrote: On 6/10/2014 9:51 PM, Steve Campbell wrote: > On 6/10/2014 3:38 PM, Zoltan Frombach wrote: >> On 6/10/2014 9:27 PM, Steve Campbell wrote: >>> On 6/10/2014 3:09 PM, Zoltan Frombach wrote: Steve, Try the following config. On your host: /etc/sysconfig/network-scripts/ifcfg-eth0: DEVICE=eth0 BOOTPROTO=none ONBOOT=yes NM_CONTROLLED=no TYPE=Ethernet HWADDR=xx:xx:xx:xx:xx:xx<- put your physical NIC's MAC address here BRIDGE=br0 USERCTL=no IPV6INIT=no IPV6_AUTOCONF=no /etc/sysconfig/network-scripts/ifcfg-br0: DEVICE=br0 BOOTPROTO=static ONBOOT=yes NM_CONTROLLED=no TYPE=Bridge IPADDR=10.0.5.16 NETMASK=255.255.255.0 <- you may need to adjust this to your network GATEWAY=10.0.5.1 DNS1=8.8.8.8 DNS2=8.8.4.4 PEERDNS=yes DELAY=0 STP=off USERCTL=no IPV6INIT=no IPV6_AUTOCONF=no Restart networking on the host. Then inside you VM: /etc/sysconfig/network-scripts/ifcfg-eth0: DEVICE=eth0 BOOTPROTO=static ONBOOT=yes NM_CONTROLLED=no TYPE=Ethernet HWADDR=xx:xx:xx:xx:xx:xx<- it must be a unique MAC address for your VM IPADDR=10.0.5.17 NETMASK=255.255.255.0 <- you may need to adjust this to your network GATEWAY=10.0.5.1 DNS1=8.8.8.8 DNS2=8.8.4.4 PEERDNS=yes USERCTL=no IPV6INIT=no IPV6_AUTOCONF=no Then in Virtual Machine Manager make sure that your VM's NIC is connected to the br0 bridge, like this: Network Source: Specify shared device name Bridge Name: br0 On 6/10/2014 8:16 PM, Steve Campbell wrote: > On 6/10/2014 12:43 PM, Digimer wrote: >> On 10/06/14 12:38 PM, Steve Campbell wrote: >>> On 6/10/2014 12:05 PM, Digimer wrote: On 10/06/14 11:46 AM, Steve Campbell wrote: > On 6/10/2014 10:46 AM, Digimer wrote: >> On 10/06/14 10:03 AM, Steve Campbell wrote: >>> I had so much trouble putting Centos 6 guest VMs on a >>> Centos 5 >>> host >>> that >>> I finally switched to a Centos 6 host. >>> >>> I've not needed more that test VMs, so I've used Virtual >>> Machine >>> Manager >>> on the old system, which worked pretty well, so I decided to >>> create my >>> first KVM guest machine. I noticed when I created it, I only >>> had the >>> options of NAT for my network interface, so I used that >>> (obvious). >>> >>> Well, after starting the VM, I find I don't have >>> connectivity >>> with >>> that >>> interface. Reading, I find examples where I need to create >>> bridges >>> perhaps. Xen did most of this for me, so it's a little >>> new to >>> me. >>> >>> Can anyone throw me a clue, please? >>> >>> steve campbell >> Setting up a bridge is not that hard, and it will give >> your VMs >> direct >> access to the outside world, and host <-> VM access just >> fine as >> well. >> >> Here is a link showing how to setup a bridge connected to a >> bond >> device. Ignore the bond and pretend it is a straight ethX >> device: >> >> https://alteeve.ca/w/AN!Cluster_Tutorial_2#Configuring_our_Bridge.2C_Bonds_and_Interfaces >> >> >> >> >> >> >> >> >> > The host has a device named virbr0 that is installed during > system > installation. It also has a network device vnet0. There are no > files in > /etc/sysconfig/network-scripts for these. > > Shouldn't I be able to use the virbr0 virtual bridge for this? > I've > tried setting up the VM's device with all of the options > that is > listed, > but to no avail. > > Should I need
Re: [CentOS-virt] Finally switching from Xen to KVM - question about networking
On 6/11/2014 10:03 AM, Zoltan Frombach wrote: > > On 6/11/2014 3:50 PM, Steve Campbell wrote: >> On 6/10/2014 4:00 PM, Zoltan Frombach wrote: >>> On 6/10/2014 9:51 PM, Steve Campbell wrote: On 6/10/2014 3:38 PM, Zoltan Frombach wrote: > On 6/10/2014 9:27 PM, Steve Campbell wrote: >> On 6/10/2014 3:09 PM, Zoltan Frombach wrote: >>> Steve, >>> >>> Try the following config. >>> >>> On your host: >>> >>> /etc/sysconfig/network-scripts/ifcfg-eth0: >>> >>> DEVICE=eth0 >>> BOOTPROTO=none >>> ONBOOT=yes >>> NM_CONTROLLED=no >>> TYPE=Ethernet >>> HWADDR=xx:xx:xx:xx:xx:xx<- put your physical NIC's MAC address >>> here >>> BRIDGE=br0 >>> USERCTL=no >>> IPV6INIT=no >>> IPV6_AUTOCONF=no >>> >>> >>> /etc/sysconfig/network-scripts/ifcfg-br0: >>> >>> DEVICE=br0 >>> BOOTPROTO=static >>> ONBOOT=yes >>> NM_CONTROLLED=no >>> TYPE=Bridge >>> IPADDR=10.0.5.16 >>> NETMASK=255.255.255.0 <- you may need to adjust this to your >>> network >>> GATEWAY=10.0.5.1 >>> DNS1=8.8.8.8 >>> DNS2=8.8.4.4 >>> PEERDNS=yes >>> DELAY=0 >>> STP=off >>> USERCTL=no >>> IPV6INIT=no >>> IPV6_AUTOCONF=no >>> >>> >>> Restart networking on the host. >>> >>> Then inside you VM: >>> >>> /etc/sysconfig/network-scripts/ifcfg-eth0: >>> >>> DEVICE=eth0 >>> BOOTPROTO=static >>> ONBOOT=yes >>> NM_CONTROLLED=no >>> TYPE=Ethernet >>> HWADDR=xx:xx:xx:xx:xx:xx<- it must be a unique MAC address for >>> your VM >>> IPADDR=10.0.5.17 >>> NETMASK=255.255.255.0 <- you may need to adjust this to your >>> network >>> GATEWAY=10.0.5.1 >>> DNS1=8.8.8.8 >>> DNS2=8.8.4.4 >>> PEERDNS=yes >>> USERCTL=no >>> IPV6INIT=no >>> IPV6_AUTOCONF=no >>> >>> >>> Then in Virtual Machine Manager make sure that your VM's NIC is >>> connected to the br0 bridge, like this: >>> >>> Network Source: Specify shared device name >>> Bridge Name: br0 >>> >>> >>> >>> On 6/10/2014 8:16 PM, Steve Campbell wrote: On 6/10/2014 12:43 PM, Digimer wrote: > On 10/06/14 12:38 PM, Steve Campbell wrote: >> On 6/10/2014 12:05 PM, Digimer wrote: >>> On 10/06/14 11:46 AM, Steve Campbell wrote: On 6/10/2014 10:46 AM, Digimer wrote: > On 10/06/14 10:03 AM, Steve Campbell wrote: >> I had so much trouble putting Centos 6 guest VMs on a >> Centos 5 >> host >> that >> I finally switched to a Centos 6 host. >> >> I've not needed more that test VMs, so I've used Virtual >> Machine >> Manager >> on the old system, which worked pretty well, so I decided to >> create my >> first KVM guest machine. I noticed when I created it, I only >> had the >> options of NAT for my network interface, so I used that >> (obvious). >> >> Well, after starting the VM, I find I don't have >> connectivity >> with >> that >> interface. Reading, I find examples where I need to create >> bridges >> perhaps. Xen did most of this for me, so it's a little >> new to >> me. >> >> Can anyone throw me a clue, please? >> >> steve campbell > Setting up a bridge is not that hard, and it will give > your VMs > direct > access to the outside world, and host <-> VM access just > fine as > well. > > Here is a link showing how to setup a bridge connected to a > bond > device. Ignore the bond and pretend it is a straight ethX > device: > > https://alteeve.ca/w/AN!Cluster_Tutorial_2#Configuring_our_Bridge.2C_Bonds_and_Interfaces > > > > > > > > > > The host has a device named virbr0 that is installed during system installation. It also has a network device vnet0. There are no files in /etc/sysconfig/network-scripts for these. Shouldn't I be able to use the virbr0 virtual bridge for this? I've tried setting up the VM's device with all of the options that is listed, but to no avail. Should I need to set up another bridge for this? And thanks for the link. steve >>> virbr0 is created and managed by libvirtd. If y
Re: [CentOS-virt] Finally switching from Xen to KVM - question about networking
On 6/11/2014 9:56 AM, NightLightHosts Admin wrote: > Do you have the proper gateway/route configured on the VM? > > On Wed, Jun 11, 2014 at 9:50 AM, Steve Campbell wrote: >> On 6/10/2014 4:00 PM, Zoltan Frombach wrote: >>> On 6/10/2014 9:51 PM, Steve Campbell wrote: On 6/10/2014 3:38 PM, Zoltan Frombach wrote: > On 6/10/2014 9:27 PM, Steve Campbell wrote: >> On 6/10/2014 3:09 PM, Zoltan Frombach wrote: >>> Steve, >>> >>> Try the following config. >>> >>> On your host: >>> >>> /etc/sysconfig/network-scripts/ifcfg-eth0: >>> >>> DEVICE=eth0 >>> BOOTPROTO=none >>> ONBOOT=yes >>> NM_CONTROLLED=no >>> TYPE=Ethernet >>> HWADDR=xx:xx:xx:xx:xx:xx<- put your physical NIC's MAC address >>> here >>> BRIDGE=br0 >>> USERCTL=no >>> IPV6INIT=no >>> IPV6_AUTOCONF=no >>> >>> >>> /etc/sysconfig/network-scripts/ifcfg-br0: >>> >>> DEVICE=br0 >>> BOOTPROTO=static >>> ONBOOT=yes >>> NM_CONTROLLED=no >>> TYPE=Bridge >>> IPADDR=10.0.5.16 >>> NETMASK=255.255.255.0 <- you may need to adjust this to your >>> network >>> GATEWAY=10.0.5.1 >>> DNS1=8.8.8.8 >>> DNS2=8.8.4.4 >>> PEERDNS=yes >>> DELAY=0 >>> STP=off >>> USERCTL=no >>> IPV6INIT=no >>> IPV6_AUTOCONF=no >>> >>> >>> Restart networking on the host. >>> >>> Then inside you VM: >>> >>> /etc/sysconfig/network-scripts/ifcfg-eth0: >>> >>> DEVICE=eth0 >>> BOOTPROTO=static >>> ONBOOT=yes >>> NM_CONTROLLED=no >>> TYPE=Ethernet >>> HWADDR=xx:xx:xx:xx:xx:xx<- it must be a unique MAC address for >>> your VM >>> IPADDR=10.0.5.17 >>> NETMASK=255.255.255.0 <- you may need to adjust this to your >>> network >>> GATEWAY=10.0.5.1 >>> DNS1=8.8.8.8 >>> DNS2=8.8.4.4 >>> PEERDNS=yes >>> USERCTL=no >>> IPV6INIT=no >>> IPV6_AUTOCONF=no >>> >>> >>> Then in Virtual Machine Manager make sure that your VM's NIC is >>> connected to the br0 bridge, like this: >>> >>> Network Source: Specify shared device name >>> Bridge Name: br0 >>> >>> >>> >>> On 6/10/2014 8:16 PM, Steve Campbell wrote: On 6/10/2014 12:43 PM, Digimer wrote: > On 10/06/14 12:38 PM, Steve Campbell wrote: >> On 6/10/2014 12:05 PM, Digimer wrote: >>> On 10/06/14 11:46 AM, Steve Campbell wrote: On 6/10/2014 10:46 AM, Digimer wrote: > On 10/06/14 10:03 AM, Steve Campbell wrote: >> I had so much trouble putting Centos 6 guest VMs on a Centos 5 >> host >> that >> I finally switched to a Centos 6 host. >> >> I've not needed more that test VMs, so I've used Virtual >> Machine >> Manager >> on the old system, which worked pretty well, so I decided to >> create my >> first KVM guest machine. I noticed when I created it, I only >> had the >> options of NAT for my network interface, so I used that >> (obvious). >> >> Well, after starting the VM, I find I don't have connectivity >> with >> that >> interface. Reading, I find examples where I need to create >> bridges >> perhaps. Xen did most of this for me, so it's a little new to >> me. >> >> Can anyone throw me a clue, please? >> >> steve campbell > Setting up a bridge is not that hard, and it will give your VMs > direct > access to the outside world, and host <-> VM access just > fine as > well. > > Here is a link showing how to setup a bridge connected to a > bond > device. Ignore the bond and pretend it is a straight ethX > device: > > https://alteeve.ca/w/AN!Cluster_Tutorial_2#Configuring_our_Bridge.2C_Bonds_and_Interfaces > > > > > > > > The host has a device named virbr0 that is installed during system installation. It also has a network device vnet0. There are no files in /etc/sysconfig/network-scripts for these. Shouldn't I be able to use the virbr0 virtual bridge for this? I've tried setting up the VM's device with all of the options that is listed, but to no avail. Should I need to set up another bridge for this? And thanks for the link. steve >>> virbr0 is created and managed by libvirtd. If you open Virtual >>> M
Re: [CentOS-virt] Finally switching from Xen to KVM - question about networking
On 6/11/2014 3:50 PM, Steve Campbell wrote: > On 6/10/2014 4:00 PM, Zoltan Frombach wrote: >> On 6/10/2014 9:51 PM, Steve Campbell wrote: >>> On 6/10/2014 3:38 PM, Zoltan Frombach wrote: On 6/10/2014 9:27 PM, Steve Campbell wrote: > On 6/10/2014 3:09 PM, Zoltan Frombach wrote: >> Steve, >> >> Try the following config. >> >> On your host: >> >> /etc/sysconfig/network-scripts/ifcfg-eth0: >> >> DEVICE=eth0 >> BOOTPROTO=none >> ONBOOT=yes >> NM_CONTROLLED=no >> TYPE=Ethernet >> HWADDR=xx:xx:xx:xx:xx:xx<- put your physical NIC's MAC address >> here >> BRIDGE=br0 >> USERCTL=no >> IPV6INIT=no >> IPV6_AUTOCONF=no >> >> >> /etc/sysconfig/network-scripts/ifcfg-br0: >> >> DEVICE=br0 >> BOOTPROTO=static >> ONBOOT=yes >> NM_CONTROLLED=no >> TYPE=Bridge >> IPADDR=10.0.5.16 >> NETMASK=255.255.255.0 <- you may need to adjust this to your >> network >> GATEWAY=10.0.5.1 >> DNS1=8.8.8.8 >> DNS2=8.8.4.4 >> PEERDNS=yes >> DELAY=0 >> STP=off >> USERCTL=no >> IPV6INIT=no >> IPV6_AUTOCONF=no >> >> >> Restart networking on the host. >> >> Then inside you VM: >> >> /etc/sysconfig/network-scripts/ifcfg-eth0: >> >> DEVICE=eth0 >> BOOTPROTO=static >> ONBOOT=yes >> NM_CONTROLLED=no >> TYPE=Ethernet >> HWADDR=xx:xx:xx:xx:xx:xx<- it must be a unique MAC address for >> your VM >> IPADDR=10.0.5.17 >> NETMASK=255.255.255.0 <- you may need to adjust this to your >> network >> GATEWAY=10.0.5.1 >> DNS1=8.8.8.8 >> DNS2=8.8.4.4 >> PEERDNS=yes >> USERCTL=no >> IPV6INIT=no >> IPV6_AUTOCONF=no >> >> >> Then in Virtual Machine Manager make sure that your VM's NIC is >> connected to the br0 bridge, like this: >> >> Network Source: Specify shared device name >> Bridge Name: br0 >> >> >> >> On 6/10/2014 8:16 PM, Steve Campbell wrote: >>> On 6/10/2014 12:43 PM, Digimer wrote: On 10/06/14 12:38 PM, Steve Campbell wrote: > On 6/10/2014 12:05 PM, Digimer wrote: >> On 10/06/14 11:46 AM, Steve Campbell wrote: >>> On 6/10/2014 10:46 AM, Digimer wrote: On 10/06/14 10:03 AM, Steve Campbell wrote: > I had so much trouble putting Centos 6 guest VMs on a Centos 5 > host > that > I finally switched to a Centos 6 host. > > I've not needed more that test VMs, so I've used Virtual > Machine > Manager > on the old system, which worked pretty well, so I decided to > create my > first KVM guest machine. I noticed when I created it, I only > had the > options of NAT for my network interface, so I used that > (obvious). > > Well, after starting the VM, I find I don't have connectivity > with > that > interface. Reading, I find examples where I need to create > bridges > perhaps. Xen did most of this for me, so it's a little new to > me. > > Can anyone throw me a clue, please? > > steve campbell Setting up a bridge is not that hard, and it will give your VMs direct access to the outside world, and host <-> VM access just fine as well. Here is a link showing how to setup a bridge connected to a bond device. Ignore the bond and pretend it is a straight ethX device: https://alteeve.ca/w/AN!Cluster_Tutorial_2#Configuring_our_Bridge.2C_Bonds_and_Interfaces >>> The host has a device named virbr0 that is installed during >>> system >>> installation. It also has a network device vnet0. There are no >>> files in >>> /etc/sysconfig/network-scripts for these. >>> >>> Shouldn't I be able to use the virbr0 virtual bridge for this? >>> I've >>> tried setting up the VM's device with all of the options that is >>> listed, >>> but to no avail. >>> >>> Should I need to set up another bridge for this? >>> >>> And thanks for the link. >>> >>> steve >> virbr0 is created and managed by libvirtd. If you open Virtual >> Machine >> Manager, connect to localhost and then double-click on >> 'localhost', >> you will see a tab for creating/managing bridges (NAT'ed, >> generally). >> I disable 'virbr0' as NAT'ing is generally not what I want. >> >
Re: [CentOS-virt] Finally switching from Xen to KVM - question about networking
Do you have the proper gateway/route configured on the VM? On Wed, Jun 11, 2014 at 9:50 AM, Steve Campbell wrote: > > On 6/10/2014 4:00 PM, Zoltan Frombach wrote: >> >> On 6/10/2014 9:51 PM, Steve Campbell wrote: >>> On 6/10/2014 3:38 PM, Zoltan Frombach wrote: On 6/10/2014 9:27 PM, Steve Campbell wrote: > On 6/10/2014 3:09 PM, Zoltan Frombach wrote: >> Steve, >> >> Try the following config. >> >> On your host: >> >> /etc/sysconfig/network-scripts/ifcfg-eth0: >> >> DEVICE=eth0 >> BOOTPROTO=none >> ONBOOT=yes >> NM_CONTROLLED=no >> TYPE=Ethernet >> HWADDR=xx:xx:xx:xx:xx:xx<- put your physical NIC's MAC address >> here >> BRIDGE=br0 >> USERCTL=no >> IPV6INIT=no >> IPV6_AUTOCONF=no >> >> >> /etc/sysconfig/network-scripts/ifcfg-br0: >> >> DEVICE=br0 >> BOOTPROTO=static >> ONBOOT=yes >> NM_CONTROLLED=no >> TYPE=Bridge >> IPADDR=10.0.5.16 >> NETMASK=255.255.255.0 <- you may need to adjust this to your >> network >> GATEWAY=10.0.5.1 >> DNS1=8.8.8.8 >> DNS2=8.8.4.4 >> PEERDNS=yes >> DELAY=0 >> STP=off >> USERCTL=no >> IPV6INIT=no >> IPV6_AUTOCONF=no >> >> >> Restart networking on the host. >> >> Then inside you VM: >> >> /etc/sysconfig/network-scripts/ifcfg-eth0: >> >> DEVICE=eth0 >> BOOTPROTO=static >> ONBOOT=yes >> NM_CONTROLLED=no >> TYPE=Ethernet >> HWADDR=xx:xx:xx:xx:xx:xx<- it must be a unique MAC address for >> your VM >> IPADDR=10.0.5.17 >> NETMASK=255.255.255.0 <- you may need to adjust this to your >> network >> GATEWAY=10.0.5.1 >> DNS1=8.8.8.8 >> DNS2=8.8.4.4 >> PEERDNS=yes >> USERCTL=no >> IPV6INIT=no >> IPV6_AUTOCONF=no >> >> >> Then in Virtual Machine Manager make sure that your VM's NIC is >> connected to the br0 bridge, like this: >> >> Network Source: Specify shared device name >> Bridge Name: br0 >> >> >> >> On 6/10/2014 8:16 PM, Steve Campbell wrote: >>> On 6/10/2014 12:43 PM, Digimer wrote: On 10/06/14 12:38 PM, Steve Campbell wrote: > On 6/10/2014 12:05 PM, Digimer wrote: >> On 10/06/14 11:46 AM, Steve Campbell wrote: >>> On 6/10/2014 10:46 AM, Digimer wrote: On 10/06/14 10:03 AM, Steve Campbell wrote: > I had so much trouble putting Centos 6 guest VMs on a Centos 5 > host > that > I finally switched to a Centos 6 host. > > I've not needed more that test VMs, so I've used Virtual > Machine > Manager > on the old system, which worked pretty well, so I decided to > create my > first KVM guest machine. I noticed when I created it, I only > had the > options of NAT for my network interface, so I used that > (obvious). > > Well, after starting the VM, I find I don't have connectivity > with > that > interface. Reading, I find examples where I need to create > bridges > perhaps. Xen did most of this for me, so it's a little new to > me. > > Can anyone throw me a clue, please? > > steve campbell Setting up a bridge is not that hard, and it will give your VMs direct access to the outside world, and host <-> VM access just fine as well. Here is a link showing how to setup a bridge connected to a bond device. Ignore the bond and pretend it is a straight ethX device: https://alteeve.ca/w/AN!Cluster_Tutorial_2#Configuring_our_Bridge.2C_Bonds_and_Interfaces >>> The host has a device named virbr0 that is installed during >>> system >>> installation. It also has a network device vnet0. There are no >>> files in >>> /etc/sysconfig/network-scripts for these. >>> >>> Shouldn't I be able to use the virbr0 virtual bridge for this? >>> I've >>> tried setting up the VM's device with all of the options that is >>> listed, >>> but to no avail. >>> >>> Should I need to set up another bridge for this? >>> >>> And thanks for the link. >>> >>> steve >> virbr0 is created and managed by libvirtd. If you open Virtual >> Machine >> Manager, connect to localhost and then double-click on >> 'localhost', >> you will see a tab for creating/managing bridges (NAT'ed, >> generally). >> I dis
Re: [CentOS-virt] Finally switching from Xen to KVM - question about networking
On 6/10/2014 4:00 PM, Zoltan Frombach wrote: > > On 6/10/2014 9:51 PM, Steve Campbell wrote: >> On 6/10/2014 3:38 PM, Zoltan Frombach wrote: >>> On 6/10/2014 9:27 PM, Steve Campbell wrote: On 6/10/2014 3:09 PM, Zoltan Frombach wrote: > Steve, > > Try the following config. > > On your host: > > /etc/sysconfig/network-scripts/ifcfg-eth0: > > DEVICE=eth0 > BOOTPROTO=none > ONBOOT=yes > NM_CONTROLLED=no > TYPE=Ethernet > HWADDR=xx:xx:xx:xx:xx:xx<- put your physical NIC's MAC address > here > BRIDGE=br0 > USERCTL=no > IPV6INIT=no > IPV6_AUTOCONF=no > > > /etc/sysconfig/network-scripts/ifcfg-br0: > > DEVICE=br0 > BOOTPROTO=static > ONBOOT=yes > NM_CONTROLLED=no > TYPE=Bridge > IPADDR=10.0.5.16 > NETMASK=255.255.255.0 <- you may need to adjust this to your > network > GATEWAY=10.0.5.1 > DNS1=8.8.8.8 > DNS2=8.8.4.4 > PEERDNS=yes > DELAY=0 > STP=off > USERCTL=no > IPV6INIT=no > IPV6_AUTOCONF=no > > > Restart networking on the host. > > Then inside you VM: > > /etc/sysconfig/network-scripts/ifcfg-eth0: > > DEVICE=eth0 > BOOTPROTO=static > ONBOOT=yes > NM_CONTROLLED=no > TYPE=Ethernet > HWADDR=xx:xx:xx:xx:xx:xx<- it must be a unique MAC address for > your VM > IPADDR=10.0.5.17 > NETMASK=255.255.255.0 <- you may need to adjust this to your > network > GATEWAY=10.0.5.1 > DNS1=8.8.8.8 > DNS2=8.8.4.4 > PEERDNS=yes > USERCTL=no > IPV6INIT=no > IPV6_AUTOCONF=no > > > Then in Virtual Machine Manager make sure that your VM's NIC is > connected to the br0 bridge, like this: > > Network Source: Specify shared device name > Bridge Name: br0 > > > > On 6/10/2014 8:16 PM, Steve Campbell wrote: >> On 6/10/2014 12:43 PM, Digimer wrote: >>> On 10/06/14 12:38 PM, Steve Campbell wrote: On 6/10/2014 12:05 PM, Digimer wrote: > On 10/06/14 11:46 AM, Steve Campbell wrote: >> On 6/10/2014 10:46 AM, Digimer wrote: >>> On 10/06/14 10:03 AM, Steve Campbell wrote: I had so much trouble putting Centos 6 guest VMs on a Centos 5 host that I finally switched to a Centos 6 host. I've not needed more that test VMs, so I've used Virtual Machine Manager on the old system, which worked pretty well, so I decided to create my first KVM guest machine. I noticed when I created it, I only had the options of NAT for my network interface, so I used that (obvious). Well, after starting the VM, I find I don't have connectivity with that interface. Reading, I find examples where I need to create bridges perhaps. Xen did most of this for me, so it's a little new to me. Can anyone throw me a clue, please? steve campbell >>> Setting up a bridge is not that hard, and it will give your VMs >>> direct >>> access to the outside world, and host <-> VM access just >>> fine as >>> well. >>> >>> Here is a link showing how to setup a bridge connected to a >>> bond >>> device. Ignore the bond and pretend it is a straight ethX >>> device: >>> >>> https://alteeve.ca/w/AN!Cluster_Tutorial_2#Configuring_our_Bridge.2C_Bonds_and_Interfaces >>> >>> >>> >>> >>> >>> >>> >>> >>> >> The host has a device named virbr0 that is installed during >> system >> installation. It also has a network device vnet0. There are no >> files in >> /etc/sysconfig/network-scripts for these. >> >> Shouldn't I be able to use the virbr0 virtual bridge for this? >> I've >> tried setting up the VM's device with all of the options that is >> listed, >> but to no avail. >> >> Should I need to set up another bridge for this? >> >> And thanks for the link. >> >> steve > virbr0 is created and managed by libvirtd. If you open Virtual > Machine > Manager, connect to localhost and then double-click on > 'localhost', > you will see a tab for creating/managing bridges (NAT'ed, > generally). > I disable 'virbr0' as NAT'ing is generally not what I want. > > The 'vnetX' devices are dynamically created to link a VM's > interface > to a bridge. Think of them as virtual network cables. They get > created >
