similar to: xen 3.1/ RHEL5 vs. ethtool

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

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

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

I want to check the speed like features of my Ethernet in dom0 and domUs. But in virtualized environment it gives strange output why is that so? how to check it otherwise? Non-virtualized FC11 [root@fasiha home]# ethtool eth0 Settings for eth0:     Supported ports: [ TP ]     Supported link modes:   10baseT/Half 10baseT/Full                             100baseT/Half 100baseT/Full    

I want to check the speed like features of my Ethernet in dom0 and domUs. But in virtualized environment it gives strange output why is that so? how to check it otherwise? Non-virtualized FC11 [root@fasiha home]# ethtool eth0 Settings for eth0:     Supported ports: [ TP ]     Supported link modes:   10baseT/Half 10baseT/Full                             100baseT/Half 100baseT/Full    

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

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

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

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

in dom0, how does one get and set the link information for a NIC? In a non-xen kernel, we could get this info by simply running: # ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes:

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

Hi LLVM-Devs, I have managed to complete updating our sources from LLVM v4.0 to v5.0, but I am getting selection errors for 'callseq_end'. I am aware that the 'ADJCALLSTACKUP' and 'ADJCALLSTACKDOWN' patterns have changed, and have added an additional argument to the TD descriptions for these. There are interactions with 'ISD::CALL' and 'ISD::RET_FLAG',

Hi Martin, Pseudo CALLSEQ_START was changed in r302527, commit message contains details on the changes. However CALLSEQ_END was not modified. If your made changes to ADJCALLSTACKUP to add additional argument, that may result in error. Thanks, --Serge 2017-09-15 19:09 GMT+07:00 Martin J. O'Riordan via llvm-dev < llvm-dev at lists.llvm.org>: > Hi LLVM-Devs, > > I have managed

Hi Serge, Thanks for your help. I have looked at the change log, and so far as I can tell, my implementation is pretty much identical to all of the in-tree targets, but I’m missing something and can’t see what it is. I have simplified my TD description to just: def MyCallseqStart : SDNode<"ISD::CALLSEQ_START", SDCallSeqStart<[SDTCisVT<0, i32>,

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