search for: 51713

...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.588319] XENBUS: Timeout connecting to device: device/vbd/51713 (local state 3, remote state 2) [ 270.588492] Magic number: 1:252:3141 [ 270.588543] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 270.588716] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [ 270.588730] EDD information not available. [ 270.589358] 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.588319] XENBUS: Timeout connecting to device: device/vbd/51713 (local state 3, remote state 2) [ 270.588492] Magic number: 1:252:3141 [ 270.588543] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 270.588716] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [ 270.588730] EDD information not available. [ 270.589358] Freeing unused kernel memor...

..."0" (n0,r2) /local/domain/0/backend/qdisk/2/51714/sector-size = "512" (n0,r2) /local/domain/0/backend/qdisk/2/51714/sectors = "2097152" (n0,r2) /local/domain/0/backend/qdisk/2/51714/hotplug-status = "connected" (n0,r2) /local/domain/0/backend/qdisk/2/51713 = "" (n0,r2) /local/domain/0/backend/qdisk/2/51713/frontend = "/local/domain/2/device/vbd/51713" (n0,r2) /local/domain/0/backend/qdisk/2/51713/params = "aio:xen//domains/ fsb.t.org/swap.img" (n0,r2) /local/domain/0/backend/qdisk/2/51713/frontend-id = "2&quot...

...64/0. [2008-09-16 07:25:19 xend 4079] DEBUG (blkif:24) exception looking up device number for xvda1: [Errno 2] No such file or directory: ''/dev/xvda1'' [2008-09-16 07:25:19 xend 4079] DEBUG (DevController:110) DevController: writing {''virtual-devi ce'': ''51713'', ''device-type'': ''disk'', ''protocol'': ''x86_64-abi'', ''backend-id'': ''0'', ''state'': ''1'', ''backend'': ''/local/domain/0/backe...

...not working. [2006-01-26 21:02:32 xend] DEBUG (blkif:24) exception looking up device number for xvda1: [Errno 2] No such file or directory : ''/dev/xvda1'' [2006-01-26 21:02:32 xend] DEBUG (DevController:104) DevController: writing {''virtual-device'': ''51713'', ''backend-id'': ''0'', ''s tate'': ''1'', ''backend'': ''/local/domain/0/backend/vbd/30/51713''} to /local/domain/30/device/vbd/51713. [2006-01-26 21:02:32 xend] DEBUG (DevController:106) Dev...

...12 0.0 1048576 6.3 2097152 12.5 2 1 1573 8 2 0 2433 6688 109973 88770 0 For the red part, I need to change the size to MB or KB. Just now, I check the xentop code, xentop gets the related information from /sys/devices/vbd-29-51713/statistics/rd_sect or /sys/devices/vbd-29-51713/statistics/wr_sect files. I do not know how to change these number to MB or KB. Does anybody know how to do that? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

...aravirtualised'', ''dev'': ''xvda1'', ''uname'': '''', ''mode'': ''w''} [2009-08-01 12:32:21 3310] DEBUG (DevController:118) DevController: writing {''virtual-device'': ''51713'', ''device-type'': ''disk'', ''protocol'': ''x86_64-abi'', ''backend-id'': ''0'', ''state'': ''1'', ''backend'': ''/local/domain/0/backe...

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

...exception looking up device number for xvda1: [Errno 2] No such file or directory: ''/dev/xvda1'' [2008-09-18 15:51:11 xend 3331] DEBUG (DevController:110) DevController: writing {''backend-id'': ''0'', ''virtual-device'': ''51713'', ''device-type'': ''disk'', ''state'': ''1'', ''backend'': ''/local/domain/0/backend/tap/10/51713''} to /local/domain/10/device/vbd/51713. ... [2008-09-18 15:51:12 xend 3331] DEBUG (XendCheck...

...console. [2010-07-04 13:14:30 9855] DEBUG (DevController:144) Waiting for 0. [2010-07-04 13:14:30 9855] DEBUG (DevController:139) Waiting for devices vscsi. [2010-07-04 13:14:30 9855] DEBUG (DevController:139) Waiting for devices vbd. [2010-07-04 13:14:30 9855] DEBUG (DevController:144) Waiting for 51713. [2010-07-04 13:14:30 9855] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/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 (DevContr...

...gistered [ 0.219513] NET: Registered protocol family 17 [ 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...

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

...trouble with block-attach: $ dd if=/dev/zero of=foo.img bs=1024k seek=64 count=0 0+0 records in 0+0 records out 0 bytes (0 B) copied, 1.6493e-05 s, 0.0 kB/s $ sudo xm block-attach 0 file://home/dank/lvmstuff/foo.img /dev/xvda1 w 0 $ sudo xm block-list 0 Vdev BE handle state evt-ch ring-ref BE-path 51713 0 0 1 -1 -1 /local/domain/0/backend/vbd/0/51713 $ sudo mkfs.ntfs /dev/xvda1 Failed to access ''/dev/xvda1'': No such file or directory The device doesn''t exist; did you specify it correctly? Was I supposed to create /dev/xvda1 myself? I thought Xen did that. Thanks, Dan...

...ch.xvda'', ''mode'': ''w'', ''backend'': ''0''} [2007-08-13 17:32:21 3195] DEBUG (DevController:115) DevController: writing {''backend-id'': ''0'', ''virtual-device'': ''51713'', ''device-type'': ''disk'', ''state'': ''1'', ''backend'': ''/local/domain/0/backend/vbd/2/51713''} to /local/domain/2/device/vbd/51713. [2007-08-13 17:32:21 3195] DEBUG (DevController:117)...

...C can not be found. As I type the command "lspci" in RHEL4.5 domU, it returned: pcilib: Cannot open /proc/bus/pci lspci: Cannot find any working access method. And I found the three lines in "dmesg" output: XENBUS: Device with no drvier: device/vbd/51713 XENBUS: Device with no driver: device/pci/0 XENBUS: Device with no driver: device/vif/0 After that, I tried to rebuild redhat4.5''s kernel, and set: CONFIG_PCI=y CONFIG_XEN_PCIDEV_FRONTEND=y in the config file "kernel-2.6.9-i686-xenU.config"....

...age file mounted via tap:aio in dom0 (as a precursor, or course, to using it for rootfs in a domU). So: [root@dom0-0-50-45-5d-59-aa tmp]# xm block-attach 0 tap:aio:/tmp/sparse.img /dev/xvda1 w 0 ... [root@dom0-0-50-45-5d-59-aa tmp]# xm block-list 0 Vdev BE handle state evt-ch ring-ref BE-path 51713 0 0 3 15 8 /local/domain/0/backend/tap/0/51713 But [root@dom0-0-50-45-5d-59-aa tmp]# mount /dev/xvda1 /mnt/tapaio mount: you must specify the filesystem type [root@dom0-0-50-45-5d-59-aa tmp]# mount -t ext3 /dev/xvda1 /mnt/tapaio mount: special device /dev/xvda1 does not exis...

I have installed Kubuntu 8.04 with xen 3.2 on kernel 2.6.24-16-xen on amd64 hardware. Then I have created a new domU with xen-tools. The domU is using loopback-images. When I try to start the domU it ends with this: Error: Device 51713 (vbd) could not be connected. losetup /dev/loop0 /home/xen/domains/xx/swap.img failed. loopx is raised by 2 for every try. It looks like a classic and simple problem, but I cannot find where to look for a aolutiuon. -- Morten Christensen _______________________________________________ Xen-user...

...oller: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 4348] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vbd/7/51713/hotplug-status. [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 ioports. [2012-01-06...

...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'', ''phy:/dev/vg/test-tmp,xvda5...

...quot; 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-aZSlKL/linux-2.6-2.6.32/debian/build/source_amd64_xen/drivers/...