similar to: zfs unmount returns with Invalid Argument

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

Package: xcp-storage-managers Version: 0.1.1-2ubuntu1 Severity: normal This bug prevents CDROM VDIs from being hotplugged into guest VMs. The issue is that the NFS ISO SR configures the ISO VDIs to be 'file' types, which it should configure them to by 'phy' types. This breaks on Debian's Xen because the Debian hotplug scripts are more robuse than the ones on XenServer, and

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

I had created a virtualbox VM to test out opensolaris. I updated to latest dev build and set my things up. Tested pools and various configs/commands. Learnt format/partition etc. And then, I wanted to move this stuff to a solaris partition on the physical disk. VB provides physical disk access. I put my solaris partition in there and created slices for root, swap etc. in that partition inside the

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

Hi, I double checked the configuration with xm and the "w!" option seems to be configured :-( I also upgraded to build 123, but also no change in behaviour. Thus is this a RAC 11.2 problem or is there a general problem using zvols as as shared disks for xVM domains ? (device (vbd (protocol x86_64-abi) (uuid 048d282d-da4c-2e0b-b9f4-f3f4cc0811c7)

On Sat, Aug 19, 2017 at 08:38:31AM -0600, stef204 wrote: > 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

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

Good afternoon people, I don't know if you can help me, I set up a Lab and I'm testing the creation of VDIs using a dc samba, that's the scenario. 1) Samba domain controller 4.13 2) Windows 2019 server as a member of the domain, in it I installed hyper-v and in it I configured the remote desktop service. I set up the template and when I create the pool I take the following error.

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

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> wrote: >>> >>> >>>> On 06/14/2015 06:47 PM, Animesh Pandey wrote: >>>>

08.10.2017, 13:50, "Richard W.M. Jones" <rjones@redhat.com>: > [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

Hello! I am trying to create snapshots for sheepdog disks using libvirt API or virsh. The disk is defined in domain as follows: <disk type='network' device='disk'>       <driver name='qemu' cache='none'/>       <source protocol='sheepdog' name='sheepvol1'/>       <target dev='vdb' bus='virtio'/> </disk>

Hello! I am trying to create snapshots for sheepdog disks using libvirt API or virsh. The disk is defined in domain as follows: <disk type='network' device='disk'>       <driver name='qemu' cache='none'/>       <source protocol='sheepdog' name='sheepvol1'/>       <target dev='vdb' bus='virtio'/> </disk>

On 06/14/2015 10:27 PM, Animesh Pandey wrote: > 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: >>>>

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'

Only able to get to this now, but need additional help, if at all possible. See comments inline below. Thanks. 19.08.2017, 10:36, "Richard W.M. Jones" <rjones@redhat.com>: > On Sat, Aug 19, 2017 at 08:38:31AM -0600, stef204 wrote: >>  Hi, >> >>  I am new to v2v/libguestfs. > >>  I need to convert a 30 GB virtual machine running Windows7 64 bit (a

Hi, I am not able to boot a vdi image on virtualbox using libvirt .It keeps showing me "Bootable medium not found". I have tried booting it manually with virtualbox GUI and it boots without any problem. May there is some problem with my libvirt domain XML . I also realized on some investigation that it is not detecting the vdi image file as a hard disk (when i am booting from a live cd)

Hi all, I installed another OpenSolaris (snv_129) in VirtualBox 3.1.0 on Windows because snv_130 doesn''t boot anymore after installation of VirtualBox guest additions. Older builds before snv_129 were running fine too. I like some features of this OS, but now I end with something funny. I installed default snv_129, installed guest additions -> reboot, set

Hello, anybody has a clue why this happens? The scenario: Each night I create LVM snapshot of my volume which contains some virtual disk images (VirtualBox VDIs). Then I rsync the content of one of the snapshot directories to a backup server. Each file size is between 1.3 GB and 6GB. I run the following commmand: sudo -u rsyncbackup rsync -avzP --exclude-from /home/rsyncbackup/excludefile -e