similar to: esx: upload the volume

Hi all, I still experience vm crashes with glusterfs. The VM I had problems (kept on crashing) was moved away from gluster and have had no problems since. Now another VM is doing the same. It just shutsdown. gluster is 3.8.13 I know now you are on 3.10 and 3.12, but I had troubles upgrading another cluster to 3.10 (although the processes were off and no files where in use gluster had to heal

Hi, I am trying to start a node using libvirt on ESX hypervisor. Before starting I am performing the following steps: 1) vol-create datastore1 /local/new_volume.xml (Creating a volume in pool) 2) define /local/esxdomain.xml (Defining a node) 3) start MyNode (Starting a node) I tried to get the status of my node and it is showing *running *but I am not able to ping my node (as it is in network).

Hi, I am currently using libvirt API(java api) for creating VMs in esxi host. I am passing commands as follows:(trying from terminal) virsh -c esx://192.168.0.144?no_verify=1 define /home/bm/eee.xml Domain eee defined from /home/bm/eee.xml I have attached the eee.xml file and the eee.vmx from the esxi datastore with this mail. the versions i am using is : virsh # version Compiled against

Hi. VMWare has an own/modified mboot.c32, which is capable of using Configfiles. This mboot.c32 is on every Installsystem for their ESXi hypervisor install-iso. Until syslinux 4.07 this works with pxelinux out of the box. Since 5.x this mboot.c32 will not work anymore. There seem to be more modifications than only a parameter "-c". Does anyone has an idea what has changed so this

If an ESX guest has a snapshot, the path the libvirt driver gives us will look like: [yellow:storage1] RHEL4-X/RHEL4-X-000003.vmdk instead of: [yellow:storage1] RHEL4-X/RHEL4-X.vmdk The current path mangling code does take this into account. This change makes it use the current mechanism first, but try again after removing a '-\d+' suffix if it gets a 404. Trying twice should make it

Hello, I am trying to access an ESXi host using libvirt but it seems that it requires netcat to be running on the ESX server. My ESX 4 does not have this installed and I am wondering if this is required or is there some other way to get this working? Thanks, Jon

hi, I am a new user of libvirt ,i really appreciate libvirt?and want to use it in my work.I want to use it to conncet to a ESXi server.when I try to connect to the server ,I use the command :virsh -c esx://name at exmaple.com,And I get an 1.error :error: internal error curl_easy_perform() returned an error: Couldn't connect to server (7) : couldn't connect to host so I think maybe

Hi, is there some easy way how to shut down vmware ESXi host? We have same apc smart 1500 and I passed usb port into one virtual linux, so it can monitor ups state via NUT. So how can i make esx server avare of low battery? Maybe using vsphere-cli utils? With regards Libor -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type:

2015-04-01 18:25 GMT+02:00 Paul Apostolescu <apbogdan@gmail.com>: > I want to create a virtual machine from scratch in ESX but I can't figure > out how to create the disks - the vmdk files. Any hints on how that can be > done or even if it's possible at all ? You can use the following virsh command: vol-create-as --pool ds --name test/disk.vmdk --capacity 10737418240

Hello, I’m running virsh v1.1.3 compiled on a ubuntu system with the "--with-esx=yes” support. root@kvm-189:/home/cisco# virsh --version 1.1.3 I also have a vcenter 5.5 environment that has following structure (couple of hosts at datacenter level, others part of cluster group): MIC-VC-ADMIN MIC-DC-ADMIN 10.58.6.110 10.58.6.113 MIC-CL-ADMIN 10.58.6.109 10.58.6.118

Dear Paul, Depending on how you want to create them, qemu-img tool might be what you're looking for. It can create empty vmdk disk images: qemu-img create -f vmdk ... Cheers, On 04/01/2015 06:25 PM, Paul Apostolescu wrote: > I want to create a virtual machine from scratch in ESX but I can't figure > out how to create the disks - the vmdk files. Any hints on how that can be >

Hi, I have started a virtual machine on my ESXi server. I was trying to attach a console to it but when I executed the command I got a message saying that *"Attaching a console is not supported in the current hypervisor." *Is there any way (patch or something) through which I can attach a console to my VM. The ESX version is 5.1 and I am using latest version of libvirt. Regards, Varun

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 =

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:

Hi! I try to integrate ESXi guests to beaker. I'd like to have dynamic installations of guests just like KVM and Xen is done. I know that virt-install is not currently supported by libvirt, so I'd like to ask, do you plan to add esxdrv support for virt-install? What's current status? Thank you, Filip

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:

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

The $vmdk value is a directory name in ESX.pm, although the later codes replace '/' with '_', the volume name isn't still friendly, for example, it looks like this: # virsh vol-list pool-dir Name Path ----------------------------------------- esx4.1-rhel6.2-x86_64_esx4.1-rhel6.2-x86_64

On Wed, Sep 17, 2014 at 10:58:18AM +0300, Shahar Havivi wrote: > 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

I want to create a virtual machine from scratch in ESX but I can't figure out how to create the disks - the vmdk files. Any hints on how that can be done or even if it's possible at all ? Thanks