similar to: Bug#377996: Error: Device 2049 (vbd) could not be connected. Backend

Package: xen-utils-3.0 Version: 3.0.2+hg9681-1 Severity: important When trying to install xen-utils, I get the following message: Unpacking xen-utils-3.0 (from .../xen-utils-3.0_3.0.2+hg9681-1_i386.deb) ... Setting up xen-utils-3.0 (3.0.2+hg9681-1) ... Starting XEN: invoke-rc.d: initscript xend, action "start" failed. dpkg: error processing xen-utils-3.0 (--configure): subprocess

Package: xen-3.0 Version: 3.0.2+hg9681-1 Your package fails to build with GCC 4.2. Version 4.2 has not been released yet but I'm building with a snapshot in order to find errors and give people an advance warning. The bug below is in your package though and not because I'm using a snapshot of the compiler so please take a look at it. You can reproduce this with the gcc-snapshot

FYI: The status of the xen-3.0 source package in Debian's testing distribution has changed. Previous version: 3.0.2+hg9656-1 Current version: 3.0.2+hg9681-1 -- This email is automatically generated; henning@makholm.net is responsible. See http://people.debian.org/~henning/trille/ for more information.

Package: xen-utils-3.0 Version: 3.0.2+hg9681-1 Severity: normal In the tls section: it fails to mention the better solution (apt-get install libc6-xen) In the kernel section: where it says "for now we cannot provide precompiled Linux kernels with the xen patch applied", that's not true either. apt-get install linux-image-2.6-xen-k7 or some such. -- System Information: Debian

Full_Name: Craig A. McKinstry Version: 1.0.0 OS: WinNT4.0 and Win98 Submission from: (NULL) (192.101.100.130) When creating a multi-panel graphic, the command par(mfg=c(i,j,r,c)) is supposed to allow the user free movement between graphics panels to develop each panel separately. This works for the first invocation of par(mfg=c()) and for the first panel panel specified, but not for subsequent

Package: xen-utils-3.0 Version: 3.0.2+hg9681-1 Severity: minor Here comes another bug report :) >From README.Debian: |* About networking: | | By default Xen modifies your networking configuration, creating a bridge. | To avoid breaking a machine's connection to the network the debian package | doesn't touch the network configuration unless requested. On the other hand | xen

Package: xen-utils-3.0 Version: 3.0.2+hg9681-0bpo1 Severity: important Disclaimer: I'm using the packages from www.backports.org here (in the box where the problem manifested), but I've seen that it happens too with the packages straight from sid. When I installed the packages for Xen and created a domU ("chen.cfg"), it couldn't be brougth up. The error that was displayed

Hi, I've downloaded and installed the Xen packages from backports.org in a box with sarge, and it doesn't work. That's the short story. Now the long one :-) The problem is that I can't bring up the domUs. This is the error displayed when I try: ~# xm create -c chen.cfg Using config file "/etc/xen/chen.cfg". Error: Device 0 (vif) could not be connected. Hotplug

Hi, i have seen a post with the same title, but didn''t help a lot -it mentioned, that the image was for LVM, which i don''t think is my case. I downloaded the debian31 image from http://jailtime.org. Initially, i had some problems and changed the configuration file a little. Here it is now: ----------- kernel = "/boot/vmlinuz-2.6-xenU" memory = 256 name =

Hi all When I have a domU that resides in the auto directory I get ''Error: Device 2049 (vbd) could not be connected'' and the domain starts in a paused mode. Shutting it down and restarting has the same effect. Following is some output from the xm log and an attempted restart. Directly after dom0 reboot: xen0:/etc/xen/scripts # xm list Name ID

Hello! This might be a FAQ, but I didn't manage to find an answer somewhere: why doesn't the linux-image-2.6.16-2-xen-686 (at least that one; that's the one I installed) create a accompanying initrd.img, but the user has to do it himself? (Like me, having troubles with the version of initramfs-tools from testing, resolved by upgrading that one to unstable's version.) Also, why

Hi, have a debian 5.0 with all patches and xen 4.3.1 (debian repo) installed. If I use a VM with paravirtualizing it works fine. But a full virtualized image doesn''t boot. Message: ---8<--- # xm create deb50.cfg: Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. ---8<--- That is my deb50.cfg ---8<--- # Debian 5.0 import os, re arch = os.uname()[4]

FYI: The status of the xen-3.0 source package in Debian's testing distribution has changed. Previous version: 3.0.2+hg9681-1 Current version: 3.0.2+hg9697-1 -- This email is automatically generated; henning@makholm.net is responsible. See http://people.debian.org/~henning/trille/ for more information.

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.

Package: xen-utils-3.0 Severity: wishlist Please include support for HVM-based guests. This allows hardware virtualization on systems with Intel's chips with VT (IE, Pentium D 930), and AMD's future chips with Pacifica. HVM allows you to run unmodified operating systems under Xen, such as Windows XP/2003. The following files are needed: /usr/lib/xen/bin/qemu-dm

problem in starting xend I tried to install xen, but got some errors when starting xend. as I logged in and tried to start xend (/etc/init.d/xend start). I just got six-seven dot (.) printed out, then it stops. I looked more closely and found that xend could not start. then I looked at /var/log/xend-debug.log. here is the last few lines: ^^^    Exception starting Xend: no element found:

Hi all, got this every time: Error: Device 5632 (vbd) could not be connected. Backend device not found. didn''t have any problem in b95 Any idea? thanks Philip xm info host : snv release : 5.11 version : snv_97 machine : i86pc nr_cpus : 2 nr_nodes : 1 sockets_per_node : 1

After a few times of building xen by source, I can''t start domU anyway. I tried "yum erase xen kernel-xen" and "yum install xen kernel-xen" again, but the problem is still exist. There are xenstore-write errors in /var/log/xen/xen-hotplug.log: xenstore-write: could not write path backend/vbd/1/2050/hotplug-error xenstore-write: could not write path

I sent before few days. However, anyone did not comments. So, I resend this patch series. I hope to response for this patch series. This patch series provides the function to display VBD information through xentop. VBD information will be possible to get through sysfs which is locale in /sys/devices/xen-backed/vbd-x-xxxx, by previous patch. In this patch series, libxenstat collects these

I''m trying to add vbd resize to GPLPV, but it doesn''t seem to work: xm block-attach w2k3test32 phy:/dev/vg-xen/virt-test-0 hdb w xenstore-read /local/domain/0/backend/vbd/377/832/sectors =44056576 lvextend --size=+1M /dev/vg-xen/virt-test-0 xenstore-read /local/domain/0/backend/vbd/377/832/sectors =44056576 The xenstore backend isn''t updated to reflect the new size