similar to: Using Solaris iSCSI target in VirtualBox iSCSI Initiator

Hi, I''m trying to migrate a VirtualBox virtual machine to Xen, but I haven''t been able to successfully boot it under xen (3.0.1 that comes with CentOS 5.5). Thinking that the problem was converting the disk format to a raw format, I tried converting the VDI disk with all these options: VBoxManage internalcommands converttoraw disk.vdi disk.raw VBoxManage clonehd disk.vdi

Hello libvirt experts, I use libvirt (0.7.5-5ubuntu27.7) with KVM / qemu (0.12.3+noroms-0ubuntu9.2). Some machines use raw images but same use Virtualbox images (.vdi). Since last Ubuntu 10.04 LTS update I can not start the vdi-images. The "driver name= type=" option was new. <devices> <emulator>/usr/bin/kvm</emulator> <disk type='file'

During some discussions and handwaving, including discussions with some experts on the Xenserver/XCP storage architecture, we came up with what we think might be a plausible proposal for an architecture for communication between toolstack and driver domain, for storage at least. I offered to write it up. The abstract proposal is as I understand the consensus from our conversation. The concrete

Hi, I''ve been touring XCP and making my way around it for the last few days, and am having problems with some reasonably straightforward actions. I''ve poured a several hours into different ways of resolving the issue, but am coming up short. Here''s the main issue. The following command (plugging in a VBD to the dom0 VM), when, run, hangs for several minutes, and then

[stef204 sent me the full log since it contains sensitive information] The log says that virt-v2v cannot see anything at all on the 34.1 GB disk (as if the disk is blank). However I think the actual problem is that you've given the wrong disk type in the XML: <disk type='file' device='disk'> <driver name='qemu' type='raw'/>

The current test for .vdi files is incorrect. It tries to detect the string "<<< Sun xVM VirtualBox Disk Image >>>". However this string is just free text and .vdi files often contain different strings (ref: [1]). The correct test in this patch looks for the magic number at offset 0x40 in the file (ref: [2]). Example: Upstream 'file' without the patch on an

Hi, I am new to v2v/libguestfs. I need to convert a 30 GB virtual machine running Windows7 64 bit (a guest on a Linux system) from Virtualbox vdi format to qcow2 (or raw/img--another debate in itself) so I can use libvirt/qemu/kvm to run it and completely migrate away from Virtualbox. The vdi machine is a mission critical production environment and I cannot afford to mess it up, etc. Will keep

hi I am having several pools of xcp with NFS shared storage as default SR on each pool and i want to do following in this arrangement -I want to share vdis among all pools, i.e. for example if I want to detach a vdi from a vm in pool-1 to a vm in pool-2. so is this possible to do so? vdi export is one of the solution but i want to do it seamlessly just like it happens within the same pool or

I''m currently getting a huge number of (failed) attempts to access my home server at UDP port 27845. I think most if not all the attacks come from China or Korea. I see there is a list of Chinese and Korean networks at <http://www.countryipblocks.net/country-blocks/>. Is there a standard way of using such a list in shorewall? -- Timothy Murphy e-mail: gayleard /at/ eircom.net

Hi dear all: I have browsed almost all architecture of libGuestFs and use it on Fedora 18. It really seems greate! However, 1. No virtual disk (*.vdi, *.vmdk...) based snashot analysis code Current LibGuestFs could recognize and virtual disk format (e.g. *.VDI) and the file syste inside it (e.g. NTFS ), but find no support for snapshot virtual disk. Virtual Machine such VirtualBox

If you use the libguestfs tools which open disk images read-only (eg. virt-df), with formats such as 'vdi', then you will see an error: error: invalid value for backingformat parameter 'vdi' This is because opening a disk image read-only will try to create a qcow2 file with the original image as a backing file. However the list of permitted backing formats was very restrictive

Hi all, I`m evaluating methods for nightly "snapshot" a physical win2003 to xcp vm. I know it would be a lot easier and reliable just to to one convert one time and start to generate real vm snapshots, but at this time I cannot use this method. I tested the sequence: disk2vdh -> xenconvert (to xcp), but a big deal of using this method is that xenconvert does not send

I'm using a Windows raw disk image that is "converted" to the VDI format by custom code that prepends a header to the image. I use 'vdi' for GUESTFS_ADD_DRIVE_OPTS_FORMAT of guestfs_add_drive_opts(). After launching the appliance, the call to guestfs_list_partitions() results in an empty list. Is there a way to add the drive but have an offset into the image file as a

It seems that lustre puts its modules in /lib/modules/2.6.16.21-0.8-default despite the fact that my kernel is 2.6.16.21-0.8-smp ! uname -a Linux n32 2.6.16.21-0.8-smp #4 SMP Sun Sep 24 08:47:30 BST 2006 i686 i686 i386 GNU/Linux make[3]: Nothing to be done for `install-exec-am''. /bin/sh ../../mkinstalldirs /lib/modules/2.6.16.21-0.8-default/kernel/fs/lustre /usr/bin/install -c -m 644

Hi, I have successfully built an ADDC on a Centos 6.5 VM running on Citrix XenServer 6.2. It seems to be working well. Now I want to test Citrix VDI-in-a-Box. I've installed vdiManager 5.4.0 on to my XenServer. It wants to authenticate to my AD server. It fails with the message: Could not connect to the user database at 10.0.1.10 with user administrator in domain test.lan I did a

I''ve just pushed vdiskadm translate to the 3.3 vdisk repo. You can now translate data from one virtual disk data type to another without creating a virtual disk. This allows the user to use a vmdk file and directly translate the data into a zvol without having to import it first to a vdisk and then export it to the zvol. # vdiskadm help translate translate - translate virtual disk data

I''ve just pushed vdiskadm import/export/convert to the 3.3 vdisk and vbox repos. You can now import a disk image from a block device or file to a vdisk, convert (in place) to a different type of vdisk and export from a vdisk to a block device or file. I''ve also pushed the full vhd support (sparse and fixed) and the ability to import a vmdk 1.1 optimized stream file. An

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

On Sun, Jun 14, 2015 at 10:51 PM, jd1008 <jd1008 at gmail.com> wrote: > > > On 06/14/2015 08:02 PM, Animesh Pandey wrote: > >> On Sun, Jun 14, 2015 at 9:47 PM, jd1008 <jd1008 at gmail.com> wrote: >> >> >>> On 06/14/2015 07:36 PM, Animesh Pandey wrote: >>> >>> On Sun, Jun 14, 2015 at 9:06 PM, jd1008 <jd1008 at gmail.com>

running windows vista: downloaded virtual machine and virtual rails cannot get virtual rails to mount to virtual machine after downloading virtual rails i attempted to extract it so i could convert it to vdi file and this is the result virtual_rails_1.1(1).7z i followed the tutorial at http://www.virtualrails.org/node/3 to create a new virtual machine, but when I start the machine i get the