search for: 51712

...nd the disk write throughput is really slow, inferior to 0.5MB/s. I''m trying to install a Debian PV there, and after more than 3 hours it is still installing the base system. I''ve looked at the xenstore backend entries, and everything looks fine: /local/domain/0/backend/qdisk/21/51712/frontend = "/local/domain/21/device/vbd/51712" (n0,r21) /local/domain/0/backend/qdisk/21/51712/params = "aio:/hdd/vm/servlet/servlet.img" (n0,r21) /local/domain/0/backend/qdisk/21/51712/frontend-id = "21" (n0,r21) /local/domain/0/backend/qdisk/21/51712/online = &...

...|cvt-xh4|0 thread_zero|dbsync (update_env) D:634f731b810a|dbsync] killing umanaged domain: 4e118da2-8485-23c9-de75-a6c6862df33c [20101026T14:50:09.640Z|debug|cvt-xh4|0 thread_zero|dbsync (update_env) D:634f731b810a|xenops] Domain.destroy: all known devices = [ frontend (domid=369 | kind=vbd | devid=51712); backend (domid=0 | kind=tap | devid=51712); frontend (domid=369 | kind=vif | devid=0); backend (domid=0 | kind=vif | devid=0) ] [20101026T14:50:09.640Z|debug|cvt-xh4|0 thread_zero|dbsync (update_env) D:634f731b810a|xenops] Domain.destroy calling Xc.domain_destroy (domid 369) [20101026T14:50:09.68...

...ts not works at all. This config works : disk = [ 'phy:/dev/drbd/by-res/ads-disk,xvda,w' ] But his one doesn't work at all : disk = [ 'drbd:ads-disk,xvda,w' ] I obtain this error : # xm create ads.cfg Using config file "/etc/xen/ads.cfg". Error: Device 51712 (vbd) could not be connected. Hotplug scripts not working. and from logs : [2011-01-23 09:41:19 2112] INFO (XendDomainInfo:2367) createDevice: vbd : {'uuid': '133a116c-4aee-f8e1-2e51-f4a66b440d77', 'bootable': 1, 'driver': 'paravirtualised', 'dev': &...

...= '512' disk = [ 'file:/home/lindi-sudo/squeeze64/disk.img,xvda,w' ] EOF 2) xm create -c config Expected results: 2) the domain boots Actual results: 2) pygrub shows "Debian GNU/Linux, with Linux 2.6.32-5-amd64" correctly but after a long timeout it prints Error: Device 51712 (vbd) could not be connected. Hotplug scripts not working. and exits. More info: 1) the same configuration and image boot on a different amd64 squeeze system. 2) sudo udevadm monitor does not print anything on the failing system but prints KERNEL[1313565376.463324] add /devices/vbd-28-51712...

...aise XendError("%s failed" % string.join(cmd)) XendError: /usr/lib64/xen/bin/xc_save 22 3 0 0 1 failed [2009-06-21 11:34:44 xend.XendDomainInfo 4686] DEBUG (XendDomainInfo:1669) XendDomainInfo.resumeDomain(3) [2009-06-21 11:34:44 xend.XendDomainInfo 4686] INFO (XendDomainInfo:1790) Dev 51712 still active, looping... [2009-06-21 11:34:44 xend.XendDomainInfo 4686] INFO (XendDomainInfo:1790) Dev 51712 still active, looping... [2009-06-21 11:34:44 xend.XendDomainInfo 4686] INFO (XendDomainInfo:1790) Dev 51712 still active, looping... [2009-06-21 11:34:44 xend.XendDomainInfo 4686] INFO (...

...verbose output when running a block-prefix script. Other than xend.log. To be more specific I''d like to use bash -x to see why I''m running into the following error: > # xm create -c host.cfg > Using config file "host.cfg". > aa:bb:cc:dd:ee:ff > Error: Device 51712 (vbd) could not be connected. Hotplug scripts not working. However xm seems to disregard any output from the block-prefix script. xend.log hangs a few minutes on the following lines: > [2011-05-31 14:28:41 1894] DEBUG (XendDomainInfo:1286) XendDomainInfo.destroyDevice: deviceClass = vbd, devic...

...s, platform-pci. I used Xen 4.0.2-rc1-pre and a DomU is a ubuntu 10.04 and I try with ubuntu 10.10. In boot I receive error "Cannot find a root partition /dev/xvda2" and a prompt (initramfs) appear. In dmesg (initramfs) appear: blkfront: xvda: barriers enabled (tag) xvda: xvda1 vbd vbd-51712: 16 xlvbd_add at /local/domain/0/backend/vbd/470/51712 I try to create n initramfs, with any modules and the DomU dont boot. I forgot something? Can someone help me? Thanks for any help. -- Roberto Scudeller Especialista Linux/Unix _______________________________________________ Xen-users...

...s, platform-pci. I used Xen 4.0.2-rc1-pre and a DomU is a ubuntu 10.04 and I try with ubuntu 10.10. In boot I receive error "Cannot find a root partition /dev/xvda2" and a prompt (initramfs) appear. In dmesg (initramfs) appear: blkfront: xvda: barriers enabled (tag) xvda: xvda1 vbd vbd-51712: 16 xlvbd_add at /local/domain/0/backend/vbd/470/51712 I try to create n initramfs, with any modules and the DomU dont boot. I forgot something? Can someone help me? Thanks for any help. -- Roberto Scudeller Especialista Linux/Unix _______________________________________________ Xen-users...

...cdc-9e14-5223-3ba2e6da4f47''} [2012-10-25 17:50:39 6523] DEBUG (DevController:63) 12345 DevController:createDevice [2012-10-25 17:50:39 6523] DEBUG (DevController:96) DevController: writing {''backend-id'': ''0'', ''virtual-device'': ''51712'', ''device-type'': ''disk'', ''state'': ''1'', ''backend'': ''/local/domain/0/backend/vbd/5/51712''} to /local/domain/5/device/vbd/51712. [2012-10-25 17:50:39 6523] DEBUG (DevController:98) DevC...

...ord "tap-" in the directory name is sufficient to distinguish VBD types. Therefore, it is better to remove the prefix "tap_" in sysfs entries of blktap. For example, currently sysfs entries are named as follows. [root@xenmachine1 ~]# ls /sys/devices/xen-backend/vbd-1-51712/statistics/ br_req oo_req rd_req rd_sect wr_req wr_sect [root@xenmachine1 ~]# ls /sys/devices/xen-backend/tap-2-51712/statistics/ tap_oo_req tap_rd_req tap_rd_sect tap_wr_req tap_wr_sect After applying these patches, names of sysfs entries are changed as follows. [root@...

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

Hi all, Today I got problem below and my domU become unresponsive and I should restart the pc to make it running properly again. [ 240.172092] INFO: task kworker/u:0:5 blocked for more than 120 seconds. [ 240.172110] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 240.172376] INFO: task jbd2/xvda1-8:153 blocked for more than 120 seconds. [ 240.172388]

...47} to /local/domain/0/backend/vkbd/6/0. [2007-12-13 17:26:20 xend 8789] DEBUG (blkif:24) exception looking up device number for xvda: [Errno 2] No such file or directory: \047/dev/xvda\047 [2007-12-13 17:26:20 xend 8789] DEBUG (DevController:110) DevController: writing {\047virtual-device\047: \04751712\047, \047device-type\047: \047disk\047, \047protocol\047: \047x86_64-abi\047, \047backend-id\047: \0470\047, \047state\047: \0471\047, \047backend\047: \047/local/domain/0/backend/tap/6/51712\047} to /local/domain/6/device/vbd/51712. [2007-12-13 17:26:20 xend 8789] DEBUG (DevController:112) DevCont...

Hi... I have had a problem when I am going to detach one specific LVM partitions of Xen, so I have been trying xm destroy <domain>, lvchange -an <lvm_partition>, lvremove -f.... So I haven''t had sucess. I restarted the server with init 1 yet and nothing... I have seem two specific process started xenwatch and xenbus, but I am not sure if this processes have some action over

...#39;store/port': '1'} [2008-03-24 18:33:29 xend 19801] DEBUG (blkif:24) exception looking up device number for xvda: [Errno 2] No such file or directory: '/dev/xvda' [2008-03-24 18:33:29 xend 19801] DEBUG (DevController:110) DevController: writing {'virtual-device': '51712', 'device-type': 'disk', 'protocol': 'x86_32-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/1/51712'} to /local/domain/1/device/vbd/51712. [2008-03-24 18:33:29 xend 19801] DEBUG (DevC...

..... xe vm-start uuid=... Got following error message: The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: another frontend device is already connected to this domain (frontend (domid=0 | kind=vbd | devid=51712); backend (domid=0 | kind=tap | devid=51712)) If I recreate VBD, it seems fine but say usual error about ''non bootable'' (as if I run installation once and stops it). Main concern - first error message? What it is? And how can I debug i xensource.log is clear: [20100829T16:31:5...

Hi, I have three Xen hosts running Xen 4.0.2 (OpenSuSE 11.4 based). I also have one ''NFS'' server with an NFS export holding VM images and configuration files. Each host has a dedicated LAN link directly to the NFS server. I have another separated NFS export for VM locking (but I had the same issues before). When I attempt to live migrate a VM, it *looks''*like

...fully. Xenbus connect timeout, kernel panic. The following is messages that boot process: netfront: Initialising virtual ethernet driver. netfront: device eth0 has copying receive path. Loading xenblk.ko module Registering block device major 202 XENBUS: Timeout connecting to device: device/vbd/51712 (state 3) XENBUS: Timeout connecting to device: device/vbd/51716 (state 3) Scanning and configuring dmraid supported devices Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: m...

...1f9 root at lab-xh3:~# xe vbd-plug uuid=716880c9-d6cb-44a8-e5cd-6a68f708c1f9 The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: the device disappeared from xenstore (frontend (domid=2 | kind=vbd | devid=51712); backend (domid=0 | kind=vbd | devid=51712)) Log file content: [20120523T14:00:23.276Z| info|lab-xh3|74 UNIX /var/lib/xcp/xapi||cli] xe vbd-plug uuid=716880c9-d6cb-44a8-e5cd-6a68f708c1f9 username=root password=null [20120523T14:00:23.278Z| info|lab-xh3|74 UNIX /var/lib/xcp/xapi|session.login_wit...

...eate or reboot any VMs using tap:aio driver. All seems to be fine with other VMs with "file" driver un 7 16:11:41 alca2 kernel: [12537879.848530] blk_tap: Error initialising /dev/xen/blktap - No more devices Jun 7 16:11:41 alca2 logger: /etc/xen/scripts/blktap: Writing backend/tap/136/51712/hotplug-status connected to xenstore. Jun 7 16:11:41 alca2 logger: /etc/xen/scripts/blktap: Writing backend/tap/136/51728/hotplug-status connected to xenstore. Jun 7 16:11:44 alca2 kernel: [12533839.409637] blktap: ring-ref 8, event-channel 12, protocol 1 (x86_64-abi) Jun 7 16:11:44 alca2 kernel...