- Users - libvirt List Archives

[libvirt-users] ANNOUNCE: ruby-libvirt 0.5.2
by Chris Lalancette 09 Jan '14

09 Jan '14

All, This is a release notification for ruby-libvirt 0.5.2. ruby-libvirt is a ruby wrapper around the libvirt API. The changelog between 0.5.1 and 0.5.2 is: * Fix to make sure we don't free more entries than retrieved (potential crash) Version 0.5.2 is available from http://libvirt.org/ruby: Tarball: http://libvirt.org/ruby/download/ruby-libvirt-0.5.2.tgz Gem: http://libvirt.org/ruby/download/ruby-libvirt-0.5.2.gem It is also available from rubygems.org; to get the latest version, run: $ gem install ruby-libvirt As usual, if you run into questions, problems, or bugs, please feel free to mail me (clalancette gmail com) and the libvirt mailing list. Thanks to Guido Günther for the patch to fix this problem.

1 0

[libvirt-users] Canceling a live migration via virsh? (QEMU/KVM)
by Scott Sullivan 08 Jan '14

08 Jan '14

I am using QEMU/KVM, using Live Migrations like this: virsh migrate --live ${name} qemu+ssh://${DESTINATION}/system My question, running this command makes it hang in the foreground. Is there a way for this to return immediately, so I can just poll for the migration status? Also, is there a way to _cancel_ a migration? I see the --timeout option, however if a given timeout is reached I would rather have the ability to cancel the migration than force the suspend. I do see there is a QEMU api migrate_cancel..eg: virsh qemu-monitor-command ${name} --pretty '{"execute":"migrate_cancel"}' Is that the only way to cancel a migration using libvirt?

2 2

[libvirt-users] Ownerships of VMs and Image files
by Christoph Pleger 07 Jan '14

07 Jan '14

Hello, I installed libvirt and qemu/kvm on a machine. I testet a little with those and found out that all users having an account on that machine can start every VM of every other user on the machine, in some conditions even directly access the image file on the real host. What I would like to have is that every user can only access the VMs and image files he or she created himself/herself, as long as he/she does not explicitly set other permissions. Is it possible to achieve that? Regards Christoph

2 1

[libvirt-users] How to start the linux container's network interface automatically
by WANG Cheng D 06 Jan '14

06 Jan '14

Dear all, I failed to start the linux container's network interface automatically. I have to start it manually each time after the container finishes booting. I know that in a native fedora, if we want the network interface to start automatically, we should edit "/etc/sysconfig/network-script/ifcfg-eth0 and add the string "ONBOOT=yes". My host is fedora 16. I used "yum --installroot=/root/fedoralxc --releasever=16 install -y openssh, bridge-utils" to setup the rootfs for my container (Laine thought that my fedora version is a little bit older, I wonder if the newer version fedora container can automatically start its network interface ) After rootfs installation, in the container's file system, there is no sub-directory named "network-scripts" in "/etc/sysconfig" . So, I created this directory manually and added a file named "ifcfg-eth0", but the container's network interface still cannot start automatically. I tried to add files ".bash_profile" and ".bashrc" in which I added the "ifconfig" in the shell script to try to configure eth0 automatically, but it still doesn't work. I wonder if there is a ".bashrc" for the root of a container? If there is, where should this file be located? Any comments will be highly appreciated. Cheng

1 0

[libvirt-users] How to start the container's network interface automatically
by WANG Cheng D 06 Jan '14

06 Jan '14

Dear all, I failed to start the container's network interface automatically. I have to start it manually each time after the container finishes booting. I know that in a native fedora, if we want the network interface to start automatically, we should edit "/etc/sysconfig/network-script/ifcfg-eth0 and add the string "ONBOOT=yes". My host is fedora. I used "yum --installroot=/root/fedoralxc --releasever=16 install -y openssh, bridge-utils" to setup the rootfs for my container After rootfs installation, in the container's file system, there is no sub-directory named "network-scripts" in "/etc/sysconfig" . So, I created this directory manually and added a file named "ifcfg-eth0", but the container's network interface still cannot start automatically. I tried to add files ".bash_profile" and ".bashrc" in which I added the "ifconfig" in the shell script to try to configure eth0 automatically, but it still doesn't work. I wonder if there is a ".bashrc" for the root of a container? If there is, where should this file be located? Any comments will be highly appreciated. Cheng

1 0

[libvirt-users] ANNOUNCE: Oz 0.12.0 release
by Chris Lalancette 04 Jan '14

04 Jan '14

All, I'm pleased to announce release 0.12.0 of Oz. Oz is a program for doing automated installation of guest operating systems with limited input from the user. Release 0.12.0 is a bugfix and feature release for Oz. Some of the highlights between Oz 0.11.0 and 0.12.0 are: * Fixes to concurrent oz-install invocations * Python 3 compatibility in the test suites * Support for Ubuntu 12.04.3 * Support for Mageia * Allow a MAC address to be passed in (instead of auto-generated) * Support for RHEL5.10 * Support for Ubuntu 13.10 * Use lxml instead of libxml2 for XML document processing (it has much better error messages) * Remove the unused "tunnels" functionality * Support FreeBSD 10.0 * Remove deprecated functions from the Guest class * Speed up guest customization on guests that support NetworkManager * Follow subprocess commands as they are executed (makes debugging easier) * Ensure that any paths from the user are absolute, otherwise things don't work properly * Add support for OpenSUSE 13.1 * Add support for Fedora 20 * Add support for RHEL-7 A tarball and zipfile of this release is available on the Github releases page: https://github.com/clalancette/oz/releases . Packages for Fedora-19, Fedora-20, and EPEL-6 have been built in Koji and will eventually make their way to stable. Instructions on how to get and use Oz are available at http://github.com/clalancette/oz/wiki . If you have questions or comments about Oz, please feel free to contact me at clalancette at gmail.com, or open up an issue on the github page: http://github.com/clalancette/oz/issues . Thanks to everyone who contributed to this release through bug reports, patches, and suggestions for improvement. Chris Lalancette

1 0

Re: [libvirt-users] [libvirt] [RFC] Implementing ftrace support for libvirt
by Mauricio Tavares 03 Jan '14

03 Jan '14

On Fri, Jan 3, 2014 at 6:46 AM, yuxh <yuxinghai(a)cn.fujitsu.com> wrote: > Hi all, > > Happy new year! > > The existing trace mechanism in libvirt is dtrace. Although the dtrace > can work, it's not work well enough. Every time we want get information > from the trace point we must write a systemtap script and run it > together with libvirt. > > That's really unpractical on some occasion, especially on production > server since the systemtap script can't be executed automatically. > And some problems may be not easy to reproduce, then it will cost a > lot of time to get the trace information again. > > So I think it is essential to add supporting for record the trace > information automatically in libvirt to satisfy the user's requirement. > That's why I'm currently implementing ftrace support in libvirt. > > How do you think about my idea? Any comment will be appreciated! > How hard/painless it would be to implement it? And, can you have both and then select which one to use? > Thanks, > Yu > > -- > libvir-list mailing list > libvir-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/libvir-list

1 0

[libvirt-users] Connect libvirt to iSCSI target
by Marco 31 Dec '13

31 Dec '13

Hi! I'm new to libvirt and face problems connecting to an iSCSI target. What I intend to do is to connect libvirt (I tried virt-manager and virsh) to an iSCSI target and then boot from the LUNs which contain the VMs. I followed the documentation¹ but got stuck at section 12.1.5.4.3. 1) virsh pool-define-as \ --name foo \ --type iscsi \ --source-host vmhost \ --source-dev iqn.2013-11.vmhost:vmpool \ --target /dev/disk/by-path 2) virsh pool-start foo error: Failed to start pool foo error: internal error: cannot find session virsh -c qemu:///system pool-start foo error: Failed to start pool foo error: internal error: cannot find session Why can't libvirt find the session, and which session? Running iscsiadm --mode discovery --type sendtargets --portal vmhost:3260,1 succeeds and lists the targets. How to connect libvirt to the iSCSI target? System info: Debian sid, Linux 3.11-2-amd64 libvirtd (libvirt) 1.1.4 virsh version: 1.1.4 iSCSI target: FreeNAS-9.1.1 Best regards Marco ¹ https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux…

2 7

[libvirt-users] how to use openConsole and openGraphics
by yue 28 Dec '13

28 Dec '13

hi,all 1.how to use openConsole and openGraphics? 2.what is the theory of that? thanks

2 3

[libvirt-users] fail to live migration is related to virtio-console
by yue 28 Dec '13

28 Dec '13

hi,all this error occured when live migration windows os, log of that vm is: features 0x1e unsupported allowed features 0x71000002 qemu warning error while loading state for instance 0x0 of device '0000:00:04.4/virtio-console' do you have some idea about that? thanks

2 1