similar to: Script for bond+vlan bridging from red hat

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

I am experiencing strange network behavior from several DomU''s. I can ssh from DomU to any host on the local lan/vlan, I can ping those hosts. However when I go to resolve a hostname DNS fails. I have verified that three other DomU''s are exhibiting the same behavior. I have also verified that Dom0 is functioning properly and can resolve hostnames and access hosts outside of the

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

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

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

We had problem using tagged vlans inside domU. Testing shows that this is caused by changing network interfaces in network-bridge script. Following patch should allow to use vlans in guest. Testing scenario: configure vlan network (e.g. vlan 1 on eth0 => eth0.1) start xend create domU and configure same vlan inside it You can see that vlan is still <interface>.<vlan_id>. You can

Hello, when I boot DomU which uses DHCP to configure IPv4 address it does never get a lease. The packets travel to Dom0 where the dhcp server receives them, sends a reply, that travels to DomU where dhclient receives it, says the checksum is invalid, and discards it. The problem is documented here: http://old-list-archives.xen.org/archives/html/xen-users/2006-02/msg00152.html

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

Hello: I just gave 3 tries at compiling a xen kernel. I managed to get the networking in the host to work ok on the third try, unfortuately xend gives me the following errors in my xend.log and will not start. Any ideas? It fails to start with the following error ---------------------------------------------------- /usr/sbin/xend [root@localhost ~]# /usr/sbin/xend start Traceback (most recent

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

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

Pardon me for a long detailed post but this looks pretty serious. The bottom line is that, when I attempt to shut down or reboot my simple xen-2.0.7 server running FC3 with two domUs, shutting down xendomains appears to send python into an infinite loop. This may be due to a serious misconfiguration on my part but it is certainly a big problem. If we shutdown the domUs manually first, the

Package: xen-utils-common Version: 4.1.4-3+deb7u1 Severity: normal Tags: patch Dear Maintainer, * What led up to the situation? I have a xen dom0 with more than one interface that I want to make bridges on * What exactly did you do (or not do) that was effective (or ineffective)? I have my own bridge making script that calls network-bridge for each interface. This used to work in

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",

A solution is to have parallel:::.slaveRSOCK() attempt to connect multiple times before failing, e.g. makeSOCKmaster <- function(master, port, timeout, useXDR, maxTries = 10L, interval = 1.0) { port <- as.integer(port) for (i in seq_len(maxTries)) { con <- tryCatch({ socketConnection(master, port = port, blocking = TRUE,

Hello I use XEN 3.0 in debian sarge. I have a domU1 for routing and firewall. This domU1 use 2 network interfaces which is on a bridge ''gate'' and the other on bridge ''lan''. dumU2 use one interface (eth0) on bridge ''lan''. Then I make a ping out of domU2 to www.debian.de so I get no answer. The name isn''t resolved. A ping to IP of

Hello, > What do you get from the "I" command? A string of 8 spaces. >> So I believe the compatibility list deserves two new lines. > >Probably best to delay adding this to the HCL until we can get the driver to shut down the UPS properly. I debugged the problem. From the source, drivers/blazer.c:418 /* * If a command is invalid, it

Package: xen-utils-common Version: 4.0.0-1 Severity: important If using ethernet bonding and network-bridge with xen the network-bridge scripts breaks the network. I have run through the commands manually in irder to establish the culprit. In the op_start function (Starting on line 214) everything is fine up until line 251. At this point the bridge has been created, devices renamed and the