- Users - libvirt List Archives

[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 03 Jan '14

03 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 30 Dec '13

30 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 27 Dec '13

27 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

[libvirt-users] Reg: Methods in DomainJobInfo
by Rathidevi 27 Dec '13

27 Dec '13

Hi All, I am new to libvirt. Please explain about the units (which is bytes or KB or MB) and uses of DomainJobInfo and DomainBlockInfo methods. Like getMemRemaining(), getDataRemaining() etc. Using libvirt version is libvirt-0.5.1. Thank you Regards, Rathidevi

2 3

[libvirt-users] Live migration without block copy
by Paul Mathews 24 Dec '13

24 Dec '13

Hello all, I'm trying to get live migration without block copying working in a custom solution, but I think I need a better understanding of the migration process. In my environment, I have two iscsi targets exported which are then placed into a raid via mdadm on the compute node. I've tried using the already exposed hook on stop to disassemble and re-export storage, and I also made my own when the source hits perform3_done phase, but at that point the md device is still locked. It seems like there should be a time in a live migration where both instances are in a paused state and everything has been flushed to disk, I'm just not familiar enough with the code to determine where that is. -Paul

1 0

[libvirt-users] man page
by Fl＠sh 23 Dec '13

23 Dec '13

It seems to me that the man page is not complete. Personally, I had to read the code to understand. Propose to amend paragraph of included files on: -i GUEST-PATH=HOST-PATH, --include GUEST-PATH=HOST-PATH File (HOST-PATH) to copy into custom dir (GUEST-PATH). -I HOST-PATH, --includefile=HOST-PATH Copy all files listed in inputfile into the appropriate temporary sandbox directories. File should contain a line like: GUEST-PATH=HOST-PATH Directory (or subdirectory) of GUEST-PATH path must to exist in the guest filesystem (use --mount) Maybe I misunderstood how to use inclusion, but it says even more about what leadership should be written in detail. P.S. On the use of the network too. -- F1ash

3 6

[libvirt-users] Virsh console stops accepting inputs
by Satvinder Gunsi 23 Dec '13

23 Dec '13

Hello All, I am trying following steps: 1. Untar a gzip image 2. virsh create NAME.xml ( for the image) 3. virsh console NAME The above steps are done for four times on different files. In step 3 above for one out of four VMs (usually the first one), when I try to login:, typing the first letter of password brings me back to "login:" prompt. Then for the next four tries "each" letter moves me from "login" to "password:" and back to "login:" I also see following error in libvirtd.log for each console login attempt. 25446: error : daemonStreamHandleAbort:609 : stream aborted at client request My libvirt version is: libvirtd (libvirt) 1.0.2 OS: FC16 Important: If I destroy the VM and bring it up again, then I donot see this issue and am able to successfully login. Can somebody help in resolving this issue. Thanks in advance, Regards, Satvinder

1 0