search for: 51714

...cal/domain/0/device-model/2 = "" (r0) /local/domain/0/device-model/2/state = "running" (r0) /local/domain/0/backend = "" (r0) /local/domain/0/backend/qdisk = "" (r0) /local/domain/0/backend/qdisk/2 = "" (r0) /local/domain/0/backend/qdisk/2/51714 = "" (n0,r2) /local/domain/0/backend/qdisk/2/51714/frontend = "/local/domain/2/device/vbd/51714" (n0,r2) /local/domain/0/backend/qdisk/2/51714/params = "aio:xen//domains/ fsb.t.org/disk.img" (n0,r2) /local/domain/0/backend/qdisk/2/51714/frontend-id = "2&quot...

...0s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... [ 270.576347] XENBUS: Timeout connecting to device: device/vbd/51714 (local state 3, remote state 2) [ 270.576524] Magic number: 1:252:3141 [ 270.576570] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 270.576698] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [ 270.576710] EDD information not available. [ 270.577319] Freeing unused kernel memor...

...0s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... [ 270.576347] XENBUS: Timeout connecting to device: device/vbd/51714 (local state 3, remote state 2) [ 270.576524] Magic number: 1:252:3141 [ 270.576570] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 270.576698] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [ 270.576710] EDD information not available. [ 270.577319] Freeing unused kernel memor...

...0af402bfeb98', 'bootable': 1, 'driver': 'paravirtualised', 'dev': 'xvda2', 'uname': 'drbd:abook-disk', 'mode': 'w'} [2011-10-29 21:03:49 26862] DEBUG (DevController:95) DevController: writing {'virtual-device': '51714', 'device-type': 'disk', 'protocol': 'x86_64-ab i', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/42/51714'} to /local/domain/42/device/vbd/51714. [2011-10-29 21:03:49 26862] DEBUG (DevCon...

...mmy-disk'', ''mode'': ''w'', ''backend'': ''0''} [2009-01-19 16:46:30 4612] DEBUG (DevController:117) DevController: writing {''backend-id'': ''0'', ''virtual-device'': ''51714'', ''device-type'': ''disk'', ''state'': ''1'', ''backend'': ''/local/domain/0/backend/vbd/1/51714''} to /local/domain/1/device/vbd/51714. [2009-01-19 16:46:30 4612] DEBUG (DevController:119) D...

...vbd/32/51713/hotplug-status. [2010-07-04 13:14:31 9855] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vbd/32/51713/hotplug-status. [2010-07-04 13:14:31 9855] DEBUG (DevController:642) hotplugStatusCallback 1. [2010-07-04 13:14:31 9855] DEBUG (DevController:144) Waiting for 51714. [2010-07-04 13:14:31 9855] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vbd/32/51714/hotplug-status. [2010-07-04 13:14:31 9855] DEBUG (DevController:642) hotplugStatusCallback 1. [2010-07-04 13:14:31 9855] DEBUG (DevController:139) Waiting for devices irq. [2010-07-04 13...

...2012-01-06 08:18:51 4348] DEBUG (DevController:642) hotplugStatusCallback 1. [2012-01-06 08:18:51 4348] DEBUG (DevController:139) Waiting for devices vscsi. [2012-01-06 08:18:51 4348] DEBUG (DevController:139) Waiting for devices vbd. [2012-01-06 08:18:51 4348] DEBUG (DevController:144) Waiting for 51714. [2012-01-06 08:18:51 4348] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vbd/7/51714/hotplug-status. [2012-01-06 08:18:51 4348] DEBUG (DevController:642) hotplugStatusCallback 1. [2012-01-06 08:18:51 4348] DEBUG (DevController:144) Waiting for 51713. [2012-01-06 08:18:51...

...e vbd [ 0.045069] xenbus_probe_device_type 1/7 51719 [ 0.045069] xenbus_probe_device_type 2/7 51718 [ 0.046084] xenbus_probe_device_type 3/7 51717 [ 0.046084] xenbus_probe_device_type 4/7 51716 [ 0.046084] xenbus_probe_device_type 5/7 51715 [ 0.046084] xenbus_probe_device_type 6/7 51714 [ 0.046084] xenbus_probe_device_type 7/7 51713 My domU configuration is the following : root = ''/dev/xvda2 ro'' disk = [ ''phy:/dev/vg/test-home,xvda7,w'', ''phy:/dev/vg/test-data,xvda6,w'',...

...bian-prueba:~# but into this guest domain "debian-prueba" when exec lsusb command get nothing, see below: root@debian-prueba:~# lsusb root@debian-prueba:~# at dmesg of this PV domain, can watch only this info about usb and xen: [ 0.316730] XENBUS: Device with no driver: device/vbd/51714 [ 0.316740] XENBUS: Device with no driver: device/vbd/51713 [ 0.316749] XENBUS: Device with no driver: device/vif/0 [ 0.316757] XENBUS: Device with no driver: device/vusb/0 [ 0.316766] XENBUS: Device with no driver: device/console/0 [ 0.316796] /build/buildd-linux-2.6_2.6.32-35-amd64...

Hi, I have a problem with a dom0 which is unable to launch my domU : all my dom0 are Debian Lenny amd64 with Debian kernel 2.6.26-2-xen-amd64 and xen-hypervisor-3.2-1-amd64. Then all domU (PV) are Debian Lenny amd64 too, with vanilla kernel 2.6.29.6. So, this new dom0 can''t launch any domU which are working on an other dom0. Software is same on both dom0, and hardware is near the

...rie-DHCP.cfg Using config file "/etc/xen/Marie-DHCP.cfg". Error: Device 0 (vif) could not be connected. Hotplug scripts not working. >>>> I watched in the hotplug.log root@debian:/dev# more /var/log/xen/xen-hotplug.log xenstore-read: couldn''t read path backend/vbd/2/51714/params xenstore-write: could not write path backend/vbd/2/51714/hotplug-error xenstore-read: couldn''t read path backend/vbd/2/51713/params xenstore-write: could not write path backend/vbd/2/51714/hotplug-error xenstore-write: could not write path backend/vbd/2/51714/hotplug-error xenstore-...

...0.219530] Bridge firewalling registered [ 0.219536] Ebtables v2.0 registered [ 0.219550] Registering the dns_resolver key type [ 0.219736] registered taskstats version 1 [ 0.219748] XENBUS: Device with no driver: device/vbd/51713 [ 0.219752] XENBUS: Device with no driver: device/vbd/51714 [ 0.219757] XENBUS: Device with no driver: device/vif/0 [ 0.219789] Magic number: 1:252:3141 [ 0.219840] console [netcon0] enabled [ 0.219844] netconsole: network logging started [ 0.219848] saa7134 ALSA driver for DMA sound loaded [ 0.219852] saa7134 ALSA: no saa7134 cards foun...

hi, i''m trying move from file: based disk to tap:aio but things don''t work i have centos4 dom0 with centos4 domU xen 3.0.4-testing changeset: 13138:d401cb96d8a0 self compiled [root@xen linux-2.6.16.38-xen]# grep XEN_BLKDEV_TAP .config CONFIG_XEN_BLKDEV_TAP=m config disk = [ ''file:/var/lib/xen/test.img,hda1,w'',

...xen:vbd'' [69] terminated by signal 9 (Killed) udevd[61]: timeout: killing ''/sbin/modprobe -b xen:vbd'' [70] [ 300.244208] XENBUS: Timeout connecting to device: device/vbd/51713 (local state 3, remote state 1) [ 300.244309] XENBUS: Timeout connecting to device: device/vbd/51714 (local state 3, remote state 1) udevd[61]: ''/sbin/modprobe -b xen:vbd'' [70] terminated by signal 9 (Killed) ... [ 300.290933] Fusion MPT base driver 3.04.18 [ 300.290943] Copyright (c) 1999-2008 LSI Corporation [ 300.310304] SCSI subsystem initialized [ 300.323846] loop: modul...

Hello! I was asking for help on the Freenode channel, and I was pointed here. I have a situation where, using xl, I can create a functional PV domU, with or without pv-grub, but I cannot access the console. Firing up xend and using xm works without trouble. Since xend and company is being deprecated, I would like to transition to using the xl toolstack. The system is an Arch Linux system

...r all mice md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 TCP bic registered Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 XENBUS: Device with no driver: device/vbd/51713 XENBUS: Device with no driver: device/vbd/51714 XENBUS: Device with no driver: device/vif/0 Write protecting the kernel read-only data: 439k Red Hat nash version 5.1.19.6 starting Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Loading xenblk.ko modul...

Hi, Recently I have installed Debian Lenny on two different machines (different ram size, disks, Xeon dual and quad core, filesystems both xfs and ext3, etc). Packages versions: Dom0: ii libc6-xen 2.7-18lenny4 GNU C Library: Shared libraries [Xen version] ii libxenstore3.0 3.2.1-2 Xenstore communications

Using 10G interfaces on kernel 3.2 + xen 4.1.2 we''re seeing: dom0 ~9.2Gbps domU *~2.5Gbps* dmesg on domU: XENBUS: Device with no driver: device/vif/0 Is this normal? Thanks Kristoffer -- View this message in context: http://xen.1045712.n5.nabble.com/10gig-in-domU-tp5634876p5634876.html Sent from the Xen - User mailing list archive at Nabble.com.

...12/params xenstore-read: couldn''t read path backend/tap/0/51712/params Nothing to flush. Nothing to flush. Nothing to flush. Nothing to flush. Nothing to flush. Nothing to flush. Nothing to flush. Nothing to flush. Nothing to flush. xenstore-read: couldn''t read path backend/vbd/13/51714/node Nothing to flush. Nothing to flush. Nothing to flush. Nothing to flush. Nothing to flush. Nothing to flush. Nothing to flush. stat: cannot stat `/tmp/maquina/domains/prueba2/disk.img'': No such file or directory stat: cannot stat `/tmp/maquina/domains/prueba2/swap.img'': No suc...

....127047] mip6: Mobile IPv6 [ 1.127052] NET: Registered protocol family 17 [ 1.127066] mpls_gso: MPLS GSO support [ 1.127070] mce: Unable to init device /dev/mcelog (rc: -5) [ 1.127161] registered taskstats version 1 [ 1.127195] xenbus_probe_frontend: Device with no driver: device/vbd/51714 [ 1.127198] xenbus_probe_frontend: Device with no driver: device/vbd/51713 [ 1.127200] xenbus_probe_frontend: Device with no driver: device/vif/0 [ 1.127220] /build/linux-RGM_Ed/linux-3.16.7-ckt9/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 1.127569] Freeing unused kernel m...