Description of problem: dd if=/dev/zero of=shared.img bs=1M count=500 xm block-attach 1 [root@station100 images]# xm block-list 1 Vdev BE handle state evt-ch ring-ref BE-path 51712 0 0 4 8 8 /local/domain/0/backend/tap/1/51712 51728 0 0 3 10 571 /local/domain/0/backend/vbd/1/51728/var/lib/xen/images/shared.img xvdb w fdisk -l in the guest doesn't show up the new block device. Version-Release number of selected component (if applicable): [root@station100 images]# rpm -q xen xen-3.0.3-41.el5 [root@station100 images]# rpm -q kernel-xen kernel-xen-2.6.18-53.el5 [root@station100 images]# rpm -q libvirt libvirt-0.2.3-9.el5 How reproducible: Steps to Reproduce: 1. 2. see above 3. Actual results: no newb lock device visible in the geust Expected results: new block device visible :) Additional info:
attaching command was: [root@station100 images]# xm block-attach 1 /var/lib/xen/images/shared.img xvdb w
any updates on this?
Hm, I believe your block-attach syntax is wrong. You need: xm block-attach <domain> tap:aio:/var/lib/xen/images/shared.img /dev/xvdb w Does that work? Chris Lalancette
yeah, that fixed it. thanks
OK, great. Going to close as NOTABUG. Chris Lalancette