virt

virt@lists.centos.org

1612 discussions

XEN multiple bridge problem - VM won' start!
by Matija Draganović 25 Nov '11

25 Nov '11

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 ;)

1 0

Bonds, VLANs, and Bridges on Centos 5.6
by Jason Nagashima 23 Nov '11

23 Nov '11

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

3 3

XEN multiple bridge problem - VM won' start!
by Matija Draganović 22 Nov '11

22 Nov '11

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 ;)

1 0

XEN multiple bridge problem - VM won' start!
by Matija Draganović 19 Nov '11

19 Nov '11

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.

1 0

high resolution video for kvm vm
by Nataraj 19 Nov '11

19 Nov '11

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

1 0

XEN multiple bridge problem - VM won' start!
by Matija Draganović 18 Nov '11

18 Nov '11

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

2 1

XEN multiple bridge problem - VM won' start!
by Matija Draganović 18 Nov '11

18 Nov '11

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 ..

2 1

P2V utility
by Rajagopal Swaminathan 08 Nov '11

08 Nov '11

Greetings, An somebody pint to me to P2V Utility for the m$ world? Like in VMware? -- Regards, Rajagopal

2 1

how to add file-based disk space to a guest
by thomas veymont 31 Oct '11

31 Oct '11

hi there, I'm following these documentations to add a file-based disk volume to a KVM guest under Centos 6.0 : http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualiz… as instructed, I created a "pool" then a "volume", file-based, e.g : mkdir /mnt/raid/kvm_pool1 virsh # pool-define-as pool1 dir - - - - "/mnt/raid/kvm_pool1" virsh # pool-autostart pool1 virsh # vol-create-as pool1 volume1 20G --allocation 15G --format qcow2 now I want to associate "volume1" to my guest OS. Following this doc: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualiz… - why does this ask me to create a file with "dd" ? it's already been created before with the virsh pool commands, isn't it? Seems to me I'm bypassing the libvirt/virsh layer if I do that. - after that, the doc tells me to do some stuff with guest XML files. Is'nt there some specific commands provided by virsh to associate a managed Pool to a managed Guest ? - in this case, should I use the virsh "attach-disk" command ? thanks. -- Tom

2 4

using local media file to install guest
by Bob Hoffman 31 Oct '11

31 Oct '11

Hi, Been fighting with this for a long time and have narrowed my issues down to one item... How to use a iso image file to install a guest os with centos6? I installed centos6 with the virt host package. According to few obscure sites virt-install cannot use local media iso to install guests. With virt-manager I was able to use the same iso to make a guest, but I do not want the gui on the server. I tried mounting, umounting it..I tried using dd to bring the bootable iso from the cdrom. the issue I think, but not sure, is the use of the console directive with virt-install. It appears --extra-args="console=tty0 console=ttyS0,115200" works fine when using --location, but not --cdrom Unfortunately '--location" will ignore the path provided for the local iso and want to go to a url, an nfs, a virtual hard drive or cdrom....thus not able to install from local media. However, the text installer does come up. when using "--cdrom" and use location to the different ISO's I added the console will not come up as the --extra-args="console=tty0 console=ttyS0,115200" is ignored I assume. I cannot believe that the only way to install a guest on my machine is to use the desktop gui or a remote iso only. There has to be a way to install via the local iso... I have tried about 40 times with different ideas, even playing with the files on the mounted bootable iso. However, the console only works with --location thus unusable.....sigh. any help appreciated. here is just a basic example of my attempts virt-install --name test --ram=1024 --vcpus=1 --prompt --nographics --location=/backups/backup1/centos6.iso --extra-args="console=tty0 console=ttyS0,115200" I do not want VNC since again, that is not part of the normal install and is again asking me to use a remote computer to install on my local one, which is just not right. There must be a way to install on my local computer, from my local computer, from local file, a local guest.... isn't there?

6 17

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt