similar to: does libvirt support VHD disk tpye?

Hi all, I had met with a question about vhd format when i install xen 4.2.0 source code on suse11_x86_64_sp2. execute steps: 1)Install fully suse 11 sp2 to host pc 2)Boot from Xen kernel menu 3)Download xen 4.2.0 source code from http://xen.org/download/index_4.2.0.html 4)Download bin86-0.16.19.tar.gz cmake-2.8.9.tar.gz Dev86src-0.16.19.tar.gz gettext-0.18.1.1.tar.gz

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

Hi sahil: I think the reason why you cannot get page shared is due to the gref you got. Gref is responsible for a page allocated from domU, in my understanding it should not be 0, that is a gref 0 can not be shared, that''s why I skip gref 0 to be nominated. The gref is nominated to Xen and later used to find a corrspond MFN, so it shall not always be the same.

[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:

blktap2: fix makefile of vhd for parallel make With parallel make, libvhd might not be created before link resulting in link error. This patch guarantees it. Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp> diff --git a/tools/blktap2/vhd/Makefile b/tools/blktap2/vhd/Makefile --- a/tools/blktap2/vhd/Makefile +++ b/tools/blktap2/vhd/Makefile @@ -12,6 +12,9 @@ CFLAGS +=

Hi, I''ve been testing Xen 4.0.1 with kernel 2.6.34.5 + http://gentoo-xen-kernel.googlecode.com/files/xen-patches-2.6.34-4.tar.bz2, and one of the things that I noticed immediately is there are two problems with tapdisk and this combination. First, the syntax "disk = [''tap:tapdisk:aio: ..." no longer works. When tested with HVM domU, it boots, but there was no disk

Hello, I have a problem with storage over NFS (NFS server is running on Open Solaris 10 with NFS version client/server/min/max=3) cat /var/log/messages from cnode1 (XCP 1.0 beta) during instalation new VM: an 18 22:57:37 cnode1 tapdisk[9661]: ERROR: errno -88 at vhd_complete: /var/run/sr-mount/2d5ed3ca-7e4d-bceb-f959-542d3bade15e/3d69f4a6-743d-486e-8a65-1734e6ef0b67.vhd: op: 2, lsec:

For those wanting to know how to mount filesystems through blktap2 here is how you do it, as I couldn''t find it fully documented. The instructions on the blktap2 readme file are rather out of date. You can mount them under Dom0 like so. e.g. to mount a vhd file, sudo xm block-attach 0 tap2:vhd:/home/xen/xenwin7-persist.vhd xvdb w 0 Now the device should appear under /dev ls

I''m getting this message (subject line) in daemon.log every time I start or restart xend. I''m not sure if this is related to the fact that I cannot boot up my Windows domU from a VHD file. The Windows domU was working fine with Xen 4.0.0 (with 2.6.32.14 dom0 kernel). When I upgraded to Xen 4.0.1-rc4 (with 2.6.32.16 dom0 kernel), I can no long boot the Windows domU from VHD. The

Package: src:blktap Version: 2.0.90-3 Severity: normal Tags: sid stretch User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built

The domU is using pygrub to boot its own 2.6.18.8-xen kernel. It can be booted successfully under 2.6.18.8-xen dom0 and xen 3.3.1. However when upgrade dom0 to 2.6.32.15 and xen 4.0.1-rc3-pre, the domU can not boot with tapdisk. I am wondering it is something related to the blktap driver. *When using tap:aio:* PATH/disk.img in domU disk configuration, the boot process hanged at a prompt: XENBUS:

The domU is using pygrub to boot its own 2.6.18.8-xen kernel. It can be booted successfully under 2.6.18.8-xen dom0 and xen 3.3.1. However when upgrade dom0 to 2.6.32.15 and xen 4.0.1-rc3-pre, the domU can not boot with tapdisk. I am wondering it is something related to the blktap driver. *When using tap:aio:* PATH/disk.img in domU disk configuration, the boot process hanged at a prompt: XENBUS:

Hi, In most cases we use image files as virtual disks under the full-virtualization situation.On the version 4.1.2 of xen,I do the following command: ############################################################ dd if=/dev/zero of=myraw.img bs=1M seek=8K count=1 #Before the command below I install the operating system in myraw.img qemu-img-xen create -b myraw.img -f qcow2 myqcow1.img 20000M

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

Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream Normally (in 'iso-based' XCP) is possible to attach VDI to dom0. That operation usually looks like: xe vbd-create vdi-uuid=... vm-uuid=(dom0 uuid) device=N xe vbd-plug I done those steps in xcp-xapi and got success (no error), but no xvd* device found. Here operations log: # xe vbd-create

Hi, I am in the process of upgrading some xen installations from 3.x to 4.1.1 and got into this: box# xl create vm1.cfg warning: Config file looks like it contains Python code. warning: Arbitrary Python is no longer supported. warning: See http://wiki.xen.org/xenwiki/PythonInXlConfig Failed to parse config file: Invalid argument I''m using python stuff to define vifs and disks

I''m using the CentOS 6 bundle of xen from http://dev.centos.org/centos/6/xen-c6/ and ran into an issue when creating domains with multiple VHD tap disks. Comparing unstable to the 4.2.1 code I''m using, it seems this issue still applies. I''m using a configuration line that looks something like disk = [

Changes: tools/blktap: remove unneeded pointer dereferencing in convert_dev_name_to_num tools/blktap: constify string arrays in convert_dev_name_to_num tools/blktap: fix params and physical-device parsing tools/blktap: remove unneeded pointer dereferencing from img2qcow.c tools/blktap: remove unneeded pointer dereferencing from qcow2raw.c tools/blktap2: fix build errors caused by Werror in

Hi Guys, I''m working with: 1. xen 4.1; 2. dom0 ubuntu kernel 3.2 I''m trying to run remus with disk replication (I can run without disk replication). But I read I need to use tap2 < http://nss.cs.ubc.ca/remus/doc.html>. Well... first I tried to create a pv guest. Then I take this guest.cfg: 1. name = "ubuntu-ha" 2. memory = 256 3. disk =

There seems to be an outdated page to use PV drivers here: http://wiki.xensource.com/xenwiki/XenWindowsGplPv I''d be great if that could be updated. After installing the PV drivers in windows I didn''t notice any difference in performance at all. Windows says the drivers are working. Some more searching and reading and it appears that I do actually need to make some changes to