similar to: are Xen 3.1.0 kernels CVE-2007-4573 vulnerable

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,

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

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

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

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:

Hi, please, excuse my poor English Exist any tool for upgrade kernel automatically in DomU machines? Because I have the following problem: After upgrade the kernel package from linux-image-2.6.24-21-xen to linux-image-2.6.24-22-xen in Dom0 (an Ubuntu Server), I modified the config files in /etc/xen/domUmachine.cfg for all my VM. Later a restarted its, but i found the following error // DomU //

If I have a linux kernel on dom0 from xen 3.0.2 and my xen binary is version 3.1.0, can I expect things to work? What about if my dom0 kernel and xen binary are both 3.1.0 and I have a para virt domU with xen 3.0.2 code in? What about if the tools are from a different version of xen? I''m asking because I''m running fedora 6 and I''d like to try out xen 3.1.0 or 3.0.4

Just reporting some iperf results. In each case, Dom0 is iperf server, DomU is iperf client: (1) Dom0: Intel Core2 3.16 GHz, CentOS 5.2, xen 3.0.3. DomU: Windows XP SP3, GPLPV 0.9.12-pre13, file based. Iperf: 1.17 Gbits/sec (2) Dom0: Intel Core2 2.33 GHz, CentOS 5.2, xen 3.0.3. DomU: Windows XP SP3, GPLPV 0.9.12-pre13, file based. Iperf: 725 Mbits/sec (3) Dom0: Intel Core2 2.33 GHz,

xen-3.0.3-94.el5_4.2 2.6.18-164.6.1.el5xen RHEL5.4 x86_64 I''ve got a dom0 that does nothing but have a DomU created. The DomU gets plenty of load. Over time, the dom0''s ipconntrack table fills up but not the DomU. Once it gets full I can restart iptables and it''s fine. The strange thing is this only happens on hosts I have provided (hardware and hosting) from one

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

Hello everyone, I''m totally new to Xen and trying to run it on some platforms (x86, x64) using SLES (that is what I have to use for reasons other than technical). Several machines on which I tried using Xen simply fails to run normally using Xen kernel: either network communication is not functioning at all despite proper configuration (that works on non-Xen kernel), or the kernel

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.

Hi There is a problem when creating a domU. I intend to install Solaris N90 on RedHat RHEL5 in paravirtualized(I''ve tried fully virtualized method, that''s no problem). #xm info release : 2.6.18-53.el5xen machine : i686 xen_caps : xen-3.0-x86_32p My steps are as follow(install via NFS): 1 mkdir disk and mkdir Solaris 2 mount /dev/cdrom /disk/Solaris, it tell me that disk

Hello, I''ve recently installed a hvm domU opensuse 11 guest and I cannot set the screen resolution higher then 640x480. This seems very strange to me, because I don''t have any problem to set higher resolution on a windows 7 domU, using the following parameters in the configuration file: stdvga=1 videoram=16 What could the problem be? Is some video driver missing? -- Flavio

Hello, I''ve recently installed a hvm domU opensuse 11 guest and I cannot set the screen resolution higher then 640x480. This seems very strange to me, because I don''t have any problem to set higher resolution on a windows 7 domU, using the following parameters in the configuration file: stdvga=1 videoram=16 What could the problem be? Is some video driver missing? -- Flavio

Hi, can anyone provide any pointers as to how to avoid this issue? A CentOS 5.3 domU on snv_111 dom0 is crashing on bott unless I remove /lib/modules/2.6.18-128.1.6.el5/kernel/drivers/xenpv_hvm dom0: haggis:~$ uname -a SunOS haggis 5.11 snv_111 i86pc i386 i86xpv Name: SUNWxvm Summary: Hypervisor Header Files Category: System/Virtualization State: Installed

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

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