similar to: Re: xen_blk timeout connecting to devic

After upgrading to a recent snapshot (6831) I am unable to boot a guest - I get the following messages when booting the guest domain: Xen_blk: Initialising virtual block device driver Xen_blk: Timeout connecting to device! ... VFS: Cannot open root device "sda1" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount

We''ve been noticing a lot of these errors when booting VMs since we moved to 3.0.3 - I''ve traced this to the hotplug scripts in Dom0 taking >10s to run to completion and specifically the vif-bridge script taking >=9s to plug the vif into the s/w bridge on occasion - was wondering if anyone has any insight into why it might take this long. I added some instrumentation to

Source: xen Version: 4.1.4-2 Severity: important Hi, using RUN+="socket:" in udev rules files has been deprecated for a while. In udev 183 support for that has been removed [1] >From the NEWS file: * udev: RUN+="socket:..." and udev_monitor_new_from_socket() is no longer supported. udev_monitor_new_from_netlink() needs to be used to subscribe to events.

tags 671018 +patch thanks This issue has been fixed upstream for 4.2 by using the same hotplug scripts for tap devices as for vif devices rather than using a special qemu-ifup script. I don't think this is an appropriate thing to backport to 4.1 for wheezy so therefore I think the right fix is as Pierre suggests to set the MAC address in the qemu-ifup script. In terms of a patch to the

Searching the archives and web i''ve learned that this error has occured for other users as well. I already did quite a bit of debugging but can''t figure out what the problem might be. I''m running Xen unstable (changeset 8002) on an AMD64 server (rented from 1&1). I''ve patched the 2.6.12.6 kernel with a custom patch to get network and disk adapter running,

Hi Maxime, Quoting Maxime Accadia (2020-02-03 14:20:47) > Hi, > > We have a VM with several USB devices attached. Everything works well, > but sometimes, after a reboot of the host, some usb device get a > different bus/device number and that prevent the reboot of the VM : > ... > Any idea on how to handle this case ? > > We were thinking about using udev, but it

Package: xen-utils-common Version: 3.4.2-4 Severity: important File: /usr/lib/xen-common/bin/xen-utils-wrapper xm invoke vtpm-common.sh from /etc/xen/hotplug, wich one call gawk, but gawk is not listed as dependence for xen packages. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux

I get the error while starting hvm doms. Any workarounds... suggestions.. Thanks /Jd Some thiings that might be useful are cut-pasted below. ifconfig -a udevmonitor output (as suggested in prev posts) qemu-dm log xend.log xend-debug does not seem to have anything interesting. ifconfig -a =========== eth0 Link encap:Ethernet HWaddr 00:0F:EA:53:5C:79 inet addr:192.168.12.103

Package: xen-utils-common Version: 3.4.2-3 Severity: minor Hi, I've just noticed that the xen-utils-common package instals the file xen-backend.rules both under /etc/udev/xen-backend.rules and /lib/udev/rules.d/xen-backend.rules I think the flormer is useless and is installed there by mistake. Kind Regards, Marco -- System Information: Debian Release: squeeze/sid APT prefers unstable

Package: xen-utils-3.1-1 Version: 3.1.0-2 Severity: wishlist File: xen-utils-3.1 qemu-dm currently is built with OSS support. This occours /dev/dsp locking once a HVM guest is started. If you have /dev/dsp already open by other applications, sound won't work within guest VM, otherwise qemu-dm will lock and won't be available to the host OS. Would be nice to see qemu-dm built with alsa

Package: xen-utils-unstable Version: 3.3-unstable+hg17961-1 Severity: important if I try to start or restart xend, I get this errors: /etc/init.d/xend restart Restarting XEN control daemon: xendTraceback (most recent call last): File "/usr/lib/xen-unstable/bin/xend", line 146, in <module> sys.exit(main()) File "/usr/lib/xen-unstable/bin/xend", line 123, in main

Package: xen-utils-3.0-unstable-1 Version: 3.0-unstable+hg11561-1 Severity: grave Justification: renders package unusable with the recent unstable kernel, the evtchn device should be created with major/minor 10, 63. Instead, it's being created with 10, 201. If fixed manually, xenstored will re-create it with the wrong minor number. This causes Xen to be entirely unusable, as xenstored is

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

Hi Kiko, 2006/2/25, Kiko Piris <menorqui@pirispons.net>: > Package: nut-usb > Version: 2.0.3-1 > Severity: important > > > When newhidups loses comunication with ups (G), it dies when trying to > reconnect with the error: > > *** glibc detected *** double free or corruption (fasttop): 0x08068268 *** > > Following is a copy&paste of the last lines of

Package: xen-utils-3.0 Version: 3.0.2+hg9697-1 Severity: normal On unstable, xen-utils-3.0 can't be installed, due to dependencies. Reproducable: yes. Just install unstable and try to install xen-utils-3.0. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash

Package: xen-utils-unstable Version: 3.3-unstable+hg17192-1 Severity: important Tags: patch In tools/firmware/Makefile, INST_DIR is $(DESTDIR)/usr/$(PREFIX)/boot but $(PREFIX) is empty. hvmloader doesn't get installed. diff -ru xen-unstable-3.3-unstable+hg17192.orig/debian/patches/tools-prefix.diff xen-unstable-3.3-unstable+hg17192/debian/patches/tools-prefix.diff ---

Package: xen-hypervisor-4.1-i386 Version: 4.1.1-1 Severity: important Tags: wheezy I cannot boot a domU with networking after installing the package. root at topsail:~# xm create /etc/xen/udevtest.cfg -c root at topsail:~# Error: Device 0 (vif) could not be connected. Hotplug scripts not working. [2011-08-03 15:56:53 4411] DEBUG (DevController:139) Waiting for devices tap2. [2011-08-03

Package: xen-utils-3.0 Version: 3.0.2+hg9681-1 Severity: normal I get this error with xen after some debug cycles, start / stopping nodes. I found this fix on the net, which fixes the problem: http://lists.xensource.com/archives/html/xen-users/2006-04/msg01070.html in /etc/init.d/xen: start) + modprobe loop max_loop=64 + cd /dev && /dev/MAKEDEV loop xend start

> -----Original Message----- > From: Ewan Mellor [mailto:ewan@xensource.com] > Sent: Tuesday, December 06, 2005 5:25 AM > To: Dave Thompson (davetho) > Cc: Xen Mailing List > Subject: Re: [Xen-devel] Hotplug scripts not working... > xen/ia64 domU stoppedworking > > On Mon, Dec 05, 2005 at 03:03:54PM -0500, Dave Thompson > (davetho) wrote: > > > >