similar to: Unable to get IP address in guest OS through DHCP

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

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

Hello everybody, Here again with a Xenbr0 bridge problem I''m a Gentoo user, xen-sources-2.6.34 and I always used the bridge from eth0 to xenbr0. Here''s what I get at boot time: * Bringing up interface eth0 * null [...] * Starting Xen control daemon ... And the bridge doesn''t come up. The normal behaviour should be that the Xenbr0 bridge comes up automatically, but

Based on Waldi''s RFC at http://lists.xen.org/archives/html/xen-devel/2012-09/msg00943.html To use it set vif.default.script="vif-openvswitch" in /etc/xen/xl.conf or use script=vif-openvswitch in the vif configuration. Appears to do the right thing for PV and HVM guests (including tap devices) and with stubdomains. In order to support VLAN tagging and trunking the

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

Hello, is there a way to start automatically the vncviewer when a domU starts? When I was using the xm toolstack I could use "xm create domain.cfg -vncviewer" or something similar (if I''m not wrong), but I don''t know how to do it with the xl toolstack. At the moment, I have to create the domain using xl create domU.cfg, then xl list to see the domU id and then xl

Hi, I build Xen 4.1.1 on a Gentoo base dom0. Everything is working great. I tried one of Joseph Glanville''s PV-HVM image (debian6) and its working as it should. Now l''im trying to build a Gentoo based domU with then same specs as Joseph''s PV-HVM. I used a copy of the .cfg and adapted to my needs to make the gentoo work. when booting the minimal install image using

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

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

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

Hello, I am trying to setup Debian Squeeze as domU, but I get the message below during the setup process: No Ethernet card was detected on Debian Squeeze domU install And it asks to select the driver to me. I followed the instructions at page 27 of the guest.pdf manual, but there is no indication on how to set-up the bridge in order to make the ethernet interface available for the guest. How

Hello Everyone, I am new with XCP. I''ve setup several hosts with* XCP 1.0* and manage it through XenCenter and command console. Each host has two NICs, one (xenbr0) connected to a physical switch for Internet (said sw1), the other (xenbr3) connected to a physical switch for internal network (said sw2). I am trying to setup VMs and VLANs on xenbr3. I created a virtual bridge by

Hello, I set up a Sabayon Linux domU as hvm guest and I completed the installation successfully. The problem is that when KDE is going to start, I see a blank screen. I use vncviewer but I don''t think this problem is related to vnc. Then I''ve read the minimal system requirements and I have seen this: 1) i686 Processor (starting from AMD K6 and Intel Pentium II) 2) 512 MB of RAM

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

Hi List, I''m new on the Xen Virtual Machines world, I did a search around looking for a solution on this problem and I could find anything I''ve a new server Dell R900 (Two QuadCore 2.93Ghz, 32GB Ram) where the following message appear when I try to boot any DomU guest machine: ERROR: Not a Xen-ELF image: No ELF notes or ''__xen_guest'' section found. ERROR:

Hello, There is a xen setup in which "brctl show" gives the following output. bridge name bridge id STP enabled interfaces eth1 8000.003048c9d4df no peth1 vif1.0 vif2.0

Hi. I got a server running Centos 5.7 x64 running default xen version 3.1, but I want to move to 4.1 from Gitco. I got win2k3/centos domU machines there. To move my server to xen 4.1, do I need to change something in our vm''s? or in our dom0? Thanks!!! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Hello, I have a network issue in dom0; I''m not sure if it''s a configuration problem or a design problem in my setup. My setup: The server (dom0) runs Ubuntu 7.10, Xen was installed using apt-get (means version: Xen 3.10, Kernel 2.6.22-14). This server has 4 NICs. I use bridged networking with my own script which creates 4 bridges ("$dir/network-bridge"