Re: [libvirt] Reusing dumpxml output
You need to take care of only two parameters ID and VNC port, other things will remain. If you want to put different path for disk you can do that as well. API is already available to define by you own xml. Even if you don't modify the id/vnc it doesn't matter, everything is taken care by libvirt. On Thu, 2008-08-14 at 01:04 +0200, Stefan de Konink wrote: I would like to reuse configurations that have been edited using the libvirt api. For example by attaching interfaces. Now the output that dumpxml generates, is very 'specific' to an active configuration. I am not able to use a stored configuration from an active domain to redefine it after it has been undefined. Is there a trick to do so? Or should one really strip all 'live' attributes first? Stefan -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list Thanks Regards --Ajish -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Reusing dumpxml output
On Thu, 14 Aug 2008, ajishrao wrote: You need to take care of only two parameters ID and VNC port, other things will remain. If you want to put different path for disk you can do that as well. API is already available to define by you own xml. Even if you don't modify the id/vnc it doesn't matter, everything is taken care by libvirt. Technically the VIF also changes, and what I see if I completely reuse the config, it automatically gets a bootloader / (I think it changes to hvm) Stefan -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH] Fix serial console telnet protocol support
Hi Mark, On Wed, Aug 13, 2008 at 06:44:28PM +0100, Mark McLoughlin wrote: With e.g.: serial type='tcp' source mode='bind' host='127.0.0.1' service=''/ protocol type='telnet'/ target port='0'/ /serial You currently get: Unknown option: listen qemu: could not open serial device 'telnet:127.0.0.1:,listen' With the telnet protocol, qemu expects server as an option rather than listen. Not that I'm qualified to comment on this but a testcase in tests/qemuxml2argv* would prevent breaking this in the future. Cheers, -- Guido -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] fail to run virsh
Hi, I installed libvirt (cvs version), and can confirm that libvirtd is running. However, virsh failed to work. I got the below message when running virsh with debugging information. How to fix this problem? Many thanks, Jun # LIBVIRT_DEBUG=1 virsh DEBUG: libvirt.c: virInitialize (register drivers) DEBUG: libvirt.c: virConnectOpenAuth (name=(null), auth=0xb7f53b84, flags=0) DEBUG: libvirt.c: do_open (Probed qemu:///system) DEBUG: lxc_driver.c: lxcCheckContainerSupport (clone call returned EINVAL, container support is not enabled) DEBUG: libvirt.c: do_open (Using qemu:///system as default URI, 1 hypervisor found) DEBUG: libvirt.c: do_open (name qemu:///system to URI components: scheme qemu opaque (null) authority (null) server (null) user (null) port 0 path /system ) DEBUG: libvirt.c: do_open (trying driver 0 (Test) ...) DEBUG: libvirt.c: do_open (driver 0 Test returned DECLINED) DEBUG: libvirt.c: do_open (trying driver 1 (QEMU) ...) DEBUG: libvirt.c: do_open (driver 1 QEMU returned DECLINED) DEBUG: libvirt.c: do_open (trying driver 2 (Xen) ...) DEBUG: libvirt.c: do_open (driver 2 Xen returned DECLINED) DEBUG: libvirt.c: do_open (trying driver 3 (OPENVZ) ...) DEBUG: libvirt.c: do_open (driver 3 OPENVZ returned DECLINED) DEBUG: libvirt.c: do_open (trying driver 4 (LXC) ...) DEBUG: libvirt.c: do_open (driver 4 LXC returned DECLINED) DEBUG: libvirt.c: do_open (trying driver 5 (remote) ...) DEBUG: remote_internal.c: doRemoteOpen (proceeding with name = qemu:///system) libvir: Remote error : No such file or directory DEBUG: libvirt.c: do_open (driver 5 remote returned ERROR) DEBUG: hash.c: virUnrefConnect (unref connection 0x806b588 qemu:///system 1) DEBUG: hash.c: virReleaseConnect (release connection 0x806b588 qemu:///system) error: failed to connect to the hypervisor -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Reusing dumpxml output
On Thu, 2008-08-14 at 09:42 +0200, Stefan de Konink wrote: On Thu, 14 Aug 2008, ajishrao wrote: You need to take care of only two parameters ID and VNC port, other things will remain. If you want to put different path for disk you can do that as well. API is already available to define by you own xml. Even if you don't modify the id/vnc it doesn't matter, everything is taken care by libvirt. Technically the VIF also changes, and what I see if I completely reuse the config, it automatically gets a bootloader / (I think it changes to hvm) You are right thats why it uses script in VIF to manage it. Yes you can use complete config. I really didn't understand your concern about bootloader/ can you elaborate little more Stefan Thanks Regards --Ajish -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Reusing dumpxml output
On Thu, Aug 14, 2008 at 09:42:09AM +0200, Stefan de Konink wrote: On Thu, 14 Aug 2008, ajishrao wrote: You need to take care of only two parameters ID and VNC port, other things will remain. If you want to put different path for disk you can do that as well. API is already available to define by you own xml. Even if you don't modify the id/vnc it doesn't matter, everything is taken care by libvirt. Technically the VIF also changes, and what I see if I completely reuse the config, it automatically gets a bootloader / (I think it changes to hvm) The target dev='vifXXX' element is ignored when creating a VM if it contains an auto-allocated VIF name. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Reusing dumpxml output
On Thu, 14 Aug 2008, Daniel P. Berrange wrote: On Thu, Aug 14, 2008 at 01:04:56AM +0200, Stefan de Konink wrote: I would like to reuse configurations that have been edited using the libvirt api. For example by attaching interfaces. Now the output that dumpxml generates, is very 'specific' to an active configuration. I am not able to use a stored configuration from an active domain to redefine it after it has been undefined. Is there a trick to do so? Or should one really strip all 'live' attributes first? The XML is supposed to be idempotent - the XML you get from 'dumpxml' should be able to be fed back into 'create' resulting in exactly the same VM config. Previously there were a few places where you had to tweak the XML, eg to remove the auto-allocated VNC port, or remove the VIF target device name. In current CVS those issues are all fixed, so you should not have to change anything in the XML. So any further problems in this area are definitely bugs. There is also the option to request the 'inactive' XML dump for a running domain which removes any auto-allocated params. This is just a convenience though, and not required for re-creating the VM later. Do you see the bootloader / bug? Or am I using a buggy git version? I'll try the inactive parameter, that should be better in general. Stefan -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: Bug with bootloader / (Re: [libvirt] Reusing dumpxml output)
On Thu, Aug 14, 2008 at 10:48:20AM +0200, Stefan de Konink wrote: Output from dumpxml: domain type='xen' id='-1' nameunittest_200808081319_00010/name uuid380ac319-6b7c-a471-305c-e467c1672c73/uuid bootloader/ os typelinux/type kernel/usr/lib/xen/boot/linux-2.6.20-xen-r6/kernel cmdline root=/dev/xvda ro/cmdline /os memory131072/memory vcpu1/vcpu on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices disk type='file' device='disk' driver name='tap' type='aio'/ source file='/mnt/images/unittest_200808081319_1'/ target dev='xvda' bus='xen'/ /disk interface type='bridge' source bridge='xenbr0'/ target dev='vif-1.0'/ mac address='00:16:3E:00:00:1E'/ ip address='85.17.131.40'/ script path='vif-bridge'/ /interface console type='pty' target port='0'/ /console /devices /domain Can you provide the corresponding output of 'xm list --long unittest_200808081319_00010' The handling of bootloaders has changed in XenD so many times I wouldn't be surprised if we have a bug in this area with certain Xen versions. *bootloader was never specified* Now if I create that file again look at the changes: domain type='xen' id='-1' nameunittest_200808081319_00010/name uuid380ac319-6b7c-a471-305c-e467c1672c73/uuid bootloader/ os typelinux/type /os memory131072/memory vcpu1/vcpu on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices disk type='file' device='disk' driver name='tap' type='aio'/ source file='/mnt/images/unittest_200808081319_00010_1'/ target dev='xvda' bus='xen'/ /disk interface type='bridge' source bridge='xenbr0'/ target dev='vif-1.0'/ mac address='00:16:3E:00:00:1E'/ ip address='85.17.131.40'/ script path='vif-bridge'/ /interface console type='pty' target port='0'/ /console /devices /domain Looks interesting he :) This is clearly broken - can you provide the 'xm list --long' output at this time too, so we can see where the kernel/initrd went. Also the '/var/log/xen/xend.log' file wil show us what config was passed to Xen at VM creation time. Now the only way to get the os / childnodes back is to remove the bootloader node. I think we can see this as a bug :) Absoutely - please file a BZ with all this xm list info the XML files at http://bugzilla.redhat.com Under the 'Virtualization Tools' product, and 'libvirt' componet. Then we can see about fixing it adding another test case to ensure it doesn't break again Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: Bug with bootloader / (Re: [libvirt] Reusing dumpxml output)
On Thu, 14 Aug 2008, Stefan de Konink wrote: On Thu, 14 Aug 2008, Daniel P. Berrange wrote: Then we can see about fixing it adding another test case to ensure it doesn't break again I'm going to upgrade to the latest git to be sure, I'll report back soon. New version fixes the issue. I still have another issue with respect to a segmentation fault on exit (libvirtd), but i'm not able to reproduce it consistently. (I think it is with respect to an umount) Stefan -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] [PATCH] Delete veth devices during lxcVMCleanup
This makes sure to delete veth devices after we've killed the container.
In the case of a destroy or crash, this ensures the system is cleaned
up properly.
To be applied atop Daniel Berrange's current LXC patch stack.
diff -r b18ae864eb98 -r cd0bd9a6288a src/lxc_driver.c
--- a/src/lxc_driver.c Wed Aug 13 09:40:08 2008 -0700
+++ b/src/lxc_driver.c Thu Aug 14 08:50:49 2008 -0700
@@ -375,6 +375,7 @@
int rc = -1;
int waitRc;
int childStatus = -1;
+virDomainNetDefPtr net;
while (((waitRc = waitpid(vm-pid, childStatus, 0)) == -1)
errno == EINTR)
@@ -403,6 +404,11 @@
vm-pid = -1;
vm-def-id = -1;
vm-monitor = -1;
+
+for (net = vm-def-nets; net; net = net-next) {
+vethInterfaceUpOrDown(net-ifname, 0);
+vethDelete(net-ifname);
+}
return rc;
}
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH] get memory in openvz driver
On Thu, Aug 14, 2008 at 06:08:31PM +0400, Evgeniy Sokolov wrote: On Wed, Aug 13, 2008 at 12:50:33PM +0400, Evgeniy Sokolov wrote: OpenVZ has several parameters for memory management. All of them can be configured independetly. Summing all the different memory limits together is wrong - this will make it impossible to implement a 'setMemory' operation because you've now no way of deciding which parameter to set. It is correct calcuation of total memory. Because of non-obvious implenetation of 'setMemory', I have asked 'how to manage memory' in begining. I propouse to set some portion of 'memory' to each limit. I don't think that will be lead to good behaviour - ultimtely I think we'll need to expose more (all?) of these memory settings directly as tunable resources. Good idea! 5 setting for low memory + application THus for the 'memory' setting we which pick the value which provides the primary memory size as available to apps within the container. In my testing the total memory inside a OpenVZ container seems to correspond to the 'lockedpages' parameter, so we should just return that value. How did you get total memory? Most big part of memory is oomguarpages (by default). Lockedpages is about %1. I've just found read these descriptions... http://wiki.openvz.org/Oomguarpages#oomguarpages http://wiki.openvz.org/Oomguarpages#privvmpages http://wiki.openvz.org/Vmguarpages#vmguarpages To summarize Oomguarpages parameter accounts the total amount of memory and swap space used by the processes of a particular container. Privvmpages parameter accounts allocated (but, possibly, not used yet) memory. The accounted value is an estimation how much memory will be really consumed when the container's applications start to use the allocated memory. Consumed memory is accounted into oomguarpages parameter vmguarpages parameter controls how much memory is available to the Virtual Environment (i.e. how much memory its applications can allocate by malloc(3) or other standard Linux memory allocation mechanisms The memory allocation guarantee (vmguarpages) is a primary tool for controlling the memory available to containers, because it allows administrators to provide Service Level Agreements So from those I'd think that 'vmguarpages' maps best into libvirt's concept of 'memory'. Though perhaps 'oomguardpages' could be set for 'memory' and 'vmguarpages' used for 'max memory' Oomguarpages Privvmpages vmguarpages are settings for apps memory. We may 1 set 'memory' to 'privvmpages' - then free will show correct value. 2 set 'memory' to 'vmguarpages' or 'oomguardpages' and 'maxmemory' to 'privvmpages'. What do 'MaxMemory' mean for other libvirt drivers? Bad point of it, for example: We can set many of Oomguarpages Privvmpages vmguarpages but application can not start because of 'kmemsize' is over. Daniel -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] breaking out of virsh console?
Hello all... In my VM's inittab, I set agetty to run on ttyS0 so I could do virsh console myvm and log in from the host machine's command line. It works perfectly. Trouble is, I don't know how to break out of it to get back to the command line on my host. I've only been able to do so by killing the virsh process. There's gotta be a better way.. Right? Thanks...Paul... -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] breaking out of virsh console?
On Thu, 2008-08-14 at 11:23 -0700, Schroeder, Paul wrote: Hello all... In my VM's inittab, I set agetty to run on ttyS0 so I could do virsh console myvm and log in from the host machine's command line. It works perfectly. Trouble is, I don't know how to break out of it to get back to the command line on my host. I've only been able to do so by killing the virsh process. There's gotta be a better way.. Right? ctrl + ] Thanks...Paul... -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Reusing dumpxml output
On Thu, 2008-08-14 at 10:12 +0100, Daniel P. Berrange wrote: There is also the option to request the 'inactive' XML dump for a running domain which removes any auto-allocated params. This is just a convenience though, and not required for re-creating the VM later. What version is this in I don't see this in the F9 virsh (libvir 0.4.4) or is it just not documented. Daniel -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] VMWare support, any news?
Hi All, I noticed there are some discussion about VMWare support of libvirt several back in April-May. Just wondering is there a prototype yet? The function I¹m interested in is to stop/start a VM by VMWare player/workstation/free server. Thanks, -Yushu -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Reusing dumpxml output
On Thu, Aug 14, 2008 at 03:31:04PM -0400, Andrew Cathrow wrote: On Thu, 2008-08-14 at 10:12 +0100, Daniel P. Berrange wrote: There is also the option to request the 'inactive' XML dump for a running domain which removes any auto-allocated params. This is just a convenience though, and not required for re-creating the VM later. What version is this in I don't see this in the F9 virsh (libvir 0.4.4) or is it just not documented. It is not exposed in virsh yet - only in the C api. It will only be useful as of 0.4.5 (yet to be released) because all current versions ignore the 'inactive' flag. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] breaking out of virsh console?
On Thu, Aug 14, 2008 at 02:26:57PM -0400, Andrew Cathrow wrote: On Thu, 2008-08-14 at 11:23 -0700, Schroeder, Paul wrote: Hello all... In my VM's inittab, I set agetty to run on ttyS0 so I could do virsh console myvm and log in from the host machine's command line. It works perfectly. Trouble is, I don't know how to break out of it to get back to the command line on my host. I've only been able to do so by killing the virsh process. There's gotta be a better way.. Right? ctrl + ] Patches to add documentation to this effect in the virsh.pod man page and / or website HTML pages are welcomed :-) Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] VMWare support, any news?
On Thu, Aug 14, 2008 at 02:11:33PM -0700, Yushu Yao wrote: Hi All, I noticed there are some discussion about VMWare support of libvirt several back in April-May. Just wondering is there a prototype yet? This is no code that I'm aware of. With the recent libvirt code refactoring it should be much quicker/easier to develop additional hypervisor backends if someone is motivated :-) The function I¹m interested in is to stop/start a VM by VMWare player/workstation/free server. Most of the interest in the past has been for VMWare ESX server. From what I understand we'd need to have completely different drivers for ESX vs Player/Workstation because they have no common management API capabilities we can use. We'd welcome patches to write a driver for either ESX or Player/Workstation or both, since they all have valid use cases Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] breaking out of virsh console?
On Thu, 14 Aug 2008, Daniel P. Berrange wrote: On Thu, Aug 14, 2008 at 02:26:57PM -0400, Andrew Cathrow wrote: On Thu, 2008-08-14 at 11:23 -0700, Schroeder, Paul wrote: Hello all... In my VM's inittab, I set agetty to run on ttyS0 so I could do virsh console myvm and log in from the host machine's command line. It works perfectly. Trouble is, I don't know how to break out of it to get back to the command line on my host. I've only been able to do so by killing the virsh process. There's gotta be a better way.. Right? ctrl + ] Patches to add documentation to this effect in the virsh.pod man page and / or website HTML pages are welcomed :-) With respect to this. Does anyone have a pam configuration to connect to vm ([EMAIL PROTECTED])? My current plan is to extend my mDNS based libvirt implementation with one login server that is able to connect to any of my other nodes in the network. But if anyone has something I can base a PAM configuration on I'm happy to reuse it :) Stefan -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] VMWare support, any news?
Thanks Daniel, Could you point me to the simplest example of one other back-end? (I looked into test one but don't know if it has been different after refactoring). So, consider VMPlayer as an example, I need simply do a system call vmplayer --xxx yyy.vmx in the driver implementation? Am I understanding it correctly? -Yushu On 8/14/08 3:13 PM, Daniel P. Berrange [EMAIL PROTECTED] wrote: On Thu, Aug 14, 2008 at 02:11:33PM -0700, Yushu Yao wrote: Hi All, I noticed there are some discussion about VMWare support of libvirt several back in April-May. Just wondering is there a prototype yet? This is no code that I'm aware of. With the recent libvirt code refactoring it should be much quicker/easier to develop additional hypervisor backends if someone is motivated :-) The function I¹m interested in is to stop/start a VM by VMWare player/workstation/free server. Most of the interest in the past has been for VMWare ESX server. From what I understand we'd need to have completely different drivers for ESX vs Player/Workstation because they have no common management API capabilities we can use. We'd welcome patches to write a driver for either ESX or Player/Workstation or both, since they all have valid use cases Daniel -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] VMWare support, any news?
On Thu, 14 Aug 2008, Yushu Yao wrote: Thanks Daniel, Could you point me to the simplest example of one other back-end? (I looked into test one but don't know if it has been different after refactoring). So, consider VMPlayer as an example, I need simply do a system call vmplayer --xxx yyy.vmx in the driver implementation? Am I understanding it correctly? Ideally you would implement the API used for ESX ;) but vmware player could be a start :) Stefan -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] VMWare support, any news?
Vmware has an api the vmware server, vmware workstation and esx all (mostly) share. -- march -Original Message- From: Stefan de Konink [EMAIL PROTECTED] Date: Fri, 15 Aug 2008 00:33:20 To: Yushu Yao[EMAIL PROTECTED] Cc: libvir-list@redhat.com Subject: Re: [libvirt] VMWare support, any news? On Thu, 14 Aug 2008, Yushu Yao wrote: Thanks Daniel, Could you point me to the simplest example of one other back-end? (I looked into test one but don't know if it has been different after refactoring). So, consider VMPlayer as an example, I need simply do a system call vmplayer --xxx yyy.vmx in the driver implementation? Am I understanding it correctly? Ideally you would implement the API used for ESX ;) but vmware player could be a start :) Stefan -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] VMWare support, any news?
Hello, even though it might probably not be exactly what you expect, I released a GPL3-Tool, the UnifiedSessionsManager, what functionally exactly does this. It supports transparently VMware-workstation+server+player and utilizes either vmrun or vmware-cmd. For new VMs the inventory entries are created transparently in case of VMserver. Therefore a unified call interface is provided - with same syntax for QEMU and Xen, which is as basic-call as follows: -START: ctys -t vmw -a create=machine-address execution-target -t VM-type -a action:=CREATE|CANCEL|LIST|ENUMERATE|SHOW|INFO machine-address:=( [label:displayName][,] [pathname:pathname][,] ) The exact syntax and components are described detailed within the manual. execution-target An execution target in email-format USER@HOST, when missing localhost is assumed. There are more options, but this call is sufficient: ctys -t vmw -a create=label:myDisplayName myExecTargetHost When no cached information is present the filesystem is scanned by a find based on a match-filter for configuration files, and the required information is fetched from the configuration file. Further information is available from the User-Manual, which is has more than 600pages. -STOP: ctys -t vmw -a cancel=label:myDisplayName myExecTargetHost Maybe this is what you functionally require. The libvirt, exactly virsh in companion with xm is used in case of Xen (-t xen) only. The URL is http://www.unifiedsessionsmanager.org http://sourceforge.net/projects/ctys Arno Michael March wrote: Vmware has an api the vmware server, vmware workstation and esx all (mostly) share. -- march -Original Message- From: Stefan de Konink [EMAIL PROTECTED] Date: Fri, 15 Aug 2008 00:33:20 To: Yushu Yao[EMAIL PROTECTED] Cc: libvir-list@redhat.com Subject: Re: [libvirt] VMWare support, any news? On Thu, 14 Aug 2008, Yushu Yao wrote: Thanks Daniel, Could you point me to the simplest example of one other back-end? (I looked into test one but don't know if it has been different after refactoring). So, consider VMPlayer as an example, I need simply do a system call vmplayer --xxx yyy.vmx in the driver implementation? Am I understanding it correctly? Ideally you would implement the API used for ESX ;) but vmware player could be a start :) Stefan -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list -- Arno-Can Uestuensoez www.i4p.de / www.i4p.com -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] breaking out of virsh console?
Hello, even though this might probably not be exactly what you expect, I released a GPL3-Tool, the UnifiedSessionsManager, what functionally supports the splitted management of Clients and Servers including Headless-Mode and allows for disconnect and reconnect by a simplified addressing schema only. But anyhow, the onyl supported communications channel is SSH, tested with OpenSSH. I personally use SSH as kerberized SSO in companion with LDAP and automount by usage of PAM, thus having exactly the functionality of a centralized access by encrypted communications only. The tool supports for DISPLAYFORWARDING as well as for CONNECTIONFORWARDING, which is a local client on caller's site. Remote execution of X11 clients are supoorted, e.g. for remote VMM execution and passing the GUI through the SSH tunnel via DISPLAYFORWARDING. Additionally several CONSOLE types are supported in a generic manner for XEN, which are: XTERM, GTERM, VNC, EMACS, NONE. Where NONE is the headless-mode for initial startup. The name UnifiedSessionsManager means, it supports the (almost) same syntax for all supported types: XEN, QEMU, VMW(VMare:workstaion,server,player),VNC,X11,CLI, and PM, where PM is a physical machine, which could be started by WoL-WakeOnLAN. Thus you can setup a login-server, where ever you want, and just access any of your PMs or VMs, physical or virtual machines, in a secure manner by SSH. And connect and reconnect arbitrarily as you require, and choose for each session a different CONSOLE type. Additionally MACROs and GROUPs are supported, though the one-call startup of any desktop with an arbitrary number of VMs is supported. This includes the automated startup of the VMs. The URL is http://www.unifiedsessionsmanager.org http://sourceforge.net/projects/ctys Arno Stefan de Konink wrote: On Thu, 14 Aug 2008, Daniel P. Berrange wrote: On Thu, Aug 14, 2008 at 02:26:57PM -0400, Andrew Cathrow wrote: On Thu, 2008-08-14 at 11:23 -0700, Schroeder, Paul wrote: Hello all... In my VM's inittab, I set agetty to run on ttyS0 so I could do virsh console myvm and log in from the host machine's command line. It works perfectly. Trouble is, I don't know how to break out of it to get back to the command line on my host. I've only been able to do so by killing the virsh process. There's gotta be a better way.. Right? ctrl + ] Patches to add documentation to this effect in the virsh.pod man page and / or website HTML pages are welcomed :-) With respect to this. Does anyone have a pam configuration to connect to vm ([EMAIL PROTECTED])? My current plan is to extend my mDNS based libvirt implementation with one login server that is able to connect to any of my other nodes in the network. But if anyone has something I can base a PAM configuration on I'm happy to reuse it :) Stefan -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list -- Arno-Can Uestuensoez www.i4p.de / www.i4p.com -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] Re: fail to run virsh
Please can somebody help? I am kind of stucked here. Thanks, Jun On Thu, Aug 14, 2008 at 5:27 PM, Jun Koi [EMAIL PROTECTED] wrote: Hi, I installed libvirt (cvs version), and can confirm that libvirtd is running. However, virsh failed to work. I got the below message when running virsh with debugging information. How to fix this problem? Many thanks, Jun # LIBVIRT_DEBUG=1 virsh DEBUG: libvirt.c: virInitialize (register drivers) DEBUG: libvirt.c: virConnectOpenAuth (name=(null), auth=0xb7f53b84, flags=0) DEBUG: libvirt.c: do_open (Probed qemu:///system) DEBUG: lxc_driver.c: lxcCheckContainerSupport (clone call returned EINVAL, container support is not enabled) DEBUG: libvirt.c: do_open (Using qemu:///system as default URI, 1 hypervisor found) DEBUG: libvirt.c: do_open (name qemu:///system to URI components: scheme qemu opaque (null) authority (null) server (null) user (null) port 0 path /system ) DEBUG: libvirt.c: do_open (trying driver 0 (Test) ...) DEBUG: libvirt.c: do_open (driver 0 Test returned DECLINED) DEBUG: libvirt.c: do_open (trying driver 1 (QEMU) ...) DEBUG: libvirt.c: do_open (driver 1 QEMU returned DECLINED) DEBUG: libvirt.c: do_open (trying driver 2 (Xen) ...) DEBUG: libvirt.c: do_open (driver 2 Xen returned DECLINED) DEBUG: libvirt.c: do_open (trying driver 3 (OPENVZ) ...) DEBUG: libvirt.c: do_open (driver 3 OPENVZ returned DECLINED) DEBUG: libvirt.c: do_open (trying driver 4 (LXC) ...) DEBUG: libvirt.c: do_open (driver 4 LXC returned DECLINED) DEBUG: libvirt.c: do_open (trying driver 5 (remote) ...) DEBUG: remote_internal.c: doRemoteOpen (proceeding with name = qemu:///system) libvir: Remote error : No such file or directory DEBUG: libvirt.c: do_open (driver 5 remote returned ERROR) DEBUG: hash.c: virUnrefConnect (unref connection 0x806b588 qemu:///system 1) DEBUG: hash.c: virReleaseConnect (release connection 0x806b588 qemu:///system) error: failed to connect to the hypervisor -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH] fix minor typo
Hi, John
Thank you for your suggestion.
I am looking around the libvirt.pot and found 4 typos additionally.
I am pushing these fixes.
Thanks
Atsushi SAKAI
John Levon [EMAIL PROTECTED] wrote:
Fix a typo in the message for the 'dump' command in virsh.
Signed-off-by: John Levon [EMAIL PROTECTED]
Index: src/virsh.c
===
RCS file: /data/cvs/libvirt/src/virsh.c,v
retrieving revision 1.157
diff -u -r1.157 virsh.c
--- src/virsh.c 22 Jul 2008 16:12:01 - 1.157
+++ src/virsh.c 13 Aug 2008 15:50:09 -
@@ -1320,7 +1320,7 @@
return FALSE;
if (virDomainCoreDump(dom, to, 0) == 0) {
-vshPrint(ctl, _(Domain %s dumpd to %s\n), name, to);
+vshPrint(ctl, _(Domain %s dumped to %s\n), name, to);
} else {
vshError(ctl, FALSE, _(Failed to core dump domain %s to %s),
name, to);
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
fix_message_20080815.patch
Description: Binary data
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
