search for: bdrv_open

Displaying 8 results from an estimated 8 matches for "bdrv_open".

2011 Jun 24
9
[PATCH] xen_disk: cope with missing xenstore "params" node
...@@ -672,11 +674,15 @@ static int blk_init(struct XenDevice *xendev) /* setup via xenbus -> create new block driver instance */ xen_be_printf(&blkdev->xendev, 2, "create new bdrv (xenbus setup)\n"); blkdev->bs = bdrv_new(blkdev->dev); - if (bdrv_open(blkdev->bs, blkdev->filename, qflags, - bdrv_find_whitelisted_format(blkdev->fileproto)) != 0) { - bdrv_delete(blkdev->bs); - return -1; + if (blkdev->bs) { + if (bdrv_open(blkdev->bs, blkdev->filename, qflags, +...
2011 Jun 27
1
[PATCH v3] xen_disk: cope with missing xenstore "params" node
...@@ -672,10 +674,15 @@ static int blk_init(struct XenDevice *xendev) /* setup via xenbus -> create new block driver instance */ xen_be_printf(&blkdev->xendev, 2, "create new bdrv (xenbus setup)\n"); blkdev->bs = bdrv_new(blkdev->dev); - if (bdrv_open(blkdev->bs, blkdev->filename, qflags, - bdrv_find_whitelisted_format(blkdev->fileproto)) != 0) { - bdrv_delete(blkdev->bs); - return -1; + if (blkdev->bs) { + if (bdrv_open(blkdev->bs, blkdev->filename, qflags, +...
2011 Jun 24
2
[PATCH v2] xen_disk: cope with missing xenstore "params" node
...@@ -672,10 +674,15 @@ static int blk_init(struct XenDevice *xendev) /* setup via xenbus -> create new block driver instance */ xen_be_printf(&blkdev->xendev, 2, "create new bdrv (xenbus setup)\n"); blkdev->bs = bdrv_new(blkdev->dev); - if (bdrv_open(blkdev->bs, blkdev->filename, qflags, - bdrv_find_whitelisted_format(blkdev->fileproto)) != 0) { - bdrv_delete(blkdev->bs); - return -1; + if (blkdev->bs) { + if (bdrv_open(blkdev->bs, blkdev->filename, qflags, +...
2008 Sep 10
2
Bug#490409: xen-3: diff for NMU version 3.2.1-2.1
...s", params); + free(params); + params = newparams; ++ format = &bdrv_raw; + } + + /* +@@ -227,9 +238,25 @@ void xenstore_parse_domain_config(int do + + /* open device now if media present */ + if (params[0]) { +- if (bdrv_open(bs, params, 0 /* snapshot */) < 0) +- fprintf(stderr, "qemu: could not open hard disk image '%s'\n", +- params); ++ if (!format) { ++ if (!drv) { ++ fprintf(stderr, "qemu: type (image format) not specified for vbd '%s'...
2018 Mar 05
2
Re: Fail in virDomainUpdateDeviceFlags (libvirt-4.0.0 + Qemu-kvm 2.9.0 + Ceph 10.2.10)
On Fri, Mar 02, 2018 at 15:32:44 -0500, John Ferlan wrote: > > > On 03/02/2018 08:28 AM, Peter Krempa wrote: > > On Tue, Feb 27, 2018 at 09:53:00 +0100, Michal Privoznik wrote: > >> On 02/27/2018 03:06 AM, Star Guo wrote: > >>> Hello Everyone, > >>> > >>> > >>> > >>> My pc run in CentOS 7.4 and install
2018 Mar 05
0
Re: Fail in virDomainUpdateDeviceFlags (libvirt-4.0.0 + Qemu-kvm 2.9.0 + Ceph 10.2.10)
...pts the device if provided). AFAICT, the "id" option is not used in libvirt yet. The block_set_io_throttle being the example I looked at. Following the code for using the "id" option, I see no connection to the secret object which would store the server passphrase. So when the bdrv_open is called from qmp_blockdev_change_medium, there is no way to "connect" to the alias. If it happens differently than that, then please show me what I'm missing. > > That was the reason why I insisted so much that you actually make it a > member of virStorageSource. > &...
2018 Feb 27
1
Reply: Fail in virDomainUpdateDeviceFlags (libvirt-4.0.0 + Qemu-kvm 2.9.0 + Ceph 10.2.10)
Dear Michal After I fix the local libvirt master branch follow your patch, and build rpm for CentOS 7.4. virDomainUpdateDeviceFlags as bellow: ================================================ 2018-02-27 09:27:43.782+0000: 16656: debug : virDomainUpdateDeviceFlags:8326 : dom=0x7f2084000c50, (VM: name=6ec499397d594e f2a64fcfc938f38225, uuid=6ec49939-7d59-4ef2-a64f-cfc938f38225), xml=<disk
2008 Mar 10
12
[RFC][PATCH] Use ioemu block drivers through blktap
When I submitted the qcow2 patch for blktap, suggestions came up that the qemu block drivers should be used also for blktap to eliminate the current code duplication in ioemu and blktap. The attached patch adds support for a tap:ioemu pseudo driver. Devices using this driver won''t use tapdisk (containing the code duplication) any more, but will connect to the qemu-dm of the domain. In