similar to: [dhcp] virtual server on DomU & dhcp relay

Today I found I can not ping some of my domU''s. I logged in to dom0, did a "xm list", all domU are there. Then I did a "ifconfig" and surprised to find some of vif''s disappeared! Like for example. "xm list" show dom13 is alive, but "brctl show" shows no vif13.0. If I "xm console 13", there''s some message: WARNING:

Hello, I am running Xen 3.0.2 on a regular Intel P4, with the default network setup. My problem is that my domU''s DHCP requests do not seem to reach the outside world. I can see them if I tcpdump in dom0 on xenbr0, but I cannot see them from another machine plugged into the same switch as my Xen machine. This external machine _can_ see the DHCP requests made when dom0 makes its

I am running Xen 4.0.1 with a 2.6.18-194.32.1.el5xen CentOS Dom0. I built and installed the Xen binaries from source. The systems boot successfully however I am having issues bring up DomUs. Here is config: name = ''xyz'' memory = 256 vcpus = 1 pae = 1 vnc = 1 vncunused = 1 disk = [ ''phy:/dev/vg1/xyz,hda,w'' ] vif = [

I am experiencing strange network behavior from several DomU''s. I can ssh from DomU to any host on the local lan/vlan, I can ping those hosts. However when I go to resolve a hostname DNS fails. I have verified that three other DomU''s are exhibiting the same behavior. I have also verified that Dom0 is functioning properly and can resolve hostnames and access hosts outside of the

Hi All I have xen 4.0 in centos dom0 the machine was working fine for months and yesterday out of sudden I can no longer provision new vms and to make things worst If any vm shutdown I cannot re run it again . the vm stop at the process of detecting the (ubuntu and debian all versions) [!] Detect Disks "No disk drive was detected. If you know the name of the driver needed by your disk

I am running Xen 4.0.1 with a 2.6.18-194.32.1.el5xen CentOS Dom0. I built and installed the Xen binaries from source. The systems boot successfully however I am having issues bring up DomUs. Here is config: name = ''xyz'' memory = 256 vcpus = 1 pae = 1 vnc = 1 vncunused = 1 disk = [ ''phy:/dev/vg1/xyz,hda,w'' ] vif = [

After running out of swap and memory and freezing, a domU called web02 won't start up. Both dom0 and domU are running CentOS release 5.4. dom0's kernel is 2.6.18-164.el5xen and I'm running the stock xen from CentOS: xen-3.0.3-94.el5 After issuing 'xen create web02' I see the following in the xen console: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) vmalloc

Hi all, A client just phoned me and said he could not SSH into his VPS, yet he can ping it. So, I login to the host node, and check it out, can''t SSH into. I shutdown iptables on the VPS (via xm console serverza.vm) but still can''t SSH into it. I restart the VPS, still can''t SSH into it. So, I check the host, and found this in /var/log/messages: Jul 22 19:19:07

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

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:

Hi all, my dom0 is centos5.2 and domU paravirtualized is centos5.1 I can play sound on dom0 but not in domU (name: gasphar), moreover I use wifi as my inet connection and on installing domU cento5.1, I used virt-manager. I know that libvirtd made virbr0 and when changing to xenbr0, I cannot connect to internet but ssh to dom0 is fine! so how do I enable sound device on domU and changing to

Hello, It looks like xen 4.1.2* has some problems with solaris 11 iso images too (s. further below log messages) hvm-solaris11.born2b3.net.cfg # --- kernel = ''/usr/lib64/xen-default/boot/hvmloader'' builder = ''hvm'' device_model= ''/usr/lib64/xen-4.1/bin/qemu-dm'' name = ''solaris11hvm.born2b3.net'' acpi =

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

Changes since v1: - Include nic,net2,vkb,vfb init functions --- This allows libxl users to get some sane default values for this complex set of structures. This is purely code movement and there are no functional changes except for a trivial error handling change in nic device init. Signed-off-by: Gianni Tedesco <gianni.tedesco@citrix.com> diff -r efe2d3ea22ae tools/libxl/libxl.c ---

Hi, I cannot get my network up in WinXP- and winVISTA-domU''s I need some help, since I got lost in the google-jungle... My system: UBUNTU gutsy gibon-AMD64 on a intel core duo-system. this is my /etc/xen/winxp.cfg: ######### # # Configuration file for the Xen instance debian.qwork.test, created # by xen-tools 3.5 on Sun Mar 16 20:03:26 2008. # # # Kernel + memory size # kernel =

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

> -----Original Message----- > From: Ewan Mellor [mailto:ewan@xensource.com] > Sent: Tuesday, December 06, 2005 9:16 AM > To: Dave Thompson (davetho) > Cc: Xen Mailing List > Subject: Re: [Xen-devel] Hotplug scripts not working... > xen/ia64 domU stoppedworking > > On Tue, Dec 06, 2005 at 09:51:24AM -0500, Dave Thompson > (davetho) wrote: > > >

Hi! Please help me. # xm create win7.hvm Using config file "./win7.hvm". Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1 grep -v ^# /etc/xen/win7.hvm | grep -vx '''' kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' memory = 2048 name = "win7" vif = [

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