virt March 2008

virt@lists.centos.org

24 participants
24 discussions

Open VPN connection problem on Virtual Box
by Todd and Margo Chester 02 May '08

02 May '08

Hi All, I am working on a mystery. I am using openvpn-2.1_beta7-gui-1.0.3-install on all the computers in question. All computers are running XP-Pro-SP2. (Mine is running in a virtual window -- details below.) This configuration works perfectly from my office. I use it to call five facilities: remote aa.bb.cc.dd port 5030 proto udp dev tap ifconfig 192.168.240.30 255.255.255.0 secret iamnottellingyou.txt ping-restart 60 ping-timer-rem persist-tun persist-key resolv-retry 86400 ping 10 comp-lzo verb 6 mute 10 But, this EXACT config works on TWO other computers, but not mine: remote ww.xx.yy.zz 5020 client dev tap proto udp resolv-retry infinite nobind persist-key persist-tun ca foo-ca.crt cert foo-client1.crt key foo-client1.key ns-cert-type server ping 10 comp-lzo verb 3 The only difference between the two computers that MY config works on and mine, is that my computer is running in a virtual window. Host: Cent OS 5.1 Guest XP-Pro-SP2 VM: VirtualBox-1.5.6_28266_rhel5-1.i586.rpm The host and the guest are connected by a bridge (br0): DEVICE=br0 TYPE=Bridge BOOTPROTO=static BROADCAST=192.168.255.255 IPADDR=192.168.255.10 NETMASK=255.255.255.0 NETWORK=192.168.255.0 GATEWAY=192.168.255.10 ONBOOT=yes USERCTL=yes IPV6INIT=no PEERDNS=no PROMISC=yes When trying to connect, the same error message pops up on my computer (virtual XP) and on the distant end's (XP) server: TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) The SAME error message! Why does the first config work, but not the second? It is obviously not the config: it is identical on the other two computers that it works on. I think it may be the way open vpn is reacting to my bridge, but then, again, the first config works. Editorial comment: AAAAAAAAAHHHHHHHHHHHHHHHHHHH!!!! Anyone know what I am doing wrong? Many thanks, -T

2 2

xenbr0 isn't created anymore
by Kai Schaetzl 02 Apr '08

02 Apr '08

Somehow I managed to disable the creation of xenbr0 on boot-up of the host system. CentOS 5 with standard CentOS Xen. I changed all Xen VMs to use xenbr0 instead of virbr0 and disabled virtlibd. Works fine. But when I later restarted the machine I found that all networking for guests had gone. On inspection there's no xenbr0 created anymore. I can get it up by stopping network (or eth0) and then running /etc/xen/scripts/network-bridge start xend-config.sxp still has (network-script network-bridge), logging shows no problems. It seems that the network-bridge script simply doesn't run, but why? I can't see any init script or so that might run it, so I assume it's xend doing that, but there's no error in any log. Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

3 30

Re: CentOS-virt Digest, Vol 7, Issue 22
by Hristo Benev 30 Mar '08

30 Mar '08

Already reported.... http://bugs.centos.org/view.php?id=2516 >Subject: RE: [CentOS-virt] xenbr0 isn't created anymore >To: <centos-virt(a)centos.org> >Message-ID: > <E2BB8074E5500C42984D980D4BD78EF9022A704E(a)MFG-NYC-EXCH2.mfg.prv> >Content-Type: text/plain; charset="us-ascii" > >Kai Schaetzl wrote: >> >> Somehow I managed to disable the creation of xenbr0 on boot-up of the host >> system. CentOS 5 with standard CentOS Xen. >> I changed all Xen VMs to use xenbr0 instead of virbr0 and disabled >> virtlibd. Works fine. But when I later restarted the machine I found that >> all networking for guests had gone. On inspection there's no xenbr0 >> created anymore. I can get it up by stopping network (or eth0) and then >> running /etc/xen/scripts/network-bridge start >> xend-config.sxp still has (network-script network-bridge), logging shows >> no problems. It seems that the network-bridge script simply doesn't run, >> but why? I can't see any init script or so that might run it, so I assume >> it's xend doing that, but there's no error in any log. > >Kai, > >Snooping around I found this in /etc/xen/qemu-ifup: > ># ># Old style bridge setup with netloop, used to have a bridge name ># of xenbrX, enslaving pethX and vif0.X, and then configuring ># eth0. ># ># New style bridge setup does not use netloop, so the bridge name ># is ethX and the physical device is enslaved pethX ># ># So if... ># ># - User asks for xenbrX ># - AND xenbrX doesn't exist ># - AND there is a ethX device which is a bridge ># ># ..then we translate xenbrX to ethX ># ># This lets old config files work without modification > >So it turns out Xen networking changed in current releases and they never >updated their Wiki. > >Now I am not sure how the vif0.X and vethX interfaces fit into the >picture here... Maybe these are no longer used? > >vifX.Y interfaces are still used though for linking domU interfaces >with the physical interface. > > >-Ross > >______________________________________________________________________ >This e-mail, and any attachments thereto, is intended only for use by >the addressee(s) named herein and may contain legally privileged >and/or confidential information. If you are not the intended recipient >of this e-mail, you are hereby notified that any dissemination, >distribution or copying of this e-mail, and any attachments thereto, >is strictly prohibited. If you have received this e-mail in error, >please immediately notify the sender and permanently delete the >original and any copy or printout thereof. > > >

3 2

Migration Problem
by Brett Worth 29 Mar '08

29 Mar '08

Hi all! I've been experimenting with Xen on CentOS 5 and RHAS 5 for a while now with mixed success I thought I'd describe my latest challenge. I'll describe this from memory since all the equipment is at work and not contactable from here. I think I've described this config to the list before but here it is again: I have 2 x HP DL585 servers each with 4 Dual core Opterons (non-vmx) and 16GB RAM configured as Xen servers. These run CentOS 5.1 with the latest updates applied. These system both attach to an iSCSI target which is an HP DL385 running ietd and serving SAN based storage. Everything runs fine if I do no migration. I was having a "soft lockup" problem which has been solved by installing the latest test kernel from redhat. They've adjusted a timer as described in this report (comment 5): https://bugzilla.redhat.com/show_bug.cgi?id=250994 Anyway things are pretty stable now but... If I do a series of migrations, live or not, from one server to the other eventually I will get the process to fail. This could take up to an hour with the migrations happening every 5 minutes. It can also happen first try. The message in the xend.log file says that it is unable to find the device number for the virtualised storage i.e. sda. In my configuration I have dom0 connecting to the LUNs used by the VMs to the domU's are not doing iSCSI. I'm passing the "/dev/disks/by-path/iscsixxx:sda1" info in via the xen config file. If I mount and unmount the same LUN's filesystem to the dom0 over and over again it works every time so there's no fundamental problem with the iSCSI connection itself. Each server is using 3 gige interfaces: One for normal LAN access, a dedicated network for the iSCSI and a crossover cable between the third gige interfaces on the servers for the migration channel. I have a xentop running on both dom0's and can tell that its failed when the vm appears in the target but the memory used by the vm doesn't start incrementing. The end result is that the VM is hung and has to be destroyed and re-created. The error happens immediately after the failed migration is initiated. I've tried doing a read of the first few blocks of the LUN on the target immediately before initiating the migration which is successful but makes no difference. I realize this is pretty sketchy information but I was wondering if others were seeing similar problems. The ability to do reliable migration is basically the prime motivation for us wanting to do virtualization at all. Otherwise we'd just run the required services on the main machine. Anyway, any help would be appreciated. Brett

1 0

i386 VM on x86_64 host in Xen
by Frans Lawaetz 24 Mar '08

24 Mar '08

>/ On Mon, 2007-12-10 at 22:34 +0000, Karanbir Singh wrote: />>/ Just wondering if people had started using i386 Xen DomU's on a x86_64 />>/ dom0 machine with 5.1 as yet ? And just wondering what their experiences />>/ have been. /I thought I would chime in here with my experience. I am running a Cent5.1 x86_64 Dom0 with a Cent 5.1 x386 domU (both fully updated). Everything works well including installation and subsequent "xm create" boots. A gotcha that I have not been able to work around has to do with the automatic save/restore with the xendomains script. When I mimic Dom0 shutdown behavior (i.e., xendomains stop) and run "xm save sdatest /var/lib/xen/save/sdatest" the following gets generated to xend.log [2008-03-24 18:33:29 xend.XendDomainInfo 19801] INFO (XendDomainInfo:1719) Dev 51728 still active, looping... [2008-03-24 18:33:29 xend.XendDomainInfo 19801] DEBUG (XendDomainInfo:1611) XendDomainInfo.resumeDomain: devices released [2008-03-24 18:33:29 xend.XendDomainInfo 19801] DEBUG (XendDomainInfo:988) XendDomainInfo.handleShutdownWatch [2008-03-24 18:33:29 xend.XendDomainInfo 19801] DEBUG (XendDomainInfo:791) Storing domain details: {'console/ring-ref': '6706833', 'console/port': '2', 'name': 'migrating-sdatest', 'console/limit': '1048576', 'vm': '/vm/a9b4b850-95ee-1364-6b2b-5e79375ce47e', 'domid': '1', 'cpu/0/availability': 'online', 'memory/target': '131072', 'store/ring-ref': '6706834', 'store/port': '1'} [2008-03-24 18:33:29 xend 19801] DEBUG (blkif:24) exception looking up device number for xvda: [Errno 2] No such file or directory: '/dev/xvda' [2008-03-24 18:33:29 xend 19801] DEBUG (DevController:110) DevController: writing {'virtual-device': '51712', 'device-type': 'disk', 'protocol': 'x86_32-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/1/51712'} to /local/domain/1/device/vbd/51712. [2008-03-24 18:33:29 xend 19801] DEBUG (DevController:112) DevController: writing {'domain': 'migrating-sdatest', 'frontend': '/local/domain/1/device/vbd/51712', 'dev': 'xvda', 'state': '1', 'params': '/dev/VolGroup00/sdatest.boot', 'mode': 'w', 'online': '1', 'frontend-id': '1', 'type': 'phy'} to /local/domain/0/backend/vbd/1/51712. [2008-03-24 18:33:29 xend 19801] DEBUG (blkif:24) exception looking up device number for xvdb: [Errno 2] No such file or directory: '/dev/xvdb' [2008-03-24 18:33:29 xend 19801] DEBUG (DevController:110) DevController: writing {'virtual-device': '51728', 'device-type': 'disk', 'protocol': 'x86_32-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/1/51728'} to /local/domain/1/device/vbd/51728. [2008-03-24 18:33:29 xend 19801] DEBUG (DevController:112) DevController: writing {'domain': 'migrating-sdatest', 'frontend': '/local/domain/1/device/vbd/51728', 'dev': 'xvdb', 'state': '1', 'params': '/dev/VolGroup00/sdatest', 'mode': 'w', 'online': '1', 'frontend-id': '1', 'type': 'phy'} to /local/domain/0/backend/vbd/1/51728. [2008-03-24 18:33:29 xend 19801] DEBUG (DevController:110) DevController: writing {'mac': '00:16:3e:00:00:11', 'handle': '0', 'protocol': 'x86_32-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/1/0'} to /local/domain/1/device/vif/0. [2008-03-24 18:33:29 xend 19801] DEBUG (DevController:112) DevController: writing {'bridge': 'xenbr0', 'domain': 'migrating-sdatest', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/1/device/vif/0', 'mac': '00:16:3e:00:00:11', 'online': '1', 'frontend-id': '1'} to /local/domain/0/backend/vif/1/0. [2008-03-24 18:33:29 xend.XendDomainInfo 19801] DEBUG (XendDomainInfo:1623) XendDomainInfo.resumeDomain: devices created [2008-03-24 18:33:29 xend.XendDomainInfo 19801] ERROR (XendDomainInfo:1628) XendDomainInfo.resume: xc.domain_resume failed on domain 1. Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1625, in resumeDomain xc.domain_resume(self.domid, fast) Error: (1, 'Internal error', "Couldn't map p2m_frame_list_list") [2008-03-24 18:33:29 xend 19801] DEBUG (XendCheckpoint:136) XendCheckpoint.save: resumeDomain ERROR Internal error: Couldn't map p2m_frame_list_list There are two errors of note -- [2008-03-24 18:33:29 xend 19801] DEBUG (blkif:24) exception looking up device number for xvda: [Errno 2] No such file or directory: '/dev/xvda' and ERROR Internal error: Couldn't map p2m_frame_list_list Someone with greater knowledge of Xen's internal workings might comment as to whether they're related errors. It looks like this is a known issue with Xen based on the following bug report (which, alas, is not showing any activity). http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1064 I suppose a temporary workaround (for a development environment) is to alter the xendomains script so that a save is not conducted but a shutdown followed by a destroy. Cheers, Frans

1 0

Re: [CentOS-virt] DHCP for Xen VMs
by Ross S. W. Walker 24 Mar '08

24 Mar '08

You might want to check iptables in the dom0. I believe iptables gets set on eth0 before it 'pivots' to peth0 and I doubt it flushes it and retargets it to the new bridged eth0 afterwards, so the dhcp traffic may appear as unsolicited and dropped on dom0 as it enters the bridge. If that turns out to be the case you will need to have iptables stopped right before the creation of peth0 and restarted afterwards (and maybe file a bug report too). -Ross ----- Original Message ----- From: centos-virt-bounces(a)centos.org <centos-virt-bounces(a)centos.org> To: centos-virt(a)centos.org <centos-virt(a)centos.org> Sent: Mon Mar 24 09:41:42 2008 Subject: Re: [CentOS-virt] DHCP for Xen VMs Ross S. W. Walker wrote on Sun, 23 Mar 2008 19:29:47 -0400: > Assuming you have a DHCP server on the local net, maybe ip tables in the dom0 is blocking the dhcp traffic? > > Did you configure xend to do bridged or nat'd? Default is bridged. Well, networking *does* work if I set an IP address manually and as I can reach it then from other machines it must be bridged. The problem is that I don't get an IP address when using dhcp :-( I wasn't aware that iptables is on and preconfigured in a domU that got setup with CentOS 5.1 virt-manager. Unfortunately, shutting it off doesn't solve the problem. Logging shows that the server gets a request from that MAC address and offers an IP address, but the client doesn't receive it. There's no firewall between the two, but the offer doesn't get back to the client somehow. Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com _______________________________________________ CentOS-virt mailing list CentOS-virt(a)centos.org http://lists.centos.org/mailman/listinfo/centos-virt ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.

2 1

Re: [CentOS-virt] DHCP for Xen VMs
by Ross S. W. Walker 24 Mar '08

24 Mar '08

Assuming you have a DHCP server on the local net, maybe ip tables in the dom0 is blocking the dhcp traffic? Did you configure xend to do bridged or nat'd? Default is bridged. -Ross ----- Original Message ----- From: centos-virt-bounces(a)centos.org <centos-virt-bounces(a)centos.org> To: centos-virt(a)centos.org <centos-virt(a)centos.org> Sent: Sun Mar 23 18:31:15 2008 Subject: Re: [CentOS-virt] DHCP for Xen VMs Ross S. W. Walker wrote on Thu, 20 Mar 2008 11:59:17 -0400: > Configure the Xen VM to use the xen managed network xenbr0 instead of the > libvirt managed network virbr0. Unfortunately, doesn't work for me. If I change to xenbr0 the VM doesn't get an IP address. And as I'm having problems with the keymap I can't even look at the logs at the moment. If I set an IP address in the same subnet manually it works, but dhclient doesn't set one. Any ideas? Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com _______________________________________________ CentOS-virt mailing list CentOS-virt(a)centos.org http://lists.centos.org/mailman/listinfo/centos-virt ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.

2 1

console keymapping problems
by Kai Schaetzl 24 Mar '08

24 Mar '08

Supposedly CentOS 5.1 should fix the problems with foreign keyboards, but I cannot see any change. The description in http://misterd77.blogspot.com/2007/11/xen-graphical-console-and-foreign.html does not work for me. Nothing changes. Has had anyone better luck? If so, how? Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

2 2

xenbr0 vs. virtbr0
by Kai Schaetzl 23 Mar '08

23 Mar '08

Just created the first completely new Xen VM with the Virtual Machine Manager after 5.0 became 5.1 and I notice these two differences: - there's now virbr0 instead of xenbr0. Which means I have now xenbr0 and vitbr0 interfaces running. As virbr0 just the new name for xenbr0? If so, can I just change that name in the older configuration files, so that all use the same interface name? - there is a (I think) new option for networking. There's virtual network and there's shared device. What's the latter? I don't remember this being available earlier. It doesn't list any devices for me. Does this refer to virtual devices of type eth0:5 etc. on the host? help is no help for this, it's empty for this section. Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

2 2

DHCP for Xen VMs
by Kai Schaetzl 23 Mar '08

23 Mar '08

I created my first Xen VM that didn't use a static IP address. It grabs an IP from the 198.168.122.0 subnet (from I don't know where). I would rather want it to use my DHCP server. How can I achieve this? Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt March 2008