similar to: Bug report on blktap-utils: vhd-update crashes with exit status 139

Hi, We found a crash in td-rated contained in the blktap-utils package. You are being contacted because your are listed as one of the maintainer of blktap-utils. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the seriousness of the bug before it is publicly disclosed. The bug report that will be

Hi, We found a crash in qemu-dm contained in the xen-utils-4.1 package. You are being contacted because your are listed as one of the maintainer of xen-utils-4.1. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the seriousness of the bug before it is publicly disclosed. The bug report that will

Hi, We found a crash in dumpcore contained in the xcp-xapi package. You are being contacted because your are listed as one of the maintainer of xcp-xapi. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the seriousness of the bug before it is publicly disclosed. The bug report that will be

Hi, We found a crash in xentrace_setmask contained in the xen-utils-4.1 package. You are being contacted because your are listed as one of the maintainer of xen-utils-4.1. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the seriousness of the bug before it is publicly disclosed. The bug report

Hi, We found a crash in xentrace_setsize contained in the xen-utils-4.1 package. You are being contacted because your are listed as one of the maintainer of xen-utils-4.1. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the seriousness of the bug before it is publicly disclosed. The bug report

Hi, We found a crash in xenctx contained in the xen-utils-4.1 package. You are being contacted because your are listed as one of the maintainer of xen-utils-4.1. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the seriousness of the bug before it is publicly disclosed. The bug report that will be

Hi, We found a crash in xenbaked contained in the xen-utils-4.1 package. You are being contacted because your are listed as one of the maintainer of xen-utils-4.1. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the seriousness of the bug before it is publicly disclosed. The bug report that will

Hi, We found a crash in tp contained in the xcp-storage-managers package. You are being contacted because your are listed as one of the maintainer of xcp-storage-managers. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the seriousness of the bug before it is publicly disclosed. The bug report

Package: xcp-storage-managers Version: 0.1.1-3.1 Severity: normal User: mayhem at forallsecure.com Usertags: mayhem tp crashes with exit status 139. We confirmed the crash by re-running it in a fresh debian unstable installation. The attachment [1] contains a testcase (under ./crash) crashing the program. It ensures that you can easily reproduce the bug. Additionally, under ./crash_info/, we

Package: xen-utils-4.1 Version: 4.1.4-4 Severity: normal User: mayhem at forallsecure.com Usertags: mayhem xenbaked crashes with exit status 139. We confirmed the crash by re-running it in a fresh debian unstable installation. The attachment [1] contains a testcase (under ./crash) crashing the program. It ensures that you can easily reproduce the bug. Additionally, under ./crash_info/, we

Package: xen-utils-4.1 Version: 4.1.4-4 Severity: normal User: mayhem at forallsecure.com Usertags: mayhem xenctx crashes with exit status 139. We confirmed the crash by re-running it in a fresh debian unstable installation. The attachment [1] contains a testcase (under ./crash) crashing the program. It ensures that you can easily reproduce the bug. Additionally, under ./crash_info/, we include

Package: xen-utils-4.1 Version: 4.1.4-4 Severity: normal User: mayhem at forallsecure.com Usertags: mayhem xentrace_setmask crashes with exit status 139. We confirmed the crash by re-running it in a fresh debian unstable installation. The attachment [1] contains a testcase (under ./crash) crashing the program. It ensures that you can easily reproduce the bug. Additionally, under ./crash_info/,

Package: xen-utils-4.1 Version: 4.1.4-4 Severity: normal User: mayhem at forallsecure.com Usertags: mayhem xentrace_setsize crashes with exit status 139. We confirmed the crash by re-running it in a fresh debian unstable installation. The attachment [1] contains a testcase (under ./crash) crashing the program. It ensures that you can easily reproduce the bug. Additionally, under ./crash_info/,

I was wondering if someone can shed some light on why vhd files created with qemu-img don''t really work right with vhd-util and consequentially blktap in general. To validate the incompatiblity its simple enough to do qemu-img create -f vpc test.vhd 40g vhd-util snapshot -n child.vhd -p test.vhd Which will show the below and then the headers don''t display the BATMAP summary:

[PATCH 0/4] VHD Support addition The patches that follow implement Microsoft''s VHD format support, and apply to xen-unstable.hg CS 15281:356588dda4bc This is based on the VHD format spec covered by Microsoft''s "Open Specification Promise": http://www.microsoft.com/interop/osp/default.mspx MS VHD Spec can be found at the following link:

Hello List, I''m using blktap on XCP 1.1 and developing a difference copy program for easy backup and remote archival. The idea is to read the BAT of VHD1 and sync it to BAT of VHD2 with BITMAP and the data blocks. Other way would be by adding a sha1 signature in each data block and comparing it with remote VHD. I tried to get some info from below programs but could not get required

(new) blktap-dkms_2.0.90-1.debian.tar.gz optional kernel (new) blktap-dkms_2.0.90-1.dsc optional kernel (new) blktap-dkms_2.0.90-1_amd64.deb optional kernel Xen API blktap kernel component DKMS package The Xen Cloud Platform (XCP) is an open source enterprise-ready server virtualization and cloud computing platform, delivering the Xen Hypervisor with support for a range of guest operating

Package: blktap Version: 2.0.90-4 Severity: important User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-6 gcc-6-unused-const-variable This package fails to build with GCC 6. GCC 6 has not been released yet, but it's expected that GCC 6 will become the default compiler for stretch. Note that only the first error is reported; there might be more. You can find a snapshot of GCC 6 in

Package: blktap-utils Version: 2.0.90-1 Severity: important User: debian-release at lists.debian.org Usertags: goal-dash Hello maintainer, While performing an archive wide checkbashisms (from the 'devscripts' package) check I've found your package containing a /bin/sh script making use of a bashism. checkbashisms' output: >possible bashism in ./usr/sbin/vhdpartx line 40

I''m newbie Xen-4.1.1 I''m trying to boot DomU with the following configuration. Sometime DomU boot, but sometime boot failed I''m not sure what is the problem. I can attach that image with tap-ctl on Dom0. Does anybody advice me about this problem?? Sincerely * Environment OS : Scientific Linux 6.1 x86_64 Kernel : 2.6.32.43