March 2012 - Users - libvirt List Archives

Re: [libvirt-users] 回复: 回复: virsh create error : monitor socket did not
by Alex Jia 15 Mar '12

15 Mar '12

On 03/15/2012 05:39 PM, 张光鹏 wrote: > sorry , i send an error template , our template like this: It probably is a bug on libvirt 0.8.7, and I haven't met this issue using your XML template on rhel6.2 with libvirt-0.9.10-5.el6.x86_64, I'm not sure whether this issue is fixed on 0.8.7-18.el6_1.4, maybe, you may upgrade your libvirt and then try it again. For libvirtd log, yeah, it will be very big if you set a low debugger level such as level 1, but as usual, we need also some debugger information except for error, maybe, you can filter some important information or set debugger level to higher level to avoid a big size log file. in addition, if you're run virt-manager please close it, otherwise, libvirt will record many debugger information into libvirtd.log. BTW, if you don't want log file eat your the whole disk space, please remember to change libvirtd.conf debugger level then remove libvirtd.log and restart libvirtd service. Regards, Alex > <domain type='kvm' > xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> > <name>one-9</name> > <vcpu>1</vcpu> > <memory>524288</memory> > <os> > <type arch='x86_64'>hvm</type> > <boot dev='hd'/> > </os> > <devices> > <emulator>/usr/bin/kvm</emulator> > <disk type='file' device='disk'> > <source file='/one_images/9/images/disk.0'/> > <target dev='hda'/> > <driver name='qemu' type='raw' cache='default'/> > </disk> > <disk type='file' device='cdrom'> > <source file='/one_images/9/images/disk.1'/> > <target dev='hdc'/> > <readonly/> > <driver name='qemu' type='raw'/> > </disk> > <interface type='bridge'> > <source bridge='kvmbr0'/> > <mac address='02:00:0b:01:01:03'/> > </interface> > <graphics type='vnc' listen='0.0.0.0' port='5909'/> > </devices> > <features> > <acpi/> > </features> > </domain> > ------------------------------------------------------------------------ > 张光鹏 > *发件人：* 张光鹏 <mailto:zhanggp@neusoft.com> > *发送时间：* 2012-03-15 17:25 > *收件人：* Alex Jia <mailto:ajia@redhat.com> > *主题：* 回复: Re: [libvirt-users] virsh create error : monitor socket > did not > Hi， > my libvirt version is 0.8.7 and qemu-kvm-0.12.1.2 on redhat6.1. > I don't set libvirt log, so thank you for reminding me. > I think my template is right ,because my code generate automatically. > But i would like to share with you and find the problem. > By the way , i configured the libvirt log, and i find this file kept > getting bigger. If this file becomes large enough , i don't think it's > a good thing , so, you must have some advise to handle it ,right? > Thanks. > ------------------------------------------------------------------------ > 张光鹏 > *发件人：* Alex Jia <mailto:ajia@redhat.com> > *发送时间：* 2012-03-15 16:56 > *收件人：* 张光鹏 <mailto:zhanggp@neusoft.com> > *抄送：* libvirt-users <mailto:libvirt-users@redhat.com> > *主题：* Re: [libvirt-users] virsh create error : monitor socket did not > On 03/15/2012 11:31 AM, 张光鹏 wrote: >> Hi, >> Occasionally I run into this situation , i created a vm-template and >> i use "virsh create vm-template " to start a vm .After a pause , i >> got this error : >> virsh create error : monitor socket did not ; > Could you provide your libvirt & qemu-kvm version ? what's your > platform? fedora or others? >> Then i try again with the same template and the same command , my vm >> created successfully. >> I try to find something in the file of >> /var/log/libvrit/qemu/vm-template.log, but i cannot find useful >> things except some parameters. > However, it's helpful if you may attach the above log as a attachment. > in addition, you may add the following lines into > /etc/libvirt/libvirtd.conf and restart libvirtd service then repeat > 'virsh create vm-template' again: > > log_filters="3:remote 3:event 1:qemu 1:libvirt 1:conf" > log_outputs="1:file:/var/log/libvirt/libvirtd.log" > > Could you attach /var/log/libvirt/libvirtd.log as a attachment in here? >> So , i wonder whether my host running vms too much ? I make sure that >> my template is right, and this error occasionally appear a few times. > But if you can attach your guest XML template as a attachment, maybe, > I can exclude other reason. > > Regards, > Alex >> Can someone teach me ? >> Thanks. >> Best regards. >> ------------------------------------------------------------------------ >> 张光鹏 >> tel: 13718913184 >> mail: zhanggp(a)neusoft.com <mailto:zhanggp@neusoft.com> >> 移动互联网事业部 >> 东软集团股份有限公司 >> http://www.neusoft.com >> --------------------------------------------------------------------------------------------------- >> Confidentiality Notice: The information contained in this e-mail and >> any accompanying attachment(s) >> is intended only for the use of the intended recipient and may be >> confidential and/or privileged of >> Neusoft Corporation, its subsidiaries and/or its affiliates. If any >> reader of this communication is >> not the intended recipient, unauthorized use, forwarding, printing, >> storing, disclosure or copying >> is strictly prohibited, and may be unlawful.If you have received this >> communication in error,please >> immediately notify the sender by return e-mail, and delete the >> original message and all copies from >> your system. Thank you. >> --------------------------------------------------------------------------------------------------- >> >> >> >> _______________________________________________ >> libvirt-users mailing list >> libvirt-users(a)redhat.com >> https://www.redhat.com/mailman/listinfo/libvirt-users > > --------------------------------------------------------------------------------------------------- > Confidentiality Notice: The information contained in this e-mail and > any accompanying attachment(s) > is intended only for the use of the intended recipient and may be > confidential and/or privileged of > Neusoft Corporation, its subsidiaries and/or its affiliates. If any > reader of this communication is > not the intended recipient, unauthorized use, forwarding, printing, > storing, disclosure or copying > is strictly prohibited, and may be unlawful.If you have received this > communication in error,please > immediately notify the sender by return e-mail, and delete the > original message and all copies from > your system. Thank you. > ---------------------------------------------------------------------------------------------------

1 0

[libvirt-users] virsh create error : monitor socket did not
by 张光鹏 15 Mar '12

15 Mar '12

Hi, Occasionally I run into this situation , i created a vm-template and i use "virsh create vm-template " to start a vm .After a pause , i got this error : virsh create error : monitor socket did not ; Then i try again with the same template and the same command , my vm created successfully. I try to find something in the file of /var/log/libvrit/qemu/vm-template.log, but i cannot find useful things except some parameters. So , i wonder whether my host running vms too much ? I make sure that my template is right, and this error occasionally appear a few times. Can someone teach me ? Thanks. Best regards. 张光鹏 tel: 13718913184 mail: zhanggp(a)neusoft.com 移动互联网事业部东软集团股份有限公司 http://www.neusoft.com --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. ---------------------------------------------------------------------------------------------------

2 1

Re: [libvirt-users] Memory statistics for DomU's
by inge85＠web.de 14 Mar '12

14 Mar '12

2 1

[libvirt-users] Memory statistics for DomU's
by inge85＠web.de 14 Mar '12

14 Mar '12

2 1

[libvirt-users] Weird behavior with LVM storage pool on host
by Ernesto Domato 14 Mar '12

14 Mar '12

Hi list, the problem that I'm having seems to be between libvirtd and udev I have two hosts with LVM. The root partition run over this LVM. After booting the machine, if I do "udevadm settle" it responds almost instantly but then if I launch libvirtd the "udevadm settle" command doesn't respond for about 2 to 3 minutes and the only way to solve this is to restart the uded daemon. This behavior happens on both hosts. The only difference between both is that one has the root partition and storage pool over the same LVM group and disk. The other has separate disks and LVM groups. Have someone experienced something like this or can help me how to debug and solve this problem?. Thanks for all. Ernesto

1 0

[libvirt-users] libvirt with sanlock
by Frido Roose 14 Mar '12

14 Mar '12

Hello, I configured libvirtd with the sanlock lock manager plugin: # rpm -qa | egrep "libvirt-0|sanlock-[01]" libvirt-lock-sanlock-0.9.4-23.el6_2.4.x86_64 sanlock-1.8-2.el6.x86_64 libvirt-0.9.4-23.el6_2.4.x86_64 # egrep -v "^#|^$" /etc/libvirt/qemu-sanlock.conf auto_disk_leases = 1 disk_lease_dir = "/var/lib/libvirt/sanlock" host_id = 4 # mount | grep sanlock /dev/mapper/kvm--shared-sanlock on /var/lib/libvirt/sanlock type gfs2 (rw,noatime,hostdata=jid=0) # cat /etc/sysconfig/sanlock SANLOCKOPTS="-R 1 -o 30" I increased the sanlock io_timeout to 30 seconds (default = 10), because the sanlock dir is on a GFS2 volume and can be blocked for some time while fencing and journal recovery takes place. With the default sanlock io timeout, I get lease timeouts because IO is blocked: Mar 5 15:37:14 raiti sanlock[5858]: 3318 s1 check_our_lease warning 79 last_success 3239 Mar 5 15:37:15 raiti sanlock[5858]: 3319 s1 check_our_lease failed 80 So far, all fine, but when I restart sanlock and libvirtd, it takes about 2 * 30 seconds = 1 minute before libvirtd is usable. "virsh list" hangs during this time. I can still live with that... But it gets worse after a reboot, when running a "virsh list" even takes a couple of minutes (like about 5 minutes) before it responds. After this initial time, virsh is responding normally, so it looks like an initialization issue to me. Is this a configuration issue, a bug, or expected behavior? Thanks for any advice... Frido

4 5

[libvirt-users] message on console by starting virt-manager , gentoo
by Marko Weber 12 Mar '12

12 Mar '12

# virt-manager /usr/share/virt-manager/virt-manager.py:306: DeprecationWarning: Importing dbus.glib to use the GLib main loop with dbus-python is deprecated. Instead, use this sequence: from dbus.mainloop.glib import DBusGMainLoop DBusGMainLoop(set_as_default=True) import dbus.glib ist that for interesr for the developers?

2 1

[libvirt-users] run virsh as non-root user
by Qu, John (IS) 12 Mar '12

12 Mar '12

Hi, I have encountered problem running virsh as non-root user. I am using eucalyptus software on top of KVM, eucalyptus requires to run virsh as non-root user. I've found that people had similiar issue posted in the list, but I didn't find the solution. I've tried few things. 1) put user eucalyptus in the libvirt group. 2) even changed owner /var/run/libvirt/libvirt-sock to eucalyptus. it didn't help. the followins showed some debug information. I would appreciate your help. export LIBVIRT_DEBUG=1 [eucalyptus@hp-a ~]$ virsh list 21:48:08.342: 5830: info : libvirt version: 0.9.4, package: 23.el6_2.4 (CentOS BuildSystem <http://bugs.centos.org>, 2012-01-17-10:52:29, c6b18n1.dev.centos.org) 21:48:08.342: 5830: debug : virInitialize:415 : register drivers 21:48:08.342: 5830: debug : virRegisterDriver:770 : driver=0x3848dc5c40 name=Test 21:48:08.342: 5830: debug : virRegisterDriver:794 : registering Test as driver 0 21:48:08.342: 5830: debug : virRegisterNetworkDriver:587 : registering Test as network driver 0 21:48:08.342: 5830: debug : virRegisterInterfaceDriver:620 : registering Test as interface driver 0 21:48:08.342: 5830: debug : virRegisterStorageDriver:653 : registering Test as storage driver 0 21:48:08.342: 5830: debug : virRegisterDeviceMonitor:686 : registering Test as device driver 0 21:48:08.342: 5830: debug : virRegisterSecretDriver:719 : registering Test as secret driver 0 21:48:08.342: 5830: debug : virRegisterNWFilterDriver:752 : registering Test as network filter driver 0 21:48:08.342: 5830: debug : virRegisterDriver:770 : driver=0x3848dc6e00 name=ESX 21:48:08.342: 5830: debug : virRegisterDriver:794 : registering ESX as driver 1 21:48:08.342: 5830: debug : virRegisterInterfaceDriver:620 : registering ESX as interface driver 1 21:48:08.342: 5830: debug : virRegisterNetworkDriver:587 : registering ESX as network driver 1 21:48:08.342: 5830: debug : virRegisterStorageDriver:653 : registering ESX as storage driver 1 21:48:08.342: 5830: debug : virRegisterDeviceMonitor:686 : registering ESX as device driver 1 21:48:08.342: 5830: debug : virRegisterSecretDriver:719 : registering ESX as secret driver 1 21:48:08.342: 5830: debug : virRegisterNWFilterDriver:752 : registering ESX as network filter driver 1 21:48:08.342: 5830: debug : virRegisterDriver:770 : driver=0x3848dc6440 name=remote 21:48:08.342: 5830: debug : virRegisterDriver:794 : registering remote as driver 2 21:48:08.342: 5830: debug : virRegisterNetworkDriver:587 : registering remote as network driver 2 21:48:08.342: 5830: debug : virRegisterInterfaceDriver:620 : registering remote as interface driver 2 21:48:08.342: 5830: debug : virRegisterStorageDriver:653 : registering remote as storage driver 2 21:48:08.342: 5830: debug : virRegisterDeviceMonitor:686 : registering remote as device driver 2 21:48:08.342: 5830: debug : virRegisterSecretDriver:719 : registering remote as secret driver 2 21:48:08.342: 5830: debug : virRegisterNWFilterDriver:752 : registering remote as network filter driver 2 21:48:08.342: 5830: debug : virEventRegisterDefaultImpl:204 : registering default event implementation 21:48:08.342: 5830: debug : virEventPollAddHandle:112 : Add handle fd=4 events=1 cb=0x3848a40cb0 opaque=(nil) 21:48:08.342: 5830: debug : virEventPollAddHandle:116 : Used 0 handle slots, adding at least 10 more 21:48:08.342: 5830: debug : virEventPollInterruptLocked:676 : Skip interrupt, 0 0 21:48:08.342: 5830: debug : virEventRegisterImpl:177 : addHandle=0x3848a41a90 updateHandle=0x3848a40bb0 removeHandle=0x3848a40a70 addTimeout=0x3848a418f0 updateTimeout=0x3848a40cf0 removeTimeout=0x3848a40970 21:48:08.342: 5830: debug : virConnectOpenAuth:1282 : name=(null), auth=0x3848dc5bc0, flags=0 21:48:08.342: 5830: debug : do_open:1019 : no name, allowing driver auto-select 21:48:08.342: 5830: debug : do_open:1056 : trying driver 0 (Test) ... 21:48:08.342: 5830: debug : do_open:1062 : driver 0 Test returned DECLINED 21:48:08.342: 5830: debug : do_open:1056 : trying driver 1 (ESX) ... 21:48:08.342: 5830: debug : do_open:1062 : driver 1 ESX returned DECLINED 21:48:08.342: 5830: debug : do_open:1056 : trying driver 2 (remote) ... 21:48:08.343: 5830: debug : remoteOpen:825 : Auto-probe remote URI 21:48:08.343: 5830: debug : remoteOpen:828 : Auto-spawn user daemon instance 21:48:08.343: 5830: debug : doRemoteOpen:520 : proceeding with name = 21:48:08.343: 5830: debug : doRemoteOpen:530 : Connecting with transport 1 21:48:08.343: 5830: debug : doRemoteOpen:577 : Proceeding with sockname @/home/eucalyptus/.libvirt/libvirt-sock 21:48:08.343: 5830: debug : virCommandRunAsync:2048 : About to run LC_ALL=C PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/java/jdk1.6.0/jre/bin HOME=/home/eucalyptus USER=eucalyptus LOGNAME=eucalyptus /usr/sbin/libvirtd --timeout=30 21:48:08.343: 5830: debug : virCommandRunAsync:2064 : Command result 0, with PID 5831 21:48:08.345: 5830: debug : virCommandRun:1870 : Result status 0, stdout: '(null)' stderr: '(null)' --------------------------------- [eucalyptus@hp-a ~]$ id uid=501(eucalyptus) gid=501(eucalyptus) groups=501(eucalyptus),0(root),502(libvirt) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 ------------------------------------------------------------- Thanks John

3 3

[libvirt-users] 'virsh list' issue
by wangsuyi640 08 Mar '12

08 Mar '12

Dear all: Afer run the command 'qemu-kvm -hda /root/free.img -m 512 -usbdevice tablet -vga qxl -spice port=5930,disable-ticketing' , and the VM starts natrually. Then I run the command 'virsh list' , it shows as follows: [root@localhost ~]# virsh list Id Name State ---------------------------------- [root@localhost ~]# there is no VM running! I am puzzled , can someone help me? Yours Sinerely! suyi

4 4

[libvirt-users] Setting the default Hypervisor
by RaSca 08 Mar '12

08 Mar '12

Hi all, I'm using libvirt with qemu-kvm and virtualbox on the same system. Everything is working, but I want to change the default uri fo virsh. At the moment, if i run: # virsh uri vbox:///system and because of this, if I try to list my vm(s) in this way: # virsh list --all Id Name State ---------------------------------- the output is empty. I need always to pass the uri: # virsh -c qemu:///system list --all Id Name State ---------------------------------- - ubuntu-vm shut off So, is there a way to set the default uri to be qemu:///system? I looked into /etc/default/libvirt-guests and /etc/default/libvirt-bin but I was not able to find an options (setting URIS= does not work). I'm on Debian Squeeze with backports. Thanks a lot, -- RaSca Mia Mamma Usa Linux: Niente è impossibile da capire, se lo spieghi bene! rasca(a)miamammausalinux.org http://www.miamammausalinux.org

2 4