April 2010 - Devel - Libvirt List Archives

by Ganesh Pagade

Hello, I am planning to develop a management application for managing Redhat Xen and Redhat KVM hypervisors. I am evaluating the Java bindings versus the C++ version of libvirt. As part of evaluation, I could not find meaningful answers to the questions below. Hence, I thought that people on this mailing list would be the most appropriate to comment on them. Can you please let me know your views? 1. Are all functions that are available in C API available in Java? 2. Are Java bindings added along with every enhancement to C API? 3. If answer to above question is negative, typically how long does it takes for the addition of Java bindings for the enhancement? 4. Most of libvirt based third party management applications use which of Java bindings or C API? 5. What are your good/bad experiences while using either of C API or Java bindings? 6. What is your concluding personal recommendation? And finally, since libvirt is a Redhat Emerging Technology project, does Redhat or any other third party service providers provide paid assistance, support? Appreciate your time. Thanks. Regards, Ganesh

15 years, 1 month

3
2
0 / 0

[libvirt] [PATCH 0/6]: Domain Snapshot API

by Chris Lalancette

Hello, Here is the next set of patches for the snapshot API. This set is much more complete, and implements the virDomainRevertToSnapshot() semantic instead of virDomainCreateFromSnapshot() that we discussed earlier. I've also incorporated all of the comments from the review of the first round of patches. Aside from implementation bugs, I consider this patchset complete. The only thing missing from the patches is real documentation along the lines of the API docs that we had discussed on-list. Next week I'll followup with some additions to the documentation that explain the semantics of these calls. Again review and comments are welcome. Chris Lalancette

15 years, 1 month

6
24
0 / 0

[libvirt] [PATCH] Rename virsh "revert-to-snapshot" to "snapshot-revert"

by Chris Lalancette

Signed-off-by: Chris Lalancette <clalance(a)redhat.com> --- tools/virsh.c | 10 +++++----- tools/virsh.pod | 4 ++-- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/tools/virsh.c b/tools/virsh.c index 8017beb..d5fe6c4 100644 --- a/tools/virsh.c +++ b/tools/virsh.c @@ -8514,22 +8514,22 @@ cleanup: } /* - * "revert-to-snapshot" command + * "snapshot-revert" command */ -static const vshCmdInfo info_revert_to_snapshot[] = { +static const vshCmdInfo info_snapshot_revert[] = { {"help", N_("Revert a domain to a snapshot")}, {"desc", N_("Revert domain to snapshot")}, {NULL, NULL} }; -static const vshCmdOptDef opts_revert_to_snapshot[] = { +static const vshCmdOptDef opts_snapshot_revert[] = { {"domain", VSH_OT_DATA, VSH_OFLAG_REQ, N_("domain name, id or uuid")}, {"snapshotname", VSH_OT_DATA, VSH_OFLAG_REQ, N_("snapshot name")}, {NULL, 0, 0, NULL} }; static int -cmdDomainRevertToSnapshot(vshControl *ctl, const vshCmd *cmd) +cmdDomainSnapshotRevert(vshControl *ctl, const vshCmd *cmd) { virDomainPtr dom = NULL; int ret = FALSE; @@ -8786,7 +8786,7 @@ static const vshCmdDef commands[] = { {"snapshot-delete", cmdSnapshotDelete, opts_snapshot_delete, info_snapshot_delete}, {"snapshot-dumpxml", cmdSnapshotDumpXML, opts_snapshot_dumpxml, info_snapshot_dumpxml}, {"snapshot-list", cmdSnapshotList, opts_snapshot_list, info_snapshot_list}, - {"revert-to-snapshot", cmdDomainRevertToSnapshot, opts_revert_to_snapshot, info_revert_to_snapshot}, + {"snapshot-revert", cmdDomainSnapshotRevert, opts_snapshot_revert, info_snapshot_revert}, {NULL, NULL, NULL, NULL} }; diff --git a/tools/virsh.pod b/tools/virsh.pod index 46ba813..4af5603 100644 --- a/tools/virsh.pod +++ b/tools/virsh.pod @@ -819,12 +819,12 @@ List all of the available snapshots for the given domain. Output the snapshot XML for the domain's snapshot named I<snapshot>. -=item B<revert-to-snapshot> I<domain> I<snapshot> +=item B<snapshot-revert> I<domain> I<snapshot> Revert the given domain to the snapshot specified by I<snapshot>. Be aware that this is a destructive action; any changes in the domain since the snapshot was taken will be lost. Also note that the state of the domain after -revert-to-snapshot is complete will be the state of the domain at the time +snapshot-revert is complete will be the state of the domain at the time the original snapshot was taken. =item B<snapshot-delete> I<domain> I<snapshot> I<--children> -- 1.6.6.1

15 years, 1 month

2
2
0 / 0

[libvirt] [PATCH 0/2]: Two small fixes

by Luiz Capitulino

Two small issues I found while testing libvirt under QMP, there is also a third I won't fix today: dommemstat doesn't work under QMP.

15 years, 1 month

2
5
0 / 0

[libvirt] [PATCH 0/2] Enhance checking of supported flags in drivers

by Jiri Denemark

I think we need a simple and consistent way of checking whether flags passed to API entry points in drivers are valid/supported or not. So far some entry points don't check flags at all and some checks for 0 when no flags are expected/supported. The first patch introduces a macro which can be called with a whitelist of supported flags (more info about it inside the patch). I don't particularily like introducing a new header file but non of existing header files looked like a good place to stick this macro in. If you think such a place exist, I'll be very happy to adapt the patch. The second patch changes all API calls introduced since the last release to use the macro for checking valid flags. I'm not sure if we can change existing API calls to do the same as it could break some badly written apps which pass invalid flags. My opinion is that we may often do that as such apps don't use the API in a documented/valid way. But even if my thinking is correct, we don't want to change it before 0.8.0. Jirka Jiri Denemark (2): Introduce virCheckFlags for consistent flags checking Use virCheckFlags for APIs added in 0.8.0 src/Makefile.am | 3 +- src/esx/esx_driver.c | 44 ++++++++++++------------- src/nwfilter/nwfilter_driver.c | 5 ++- src/qemu/qemu_driver.c | 69 +++++++++++++++++++--------------------- src/storage/storage_driver.c | 7 +--- src/util/checks.h | 37 +++++++++++++++++++++ src/vbox/vbox_tmpl.c | 42 +++++++++++++++++------- src/xen/xend_internal.c | 5 +++ 8 files changed, 133 insertions(+), 79 deletions(-) create mode 100644 src/util/checks.h

15 years, 1 month

2
3
0 / 0

[libvirt] [PATCH] nwfilter: Fix memory leak on daemon init and shutdown

by Stefan Berger

This patch fixes a memory leak on daemon init and shutdown. The module was initialized twice and not shut down. Signed-off-by: Stefan Berger <stefanb(a)us.ibm.com>

15 years, 1 month

2
2
0 / 0

[libvirt] libvirt Error Domain didn't show up

by Roche, Christian (EXT-Other - MA/Rabat)

Hi there, I'm trying to use kvm on CentOS 5.4 64-bit to virtualize Windows Server 2003. I've been able to install and start the system using 1GB of memory, however when I try to increase the amount of memory available to the VM to 4GB by editing /etc/libvirt/qemu/windows2003.xml, I get the following message when starting the VM through virt-manager: --------------------------------- Error starting domain: internal error Domain windows2003 didn't show up Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 498, in run_domain vm.startup() File "/usr/share/virt-manager/virtManager/domain.py", line 573, in startup self.vm.create() File "/usr/lib64/python2.4/site-packages/libvirt.py", line 287, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: internal error Domain windows2003 didn't show up --------------------------------- Here is the content of /var/log/libvirt/qemu/windows2003.log : --------------------------------- LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin /usr/bin/qemu-system-x86_64 -S -M pc -no-kqemu -m 4096 -smp 4 -monitor pty -pidfile /var/run/libvirt/qemu//windows2003.pid -localtime -boot c -hda /dev/mapper/Raid5-Windows -cdrom /var/lib/libvirt/images/viostor.iso -net nic,macaddr=54:52:00:07:a9:b6,vlan=0 -net tap,fd=16,script=,vlan=0,ifname=vnet0 -serial pty -parallel none -usb -usbdevice tablet -vnc 127.0.0.1:0 -k fr QEMU PC emulator version 0.9.0, Copyright (c) 2003-2007 Fabrice Bellard usage: qemu [options] [disk_image] 'disk_image' is a raw hard image image for IDE hard disk 0 Standard options: -M machine select emulated machine (-M ? for list) -fda/-fdb file use 'file' as floppy disk 0/1 image -hda/-hdb file use 'file' as IDE hard disk 0/1 image blah blah blah --------------------------------- It looks like qemu is unhappy about the memory parameter. Here is my config: >uname -a Linux silver 2.6.18-164.15.1.el5 #1 SMP Wed Mar 17 11:30:06 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux >grep virt /var/log/rpmpkgs libvirt-0.6.3-20.1.el5_4.x86_64.rpm libvirt-python-0.6.3-20.1.el5_4.x86_64.rpm python-virtinst-0.400.3-5.el5.noarch.rpm virt-manager-0.6.1-8.el5.x86_64.rpm Any idea ? Thanks, Christian Roche NSN/Rabat +212 6 61 44 11 71

15 years, 1 month

1
0
0 / 0

Re: [libvirt] Domain not stable while created...

by Sankamesh

Thanks Mr. Stefan Will that crash mainly be due to the kernel ? Since am not sure about that,else I should try with different image. When I use via a config file using "xm create libvirt-ttylinux.conf ", then the domain runs stable.... But when I use the virsh -c xen:/// define libvirt-ttylinux.xml" and "virsh start ttyimage, it crashes after sometime. The ibvirt-ttylinux.conf file :: -------------------------------------------------------------------------------------------------------------------------------- kernel = "/boot/vmlinuz-2.6.18-164.2.1.el5xen" ramdisk= "/boot/initrd-2.6.18-164.2.1.el5xen.img" memory = 64 name = "ttylinux" disk = ['file:/usr/local/ttylinux-xen-libvirt/ttylinux-xen.img,sda1,w'] root = "/dev/sda1 ro" vif = [''] -------------------------------------------------------------------------------------------------------------------------------- I give the same Xen kernel parameter here in xml file, and use virsh to create domain --------------------------------------------------------------------------------------------------------------------------------------- <?xml version="1.0" encoding="utf-8"?> <domain type='xen'> <name>ttyimage</name> <os> <type>linux</type> <kernel>/boot/vmlinuz-2.6.18-164.2.1.el5xen</kernel> <initrd>/boot/initrd-2.6.18-164.2.1.el5xen.img</initrd> </os> <memory>65536</memory> <vcpu>1</vcpu> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <graphics type='vnc' port='5900'/> <disk type='file'> <source file='/usr/local/ttylinux-xen-libvirt/ttylinux-xen.img' /> <target dev='sda1' /> </disk> <interface type='bridge'> <source bridge='virbr0' /> <mac address='00:1d:60:ec:ae:1c' /> <target dev='testnimb-0' /> </interface> </devices> </domain> --------------------------------------------------------------------------------------------------------------------------------------- My Boot grub file data:: --------------------------------------------------------------------------------------------------------------------------------------title Scientific Linux (2.6.18-164.2.1.el5xen) root (hd0,0) kernel /xen.gz-2.6.18-164.2.1.el5 module /vmlinuz-2.6.18-164.2.1.el5xen ro root=LABEL=/1 rhgb quiet module /initrd-2.6.18-164.2.1.el5xen.img -------------------------------------------------------------------------------------------------------------------------------------- Why is this difference between the xm (when i destroy the image,domain is also destroyed) and virsh (domain is not destroyed while destroying the image) . I doubt that am making some mistake with the xml file .... Is that true? Kindly give some suggestions Thanks ________________________________ libvir-list-bounces(a)redhat.com wrote on 04/10/2010 09:47:17 AM: > libvir-list > > Hello, > > Thanks Alex > > I created a domain using "virsh -c xen:/// define libvirt-ttylinux.xml" and > "virsh start ttyimage" for a simple ttyimage. > > Problem I face is that the image shutsdown immedialtely once virsh > start guest is typed. > I checked the Xend Logs > ---------------------------------------------------------------------------------------------------------- > ---[2010-04-11 07:08:02 xend 3155] DEBUG (DevController:116) > DevController: writing {'frontend-id': '6', 'domain': 'ttyimage', [...] > [2010-04-11 07:08:02 xend 3155] DEBUG (vfbif:11) Spawn: ['/usr/lib/ > xen/bin/qemu-dm', '-M', 'xenpv', '-d', '6', '-domain-name', > 'ttyimage', '-vnc', '127.0.0.1:0', '-vncunused', '-k', 'en-us'] > [2010-04-11 07:08:02 xend.XendDomainInfo 3155] DEBUG > (XendDomainInfo:992) Storing VM details: {'shadow_memory': '0', > 'uuid': 'd5e916b0-bc2d-01f9-8156-4808c754f67a', 'on_reboot': > 'restart', 'start_time': '1270937282.29', 'on_poweroff': 'destroy', > 'name': 'ttyimage', 'xend/restart_count': '0', 'vcpus': '1', > 'vcpu_avail': '1', 'memory': '64', 'on_crash': 'destroy', 'image': > '(linux (kernel /boot/vmlinuz-2.6.18-164.2.1.el5xen))', 'maxmem': '64'} > [2010-04-11 07:08:02 xend.XendDomainInfo 3155] DEBUG > (XendDomainInfo:1027) Storing domain details: {'console/ring-ref': > '65674', 'console/port': '2', 'name': 'ttyimage', 'console/limit': > '1048576', 'vm': '/vm/d5e916b0-bc2d-01f9-8156-4808c754f67a', > 'domid': '6', 'cpu/0/availability': 'online', 'memory/target': > '65536', 'store/ring-ref': '65675', 'store/port': '1'} > [2010-04-11 07:08:02 xend.XendDomainInfo 3155] DEBUG > (XendDomainInfo:1249) XendDomainInfo.handleShutdownWatch > [2010-04-11 07:08:02 xend 3155] DEBUG (DevController:158) Waiting > for devices vif. > [2010-04-11 07:08:02 xend 3155] DEBUG (DevController:164) Waiting for 0. > [2010-04-11 07:08:02 xend 3155] DEBUG (DevController:509) > hotplugStatusCallback /local/domain/0/backend/vif/6/0/hotplug-status. > [2010-04-11 07:08:51 xend 3155] INFO (XendDomain:387) Domain > ttyimage (6) unpaused. > [2010-04-11 07:08:54 xend.XendDomainInfo 3155] WARNING > (XendDomainInfo:1177) Domain has crashed: name=ttyimage id=6. You domain crashed here... Is the VM image and kernel in that image known to work? Regards, Stefan Send free SMS to your Friends on Mobile from your Yahoo! Messenger. Download Now! http://messenger.yahoo.com/download.php

15 years, 1 month

2
1
0 / 0

[libvirt] about qemu monitor mode.

by Osier Yang

Hello there libvirt compiles JSON mode as the default qemu monitor mode if yajl-devel is available. As a result of this solution, the user has no way to change into the text mode. And because the qemu QMP always lacks commands currently, such as "savevm", it will prevent us creating the snapshot of domain, especially for us who want to do some testing. What I think is could we add the configuration item in qemu.conf? so that the user can choose which mode to use, such as: monitor_mode=json #monitor_mode=text Regards osier

15 years, 1 month

2
1
0 / 0

[libvirt] libvirt: C++ or Java

by Gokhale, Shashibhushan

Hello, I am planning to develop a management application for managing Redhat Xen and Redhat KVM hypervisors. I am evaluating the Java bindings versus the C++ version of libvirt. As part of evaluation, I could not find meaningful answers to the questions below. Hence, I thought that people on this mailing list would be the most appropriate to comment on them. Can you please let me know your views? 1. Are all functions that are available in C API available in Java? 2. Are Java bindings added along with every enhancement to C API? 3. If answer to above question is negative, typically how long does it takes for the addition of Java bindings for the enhancement? 4. Most of libvirt based third party management applications use which of Java bindings or C API? 5. What are your good/bad experiences while using either of C API or Java bindings? 6. What is your concluding personal recommendation? And finally, since libvirt is a Redhat Emerging Technology project, does Redhat or any other third party service providers provide paid assistance, support? Thanks, Shashi

15 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Devel April 2010