search for: hostconfiguration

So Working on CEntOS 5 I am trying to sett up Xen with 2 bridges, one that connects dom0 and most of the domU to the physical card and the out to the network. Got that figured out no problem, now i want to have a second bridge that runs a local network for all the doms that doesn''t connect to the network. With code I have found used in multiple places I can easily get 2 bridges, and

Hi *, having built Xen 4.1.0 and running my Dom0 on Slackware 13.1, I''m trying to assign different physical network interfaces to different DomU guests: vif = [ ''bridge=ethX'' ] in the DomU configuration files. My /etc/xen/scripts/network-bridge script, however, doesn''t create more than one bridge: root@cen:~# /etc/xen/scripts/network-bridge start

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

Dear List, I use Debian Squeeze with Xen dom0 Kernel 2.6.32-5-xen-686, the Xen Hypervisor 4.1 and qemu 4.0. I have installed a HVM domU which contains a Debian Squeeze standard installation. Everytime I start the domU with the ''xm create ..'' command from dom0, the eth0 lan connection gets interrupted and rebuilts. When domU is booted, the dom0 system hangs every minute for

Hi, I am using Xen 4.1.1 with Linux 3.0.1 kernel. Previously (Xen 3.4.4 and linux kernel 2.6.18) Xen by default created veth0 <--> vif0.0 pair in dom0. With Xen 4.1.1 these pairs are missing in dom0. Using command ''ip link add type veth'' I can create veth0 and veth1 but vif0.0 is still missing in dom0. (When new domU created I can see vif1.x created) Could you please help

Hi, I am using Xen 4.1.1 with Linux 3.0.1 kernel. Previously (Xen 3.4.4 and linux kernel 2.6.18) Xen by default created veth0 <--> vif0.0 pair in dom0. With Xen 4.1.1 these pairs are missing in dom0. Using command ''ip link add type veth'' I can create veth0 and veth1 but vif0.0 is still missing in dom0. (When new domU created I can see vif1.x created) Could you please help

Hi, We just migrated xen on gentoo on amd64 from 4.0 to 4.1 and encountered a few issues that were not documented. Here is how we solved them and what issues are remaining: 1. Our config files were referring to the LVM devices like /dev/vg/domU-root with disk = [ ''phy:vg/domU-root,sda1,w'' ]. This does not work anymore, we have to include ''/dev/'': disk = [

Hi, We just migrated xen on gentoo on amd64 from 4.0 to 4.1 and encountered a few issues that were not documented. Here is how we solved them and what issues are remaining: 1. Our config files were referring to the LVM devices like /dev/vg/domU-root with disk = [ ''phy:vg/domU-root,sda1,w'' ]. This does not work anymore, we have to include ''/dev/'': disk = [

Recently I installed Xen on my computer.But there are some problems during the starting time. The /var/log/xen/xend.log is follows: [2011-06-10 14:24:36 1395] DEBUG (XendDomainInfo:1794) Storing domain details: {''cpu/3/availability'': ''online'', ''description'': '''', ''console/limit'': ''1048576'',

Package: xen-utils-common Version: 4.0.0-1 Severity: important If using ethernet bonding and network-bridge with xen the network-bridge scripts breaks the network. I have run through the commands manually in irder to establish the culprit. In the op_start function (Starting on line 214) everything is fine up until line 251. At this point the bridge has been created, devices renamed and the

I come across some problem when using xen-4.1.1-rc1-pre from xen-4.1-testing tree and 2.6.32.36xen linux kernel from git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git. when I use ''xend restart'' , it hangs when kernel dmesg printing ''Bridge firewalling registered'' and the console show below messages: localhost# xend restart Nothing to flush. Cannot

Hi all, Does anyone know what the correct steps are to add a XEN bridge, let''s say xenbr0 to Debian Squeeze? I have added the following to /etc/network/interfaces # XEN Bridge auto xenbr0 iface xenbr0 inet manual bridge ports eth0 bridge_stp off bridge_fd 0 And then rebooted the server but brctl show still shows eth0 as bridge: newusaxen:~# brctl

Hello, Are there any good alternatives to the network-nat script on Debian Squeeze? I have tried using (network-script network-nat) and (vif-script vif-nat), but I end up with an error message like Error: Device 1 (vif) could not be connected. ip addr add 10.0.1.259 dev vif4.1 failed with configuration file directive vif =[ ''script=vif-nat,ip=10.0.1.132'' ] I need Internet

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

Package: xen-utils-4.0 Version: 4.0.1-2 Severity: normal This issue is similar to http://lists.alioth.debian.org/pipermail/pkg-xen-devel/2011-March/003217.html but since I was not able to find a bug report I'm reporting this now. Steps to reproduce: 1) cat << EOF > config name = 'squeeze64' vcpus = '4' memory = '512' disk = [

The following series flushes my documentation queue and replaces previous postings of those patches. The main difference is that the xl cfg file is now formatted using POD instead of markdown and presented as a manpage. I have setup a cron job to build docs/html and publish it at http://xenbits.xen.org/docs/unstable/ (it''s a bit bare right now). The motivation for some of these patches