search for: blk0

blkcat allows to extract files given their data units (clusters for NTFS, fragments for ExtX). This API allows to recover files which icat cannot. For example icat often fails retrieving deleted files on Ext3/Ext4 filesystems. As this API works at data unit level, some garbage at the beginning or at the end of the files is expected. An example of blkcat can be found here:

...en-us \ > -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 \ > -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on \ > -vnc :9 \ > -chardev socket,id=char0,path=/var/tmp/vhost.0 \ > -device vhost-user-blk-pci,id=blk0,chardev=char0,num-queues=4 \ > > But most of the time, VM boot failed with following message in vnc screen: > Warning: /dev/disk/by-uuid/e0dcaf0c-bc23-4df6-b2cd-d40aa1bbb0b5 does not exist > > Generating "/run/initramfs/rdsosreport.txt" > > Entering emergency...

...t to add the vhost-user-scsi-pci/vhost-user-blk-pci support for libvirt. The usage in qemu like this: Vhost-SCSI -chardev socket,id=char0,path=/var/tmp/vhost.0 -device vhost-user-scsi-pci,id=scsi0,chardev=char0 Vhost-BLK -chardev socket,id=char1,path=/var/tmp/vhost.1 -device vhost-user-blk-pci,id=blk0,chardev=char1 What type should I add for libvirt. Type1: <hostdev mode='subsystem' type='vhost-user'> <source protocol='vhost-user-scsi' path='/tmp/vhost-scsi.sock'></source> <alias name="vhost-user-scsi-disk1"/>...

...ueue(<queue num='4'/>) or reusing the driver label (<driver name='vhostuser' queues='4'), which one is better? Qemu support multiqueue like this: -device vhost-user-scsi-pci,id=scsi0,chardev=spdk_vhost_scsi0,num_queues=4 -device vhost-user-blk-pci,chardev=spdk_vhost_blk0,num-queues=4 Another question: When qemu is connecting to a vhost-user-scsi controller[1], there may exist multiple LUNs under one target, then one disklabel(<disk/>) will represent multiple SCSI LUNs, the 'dev' property(<target dev='sda' bus='scsi'/>) will be...

...i support > for libvirt. > > The usage in qemu like this: > > Vhost-SCSI > -chardev socket,id=char0,path=/var/tmp/vhost.0 > -device vhost-user-scsi-pci,id=scsi0,chardev=char0 > Vhost-BLK > -chardev socket,id=char1,path=/var/tmp/vhost.1 > -device vhost-user-blk-pci,id=blk0,chardev=char1 > Indeed that matches what I see for the qemu commits too: https://git.qemu.org/?p=qemu.git;a=commit;h=00343e4b54b https://git.qemu.org/?p=qemu.git;a=commit;h=f12c1ebddf7 > What type should I add for libvirt. > Type1: > <hostdev mode='subsystem' type=...

...reusing the driver label > > (<driver name='vhostuser' queues='4'), which one is better? > > Qemu support multiqueue like this: > > -device vhost-user-scsi-pci,id=scsi0,chardev=spdk_vhost_scsi0,num_queues=4 > > -device vhost-user-blk-pci,chardev=spdk_vhost_blk0,num-queues=4 > > > > num-queues is already supported by libvirt for both <disk> and <hostdev> > with <driver queues=X/>, so whether we use <disk> or <hostdev> you won't > need to add any new XML here. Got it. > > > Another question: >...

Package: src:xen Version: 4.8.1~pre.2017.01.23-1 Severity: wishlist Dear Maintainer, In Xen 4.8 it is possible to enable OVMF without the need for any OVMF code or binary to be on the system. Currently, OVMF is not enabled, probably because it used to require OVMF at compile time which would make for a hard dependency on non-free code. Since this is no longer the case, you could make it a

...#39;4'/>) or reusing the driver label > (<driver name='vhostuser' queues='4'), which one is better? > Qemu support multiqueue like this: > -device vhost-user-scsi-pci,id=scsi0,chardev=spdk_vhost_scsi0,num_queues=4 > -device vhost-user-blk-pci,chardev=spdk_vhost_blk0,num-queues=4 > num-queues is already supported by libvirt for both <disk> and <hostdev> with <driver queues=X/>, so whether we use <disk> or <hostdev> you won't need to add any new XML here. > Another question: > When qemu is connecting to a vhost-user-...

...oves the buffer allocation into devices, the second patch adds the `shared_buffer_mutex` parameter to vdpa_sim_blk to use the same ramdisk for all devices. Tested with QEMU v8.0.0-rc2 in this way: modprobe vhost_vdpa modprobe vdpa_sim_blk shared_backend=true vdpa dev add mgmtdev vdpasim_blk name blk0 vdpa dev add mgmtdev vdpasim_blk name blk1 qemu-system-x86_64 -m 512M -smp 2 -M q35,accel=kvm,memory-backend=mem \ ?-object memory-backend-file,share=on,id=mem,size="512M",mem-path="/dev/shm" ?... ?-blockdev node-name=drive_src1,driver=virtio-blk-vhost-vdpa,path=/dev/vhost-v...

From: Matt Fleming <matt.fleming at linux.intel.com> This series fixes some bugs and switches the elflink branch to be entirely ELF modules. It applies on top of, http://syslinux.zytor.com/archives/2011-April/016369.html The deletions in the diff stat below are mainly from deleting com32/elflink/modules (finally!). Now there should be no duplicate code because we don't need COM32 and