similar to: Backend device not found

hi all, When i tried to install debian as a new guest VM in paravirtualized mode on Xen the following error occurs. please help me to resolve the problem.. Unable to complete install ''<type ''exceptions.ValueError''> Invalid install location: Opening URL http://172.16.0.31:8088/debian1 failed.. Traceback (most recent call last):   File

I''m running Xen3 7775 with udev 073 (which was a PITA to get working, as the initrd I''ve been running for quite some time uses an older one -- but that''s an entirely different story). My dom0 is Gentoo-based. When I try to start a DomU, it times out waiting for hotplug-based notification, as per the following: DEBUG (DevController:69) Waiting for devices vif. DEBUG

I''m running Xen3 7775 with udev 073 (which was a PITA to get working, as the initrd I''ve been running for quite some time uses an older one -- but that''s an entirely different story). My dom0 is Gentoo-based. When I try to start a DomU, it times out waiting for hotplug-based notification, as per the following: DEBUG (DevController:69) Waiting for devices vif. DEBUG

Fasiha Ashraf --- On Sat, 22/8/09, Fasiha Ashraf <feehapk@yahoo.co.in> wrote: From: Fasiha Ashraf <feehapk@yahoo.co.in> Subject: Re: [Xen-users] my bootlog To: "Boris Derzhavets" <bderzhavets@yahoo.com> Date: Saturday, 22 August, 2009, 11:12 AM Please check what wrong here grub.conf        title Fedora (2.6.30-rc6-tip)         root (hd0,6)         kernel

Hi: I''m newbie to Xen. I''m using Suse as Dom0, and Debian5 as DomU. If no IP is specified, VM starts OK. Else, it fails and shows the following error: *Device* *0* (*vif*) *could* not be *connected*. *Hotplug* *scripts* not working. Googl''ing a lot bit I''ve seen this error is quite common, but I have found no solution. Any ideas? If you need any other

Hi All, I am working on creating storage driver domain with xen-4.3.0 . I am referring this - http://wiki.xen.org/wiki?title=Storage_driver_domains&oldid=9371 I have created Storage domain with xl utility of xen, then followed above wiki for rest of the steps, additionally I did install blktap-dkms package also- Following xen processes are running on Domain 0:

Hi All, I am working on creating storage driver domain with xen-4.3.0 . I am referring this - http://wiki.xen.org/wiki?title=Storage_driver_domains&oldid=9371 I have created Storage domain with xl utility of xen, then followed above wiki for rest of the steps, additionally I did install blktap-dkms package also- Following xen processes are running on Domain 0:

Hi there, I am getting very low throughput (around 0.29Mbps) while running netperf benchmark for guest to guest communication on a single physical host. To analyse where the time is spent in hypervisor I wanna use profiling. Please help me choosing good profiler according to my requirments. Should it be better in my case, Xentrace, gprof, xenoprof  or Oprofile. Is it possible to use some vtune

Hi there, I am getting very low throughput (around 0.29Mbps) while running netperf benchmark for guest to guest communication on a single physical host. To analyse where the time is spent in hypervisor I wanna use profiling. Please help me choosing good profiler according to my requirments. Should it be better in my case, Xentrace, gprof, xenoprof  or Oprofile. Is it possible to use some vtune

This is my install profile F11.install name="FC11-G1S2" memory=500 disk = [''phy:/dev/sda3,0,w'' ] vif = [ ''bridge=eth0'' ] vfb = [ ''type=vnc,vncunused=1''] kernel = "/etc/xen/vm/vmlinuz.1" ramdisk = "/etc/xen/vm/initrd.img.1" vcpus=1 on_reboot = ''restart'' on_crash = ''restart''

I have set-up xen on my Intel quad core server. Now running different experiment to measure network throughput in virtualized environment. these are some of the results: Netperf-4.5 results for inter-domain communication. Sr.No.              Client               Server               Time(sec)        Throughput(Mbps)    1                   Guest-1              Dom0                   

Hello, My name is Fermín Galán. I have started recently to use Xen (so please forgive me in advance if I''m too "newbie" :) and I''m facing my first problems... I''m trying to create a domU, but I''m getting an error: tornado:~# xm create test.cfg -c Using config file "/etc/xen/test.cfg". Error: Device 2049 (vbd) could not be connected.

HI there, I am using a Dell PowerEdge 2970 with following specs:2 x AMD Dual Core Opteron processors, 2GHz, 2 MB L2 Cache.8 GB RAM (4 x 2 GB)4 x 146 GB Hard DisksDual Port Gigabit Ethernet NIC10 Gbps PCI EthernetFedora 11 operating system installed.What I want here is Building and Installing Xen 4.3 in Fedora 11. for this I followed the following steps

[This email is either empty or too large to be displayed at this time]

I''m running SLES10 SP1 and have been using file:/ for my file-backed domUs. The domUs sit on a shared OCFS2 SAN-backed filesystem and are run on my three or four XEN servers. I''m having issues with the loopback devices not being released when the domUs shutdown or migrate, so I decided to switch over to tap:aio for my file-backed domUs. This isn''t working, either.

[This email is either empty or too large to be displayed at this time]

I want to check the speed like features of my Ethernet in dom0 and domUs. But in virtualized environment it gives strange output why is that so? how to check it otherwise? Non-virtualized FC11 [root@fasiha home]# ethtool eth0 Settings for eth0:     Supported ports: [ TP ]     Supported link modes:   10baseT/Half 10baseT/Full                             100baseT/Half 100baseT/Full    

I want to check the speed like features of my Ethernet in dom0 and domUs. But in virtualized environment it gives strange output why is that so? how to check it otherwise? Non-virtualized FC11 [root@fasiha home]# ethtool eth0 Settings for eth0:     Supported ports: [ TP ]     Supported link modes:   10baseT/Half 10baseT/Full                             100baseT/Half 100baseT/Full    

Folks, Xen 3.4.2 is the latest maintenance release in the 3.4 stable branch. There are a range of bug fixes since 3.4.1, and we recommend users to upgrade. The source repository can be downloaded from: http://xenbits.xensource.com/xen-3.4-testing.hg The release is tagged ''RELEASE-3.4.2''. Alternatively source tarballs can be downloaded from:

Folks, Xen 3.4.2 is the latest maintenance release in the 3.4 stable branch. There are a range of bug fixes since 3.4.1, and we recommend users to upgrade. The source repository can be downloaded from: http://xenbits.xensource.com/xen-3.4-testing.hg The release is tagged ''RELEASE-3.4.2''. Alternatively source tarballs can be downloaded from: