similar to: [PATCH] v2v: fix -it ssh syntax in example (RHBZ#1540535)

Thanks a ton for the reply Matthias. I am little confused here. How to add volume on my esx server using virsh? I did SCP and copied my vmdk image to [datastore1] testNode/cluster.vmdk and also modified my xml file as you suggested. Now when I tried starting the node it gave me an error message saying: "error: Failed to start testNode error: internal error: Could not start domain:

On Friday, 8 December 2017 17:02:30 CET Richard W.M. Jones wrote: > This enhances the existing VMX input support allowing it to be > used over SSH to the ESXi server. > > The original command (for local .vmx files) was: > > $ virt-v2v -i vmx guest.vmx -o local -os /var/tmp > > Adding ‘-it ssh’ and using an SSH remote path gives the new syntax: > > $ virt-v2v \

Hi, Today I was trying to start a node using libvirt on ESX (esxi-5.1) hypervisor and I got the following error message: *virsh # define /local/myNode/esxdomain.xml* *Domain testNode defined from /local/myNode/esxdomain.xml* *virsh # start testNode* *error: Failed to start domain testNode* *error: internal error: Could not start domain: GenericVmConfigFault - Cannot open the disk

2013/8/12 varun bhatnagar <varun292006@gmail.com>: > Hi, > > Today I was trying to start a node using libvirt on ESX (esxi-5.1) > hypervisor and I got the following error message: > > virsh # define /local/myNode/esxdomain.xml > Domain testNode defined from /local/myNode/esxdomain.xml > virsh # start testNode > error: Failed to start domain testNode > error:

In previous discussion here: https://www.redhat.com/archives/libguestfs/2017-December/thread.html#00027 we preferred to use ssh://... URLs instead of server:/path. However the URL approach had the problem that the user had to replace spaces with %20 in the paths. However since using space gives an error, we can replace spaces with %20 safely in code, thus removing one obstacle from users.

We only use xmlParseURI to parse our own "homebrew" URIs, for example the ones used by guestfish --add or virt-v2v. Unfortunately xmlParseURI cannot handle URIs with spaces or other non-RFC-compliant characters so simple commands like these fail: $ guestfish -a 'ssh://example.com/virtual machine.img' guestfish: --add: could not parse URI 'ssh://example.com/virtual

This enhances the existing VMX input support allowing it to be used over SSH to the ESXi server. The original command (for local .vmx files) was: $ virt-v2v -i vmx guest.vmx -o local -os /var/tmp Adding ‘-it ssh’ and using an SSH remote path gives the new syntax: $ virt-v2v \ -i vmx -it ssh \ "root@esxi.example.com:/vmfs/volumes/datastore1/guest/guest.vmx" \ -o local

Hi, I cant seem to get my upssched to get called by upsmon. Upsmon -c fsd just shuts down without the message I set or the one in upssched-cmd /etc/ups/upsmon.conf: MONITOR ups6 at localhost 1 <user> <pass> master MONITOR ups8 at localhost 1 <user> <pass> master SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /usr/sbin/upssched NOTIFYMSG

The first patch was previously posted here: https://www.redhat.com/archives/libguestfs/2017-December/msg00018.html That patch hasn't changed except that I made the ‘input_transport’ variable type-safe. The second patch adds a significant new mode for liberating data from VMware: the ability to copy VMs over SSH directly from ESXi hypervisors. Although this requires enabling SSH access (a

This isn't quite the full thing. I think that Pino is also working on replacing the ssh and scp commands in the v2v/input_vmx.ml file with libssh. Without those changes, -i vmx will still issue raw ssh and scp commands, which will use ssh-agent (or keyboard-interactive). The Xen input method doesn't use raw ssh and scp commands, so that one is OK. Rich.

Hi, Dear Mr/Mrs. I have two questions ask for help: my virt-manager and libvirt version is : linux-vaan:~ # rpm -q libvirt libvirt-0.8.5-1.2.i586 linux-vaan:~ # uname -a Linux linux-vaan 2.6.34-12-desktop #1 SMP PREEMPT 2010-06-29 02:39:08 +0200 i686 i386 GNU/Linux linux-vaan:~ # rpm -q virt-manager virt-manager-0.8.5-3.1.i586 linux-vaan:~ # cat /etc/SuSE-release openSUSE 11.3 (i586) VERSION =

I always used IET on CentOS but I have a quick server to setup to backup some VM's, then migrate to DAS on another server and the easiest way for me will be to accomplish this via iSCSI vmfs stores. I figured I would just use the ini that ships with CentOS but have never used it against ESX, anyone do this and have experiences they care to share? Should it be trivial or are there any non

https://bugzilla.samba.org/show_bug.cgi?id=8177 Summary: Problems with big sparsed files Product: rsync Version: 3.0.8 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: joluinfante at gmail.com

We only use xmlParseURI to parse our own "homebrew" URIs, for example the ones used by guestfish --add or virt-v2v. Unfortunately xmlParseURI cannot handle URIs with spaces or other non-RFC-compliant characters so simple commands like these fail: $ guestfish -a 'ssh://example.com/virtual machine.img' guestfish: --add: could not parse URI 'ssh://example.com/virtual

An alternate solution to: https://www.redhat.com/archives/libguestfs/2017-December/msg00035.html "[PATCH] v2v: -i vmx: Allow ssh URLs to use spaces." is to classify all URLs processed by libguestfs as either ordinary URLs or the special non-standard URLs that we use for things like ‘virt-v2v -i vmx’ and ‘guestfish --add’. For the non-standard URLs, provide a wrapper around

Hello All, The version of R I am using is as follows > version _ platform x86_64-pc-linux-gnu arch x86_64 os linux-gnu system x86_64, linux-gnu status major 2 minor 14.1 year 2011 month 12 day 22 svn rev 57956 language R version.string R version 2.14.1 (2011-12-22) I just few days

Previously posted: https://www.redhat.com/archives/libguestfs/2017-December/msg00046.html Rich.

On 16.09.14 15:09, Richard W.M. Jones wrote: > On Tue, Sep 16, 2014 at 05:06:57PM +0300, Shahar Havivi wrote: > > I am using upstream qemu while using this local variables: > > export PATH=/home/shahar/git/qemu:$PATH > > export LIBGUESTFS_HV=/home/shahar/git/qemu/x86_64-softmmu/qemu-system-x86_64 > > > > Is that sufficient? > > Yup, upstream qemu should

On Mon, Apr 19, 2010 at 10:17:07PM +0800, Wilkinson, Alex wrote: > The aforementioned article says that libguestfs supports VMware's > VMDKs. This is partly true. We rely on qemu's support for VMDK which is rather sketchy. In particular, qemu cannot handle some VMDKs from ESX 4.0. However ... > So if these VMDKs live on a vmfs on an ESX server, what do > you recomend as

To Whom It May concern: I found that the following error is caused by adding a scsi disk to install the os, I remove the scsi disk and the error remove but still report 'out of memory': virsh # dumpxml win2003_122 internal error Invalid or not yet handled value '/vmfs/devices/genscsi/mp x.vmhba0:C0:T1:L0' for VMX entry 'scsi0:1.fileName' virsh # list --all Id Name