similar to: installing DomU with two network bridges via virt-install

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

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

I''m running xen 3.1.2 as bastardized by RedHat on a redhat clone operating system. I''m using the xendomains script as it came out of the box to start my domU''s at boot and stop them at shutdown. There are three problems right now: 1) left to its own devices, service xendomains stop attempts to do "xm save" on each of the domU''s. that takes quite a

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

I have installed the xen 3.1.0 x86_64 tarball compiled for RHEL5 on a RHEL5 system. The system in question was able to boot with the xen kernel that came with RHEL5. I untarred the tarball, and did cd /boot mkinitrd /boot/initrd-2.6.18-xen.img 2.6.18-xen The command exited properly and made a initrd image. The machine booted with a grub.conf entry like this: title Xen 3.1.0 root

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

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

When I boot from a regular centos kernel, I get this for a mac 00:19:db:e5:91:4f somehow it is getting reversed. Could I have messed something up when I built the kernel? Greg No virus found in this outgoing message. Checked by AVG. Version: 7.5.524 / Virus Database: 269.24.3/1472 - Release Date: 5/29/2008 7:27 AM _______________________________________________ Xen-users mailing list

Hi, I have been able to run 32 bit virtual machines on a 64 bit machine quite nicely with xen3.1 but sometimes when running yum the messages "do_wp_page: bogus page at address 0070d638" and "kernel: VM: killing process yum" and yum just stops working. I also get Kernel Panic. Does anyone have any idea, what could be the probem? Thanks, Ricardo

Hello, I knew that Amazon ec2 is using xen...but are they any documents/tutorial which teach how to plan/design/implement a grid/cloud computing infrastructure using Xen? Thanks. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Setup: RedHat/Centos/Sci. Linux 5 update 3, Dom0: kernel-xen-2.6.18-164.10.1.el5xen 64-bit (on Dell Poweredge 2950 dual quad-core). DomU: kernel-xen-2.6.18-164.10.1.el5xen 32-bit, 1 vcpu 6 domU''s per dom0. We have also seen the same problem with 2.6.18-164.9.1 and 2.6.18-164.6.1 kernels on this branch. Symptom: On 32-bit domU only (we have never seen 64-bit domU be affected), we observe

Hi. I am trying to setup my firewall in DomU. However, I have got a little problem. My pon dsl-provider exits with following message. Nov 18 09:44:40 alsfw01 pppd[1723]: Plugin rp-pppoe.so loaded. Nov 18 09:44:40 alsfw01 pppd[1723]: Linux kernel does not support PPPoE -- are you running 2.4.x? Nov 18 09:44:40 alsfw01 pppd[1723]: Exit. I am running xen out of the box on Debian Stable. My

It seems that with their specific Xen packages, Debian likes to go against the norm, and rather than calling the Xen bridging device something sensible like "xenbr0", they rename the main physical ethernet device "eth0" to "peth0" and create "eth0" as the Xen bridge (as far as I can tell, anyways). Anyone know where exactly they do this so I can reverse it?

>/ these are the packages installed:/ > >/ ii linux-image-2.6.18-6-xen-amd64 2.6.18.dfsg.1-18etch1 / >/ Linux 2.6.18 image on AMD64/ >/ ii linux-modules-2.6.18-6-xen-amd64 2.6.18.dfsg.1-18etch1 / >/ Linux 2.6.18 modules on AMD64/ >/ ii xen-hypervisor-3.2-1-amd64 3.2.0-2 / >/ The Xen Hypervisor on

Hi, I (just) posted something similar to this on the fedora-xen list so apologies if some of you see it twice. I''m about to commission a new dom0 host to host multiple dom0 instances for testing purposes. I''m currently trying to decide what platform to use. I''ve previously used FC6 and CentOS5 as Dom0 hosts. I''d like to be able to use Xen 3.2, and I see

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,