Date: Thu, 15 Mar 2012 18:07:07 +0800
From: Alex Jia <ajia@redhat.com>
To: ??? <zhanggp@neusoft.com>
Cc: "libvirt-users@redhat.com" <libvirt-users@redhat.com>
Subject: Re: [libvirt-users] ??: ??: virsh create error : monitor
socket did not
Message-ID: <4F61BF4B.2030103@redhat.com>
Content-Type: text/plain; charset="gb2312"

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@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@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.
> ---------------------------------------------------------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.redhat.com/archives/libvirt-users/attachments/20120315/d9139b5d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 11635 bytes
Desc: not available
URL: <https://www.redhat.com/archives/libvirt-users/attachments/20120315/d9139b5d/attachment.jpe>

------------------------------

_______________________________________________
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users

End of libvirt-users Digest, Vol 27, Issue 27
*********************************************