similar to: Xen 3.0.2 and DHCP from domU

Hello, I''m trying to get PDB working in accordance with the instructions at http://www.cl.cam.ac.uk/~sos22/replay.bk/docs/misc/XenDebugger-HOWTO and a message from this list: http://lists.xensource.com/archives/html/xen-devel/2004-08/msg00017.html When I try to build pdb I first get errors because the Makefile is configured to treat warnings as errors, and there are some warnings.

I hate intermittent problems ... Most of the time, my domUs launch just fine. But, occasionally I get a failure to connect a vdb or vif and the domU fails to completely launch ("xm list" shows it is present but no console activity either through "xm create -c" or through "xm console"). The log shows a stack trace in DevController.py in the area of waiting for

I hate intermittent problems ... Most of the time, my domUs launch just fine. But, occasionally I get a failure to connect a vdb or vif and the domU fails to completely launch ("xm list" shows it is present but no console activity either through "xm create -c" or through "xm console"). The log shows a stack trace in DevController.py in the area of waiting for

Hi, until now, i have been using Xen 3.0.2. Now i upgraded to Xen 3.0.4. Can anybody confirm, that the ordner in the config files for the network interfaces has not changed? My config file used to read: vif = [ ''bridge=xenbr0'', ''bridge=xenbr1'' ] So inside the DomU, eth0 was attached to xenbr0 on the host and eth1 was attached to xenbr1. Now i upgraded to

Hello, I have a Gentoo Linux guest, which was working very well with the past xm tool stack. Since the migration to xen-4.1.1 and to the new xl tool stack, I have a problem for the IP assignation. Actually, when dhcpcd starts at boot time the IP address is not correctly assigned. This also happens if I perform "dhcpcd eth0" once I''ve accessed to the guest shell. I

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 all, Has anyone managed to get CentOS 6 domU (i.e. guest) working on a Debian 6 do0? Both OS''s are 32bit and I''m running XEN 4.0.1 with HVM support. A CentOS 5.6 domU works fine on this very same server though. When I start CentOS 6, I get the following error: newusaxen:~# xm create -c /xen/genocide.cfg Using config file "/xen/genocide.cfg". xenconsole: Could

As I received no response on the general CentOS list, I'll repost it here as the question is about Xen virtual machine routing. This is my network setup: http://pastebin.com/kyWpTQYU Lets assume my dom0's eth2 public ip is 1.2.3.33 and my dmz network 11.22.33.96/255.255.255.224 . I have created NAT from my LAN with iptables. You can see my /etc/sysconfig/iptables here:

Hello, I''m using Xen 4.0.0 compiled from source with the 2.6.31.13 kernel that it pulls down on its own. I added support for the aacraid driver to the kernel using ''make menuconfig'' from the build-linux-2.6-pvops_x86_64 subdirectory, and then built and installed the whole thing using ''make install'' from the xen-4.0.0 directory. I compiled this

Package: xen-hypervisor-3.0-unstable-1-amd64 Version: 3.0-unstable+hg11561-1 Severity: important The HVM domU won't start. The following is the config (comments stripped). --------------------begin-------------------- import os, re arch = os.uname()[4] if re.search('64', arch): arch_libdir = 'lib64' else: arch_libdir = 'lib' kernel =

Hello, Has any more work been done on this front? The message below is from Sept. 2006. In particular, the LT/TXT Technology Enabling Platform (TEP) is now available from MPC Corp. Where can one obtain an appropriate AC SINIT module (i.e., like lpg_sinit_20050831_pae.auth.bin below)? I would like to begin using Xen with TXT support. Thanks, -Jon This patch adds SMP support to the

Hey folks, I created a DomU, installed Linux, and then realized I''d only given it 1 NIC so brought it down to edit the cfg file to give it another NIC. Originally I just had : vif = [''''] And so I guess the defaults worked for the 1 NIC. So I changed it to : vif =

Hello ! I which to use Xen in order to virtualize a complete local servers farm, using dom0 in front and multiple domU behind. I''m using an external interface, eth0, on Dom0, and a dummy interface, on which the DomUs are bridged through xenbr0. DomU DomU ---Dom0-- | | | | ---------------- | [vif1 vif2 dummy] | xenbr0 eth0---- local

Hi, I have two physical machines connected through a switch in a 192.168.1.* subnet. Dom0''s are assigned static ip addresses 192.168.1.100, 192.168.1.101 respectively. Dom0''s can ping each other. Each physical machine has a domu guest and static address assigned to domu''s are 192.168.1.200, 192.168.1.201 respectively. However domu''s can neither ping each other

Hi, I have Xen 3.0.3 installed on CentOS 5.5 with 2 paravirtualized domU''s configured to use the default bridge networking and am having networking issues. If I boot the computer fresh I am able to ping dom0 and can SSH into it and start the domU''s. The following ping snippet demonstrates the problem. The first group of "Destination Host Unreachable" is while the

I have fedora13 as domain0 kernel on xen-3.4.3 or xen-4.0.1. I installed ubuntu10.04 as guest-os following this : 1) download installer from : - http://fi.archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/vmlinuz - http://fi.archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/initrd.gz to /boot directory 2) edit xen guest

Hi all, I just compiled an installed the Xen Hypervisor, Tools and a new Kernel from the 3.1 source. The dom0 is running without problem and the xm seems to work fine, too (tried xm info, xm list, xm dmesg). Unforunately on creation of a domU I always get an error using a config file and a domU image that is definitley working (at least with 3.0.4): Using config file

If I try to ifup eth0, I get the following: Device eth0 does not seem to be present, delaying initialization. DomU: Linux fedora1 2.6.16-1.2133_FC5xenU #1 SMP Tue Jun 6 02:58:27 EDT 2006 i686 i686 i386 GNU/Linux config: kernel = "/boot/vmlinuz-2.6-xenU" #ramdisk="/boot/initrd-2.6.16-1.2133_FC5xenU.img" memory = 128 name = "fedora1" #dhcp = "dhcp" disk =

Hi! I have a problem with my new Xen setup. I have installed Debian etch with netinstall and I''m using 2.6.18-6-xen-amd64 kernel in my dom0 and 3.0.3-0-4 version xen hypervisor. I''m using four network cards on my system and using three of them as xen bridges and dom0 is using the fourth one only for it''s own. So basicly both of my virtual servers use a network card

I am just beginning to learn R, using _R for Dummies_ by Andrie de Vries and Joris Meys. I am using Windows 7, and RGui (64-bit) version 3.0.2. I have reached the chapter on "Getting Data Into and Out of R." But the code they use for importing data doesn't seem to be working for me. Their example is:> elements <- read.csv(file.path("f:", "elements.csv"))