From raju.rajsand at gmail.com  Mon Nov  7 13:17:22 2011
From: raju.rajsand at gmail.com (Rajagopal Swaminathan)
Date: Mon, 7 Nov 2011 23:47:22 +0530
Subject: [CentOS-virt] P2V utility
Message-ID: <CA+YdgaqusA9ZR2ekkyXtkggKBsH73=HYe1c=XVTSnq7OQ_kq+Q@mail.gmail.com>

Greetings,

An somebody pint to me to P2V Utility for the m$ world?

Like in VMware?

-- 
Regards,

Rajagopal

From lorenzo at tulug.it  Tue Nov  8 09:20:52 2011
From: lorenzo at tulug.it (Lorenzo)
Date: Tue, 8 Nov 2011 15:20:52 +0100
Subject: [CentOS-virt] P2V utility
In-Reply-To: <CA+YdgaqusA9ZR2ekkyXtkggKBsH73=HYe1c=XVTSnq7OQ_kq+Q@mail.gmail.com>
References: <CA+YdgaqusA9ZR2ekkyXtkggKBsH73=HYe1c=XVTSnq7OQ_kq+Q@mail.gmail.com>
Message-ID: <CADE4e0WfAq++1UDq-Vj3EhR=K1=xQTwmU0qsVhLrXVKgy+SDhg@mail.gmail.com>

2011/11/7 Rajagopal Swaminathan <raju.rajsand at gmail.com>:
> Greetings,
>
> An somebody pint to me to P2V Utility for the m$ world?
>
> Like in VMware?
>
> --
> Regards,
>
> Rajagopal

Try here:
http://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE
not centos specific, but I found a lot of useful info.

Regards,
Lorenzo

From mdra137 at gmail.com  Fri Nov 18 08:39:23 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Fri, 18 Nov 2011 14:39:23 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0BmRWi7_=FEJ0WSTzs5J1-2wuJ_AZdN=_S8WKWg94E_Vg@mail.gmail.com>

Hi,

I've been using CentOS & Xen on a server that has 2 VM's configured. The
default configuration includes one physical iface that is propagated (by a
default bridge) to the VM's.

Since I wanted to configure additional physical iface, define a new bridge
and propagate it to the viface-s of the VM's, i configured the bridge/phys.
iface and brought it up (here are configurations that I set up):

-> eth3
DEVICE=eth3
BOOTPROTO=static
HWADDR=D4:85:64:4B:76:AB
ONBOOT=yes
#HOTPLUG=no
#DHCP_HOSTNAME=kdr-3k-4r-3o-07
BRIDGE=br0
TYPE=Ethernet

-> br0
DEVICE=br0
TYPE=Bridge
BOOTPROTO=none
ONBOOT=yes

Then I configured new virt. ifaces on VM's (using virsh edit, config is
listed below):

<interface type='bridge'>
<mac address='00:16:36:17:62:5d'/>
<source bridge='xenbr0'/>
<script path='vif-bridge'/>
<target dev='vif5.0'/>
</interface>
<interface type='bridge'>
<mac address='00:16:3e:ca:63:39'/>
<source bridge='br0'/>
<script path='vif-bridge'/>
<target dev='vif5.1'/>
</interface>

You can see the default bridge (xenbr0 -> vif5.0) and my new bridge br0
connected to vif5.1.

So, here I got stuck up - when I try tu start a VM (xm create VIRT_SRV),
the VM starts booting but hangs up (I can ping it form another srv., but
when I try SSH it says "connection refused"). When I remove configuration
for vif5.1 the VM starts up normally. I actually managed to start VM with
vif5.1 up once, but next time I restarted it, the problem was there :/


Furthermore, I noticed this in the Xen log:

[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vif.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 0.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vif/1/1/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices usb.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vbd.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 768.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vbd/1/768/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 5632.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vbd/1/5632/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices irq.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vkbd.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vfb.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices pci.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices ioports.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices tap.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vtpm.

So the boot process goes on regulary until the last line ("Waiting for
devices vtpm"). It seems like TPM makes it impossible for VM's to start
regulary. When I open the VM's console (with virt-manager) I see the whole
boot process but it hangs when it tries to start iface eth2 (attached to
the second bridge) ...

Does anybody have a clue why is this happening?

Thanks in advance ..
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.centos.org/pipermail/centos-virt/attachments/20111118/e056a2eb/attachment.html 

From peter.peltonen at gmail.com  Fri Nov 18 09:33:35 2011
From: peter.peltonen at gmail.com (Peter Peltonen)
Date: Fri, 18 Nov 2011 16:33:35 +0200
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
In-Reply-To: <CALZem0BmRWi7_=FEJ0WSTzs5J1-2wuJ_AZdN=_S8WKWg94E_Vg@mail.gmail.com>
References: <CALZem0BmRWi7_=FEJ0WSTzs5J1-2wuJ_AZdN=_S8WKWg94E_Vg@mail.gmail.com>
Message-ID: <CAGTVFvHkhkUytpf9ei2vGT0_NhLsOhXikDPV9ORAKYitttjCdA@mail.gmail.com>

Hi,

2011/11/18 Matija Draganovi? <mdra137 at gmail.com>:
> I've been using CentOS & Xen on a server that has 2 VM's configured. The
> default configuration includes one physical iface that is propagated (by a
> default bridge) to the VM's.

You do not mention which version of CentOS and Xen you are using?

>
> Since I wanted to configure additional physical iface, define a new bridge
> and propagate it to the viface-s of the VM's, i configured the bridge/phys.
> iface and brought it up (here are configurations that I set up):
>
> -> eth3
> DEVICE=eth3
> BOOTPROTO=static
> HWADDR=D4:85:64:4B:76:AB
> ONBOOT=yes
> #HOTPLUG=no
> #DHCP_HOSTNAME=kdr-3k-4r-3o-07
> BRIDGE=br0
> TYPE=Ethernet
>
> -> br0
> DEVICE=br0
> TYPE=Bridge
> BOOTPROTO=none
> ONBOOT=yes

If this is a CentOS5 machine with the CentOS provided Xen 3.0
packages, then here is info how i got my bridges to work with that
setup:

* For dom0 I configured eth0 and eth1 as usual in /etc/sysconfig/network-scripts

* I did not configure br0 or br1 in network-scripts, but instead I
created a file called /etc/xen/scripts/my-network-script having this
contents:

#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0
"$dir/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=xenbr1

* Then I modified in dom0 the file /etc/xen/xend-config.sxp in the
following way:

#(network-script network-bridge)
(network-script my-network-script)

* Now rebooting dom0 made the bridges available

* After that I could configure them in my domU config:

vif = [ "mac=00:16:3E:69:29:25,bridge=xenbr0,script=vif-bridge","mac=00:16:3E:E6:B0:6D,bridge=xenbr1,script=vif-bridge"
]

* After starting the domU I could configure the interfaces in
network-scripts using the hardware addresses specified in the domU
config


It seems that configuring bridging is done a bit differently in
different Xen versions, so this might not work if you are using some
other kind of config. With CentOS6 and 3rd party Xen 4.1 packages this
procedure did not work at all and instead I needed to do the
following:

* in dom0 create the br0 and br1 devices in network-scripts

* in dom0 /etc/xen/xend-config.sxp put instead:

#(network-script network-bridge)
(network-script /bin/true)

* and in dom0 use different configuration for the domU config files like this:

vif = [ "mac=00:16:3E:69:29:25,bridge=br0","mac=00:16:3E:E6:B0:6D,bridge=br1" ]


Hope this helps, unfortuantely I am not familiar with virsh at all.

Best,
Peter

From mdra137 at gmail.com  Fri Nov 18 12:17:17 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Fri, 18 Nov 2011 18:17:17 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0D1Z-dbkvM+-0+DgVGSGd_dHa757rSqMUZcAgCfffstwQ@mail.gmail.com>

Dear Peter,


Thanks for your reply. I was so occupied with troubleshooting that I forgot
to mention the OS & Xen version :)

My CentOS version is
CentOS release 5.7 (Final)
Linux 2.6.18-274.7.1.el5xen #1 SMP Thu Oct 20 17:06:34 EDT 2011 x86_64
x86_64 x86_64 GNU/Linux

and Xen v3.0.

I tried creating bridges the same way you did and succedded. I also tried
doing the same via ifcfg scripts, and it also worked.

I have no problem with creating bridges and connecting them with physical
ifaces, but I can't start my VM's (most of the time one VM start but the
other one hangs while trying to initalize eth2 that is connected to my
second (non default - xenbr1) bridge)).

The only diference between your config and mine is that I have vifname-s
listed (example below):

vif = [
"mac=00:16:36:72:35:e5,bridge=xenbr0,script=vif-bridge,vifname=vif4.0",
"mac=00:16:3e:57:de:0d,bridge=xenbr1,script=vif-bridge, vifname=vif4.1" ]

I'm not saying that this could be the problem, but since I'm slowly running
out of ideas - it's a longshot :)

So, to sum it all up - I can create bridges properly, but my VM's hang when
they try to bring up vifaces connected to the xenbr1. Also, I have no
problem with having only one bridge active - problem appears when I have
multiple bridges.

Br,
Matija
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.centos.org/pipermail/centos-virt/attachments/20111118/2a75ed85/attachment.html 

From maillists at conactive.com  Fri Nov 18 13:33:20 2011
From: maillists at conactive.com (Kai Schaetzl)
Date: Fri, 18 Nov 2011 19:33:20 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
In-Reply-To: <CALZem0D1Z-dbkvM+-0+DgVGSGd_dHa757rSqMUZcAgCfffstwQ@mail.gmail.com>
References: <CALZem0D1Z-dbkvM+-0+DgVGSGd_dHa757rSqMUZcAgCfffstwQ@mail.gmail.com>
Message-ID: <VA.00003db7.1907ac90@news.conactive.com>

Matija Draganovi? wrote on Fri, 18 Nov 2011 18:17:17 +0100:

> The only diference between your config and mine is that I have vifname-s
> listed

Then remove it. I've never seen it like that. If I remember it correctly 
the vifnames are created dynamically. You can't rely on them I suppose.

And I don't remember using "script" either.

If you can't get it to work then use the second method Peter describes. 
That one should also work for Xen 3.0 and is guaranteed to create stable 
bridging.



Kai

-- 
Get your web at Conactive Internet Services: http://www.conactive.com




From jason at daylife.com  Fri Nov 18 17:56:02 2011
From: jason at daylife.com (Jason Nagashima)
Date: Fri, 18 Nov 2011 17:56:02 -0500 (EST)
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <1331504081.4540.1321656727740.JavaMail.root@mailbox01.hq.daylife.com>
Message-ID: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>

Running on Centos 5.6 with KVM... 

I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?

I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it.  There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.

Any advice/working examples would be greatly appreciated.

Regards,
Jason

From incoming-centos at rjl.com  Fri Nov 18 23:34:25 2011
From: incoming-centos at rjl.com (Nataraj)
Date: Fri, 18 Nov 2011 20:34:25 -0800
Subject: [CentOS-virt] high resolution video for kvm vm
Message-ID: <4EC731D1.40109@rjl.com>

I'm running a fuduntu vm (based on fedora 14)  on a CentOS 6 kvm
server.  I have tried changing the video in virt-manager from cirrus to
vga and restarting the VM, but the maximum resolution that the client
will let me set is still only 1024x768.  Should I be able to get  high
res video with the kvm VGA mode?  Note that the VM is running on a
CentOS server while virt-manager is running on my local desktop.

Would I be better off trying to get the vmware VGA driver working?  I'm
assuming I have to extract the driver from the vmware tools package and
manually install it into the X server, because VMware tools won't
install under kvm.

Also, I run with the keyboard option to swap caps lock and control on my
linux desktop, which does not seem to get passed through to the guest. 
I tried setting the same swap caps lock and control option in the guest,
but it does not work.  Any ideas?

Thanks,
Nataraj


From mdra137 at gmail.com  Sat Nov 19 01:32:21 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Sat, 19 Nov 2011 07:32:21 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0A+hx+b2OFOEYD-YdpXxV9Y=jFUP=UTjgFLBqBqca78YQ@mail.gmail.com>

I tried to remove vifname and vif-script but the problem remains. I think
that the bridges are ok, but for some reason VM's hang when they try to
connect their vifaces to them.

I'll try some different configurations of the physical ifaces (an vifaces
also), maybe I'll be able to find out something. Also, I'll focus on the
vTPM, since the following line shows up in the Xen log when the VM tries to
bring up the iface connected to the second bridge:

[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vtpm


Furthermore, it appears that sometimes the VM's manage to start regulary, I
just can't figure out when & why :/

Tnx for your comments ..

Br,
M.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.centos.org/pipermail/centos-virt/attachments/20111119/cc41e78f/attachment.html 

From mdra137 at gmail.com  Tue Nov 22 04:37:31 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Tue, 22 Nov 2011 10:37:31 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0AS0ptzxMRXooEFHLCAR=OCnaFcXS5AcMmQduevWSFjrQ@mail.gmail.com>

Ok, after trying multiple different configurations I decided to play by the
book - I removed ifcfg script for creating the additional bridge and set up
an Xen script. So my new configuration is:

-> eth3 (my physical interface)
# NetXen Incorporated NX3031 Multifunction 1/10-Gigabit Server Adapter
DEVICE=eth3
BOOTPROTO=static
HWADDR= ...
ONBOOT=yes
IPADDR= ...
NETMASK= ...
NETWORK= ...

and the network-xen-multi-bridge script:

#!/bin/sh
# network-xen-multi-bridge
# Exit if anything goes wrong.
set -e
# First arg is the operation.
OP=$1
shift
script=/etc/xen/scripts/network-bridge.xen
case ${OP} in
start)
$script start vifnum=3 bridge=xenbr3 netdev=eth3
$script start vifnum=0 bridge=xenbr0 netdev=eth0
;;
stop)
$script stop vifnum=3 bridge=xenbr3 netdev=eth3
$script stop vifnum=0 bridge=xenbr0 netdev=eth0
;;
status)
$script status vifnum=3 bridge=xenbr3 netdev=eth3
$script status vifnum=0 bridge=xenbr0 netdev=eth0
;;
*)
echo 'Unknown command: ' ${OP}
echo 'Valid commands are: start, stop, status'
exit 1
esac

After I restart the physical server bridges are set up correctly:

# brctl show
bridge name bridge id STP enabled interfaces
virbr0 8000.000000000000 yes
xenbr0 8000.feffffffffff no vif0.0
peth0
xenbr3 8000.feffffffffff no vif0.3
peth3

Unfortunately, this did not solve the problem - I manage to start one VM
(connected to both of the bridges), but when I try to start the other one,
it just hangs when trying to bring up the second interface (connected to
xenbr3) :/

I'm currently completely out of ideas, but I'm not giving up ;)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.centos.org/pipermail/centos-virt/attachments/20111122/eb760bb6/attachment.html 

From tait at taiter.com  Tue Nov 22 11:07:54 2011
From: tait at taiter.com (Tait Clarridge)
Date: Tue, 22 Nov 2011 11:07:54 -0500
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>
References: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>
Message-ID: <1321978074.22491.12.camel@tclarrltp.frontiernetworks.ca>

On Fri, 2011-11-18 at 17:56 -0500, Jason Nagashima wrote:
> Running on Centos 5.6 with KVM... 
> 
> I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?
> 
> I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it.  There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.
> 
> Any advice/working examples would be greatly appreciated.

Hi Jason,

I have had luck doing this with Xen, where I create bond0 on a trunk
interface and have xen bring it up as xenbr0 with pbond0 in the back
end.

You should be able to do roughly the same by creating a bridge interface
in /etc/sysconfig/network-scripts referencing bond0 as a member.

After that you should be able to run a script to create VLAN bridges
like the following:

#!/bin/bash
/sbin/modprobe 8021q

# Add your vlans here that you want with the numbers separated by a 
# space
VLANS="5 10 15 20"
# This should work with the bonding interface
TRUNKINT="bond0"
for VLAN in $VLANS
do
	vconfig add $TRUNKINT $VLAN
	brctl add br$VLAN
	brctl addif br$VLAN $TRUNKINT.$VLAN
	ifconfig $TRUNKINT.$VLAN up
	ifconfig br$VLAN up
done

I have done this with Xen on 5.5, 5.6 and 5.7... but it should work for
KVM. If you create the standard bridge interface br0 using just bond0
that will get you a trunk on whatever the native vlan is for that trunk.

Tait



From dmartls1 at gmail.com  Tue Nov 22 12:39:02 2011
From: dmartls1 at gmail.com (David Martin)
Date: Tue, 22 Nov 2011 11:39:02 -0600
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <1321978074.22491.12.camel@tclarrltp.frontiernetworks.ca>
References: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>
	<1321978074.22491.12.camel@tclarrltp.frontiernetworks.ca>
Message-ID: <CAAsqWCd+KWrX-SpRcYVNzCVC4HDV25C1QeOZzu-ChN0ZHyhdBw@mail.gmail.com>

We are doing this quite a bit in production and it works great.

bond as you normally would:
DEVICE=bond0
ONBOOT=yes
USERCTL=no
BONDING_OPTS="mode=4 miimon=100"

one of these for each vlan (in this case 50):
VLAN=yes
VLAN_NAME_TYPE=VLAN_PLUS_VID_NO_PAD
DEVICE=vlan50
PHYSDEV=bond0
TYPE=Ethernet
ONBOOT=yes
BRIDGE=br50

and finally the bridge device to expose to guests:
DEVICE=br50
TYPE=Bridge
ONBOOT=yes
DELAY=0
GATEWAYDEV=none




On Tue, Nov 22, 2011 at 10:07 AM, Tait Clarridge <tait at taiter.com> wrote:
> On Fri, 2011-11-18 at 17:56 -0500, Jason Nagashima wrote:
>> Running on Centos 5.6 with KVM...
>>
>> I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?
>>
>> I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it. ?There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.
>>
>> Any advice/working examples would be greatly appreciated.
>
> Hi Jason,
>
> I have had luck doing this with Xen, where I create bond0 on a trunk
> interface and have xen bring it up as xenbr0 with pbond0 in the back
> end.
>
> You should be able to do roughly the same by creating a bridge interface
> in /etc/sysconfig/network-scripts referencing bond0 as a member.
>
> After that you should be able to run a script to create VLAN bridges
> like the following:
>
> #!/bin/bash
> /sbin/modprobe 8021q
>
> # Add your vlans here that you want with the numbers separated by a
> # space
> VLANS="5 10 15 20"
> # This should work with the bonding interface
> TRUNKINT="bond0"
> for VLAN in $VLANS
> do
> ? ? ? ?vconfig add $TRUNKINT $VLAN
> ? ? ? ?brctl add br$VLAN
> ? ? ? ?brctl addif br$VLAN $TRUNKINT.$VLAN
> ? ? ? ?ifconfig $TRUNKINT.$VLAN up
> ? ? ? ?ifconfig br$VLAN up
> done
>
> I have done this with Xen on 5.5, 5.6 and 5.7... but it should work for
> KVM. If you create the standard bridge interface br0 using just bond0
> that will get you a trunk on whatever the native vlan is for that trunk.
>
> Tait
>
>
> _______________________________________________
> CentOS-virt mailing list
> CentOS-virt at centos.org
> http://lists.centos.org/mailman/listinfo/centos-virt
>

From jason at daylife.com  Wed Nov 23 16:49:56 2011
From: jason at daylife.com (Jason Nagashima)
Date: Wed, 23 Nov 2011 16:49:56 -0500 (EST)
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <CAAsqWCd+KWrX-SpRcYVNzCVC4HDV25C1QeOZzu-ChN0ZHyhdBw@mail.gmail.com>
Message-ID: <206550579.4866.1322084996341.JavaMail.root@mailbox01.hq.daylife.com>

Awesome!

Thank you everyone for responding and helping out. I'm happy to report that we got it working!

Cheers,
Jason

----- Original Message -----
From: "David Martin" <dmartls1 at gmail.com>
To: "Discussion about the virtualization on CentOS" <centos-virt at centos.org>
Sent: Tuesday, November 22, 2011 12:39:02 PM
Subject: Re: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6

We are doing this quite a bit in production and it works great.

bond as you normally would:
DEVICE=bond0
ONBOOT=yes
USERCTL=no
BONDING_OPTS="mode=4 miimon=100"

one of these for each vlan (in this case 50):
VLAN=yes
VLAN_NAME_TYPE=VLAN_PLUS_VID_NO_PAD
DEVICE=vlan50
PHYSDEV=bond0
TYPE=Ethernet
ONBOOT=yes
BRIDGE=br50

and finally the bridge device to expose to guests:
DEVICE=br50
TYPE=Bridge
ONBOOT=yes
DELAY=0
GATEWAYDEV=none




On Tue, Nov 22, 2011 at 10:07 AM, Tait Clarridge <tait at taiter.com> wrote:
> On Fri, 2011-11-18 at 17:56 -0500, Jason Nagashima wrote:
>> Running on Centos 5.6 with KVM...
>>
>> I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?
>>
>> I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it. ?There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.
>>
>> Any advice/working examples would be greatly appreciated.
>
> Hi Jason,
>
> I have had luck doing this with Xen, where I create bond0 on a trunk
> interface and have xen bring it up as xenbr0 with pbond0 in the back
> end.
>
> You should be able to do roughly the same by creating a bridge interface
> in /etc/sysconfig/network-scripts referencing bond0 as a member.
>
> After that you should be able to run a script to create VLAN bridges
> like the following:
>
> #!/bin/bash
> /sbin/modprobe 8021q
>
> # Add your vlans here that you want with the numbers separated by a
> # space
> VLANS="5 10 15 20"
> # This should work with the bonding interface
> TRUNKINT="bond0"
> for VLAN in $VLANS
> do
> ? ? ? ?vconfig add $TRUNKINT $VLAN
> ? ? ? ?brctl add br$VLAN
> ? ? ? ?brctl addif br$VLAN $TRUNKINT.$VLAN
> ? ? ? ?ifconfig $TRUNKINT.$VLAN up
> ? ? ? ?ifconfig br$VLAN up
> done
>
> I have done this with Xen on 5.5, 5.6 and 5.7... but it should work for
> KVM. If you create the standard bridge interface br0 using just bond0
> that will get you a trunk on whatever the native vlan is for that trunk.
>
> Tait
>
>
> _______________________________________________
> CentOS-virt mailing list
> CentOS-virt at centos.org
> http://lists.centos.org/mailman/listinfo/centos-virt
>
_______________________________________________
CentOS-virt mailing list
CentOS-virt at centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

From mdra137 at gmail.com  Fri Nov 25 06:11:44 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Fri, 25 Nov 2011 12:11:44 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0BCpJuchqLS6vws9Sm+_YPbR3AkLVyiKBQpJAPDGvzSGQ@mail.gmail.com>

Finally, I managed to solve the problem. The problem was rather strange -
after configuring bridges I added new ifaces to the VM. For some reason,
during boot process of the VM's, wrong interface was started (VM tried to
bring up eth2 instead eth1?).

After adding the new ifaces through virt-manager, the VM started regulary
and created a new network script for eth2
(/etc/sysconfig/network-scripts/ifcfg-eth2). I think that the problem was
this - when the VM is restarted it tried to bring up eth2 while vif-script
tried to propagate second bridge via eth1 iface. I resolved this simply by
replacing ifcfg-eth2 script with ifcfg-eth1. Now, VM starts/restarts
regulary ;)

So, the process for creating and configuring new bridges that I follow is
(tried on multiple servers):

- create new script that sets up multiple bridges in /etc/xen/scripts/

example: network-xen-multi-bridge

#!/bin/sh
# network-xen-multi-bridge
# Exit if anything goes wrong.
set -e
# First arg is the operation.
OP=$1
shift
script=/etc/xen/scripts/network-bridge.xen
case ${OP} in
start)
        $script start vifnum=3 bridge=xenbr3 netdev=eth3
        $script start vifnum=0 bridge=xenbr0 netdev=eth0
        ;;
stop)
        $script stop vifnum=3 bridge=xenbr3 netdev=eth3
        $script stop vifnum=0 bridge=xenbr0 netdev=eth0
        ;;
status)
        $script status vifnum=3 bridge=xenbr3 netdev=eth3
        $script status vifnum=0 bridge=xenbr0 netdev=eth0
        ;;
*)
        echo 'Unknown command: ' ${OP}
        echo 'Valid commands are: start, stop, status'
        exit 1
esac



- make it executable (chmod 755 network-xen-multi-bridge)

- configure /etc/xen/xend-config.sxp (comment out the current script and
add the new one);

# It is possible to use the network-bridge script in more complicated
# scenarios, such as having two outgoing interfaces, with two bridges, and
# two fake interfaces per guest domain.  To do things like this, write
# yourself a wrapper script, and call network-bridge from it, as appropriate.
#
#(network-script network-bridge)
(network-script  network-xen-multi-bridge)



- restart physical server so the bridges are properly created

- add virt. ifaces to the VM's (via virt-manager or via config. files in
/etc/xen/ ..)

- boot VM

- configure newly added iface in /etc/sysconfig/network-scripts/

- restart VM

Additionaly I check everything by restarting phys. server to make sure that
everything is ok ;)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.centos.org/pipermail/centos-virt/attachments/20111125/1304c71b/attachment.html 

From mail-lists at karan.org  Fri Nov 25 19:29:20 2011
From: mail-lists at karan.org (Karanbir Singh)
Date: Sat, 26 Nov 2011 00:29:20 +0000
Subject: [CentOS-virt] Device renaming heads up
Message-ID: <4ED032E0.1040109@karan.org>

hi Guys,

Just in case anyone hasent noticed this :
https://bugzilla.redhat.com/show_bug.cgi?id=729586 device naming mixup
causing lots of domU's to not come back after a kernel update...

- KB

From toddandmargo at gmail.com  Mon Nov 28 13:37:50 2011
From: toddandmargo at gmail.com (Todd And Margo Chester)
Date: Mon, 28 Nov 2011 10:37:50 -0800
Subject: [CentOS-virt] kvm: w7 bsod's at shutdown
Message-ID: <4ED3D4FE.9090008@gmail.com>

Hi All,

I am using Scientific Linux 6.1 x64

Any idea how to get my W7 x32 guest to shutdown with out a BSOD?
I have to go into virt-manager and kill it all the time.  My XP guest
shuts down without issue.

Many thanks,
-T

$ rpm -qa \*kvm\*
qemu-kvm-0.12.1.2-2.160.el6_1.2.x86_64

$ rpm -qa \*virt\*
python-virtinst-0.500.5-3.el6.noarch
libvirt-0.8.7-18.el6_1.1.x86_64
libvirt-client-0.8.7-18.el6_1.1.x86_64
virt-manager-0.8.6-4.el6.noarch
libvirt-python-0.8.7-18.el6_1.1.x86_64


From byrnejb at harte-lyne.ca  Tue Nov 29 15:51:45 2011
From: byrnejb at harte-lyne.ca (James B. Byrne)
Date: Tue, 29 Nov 2011 15:51:45 -0500 (EST)
Subject: [CentOS-virt] Transfer of LVM based guests
Message-ID: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>

I am investigating the procedure to follow when moving a
KVM guest instance from one host to another where the
guest uses LVM as its storage.  As a preliminary cut I
have cobbled the following together from various sources
located through Google searches:

1.  Log in to vmhost_old

2.  Shutdown guest

3.  Create an LVM snapshot of the guest volume
3.a.   lvcreate -s -L 300m -n LVM_guest_snapshot guest_lv

4.  Convert snapshot to a file image
4.a    dd if=/dev/vhost/LVM_guest_snapshot
          of=/tmp/fs/LVM_guest_snapshot.img bs=4096

5.  Remove the original snapshot
5.a    lvremove /dev/vhost/LVM_guest_snapshot

6.  Move the snapshot image file to the new KVM host. Note
that for large vm guest images tape transport is probably
better than network transfers.

7.  Log in to vhost_new

8.  Create a new lv on the new vhost
8.a    lvcreate -n guest_name_lv -L 60G vhost_new_vg

9.  Copy transferred image to new LV
9.a    dd if=tmp/LVM_guest_snapshot.img
       of=/dev/vhost_new/guest_name_lv bs=4096

10.  Copy guest xml file from vhost_old via sftp
10.a.   get /etc/libvirt/qemu/guest_name.xml \
           /etc/libvirt/qemu/guest_name.xml

11. Start new guest?


Is there anything obviously wrong or omitted from this?


-- 
***          E-Mail is NOT a SECURE channel          ***
James B. Byrne                mailto:ByrneJB at Harte-Lyne.ca
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3


From Ed at Heron-ent.com  Tue Nov 29 17:11:01 2011
From: Ed at Heron-ent.com (Ed Heron)
Date: Tue, 29 Nov 2011 15:11:01 -0700
Subject: [CentOS-virt] Transfer of LVM based guests
In-Reply-To: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
References: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
Message-ID: <1322604661.4811.13.camel@elap.rgtravel.com>

On Tue, 2011-11-29 at 15:51 -0500, James B. Byrne wrote:
> I am investigating the procedure to follow when moving a
> KVM guest instance from one host to another where the
> guest uses LVM as its storage.  As a preliminary cut I
> have cobbled the following together from various sources
> located through Google searches:
> ...

  If you are moving the virtual disk, you can't run the virtual machine while you are moving it.  Therefore, taking a snapshot (and removing it later) is superfluous.

  I use md5sum to give myself some extra re-assurance that a copy that big is accurate.

  Are the virtualization servers at the same location?

  How often do you move virtual machines?

  If your virtualization servers are in the same location, you might want to look into setting up a LAN for transferring virtual machine images.  It would only take an extra network card in each virtualization server and a Gb Ethernet switch (or better).

  If you are interested in virtual disk replication, you might want to look at DRBD.  It adds an extra layer to your storage, but allows for hot replication of disk space which would allow you to start a virtual machine on any virtualization server.



From byrnejb at harte-lyne.ca  Wed Nov 30 11:23:11 2011
From: byrnejb at harte-lyne.ca (James B. Byrne)
Date: Wed, 30 Nov 2011 11:23:11 -0500 (EST)
Subject: [CentOS-virt] Transfer of LVM based guests
In-Reply-To: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
References: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
Message-ID: <40363.216.185.71.25.1322670191.squirrel@webmail.harte-lyne.ca>


On Tue, November 29, 2011 17:11:01, Ed Heron Ed at
Heron-ent.com wrote:

> If you are moving the virtual disk, you can't run
> the virtual machine while you are moving it.
> Therefore, taking a snapshot (and removing it later)
> is superfluous.

Point taken.

> I use md5sum to give myself some extra re-assurance
> that a copy that big is accurate.

Good idea.

> Are the virtualization servers at the same location?

At the moment. It is planned that there will be two vhosts
at each of two different locations, one backing up the
other.

>  How often do you move virtual machines?

I have not moved any as of yet.  I am investigating how to
do this as part of setting up our first virtual server
host.  I am discovering what is possible and the
techniques used.  Moving vm guests is not being considered
for load balancing but is under consideration for
providing warm spares for use in a DR situation.

> If your virtualization servers are in the same
> location, you might want to look into setting up a
> LAN for transferring virtual machine images.  It
> would only take an extra network card in each
> virtualization server and a Gb Ethernet switch
> (or better).

Our vhosts all (will) have two nics, one for public IPs
and one for private IPs.  The private IPs are used for
vhost management.  The experimental vhost is so equipped.

> If you are interested in virtual disk replication,
> you might want to look at DRBD.  It adds an extra layer
> to your storage, but allows for hot replication of
> disk space which would allow you to start a virtual
> machine on any virtualization server.

This is a useful suggestion. However, I find that the
availability of a DRDB package on CentOS-6 is presently an
issue.  And, our vm project has already expanded into
multiple areas with commensurate delays.  I think that I
will leave DRDB for a later time.

So, what I now have for a proposed procedure is:

1.  Log in to vmhost_old

2.  Shutdown guest

3.  Convert guest lvs to file images for each lv
3.a    dd if=/dev/vhost/lv_vhost_guest
          of=/tmp/fs/lv_vhost_guest.img bs=4096

4.  Create MD5 hash for each image file
4.a    md5sum /tmp/fs/lv_vhost_guest.img > \
              /tmp/fs/lv_vhost_guest.md5

5.  Move the guest image file(s)  and the checksum file to
the new vhost; preserving both the directory structure and
file names or subsequently modifying the file names in the
md5 checksum file. Note that for large vm guest images
tape transport is probably better than network transfers.

6.  Log in to vhost_new

7.  Verify md5 checksum(s) on transferred file(s).
7.a    md5sum -c /tmp/fs/lv_vhost_guest.md5

8.  Create a new lv(s) on the new vhost. Ensure sufficient
size.
8.a    lvcreate -n lv_guest_name -L 60G vhost_new_vg

9.  Copy transferred image to new LV
9.a    dd if=/tmp/fs/lv_vhost_guest.img
       of=/dev/vhost_new/lv_guest_name bs=4096

10.  Copy guest xml file from vhost_old via sftp
10.a.   get /etc/libvirt/qemu/guest_name.xml \
           /etc/libvirt/qemu/guest_name.xml

11. Start new guest?


Thanks,


-- 
***          E-Mail is NOT a SECURE channel          ***
James B. Byrne                mailto:ByrneJB at Harte-Lyne.ca
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3


From raju.rajsand at gmail.com  Mon Nov  7 18:17:22 2011
From: raju.rajsand at gmail.com (Rajagopal Swaminathan)
Date: Mon, 7 Nov 2011 23:47:22 +0530
Subject: [CentOS-virt] P2V utility
Message-ID: <CA+YdgaqusA9ZR2ekkyXtkggKBsH73=HYe1c=XVTSnq7OQ_kq+Q@mail.gmail.com>

Greetings,

An somebody pint to me to P2V Utility for the m$ world?

Like in VMware?

-- 
Regards,

Rajagopal


From lorenzo at tulug.it  Tue Nov  8 14:20:52 2011
From: lorenzo at tulug.it (Lorenzo)
Date: Tue, 8 Nov 2011 15:20:52 +0100
Subject: [CentOS-virt] P2V utility
In-Reply-To: <CA+YdgaqusA9ZR2ekkyXtkggKBsH73=HYe1c=XVTSnq7OQ_kq+Q@mail.gmail.com>
References: <CA+YdgaqusA9ZR2ekkyXtkggKBsH73=HYe1c=XVTSnq7OQ_kq+Q@mail.gmail.com>
Message-ID: <CADE4e0WfAq++1UDq-Vj3EhR=K1=xQTwmU0qsVhLrXVKgy+SDhg@mail.gmail.com>

2011/11/7 Rajagopal Swaminathan <raju.rajsand at gmail.com>:
> Greetings,
>
> An somebody pint to me to P2V Utility for the m$ world?
>
> Like in VMware?
>
> --
> Regards,
>
> Rajagopal

Try here:
http://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE
not centos specific, but I found a lot of useful info.

Regards,
Lorenzo


From mdra137 at gmail.com  Fri Nov 18 13:39:23 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Fri, 18 Nov 2011 14:39:23 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0BmRWi7_=FEJ0WSTzs5J1-2wuJ_AZdN=_S8WKWg94E_Vg@mail.gmail.com>

Hi,

I've been using CentOS & Xen on a server that has 2 VM's configured. The
default configuration includes one physical iface that is propagated (by a
default bridge) to the VM's.

Since I wanted to configure additional physical iface, define a new bridge
and propagate it to the viface-s of the VM's, i configured the bridge/phys.
iface and brought it up (here are configurations that I set up):

-> eth3
DEVICE=eth3
BOOTPROTO=static
HWADDR=D4:85:64:4B:76:AB
ONBOOT=yes
#HOTPLUG=no
#DHCP_HOSTNAME=kdr-3k-4r-3o-07
BRIDGE=br0
TYPE=Ethernet

-> br0
DEVICE=br0
TYPE=Bridge
BOOTPROTO=none
ONBOOT=yes

Then I configured new virt. ifaces on VM's (using virsh edit, config is
listed below):

<interface type='bridge'>
<mac address='00:16:36:17:62:5d'/>
<source bridge='xenbr0'/>
<script path='vif-bridge'/>
<target dev='vif5.0'/>
</interface>
<interface type='bridge'>
<mac address='00:16:3e:ca:63:39'/>
<source bridge='br0'/>
<script path='vif-bridge'/>
<target dev='vif5.1'/>
</interface>

You can see the default bridge (xenbr0 -> vif5.0) and my new bridge br0
connected to vif5.1.

So, here I got stuck up - when I try tu start a VM (xm create VIRT_SRV),
the VM starts booting but hangs up (I can ping it form another srv., but
when I try SSH it says "connection refused"). When I remove configuration
for vif5.1 the VM starts up normally. I actually managed to start VM with
vif5.1 up once, but next time I restarted it, the problem was there :/


Furthermore, I noticed this in the Xen log:

[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vif.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 0.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vif/1/1/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices usb.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vbd.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 768.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vbd/1/768/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 5632.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vbd/1/5632/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices irq.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vkbd.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vfb.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices pci.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices ioports.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices tap.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vtpm.

So the boot process goes on regulary until the last line ("Waiting for
devices vtpm"). It seems like TPM makes it impossible for VM's to start
regulary. When I open the VM's console (with virt-manager) I see the whole
boot process but it hangs when it tries to start iface eth2 (attached to
the second bridge) ...

Does anybody have a clue why is this happening?

Thanks in advance ..
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111118/e056a2eb/attachment-0002.html>

From peter.peltonen at gmail.com  Fri Nov 18 14:33:35 2011
From: peter.peltonen at gmail.com (Peter Peltonen)
Date: Fri, 18 Nov 2011 16:33:35 +0200
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
In-Reply-To: <CALZem0BmRWi7_=FEJ0WSTzs5J1-2wuJ_AZdN=_S8WKWg94E_Vg@mail.gmail.com>
References: <CALZem0BmRWi7_=FEJ0WSTzs5J1-2wuJ_AZdN=_S8WKWg94E_Vg@mail.gmail.com>
Message-ID: <CAGTVFvHkhkUytpf9ei2vGT0_NhLsOhXikDPV9ORAKYitttjCdA@mail.gmail.com>

Hi,

2011/11/18 Matija Draganovi? <mdra137 at gmail.com>:
> I've been using CentOS & Xen on a server that has 2 VM's configured. The
> default configuration includes one physical iface that is propagated (by a
> default bridge) to the VM's.

You do not mention which version of CentOS and Xen you are using?

>
> Since I wanted to configure additional physical iface, define a new bridge
> and propagate it to the viface-s of the VM's, i configured the bridge/phys.
> iface and brought it up (here are configurations that I set up):
>
> -> eth3
> DEVICE=eth3
> BOOTPROTO=static
> HWADDR=D4:85:64:4B:76:AB
> ONBOOT=yes
> #HOTPLUG=no
> #DHCP_HOSTNAME=kdr-3k-4r-3o-07
> BRIDGE=br0
> TYPE=Ethernet
>
> -> br0
> DEVICE=br0
> TYPE=Bridge
> BOOTPROTO=none
> ONBOOT=yes

If this is a CentOS5 machine with the CentOS provided Xen 3.0
packages, then here is info how i got my bridges to work with that
setup:

* For dom0 I configured eth0 and eth1 as usual in /etc/sysconfig/network-scripts

* I did not configure br0 or br1 in network-scripts, but instead I
created a file called /etc/xen/scripts/my-network-script having this
contents:

#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0
"$dir/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=xenbr1

* Then I modified in dom0 the file /etc/xen/xend-config.sxp in the
following way:

#(network-script network-bridge)
(network-script my-network-script)

* Now rebooting dom0 made the bridges available

* After that I could configure them in my domU config:

vif = [ "mac=00:16:3E:69:29:25,bridge=xenbr0,script=vif-bridge","mac=00:16:3E:E6:B0:6D,bridge=xenbr1,script=vif-bridge"
]

* After starting the domU I could configure the interfaces in
network-scripts using the hardware addresses specified in the domU
config


It seems that configuring bridging is done a bit differently in
different Xen versions, so this might not work if you are using some
other kind of config. With CentOS6 and 3rd party Xen 4.1 packages this
procedure did not work at all and instead I needed to do the
following:

* in dom0 create the br0 and br1 devices in network-scripts

* in dom0 /etc/xen/xend-config.sxp put instead:

#(network-script network-bridge)
(network-script /bin/true)

* and in dom0 use different configuration for the domU config files like this:

vif = [ "mac=00:16:3E:69:29:25,bridge=br0","mac=00:16:3E:E6:B0:6D,bridge=br1" ]


Hope this helps, unfortuantely I am not familiar with virsh at all.

Best,
Peter


From mdra137 at gmail.com  Fri Nov 18 17:17:17 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Fri, 18 Nov 2011 18:17:17 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0D1Z-dbkvM+-0+DgVGSGd_dHa757rSqMUZcAgCfffstwQ@mail.gmail.com>

Dear Peter,


Thanks for your reply. I was so occupied with troubleshooting that I forgot
to mention the OS & Xen version :)

My CentOS version is
CentOS release 5.7 (Final)
Linux 2.6.18-274.7.1.el5xen #1 SMP Thu Oct 20 17:06:34 EDT 2011 x86_64
x86_64 x86_64 GNU/Linux

and Xen v3.0.

I tried creating bridges the same way you did and succedded. I also tried
doing the same via ifcfg scripts, and it also worked.

I have no problem with creating bridges and connecting them with physical
ifaces, but I can't start my VM's (most of the time one VM start but the
other one hangs while trying to initalize eth2 that is connected to my
second (non default - xenbr1) bridge)).

The only diference between your config and mine is that I have vifname-s
listed (example below):

vif = [
"mac=00:16:36:72:35:e5,bridge=xenbr0,script=vif-bridge,vifname=vif4.0",
"mac=00:16:3e:57:de:0d,bridge=xenbr1,script=vif-bridge, vifname=vif4.1" ]

I'm not saying that this could be the problem, but since I'm slowly running
out of ideas - it's a longshot :)

So, to sum it all up - I can create bridges properly, but my VM's hang when
they try to bring up vifaces connected to the xenbr1. Also, I have no
problem with having only one bridge active - problem appears when I have
multiple bridges.

Br,
Matija
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111118/2a75ed85/attachment-0002.html>

From maillists at conactive.com  Fri Nov 18 18:33:20 2011
From: maillists at conactive.com (Kai Schaetzl)
Date: Fri, 18 Nov 2011 19:33:20 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
In-Reply-To: <CALZem0D1Z-dbkvM+-0+DgVGSGd_dHa757rSqMUZcAgCfffstwQ@mail.gmail.com>
References: <CALZem0D1Z-dbkvM+-0+DgVGSGd_dHa757rSqMUZcAgCfffstwQ@mail.gmail.com>
Message-ID: <VA.00003db7.1907ac90@news.conactive.com>

Matija Draganovi? wrote on Fri, 18 Nov 2011 18:17:17 +0100:

> The only diference between your config and mine is that I have vifname-s
> listed

Then remove it. I've never seen it like that. If I remember it correctly 
the vifnames are created dynamically. You can't rely on them I suppose.

And I don't remember using "script" either.

If you can't get it to work then use the second method Peter describes. 
That one should also work for Xen 3.0 and is guaranteed to create stable 
bridging.



Kai

-- 
Get your web at Conactive Internet Services: http://www.conactive.com





From jason at daylife.com  Fri Nov 18 22:56:02 2011
From: jason at daylife.com (Jason Nagashima)
Date: Fri, 18 Nov 2011 17:56:02 -0500 (EST)
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <1331504081.4540.1321656727740.JavaMail.root@mailbox01.hq.daylife.com>
Message-ID: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>

Running on Centos 5.6 with KVM... 

I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?

I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it.  There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.

Any advice/working examples would be greatly appreciated.

Regards,
Jason


From incoming-centos at rjl.com  Sat Nov 19 04:34:25 2011
From: incoming-centos at rjl.com (Nataraj)
Date: Fri, 18 Nov 2011 20:34:25 -0800
Subject: [CentOS-virt] high resolution video for kvm vm
Message-ID: <4EC731D1.40109@rjl.com>

I'm running a fuduntu vm (based on fedora 14)  on a CentOS 6 kvm
server.  I have tried changing the video in virt-manager from cirrus to
vga and restarting the VM, but the maximum resolution that the client
will let me set is still only 1024x768.  Should I be able to get  high
res video with the kvm VGA mode?  Note that the VM is running on a
CentOS server while virt-manager is running on my local desktop.

Would I be better off trying to get the vmware VGA driver working?  I'm
assuming I have to extract the driver from the vmware tools package and
manually install it into the X server, because VMware tools won't
install under kvm.

Also, I run with the keyboard option to swap caps lock and control on my
linux desktop, which does not seem to get passed through to the guest. 
I tried setting the same swap caps lock and control option in the guest,
but it does not work.  Any ideas?

Thanks,
Nataraj



From mdra137 at gmail.com  Sat Nov 19 06:32:21 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Sat, 19 Nov 2011 07:32:21 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0A+hx+b2OFOEYD-YdpXxV9Y=jFUP=UTjgFLBqBqca78YQ@mail.gmail.com>

I tried to remove vifname and vif-script but the problem remains. I think
that the bridges are ok, but for some reason VM's hang when they try to
connect their vifaces to them.

I'll try some different configurations of the physical ifaces (an vifaces
also), maybe I'll be able to find out something. Also, I'll focus on the
vTPM, since the following line shows up in the Xen log when the VM tries to
bring up the iface connected to the second bridge:

[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vtpm


Furthermore, it appears that sometimes the VM's manage to start regulary, I
just can't figure out when & why :/

Tnx for your comments ..

Br,
M.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111119/cc41e78f/attachment-0002.html>

From mdra137 at gmail.com  Tue Nov 22 09:37:31 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Tue, 22 Nov 2011 10:37:31 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0AS0ptzxMRXooEFHLCAR=OCnaFcXS5AcMmQduevWSFjrQ@mail.gmail.com>

Ok, after trying multiple different configurations I decided to play by the
book - I removed ifcfg script for creating the additional bridge and set up
an Xen script. So my new configuration is:

-> eth3 (my physical interface)
# NetXen Incorporated NX3031 Multifunction 1/10-Gigabit Server Adapter
DEVICE=eth3
BOOTPROTO=static
HWADDR= ...
ONBOOT=yes
IPADDR= ...
NETMASK= ...
NETWORK= ...

and the network-xen-multi-bridge script:

#!/bin/sh
# network-xen-multi-bridge
# Exit if anything goes wrong.
set -e
# First arg is the operation.
OP=$1
shift
script=/etc/xen/scripts/network-bridge.xen
case ${OP} in
start)
$script start vifnum=3 bridge=xenbr3 netdev=eth3
$script start vifnum=0 bridge=xenbr0 netdev=eth0
;;
stop)
$script stop vifnum=3 bridge=xenbr3 netdev=eth3
$script stop vifnum=0 bridge=xenbr0 netdev=eth0
;;
status)
$script status vifnum=3 bridge=xenbr3 netdev=eth3
$script status vifnum=0 bridge=xenbr0 netdev=eth0
;;
*)
echo 'Unknown command: ' ${OP}
echo 'Valid commands are: start, stop, status'
exit 1
esac

After I restart the physical server bridges are set up correctly:

# brctl show
bridge name bridge id STP enabled interfaces
virbr0 8000.000000000000 yes
xenbr0 8000.feffffffffff no vif0.0
peth0
xenbr3 8000.feffffffffff no vif0.3
peth3

Unfortunately, this did not solve the problem - I manage to start one VM
(connected to both of the bridges), but when I try to start the other one,
it just hangs when trying to bring up the second interface (connected to
xenbr3) :/

I'm currently completely out of ideas, but I'm not giving up ;)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111122/eb760bb6/attachment-0002.html>

From tait at taiter.com  Tue Nov 22 16:07:54 2011
From: tait at taiter.com (Tait Clarridge)
Date: Tue, 22 Nov 2011 11:07:54 -0500
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>
References: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>
Message-ID: <1321978074.22491.12.camel@tclarrltp.frontiernetworks.ca>

On Fri, 2011-11-18 at 17:56 -0500, Jason Nagashima wrote:
> Running on Centos 5.6 with KVM... 
> 
> I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?
> 
> I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it.  There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.
> 
> Any advice/working examples would be greatly appreciated.

Hi Jason,

I have had luck doing this with Xen, where I create bond0 on a trunk
interface and have xen bring it up as xenbr0 with pbond0 in the back
end.

You should be able to do roughly the same by creating a bridge interface
in /etc/sysconfig/network-scripts referencing bond0 as a member.

After that you should be able to run a script to create VLAN bridges
like the following:

#!/bin/bash
/sbin/modprobe 8021q

# Add your vlans here that you want with the numbers separated by a 
# space
VLANS="5 10 15 20"
# This should work with the bonding interface
TRUNKINT="bond0"
for VLAN in $VLANS
do
	vconfig add $TRUNKINT $VLAN
	brctl add br$VLAN
	brctl addif br$VLAN $TRUNKINT.$VLAN
	ifconfig $TRUNKINT.$VLAN up
	ifconfig br$VLAN up
done

I have done this with Xen on 5.5, 5.6 and 5.7... but it should work for
KVM. If you create the standard bridge interface br0 using just bond0
that will get you a trunk on whatever the native vlan is for that trunk.

Tait




From dmartls1 at gmail.com  Tue Nov 22 17:39:02 2011
From: dmartls1 at gmail.com (David Martin)
Date: Tue, 22 Nov 2011 11:39:02 -0600
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <1321978074.22491.12.camel@tclarrltp.frontiernetworks.ca>
References: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>
	<1321978074.22491.12.camel@tclarrltp.frontiernetworks.ca>
Message-ID: <CAAsqWCd+KWrX-SpRcYVNzCVC4HDV25C1QeOZzu-ChN0ZHyhdBw@mail.gmail.com>

We are doing this quite a bit in production and it works great.

bond as you normally would:
DEVICE=bond0
ONBOOT=yes
USERCTL=no
BONDING_OPTS="mode=4 miimon=100"

one of these for each vlan (in this case 50):
VLAN=yes
VLAN_NAME_TYPE=VLAN_PLUS_VID_NO_PAD
DEVICE=vlan50
PHYSDEV=bond0
TYPE=Ethernet
ONBOOT=yes
BRIDGE=br50

and finally the bridge device to expose to guests:
DEVICE=br50
TYPE=Bridge
ONBOOT=yes
DELAY=0
GATEWAYDEV=none




On Tue, Nov 22, 2011 at 10:07 AM, Tait Clarridge <tait at taiter.com> wrote:
> On Fri, 2011-11-18 at 17:56 -0500, Jason Nagashima wrote:
>> Running on Centos 5.6 with KVM...
>>
>> I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?
>>
>> I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it. ?There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.
>>
>> Any advice/working examples would be greatly appreciated.
>
> Hi Jason,
>
> I have had luck doing this with Xen, where I create bond0 on a trunk
> interface and have xen bring it up as xenbr0 with pbond0 in the back
> end.
>
> You should be able to do roughly the same by creating a bridge interface
> in /etc/sysconfig/network-scripts referencing bond0 as a member.
>
> After that you should be able to run a script to create VLAN bridges
> like the following:
>
> #!/bin/bash
> /sbin/modprobe 8021q
>
> # Add your vlans here that you want with the numbers separated by a
> # space
> VLANS="5 10 15 20"
> # This should work with the bonding interface
> TRUNKINT="bond0"
> for VLAN in $VLANS
> do
> ? ? ? ?vconfig add $TRUNKINT $VLAN
> ? ? ? ?brctl add br$VLAN
> ? ? ? ?brctl addif br$VLAN $TRUNKINT.$VLAN
> ? ? ? ?ifconfig $TRUNKINT.$VLAN up
> ? ? ? ?ifconfig br$VLAN up
> done
>
> I have done this with Xen on 5.5, 5.6 and 5.7... but it should work for
> KVM. If you create the standard bridge interface br0 using just bond0
> that will get you a trunk on whatever the native vlan is for that trunk.
>
> Tait
>
>
> _______________________________________________
> CentOS-virt mailing list
> CentOS-virt at centos.org
> http://lists.centos.org/mailman/listinfo/centos-virt
>


From jason at daylife.com  Wed Nov 23 21:49:56 2011
From: jason at daylife.com (Jason Nagashima)
Date: Wed, 23 Nov 2011 16:49:56 -0500 (EST)
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <CAAsqWCd+KWrX-SpRcYVNzCVC4HDV25C1QeOZzu-ChN0ZHyhdBw@mail.gmail.com>
Message-ID: <206550579.4866.1322084996341.JavaMail.root@mailbox01.hq.daylife.com>

Awesome!

Thank you everyone for responding and helping out. I'm happy to report that we got it working!

Cheers,
Jason

----- Original Message -----
From: "David Martin" <dmartls1 at gmail.com>
To: "Discussion about the virtualization on CentOS" <centos-virt at centos.org>
Sent: Tuesday, November 22, 2011 12:39:02 PM
Subject: Re: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6

We are doing this quite a bit in production and it works great.

bond as you normally would:
DEVICE=bond0
ONBOOT=yes
USERCTL=no
BONDING_OPTS="mode=4 miimon=100"

one of these for each vlan (in this case 50):
VLAN=yes
VLAN_NAME_TYPE=VLAN_PLUS_VID_NO_PAD
DEVICE=vlan50
PHYSDEV=bond0
TYPE=Ethernet
ONBOOT=yes
BRIDGE=br50

and finally the bridge device to expose to guests:
DEVICE=br50
TYPE=Bridge
ONBOOT=yes
DELAY=0
GATEWAYDEV=none




On Tue, Nov 22, 2011 at 10:07 AM, Tait Clarridge <tait at taiter.com> wrote:
> On Fri, 2011-11-18 at 17:56 -0500, Jason Nagashima wrote:
>> Running on Centos 5.6 with KVM...
>>
>> I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?
>>
>> I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it. ?There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.
>>
>> Any advice/working examples would be greatly appreciated.
>
> Hi Jason,
>
> I have had luck doing this with Xen, where I create bond0 on a trunk
> interface and have xen bring it up as xenbr0 with pbond0 in the back
> end.
>
> You should be able to do roughly the same by creating a bridge interface
> in /etc/sysconfig/network-scripts referencing bond0 as a member.
>
> After that you should be able to run a script to create VLAN bridges
> like the following:
>
> #!/bin/bash
> /sbin/modprobe 8021q
>
> # Add your vlans here that you want with the numbers separated by a
> # space
> VLANS="5 10 15 20"
> # This should work with the bonding interface
> TRUNKINT="bond0"
> for VLAN in $VLANS
> do
> ? ? ? ?vconfig add $TRUNKINT $VLAN
> ? ? ? ?brctl add br$VLAN
> ? ? ? ?brctl addif br$VLAN $TRUNKINT.$VLAN
> ? ? ? ?ifconfig $TRUNKINT.$VLAN up
> ? ? ? ?ifconfig br$VLAN up
> done
>
> I have done this with Xen on 5.5, 5.6 and 5.7... but it should work for
> KVM. If you create the standard bridge interface br0 using just bond0
> that will get you a trunk on whatever the native vlan is for that trunk.
>
> Tait
>
>
> _______________________________________________
> CentOS-virt mailing list
> CentOS-virt at centos.org
> http://lists.centos.org/mailman/listinfo/centos-virt
>
_______________________________________________
CentOS-virt mailing list
CentOS-virt at centos.org
http://lists.centos.org/mailman/listinfo/centos-virt


From mdra137 at gmail.com  Fri Nov 25 11:11:44 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Fri, 25 Nov 2011 12:11:44 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0BCpJuchqLS6vws9Sm+_YPbR3AkLVyiKBQpJAPDGvzSGQ@mail.gmail.com>

Finally, I managed to solve the problem. The problem was rather strange -
after configuring bridges I added new ifaces to the VM. For some reason,
during boot process of the VM's, wrong interface was started (VM tried to
bring up eth2 instead eth1?).

After adding the new ifaces through virt-manager, the VM started regulary
and created a new network script for eth2
(/etc/sysconfig/network-scripts/ifcfg-eth2). I think that the problem was
this - when the VM is restarted it tried to bring up eth2 while vif-script
tried to propagate second bridge via eth1 iface. I resolved this simply by
replacing ifcfg-eth2 script with ifcfg-eth1. Now, VM starts/restarts
regulary ;)

So, the process for creating and configuring new bridges that I follow is
(tried on multiple servers):

- create new script that sets up multiple bridges in /etc/xen/scripts/

example: network-xen-multi-bridge

#!/bin/sh
# network-xen-multi-bridge
# Exit if anything goes wrong.
set -e
# First arg is the operation.
OP=$1
shift
script=/etc/xen/scripts/network-bridge.xen
case ${OP} in
start)
        $script start vifnum=3 bridge=xenbr3 netdev=eth3
        $script start vifnum=0 bridge=xenbr0 netdev=eth0
        ;;
stop)
        $script stop vifnum=3 bridge=xenbr3 netdev=eth3
        $script stop vifnum=0 bridge=xenbr0 netdev=eth0
        ;;
status)
        $script status vifnum=3 bridge=xenbr3 netdev=eth3
        $script status vifnum=0 bridge=xenbr0 netdev=eth0
        ;;
*)
        echo 'Unknown command: ' ${OP}
        echo 'Valid commands are: start, stop, status'
        exit 1
esac



- make it executable (chmod 755 network-xen-multi-bridge)

- configure /etc/xen/xend-config.sxp (comment out the current script and
add the new one);

# It is possible to use the network-bridge script in more complicated
# scenarios, such as having two outgoing interfaces, with two bridges, and
# two fake interfaces per guest domain.  To do things like this, write
# yourself a wrapper script, and call network-bridge from it, as appropriate.
#
#(network-script network-bridge)
(network-script  network-xen-multi-bridge)



- restart physical server so the bridges are properly created

- add virt. ifaces to the VM's (via virt-manager or via config. files in
/etc/xen/ ..)

- boot VM

- configure newly added iface in /etc/sysconfig/network-scripts/

- restart VM

Additionaly I check everything by restarting phys. server to make sure that
everything is ok ;)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111125/1304c71b/attachment-0002.html>

From mail-lists at karan.org  Sat Nov 26 00:29:20 2011
From: mail-lists at karan.org (Karanbir Singh)
Date: Sat, 26 Nov 2011 00:29:20 +0000
Subject: [CentOS-virt] Device renaming heads up
Message-ID: <4ED032E0.1040109@karan.org>

hi Guys,

Just in case anyone hasent noticed this :
https://bugzilla.redhat.com/show_bug.cgi?id=729586 device naming mixup
causing lots of domU's to not come back after a kernel update...

- KB


From toddandmargo at gmail.com  Mon Nov 28 18:37:50 2011
From: toddandmargo at gmail.com (Todd And Margo Chester)
Date: Mon, 28 Nov 2011 10:37:50 -0800
Subject: [CentOS-virt] kvm: w7 bsod's at shutdown
Message-ID: <4ED3D4FE.9090008@gmail.com>

Hi All,

I am using Scientific Linux 6.1 x64

Any idea how to get my W7 x32 guest to shutdown with out a BSOD?
I have to go into virt-manager and kill it all the time.  My XP guest
shuts down without issue.

Many thanks,
-T

$ rpm -qa \*kvm\*
qemu-kvm-0.12.1.2-2.160.el6_1.2.x86_64

$ rpm -qa \*virt\*
python-virtinst-0.500.5-3.el6.noarch
libvirt-0.8.7-18.el6_1.1.x86_64
libvirt-client-0.8.7-18.el6_1.1.x86_64
virt-manager-0.8.6-4.el6.noarch
libvirt-python-0.8.7-18.el6_1.1.x86_64



From byrnejb at harte-lyne.ca  Tue Nov 29 20:51:45 2011
From: byrnejb at harte-lyne.ca (James B. Byrne)
Date: Tue, 29 Nov 2011 15:51:45 -0500 (EST)
Subject: [CentOS-virt] Transfer of LVM based guests
Message-ID: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>

I am investigating the procedure to follow when moving a
KVM guest instance from one host to another where the
guest uses LVM as its storage.  As a preliminary cut I
have cobbled the following together from various sources
located through Google searches:

1.  Log in to vmhost_old

2.  Shutdown guest

3.  Create an LVM snapshot of the guest volume
3.a.   lvcreate -s -L 300m -n LVM_guest_snapshot guest_lv

4.  Convert snapshot to a file image
4.a    dd if=/dev/vhost/LVM_guest_snapshot
          of=/tmp/fs/LVM_guest_snapshot.img bs=4096

5.  Remove the original snapshot
5.a    lvremove /dev/vhost/LVM_guest_snapshot

6.  Move the snapshot image file to the new KVM host. Note
that for large vm guest images tape transport is probably
better than network transfers.

7.  Log in to vhost_new

8.  Create a new lv on the new vhost
8.a    lvcreate -n guest_name_lv -L 60G vhost_new_vg

9.  Copy transferred image to new LV
9.a    dd if=tmp/LVM_guest_snapshot.img
       of=/dev/vhost_new/guest_name_lv bs=4096

10.  Copy guest xml file from vhost_old via sftp
10.a.   get /etc/libvirt/qemu/guest_name.xml \
           /etc/libvirt/qemu/guest_name.xml

11. Start new guest?


Is there anything obviously wrong or omitted from this?


-- 
***          E-Mail is NOT a SECURE channel          ***
James B. Byrne                mailto:ByrneJB at Harte-Lyne.ca
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3



From Ed at Heron-ent.com  Tue Nov 29 22:11:01 2011
From: Ed at Heron-ent.com (Ed Heron)
Date: Tue, 29 Nov 2011 15:11:01 -0700
Subject: [CentOS-virt] Transfer of LVM based guests
In-Reply-To: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
References: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
Message-ID: <1322604661.4811.13.camel@elap.rgtravel.com>

On Tue, 2011-11-29 at 15:51 -0500, James B. Byrne wrote:
> I am investigating the procedure to follow when moving a
> KVM guest instance from one host to another where the
> guest uses LVM as its storage.  As a preliminary cut I
> have cobbled the following together from various sources
> located through Google searches:
> ...

  If you are moving the virtual disk, you can't run the virtual machine while you are moving it.  Therefore, taking a snapshot (and removing it later) is superfluous.

  I use md5sum to give myself some extra re-assurance that a copy that big is accurate.

  Are the virtualization servers at the same location?

  How often do you move virtual machines?

  If your virtualization servers are in the same location, you might want to look into setting up a LAN for transferring virtual machine images.  It would only take an extra network card in each virtualization server and a Gb Ethernet switch (or better).

  If you are interested in virtual disk replication, you might want to look at DRBD.  It adds an extra layer to your storage, but allows for hot replication of disk space which would allow you to start a virtual machine on any virtualization server.




From byrnejb at harte-lyne.ca  Wed Nov 30 16:23:11 2011
From: byrnejb at harte-lyne.ca (James B. Byrne)
Date: Wed, 30 Nov 2011 11:23:11 -0500 (EST)
Subject: [CentOS-virt] Transfer of LVM based guests
In-Reply-To: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
References: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
Message-ID: <40363.216.185.71.25.1322670191.squirrel@webmail.harte-lyne.ca>


On Tue, November 29, 2011 17:11:01, Ed Heron Ed at
Heron-ent.com wrote:

> If you are moving the virtual disk, you can't run
> the virtual machine while you are moving it.
> Therefore, taking a snapshot (and removing it later)
> is superfluous.

Point taken.

> I use md5sum to give myself some extra re-assurance
> that a copy that big is accurate.

Good idea.

> Are the virtualization servers at the same location?

At the moment. It is planned that there will be two vhosts
at each of two different locations, one backing up the
other.

>  How often do you move virtual machines?

I have not moved any as of yet.  I am investigating how to
do this as part of setting up our first virtual server
host.  I am discovering what is possible and the
techniques used.  Moving vm guests is not being considered
for load balancing but is under consideration for
providing warm spares for use in a DR situation.

> If your virtualization servers are in the same
> location, you might want to look into setting up a
> LAN for transferring virtual machine images.  It
> would only take an extra network card in each
> virtualization server and a Gb Ethernet switch
> (or better).

Our vhosts all (will) have two nics, one for public IPs
and one for private IPs.  The private IPs are used for
vhost management.  The experimental vhost is so equipped.

> If you are interested in virtual disk replication,
> you might want to look at DRBD.  It adds an extra layer
> to your storage, but allows for hot replication of
> disk space which would allow you to start a virtual
> machine on any virtualization server.

This is a useful suggestion. However, I find that the
availability of a DRDB package on CentOS-6 is presently an
issue.  And, our vm project has already expanded into
multiple areas with commensurate delays.  I think that I
will leave DRDB for a later time.

So, what I now have for a proposed procedure is:

1.  Log in to vmhost_old

2.  Shutdown guest

3.  Convert guest lvs to file images for each lv
3.a    dd if=/dev/vhost/lv_vhost_guest
          of=/tmp/fs/lv_vhost_guest.img bs=4096

4.  Create MD5 hash for each image file
4.a    md5sum /tmp/fs/lv_vhost_guest.img > \
              /tmp/fs/lv_vhost_guest.md5

5.  Move the guest image file(s)  and the checksum file to
the new vhost; preserving both the directory structure and
file names or subsequently modifying the file names in the
md5 checksum file. Note that for large vm guest images
tape transport is probably better than network transfers.

6.  Log in to vhost_new

7.  Verify md5 checksum(s) on transferred file(s).
7.a    md5sum -c /tmp/fs/lv_vhost_guest.md5

8.  Create a new lv(s) on the new vhost. Ensure sufficient
size.
8.a    lvcreate -n lv_guest_name -L 60G vhost_new_vg

9.  Copy transferred image to new LV
9.a    dd if=/tmp/fs/lv_vhost_guest.img
       of=/dev/vhost_new/lv_guest_name bs=4096

10.  Copy guest xml file from vhost_old via sftp
10.a.   get /etc/libvirt/qemu/guest_name.xml \
           /etc/libvirt/qemu/guest_name.xml

11. Start new guest?


Thanks,


-- 
***          E-Mail is NOT a SECURE channel          ***
James B. Byrne                mailto:ByrneJB at Harte-Lyne.ca
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3



From raju.rajsand at gmail.com  Mon Nov  7 18:17:22 2011
From: raju.rajsand at gmail.com (Rajagopal Swaminathan)
Date: Mon, 7 Nov 2011 23:47:22 +0530
Subject: [CentOS-virt] P2V utility
Message-ID: <CA+YdgaqusA9ZR2ekkyXtkggKBsH73=HYe1c=XVTSnq7OQ_kq+Q@mail.gmail.com>

Greetings,

An somebody pint to me to P2V Utility for the m$ world?

Like in VMware?

-- 
Regards,

Rajagopal


From lorenzo at tulug.it  Tue Nov  8 14:20:52 2011
From: lorenzo at tulug.it (Lorenzo)
Date: Tue, 8 Nov 2011 15:20:52 +0100
Subject: [CentOS-virt] P2V utility
In-Reply-To: <CA+YdgaqusA9ZR2ekkyXtkggKBsH73=HYe1c=XVTSnq7OQ_kq+Q@mail.gmail.com>
References: <CA+YdgaqusA9ZR2ekkyXtkggKBsH73=HYe1c=XVTSnq7OQ_kq+Q@mail.gmail.com>
Message-ID: <CADE4e0WfAq++1UDq-Vj3EhR=K1=xQTwmU0qsVhLrXVKgy+SDhg@mail.gmail.com>

2011/11/7 Rajagopal Swaminathan <raju.rajsand at gmail.com>:
> Greetings,
>
> An somebody pint to me to P2V Utility for the m$ world?
>
> Like in VMware?
>
> --
> Regards,
>
> Rajagopal

Try here:
http://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE
not centos specific, but I found a lot of useful info.

Regards,
Lorenzo


From mdra137 at gmail.com  Fri Nov 18 13:39:23 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Fri, 18 Nov 2011 14:39:23 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0BmRWi7_=FEJ0WSTzs5J1-2wuJ_AZdN=_S8WKWg94E_Vg@mail.gmail.com>

Hi,

I've been using CentOS & Xen on a server that has 2 VM's configured. The
default configuration includes one physical iface that is propagated (by a
default bridge) to the VM's.

Since I wanted to configure additional physical iface, define a new bridge
and propagate it to the viface-s of the VM's, i configured the bridge/phys.
iface and brought it up (here are configurations that I set up):

-> eth3
DEVICE=eth3
BOOTPROTO=static
HWADDR=D4:85:64:4B:76:AB
ONBOOT=yes
#HOTPLUG=no
#DHCP_HOSTNAME=kdr-3k-4r-3o-07
BRIDGE=br0
TYPE=Ethernet

-> br0
DEVICE=br0
TYPE=Bridge
BOOTPROTO=none
ONBOOT=yes

Then I configured new virt. ifaces on VM's (using virsh edit, config is
listed below):

<interface type='bridge'>
<mac address='00:16:36:17:62:5d'/>
<source bridge='xenbr0'/>
<script path='vif-bridge'/>
<target dev='vif5.0'/>
</interface>
<interface type='bridge'>
<mac address='00:16:3e:ca:63:39'/>
<source bridge='br0'/>
<script path='vif-bridge'/>
<target dev='vif5.1'/>
</interface>

You can see the default bridge (xenbr0 -> vif5.0) and my new bridge br0
connected to vif5.1.

So, here I got stuck up - when I try tu start a VM (xm create VIRT_SRV),
the VM starts booting but hangs up (I can ping it form another srv., but
when I try SSH it says "connection refused"). When I remove configuration
for vif5.1 the VM starts up normally. I actually managed to start VM with
vif5.1 up once, but next time I restarted it, the problem was there :/


Furthermore, I noticed this in the Xen log:

[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vif.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 0.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vif/1/1/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices usb.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vbd.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 768.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vbd/1/768/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 5632.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vbd/1/5632/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices irq.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vkbd.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vfb.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices pci.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices ioports.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices tap.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vtpm.

So the boot process goes on regulary until the last line ("Waiting for
devices vtpm"). It seems like TPM makes it impossible for VM's to start
regulary. When I open the VM's console (with virt-manager) I see the whole
boot process but it hangs when it tries to start iface eth2 (attached to
the second bridge) ...

Does anybody have a clue why is this happening?

Thanks in advance ..
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111118/e056a2eb/attachment-0003.html>

From peter.peltonen at gmail.com  Fri Nov 18 14:33:35 2011
From: peter.peltonen at gmail.com (Peter Peltonen)
Date: Fri, 18 Nov 2011 16:33:35 +0200
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
In-Reply-To: <CALZem0BmRWi7_=FEJ0WSTzs5J1-2wuJ_AZdN=_S8WKWg94E_Vg@mail.gmail.com>
References: <CALZem0BmRWi7_=FEJ0WSTzs5J1-2wuJ_AZdN=_S8WKWg94E_Vg@mail.gmail.com>
Message-ID: <CAGTVFvHkhkUytpf9ei2vGT0_NhLsOhXikDPV9ORAKYitttjCdA@mail.gmail.com>

Hi,

2011/11/18 Matija Draganovi? <mdra137 at gmail.com>:
> I've been using CentOS & Xen on a server that has 2 VM's configured. The
> default configuration includes one physical iface that is propagated (by a
> default bridge) to the VM's.

You do not mention which version of CentOS and Xen you are using?

>
> Since I wanted to configure additional physical iface, define a new bridge
> and propagate it to the viface-s of the VM's, i configured the bridge/phys.
> iface and brought it up (here are configurations that I set up):
>
> -> eth3
> DEVICE=eth3
> BOOTPROTO=static
> HWADDR=D4:85:64:4B:76:AB
> ONBOOT=yes
> #HOTPLUG=no
> #DHCP_HOSTNAME=kdr-3k-4r-3o-07
> BRIDGE=br0
> TYPE=Ethernet
>
> -> br0
> DEVICE=br0
> TYPE=Bridge
> BOOTPROTO=none
> ONBOOT=yes

If this is a CentOS5 machine with the CentOS provided Xen 3.0
packages, then here is info how i got my bridges to work with that
setup:

* For dom0 I configured eth0 and eth1 as usual in /etc/sysconfig/network-scripts

* I did not configure br0 or br1 in network-scripts, but instead I
created a file called /etc/xen/scripts/my-network-script having this
contents:

#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0
"$dir/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=xenbr1

* Then I modified in dom0 the file /etc/xen/xend-config.sxp in the
following way:

#(network-script network-bridge)
(network-script my-network-script)

* Now rebooting dom0 made the bridges available

* After that I could configure them in my domU config:

vif = [ "mac=00:16:3E:69:29:25,bridge=xenbr0,script=vif-bridge","mac=00:16:3E:E6:B0:6D,bridge=xenbr1,script=vif-bridge"
]

* After starting the domU I could configure the interfaces in
network-scripts using the hardware addresses specified in the domU
config


It seems that configuring bridging is done a bit differently in
different Xen versions, so this might not work if you are using some
other kind of config. With CentOS6 and 3rd party Xen 4.1 packages this
procedure did not work at all and instead I needed to do the
following:

* in dom0 create the br0 and br1 devices in network-scripts

* in dom0 /etc/xen/xend-config.sxp put instead:

#(network-script network-bridge)
(network-script /bin/true)

* and in dom0 use different configuration for the domU config files like this:

vif = [ "mac=00:16:3E:69:29:25,bridge=br0","mac=00:16:3E:E6:B0:6D,bridge=br1" ]


Hope this helps, unfortuantely I am not familiar with virsh at all.

Best,
Peter


From mdra137 at gmail.com  Fri Nov 18 17:17:17 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Fri, 18 Nov 2011 18:17:17 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0D1Z-dbkvM+-0+DgVGSGd_dHa757rSqMUZcAgCfffstwQ@mail.gmail.com>

Dear Peter,


Thanks for your reply. I was so occupied with troubleshooting that I forgot
to mention the OS & Xen version :)

My CentOS version is
CentOS release 5.7 (Final)
Linux 2.6.18-274.7.1.el5xen #1 SMP Thu Oct 20 17:06:34 EDT 2011 x86_64
x86_64 x86_64 GNU/Linux

and Xen v3.0.

I tried creating bridges the same way you did and succedded. I also tried
doing the same via ifcfg scripts, and it also worked.

I have no problem with creating bridges and connecting them with physical
ifaces, but I can't start my VM's (most of the time one VM start but the
other one hangs while trying to initalize eth2 that is connected to my
second (non default - xenbr1) bridge)).

The only diference between your config and mine is that I have vifname-s
listed (example below):

vif = [
"mac=00:16:36:72:35:e5,bridge=xenbr0,script=vif-bridge,vifname=vif4.0",
"mac=00:16:3e:57:de:0d,bridge=xenbr1,script=vif-bridge, vifname=vif4.1" ]

I'm not saying that this could be the problem, but since I'm slowly running
out of ideas - it's a longshot :)

So, to sum it all up - I can create bridges properly, but my VM's hang when
they try to bring up vifaces connected to the xenbr1. Also, I have no
problem with having only one bridge active - problem appears when I have
multiple bridges.

Br,
Matija
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111118/2a75ed85/attachment-0003.html>

From maillists at conactive.com  Fri Nov 18 18:33:20 2011
From: maillists at conactive.com (Kai Schaetzl)
Date: Fri, 18 Nov 2011 19:33:20 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
In-Reply-To: <CALZem0D1Z-dbkvM+-0+DgVGSGd_dHa757rSqMUZcAgCfffstwQ@mail.gmail.com>
References: <CALZem0D1Z-dbkvM+-0+DgVGSGd_dHa757rSqMUZcAgCfffstwQ@mail.gmail.com>
Message-ID: <VA.00003db7.1907ac90@news.conactive.com>

Matija Draganovi? wrote on Fri, 18 Nov 2011 18:17:17 +0100:

> The only diference between your config and mine is that I have vifname-s
> listed

Then remove it. I've never seen it like that. If I remember it correctly 
the vifnames are created dynamically. You can't rely on them I suppose.

And I don't remember using "script" either.

If you can't get it to work then use the second method Peter describes. 
That one should also work for Xen 3.0 and is guaranteed to create stable 
bridging.



Kai

-- 
Get your web at Conactive Internet Services: http://www.conactive.com





From jason at daylife.com  Fri Nov 18 22:56:02 2011
From: jason at daylife.com (Jason Nagashima)
Date: Fri, 18 Nov 2011 17:56:02 -0500 (EST)
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <1331504081.4540.1321656727740.JavaMail.root@mailbox01.hq.daylife.com>
Message-ID: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>

Running on Centos 5.6 with KVM... 

I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?

I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it.  There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.

Any advice/working examples would be greatly appreciated.

Regards,
Jason


From incoming-centos at rjl.com  Sat Nov 19 04:34:25 2011
From: incoming-centos at rjl.com (Nataraj)
Date: Fri, 18 Nov 2011 20:34:25 -0800
Subject: [CentOS-virt] high resolution video for kvm vm
Message-ID: <4EC731D1.40109@rjl.com>

I'm running a fuduntu vm (based on fedora 14)  on a CentOS 6 kvm
server.  I have tried changing the video in virt-manager from cirrus to
vga and restarting the VM, but the maximum resolution that the client
will let me set is still only 1024x768.  Should I be able to get  high
res video with the kvm VGA mode?  Note that the VM is running on a
CentOS server while virt-manager is running on my local desktop.

Would I be better off trying to get the vmware VGA driver working?  I'm
assuming I have to extract the driver from the vmware tools package and
manually install it into the X server, because VMware tools won't
install under kvm.

Also, I run with the keyboard option to swap caps lock and control on my
linux desktop, which does not seem to get passed through to the guest. 
I tried setting the same swap caps lock and control option in the guest,
but it does not work.  Any ideas?

Thanks,
Nataraj



From mdra137 at gmail.com  Sat Nov 19 06:32:21 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Sat, 19 Nov 2011 07:32:21 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0A+hx+b2OFOEYD-YdpXxV9Y=jFUP=UTjgFLBqBqca78YQ@mail.gmail.com>

I tried to remove vifname and vif-script but the problem remains. I think
that the bridges are ok, but for some reason VM's hang when they try to
connect their vifaces to them.

I'll try some different configurations of the physical ifaces (an vifaces
also), maybe I'll be able to find out something. Also, I'll focus on the
vTPM, since the following line shows up in the Xen log when the VM tries to
bring up the iface connected to the second bridge:

[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vtpm


Furthermore, it appears that sometimes the VM's manage to start regulary, I
just can't figure out when & why :/

Tnx for your comments ..

Br,
M.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111119/cc41e78f/attachment-0003.html>

From mdra137 at gmail.com  Tue Nov 22 09:37:31 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Tue, 22 Nov 2011 10:37:31 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0AS0ptzxMRXooEFHLCAR=OCnaFcXS5AcMmQduevWSFjrQ@mail.gmail.com>

Ok, after trying multiple different configurations I decided to play by the
book - I removed ifcfg script for creating the additional bridge and set up
an Xen script. So my new configuration is:

-> eth3 (my physical interface)
# NetXen Incorporated NX3031 Multifunction 1/10-Gigabit Server Adapter
DEVICE=eth3
BOOTPROTO=static
HWADDR= ...
ONBOOT=yes
IPADDR= ...
NETMASK= ...
NETWORK= ...

and the network-xen-multi-bridge script:

#!/bin/sh
# network-xen-multi-bridge
# Exit if anything goes wrong.
set -e
# First arg is the operation.
OP=$1
shift
script=/etc/xen/scripts/network-bridge.xen
case ${OP} in
start)
$script start vifnum=3 bridge=xenbr3 netdev=eth3
$script start vifnum=0 bridge=xenbr0 netdev=eth0
;;
stop)
$script stop vifnum=3 bridge=xenbr3 netdev=eth3
$script stop vifnum=0 bridge=xenbr0 netdev=eth0
;;
status)
$script status vifnum=3 bridge=xenbr3 netdev=eth3
$script status vifnum=0 bridge=xenbr0 netdev=eth0
;;
*)
echo 'Unknown command: ' ${OP}
echo 'Valid commands are: start, stop, status'
exit 1
esac

After I restart the physical server bridges are set up correctly:

# brctl show
bridge name bridge id STP enabled interfaces
virbr0 8000.000000000000 yes
xenbr0 8000.feffffffffff no vif0.0
peth0
xenbr3 8000.feffffffffff no vif0.3
peth3

Unfortunately, this did not solve the problem - I manage to start one VM
(connected to both of the bridges), but when I try to start the other one,
it just hangs when trying to bring up the second interface (connected to
xenbr3) :/

I'm currently completely out of ideas, but I'm not giving up ;)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111122/eb760bb6/attachment-0003.html>

From tait at taiter.com  Tue Nov 22 16:07:54 2011
From: tait at taiter.com (Tait Clarridge)
Date: Tue, 22 Nov 2011 11:07:54 -0500
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>
References: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>
Message-ID: <1321978074.22491.12.camel@tclarrltp.frontiernetworks.ca>

On Fri, 2011-11-18 at 17:56 -0500, Jason Nagashima wrote:
> Running on Centos 5.6 with KVM... 
> 
> I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?
> 
> I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it.  There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.
> 
> Any advice/working examples would be greatly appreciated.

Hi Jason,

I have had luck doing this with Xen, where I create bond0 on a trunk
interface and have xen bring it up as xenbr0 with pbond0 in the back
end.

You should be able to do roughly the same by creating a bridge interface
in /etc/sysconfig/network-scripts referencing bond0 as a member.

After that you should be able to run a script to create VLAN bridges
like the following:

#!/bin/bash
/sbin/modprobe 8021q

# Add your vlans here that you want with the numbers separated by a 
# space
VLANS="5 10 15 20"
# This should work with the bonding interface
TRUNKINT="bond0"
for VLAN in $VLANS
do
	vconfig add $TRUNKINT $VLAN
	brctl add br$VLAN
	brctl addif br$VLAN $TRUNKINT.$VLAN
	ifconfig $TRUNKINT.$VLAN up
	ifconfig br$VLAN up
done

I have done this with Xen on 5.5, 5.6 and 5.7... but it should work for
KVM. If you create the standard bridge interface br0 using just bond0
that will get you a trunk on whatever the native vlan is for that trunk.

Tait




From dmartls1 at gmail.com  Tue Nov 22 17:39:02 2011
From: dmartls1 at gmail.com (David Martin)
Date: Tue, 22 Nov 2011 11:39:02 -0600
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <1321978074.22491.12.camel@tclarrltp.frontiernetworks.ca>
References: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>
	<1321978074.22491.12.camel@tclarrltp.frontiernetworks.ca>
Message-ID: <CAAsqWCd+KWrX-SpRcYVNzCVC4HDV25C1QeOZzu-ChN0ZHyhdBw@mail.gmail.com>

We are doing this quite a bit in production and it works great.

bond as you normally would:
DEVICE=bond0
ONBOOT=yes
USERCTL=no
BONDING_OPTS="mode=4 miimon=100"

one of these for each vlan (in this case 50):
VLAN=yes
VLAN_NAME_TYPE=VLAN_PLUS_VID_NO_PAD
DEVICE=vlan50
PHYSDEV=bond0
TYPE=Ethernet
ONBOOT=yes
BRIDGE=br50

and finally the bridge device to expose to guests:
DEVICE=br50
TYPE=Bridge
ONBOOT=yes
DELAY=0
GATEWAYDEV=none




On Tue, Nov 22, 2011 at 10:07 AM, Tait Clarridge <tait at taiter.com> wrote:
> On Fri, 2011-11-18 at 17:56 -0500, Jason Nagashima wrote:
>> Running on Centos 5.6 with KVM...
>>
>> I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?
>>
>> I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it. ?There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.
>>
>> Any advice/working examples would be greatly appreciated.
>
> Hi Jason,
>
> I have had luck doing this with Xen, where I create bond0 on a trunk
> interface and have xen bring it up as xenbr0 with pbond0 in the back
> end.
>
> You should be able to do roughly the same by creating a bridge interface
> in /etc/sysconfig/network-scripts referencing bond0 as a member.
>
> After that you should be able to run a script to create VLAN bridges
> like the following:
>
> #!/bin/bash
> /sbin/modprobe 8021q
>
> # Add your vlans here that you want with the numbers separated by a
> # space
> VLANS="5 10 15 20"
> # This should work with the bonding interface
> TRUNKINT="bond0"
> for VLAN in $VLANS
> do
> ? ? ? ?vconfig add $TRUNKINT $VLAN
> ? ? ? ?brctl add br$VLAN
> ? ? ? ?brctl addif br$VLAN $TRUNKINT.$VLAN
> ? ? ? ?ifconfig $TRUNKINT.$VLAN up
> ? ? ? ?ifconfig br$VLAN up
> done
>
> I have done this with Xen on 5.5, 5.6 and 5.7... but it should work for
> KVM. If you create the standard bridge interface br0 using just bond0
> that will get you a trunk on whatever the native vlan is for that trunk.
>
> Tait
>
>
> _______________________________________________
> CentOS-virt mailing list
> CentOS-virt at centos.org
> http://lists.centos.org/mailman/listinfo/centos-virt
>


From jason at daylife.com  Wed Nov 23 21:49:56 2011
From: jason at daylife.com (Jason Nagashima)
Date: Wed, 23 Nov 2011 16:49:56 -0500 (EST)
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <CAAsqWCd+KWrX-SpRcYVNzCVC4HDV25C1QeOZzu-ChN0ZHyhdBw@mail.gmail.com>
Message-ID: <206550579.4866.1322084996341.JavaMail.root@mailbox01.hq.daylife.com>

Awesome!

Thank you everyone for responding and helping out. I'm happy to report that we got it working!

Cheers,
Jason

----- Original Message -----
From: "David Martin" <dmartls1 at gmail.com>
To: "Discussion about the virtualization on CentOS" <centos-virt at centos.org>
Sent: Tuesday, November 22, 2011 12:39:02 PM
Subject: Re: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6

We are doing this quite a bit in production and it works great.

bond as you normally would:
DEVICE=bond0
ONBOOT=yes
USERCTL=no
BONDING_OPTS="mode=4 miimon=100"

one of these for each vlan (in this case 50):
VLAN=yes
VLAN_NAME_TYPE=VLAN_PLUS_VID_NO_PAD
DEVICE=vlan50
PHYSDEV=bond0
TYPE=Ethernet
ONBOOT=yes
BRIDGE=br50

and finally the bridge device to expose to guests:
DEVICE=br50
TYPE=Bridge
ONBOOT=yes
DELAY=0
GATEWAYDEV=none




On Tue, Nov 22, 2011 at 10:07 AM, Tait Clarridge <tait at taiter.com> wrote:
> On Fri, 2011-11-18 at 17:56 -0500, Jason Nagashima wrote:
>> Running on Centos 5.6 with KVM...
>>
>> I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?
>>
>> I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it. ?There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.
>>
>> Any advice/working examples would be greatly appreciated.
>
> Hi Jason,
>
> I have had luck doing this with Xen, where I create bond0 on a trunk
> interface and have xen bring it up as xenbr0 with pbond0 in the back
> end.
>
> You should be able to do roughly the same by creating a bridge interface
> in /etc/sysconfig/network-scripts referencing bond0 as a member.
>
> After that you should be able to run a script to create VLAN bridges
> like the following:
>
> #!/bin/bash
> /sbin/modprobe 8021q
>
> # Add your vlans here that you want with the numbers separated by a
> # space
> VLANS="5 10 15 20"
> # This should work with the bonding interface
> TRUNKINT="bond0"
> for VLAN in $VLANS
> do
> ? ? ? ?vconfig add $TRUNKINT $VLAN
> ? ? ? ?brctl add br$VLAN
> ? ? ? ?brctl addif br$VLAN $TRUNKINT.$VLAN
> ? ? ? ?ifconfig $TRUNKINT.$VLAN up
> ? ? ? ?ifconfig br$VLAN up
> done
>
> I have done this with Xen on 5.5, 5.6 and 5.7... but it should work for
> KVM. If you create the standard bridge interface br0 using just bond0
> that will get you a trunk on whatever the native vlan is for that trunk.
>
> Tait
>
>
> _______________________________________________
> CentOS-virt mailing list
> CentOS-virt at centos.org
> http://lists.centos.org/mailman/listinfo/centos-virt
>
_______________________________________________
CentOS-virt mailing list
CentOS-virt at centos.org
http://lists.centos.org/mailman/listinfo/centos-virt


From mdra137 at gmail.com  Fri Nov 25 11:11:44 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Fri, 25 Nov 2011 12:11:44 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0BCpJuchqLS6vws9Sm+_YPbR3AkLVyiKBQpJAPDGvzSGQ@mail.gmail.com>

Finally, I managed to solve the problem. The problem was rather strange -
after configuring bridges I added new ifaces to the VM. For some reason,
during boot process of the VM's, wrong interface was started (VM tried to
bring up eth2 instead eth1?).

After adding the new ifaces through virt-manager, the VM started regulary
and created a new network script for eth2
(/etc/sysconfig/network-scripts/ifcfg-eth2). I think that the problem was
this - when the VM is restarted it tried to bring up eth2 while vif-script
tried to propagate second bridge via eth1 iface. I resolved this simply by
replacing ifcfg-eth2 script with ifcfg-eth1. Now, VM starts/restarts
regulary ;)

So, the process for creating and configuring new bridges that I follow is
(tried on multiple servers):

- create new script that sets up multiple bridges in /etc/xen/scripts/

example: network-xen-multi-bridge

#!/bin/sh
# network-xen-multi-bridge
# Exit if anything goes wrong.
set -e
# First arg is the operation.
OP=$1
shift
script=/etc/xen/scripts/network-bridge.xen
case ${OP} in
start)
        $script start vifnum=3 bridge=xenbr3 netdev=eth3
        $script start vifnum=0 bridge=xenbr0 netdev=eth0
        ;;
stop)
        $script stop vifnum=3 bridge=xenbr3 netdev=eth3
        $script stop vifnum=0 bridge=xenbr0 netdev=eth0
        ;;
status)
        $script status vifnum=3 bridge=xenbr3 netdev=eth3
        $script status vifnum=0 bridge=xenbr0 netdev=eth0
        ;;
*)
        echo 'Unknown command: ' ${OP}
        echo 'Valid commands are: start, stop, status'
        exit 1
esac



- make it executable (chmod 755 network-xen-multi-bridge)

- configure /etc/xen/xend-config.sxp (comment out the current script and
add the new one);

# It is possible to use the network-bridge script in more complicated
# scenarios, such as having two outgoing interfaces, with two bridges, and
# two fake interfaces per guest domain.  To do things like this, write
# yourself a wrapper script, and call network-bridge from it, as appropriate.
#
#(network-script network-bridge)
(network-script  network-xen-multi-bridge)



- restart physical server so the bridges are properly created

- add virt. ifaces to the VM's (via virt-manager or via config. files in
/etc/xen/ ..)

- boot VM

- configure newly added iface in /etc/sysconfig/network-scripts/

- restart VM

Additionaly I check everything by restarting phys. server to make sure that
everything is ok ;)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111125/1304c71b/attachment-0003.html>

From mail-lists at karan.org  Sat Nov 26 00:29:20 2011
From: mail-lists at karan.org (Karanbir Singh)
Date: Sat, 26 Nov 2011 00:29:20 +0000
Subject: [CentOS-virt] Device renaming heads up
Message-ID: <4ED032E0.1040109@karan.org>

hi Guys,

Just in case anyone hasent noticed this :
https://bugzilla.redhat.com/show_bug.cgi?id=729586 device naming mixup
causing lots of domU's to not come back after a kernel update...

- KB


From toddandmargo at gmail.com  Mon Nov 28 18:37:50 2011
From: toddandmargo at gmail.com (Todd And Margo Chester)
Date: Mon, 28 Nov 2011 10:37:50 -0800
Subject: [CentOS-virt] kvm: w7 bsod's at shutdown
Message-ID: <4ED3D4FE.9090008@gmail.com>

Hi All,

I am using Scientific Linux 6.1 x64

Any idea how to get my W7 x32 guest to shutdown with out a BSOD?
I have to go into virt-manager and kill it all the time.  My XP guest
shuts down without issue.

Many thanks,
-T

$ rpm -qa \*kvm\*
qemu-kvm-0.12.1.2-2.160.el6_1.2.x86_64

$ rpm -qa \*virt\*
python-virtinst-0.500.5-3.el6.noarch
libvirt-0.8.7-18.el6_1.1.x86_64
libvirt-client-0.8.7-18.el6_1.1.x86_64
virt-manager-0.8.6-4.el6.noarch
libvirt-python-0.8.7-18.el6_1.1.x86_64



From byrnejb at harte-lyne.ca  Tue Nov 29 20:51:45 2011
From: byrnejb at harte-lyne.ca (James B. Byrne)
Date: Tue, 29 Nov 2011 15:51:45 -0500 (EST)
Subject: [CentOS-virt] Transfer of LVM based guests
Message-ID: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>

I am investigating the procedure to follow when moving a
KVM guest instance from one host to another where the
guest uses LVM as its storage.  As a preliminary cut I
have cobbled the following together from various sources
located through Google searches:

1.  Log in to vmhost_old

2.  Shutdown guest

3.  Create an LVM snapshot of the guest volume
3.a.   lvcreate -s -L 300m -n LVM_guest_snapshot guest_lv

4.  Convert snapshot to a file image
4.a    dd if=/dev/vhost/LVM_guest_snapshot
          of=/tmp/fs/LVM_guest_snapshot.img bs=4096

5.  Remove the original snapshot
5.a    lvremove /dev/vhost/LVM_guest_snapshot

6.  Move the snapshot image file to the new KVM host. Note
that for large vm guest images tape transport is probably
better than network transfers.

7.  Log in to vhost_new

8.  Create a new lv on the new vhost
8.a    lvcreate -n guest_name_lv -L 60G vhost_new_vg

9.  Copy transferred image to new LV
9.a    dd if=tmp/LVM_guest_snapshot.img
       of=/dev/vhost_new/guest_name_lv bs=4096

10.  Copy guest xml file from vhost_old via sftp
10.a.   get /etc/libvirt/qemu/guest_name.xml \
           /etc/libvirt/qemu/guest_name.xml

11. Start new guest?


Is there anything obviously wrong or omitted from this?


-- 
***          E-Mail is NOT a SECURE channel          ***
James B. Byrne                mailto:ByrneJB at Harte-Lyne.ca
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3



From Ed at Heron-ent.com  Tue Nov 29 22:11:01 2011
From: Ed at Heron-ent.com (Ed Heron)
Date: Tue, 29 Nov 2011 15:11:01 -0700
Subject: [CentOS-virt] Transfer of LVM based guests
In-Reply-To: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
References: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
Message-ID: <1322604661.4811.13.camel@elap.rgtravel.com>

On Tue, 2011-11-29 at 15:51 -0500, James B. Byrne wrote:
> I am investigating the procedure to follow when moving a
> KVM guest instance from one host to another where the
> guest uses LVM as its storage.  As a preliminary cut I
> have cobbled the following together from various sources
> located through Google searches:
> ...

  If you are moving the virtual disk, you can't run the virtual machine while you are moving it.  Therefore, taking a snapshot (and removing it later) is superfluous.

  I use md5sum to give myself some extra re-assurance that a copy that big is accurate.

  Are the virtualization servers at the same location?

  How often do you move virtual machines?

  If your virtualization servers are in the same location, you might want to look into setting up a LAN for transferring virtual machine images.  It would only take an extra network card in each virtualization server and a Gb Ethernet switch (or better).

  If you are interested in virtual disk replication, you might want to look at DRBD.  It adds an extra layer to your storage, but allows for hot replication of disk space which would allow you to start a virtual machine on any virtualization server.




From byrnejb at harte-lyne.ca  Wed Nov 30 16:23:11 2011
From: byrnejb at harte-lyne.ca (James B. Byrne)
Date: Wed, 30 Nov 2011 11:23:11 -0500 (EST)
Subject: [CentOS-virt] Transfer of LVM based guests
In-Reply-To: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
References: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
Message-ID: <40363.216.185.71.25.1322670191.squirrel@webmail.harte-lyne.ca>


On Tue, November 29, 2011 17:11:01, Ed Heron Ed at
Heron-ent.com wrote:

> If you are moving the virtual disk, you can't run
> the virtual machine while you are moving it.
> Therefore, taking a snapshot (and removing it later)
> is superfluous.

Point taken.

> I use md5sum to give myself some extra re-assurance
> that a copy that big is accurate.

Good idea.

> Are the virtualization servers at the same location?

At the moment. It is planned that there will be two vhosts
at each of two different locations, one backing up the
other.

>  How often do you move virtual machines?

I have not moved any as of yet.  I am investigating how to
do this as part of setting up our first virtual server
host.  I am discovering what is possible and the
techniques used.  Moving vm guests is not being considered
for load balancing but is under consideration for
providing warm spares for use in a DR situation.

> If your virtualization servers are in the same
> location, you might want to look into setting up a
> LAN for transferring virtual machine images.  It
> would only take an extra network card in each
> virtualization server and a Gb Ethernet switch
> (or better).

Our vhosts all (will) have two nics, one for public IPs
and one for private IPs.  The private IPs are used for
vhost management.  The experimental vhost is so equipped.

> If you are interested in virtual disk replication,
> you might want to look at DRBD.  It adds an extra layer
> to your storage, but allows for hot replication of
> disk space which would allow you to start a virtual
> machine on any virtualization server.

This is a useful suggestion. However, I find that the
availability of a DRDB package on CentOS-6 is presently an
issue.  And, our vm project has already expanded into
multiple areas with commensurate delays.  I think that I
will leave DRDB for a later time.

So, what I now have for a proposed procedure is:

1.  Log in to vmhost_old

2.  Shutdown guest

3.  Convert guest lvs to file images for each lv
3.a    dd if=/dev/vhost/lv_vhost_guest
          of=/tmp/fs/lv_vhost_guest.img bs=4096

4.  Create MD5 hash for each image file
4.a    md5sum /tmp/fs/lv_vhost_guest.img > \
              /tmp/fs/lv_vhost_guest.md5

5.  Move the guest image file(s)  and the checksum file to
the new vhost; preserving both the directory structure and
file names or subsequently modifying the file names in the
md5 checksum file. Note that for large vm guest images
tape transport is probably better than network transfers.

6.  Log in to vhost_new

7.  Verify md5 checksum(s) on transferred file(s).
7.a    md5sum -c /tmp/fs/lv_vhost_guest.md5

8.  Create a new lv(s) on the new vhost. Ensure sufficient
size.
8.a    lvcreate -n lv_guest_name -L 60G vhost_new_vg

9.  Copy transferred image to new LV
9.a    dd if=/tmp/fs/lv_vhost_guest.img
       of=/dev/vhost_new/lv_guest_name bs=4096

10.  Copy guest xml file from vhost_old via sftp
10.a.   get /etc/libvirt/qemu/guest_name.xml \
           /etc/libvirt/qemu/guest_name.xml

11. Start new guest?


Thanks,


-- 
***          E-Mail is NOT a SECURE channel          ***
James B. Byrne                mailto:ByrneJB at Harte-Lyne.ca
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3



From raju.rajsand at gmail.com  Mon Nov  7 18:17:22 2011
From: raju.rajsand at gmail.com (Rajagopal Swaminathan)
Date: Mon, 7 Nov 2011 23:47:22 +0530
Subject: [CentOS-virt] P2V utility
Message-ID: <CA+YdgaqusA9ZR2ekkyXtkggKBsH73=HYe1c=XVTSnq7OQ_kq+Q@mail.gmail.com>

Greetings,

An somebody pint to me to P2V Utility for the m$ world?

Like in VMware?

-- 
Regards,

Rajagopal


From lorenzo at tulug.it  Tue Nov  8 14:20:52 2011
From: lorenzo at tulug.it (Lorenzo)
Date: Tue, 8 Nov 2011 15:20:52 +0100
Subject: [CentOS-virt] P2V utility
In-Reply-To: <CA+YdgaqusA9ZR2ekkyXtkggKBsH73=HYe1c=XVTSnq7OQ_kq+Q@mail.gmail.com>
References: <CA+YdgaqusA9ZR2ekkyXtkggKBsH73=HYe1c=XVTSnq7OQ_kq+Q@mail.gmail.com>
Message-ID: <CADE4e0WfAq++1UDq-Vj3EhR=K1=xQTwmU0qsVhLrXVKgy+SDhg@mail.gmail.com>

2011/11/7 Rajagopal Swaminathan <raju.rajsand at gmail.com>:
> Greetings,
>
> An somebody pint to me to P2V Utility for the m$ world?
>
> Like in VMware?
>
> --
> Regards,
>
> Rajagopal

Try here:
http://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE
not centos specific, but I found a lot of useful info.

Regards,
Lorenzo


From mdra137 at gmail.com  Fri Nov 18 13:39:23 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Fri, 18 Nov 2011 14:39:23 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0BmRWi7_=FEJ0WSTzs5J1-2wuJ_AZdN=_S8WKWg94E_Vg@mail.gmail.com>

Hi,

I've been using CentOS & Xen on a server that has 2 VM's configured. The
default configuration includes one physical iface that is propagated (by a
default bridge) to the VM's.

Since I wanted to configure additional physical iface, define a new bridge
and propagate it to the viface-s of the VM's, i configured the bridge/phys.
iface and brought it up (here are configurations that I set up):

-> eth3
DEVICE=eth3
BOOTPROTO=static
HWADDR=D4:85:64:4B:76:AB
ONBOOT=yes
#HOTPLUG=no
#DHCP_HOSTNAME=kdr-3k-4r-3o-07
BRIDGE=br0
TYPE=Ethernet

-> br0
DEVICE=br0
TYPE=Bridge
BOOTPROTO=none
ONBOOT=yes

Then I configured new virt. ifaces on VM's (using virsh edit, config is
listed below):

<interface type='bridge'>
<mac address='00:16:36:17:62:5d'/>
<source bridge='xenbr0'/>
<script path='vif-bridge'/>
<target dev='vif5.0'/>
</interface>
<interface type='bridge'>
<mac address='00:16:3e:ca:63:39'/>
<source bridge='br0'/>
<script path='vif-bridge'/>
<target dev='vif5.1'/>
</interface>

You can see the default bridge (xenbr0 -> vif5.0) and my new bridge br0
connected to vif5.1.

So, here I got stuck up - when I try tu start a VM (xm create VIRT_SRV),
the VM starts booting but hangs up (I can ping it form another srv., but
when I try SSH it says "connection refused"). When I remove configuration
for vif5.1 the VM starts up normally. I actually managed to start VM with
vif5.1 up once, but next time I restarted it, the problem was there :/


Furthermore, I noticed this in the Xen log:

[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vif.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 0.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vif/1/1/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices usb.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vbd.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 768.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vbd/1/768/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 5632.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vbd/1/5632/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices irq.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vkbd.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vfb.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices pci.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices ioports.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices tap.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vtpm.

So the boot process goes on regulary until the last line ("Waiting for
devices vtpm"). It seems like TPM makes it impossible for VM's to start
regulary. When I open the VM's console (with virt-manager) I see the whole
boot process but it hangs when it tries to start iface eth2 (attached to
the second bridge) ...

Does anybody have a clue why is this happening?

Thanks in advance ..
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111118/e056a2eb/attachment-0004.html>

From peter.peltonen at gmail.com  Fri Nov 18 14:33:35 2011
From: peter.peltonen at gmail.com (Peter Peltonen)
Date: Fri, 18 Nov 2011 16:33:35 +0200
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
In-Reply-To: <CALZem0BmRWi7_=FEJ0WSTzs5J1-2wuJ_AZdN=_S8WKWg94E_Vg@mail.gmail.com>
References: <CALZem0BmRWi7_=FEJ0WSTzs5J1-2wuJ_AZdN=_S8WKWg94E_Vg@mail.gmail.com>
Message-ID: <CAGTVFvHkhkUytpf9ei2vGT0_NhLsOhXikDPV9ORAKYitttjCdA@mail.gmail.com>

Hi,

2011/11/18 Matija Draganovi? <mdra137 at gmail.com>:
> I've been using CentOS & Xen on a server that has 2 VM's configured. The
> default configuration includes one physical iface that is propagated (by a
> default bridge) to the VM's.

You do not mention which version of CentOS and Xen you are using?

>
> Since I wanted to configure additional physical iface, define a new bridge
> and propagate it to the viface-s of the VM's, i configured the bridge/phys.
> iface and brought it up (here are configurations that I set up):
>
> -> eth3
> DEVICE=eth3
> BOOTPROTO=static
> HWADDR=D4:85:64:4B:76:AB
> ONBOOT=yes
> #HOTPLUG=no
> #DHCP_HOSTNAME=kdr-3k-4r-3o-07
> BRIDGE=br0
> TYPE=Ethernet
>
> -> br0
> DEVICE=br0
> TYPE=Bridge
> BOOTPROTO=none
> ONBOOT=yes

If this is a CentOS5 machine with the CentOS provided Xen 3.0
packages, then here is info how i got my bridges to work with that
setup:

* For dom0 I configured eth0 and eth1 as usual in /etc/sysconfig/network-scripts

* I did not configure br0 or br1 in network-scripts, but instead I
created a file called /etc/xen/scripts/my-network-script having this
contents:

#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0
"$dir/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=xenbr1

* Then I modified in dom0 the file /etc/xen/xend-config.sxp in the
following way:

#(network-script network-bridge)
(network-script my-network-script)

* Now rebooting dom0 made the bridges available

* After that I could configure them in my domU config:

vif = [ "mac=00:16:3E:69:29:25,bridge=xenbr0,script=vif-bridge","mac=00:16:3E:E6:B0:6D,bridge=xenbr1,script=vif-bridge"
]

* After starting the domU I could configure the interfaces in
network-scripts using the hardware addresses specified in the domU
config


It seems that configuring bridging is done a bit differently in
different Xen versions, so this might not work if you are using some
other kind of config. With CentOS6 and 3rd party Xen 4.1 packages this
procedure did not work at all and instead I needed to do the
following:

* in dom0 create the br0 and br1 devices in network-scripts

* in dom0 /etc/xen/xend-config.sxp put instead:

#(network-script network-bridge)
(network-script /bin/true)

* and in dom0 use different configuration for the domU config files like this:

vif = [ "mac=00:16:3E:69:29:25,bridge=br0","mac=00:16:3E:E6:B0:6D,bridge=br1" ]


Hope this helps, unfortuantely I am not familiar with virsh at all.

Best,
Peter


From mdra137 at gmail.com  Fri Nov 18 17:17:17 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Fri, 18 Nov 2011 18:17:17 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0D1Z-dbkvM+-0+DgVGSGd_dHa757rSqMUZcAgCfffstwQ@mail.gmail.com>

Dear Peter,


Thanks for your reply. I was so occupied with troubleshooting that I forgot
to mention the OS & Xen version :)

My CentOS version is
CentOS release 5.7 (Final)
Linux 2.6.18-274.7.1.el5xen #1 SMP Thu Oct 20 17:06:34 EDT 2011 x86_64
x86_64 x86_64 GNU/Linux

and Xen v3.0.

I tried creating bridges the same way you did and succedded. I also tried
doing the same via ifcfg scripts, and it also worked.

I have no problem with creating bridges and connecting them with physical
ifaces, but I can't start my VM's (most of the time one VM start but the
other one hangs while trying to initalize eth2 that is connected to my
second (non default - xenbr1) bridge)).

The only diference between your config and mine is that I have vifname-s
listed (example below):

vif = [
"mac=00:16:36:72:35:e5,bridge=xenbr0,script=vif-bridge,vifname=vif4.0",
"mac=00:16:3e:57:de:0d,bridge=xenbr1,script=vif-bridge, vifname=vif4.1" ]

I'm not saying that this could be the problem, but since I'm slowly running
out of ideas - it's a longshot :)

So, to sum it all up - I can create bridges properly, but my VM's hang when
they try to bring up vifaces connected to the xenbr1. Also, I have no
problem with having only one bridge active - problem appears when I have
multiple bridges.

Br,
Matija
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111118/2a75ed85/attachment-0004.html>

From maillists at conactive.com  Fri Nov 18 18:33:20 2011
From: maillists at conactive.com (Kai Schaetzl)
Date: Fri, 18 Nov 2011 19:33:20 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
In-Reply-To: <CALZem0D1Z-dbkvM+-0+DgVGSGd_dHa757rSqMUZcAgCfffstwQ@mail.gmail.com>
References: <CALZem0D1Z-dbkvM+-0+DgVGSGd_dHa757rSqMUZcAgCfffstwQ@mail.gmail.com>
Message-ID: <VA.00003db7.1907ac90@news.conactive.com>

Matija Draganovi? wrote on Fri, 18 Nov 2011 18:17:17 +0100:

> The only diference between your config and mine is that I have vifname-s
> listed

Then remove it. I've never seen it like that. If I remember it correctly 
the vifnames are created dynamically. You can't rely on them I suppose.

And I don't remember using "script" either.

If you can't get it to work then use the second method Peter describes. 
That one should also work for Xen 3.0 and is guaranteed to create stable 
bridging.



Kai

-- 
Get your web at Conactive Internet Services: http://www.conactive.com





From jason at daylife.com  Fri Nov 18 22:56:02 2011
From: jason at daylife.com (Jason Nagashima)
Date: Fri, 18 Nov 2011 17:56:02 -0500 (EST)
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <1331504081.4540.1321656727740.JavaMail.root@mailbox01.hq.daylife.com>
Message-ID: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>

Running on Centos 5.6 with KVM... 

I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?

I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it.  There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.

Any advice/working examples would be greatly appreciated.

Regards,
Jason


From incoming-centos at rjl.com  Sat Nov 19 04:34:25 2011
From: incoming-centos at rjl.com (Nataraj)
Date: Fri, 18 Nov 2011 20:34:25 -0800
Subject: [CentOS-virt] high resolution video for kvm vm
Message-ID: <4EC731D1.40109@rjl.com>

I'm running a fuduntu vm (based on fedora 14)  on a CentOS 6 kvm
server.  I have tried changing the video in virt-manager from cirrus to
vga and restarting the VM, but the maximum resolution that the client
will let me set is still only 1024x768.  Should I be able to get  high
res video with the kvm VGA mode?  Note that the VM is running on a
CentOS server while virt-manager is running on my local desktop.

Would I be better off trying to get the vmware VGA driver working?  I'm
assuming I have to extract the driver from the vmware tools package and
manually install it into the X server, because VMware tools won't
install under kvm.

Also, I run with the keyboard option to swap caps lock and control on my
linux desktop, which does not seem to get passed through to the guest. 
I tried setting the same swap caps lock and control option in the guest,
but it does not work.  Any ideas?

Thanks,
Nataraj



From mdra137 at gmail.com  Sat Nov 19 06:32:21 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Sat, 19 Nov 2011 07:32:21 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0A+hx+b2OFOEYD-YdpXxV9Y=jFUP=UTjgFLBqBqca78YQ@mail.gmail.com>

I tried to remove vifname and vif-script but the problem remains. I think
that the bridges are ok, but for some reason VM's hang when they try to
connect their vifaces to them.

I'll try some different configurations of the physical ifaces (an vifaces
also), maybe I'll be able to find out something. Also, I'll focus on the
vTPM, since the following line shows up in the Xen log when the VM tries to
bring up the iface connected to the second bridge:

[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vtpm


Furthermore, it appears that sometimes the VM's manage to start regulary, I
just can't figure out when & why :/

Tnx for your comments ..

Br,
M.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111119/cc41e78f/attachment-0004.html>

From mdra137 at gmail.com  Tue Nov 22 09:37:31 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Tue, 22 Nov 2011 10:37:31 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0AS0ptzxMRXooEFHLCAR=OCnaFcXS5AcMmQduevWSFjrQ@mail.gmail.com>

Ok, after trying multiple different configurations I decided to play by the
book - I removed ifcfg script for creating the additional bridge and set up
an Xen script. So my new configuration is:

-> eth3 (my physical interface)
# NetXen Incorporated NX3031 Multifunction 1/10-Gigabit Server Adapter
DEVICE=eth3
BOOTPROTO=static
HWADDR= ...
ONBOOT=yes
IPADDR= ...
NETMASK= ...
NETWORK= ...

and the network-xen-multi-bridge script:

#!/bin/sh
# network-xen-multi-bridge
# Exit if anything goes wrong.
set -e
# First arg is the operation.
OP=$1
shift
script=/etc/xen/scripts/network-bridge.xen
case ${OP} in
start)
$script start vifnum=3 bridge=xenbr3 netdev=eth3
$script start vifnum=0 bridge=xenbr0 netdev=eth0
;;
stop)
$script stop vifnum=3 bridge=xenbr3 netdev=eth3
$script stop vifnum=0 bridge=xenbr0 netdev=eth0
;;
status)
$script status vifnum=3 bridge=xenbr3 netdev=eth3
$script status vifnum=0 bridge=xenbr0 netdev=eth0
;;
*)
echo 'Unknown command: ' ${OP}
echo 'Valid commands are: start, stop, status'
exit 1
esac

After I restart the physical server bridges are set up correctly:

# brctl show
bridge name bridge id STP enabled interfaces
virbr0 8000.000000000000 yes
xenbr0 8000.feffffffffff no vif0.0
peth0
xenbr3 8000.feffffffffff no vif0.3
peth3

Unfortunately, this did not solve the problem - I manage to start one VM
(connected to both of the bridges), but when I try to start the other one,
it just hangs when trying to bring up the second interface (connected to
xenbr3) :/

I'm currently completely out of ideas, but I'm not giving up ;)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111122/eb760bb6/attachment-0004.html>

From tait at taiter.com  Tue Nov 22 16:07:54 2011
From: tait at taiter.com (Tait Clarridge)
Date: Tue, 22 Nov 2011 11:07:54 -0500
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>
References: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>
Message-ID: <1321978074.22491.12.camel@tclarrltp.frontiernetworks.ca>

On Fri, 2011-11-18 at 17:56 -0500, Jason Nagashima wrote:
> Running on Centos 5.6 with KVM... 
> 
> I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?
> 
> I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it.  There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.
> 
> Any advice/working examples would be greatly appreciated.

Hi Jason,

I have had luck doing this with Xen, where I create bond0 on a trunk
interface and have xen bring it up as xenbr0 with pbond0 in the back
end.

You should be able to do roughly the same by creating a bridge interface
in /etc/sysconfig/network-scripts referencing bond0 as a member.

After that you should be able to run a script to create VLAN bridges
like the following:

#!/bin/bash
/sbin/modprobe 8021q

# Add your vlans here that you want with the numbers separated by a 
# space
VLANS="5 10 15 20"
# This should work with the bonding interface
TRUNKINT="bond0"
for VLAN in $VLANS
do
	vconfig add $TRUNKINT $VLAN
	brctl add br$VLAN
	brctl addif br$VLAN $TRUNKINT.$VLAN
	ifconfig $TRUNKINT.$VLAN up
	ifconfig br$VLAN up
done

I have done this with Xen on 5.5, 5.6 and 5.7... but it should work for
KVM. If you create the standard bridge interface br0 using just bond0
that will get you a trunk on whatever the native vlan is for that trunk.

Tait




From dmartls1 at gmail.com  Tue Nov 22 17:39:02 2011
From: dmartls1 at gmail.com (David Martin)
Date: Tue, 22 Nov 2011 11:39:02 -0600
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <1321978074.22491.12.camel@tclarrltp.frontiernetworks.ca>
References: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>
	<1321978074.22491.12.camel@tclarrltp.frontiernetworks.ca>
Message-ID: <CAAsqWCd+KWrX-SpRcYVNzCVC4HDV25C1QeOZzu-ChN0ZHyhdBw@mail.gmail.com>

We are doing this quite a bit in production and it works great.

bond as you normally would:
DEVICE=bond0
ONBOOT=yes
USERCTL=no
BONDING_OPTS="mode=4 miimon=100"

one of these for each vlan (in this case 50):
VLAN=yes
VLAN_NAME_TYPE=VLAN_PLUS_VID_NO_PAD
DEVICE=vlan50
PHYSDEV=bond0
TYPE=Ethernet
ONBOOT=yes
BRIDGE=br50

and finally the bridge device to expose to guests:
DEVICE=br50
TYPE=Bridge
ONBOOT=yes
DELAY=0
GATEWAYDEV=none




On Tue, Nov 22, 2011 at 10:07 AM, Tait Clarridge <tait at taiter.com> wrote:
> On Fri, 2011-11-18 at 17:56 -0500, Jason Nagashima wrote:
>> Running on Centos 5.6 with KVM...
>>
>> I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?
>>
>> I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it. ?There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.
>>
>> Any advice/working examples would be greatly appreciated.
>
> Hi Jason,
>
> I have had luck doing this with Xen, where I create bond0 on a trunk
> interface and have xen bring it up as xenbr0 with pbond0 in the back
> end.
>
> You should be able to do roughly the same by creating a bridge interface
> in /etc/sysconfig/network-scripts referencing bond0 as a member.
>
> After that you should be able to run a script to create VLAN bridges
> like the following:
>
> #!/bin/bash
> /sbin/modprobe 8021q
>
> # Add your vlans here that you want with the numbers separated by a
> # space
> VLANS="5 10 15 20"
> # This should work with the bonding interface
> TRUNKINT="bond0"
> for VLAN in $VLANS
> do
> ? ? ? ?vconfig add $TRUNKINT $VLAN
> ? ? ? ?brctl add br$VLAN
> ? ? ? ?brctl addif br$VLAN $TRUNKINT.$VLAN
> ? ? ? ?ifconfig $TRUNKINT.$VLAN up
> ? ? ? ?ifconfig br$VLAN up
> done
>
> I have done this with Xen on 5.5, 5.6 and 5.7... but it should work for
> KVM. If you create the standard bridge interface br0 using just bond0
> that will get you a trunk on whatever the native vlan is for that trunk.
>
> Tait
>
>
> _______________________________________________
> CentOS-virt mailing list
> CentOS-virt at centos.org
> http://lists.centos.org/mailman/listinfo/centos-virt
>


From jason at daylife.com  Wed Nov 23 21:49:56 2011
From: jason at daylife.com (Jason Nagashima)
Date: Wed, 23 Nov 2011 16:49:56 -0500 (EST)
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <CAAsqWCd+KWrX-SpRcYVNzCVC4HDV25C1QeOZzu-ChN0ZHyhdBw@mail.gmail.com>
Message-ID: <206550579.4866.1322084996341.JavaMail.root@mailbox01.hq.daylife.com>

Awesome!

Thank you everyone for responding and helping out. I'm happy to report that we got it working!

Cheers,
Jason

----- Original Message -----
From: "David Martin" <dmartls1 at gmail.com>
To: "Discussion about the virtualization on CentOS" <centos-virt at centos.org>
Sent: Tuesday, November 22, 2011 12:39:02 PM
Subject: Re: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6

We are doing this quite a bit in production and it works great.

bond as you normally would:
DEVICE=bond0
ONBOOT=yes
USERCTL=no
BONDING_OPTS="mode=4 miimon=100"

one of these for each vlan (in this case 50):
VLAN=yes
VLAN_NAME_TYPE=VLAN_PLUS_VID_NO_PAD
DEVICE=vlan50
PHYSDEV=bond0
TYPE=Ethernet
ONBOOT=yes
BRIDGE=br50

and finally the bridge device to expose to guests:
DEVICE=br50
TYPE=Bridge
ONBOOT=yes
DELAY=0
GATEWAYDEV=none




On Tue, Nov 22, 2011 at 10:07 AM, Tait Clarridge <tait at taiter.com> wrote:
> On Fri, 2011-11-18 at 17:56 -0500, Jason Nagashima wrote:
>> Running on Centos 5.6 with KVM...
>>
>> I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?
>>
>> I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it. ?There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.
>>
>> Any advice/working examples would be greatly appreciated.
>
> Hi Jason,
>
> I have had luck doing this with Xen, where I create bond0 on a trunk
> interface and have xen bring it up as xenbr0 with pbond0 in the back
> end.
>
> You should be able to do roughly the same by creating a bridge interface
> in /etc/sysconfig/network-scripts referencing bond0 as a member.
>
> After that you should be able to run a script to create VLAN bridges
> like the following:
>
> #!/bin/bash
> /sbin/modprobe 8021q
>
> # Add your vlans here that you want with the numbers separated by a
> # space
> VLANS="5 10 15 20"
> # This should work with the bonding interface
> TRUNKINT="bond0"
> for VLAN in $VLANS
> do
> ? ? ? ?vconfig add $TRUNKINT $VLAN
> ? ? ? ?brctl add br$VLAN
> ? ? ? ?brctl addif br$VLAN $TRUNKINT.$VLAN
> ? ? ? ?ifconfig $TRUNKINT.$VLAN up
> ? ? ? ?ifconfig br$VLAN up
> done
>
> I have done this with Xen on 5.5, 5.6 and 5.7... but it should work for
> KVM. If you create the standard bridge interface br0 using just bond0
> that will get you a trunk on whatever the native vlan is for that trunk.
>
> Tait
>
>
> _______________________________________________
> CentOS-virt mailing list
> CentOS-virt at centos.org
> http://lists.centos.org/mailman/listinfo/centos-virt
>
_______________________________________________
CentOS-virt mailing list
CentOS-virt at centos.org
http://lists.centos.org/mailman/listinfo/centos-virt


From mdra137 at gmail.com  Fri Nov 25 11:11:44 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Fri, 25 Nov 2011 12:11:44 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0BCpJuchqLS6vws9Sm+_YPbR3AkLVyiKBQpJAPDGvzSGQ@mail.gmail.com>

Finally, I managed to solve the problem. The problem was rather strange -
after configuring bridges I added new ifaces to the VM. For some reason,
during boot process of the VM's, wrong interface was started (VM tried to
bring up eth2 instead eth1?).

After adding the new ifaces through virt-manager, the VM started regulary
and created a new network script for eth2
(/etc/sysconfig/network-scripts/ifcfg-eth2). I think that the problem was
this - when the VM is restarted it tried to bring up eth2 while vif-script
tried to propagate second bridge via eth1 iface. I resolved this simply by
replacing ifcfg-eth2 script with ifcfg-eth1. Now, VM starts/restarts
regulary ;)

So, the process for creating and configuring new bridges that I follow is
(tried on multiple servers):

- create new script that sets up multiple bridges in /etc/xen/scripts/

example: network-xen-multi-bridge

#!/bin/sh
# network-xen-multi-bridge
# Exit if anything goes wrong.
set -e
# First arg is the operation.
OP=$1
shift
script=/etc/xen/scripts/network-bridge.xen
case ${OP} in
start)
        $script start vifnum=3 bridge=xenbr3 netdev=eth3
        $script start vifnum=0 bridge=xenbr0 netdev=eth0
        ;;
stop)
        $script stop vifnum=3 bridge=xenbr3 netdev=eth3
        $script stop vifnum=0 bridge=xenbr0 netdev=eth0
        ;;
status)
        $script status vifnum=3 bridge=xenbr3 netdev=eth3
        $script status vifnum=0 bridge=xenbr0 netdev=eth0
        ;;
*)
        echo 'Unknown command: ' ${OP}
        echo 'Valid commands are: start, stop, status'
        exit 1
esac



- make it executable (chmod 755 network-xen-multi-bridge)

- configure /etc/xen/xend-config.sxp (comment out the current script and
add the new one);

# It is possible to use the network-bridge script in more complicated
# scenarios, such as having two outgoing interfaces, with two bridges, and
# two fake interfaces per guest domain.  To do things like this, write
# yourself a wrapper script, and call network-bridge from it, as appropriate.
#
#(network-script network-bridge)
(network-script  network-xen-multi-bridge)



- restart physical server so the bridges are properly created

- add virt. ifaces to the VM's (via virt-manager or via config. files in
/etc/xen/ ..)

- boot VM

- configure newly added iface in /etc/sysconfig/network-scripts/

- restart VM

Additionaly I check everything by restarting phys. server to make sure that
everything is ok ;)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111125/1304c71b/attachment-0004.html>

From mail-lists at karan.org  Sat Nov 26 00:29:20 2011
From: mail-lists at karan.org (Karanbir Singh)
Date: Sat, 26 Nov 2011 00:29:20 +0000
Subject: [CentOS-virt] Device renaming heads up
Message-ID: <4ED032E0.1040109@karan.org>

hi Guys,

Just in case anyone hasent noticed this :
https://bugzilla.redhat.com/show_bug.cgi?id=729586 device naming mixup
causing lots of domU's to not come back after a kernel update...

- KB


From toddandmargo at gmail.com  Mon Nov 28 18:37:50 2011
From: toddandmargo at gmail.com (Todd And Margo Chester)
Date: Mon, 28 Nov 2011 10:37:50 -0800
Subject: [CentOS-virt] kvm: w7 bsod's at shutdown
Message-ID: <4ED3D4FE.9090008@gmail.com>

Hi All,

I am using Scientific Linux 6.1 x64

Any idea how to get my W7 x32 guest to shutdown with out a BSOD?
I have to go into virt-manager and kill it all the time.  My XP guest
shuts down without issue.

Many thanks,
-T

$ rpm -qa \*kvm\*
qemu-kvm-0.12.1.2-2.160.el6_1.2.x86_64

$ rpm -qa \*virt\*
python-virtinst-0.500.5-3.el6.noarch
libvirt-0.8.7-18.el6_1.1.x86_64
libvirt-client-0.8.7-18.el6_1.1.x86_64
virt-manager-0.8.6-4.el6.noarch
libvirt-python-0.8.7-18.el6_1.1.x86_64



From byrnejb at harte-lyne.ca  Tue Nov 29 20:51:45 2011
From: byrnejb at harte-lyne.ca (James B. Byrne)
Date: Tue, 29 Nov 2011 15:51:45 -0500 (EST)
Subject: [CentOS-virt] Transfer of LVM based guests
Message-ID: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>

I am investigating the procedure to follow when moving a
KVM guest instance from one host to another where the
guest uses LVM as its storage.  As a preliminary cut I
have cobbled the following together from various sources
located through Google searches:

1.  Log in to vmhost_old

2.  Shutdown guest

3.  Create an LVM snapshot of the guest volume
3.a.   lvcreate -s -L 300m -n LVM_guest_snapshot guest_lv

4.  Convert snapshot to a file image
4.a    dd if=/dev/vhost/LVM_guest_snapshot
          of=/tmp/fs/LVM_guest_snapshot.img bs=4096

5.  Remove the original snapshot
5.a    lvremove /dev/vhost/LVM_guest_snapshot

6.  Move the snapshot image file to the new KVM host. Note
that for large vm guest images tape transport is probably
better than network transfers.

7.  Log in to vhost_new

8.  Create a new lv on the new vhost
8.a    lvcreate -n guest_name_lv -L 60G vhost_new_vg

9.  Copy transferred image to new LV
9.a    dd if=tmp/LVM_guest_snapshot.img
       of=/dev/vhost_new/guest_name_lv bs=4096

10.  Copy guest xml file from vhost_old via sftp
10.a.   get /etc/libvirt/qemu/guest_name.xml \
           /etc/libvirt/qemu/guest_name.xml

11. Start new guest?


Is there anything obviously wrong or omitted from this?


-- 
***          E-Mail is NOT a SECURE channel          ***
James B. Byrne                mailto:ByrneJB at Harte-Lyne.ca
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3



From Ed at Heron-ent.com  Tue Nov 29 22:11:01 2011
From: Ed at Heron-ent.com (Ed Heron)
Date: Tue, 29 Nov 2011 15:11:01 -0700
Subject: [CentOS-virt] Transfer of LVM based guests
In-Reply-To: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
References: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
Message-ID: <1322604661.4811.13.camel@elap.rgtravel.com>

On Tue, 2011-11-29 at 15:51 -0500, James B. Byrne wrote:
> I am investigating the procedure to follow when moving a
> KVM guest instance from one host to another where the
> guest uses LVM as its storage.  As a preliminary cut I
> have cobbled the following together from various sources
> located through Google searches:
> ...

  If you are moving the virtual disk, you can't run the virtual machine while you are moving it.  Therefore, taking a snapshot (and removing it later) is superfluous.

  I use md5sum to give myself some extra re-assurance that a copy that big is accurate.

  Are the virtualization servers at the same location?

  How often do you move virtual machines?

  If your virtualization servers are in the same location, you might want to look into setting up a LAN for transferring virtual machine images.  It would only take an extra network card in each virtualization server and a Gb Ethernet switch (or better).

  If you are interested in virtual disk replication, you might want to look at DRBD.  It adds an extra layer to your storage, but allows for hot replication of disk space which would allow you to start a virtual machine on any virtualization server.




From byrnejb at harte-lyne.ca  Wed Nov 30 16:23:11 2011
From: byrnejb at harte-lyne.ca (James B. Byrne)
Date: Wed, 30 Nov 2011 11:23:11 -0500 (EST)
Subject: [CentOS-virt] Transfer of LVM based guests
In-Reply-To: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
References: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
Message-ID: <40363.216.185.71.25.1322670191.squirrel@webmail.harte-lyne.ca>


On Tue, November 29, 2011 17:11:01, Ed Heron Ed at
Heron-ent.com wrote:

> If you are moving the virtual disk, you can't run
> the virtual machine while you are moving it.
> Therefore, taking a snapshot (and removing it later)
> is superfluous.

Point taken.

> I use md5sum to give myself some extra re-assurance
> that a copy that big is accurate.

Good idea.

> Are the virtualization servers at the same location?

At the moment. It is planned that there will be two vhosts
at each of two different locations, one backing up the
other.

>  How often do you move virtual machines?

I have not moved any as of yet.  I am investigating how to
do this as part of setting up our first virtual server
host.  I am discovering what is possible and the
techniques used.  Moving vm guests is not being considered
for load balancing but is under consideration for
providing warm spares for use in a DR situation.

> If your virtualization servers are in the same
> location, you might want to look into setting up a
> LAN for transferring virtual machine images.  It
> would only take an extra network card in each
> virtualization server and a Gb Ethernet switch
> (or better).

Our vhosts all (will) have two nics, one for public IPs
and one for private IPs.  The private IPs are used for
vhost management.  The experimental vhost is so equipped.

> If you are interested in virtual disk replication,
> you might want to look at DRBD.  It adds an extra layer
> to your storage, but allows for hot replication of
> disk space which would allow you to start a virtual
> machine on any virtualization server.

This is a useful suggestion. However, I find that the
availability of a DRDB package on CentOS-6 is presently an
issue.  And, our vm project has already expanded into
multiple areas with commensurate delays.  I think that I
will leave DRDB for a later time.

So, what I now have for a proposed procedure is:

1.  Log in to vmhost_old

2.  Shutdown guest

3.  Convert guest lvs to file images for each lv
3.a    dd if=/dev/vhost/lv_vhost_guest
          of=/tmp/fs/lv_vhost_guest.img bs=4096

4.  Create MD5 hash for each image file
4.a    md5sum /tmp/fs/lv_vhost_guest.img > \
              /tmp/fs/lv_vhost_guest.md5

5.  Move the guest image file(s)  and the checksum file to
the new vhost; preserving both the directory structure and
file names or subsequently modifying the file names in the
md5 checksum file. Note that for large vm guest images
tape transport is probably better than network transfers.

6.  Log in to vhost_new

7.  Verify md5 checksum(s) on transferred file(s).
7.a    md5sum -c /tmp/fs/lv_vhost_guest.md5

8.  Create a new lv(s) on the new vhost. Ensure sufficient
size.
8.a    lvcreate -n lv_guest_name -L 60G vhost_new_vg

9.  Copy transferred image to new LV
9.a    dd if=/tmp/fs/lv_vhost_guest.img
       of=/dev/vhost_new/lv_guest_name bs=4096

10.  Copy guest xml file from vhost_old via sftp
10.a.   get /etc/libvirt/qemu/guest_name.xml \
           /etc/libvirt/qemu/guest_name.xml

11. Start new guest?


Thanks,


-- 
***          E-Mail is NOT a SECURE channel          ***
James B. Byrne                mailto:ByrneJB at Harte-Lyne.ca
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3



From raju.rajsand at gmail.com  Mon Nov  7 18:17:22 2011
From: raju.rajsand at gmail.com (Rajagopal Swaminathan)
Date: Mon, 7 Nov 2011 23:47:22 +0530
Subject: [CentOS-virt] P2V utility
Message-ID: <CA+YdgaqusA9ZR2ekkyXtkggKBsH73=HYe1c=XVTSnq7OQ_kq+Q@mail.gmail.com>

Greetings,

An somebody pint to me to P2V Utility for the m$ world?

Like in VMware?

-- 
Regards,

Rajagopal


From lorenzo at tulug.it  Tue Nov  8 14:20:52 2011
From: lorenzo at tulug.it (Lorenzo)
Date: Tue, 8 Nov 2011 15:20:52 +0100
Subject: [CentOS-virt] P2V utility
In-Reply-To: <CA+YdgaqusA9ZR2ekkyXtkggKBsH73=HYe1c=XVTSnq7OQ_kq+Q@mail.gmail.com>
References: <CA+YdgaqusA9ZR2ekkyXtkggKBsH73=HYe1c=XVTSnq7OQ_kq+Q@mail.gmail.com>
Message-ID: <CADE4e0WfAq++1UDq-Vj3EhR=K1=xQTwmU0qsVhLrXVKgy+SDhg@mail.gmail.com>

2011/11/7 Rajagopal Swaminathan <raju.rajsand at gmail.com>:
> Greetings,
>
> An somebody pint to me to P2V Utility for the m$ world?
>
> Like in VMware?
>
> --
> Regards,
>
> Rajagopal

Try here:
http://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE
not centos specific, but I found a lot of useful info.

Regards,
Lorenzo


From mdra137 at gmail.com  Fri Nov 18 13:39:23 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Fri, 18 Nov 2011 14:39:23 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0BmRWi7_=FEJ0WSTzs5J1-2wuJ_AZdN=_S8WKWg94E_Vg@mail.gmail.com>

Hi,

I've been using CentOS & Xen on a server that has 2 VM's configured. The
default configuration includes one physical iface that is propagated (by a
default bridge) to the VM's.

Since I wanted to configure additional physical iface, define a new bridge
and propagate it to the viface-s of the VM's, i configured the bridge/phys.
iface and brought it up (here are configurations that I set up):

-> eth3
DEVICE=eth3
BOOTPROTO=static
HWADDR=D4:85:64:4B:76:AB
ONBOOT=yes
#HOTPLUG=no
#DHCP_HOSTNAME=kdr-3k-4r-3o-07
BRIDGE=br0
TYPE=Ethernet

-> br0
DEVICE=br0
TYPE=Bridge
BOOTPROTO=none
ONBOOT=yes

Then I configured new virt. ifaces on VM's (using virsh edit, config is
listed below):

<interface type='bridge'>
<mac address='00:16:36:17:62:5d'/>
<source bridge='xenbr0'/>
<script path='vif-bridge'/>
<target dev='vif5.0'/>
</interface>
<interface type='bridge'>
<mac address='00:16:3e:ca:63:39'/>
<source bridge='br0'/>
<script path='vif-bridge'/>
<target dev='vif5.1'/>
</interface>

You can see the default bridge (xenbr0 -> vif5.0) and my new bridge br0
connected to vif5.1.

So, here I got stuck up - when I try tu start a VM (xm create VIRT_SRV),
the VM starts booting but hangs up (I can ping it form another srv., but
when I try SSH it says "connection refused"). When I remove configuration
for vif5.1 the VM starts up normally. I actually managed to start VM with
vif5.1 up once, but next time I restarted it, the problem was there :/


Furthermore, I noticed this in the Xen log:

[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vif.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 0.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vif/1/1/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices usb.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vbd.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 768.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vbd/1/768/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 5632.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vbd/1/5632/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices irq.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vkbd.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vfb.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices pci.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices ioports.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices tap.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vtpm.

So the boot process goes on regulary until the last line ("Waiting for
devices vtpm"). It seems like TPM makes it impossible for VM's to start
regulary. When I open the VM's console (with virt-manager) I see the whole
boot process but it hangs when it tries to start iface eth2 (attached to
the second bridge) ...

Does anybody have a clue why is this happening?

Thanks in advance ..
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111118/e056a2eb/attachment-0005.html>

From peter.peltonen at gmail.com  Fri Nov 18 14:33:35 2011
From: peter.peltonen at gmail.com (Peter Peltonen)
Date: Fri, 18 Nov 2011 16:33:35 +0200
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
In-Reply-To: <CALZem0BmRWi7_=FEJ0WSTzs5J1-2wuJ_AZdN=_S8WKWg94E_Vg@mail.gmail.com>
References: <CALZem0BmRWi7_=FEJ0WSTzs5J1-2wuJ_AZdN=_S8WKWg94E_Vg@mail.gmail.com>
Message-ID: <CAGTVFvHkhkUytpf9ei2vGT0_NhLsOhXikDPV9ORAKYitttjCdA@mail.gmail.com>

Hi,

2011/11/18 Matija Draganovi? <mdra137 at gmail.com>:
> I've been using CentOS & Xen on a server that has 2 VM's configured. The
> default configuration includes one physical iface that is propagated (by a
> default bridge) to the VM's.

You do not mention which version of CentOS and Xen you are using?

>
> Since I wanted to configure additional physical iface, define a new bridge
> and propagate it to the viface-s of the VM's, i configured the bridge/phys.
> iface and brought it up (here are configurations that I set up):
>
> -> eth3
> DEVICE=eth3
> BOOTPROTO=static
> HWADDR=D4:85:64:4B:76:AB
> ONBOOT=yes
> #HOTPLUG=no
> #DHCP_HOSTNAME=kdr-3k-4r-3o-07
> BRIDGE=br0
> TYPE=Ethernet
>
> -> br0
> DEVICE=br0
> TYPE=Bridge
> BOOTPROTO=none
> ONBOOT=yes

If this is a CentOS5 machine with the CentOS provided Xen 3.0
packages, then here is info how i got my bridges to work with that
setup:

* For dom0 I configured eth0 and eth1 as usual in /etc/sysconfig/network-scripts

* I did not configure br0 or br1 in network-scripts, but instead I
created a file called /etc/xen/scripts/my-network-script having this
contents:

#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0
"$dir/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=xenbr1

* Then I modified in dom0 the file /etc/xen/xend-config.sxp in the
following way:

#(network-script network-bridge)
(network-script my-network-script)

* Now rebooting dom0 made the bridges available

* After that I could configure them in my domU config:

vif = [ "mac=00:16:3E:69:29:25,bridge=xenbr0,script=vif-bridge","mac=00:16:3E:E6:B0:6D,bridge=xenbr1,script=vif-bridge"
]

* After starting the domU I could configure the interfaces in
network-scripts using the hardware addresses specified in the domU
config


It seems that configuring bridging is done a bit differently in
different Xen versions, so this might not work if you are using some
other kind of config. With CentOS6 and 3rd party Xen 4.1 packages this
procedure did not work at all and instead I needed to do the
following:

* in dom0 create the br0 and br1 devices in network-scripts

* in dom0 /etc/xen/xend-config.sxp put instead:

#(network-script network-bridge)
(network-script /bin/true)

* and in dom0 use different configuration for the domU config files like this:

vif = [ "mac=00:16:3E:69:29:25,bridge=br0","mac=00:16:3E:E6:B0:6D,bridge=br1" ]


Hope this helps, unfortuantely I am not familiar with virsh at all.

Best,
Peter


From mdra137 at gmail.com  Fri Nov 18 17:17:17 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Fri, 18 Nov 2011 18:17:17 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0D1Z-dbkvM+-0+DgVGSGd_dHa757rSqMUZcAgCfffstwQ@mail.gmail.com>

Dear Peter,


Thanks for your reply. I was so occupied with troubleshooting that I forgot
to mention the OS & Xen version :)

My CentOS version is
CentOS release 5.7 (Final)
Linux 2.6.18-274.7.1.el5xen #1 SMP Thu Oct 20 17:06:34 EDT 2011 x86_64
x86_64 x86_64 GNU/Linux

and Xen v3.0.

I tried creating bridges the same way you did and succedded. I also tried
doing the same via ifcfg scripts, and it also worked.

I have no problem with creating bridges and connecting them with physical
ifaces, but I can't start my VM's (most of the time one VM start but the
other one hangs while trying to initalize eth2 that is connected to my
second (non default - xenbr1) bridge)).

The only diference between your config and mine is that I have vifname-s
listed (example below):

vif = [
"mac=00:16:36:72:35:e5,bridge=xenbr0,script=vif-bridge,vifname=vif4.0",
"mac=00:16:3e:57:de:0d,bridge=xenbr1,script=vif-bridge, vifname=vif4.1" ]

I'm not saying that this could be the problem, but since I'm slowly running
out of ideas - it's a longshot :)

So, to sum it all up - I can create bridges properly, but my VM's hang when
they try to bring up vifaces connected to the xenbr1. Also, I have no
problem with having only one bridge active - problem appears when I have
multiple bridges.

Br,
Matija
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111118/2a75ed85/attachment-0005.html>

From maillists at conactive.com  Fri Nov 18 18:33:20 2011
From: maillists at conactive.com (Kai Schaetzl)
Date: Fri, 18 Nov 2011 19:33:20 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
In-Reply-To: <CALZem0D1Z-dbkvM+-0+DgVGSGd_dHa757rSqMUZcAgCfffstwQ@mail.gmail.com>
References: <CALZem0D1Z-dbkvM+-0+DgVGSGd_dHa757rSqMUZcAgCfffstwQ@mail.gmail.com>
Message-ID: <VA.00003db7.1907ac90@news.conactive.com>

Matija Draganovi? wrote on Fri, 18 Nov 2011 18:17:17 +0100:

> The only diference between your config and mine is that I have vifname-s
> listed

Then remove it. I've never seen it like that. If I remember it correctly 
the vifnames are created dynamically. You can't rely on them I suppose.

And I don't remember using "script" either.

If you can't get it to work then use the second method Peter describes. 
That one should also work for Xen 3.0 and is guaranteed to create stable 
bridging.



Kai

-- 
Get your web at Conactive Internet Services: http://www.conactive.com





From jason at daylife.com  Fri Nov 18 22:56:02 2011
From: jason at daylife.com (Jason Nagashima)
Date: Fri, 18 Nov 2011 17:56:02 -0500 (EST)
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <1331504081.4540.1321656727740.JavaMail.root@mailbox01.hq.daylife.com>
Message-ID: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>

Running on Centos 5.6 with KVM... 

I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?

I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it.  There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.

Any advice/working examples would be greatly appreciated.

Regards,
Jason


From incoming-centos at rjl.com  Sat Nov 19 04:34:25 2011
From: incoming-centos at rjl.com (Nataraj)
Date: Fri, 18 Nov 2011 20:34:25 -0800
Subject: [CentOS-virt] high resolution video for kvm vm
Message-ID: <4EC731D1.40109@rjl.com>

I'm running a fuduntu vm (based on fedora 14)  on a CentOS 6 kvm
server.  I have tried changing the video in virt-manager from cirrus to
vga and restarting the VM, but the maximum resolution that the client
will let me set is still only 1024x768.  Should I be able to get  high
res video with the kvm VGA mode?  Note that the VM is running on a
CentOS server while virt-manager is running on my local desktop.

Would I be better off trying to get the vmware VGA driver working?  I'm
assuming I have to extract the driver from the vmware tools package and
manually install it into the X server, because VMware tools won't
install under kvm.

Also, I run with the keyboard option to swap caps lock and control on my
linux desktop, which does not seem to get passed through to the guest. 
I tried setting the same swap caps lock and control option in the guest,
but it does not work.  Any ideas?

Thanks,
Nataraj



From mdra137 at gmail.com  Sat Nov 19 06:32:21 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Sat, 19 Nov 2011 07:32:21 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0A+hx+b2OFOEYD-YdpXxV9Y=jFUP=UTjgFLBqBqca78YQ@mail.gmail.com>

I tried to remove vifname and vif-script but the problem remains. I think
that the bridges are ok, but for some reason VM's hang when they try to
connect their vifaces to them.

I'll try some different configurations of the physical ifaces (an vifaces
also), maybe I'll be able to find out something. Also, I'll focus on the
vTPM, since the following line shows up in the Xen log when the VM tries to
bring up the iface connected to the second bridge:

[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vtpm


Furthermore, it appears that sometimes the VM's manage to start regulary, I
just can't figure out when & why :/

Tnx for your comments ..

Br,
M.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111119/cc41e78f/attachment-0005.html>

From mdra137 at gmail.com  Tue Nov 22 09:37:31 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Tue, 22 Nov 2011 10:37:31 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0AS0ptzxMRXooEFHLCAR=OCnaFcXS5AcMmQduevWSFjrQ@mail.gmail.com>

Ok, after trying multiple different configurations I decided to play by the
book - I removed ifcfg script for creating the additional bridge and set up
an Xen script. So my new configuration is:

-> eth3 (my physical interface)
# NetXen Incorporated NX3031 Multifunction 1/10-Gigabit Server Adapter
DEVICE=eth3
BOOTPROTO=static
HWADDR= ...
ONBOOT=yes
IPADDR= ...
NETMASK= ...
NETWORK= ...

and the network-xen-multi-bridge script:

#!/bin/sh
# network-xen-multi-bridge
# Exit if anything goes wrong.
set -e
# First arg is the operation.
OP=$1
shift
script=/etc/xen/scripts/network-bridge.xen
case ${OP} in
start)
$script start vifnum=3 bridge=xenbr3 netdev=eth3
$script start vifnum=0 bridge=xenbr0 netdev=eth0
;;
stop)
$script stop vifnum=3 bridge=xenbr3 netdev=eth3
$script stop vifnum=0 bridge=xenbr0 netdev=eth0
;;
status)
$script status vifnum=3 bridge=xenbr3 netdev=eth3
$script status vifnum=0 bridge=xenbr0 netdev=eth0
;;
*)
echo 'Unknown command: ' ${OP}
echo 'Valid commands are: start, stop, status'
exit 1
esac

After I restart the physical server bridges are set up correctly:

# brctl show
bridge name bridge id STP enabled interfaces
virbr0 8000.000000000000 yes
xenbr0 8000.feffffffffff no vif0.0
peth0
xenbr3 8000.feffffffffff no vif0.3
peth3

Unfortunately, this did not solve the problem - I manage to start one VM
(connected to both of the bridges), but when I try to start the other one,
it just hangs when trying to bring up the second interface (connected to
xenbr3) :/

I'm currently completely out of ideas, but I'm not giving up ;)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111122/eb760bb6/attachment-0005.html>

From tait at taiter.com  Tue Nov 22 16:07:54 2011
From: tait at taiter.com (Tait Clarridge)
Date: Tue, 22 Nov 2011 11:07:54 -0500
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>
References: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>
Message-ID: <1321978074.22491.12.camel@tclarrltp.frontiernetworks.ca>

On Fri, 2011-11-18 at 17:56 -0500, Jason Nagashima wrote:
> Running on Centos 5.6 with KVM... 
> 
> I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?
> 
> I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it.  There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.
> 
> Any advice/working examples would be greatly appreciated.

Hi Jason,

I have had luck doing this with Xen, where I create bond0 on a trunk
interface and have xen bring it up as xenbr0 with pbond0 in the back
end.

You should be able to do roughly the same by creating a bridge interface
in /etc/sysconfig/network-scripts referencing bond0 as a member.

After that you should be able to run a script to create VLAN bridges
like the following:

#!/bin/bash
/sbin/modprobe 8021q

# Add your vlans here that you want with the numbers separated by a 
# space
VLANS="5 10 15 20"
# This should work with the bonding interface
TRUNKINT="bond0"
for VLAN in $VLANS
do
	vconfig add $TRUNKINT $VLAN
	brctl add br$VLAN
	brctl addif br$VLAN $TRUNKINT.$VLAN
	ifconfig $TRUNKINT.$VLAN up
	ifconfig br$VLAN up
done

I have done this with Xen on 5.5, 5.6 and 5.7... but it should work for
KVM. If you create the standard bridge interface br0 using just bond0
that will get you a trunk on whatever the native vlan is for that trunk.

Tait




From dmartls1 at gmail.com  Tue Nov 22 17:39:02 2011
From: dmartls1 at gmail.com (David Martin)
Date: Tue, 22 Nov 2011 11:39:02 -0600
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <1321978074.22491.12.camel@tclarrltp.frontiernetworks.ca>
References: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>
	<1321978074.22491.12.camel@tclarrltp.frontiernetworks.ca>
Message-ID: <CAAsqWCd+KWrX-SpRcYVNzCVC4HDV25C1QeOZzu-ChN0ZHyhdBw@mail.gmail.com>

We are doing this quite a bit in production and it works great.

bond as you normally would:
DEVICE=bond0
ONBOOT=yes
USERCTL=no
BONDING_OPTS="mode=4 miimon=100"

one of these for each vlan (in this case 50):
VLAN=yes
VLAN_NAME_TYPE=VLAN_PLUS_VID_NO_PAD
DEVICE=vlan50
PHYSDEV=bond0
TYPE=Ethernet
ONBOOT=yes
BRIDGE=br50

and finally the bridge device to expose to guests:
DEVICE=br50
TYPE=Bridge
ONBOOT=yes
DELAY=0
GATEWAYDEV=none




On Tue, Nov 22, 2011 at 10:07 AM, Tait Clarridge <tait at taiter.com> wrote:
> On Fri, 2011-11-18 at 17:56 -0500, Jason Nagashima wrote:
>> Running on Centos 5.6 with KVM...
>>
>> I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?
>>
>> I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it. ?There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.
>>
>> Any advice/working examples would be greatly appreciated.
>
> Hi Jason,
>
> I have had luck doing this with Xen, where I create bond0 on a trunk
> interface and have xen bring it up as xenbr0 with pbond0 in the back
> end.
>
> You should be able to do roughly the same by creating a bridge interface
> in /etc/sysconfig/network-scripts referencing bond0 as a member.
>
> After that you should be able to run a script to create VLAN bridges
> like the following:
>
> #!/bin/bash
> /sbin/modprobe 8021q
>
> # Add your vlans here that you want with the numbers separated by a
> # space
> VLANS="5 10 15 20"
> # This should work with the bonding interface
> TRUNKINT="bond0"
> for VLAN in $VLANS
> do
> ? ? ? ?vconfig add $TRUNKINT $VLAN
> ? ? ? ?brctl add br$VLAN
> ? ? ? ?brctl addif br$VLAN $TRUNKINT.$VLAN
> ? ? ? ?ifconfig $TRUNKINT.$VLAN up
> ? ? ? ?ifconfig br$VLAN up
> done
>
> I have done this with Xen on 5.5, 5.6 and 5.7... but it should work for
> KVM. If you create the standard bridge interface br0 using just bond0
> that will get you a trunk on whatever the native vlan is for that trunk.
>
> Tait
>
>
> _______________________________________________
> CentOS-virt mailing list
> CentOS-virt at centos.org
> http://lists.centos.org/mailman/listinfo/centos-virt
>


From jason at daylife.com  Wed Nov 23 21:49:56 2011
From: jason at daylife.com (Jason Nagashima)
Date: Wed, 23 Nov 2011 16:49:56 -0500 (EST)
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <CAAsqWCd+KWrX-SpRcYVNzCVC4HDV25C1QeOZzu-ChN0ZHyhdBw@mail.gmail.com>
Message-ID: <206550579.4866.1322084996341.JavaMail.root@mailbox01.hq.daylife.com>

Awesome!

Thank you everyone for responding and helping out. I'm happy to report that we got it working!

Cheers,
Jason

----- Original Message -----
From: "David Martin" <dmartls1 at gmail.com>
To: "Discussion about the virtualization on CentOS" <centos-virt at centos.org>
Sent: Tuesday, November 22, 2011 12:39:02 PM
Subject: Re: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6

We are doing this quite a bit in production and it works great.

bond as you normally would:
DEVICE=bond0
ONBOOT=yes
USERCTL=no
BONDING_OPTS="mode=4 miimon=100"

one of these for each vlan (in this case 50):
VLAN=yes
VLAN_NAME_TYPE=VLAN_PLUS_VID_NO_PAD
DEVICE=vlan50
PHYSDEV=bond0
TYPE=Ethernet
ONBOOT=yes
BRIDGE=br50

and finally the bridge device to expose to guests:
DEVICE=br50
TYPE=Bridge
ONBOOT=yes
DELAY=0
GATEWAYDEV=none




On Tue, Nov 22, 2011 at 10:07 AM, Tait Clarridge <tait at taiter.com> wrote:
> On Fri, 2011-11-18 at 17:56 -0500, Jason Nagashima wrote:
>> Running on Centos 5.6 with KVM...
>>
>> I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?
>>
>> I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it. ?There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.
>>
>> Any advice/working examples would be greatly appreciated.
>
> Hi Jason,
>
> I have had luck doing this with Xen, where I create bond0 on a trunk
> interface and have xen bring it up as xenbr0 with pbond0 in the back
> end.
>
> You should be able to do roughly the same by creating a bridge interface
> in /etc/sysconfig/network-scripts referencing bond0 as a member.
>
> After that you should be able to run a script to create VLAN bridges
> like the following:
>
> #!/bin/bash
> /sbin/modprobe 8021q
>
> # Add your vlans here that you want with the numbers separated by a
> # space
> VLANS="5 10 15 20"
> # This should work with the bonding interface
> TRUNKINT="bond0"
> for VLAN in $VLANS
> do
> ? ? ? ?vconfig add $TRUNKINT $VLAN
> ? ? ? ?brctl add br$VLAN
> ? ? ? ?brctl addif br$VLAN $TRUNKINT.$VLAN
> ? ? ? ?ifconfig $TRUNKINT.$VLAN up
> ? ? ? ?ifconfig br$VLAN up
> done
>
> I have done this with Xen on 5.5, 5.6 and 5.7... but it should work for
> KVM. If you create the standard bridge interface br0 using just bond0
> that will get you a trunk on whatever the native vlan is for that trunk.
>
> Tait
>
>
> _______________________________________________
> CentOS-virt mailing list
> CentOS-virt at centos.org
> http://lists.centos.org/mailman/listinfo/centos-virt
>
_______________________________________________
CentOS-virt mailing list
CentOS-virt at centos.org
http://lists.centos.org/mailman/listinfo/centos-virt


From mdra137 at gmail.com  Fri Nov 25 11:11:44 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Fri, 25 Nov 2011 12:11:44 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0BCpJuchqLS6vws9Sm+_YPbR3AkLVyiKBQpJAPDGvzSGQ@mail.gmail.com>

Finally, I managed to solve the problem. The problem was rather strange -
after configuring bridges I added new ifaces to the VM. For some reason,
during boot process of the VM's, wrong interface was started (VM tried to
bring up eth2 instead eth1?).

After adding the new ifaces through virt-manager, the VM started regulary
and created a new network script for eth2
(/etc/sysconfig/network-scripts/ifcfg-eth2). I think that the problem was
this - when the VM is restarted it tried to bring up eth2 while vif-script
tried to propagate second bridge via eth1 iface. I resolved this simply by
replacing ifcfg-eth2 script with ifcfg-eth1. Now, VM starts/restarts
regulary ;)

So, the process for creating and configuring new bridges that I follow is
(tried on multiple servers):

- create new script that sets up multiple bridges in /etc/xen/scripts/

example: network-xen-multi-bridge

#!/bin/sh
# network-xen-multi-bridge
# Exit if anything goes wrong.
set -e
# First arg is the operation.
OP=$1
shift
script=/etc/xen/scripts/network-bridge.xen
case ${OP} in
start)
        $script start vifnum=3 bridge=xenbr3 netdev=eth3
        $script start vifnum=0 bridge=xenbr0 netdev=eth0
        ;;
stop)
        $script stop vifnum=3 bridge=xenbr3 netdev=eth3
        $script stop vifnum=0 bridge=xenbr0 netdev=eth0
        ;;
status)
        $script status vifnum=3 bridge=xenbr3 netdev=eth3
        $script status vifnum=0 bridge=xenbr0 netdev=eth0
        ;;
*)
        echo 'Unknown command: ' ${OP}
        echo 'Valid commands are: start, stop, status'
        exit 1
esac



- make it executable (chmod 755 network-xen-multi-bridge)

- configure /etc/xen/xend-config.sxp (comment out the current script and
add the new one);

# It is possible to use the network-bridge script in more complicated
# scenarios, such as having two outgoing interfaces, with two bridges, and
# two fake interfaces per guest domain.  To do things like this, write
# yourself a wrapper script, and call network-bridge from it, as appropriate.
#
#(network-script network-bridge)
(network-script  network-xen-multi-bridge)



- restart physical server so the bridges are properly created

- add virt. ifaces to the VM's (via virt-manager or via config. files in
/etc/xen/ ..)

- boot VM

- configure newly added iface in /etc/sysconfig/network-scripts/

- restart VM

Additionaly I check everything by restarting phys. server to make sure that
everything is ok ;)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111125/1304c71b/attachment-0005.html>

From mail-lists at karan.org  Sat Nov 26 00:29:20 2011
From: mail-lists at karan.org (Karanbir Singh)
Date: Sat, 26 Nov 2011 00:29:20 +0000
Subject: [CentOS-virt] Device renaming heads up
Message-ID: <4ED032E0.1040109@karan.org>

hi Guys,

Just in case anyone hasent noticed this :
https://bugzilla.redhat.com/show_bug.cgi?id=729586 device naming mixup
causing lots of domU's to not come back after a kernel update...

- KB


From toddandmargo at gmail.com  Mon Nov 28 18:37:50 2011
From: toddandmargo at gmail.com (Todd And Margo Chester)
Date: Mon, 28 Nov 2011 10:37:50 -0800
Subject: [CentOS-virt] kvm: w7 bsod's at shutdown
Message-ID: <4ED3D4FE.9090008@gmail.com>

Hi All,

I am using Scientific Linux 6.1 x64

Any idea how to get my W7 x32 guest to shutdown with out a BSOD?
I have to go into virt-manager and kill it all the time.  My XP guest
shuts down without issue.

Many thanks,
-T

$ rpm -qa \*kvm\*
qemu-kvm-0.12.1.2-2.160.el6_1.2.x86_64

$ rpm -qa \*virt\*
python-virtinst-0.500.5-3.el6.noarch
libvirt-0.8.7-18.el6_1.1.x86_64
libvirt-client-0.8.7-18.el6_1.1.x86_64
virt-manager-0.8.6-4.el6.noarch
libvirt-python-0.8.7-18.el6_1.1.x86_64



From byrnejb at harte-lyne.ca  Tue Nov 29 20:51:45 2011
From: byrnejb at harte-lyne.ca (James B. Byrne)
Date: Tue, 29 Nov 2011 15:51:45 -0500 (EST)
Subject: [CentOS-virt] Transfer of LVM based guests
Message-ID: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>

I am investigating the procedure to follow when moving a
KVM guest instance from one host to another where the
guest uses LVM as its storage.  As a preliminary cut I
have cobbled the following together from various sources
located through Google searches:

1.  Log in to vmhost_old

2.  Shutdown guest

3.  Create an LVM snapshot of the guest volume
3.a.   lvcreate -s -L 300m -n LVM_guest_snapshot guest_lv

4.  Convert snapshot to a file image
4.a    dd if=/dev/vhost/LVM_guest_snapshot
          of=/tmp/fs/LVM_guest_snapshot.img bs=4096

5.  Remove the original snapshot
5.a    lvremove /dev/vhost/LVM_guest_snapshot

6.  Move the snapshot image file to the new KVM host. Note
that for large vm guest images tape transport is probably
better than network transfers.

7.  Log in to vhost_new

8.  Create a new lv on the new vhost
8.a    lvcreate -n guest_name_lv -L 60G vhost_new_vg

9.  Copy transferred image to new LV
9.a    dd if=tmp/LVM_guest_snapshot.img
       of=/dev/vhost_new/guest_name_lv bs=4096

10.  Copy guest xml file from vhost_old via sftp
10.a.   get /etc/libvirt/qemu/guest_name.xml \
           /etc/libvirt/qemu/guest_name.xml

11. Start new guest?


Is there anything obviously wrong or omitted from this?


-- 
***          E-Mail is NOT a SECURE channel          ***
James B. Byrne                mailto:ByrneJB at Harte-Lyne.ca
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3



From Ed at Heron-ent.com  Tue Nov 29 22:11:01 2011
From: Ed at Heron-ent.com (Ed Heron)
Date: Tue, 29 Nov 2011 15:11:01 -0700
Subject: [CentOS-virt] Transfer of LVM based guests
In-Reply-To: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
References: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
Message-ID: <1322604661.4811.13.camel@elap.rgtravel.com>

On Tue, 2011-11-29 at 15:51 -0500, James B. Byrne wrote:
> I am investigating the procedure to follow when moving a
> KVM guest instance from one host to another where the
> guest uses LVM as its storage.  As a preliminary cut I
> have cobbled the following together from various sources
> located through Google searches:
> ...

  If you are moving the virtual disk, you can't run the virtual machine while you are moving it.  Therefore, taking a snapshot (and removing it later) is superfluous.

  I use md5sum to give myself some extra re-assurance that a copy that big is accurate.

  Are the virtualization servers at the same location?

  How often do you move virtual machines?

  If your virtualization servers are in the same location, you might want to look into setting up a LAN for transferring virtual machine images.  It would only take an extra network card in each virtualization server and a Gb Ethernet switch (or better).

  If you are interested in virtual disk replication, you might want to look at DRBD.  It adds an extra layer to your storage, but allows for hot replication of disk space which would allow you to start a virtual machine on any virtualization server.




From byrnejb at harte-lyne.ca  Wed Nov 30 16:23:11 2011
From: byrnejb at harte-lyne.ca (James B. Byrne)
Date: Wed, 30 Nov 2011 11:23:11 -0500 (EST)
Subject: [CentOS-virt] Transfer of LVM based guests
In-Reply-To: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
References: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
Message-ID: <40363.216.185.71.25.1322670191.squirrel@webmail.harte-lyne.ca>


On Tue, November 29, 2011 17:11:01, Ed Heron Ed at
Heron-ent.com wrote:

> If you are moving the virtual disk, you can't run
> the virtual machine while you are moving it.
> Therefore, taking a snapshot (and removing it later)
> is superfluous.

Point taken.

> I use md5sum to give myself some extra re-assurance
> that a copy that big is accurate.

Good idea.

> Are the virtualization servers at the same location?

At the moment. It is planned that there will be two vhosts
at each of two different locations, one backing up the
other.

>  How often do you move virtual machines?

I have not moved any as of yet.  I am investigating how to
do this as part of setting up our first virtual server
host.  I am discovering what is possible and the
techniques used.  Moving vm guests is not being considered
for load balancing but is under consideration for
providing warm spares for use in a DR situation.

> If your virtualization servers are in the same
> location, you might want to look into setting up a
> LAN for transferring virtual machine images.  It
> would only take an extra network card in each
> virtualization server and a Gb Ethernet switch
> (or better).

Our vhosts all (will) have two nics, one for public IPs
and one for private IPs.  The private IPs are used for
vhost management.  The experimental vhost is so equipped.

> If you are interested in virtual disk replication,
> you might want to look at DRBD.  It adds an extra layer
> to your storage, but allows for hot replication of
> disk space which would allow you to start a virtual
> machine on any virtualization server.

This is a useful suggestion. However, I find that the
availability of a DRDB package on CentOS-6 is presently an
issue.  And, our vm project has already expanded into
multiple areas with commensurate delays.  I think that I
will leave DRDB for a later time.

So, what I now have for a proposed procedure is:

1.  Log in to vmhost_old

2.  Shutdown guest

3.  Convert guest lvs to file images for each lv
3.a    dd if=/dev/vhost/lv_vhost_guest
          of=/tmp/fs/lv_vhost_guest.img bs=4096

4.  Create MD5 hash for each image file
4.a    md5sum /tmp/fs/lv_vhost_guest.img > \
              /tmp/fs/lv_vhost_guest.md5

5.  Move the guest image file(s)  and the checksum file to
the new vhost; preserving both the directory structure and
file names or subsequently modifying the file names in the
md5 checksum file. Note that for large vm guest images
tape transport is probably better than network transfers.

6.  Log in to vhost_new

7.  Verify md5 checksum(s) on transferred file(s).
7.a    md5sum -c /tmp/fs/lv_vhost_guest.md5

8.  Create a new lv(s) on the new vhost. Ensure sufficient
size.
8.a    lvcreate -n lv_guest_name -L 60G vhost_new_vg

9.  Copy transferred image to new LV
9.a    dd if=/tmp/fs/lv_vhost_guest.img
       of=/dev/vhost_new/lv_guest_name bs=4096

10.  Copy guest xml file from vhost_old via sftp
10.a.   get /etc/libvirt/qemu/guest_name.xml \
           /etc/libvirt/qemu/guest_name.xml

11. Start new guest?


Thanks,


-- 
***          E-Mail is NOT a SECURE channel          ***
James B. Byrne                mailto:ByrneJB at Harte-Lyne.ca
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3



From raju.rajsand at gmail.com  Mon Nov  7 18:17:22 2011
From: raju.rajsand at gmail.com (Rajagopal Swaminathan)
Date: Mon, 7 Nov 2011 23:47:22 +0530
Subject: [CentOS-virt] P2V utility
Message-ID: <CA+YdgaqusA9ZR2ekkyXtkggKBsH73=HYe1c=XVTSnq7OQ_kq+Q@mail.gmail.com>

Greetings,

An somebody pint to me to P2V Utility for the m$ world?

Like in VMware?

-- 
Regards,

Rajagopal


From lorenzo at tulug.it  Tue Nov  8 14:20:52 2011
From: lorenzo at tulug.it (Lorenzo)
Date: Tue, 8 Nov 2011 15:20:52 +0100
Subject: [CentOS-virt] P2V utility
In-Reply-To: <CA+YdgaqusA9ZR2ekkyXtkggKBsH73=HYe1c=XVTSnq7OQ_kq+Q@mail.gmail.com>
References: <CA+YdgaqusA9ZR2ekkyXtkggKBsH73=HYe1c=XVTSnq7OQ_kq+Q@mail.gmail.com>
Message-ID: <CADE4e0WfAq++1UDq-Vj3EhR=K1=xQTwmU0qsVhLrXVKgy+SDhg@mail.gmail.com>

2011/11/7 Rajagopal Swaminathan <raju.rajsand at gmail.com>:
> Greetings,
>
> An somebody pint to me to P2V Utility for the m$ world?
>
> Like in VMware?
>
> --
> Regards,
>
> Rajagopal

Try here:
http://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE
not centos specific, but I found a lot of useful info.

Regards,
Lorenzo


From mdra137 at gmail.com  Fri Nov 18 13:39:23 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Fri, 18 Nov 2011 14:39:23 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0BmRWi7_=FEJ0WSTzs5J1-2wuJ_AZdN=_S8WKWg94E_Vg@mail.gmail.com>

Hi,

I've been using CentOS & Xen on a server that has 2 VM's configured. The
default configuration includes one physical iface that is propagated (by a
default bridge) to the VM's.

Since I wanted to configure additional physical iface, define a new bridge
and propagate it to the viface-s of the VM's, i configured the bridge/phys.
iface and brought it up (here are configurations that I set up):

-> eth3
DEVICE=eth3
BOOTPROTO=static
HWADDR=D4:85:64:4B:76:AB
ONBOOT=yes
#HOTPLUG=no
#DHCP_HOSTNAME=kdr-3k-4r-3o-07
BRIDGE=br0
TYPE=Ethernet

-> br0
DEVICE=br0
TYPE=Bridge
BOOTPROTO=none
ONBOOT=yes

Then I configured new virt. ifaces on VM's (using virsh edit, config is
listed below):

<interface type='bridge'>
<mac address='00:16:36:17:62:5d'/>
<source bridge='xenbr0'/>
<script path='vif-bridge'/>
<target dev='vif5.0'/>
</interface>
<interface type='bridge'>
<mac address='00:16:3e:ca:63:39'/>
<source bridge='br0'/>
<script path='vif-bridge'/>
<target dev='vif5.1'/>
</interface>

You can see the default bridge (xenbr0 -> vif5.0) and my new bridge br0
connected to vif5.1.

So, here I got stuck up - when I try tu start a VM (xm create VIRT_SRV),
the VM starts booting but hangs up (I can ping it form another srv., but
when I try SSH it says "connection refused"). When I remove configuration
for vif5.1 the VM starts up normally. I actually managed to start VM with
vif5.1 up once, but next time I restarted it, the problem was there :/


Furthermore, I noticed this in the Xen log:

[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vif.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 0.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vif/1/1/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices usb.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vbd.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 768.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vbd/1/768/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:166) Waiting for 5632.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:544)
hotplugStatusCallback /local/domain/0/backend/vbd/1/5632/hotplug-status.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:558)
hotplugStatusCallback 1.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices irq.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vkbd.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vfb.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices pci.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices ioports.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices tap.
[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vtpm.

So the boot process goes on regulary until the last line ("Waiting for
devices vtpm"). It seems like TPM makes it impossible for VM's to start
regulary. When I open the VM's console (with virt-manager) I see the whole
boot process but it hangs when it tries to start iface eth2 (attached to
the second bridge) ...

Does anybody have a clue why is this happening?

Thanks in advance ..
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111118/e056a2eb/attachment-0006.html>

From peter.peltonen at gmail.com  Fri Nov 18 14:33:35 2011
From: peter.peltonen at gmail.com (Peter Peltonen)
Date: Fri, 18 Nov 2011 16:33:35 +0200
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
In-Reply-To: <CALZem0BmRWi7_=FEJ0WSTzs5J1-2wuJ_AZdN=_S8WKWg94E_Vg@mail.gmail.com>
References: <CALZem0BmRWi7_=FEJ0WSTzs5J1-2wuJ_AZdN=_S8WKWg94E_Vg@mail.gmail.com>
Message-ID: <CAGTVFvHkhkUytpf9ei2vGT0_NhLsOhXikDPV9ORAKYitttjCdA@mail.gmail.com>

Hi,

2011/11/18 Matija Draganovi? <mdra137 at gmail.com>:
> I've been using CentOS & Xen on a server that has 2 VM's configured. The
> default configuration includes one physical iface that is propagated (by a
> default bridge) to the VM's.

You do not mention which version of CentOS and Xen you are using?

>
> Since I wanted to configure additional physical iface, define a new bridge
> and propagate it to the viface-s of the VM's, i configured the bridge/phys.
> iface and brought it up (here are configurations that I set up):
>
> -> eth3
> DEVICE=eth3
> BOOTPROTO=static
> HWADDR=D4:85:64:4B:76:AB
> ONBOOT=yes
> #HOTPLUG=no
> #DHCP_HOSTNAME=kdr-3k-4r-3o-07
> BRIDGE=br0
> TYPE=Ethernet
>
> -> br0
> DEVICE=br0
> TYPE=Bridge
> BOOTPROTO=none
> ONBOOT=yes

If this is a CentOS5 machine with the CentOS provided Xen 3.0
packages, then here is info how i got my bridges to work with that
setup:

* For dom0 I configured eth0 and eth1 as usual in /etc/sysconfig/network-scripts

* I did not configure br0 or br1 in network-scripts, but instead I
created a file called /etc/xen/scripts/my-network-script having this
contents:

#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0
"$dir/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=xenbr1

* Then I modified in dom0 the file /etc/xen/xend-config.sxp in the
following way:

#(network-script network-bridge)
(network-script my-network-script)

* Now rebooting dom0 made the bridges available

* After that I could configure them in my domU config:

vif = [ "mac=00:16:3E:69:29:25,bridge=xenbr0,script=vif-bridge","mac=00:16:3E:E6:B0:6D,bridge=xenbr1,script=vif-bridge"
]

* After starting the domU I could configure the interfaces in
network-scripts using the hardware addresses specified in the domU
config


It seems that configuring bridging is done a bit differently in
different Xen versions, so this might not work if you are using some
other kind of config. With CentOS6 and 3rd party Xen 4.1 packages this
procedure did not work at all and instead I needed to do the
following:

* in dom0 create the br0 and br1 devices in network-scripts

* in dom0 /etc/xen/xend-config.sxp put instead:

#(network-script network-bridge)
(network-script /bin/true)

* and in dom0 use different configuration for the domU config files like this:

vif = [ "mac=00:16:3E:69:29:25,bridge=br0","mac=00:16:3E:E6:B0:6D,bridge=br1" ]


Hope this helps, unfortuantely I am not familiar with virsh at all.

Best,
Peter


From mdra137 at gmail.com  Fri Nov 18 17:17:17 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Fri, 18 Nov 2011 18:17:17 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0D1Z-dbkvM+-0+DgVGSGd_dHa757rSqMUZcAgCfffstwQ@mail.gmail.com>

Dear Peter,


Thanks for your reply. I was so occupied with troubleshooting that I forgot
to mention the OS & Xen version :)

My CentOS version is
CentOS release 5.7 (Final)
Linux 2.6.18-274.7.1.el5xen #1 SMP Thu Oct 20 17:06:34 EDT 2011 x86_64
x86_64 x86_64 GNU/Linux

and Xen v3.0.

I tried creating bridges the same way you did and succedded. I also tried
doing the same via ifcfg scripts, and it also worked.

I have no problem with creating bridges and connecting them with physical
ifaces, but I can't start my VM's (most of the time one VM start but the
other one hangs while trying to initalize eth2 that is connected to my
second (non default - xenbr1) bridge)).

The only diference between your config and mine is that I have vifname-s
listed (example below):

vif = [
"mac=00:16:36:72:35:e5,bridge=xenbr0,script=vif-bridge,vifname=vif4.0",
"mac=00:16:3e:57:de:0d,bridge=xenbr1,script=vif-bridge, vifname=vif4.1" ]

I'm not saying that this could be the problem, but since I'm slowly running
out of ideas - it's a longshot :)

So, to sum it all up - I can create bridges properly, but my VM's hang when
they try to bring up vifaces connected to the xenbr1. Also, I have no
problem with having only one bridge active - problem appears when I have
multiple bridges.

Br,
Matija
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111118/2a75ed85/attachment-0006.html>

From maillists at conactive.com  Fri Nov 18 18:33:20 2011
From: maillists at conactive.com (Kai Schaetzl)
Date: Fri, 18 Nov 2011 19:33:20 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
In-Reply-To: <CALZem0D1Z-dbkvM+-0+DgVGSGd_dHa757rSqMUZcAgCfffstwQ@mail.gmail.com>
References: <CALZem0D1Z-dbkvM+-0+DgVGSGd_dHa757rSqMUZcAgCfffstwQ@mail.gmail.com>
Message-ID: <VA.00003db7.1907ac90@news.conactive.com>

Matija Draganovi? wrote on Fri, 18 Nov 2011 18:17:17 +0100:

> The only diference between your config and mine is that I have vifname-s
> listed

Then remove it. I've never seen it like that. If I remember it correctly 
the vifnames are created dynamically. You can't rely on them I suppose.

And I don't remember using "script" either.

If you can't get it to work then use the second method Peter describes. 
That one should also work for Xen 3.0 and is guaranteed to create stable 
bridging.



Kai

-- 
Get your web at Conactive Internet Services: http://www.conactive.com





From jason at daylife.com  Fri Nov 18 22:56:02 2011
From: jason at daylife.com (Jason Nagashima)
Date: Fri, 18 Nov 2011 17:56:02 -0500 (EST)
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <1331504081.4540.1321656727740.JavaMail.root@mailbox01.hq.daylife.com>
Message-ID: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>

Running on Centos 5.6 with KVM... 

I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?

I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it.  There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.

Any advice/working examples would be greatly appreciated.

Regards,
Jason


From incoming-centos at rjl.com  Sat Nov 19 04:34:25 2011
From: incoming-centos at rjl.com (Nataraj)
Date: Fri, 18 Nov 2011 20:34:25 -0800
Subject: [CentOS-virt] high resolution video for kvm vm
Message-ID: <4EC731D1.40109@rjl.com>

I'm running a fuduntu vm (based on fedora 14)  on a CentOS 6 kvm
server.  I have tried changing the video in virt-manager from cirrus to
vga and restarting the VM, but the maximum resolution that the client
will let me set is still only 1024x768.  Should I be able to get  high
res video with the kvm VGA mode?  Note that the VM is running on a
CentOS server while virt-manager is running on my local desktop.

Would I be better off trying to get the vmware VGA driver working?  I'm
assuming I have to extract the driver from the vmware tools package and
manually install it into the X server, because VMware tools won't
install under kvm.

Also, I run with the keyboard option to swap caps lock and control on my
linux desktop, which does not seem to get passed through to the guest. 
I tried setting the same swap caps lock and control option in the guest,
but it does not work.  Any ideas?

Thanks,
Nataraj



From mdra137 at gmail.com  Sat Nov 19 06:32:21 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Sat, 19 Nov 2011 07:32:21 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0A+hx+b2OFOEYD-YdpXxV9Y=jFUP=UTjgFLBqBqca78YQ@mail.gmail.com>

I tried to remove vifname and vif-script but the problem remains. I think
that the bridges are ok, but for some reason VM's hang when they try to
connect their vifaces to them.

I'll try some different configurations of the physical ifaces (an vifaces
also), maybe I'll be able to find out something. Also, I'll focus on the
vTPM, since the following line shows up in the Xen log when the VM tries to
bring up the iface connected to the second bridge:

[2011-11-18 09:27:16 xend 8213] DEBUG (DevController:160) Waiting for
devices vtpm


Furthermore, it appears that sometimes the VM's manage to start regulary, I
just can't figure out when & why :/

Tnx for your comments ..

Br,
M.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111119/cc41e78f/attachment-0006.html>

From mdra137 at gmail.com  Tue Nov 22 09:37:31 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Tue, 22 Nov 2011 10:37:31 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0AS0ptzxMRXooEFHLCAR=OCnaFcXS5AcMmQduevWSFjrQ@mail.gmail.com>

Ok, after trying multiple different configurations I decided to play by the
book - I removed ifcfg script for creating the additional bridge and set up
an Xen script. So my new configuration is:

-> eth3 (my physical interface)
# NetXen Incorporated NX3031 Multifunction 1/10-Gigabit Server Adapter
DEVICE=eth3
BOOTPROTO=static
HWADDR= ...
ONBOOT=yes
IPADDR= ...
NETMASK= ...
NETWORK= ...

and the network-xen-multi-bridge script:

#!/bin/sh
# network-xen-multi-bridge
# Exit if anything goes wrong.
set -e
# First arg is the operation.
OP=$1
shift
script=/etc/xen/scripts/network-bridge.xen
case ${OP} in
start)
$script start vifnum=3 bridge=xenbr3 netdev=eth3
$script start vifnum=0 bridge=xenbr0 netdev=eth0
;;
stop)
$script stop vifnum=3 bridge=xenbr3 netdev=eth3
$script stop vifnum=0 bridge=xenbr0 netdev=eth0
;;
status)
$script status vifnum=3 bridge=xenbr3 netdev=eth3
$script status vifnum=0 bridge=xenbr0 netdev=eth0
;;
*)
echo 'Unknown command: ' ${OP}
echo 'Valid commands are: start, stop, status'
exit 1
esac

After I restart the physical server bridges are set up correctly:

# brctl show
bridge name bridge id STP enabled interfaces
virbr0 8000.000000000000 yes
xenbr0 8000.feffffffffff no vif0.0
peth0
xenbr3 8000.feffffffffff no vif0.3
peth3

Unfortunately, this did not solve the problem - I manage to start one VM
(connected to both of the bridges), but when I try to start the other one,
it just hangs when trying to bring up the second interface (connected to
xenbr3) :/

I'm currently completely out of ideas, but I'm not giving up ;)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111122/eb760bb6/attachment-0006.html>

From tait at taiter.com  Tue Nov 22 16:07:54 2011
From: tait at taiter.com (Tait Clarridge)
Date: Tue, 22 Nov 2011 11:07:54 -0500
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>
References: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>
Message-ID: <1321978074.22491.12.camel@tclarrltp.frontiernetworks.ca>

On Fri, 2011-11-18 at 17:56 -0500, Jason Nagashima wrote:
> Running on Centos 5.6 with KVM... 
> 
> I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?
> 
> I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it.  There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.
> 
> Any advice/working examples would be greatly appreciated.

Hi Jason,

I have had luck doing this with Xen, where I create bond0 on a trunk
interface and have xen bring it up as xenbr0 with pbond0 in the back
end.

You should be able to do roughly the same by creating a bridge interface
in /etc/sysconfig/network-scripts referencing bond0 as a member.

After that you should be able to run a script to create VLAN bridges
like the following:

#!/bin/bash
/sbin/modprobe 8021q

# Add your vlans here that you want with the numbers separated by a 
# space
VLANS="5 10 15 20"
# This should work with the bonding interface
TRUNKINT="bond0"
for VLAN in $VLANS
do
	vconfig add $TRUNKINT $VLAN
	brctl add br$VLAN
	brctl addif br$VLAN $TRUNKINT.$VLAN
	ifconfig $TRUNKINT.$VLAN up
	ifconfig br$VLAN up
done

I have done this with Xen on 5.5, 5.6 and 5.7... but it should work for
KVM. If you create the standard bridge interface br0 using just bond0
that will get you a trunk on whatever the native vlan is for that trunk.

Tait




From dmartls1 at gmail.com  Tue Nov 22 17:39:02 2011
From: dmartls1 at gmail.com (David Martin)
Date: Tue, 22 Nov 2011 11:39:02 -0600
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <1321978074.22491.12.camel@tclarrltp.frontiernetworks.ca>
References: <1054915728.4546.1321656962040.JavaMail.root@mailbox01.hq.daylife.com>
	<1321978074.22491.12.camel@tclarrltp.frontiernetworks.ca>
Message-ID: <CAAsqWCd+KWrX-SpRcYVNzCVC4HDV25C1QeOZzu-ChN0ZHyhdBw@mail.gmail.com>

We are doing this quite a bit in production and it works great.

bond as you normally would:
DEVICE=bond0
ONBOOT=yes
USERCTL=no
BONDING_OPTS="mode=4 miimon=100"

one of these for each vlan (in this case 50):
VLAN=yes
VLAN_NAME_TYPE=VLAN_PLUS_VID_NO_PAD
DEVICE=vlan50
PHYSDEV=bond0
TYPE=Ethernet
ONBOOT=yes
BRIDGE=br50

and finally the bridge device to expose to guests:
DEVICE=br50
TYPE=Bridge
ONBOOT=yes
DELAY=0
GATEWAYDEV=none




On Tue, Nov 22, 2011 at 10:07 AM, Tait Clarridge <tait at taiter.com> wrote:
> On Fri, 2011-11-18 at 17:56 -0500, Jason Nagashima wrote:
>> Running on Centos 5.6 with KVM...
>>
>> I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?
>>
>> I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it. ?There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.
>>
>> Any advice/working examples would be greatly appreciated.
>
> Hi Jason,
>
> I have had luck doing this with Xen, where I create bond0 on a trunk
> interface and have xen bring it up as xenbr0 with pbond0 in the back
> end.
>
> You should be able to do roughly the same by creating a bridge interface
> in /etc/sysconfig/network-scripts referencing bond0 as a member.
>
> After that you should be able to run a script to create VLAN bridges
> like the following:
>
> #!/bin/bash
> /sbin/modprobe 8021q
>
> # Add your vlans here that you want with the numbers separated by a
> # space
> VLANS="5 10 15 20"
> # This should work with the bonding interface
> TRUNKINT="bond0"
> for VLAN in $VLANS
> do
> ? ? ? ?vconfig add $TRUNKINT $VLAN
> ? ? ? ?brctl add br$VLAN
> ? ? ? ?brctl addif br$VLAN $TRUNKINT.$VLAN
> ? ? ? ?ifconfig $TRUNKINT.$VLAN up
> ? ? ? ?ifconfig br$VLAN up
> done
>
> I have done this with Xen on 5.5, 5.6 and 5.7... but it should work for
> KVM. If you create the standard bridge interface br0 using just bond0
> that will get you a trunk on whatever the native vlan is for that trunk.
>
> Tait
>
>
> _______________________________________________
> CentOS-virt mailing list
> CentOS-virt at centos.org
> http://lists.centos.org/mailman/listinfo/centos-virt
>


From jason at daylife.com  Wed Nov 23 21:49:56 2011
From: jason at daylife.com (Jason Nagashima)
Date: Wed, 23 Nov 2011 16:49:56 -0500 (EST)
Subject: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6
In-Reply-To: <CAAsqWCd+KWrX-SpRcYVNzCVC4HDV25C1QeOZzu-ChN0ZHyhdBw@mail.gmail.com>
Message-ID: <206550579.4866.1322084996341.JavaMail.root@mailbox01.hq.daylife.com>

Awesome!

Thank you everyone for responding and helping out. I'm happy to report that we got it working!

Cheers,
Jason

----- Original Message -----
From: "David Martin" <dmartls1 at gmail.com>
To: "Discussion about the virtualization on CentOS" <centos-virt at centos.org>
Sent: Tuesday, November 22, 2011 12:39:02 PM
Subject: Re: [CentOS-virt] Bonds, VLANs, and Bridges on Centos 5.6

We are doing this quite a bit in production and it works great.

bond as you normally would:
DEVICE=bond0
ONBOOT=yes
USERCTL=no
BONDING_OPTS="mode=4 miimon=100"

one of these for each vlan (in this case 50):
VLAN=yes
VLAN_NAME_TYPE=VLAN_PLUS_VID_NO_PAD
DEVICE=vlan50
PHYSDEV=bond0
TYPE=Ethernet
ONBOOT=yes
BRIDGE=br50

and finally the bridge device to expose to guests:
DEVICE=br50
TYPE=Bridge
ONBOOT=yes
DELAY=0
GATEWAYDEV=none




On Tue, Nov 22, 2011 at 10:07 AM, Tait Clarridge <tait at taiter.com> wrote:
> On Fri, 2011-11-18 at 17:56 -0500, Jason Nagashima wrote:
>> Running on Centos 5.6 with KVM...
>>
>> I was wondering if anyone had any luck configuring the NICs where eth0 and eth1 are bonded together with vlan support to a bridge?
>>
>> I noticed some threads show this as a possibility (http://lists.centos.org/pipermail/centos-virt/2009-November/001417.html), but haven't had any luck implementing it. ?There also seems to be a bug with 5.6 (http://bugs.centos.org/view.php?id=4801), but that post died the day it was created it.
>>
>> Any advice/working examples would be greatly appreciated.
>
> Hi Jason,
>
> I have had luck doing this with Xen, where I create bond0 on a trunk
> interface and have xen bring it up as xenbr0 with pbond0 in the back
> end.
>
> You should be able to do roughly the same by creating a bridge interface
> in /etc/sysconfig/network-scripts referencing bond0 as a member.
>
> After that you should be able to run a script to create VLAN bridges
> like the following:
>
> #!/bin/bash
> /sbin/modprobe 8021q
>
> # Add your vlans here that you want with the numbers separated by a
> # space
> VLANS="5 10 15 20"
> # This should work with the bonding interface
> TRUNKINT="bond0"
> for VLAN in $VLANS
> do
> ? ? ? ?vconfig add $TRUNKINT $VLAN
> ? ? ? ?brctl add br$VLAN
> ? ? ? ?brctl addif br$VLAN $TRUNKINT.$VLAN
> ? ? ? ?ifconfig $TRUNKINT.$VLAN up
> ? ? ? ?ifconfig br$VLAN up
> done
>
> I have done this with Xen on 5.5, 5.6 and 5.7... but it should work for
> KVM. If you create the standard bridge interface br0 using just bond0
> that will get you a trunk on whatever the native vlan is for that trunk.
>
> Tait
>
>
> _______________________________________________
> CentOS-virt mailing list
> CentOS-virt at centos.org
> http://lists.centos.org/mailman/listinfo/centos-virt
>
_______________________________________________
CentOS-virt mailing list
CentOS-virt at centos.org
http://lists.centos.org/mailman/listinfo/centos-virt


From mdra137 at gmail.com  Fri Nov 25 11:11:44 2011
From: mdra137 at gmail.com (=?ISO-8859-2?Q?Matija_Draganovi=E6?=)
Date: Fri, 25 Nov 2011 12:11:44 +0100
Subject: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Message-ID: <CALZem0BCpJuchqLS6vws9Sm+_YPbR3AkLVyiKBQpJAPDGvzSGQ@mail.gmail.com>

Finally, I managed to solve the problem. The problem was rather strange -
after configuring bridges I added new ifaces to the VM. For some reason,
during boot process of the VM's, wrong interface was started (VM tried to
bring up eth2 instead eth1?).

After adding the new ifaces through virt-manager, the VM started regulary
and created a new network script for eth2
(/etc/sysconfig/network-scripts/ifcfg-eth2). I think that the problem was
this - when the VM is restarted it tried to bring up eth2 while vif-script
tried to propagate second bridge via eth1 iface. I resolved this simply by
replacing ifcfg-eth2 script with ifcfg-eth1. Now, VM starts/restarts
regulary ;)

So, the process for creating and configuring new bridges that I follow is
(tried on multiple servers):

- create new script that sets up multiple bridges in /etc/xen/scripts/

example: network-xen-multi-bridge

#!/bin/sh
# network-xen-multi-bridge
# Exit if anything goes wrong.
set -e
# First arg is the operation.
OP=$1
shift
script=/etc/xen/scripts/network-bridge.xen
case ${OP} in
start)
        $script start vifnum=3 bridge=xenbr3 netdev=eth3
        $script start vifnum=0 bridge=xenbr0 netdev=eth0
        ;;
stop)
        $script stop vifnum=3 bridge=xenbr3 netdev=eth3
        $script stop vifnum=0 bridge=xenbr0 netdev=eth0
        ;;
status)
        $script status vifnum=3 bridge=xenbr3 netdev=eth3
        $script status vifnum=0 bridge=xenbr0 netdev=eth0
        ;;
*)
        echo 'Unknown command: ' ${OP}
        echo 'Valid commands are: start, stop, status'
        exit 1
esac



- make it executable (chmod 755 network-xen-multi-bridge)

- configure /etc/xen/xend-config.sxp (comment out the current script and
add the new one);

# It is possible to use the network-bridge script in more complicated
# scenarios, such as having two outgoing interfaces, with two bridges, and
# two fake interfaces per guest domain.  To do things like this, write
# yourself a wrapper script, and call network-bridge from it, as appropriate.
#
#(network-script network-bridge)
(network-script  network-xen-multi-bridge)



- restart physical server so the bridges are properly created

- add virt. ifaces to the VM's (via virt-manager or via config. files in
/etc/xen/ ..)

- boot VM

- configure newly added iface in /etc/sysconfig/network-scripts/

- restart VM

Additionaly I check everything by restarting phys. server to make sure that
everything is ok ;)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20111125/1304c71b/attachment-0006.html>

From mail-lists at karan.org  Sat Nov 26 00:29:20 2011
From: mail-lists at karan.org (Karanbir Singh)
Date: Sat, 26 Nov 2011 00:29:20 +0000
Subject: [CentOS-virt] Device renaming heads up
Message-ID: <4ED032E0.1040109@karan.org>

hi Guys,

Just in case anyone hasent noticed this :
https://bugzilla.redhat.com/show_bug.cgi?id=729586 device naming mixup
causing lots of domU's to not come back after a kernel update...

- KB


From toddandmargo at gmail.com  Mon Nov 28 18:37:50 2011
From: toddandmargo at gmail.com (Todd And Margo Chester)
Date: Mon, 28 Nov 2011 10:37:50 -0800
Subject: [CentOS-virt] kvm: w7 bsod's at shutdown
Message-ID: <4ED3D4FE.9090008@gmail.com>

Hi All,

I am using Scientific Linux 6.1 x64

Any idea how to get my W7 x32 guest to shutdown with out a BSOD?
I have to go into virt-manager and kill it all the time.  My XP guest
shuts down without issue.

Many thanks,
-T

$ rpm -qa \*kvm\*
qemu-kvm-0.12.1.2-2.160.el6_1.2.x86_64

$ rpm -qa \*virt\*
python-virtinst-0.500.5-3.el6.noarch
libvirt-0.8.7-18.el6_1.1.x86_64
libvirt-client-0.8.7-18.el6_1.1.x86_64
virt-manager-0.8.6-4.el6.noarch
libvirt-python-0.8.7-18.el6_1.1.x86_64



From byrnejb at harte-lyne.ca  Tue Nov 29 20:51:45 2011
From: byrnejb at harte-lyne.ca (James B. Byrne)
Date: Tue, 29 Nov 2011 15:51:45 -0500 (EST)
Subject: [CentOS-virt] Transfer of LVM based guests
Message-ID: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>

I am investigating the procedure to follow when moving a
KVM guest instance from one host to another where the
guest uses LVM as its storage.  As a preliminary cut I
have cobbled the following together from various sources
located through Google searches:

1.  Log in to vmhost_old

2.  Shutdown guest

3.  Create an LVM snapshot of the guest volume
3.a.   lvcreate -s -L 300m -n LVM_guest_snapshot guest_lv

4.  Convert snapshot to a file image
4.a    dd if=/dev/vhost/LVM_guest_snapshot
          of=/tmp/fs/LVM_guest_snapshot.img bs=4096

5.  Remove the original snapshot
5.a    lvremove /dev/vhost/LVM_guest_snapshot

6.  Move the snapshot image file to the new KVM host. Note
that for large vm guest images tape transport is probably
better than network transfers.

7.  Log in to vhost_new

8.  Create a new lv on the new vhost
8.a    lvcreate -n guest_name_lv -L 60G vhost_new_vg

9.  Copy transferred image to new LV
9.a    dd if=tmp/LVM_guest_snapshot.img
       of=/dev/vhost_new/guest_name_lv bs=4096

10.  Copy guest xml file from vhost_old via sftp
10.a.   get /etc/libvirt/qemu/guest_name.xml \
           /etc/libvirt/qemu/guest_name.xml

11. Start new guest?


Is there anything obviously wrong or omitted from this?


-- 
***          E-Mail is NOT a SECURE channel          ***
James B. Byrne                mailto:ByrneJB at Harte-Lyne.ca
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3



From Ed at Heron-ent.com  Tue Nov 29 22:11:01 2011
From: Ed at Heron-ent.com (Ed Heron)
Date: Tue, 29 Nov 2011 15:11:01 -0700
Subject: [CentOS-virt] Transfer of LVM based guests
In-Reply-To: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
References: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
Message-ID: <1322604661.4811.13.camel@elap.rgtravel.com>

On Tue, 2011-11-29 at 15:51 -0500, James B. Byrne wrote:
> I am investigating the procedure to follow when moving a
> KVM guest instance from one host to another where the
> guest uses LVM as its storage.  As a preliminary cut I
> have cobbled the following together from various sources
> located through Google searches:
> ...

  If you are moving the virtual disk, you can't run the virtual machine while you are moving it.  Therefore, taking a snapshot (and removing it later) is superfluous.

  I use md5sum to give myself some extra re-assurance that a copy that big is accurate.

  Are the virtualization servers at the same location?

  How often do you move virtual machines?

  If your virtualization servers are in the same location, you might want to look into setting up a LAN for transferring virtual machine images.  It would only take an extra network card in each virtualization server and a Gb Ethernet switch (or better).

  If you are interested in virtual disk replication, you might want to look at DRBD.  It adds an extra layer to your storage, but allows for hot replication of disk space which would allow you to start a virtual machine on any virtualization server.




From byrnejb at harte-lyne.ca  Wed Nov 30 16:23:11 2011
From: byrnejb at harte-lyne.ca (James B. Byrne)
Date: Wed, 30 Nov 2011 11:23:11 -0500 (EST)
Subject: [CentOS-virt] Transfer of LVM based guests
In-Reply-To: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
References: <38874.216.185.71.25.1322599905.squirrel@webmail.harte-lyne.ca>
Message-ID: <40363.216.185.71.25.1322670191.squirrel@webmail.harte-lyne.ca>


On Tue, November 29, 2011 17:11:01, Ed Heron Ed at
Heron-ent.com wrote:

> If you are moving the virtual disk, you can't run
> the virtual machine while you are moving it.
> Therefore, taking a snapshot (and removing it later)
> is superfluous.

Point taken.

> I use md5sum to give myself some extra re-assurance
> that a copy that big is accurate.

Good idea.

> Are the virtualization servers at the same location?

At the moment. It is planned that there will be two vhosts
at each of two different locations, one backing up the
other.

>  How often do you move virtual machines?

I have not moved any as of yet.  I am investigating how to
do this as part of setting up our first virtual server
host.  I am discovering what is possible and the
techniques used.  Moving vm guests is not being considered
for load balancing but is under consideration for
providing warm spares for use in a DR situation.

> If your virtualization servers are in the same
> location, you might want to look into setting up a
> LAN for transferring virtual machine images.  It
> would only take an extra network card in each
> virtualization server and a Gb Ethernet switch
> (or better).

Our vhosts all (will) have two nics, one for public IPs
and one for private IPs.  The private IPs are used for
vhost management.  The experimental vhost is so equipped.

> If you are interested in virtual disk replication,
> you might want to look at DRBD.  It adds an extra layer
> to your storage, but allows for hot replication of
> disk space which would allow you to start a virtual
> machine on any virtualization server.

This is a useful suggestion. However, I find that the
availability of a DRDB package on CentOS-6 is presently an
issue.  And, our vm project has already expanded into
multiple areas with commensurate delays.  I think that I
will leave DRDB for a later time.

So, what I now have for a proposed procedure is:

1.  Log in to vmhost_old

2.  Shutdown guest

3.  Convert guest lvs to file images for each lv
3.a    dd if=/dev/vhost/lv_vhost_guest
          of=/tmp/fs/lv_vhost_guest.img bs=4096

4.  Create MD5 hash for each image file
4.a    md5sum /tmp/fs/lv_vhost_guest.img > \
              /tmp/fs/lv_vhost_guest.md5

5.  Move the guest image file(s)  and the checksum file to
the new vhost; preserving both the directory structure and
file names or subsequently modifying the file names in the
md5 checksum file. Note that for large vm guest images
tape transport is probably better than network transfers.

6.  Log in to vhost_new

7.  Verify md5 checksum(s) on transferred file(s).
7.a    md5sum -c /tmp/fs/lv_vhost_guest.md5

8.  Create a new lv(s) on the new vhost. Ensure sufficient
size.
8.a    lvcreate -n lv_guest_name -L 60G vhost_new_vg

9.  Copy transferred image to new LV
9.a    dd if=/tmp/fs/lv_vhost_guest.img
       of=/dev/vhost_new/lv_guest_name bs=4096

10.  Copy guest xml file from vhost_old via sftp
10.a.   get /etc/libvirt/qemu/guest_name.xml \
           /etc/libvirt/qemu/guest_name.xml

11. Start new guest?


Thanks,


-- 
***          E-Mail is NOT a SECURE channel          ***
James B. Byrne                mailto:ByrneJB at Harte-Lyne.ca
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3