search for: vmteste

Hi, Is virsh able to access the VMX config of a virtual machine running on a esxi host? I would like to take backups of my virtual machine configs and the doku section "Converting from VMware VMX config to domain XML config" (http://libvirt.org/drvesx.html) comes close to this - but does not tell how to get access to the vmx file. I would prefer a solution where ssh access to the

Hi. This is not a question, I had the following problem and I want to share my solution. ------- I tried to create a new virtual machine with this command: $ virt-install --connect qemu:///system -n vmTeste -r 512 -f /var/lib/libvirt/images/vmTeste.qcow2 -s 2 -c /media/Data/isos/debian-506-amd64-netinst.iso --vnc --noautoconsole --accelerate --hvm And I got this error: ERROR Unable to deny all devices for vmTeste: No such file or directory Traceback (most recent call last): File "/usr/bin...

Hi all! I want to assign a physical network card (e100) to a domU: I think Dom0 is ok but domU does not recognize the pci nic. into DomU I don''t know wath should I see: I have nothing in dmesg nor in messages... Into Dom0 I have this modules.conf: options pciback hide=(0000:03: 08.0) install e100 /sbin/modprobe pciback; /sbin/modprobe --ignore-install e100 This is dmesg: pciback

Hi, I have another question, when I do the blockcommit command and get the result " Top image as the active layer is currently unsupported ", is it being developed? root@cvk-31:/vms/images# virsh blockcommit Vmtest /vms/images/Vmtest1;echo $? error: internal error unable to execute QEMU command 'block-commit': Top image as the active layer is currently unsupported 1 But as I

I had test the command virsh blockcommit, but it failed, with the libvirt version 1.1.0, and qemu version 1.6.0. Is this feature being developing? Thanks root at cvk-31:/vms/images# virsh -v 1.1.0 root at cvk-31:/vms/images# qemu-img -V qemu-img version 1.6.0, Copyright (c) 2004-2008 Fabrice Bellard usage: qemu-img command [command options] root at cvk-31:/vms/images# virsh blockcommit Vmtest

Dear all, I followed the steps described in the wiki in order to get an Arnadle board running Xen, but I''m having trouble in starting a domU. Let me describe you the steps I followed. Sorry for such a long mail, but I think that a verbose description is necessary so you can point me what I''m doing wrong. I couldn''t boot properly over the network. This is why I

On Tue, Feb 28, 2023 at 07:04:33PM +0000, Bobby Eshleman wrote: > Add support for sockmap to vsock. > > We're testing usage of vsock as a way to redirect guest-local UDS > requests to the host and this patch series greatly improves the > performance of such a setup. > > Compared to copying packets via userspace, this improves throughput by > 121% in basic testing.

My server was installed as a "minimal install" in text mode, so there may be some difference between my setup and your laptop. Are you able to email the output of "systemctl list-unit-files" to me so that I can see what services are enabled? I tried installing a couple of the other drivers mentioned in the log file... # dnf install libvirt-daemon-driver-lxc # dnf install

Hi, I am seeing a problem with a earlier working domain configuration. Here is the domain xml file. I am not getting the virsh console now. I am trying this on RHEL 6.0. Here is the list of steps that I am using: [root at krm1 test]# virsh define vmtest.xml Domain vmtest3 defined from vmtest.xml [root at krm1 test]# virsh start vmtest3 Domain vmtest3 started [root at krm1 test]# virsh

Hi, I am using libvirt and virsh for my application. I am trying to manage snapshots for my infrastructure. All virsh commands are working fine like snapshot-create, delete, list, revert, current. But when I try to do the same using libvirt, I get out of memory error. Here are the commands that i execute on my host in a python shell... import libvirt conn =

Hi, I''m trying to install Xen on Ubuntu 11.04. I read somewhere (please correct me if this is wrong) that Ubuntu hasn''t had dom0 support since 8.04 LTS, and the recommended action was to grab a dom0-enabled kernel from Debian, so I did. I''m running 2.6.32-5-xen-amd64 and built Xen 4.1.1 from source. After installation and some troubleshooting, I tried to start

Hi, I am trying to upgrade my Xen host (Dom0) and are having troubles getting it to work. I think that it has booted into a kernel that supports Xen (running 'xl info' does list some Xen capabilities), but I have three problems (that I have found so far). Firstly, the "libvirtd" daemon doesn't start on bootup (and as a result all 'virsh' commands fail). It

Also includes a couple minor model changes to support better error reporting. This method was added so that a client could submit multiple vms to the service layer in one call and get back appropriate messages showing any failures without those failures also causing the entire call to fail, or forcing the client to implement handling (begin/rescue blocks) of these errors to continue through the

[dropping libvir-list - this is a usage question, not a development question] On 09/02/2013 11:29 PM, Guozhonghua wrote: > I had test the command virsh blockcommit, but it failed, with the libvirt version 1.1.0, and qemu version 1.6.0. > Is this feature being developing? Thanks The feature is supported, but you have to use it correctly. In particular, your backing chain MUST label the

On 09/03/2013 06:56 PM, Guozhonghua wrote: > Hi, > > I have another question, when I do the blockcommit command and get the result " Top image as the active layer is currently unsupported ", is it being developed? > root@cvk-31:/vms/images# virsh blockcommit Vmtest /vms/images/Vmtest1;echo $? > error: internal error unable to execute QEMU command 'block-commit':

On 07/23/2017 04:25 PM, G Crowe wrote: > Hi, > I am trying to upgrade my Xen host (Dom0) and are having troubles getting > it to work. > > I think that it has booted into a kernel that supports Xen (running 'xl info' > does list some Xen capabilities), but I have three problems (that I have found > so far). > > Firstly, the "libvirtd" daemon

This resend includes the rebase, but fixes a problem I just noticed with nil/empty checks.

This is a resend of the 2-patch series from a week or so ago, needed to be rebased due to some commits on next

The following two patches should be applied in the order: * [PATCH server] Add svc_vm_actions method to VmService. * [PATCH server] Cloud UI layer to initiate actions on vms. The service layer patch should work fine on its own (and not break anything), but cloud patch relies on service being there.

Note that this does not help with the original problem but points out a critical design flaw. To me your it infrastructure design has no working disaster recovery plan. You should always be able to access critical functionality and from there be able to restore complete functionality step by step. In your case the outermost functionality is the vm host. You should always be able to log into that