similar to: Debian & eth0 vs. peth0

I installed 64-bit xen 3.1.0 (from xensource.com tarballs) on three new machines today, using a configuration setup that I''ve used successfully many times before. However, I encountered a new problem. These are Dell Poweredge 1950 servers, by the way. >From lspci 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 08:00.0 Ethernet

I am posting the message below again because it did not go through last night. Help! Steve Timm -- ------------------------------------------------------------------ Steven C. Timm, Ph.D (630) 840-8525 timm@fnal.gov http://home.fnal.gov/~timm/ Fermilab Computing Division, Scientific Computing Facilities, Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.

I have a Xen DomU configuration that was made in the days before libvirt and virt-install. In this configuration I have: vif = [ ''mac=00:16:3e:05:06:01, bridge=xenbr0'', ''mac=00:16:3e:05:06:0a, bridge=xenbr1'' ] and then in xend-config.sxp I define (network-script my-network-bridge) where my-network-bridge is in the scripts directory and looks like this:

I have the xensource 3.1.0 x86_64 tarball installed over a RHEL5 clone distribution. The "ethtool" utility only returns the following information: [root@fermigrid5 etc]# ethtool eth0 Settings for eth0: Link detected: yes [root@fermigrid5 etc]# Since I have no vanilla-installed rhel5 machines with which to compare, I am not sure if I am dealing with a bug in the ethtool (whose

I added a virtual interface eth0:1 on one of my machines and suddenly networking breaks on startup of the system (eth0 is gone) when xend starts and runs the network-bridge script. This is supposed to be fixed according to: https://bugzilla.redhat.com/show_bug.cgi I checked and the network-bridge script contains this fix. It works fine on one of my PCs when eth0:1 is added, but not on this

Does anyone know if the Xen 3.1.0 kernels as distributed in the "open source" tarballs (x86_64 version) are vulnerable to the recently-announced vulnerability CVE-2007-4573? IF so, is there any plan to release patched tarballs anytime soon? Thanks Steve Timm -- ------------------------------------------------------------------ Steven C. Timm, Ph.D (630) 840-8525 timm@fnal.gov

Hi, If one sets xend to use network-bridge and there are no bridges already present then it seems that xend will clone eth0 to peth0, create xenbr0 and add peth0 and vif0.0 as ports on that bridge. If on the other hand xenbr0 is created in /etc/network/interfaces then xend will not do any of that peth0 stuff, nor will it add vif0.0 to xenbr0, yet (barring some changes in iptables rules) things

I tried netperf / netserver with Dom0 / DomU, but I could''nt get a correct NW traffic with xentop. Is there anybody could help me? At Host1''s Dom0, run netperf -H VMIP At Host2''s DomU (with VMIP named TTVM), run netserver At Host1, run xentop this way ->"xentop -n -b -d 1" At Host2, run xentop this way->"xentop -n -b -d 1" In Host2''s

Hello Community, I successfully installed and run xen (xm list and xm info can output appropriately). However, while I was installing domU image by using virt-install -p at domU OS. I encountered an error information" Host does not support virtualization type ''xen'' ". I built xen from source. Some of my friends have the same issue, but if they use pre-build xen, the

HI, guys Recently,I met a problem. Xen''s version: 3.4.3 guest os:redhat 4.8 32bit And xen.independent_wallclock = 1 has been set. The time of guest os change to be fast suddenly, about 2000 second. because the change is too wild, ntp didn''t sync to the ntp server''s time. my application is dependent on the systme time. And this occurs a lot of times. I don''t

Hi! I want to forward the port 3389 from the domU to the virtual server with ip address 192.168.122.77 with not success... I tried a lot of iptables rules with no luck so far. Is this possible? I take a look at other post and I don''t found an answer. By example: /sbin/iptables -t nat -A PREROUTING -p tcp -i xenbr0 --dport 3389 -j DNAT --to 192.168.122.77:3389 the virtual nic for the

Has anyone yet figured out what it would take to make Xen run on top of the Red Hat Enterprise Linux 6 beta? We are heavily invested in Xen under RHEL5 (actually a redhat clone) distribution, but already the xen kernel they are shipping with update 4 and 5 is shaky and has bugs which they don''t seem to be in a hurry to fix. Basically I am wondering if Redhat 6 is just going to have

Hello list, I tried to install Xen 3.1.0 on Scientific Linux (RHEL4), but this mission failed.. Hope you can help me by finding the reason for my problem. I downloaded the xen sources from http://bits.xensource.com/oss-xen/release/3.1.0/src.tgz/xen-3.1.0-src.tgz and compiled them by running "make" and "./install.sh". This seemed to work. After setting up grub like this,

I have seen the following kernel panic 5 times today on three different machines, two of which had been stable for months and one of which is a brand new install. We are running the x86_64 xen kernel and userland tools that came in the Xen 3.1.0 tarball from xen.org, on top of scientific linux (redhat clone) 5.1 or 5.2. <Aug/28 12:21 pm>Unable to handle kernel NULL pointer dereference at

I have a new x3655 IBM and whenever the /etc/xen/scripts/network-bridge script starts, the ethernet would no longer work. This post isn''t about the cause, but the fix. I did a lot of tcpdumps and Googling, but I''ll spare you that. All they do is prove that yes, there is an issue. :) I tried Debian 4.0 i386/amd64 and Ubuntu 7.04 Server i386/amd64 and they all exhibit the

Hi, I''ve installed xen 3.0.3 from packages (xen-linux-system) on a debian etch, and i''ve configured it with network-bridge script in the default way (netdev=eth0, bridge=xenbr0, etc...) which is ok for me. the problem I have: I cannot ping any outer machine from dom0 (nor any outer machine can ping me). It gives me a "Destination Host Unreachable" message that

Hi, I was hoping someone on this forums could help me out with a problem I was facing with Xen. When I compiled the kernel for Xen-3.1.3 using "make world"(I know this is an old version but I need to use it for some compatibility issues), the kernel was missing the Xen netloop module. There was no /kernel/drivers/xen/netback/netloop.ko in the newly compiled kernel. I think we would

I just downloaded Debian Squeeze and installed Xen from packages, following the instructions here: http://wiki.debian.org/Xen I am able to get PV guests up and running easily, but HVM guests will not even boot. The HVM I am currently trying to run is Debian sarge, which I installed into a disk image and configured using qemu. I am running on an HP Proliant ML150G6, which has Intel-VT hardware

I have nic bonding (mode=802.3ad) setup on 2 servers, both running Centos 5.5 In the "Active Aggregator Info", on one reports 4 ports - which is correct - but the other only reports 3 ports. It''s always eth0 that shows a different aggregator ID. Changing the cables around so it hits a different port on the switch makes no difference. The switch is correctly configured for the

Hi: Reading Red Hat''s Website and a printed manual of RH184 (Red Hat Virtualization course) I see that RHEL 5 only supports RHEL 4.5 and RHEL 5 as paravirtualized guests. So I asume this is the same situation for CentOS 5, right? What''s the dependency between Xen versions for paravirtualized guests? I ask this questions because I got this experiences: 1. Running CentOS 5 as