similar to: DomU strange network behavior

Hello, I just setup a Xen server and wanted to use bond0 for my network connection. I ended up downloading and addeding the attatched file and making the following change in /etc/xen/xend-config.sxp. I added this line: (network-script 'network-bond netdev=bond0') Would this line be a good one to add to the commented lines and include the network-bond file in the scripts? Just thought

A huge thank you to mario from the ''openvswitch on Xen 4.1'' post. I was having some trouble with using openvswitch with Xen 4.1 (I''m currently migrating from 4.0.1) until I saw his post and noticed that the xl.conf needed the full path to the networking script. Made this change and all is good now. Thank you. I would like to contribute what I have for using

Hallo, I have running xen-4.2/linux-3.8 (compiled) on any hosts. - dell pe r720: drac, eth0-3:igb squeeze -> boot_xen:ok net:ok bridge:ok - dell pe R620: drac=eth0, eth1-3:tg3 wheezy -> boot_xen:ok net:ok bridge:fail So i running "xend start" (or "xenbridges start") on my patient (R620 with broadcom tg3) network will be lost: RTNETLINK answers: File exists

Hi, The attached patch fixes the setup of the bridge ports and the bridge itself. Changes: * move some functions to xen-network-common.sh, so both vif-bridge and network-bridge can use them. * add a new function to configure bridge ports and use it. * make sure arp requests, ipv6 autoconfiguration and ipv6 router solicitations are disabled for the bridge ports and also for the

Hello, What is for you the best GlusterFS scenario in using XenServer (i'm not talking about Xen on a linux but XenServer baremetal) for a web farm (Apache-Tomcat) ? I were thinking of using ZFS as the filesystem for the different nodes. The objectives/needs : * A storage cluster with the capacity equal to at least 1 node(assuming all nodes are the same). * being able to lose/take down any

Supermicro X7DWN+, XEON 5410, Centos 5.2, Xen 3.2.1 At what looks like random times network traffic over xen bridge stops working, the only way I found to fix it is a reboot. This sometimes takes 10 min, other times it may be up for 10 days. This happened with default xen that comes with RedHat EL 5.2 as well as a default install of Fedora 8. Any ideas? ><> Nathan Stratton

Hello folks, I am running Xen 2.6 under Centos 5.2 installation, and am trying to port Xen migration abilities to Infiniband. But, the InfiniBand drivers do not work under Xen kernel, only under non-Xen kernels. It looks like I need to install some patches to rectify the situation. Has anyone ever worked with Infiniband and Xen and would be able to give me inputs about the same? I would really

I have 6 boxes with a client config (see below) across 6 boxes. I am using distribute across 3 replicate pairs. Since I am running xen I need to disable-direct-io and that slows things down quite a bit. My thought was to move the replicate / distribute to the backend server config so that self heal can happen on faster backend rather then frontend client with disable-direct-io. Does this

Hello, On a xenserver with several (39) domUs, we experience problems with the system clock of the domUs. The clock seems to drift away several seconds up to two minutes from the dom0 clock. We do have set independent_wallclock=0. According to the docs (i.e. http://wiki.xensource.com/xenwiki/InstallationNotes) that way domUs should use the dom0 clock, but apparently that''s not the case.

Lets say you had 4 servers and you wanted to setup replicate and distribute. What methoid would be better: server sdb1 xen0 brick0 xen1 mirror0 xen2 brick1 xen3 mirror1 replicate block0 - brick0 mirror0 replicate block1 - brick1 mirror1 distribute unify - block0 block1 or server sdb1 sdb2 xen0 brick0 mirror3 xen1 brick1 mirror0 xen2 brick2 mirror1 xen3 brick3 mirror2 replicate block0 -

Package: xen-utils-common Version: 4.1.4-3 Severity: important Dear Maintainer, Executive summary: dist-upgrade - squeeze to wheezy. Rebooted machine; no default route on network interface eth0. Commented 'transfer_addrs' function in network-bridge produced a machine which worked after reboot. We're using network-bridge as our xen networking configuration. After rebooting the

Hi, I have a small issue with the SAY command and i hope you can clarify it out for me. I boot my system with the attached extlinux.conf, which has some entries to boot old kernels. When i'm booting the old versions i'd like to have a reminder message recalling me that the most recent kernel is not being used, so that i don't forget to switch back to it, for example after many days of

In reading the Xen list there are frequent postings regarding NTP time drift issues for virtualized guests, correct configurations, etc. We have a solution (no cost) for monitoring time drift of hosts for anyone needing to do so or to determine whether their environment is maintaining time synchronization. For etiquette I am not publishing the information to the list mailing. If interested,

xenconsole fix. reference of tty->count in xencons_close() is racy. It must be protected by tty_sem semaphore like con_close() in drivers/char/vt.c -- yamahata _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Greetings. I''ve reviewed the list archives, particularly the posts from Zakk, on this subject, and found results similar to his. drbd provides a block-drbd script, but with full virtualization, at least on RHEL 5, this does not work; by the time the block script is run, the qemu-dm has already been started. Instead I''ve been simply musing the possibility of keeping the drbd

Hello Everyone, I recently had a question that got no responses about GFS+DRBD clusters for Xen VM storage, but after some consideration (and a lot of Googling) I have a couple of new questions. Basically what we have here are two servers that will each have a RAID-5 array filled up with 5 x 320GB SATA drives, I want to have these as useable file systems on both servers (as they will both be

I'm happy to look at a patch that does this. I'd start with a small interval and increase it by 50%, say, on each try wit a max retry time limit. This isn't eliminating the problem,only reducing the probability, but still worth it. I had considered doing something like this but it didn't seem necessary at the time. You don't want to retry indefinitely since the connection

Great. For the record of this thread, I've submitted patch PR17391 (https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17391). I've patched it against the latest R-devel on the SVN, passes 'make check-all', and I've verified it works with the above tests. /Henrik On Fri, Mar 9, 2018 at 4:37 AM, <luke-tierney at uiowa.edu> wrote: > I'm happy to look at a

I have an issue where winbind will occasionally pause for 30 seconds. # strace -T -t ls -l /share 16:52:20 read(4, "/var/lib/samba/winbindd_privileg"..., 35) = 35 <0.000009> 16:52:20 lstat("/var/lib/samba/winbindd_privileged", {st_mode=S_IFDIR|0750, st_size=72, ...}) = 0 <0.000011> 16:52:20 lstat("/var/lib/samba/winbindd_privileged/pipe",