similar to: Bug#695645: xen-utils-common: xm block-attach does not create /dev/xvd* devices on dom0

Hello List, i am trying to boot a 2.6.28 vanilla kernel as a DomU. This is some of my config: ---------------------------------------------- root = ''/dev/xvda2 ro'' disk = [ ''drbd:pgone,xvda2,w'', ''phy:/dev/vg/pgone-swap,xvda1,w'',

Hi have 4 dom0 with debian lenny running xen. When I run ps axf|grep xvd I see it''s different on diferent dom0s. dom0-A 15677 ? S< 0:00 \_ [blkback.139.xvd] 15678 ? S< 0:38 \_ [blkback.139.xvd] 17015 ? S< 0:00 \_ [blkback.140.xvd] 17016 ? S< 2:34 \_ [blkback.140.xvd] 21309 ? S< 0:00 \_ [blkback.142.xvd] 21310 ?

Hello, I read the blktap readme; there is a section there titled: Mounting images in Dom0 using the blktap driver. It says there that you can mount an image by: xm block-attach 0 tap:aio:<FILENAME> /dev/xvda1 w 0 mount /dev/xvda1 /mnt/disk <--- don''t use loop driver This option also appears in: http://wiki.rpath.com/wiki/Xen_DomU_Guide I assume that this option is not

We recently added a disk to our Coraid SAN. We''ve used tons of devices off of this SAN with Xen before, but this time we experienced some weird behavior. I configured a DomU to have the device directly offered as a disk (i.e. ''phy/dev/etherd/e1.1,sdb1,rw''). When I tried to boot it, an xvd process showed up as usual. However, it consumed 100% processor

Hello, This is a second post, with a trial which is different from the first one , in order to solve my blcok-attach problem. I tried the following two actions, according to the blktap readme: qcow-create 1000 qcowFile.img Creating file size 1048576000 Created cksum: 1813725440 then xm block-attach 0 tap:qcow:qcowFile.img /dev/xvda1 w 0 I see in the /var/log/xen/xend.log: [2007-03-13

LANANA has officially assigned the block major of 202 for xvd devices (http://www.lanana.org/docs/device-list/devices-2.6+.txt). Take advantage of knowing this so people don''t have to do the mknod on their system. Also, fix up the scsi regex to get sda correct without having to do hacks like sda0. Signed-off-by: Jeremy Katz <katzj@redhat.com> Jeremy

Hello list! (resending, it seems the previous mail didn''t make it to the list) At some point Xen supported block-reconfigure to resize domU disks on the fly.. This is not working atm/anymore? Discussion about the subject.. (in the end of the thread): http://lists.xensource.com/archives/html/xen-users/2008-04/msg00246.html Support for online resizing Linux SCSI disks was accepted

Hi! Say I export an LVM logical volume from dom0 as /dev/xvda to the domU: disk = [ ''phy:xenimages/stan,xvda,w'' ] No I can lvresize xenimages/stan in dom0, but the domU stays ignorant of this change. How could I propagate the resize to the domU without rebooting or temporarily breaking its connection to /dev/xvda? Sort of a SCSI rescan, perhaps? -- Thanks, Feri.

Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream Normally (in 'iso-based' XCP) is possible to attach VDI to dom0. That operation usually looks like: xe vbd-create vdi-uuid=... vm-uuid=(dom0 uuid) device=N xe vbd-plug I done those steps in xcp-xapi and got success (no error), but no xvd* device found. Here operations log: # xe vbd-create

Hi, I am able to get Xend running on Fedora 8 but when I try to create any VM it fails. The xm create osc.cfg throws following error - [root@asds174 vm_images]# xm create osc.cfg Modified arg=osc.cfg stop3 Using config file "./osc.cfg". group_id=None [''create'', ''osc.cfg''] Stop 1 None [''vm'', [''name'',

Hello, I''ve installed XenExpress 3.2. Within a DomU (Debian) I want to recompile the kernel. I installed the kernel-source /kernel-xs-xen/kernel-2.6.16.38-xs3.2.0.531.3960.src.rpm from the XenServer-3.2.0-src1.iso. The kernel and modules build well. But: ---------------------------- IPCopHost:~# mkinitrd -o /boot/initrd-2.6.16.xen-38 2.6.16.xen-38 /usr/sbin/mkinitrd: /dev/xvda1: Unknown

Hi Everyone, When you want to use ionice to limit the amount of disk a DomU has, due to have to run ionice on every blkback process? Incidently, what is the format of the blkback process? I see the following in ps aux: blkback.xx.xvda blkback.xx.xvda1 blkback.xx.xvd where xx appears to be the domain ID. I''m curious as to the last few letters mean? Thanks

Hi,All, I installed a guest os with full-virtualization and a local volume as the disk, now becuase of poor performance, I want to change the full-virtualization guest to para-virtualization, so I just changed the config file to boot the guest os with para-virtualization, but it fails to boot. but how can I convert the full-virtualization guest to para-virtualization without reinstall the os,on

Hello folks, After I upgrade xen-tools to 4.1-unstable, the vm can''t start with disk = [ ''tap:aio:/path/to/image.img,xvda1,w'' ] The vm can''t connect to blk back-end because xm command doesn''t set tapdisk2 (tap-ctl) correctly. But with xl command, everything work right. Any help to xm? I need python support provided by xm in vm config file. Thanks.

Hello folks, After I upgrade xen-tools to 4.1-unstable, the vm can''t start with disk = [ ''tap:aio:/path/to/image.img,xvda1,w'' ] The vm can''t connect to blk back-end because xm command doesn''t set tapdisk2 (tap-ctl) correctly. But with xl command, everything work right. Any help to xm? I need python support provided by xm in vm config file. Thanks.

This fixes the xapi test case 02 with those parts that currently do not work disabled with ''if 0:'' Signed-off-by: Stefan Berger <stefanb@us.ibm.com> Index: root/xen-unstable.hg/tools/xm-test/tests/xapi/02_xapi-vbd_basic.py =================================================================== --- root.orig/xen-unstable.hg/tools/xm-test/tests/xapi/02_xapi-vbd_basic.py +++

Hi everyone, I generated my own DomU guest using opensuse''s yast dirinstall and stored it on a seperate iscsi target. I created it as a DomU on my Domain0 (2.6.25.16-0.1-xen kernel) successfully, using the following configuration: name = "vm01-opensuse11-base-LAMP" memory = 256 kernel = "/boot/vmlinuz-xen" ramdisk = "/boot/initrd-xen" root =

This patch enables ''xm pci-attach/detach'' commands to be executed via xen-api. Regards, ----------------------- Yosuke Iwamatsu NEC Corporation _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi all, I'm running Centos 5.5 with Xen 4.0.1 Would like to use a USB key (not a block device) in my domU. Dom0 lsusb yields; Bus 002 Device 004: ID 064f:0bd8 ABC-Systems AB CDE/FG xm usb-add shows; Usage: xm usb-add <domain> <[host:bus.addr] [host:vendor_id:product_id]> Not sure what combo will work in this case. However, I've read some notes regarding xm usb-attach.

I''m a complete newbie at Xen, just getting started. I was happy to see that Ubuntu 11.10 includes Xen again, http://zulcss.wordpress.com/2011/09/04/xen-4-1-1-on-ubuntu/ So I installed ubuntu 11.10''s precompiled Xen, and started playing around with it. I''m not even trying to start another VM at the moment, just playing around with mounting block devices, and had trouble