similar to: Error: Device 0 not connected, waiting for vif2.0 to become free. Usage count = 18236

When i do #xm create name.cfg i''ve ADDRCONF(NETDEV_UP): vif2.0: link is not ready My DomU was created but can''t access to network.... What do think about it? I use xen 3.0.4 HVM. Thanks! -- Benjamin HENRION Elève de 4eme année de l'' EXIA (Nancy) Ecole supérieure d''informatique Spé Réseaux _______________________________________________ Xen-users mailing

Package: xen-utils-common Version: 4.1.2-1 Severity: normal Hi, I was doing some experiments today with XL TOOLSTACK, and found few problems when trying to do PV domU boot. I was trying to run kfreebsd9 or linux-3.2 kernel in qemu using PV i386, and with simple configuration without any disks, nics or virtual framebuffer, kernel boots (and then kernel itselfs correctly fails with information

Hi all, I have strange problem with memory allocation on my xen server. My xen server: - distro: Debian squeeze - xen-hypervisor: xen-hypervisor-4.0-i386 4.0.1-1 - boot options: /xen-4.0-i386.gz placeholder dom0_mem=256M Dom0: - kernel: 2.6.32-5-xen-686 #1 SMP - /etc/xen/xend-config.sxp: (dom0-min-mem 256) (enable-dom0-ballooning no) DomU: - name: storage - distro: Debian

It is rc2-pre. Stubdom fails again.   Boris --- On Fri, 4/10/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: Re: [Xen-devel] First release candidate for Xen 3.4.0 To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Keir Fraser" <keir.fraser@eu.citrix.com> Date: Friday, April

Hi all. I have a problem with pciback in OpenSUSE using PVM. I try to send 3 nic for the PVM.. its ok.. but.. if i try ifconfig eth3 up.. got the error... Please.. see this. Anybody.. know this problem? Thanks, Junior opensuse:~ # uptime 3:36pm up 0:03, 2 users, load average: 0.02, 0.06, 0.02 opensuse:~ # uname -a Linux opensuse 2.6.27.7-9-xen #1 SMP 2008-12-04 18:10:04 +0100 x86_64

Hello, This is my first post in this list. I''m running Debian Squeeze as Dom0 on a bi-xeon 64 bits : root@sd-29499:/etc/xen# uname -a Linux sd-29499 2.6.32-5-xen-amd64 #1 SMP Tue Mar 8 00:01:30 UTC 2011 x86_64 GNU/Linux I''m trying to install a Squeeze DomU but there is no network card, even during install wich doesn''t show any network card with lspci (but when I

Hi all, I ran into this error when I tried to create a new virtual environment using the xm create command... clever2:/etc/xen# xm create -c /etc/xen/xen1-config.sxp Using config file "/etc/xen/xen1-config.sxp". Error: ''features'' is an invalid keyword argument for this function clever2:/etc/xen# Here is my config file : clever2:/etc/xen# cat xen1-config.sxp

Hi, some more info which I collected during physically accessing the machine while rebooting. I was suprised that while it was not able to do anything it was not a ''static'' kernel panic, but the following text was scrolling continously thru the screen: """ ata3: port reset, p_is 1 is e pis 1 cmd c017 tf 50 ss 113 se 0 ata3: status=0x50 { DriveReady SeekComplete }

Hi. How I can see what happend in my domU??? dom0 Debian Lenny domU FreeBSD6.4 xen 3.2-1 -------- Xen 3.2-1 :/etc/xen# xm create tttt.cfg Using config file "./tttt.cfg". Started domain freebsd -------- /etc/xen# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 2969 4 r----- 48.0 freebsd

This patch adds an ACM hook into the network scripts (/etc/xen/scripts). It adds iptables rules that enforce mandatory access control on network packets exchanged between virtual interfaces. If ACM is active, this patch sets the default FORWARD policy in Dom0 to DROP and adds iptables ACCEPT rules between vifs that belong to domains that are permitted to share (determined by using the

Hi Lists, sorry for reposting this, but since no response has arrived so far and my time on this project is passing by I need to make a conclusion. Do I better use my DVR cards in dom0 or moving it to a separate physical machine rather than using them in a domU? Could someone shed light on why it is trickier to pass-thru one of these cards than any other pci devices? Do they try to read-write

Hi Lists, sorry for reposting this, but since no response has arrived so far and my time on this project is passing by I need to make a conclusion. Do I better use my DVR cards in dom0 or moving it to a separate physical machine rather than using them in a domU? Could someone shed light on why it is trickier to pass-thru one of these cards than any other pci devices? Do they try to read-write

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-4 Severity: normal Xen Networking[1] works by creating a new pair of virtual ethernet interfaces (vifN.M in dom0 and ethM in domU with id N) and connecting then by an internal "crossover ethernet cable". My understanding of the "internal crossover" thing is that networking statistics should be the same no matter if you measure

Hi, Firstly I apologise for the cross-post, however I don't expect to get as quick a response from the package maintainers as I do from the Debian community, and this issue affects a service that I've got scheduled to go live at midnight this evening. :( A recent update from xen-hypervisor-4.1-amd64 version 4.1.3-7, to version 4.1.3-8 on Debian Wheezy has caused all vm's on this host

Hi, Firstly I apologise for the cross-post, however I don't expect to get as quick a response from the package maintainers as I do from the Debian community, and this issue affects a service that I've got scheduled to go live at midnight this evening. :( A recent update from xen-hypervisor-4.1-amd64 version 4.1.3-7, to version 4.1.3-8 on Debian Wheezy has caused all vm's on this host

Hi, I''ve bit the bullet and gone with Xen, but I get some odd networking. Basically, this was the original idea. eth0 external eth1 internal create bridge br0 for eth0 create bridge br1 for eth1 Strip IP addresses for eth0 and eth1 and assign to br0 and br1 respectively. Worked great in a non-xen kernel under Fedora 8 in KVM/Qemu. Booting into Xen, my eth1 becomes eth2, I also get

I am running Xen on Debian wheezy. I switched from routed networking to bridged networking. Now I can''t seem to get eth0 to come up. When the network script tries to bring it up, it gets an error: RTNETLINK answers: File exists Any tips? details below brian root@trout:/etc/xen# egrep -v ''#|^ *$'' xend-config.sxp (network-script network-bridge) (vif-script vif-bridge)

Hello, I am having big problems with Xen virtual network interfaces. First I tried typical bridge support, no luck. The packets sent from dom0 to domU seemed to disappear somewhere. Then, to debug the problem I have set up a simple point-to-point link and still have the same problem. I am using Xen 3.0.4-1 and Linux 2.6.16.x in both dom0 and domU. I have tried kernel 2.6.16.35 and 2.6.16.41. I

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 =

Hi, I am running Xen 3.3.1 built from Source with Debian Lenny as the dom0. Everything works fine so far except pyGRUB. So, what I did was install CentOS (latest version ... 5.3 or something) using qemu to a LVM logical volume and from within CentOS I installed the Xen Kernel. Now pyGRUB shows me 3 grub entries: 1) CentOS (2.6.18-128.1.10.el5xen) <= xen hypervisor 2) CentOS