search for: vbd

...because vbd_size() dereferences bd_disk if bd_part is NULL. Signed-off-by: Laszlo Ersek<lersek@redhat.com> --- drivers/xen/blkback/vbd.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff -r 415a9b435fef drivers/xen/blkback/vbd.c --- a/drivers/xen/blkback/vbd.c Mon May 23 18:36:33 2011...

...en/blktapX to qemu-dm, which I can access fine, but eject does not work, since qemu only sees the phy: device and can''t open another file. xen-blockfront in PVonHVM and Windows-GPLPV driver both reject CDROM-devices, so the CDROM remains IDE emulated. With GPLPV /local/domain/0/backend/vbd/18/768/state changes from "1" → "4", while with Linux it changes to "6" as soon as the Xen modules probe the XenBus. After that Xend refused to change the medium with the following error: > error: POST operation failed: xend_post: error from xen daemon: (xend.err...

This patch series copies the core of the tapdisk process from blktap2, with updates coming from blktap2.5. Signed-off-by: Thanos Makatos <thanos.makatos@citrix.com>

...(We call the "create" operation for this object "prepare" to avoid confusion with other kinds of "create".) The toolstack promises that no two vdis for the same target will simultaneously be active, even if the two vdis are on different hosts. vbd Provision of a facility for a guest to access a particular target via a particular vdi. There may be zero or more of these at any point for a particular vdi. Non-persistent, created on request by toolstack, enumerable. Abstract operations: plug, unplug. (We call the...

...oot] $ xl create a0 $ xl cd-eject a0 hdc [However, the guest OS still sees the CD inserted] $ xl block-list a0 Segmentation fault $ xl cd-insert a0 hdc file:/images/xs-tools-6.0.0.iso Segmentation fault The problem seems to be that xl cd-eject is writing corrupt values to xenstore. Note that vbd/1/5632 is still there as when it booted, but qdisk/1/5632 has some random stuff in it $ xenstore-ls -f /local/domain/0/backend /local/domain/0/backend/qdisk = "" /local/domain/0/backend/qdisk/1 = "" /local/domain/0/backend/qdisk/1/768 = "" /local/domain/0/backend/qdis...

I tried to use cdrom in domU linux pv (Linux Mint 11 based on Natty). With ''/mnt/vm/iso/test.iso,raw,xvdb,ro,cdrom'', Mint sees it as internal disk (not cdrom) and only administrators can mount it. I tried also ''/dev/scd0,raw,xvdb,ro,cdrom'' does the same thing. Is possible use cdrom on linux domU pv full working where also normal user can mount it without

Hi! Please help me. # xm create win7.hvm Using config file "./win7.hvm". Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1 grep -v ^# /etc/xen/win7.hvm | grep -vx '''' kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' memory = 2048 name = "win7" vif = [ ''type...

...emory', 128], ['vcpus', 1], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.16-1-xen-vserver-686'], ['ip', ':1.2.3.4:::10-1-1-138:eth0:on'], ['root', '/dev/hda1'], ['args', '3']]], ['device', ['vbd', ['uname', 'file:/vserver/images/vm01.img'], ['dev', 'hda1'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'file:/vserver/images/vm01-swap.img'], ['dev', 'hda2'], ['mode', 'w']]], [...

...emory', 128], ['vcpus', 1], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.16-1-xen-vserver-686'], ['ip', ':1.2.3.4:::10-1-1-138:eth0:on'], ['root', '/dev/hda1'], ['args', '3']]], ['device', ['vbd', ['uname', 'file:/vserver/images/vm01.img'], ['dev', 'hda1'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'file:/vserver/images/vm01-swap.img'], ['dev', 'hda2'], ['mode', 'w']]], [...

Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream vbd plug to PV domain cause following error: 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=4 | kind=vbd | devid=51760); backend (domid=0 | kind=vbd...

...en (so please forgive me in advance if I''m too "newbie" :) and I''m facing my first problems... I''m trying to create a domU, but I''m getting an error: tornado:~# xm create test.cfg -c Using config file "/etc/xen/test.cfg". Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. I''ve goolgled for the error message, but nothing I''ve found seems to apply to my case. Any idea of what can be the meaning, possible solution or further test that can be performed in order to diagnose the problem? Thanks in a...

If I start a domain with a number of vbd devices, it''s a crap shoot if they''ll all show up in the domU''s /proc/partitions. I''ll eventually see all the devices if I keep rebooting the domU. The value of /local/domain/$DOMID/device/vbd/*/state are all 1 for the missing devices, and 4 for the ones tha...

...ndDomainInfo:1912) XendDomainInfo.destroyDomain(8) [2009-02-26 18:02:11 552] DEBUG (XendDomainInfo:1542) Removing vif/0 [2009-02-26 18:02:11 552] DEBUG (XendDomainInfo:603) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 [2009-02-26 18:02:11 552] DEBUG (XendDomainInfo:1542) Removing vbd/768 [2009-02-26 18:02:11 552] DEBUG (XendDomainInfo:603) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768 [2009-02-26 18:02:11 552] DEBUG (XendDomainInfo:1542) Removing vbd/5632 [2009-02-26 18:02:11 552] DEBUG (XendDomainInfo:603) XendDomainInfo.destroyDevice: deviceClass = vbd, de...

...om0, everything came up OK. Then I created a new domU for testing and did an xm shutdown without ever logging in, it happened again. The domUs I did not shut down continue to work, and xentop continues to work, though it displays Found interface vif4.0 but domain 4 does not exist. Found interface vbd-4-2050 but domain 4 does not exist. Found interface vbd-4-2049 but domain 4 does not exist. vbd-4-2050 is VBD. vbd-4-2049 is VBD. vbd-3-2050 is VBD. vbd-3-2049 is VBD. vbd-2-2050 is VBD. vbd-2-2049 is VBD. vbd-1-2050 is VBD. vbd-1-2049 is VBD. where 4 references the domU I shut down. Since the do...

Hi, since I upgraded from Lenny, DRBD VBD scripts 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: D...

parent: 24691:3432abcf9380 tip Fix x86_32 build branch: default commit: 4 modified, 1439 unknown update: (current) /usr/src/xen-4.2/stubdom/ioemu/block-vbd.c: In function âqemu_aio_waitâ: /usr/src/xen-4.2/stubdom/ioemu/block-vbd.c:147:20: error: macro "remove_waiter" requires 2 arguments, but only 1 given /usr/src/xen-4.2/stubdom/ioemu/block-vbd.c:147:5: error: âremove_waiterâ undeclared (first use in this function) /usr/src/xen-4.2/stubdom/...

Hi, From cset 10921, ioemu: prefix is removed from disk config in /etc/xen/xmexample.hvm. Now HVM VBD driver is available, this thus raises a question: how would HVM domain know if one disk is a qemu-dm disk or a VBD disk? From current implementation, qemu-dm will recognize disk had, hdb, hdc, hdd, and VBD drive can recognize all disk (had~hdd, hde, hdf ...) . So the result is: qemu-dm will mount...

...s 0000:00:01.3: SMB base address uninitialized - upgrade BIOS or use f orce_addr=0xaddr hdc: ATAPI 4X CD-ROM drive, 512kB Cache, (U)DMA Uniform CD-ROM driver Revision: 3.20 Registering block device major 3 register_blkdev: cannot get major 3 for ide xen_blk: can''t get major 3 with name ide vbd vbd-768: 19 xlvbd_add at /local/domain/0/backend/vbd/109/768 Registering block device major 3 register_blkdev: cannot get major 3 for ide xen_blk: can''t get major 3 with name ide vbd vbd-768: 19 xlvbd_add at /local/domain/0/backend/vbd/109/768 Registering block device major 22 register_blk...

I''m trying to add vbd resize to GPLPV, but it doesn''t seem to work: xm block-attach w2k3test32 phy:/dev/vg-xen/virt-test-0 hdb w xenstore-read /local/domain/0/backend/vbd/377/832/sectors =44056576 lvextend --size=+1M /dev/vg-xen/virt-test-0 xenstore-read /local/domain/0/backend/vbd/377/832/sectors =44056576...

Hi, have a debian 5.0 with all patches and xen 4.3.1 (debian repo) installed. If I use a VM with paravirtualizing it works fine. But a full virtualized image doesn''t boot. Message: ---8<--- # xm create deb50.cfg: Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. ---8<--- That is my deb50.cfg ---8<--- # Debian 5.0 import os, re arch = os.uname()[4] if re.search(''64'', arch): arch_libdir = ''lib64'' else: arch_libdir = ''lib'' kernel...