similar to: 2 Problems with attaching/detaching disks with virsh and KVM

On Wed, Sep 11, 2019 at 08:48:28AM -0500, Eric Blake wrote: > On 9/11/19 5:40 AM, Richard W.M. Jones wrote: > > Very much a work in progress as there are still many tests using > > qemu-io which are candidates for conversion. > > > > You'll notice at the end of test-full.sh that the new test has some > > duplicated code which looks as if it ought to be

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, Look under examples: http://builder.virt-tools.org/artifacts/libvirt-virshcmdref/html/sect-attach-disk.html (root at h2)-(/)# virsh attach-disk vps_99 /dev/nbd2 vdb --address pci:0000.00.11.0 --persistent *error: command 'attach-disk' doesn't support option --address* (root at h2)-(/)# virsh --version 0.7.5 Is someone playing a trick on me? Regards, Daniele -------------- next

Hi, have permanent failure when try to create VDI on local SR type=file or type=ext. On both types it failed with the same error: SR_BACKEND_FAILURE_78 VDI Creation failed [opterr=error 127] I am on Debian box with kernel 3.3.0-rc7, Xen version 4.1.2 (Debian 4.1.2-2.1), Xen-API Version: 1.3.2-4 (Kronos) Is it a bug, or am I missing something? Anybody managed to workaround this problem? Here is

The log snippet doesn''t have the detail in it - have a look in /var/log/SMlog - you might find something more useful in there. Jon On 5 Apr 2012, at 10:23, Dimitar Kazakov wrote: > Hi, > have permanent failure when try to create VDI on local SR type=file or > type=ext. On both types it failed with the same error: > SR_BACKEND_FAILURE_78 > VDI Creation failed

Thanks! I found the problem in SMlog. /usr/sbin/td-util create vhd 1024 /var/run/sr-mount/4137dc90-4ad7-ecc6-dd2f-6f05ac280fc2/247b64e4-6b7f-4b2f-bd73-50e848c78d71.vhd /usr/sbin/td-util: error while loading shared libraries: libxenctrl.so.4.0: cannot open shared object file: No such file or directory td-util from blktap-utils 2.0.90-3 (testing) is looking for libxenctrl.so.4.0, but the package

Hi, Filesystem is a XFS. The source file isn't a sparse file, but have big chunks of \0's. $ ls -lh probeta.vdi -rw------- 1 djgera djgera 11G 2008-09-14 02:47 probeta.vdi $ ls -l probeta.vdi -rw------- 1 djgera djgera 10737459712 2008-09-14 02:47 probeta.vdi $ du -h probeta.vdi 11G probeta.vdi when copy with $ rsync -aSv --progress probeta.vdi test-sparse.vdi sending incremental

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

This fixes the xapi test case 02 with those parts that currently do not work disabled with ''if 0:'' Signed-off-by: Stefan Berger <stefanb@us.ibm.com> Index: root/xen-unstable.hg/tools/xm-test/tests/xapi/02_xapi-vbd_basic.py =================================================================== --- root.orig/xen-unstable.hg/tools/xm-test/tests/xapi/02_xapi-vbd_basic.py +++

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'

Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream vbd plug to PV domain cause following error: The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: the device disappeared from xenstore (frontend (domid=4 | kind=vbd | devid=51760); backend (domid=0 | kind=vbd | devid=51760)) (same error

Hello I have a problem with VDI already attached RW in the "adding tag" in blktap2. This issue is on all hosts in pool with attached lvmoiscsi SR. Is there any solution to this problem? /var/log/SMlog: [32484] 2013-01-17 14:59:44.200883 vdi_activate {''sr_uuid'': ''e33281eb-ba4c-3829-9b61-7c64764dff9c'', ''subtask_of'':

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

On Thu, 4 Aug 2016 17:51:09 +0200 rme at bluemail.ch wrote: > Even some more observations. > > I noticed when I join my machine to AD it prompts a second time for > the credentials. It does not matter what I enter or even cancel the > dialog it will always display an error: > > Changing the Primary Domain DNS name of this computer to "" failed. > The name will

This logfile was recorded while the vm-start was running. -------------- next part -------------- [20120727T14:43:34.919Z| info|vh10|1021 UNIX /var/lib/xcp/xapi|session.logout D:dd291648d150|xapi] Session.destroy trackid=e3179eeb95ba96c64ab771d0cb1557b6 [20120727T14:44:02.180Z|debug|vh10|25|Starting periodic scheduler D:641021a392d0|backgroundscheduler] Adding function Logrotate to queue,

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

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

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

Anyone have any idea on this. I wanted to separate out my VirtualBox VDIs so that I could activate compression on the rest of the parent directory structure so I created a ZFS filesystem under my user directory. mv .VirtualBox .VirtualBox_orig zfs create /export/home/user/.VirtualBox zfs create /export/home/user/.VirtualBox/VDI zfs set compression=off /export/home/user/.VirtualBox/VDI zfs set

Hello, I?m using ZFS to export some iscsi targets for the virtual box iscsi initiator. It works ok if I try to install the guest OS manually. However, I?d like to be able to import my already prepared guest os vdi images into the iscsi devices but I can?t figure out how to do it. Each time I tried, I cannot boot. It only works if I save the manually installed guest os and re-instate the same