[prev in list] [next in list] [prev in thread] [next in thread] 

List:       libvir-list
Subject:    Re: [libvirt] =?utf-8?b?562U5aSNOiDnrZTlpI06ICDnrZTlpI06IEhlbHDvvJpD?=
From:       Jim Fehlig <jfehlig () suse ! com>
Date:       2017-11-28 18:41:17
Message-ID: 3e817837-3cbb-7b24-a41c-76492b13ef77 () suse ! com
[Download RAW message or body]

On 11/27/2017 09:26 PM, Chenjia (C) wrote:
> Dear libvirt expert:
> 	Thanks for your replay, we are not restore from the same state file twice, only \
> one time. we have 40 process, each process handle it's own VM and VM state file, \
> and each process will do following things cycle:  While(1)
> 		{
> 			Virsh restore state file
> 			do something in VM in 20s
> 			virsh destroy vm
> 		}
> 	so we have sure now: There is currently no way to reduce these 40 xen status files \
> space.  
> 	
> 	When we do the above things, we got a xen crash on xen-4.7.0, so we try to use the \
> xen-4.8.2 and libvirt 2.5.0, and the crash problem is no longer exist, but we got a \
> new problem:  we add the <interface> in config fie of VM:
> 		<interface type='bridge'>
> 			<mac address='18:c5:8a:15:c1:39'/>
> 			<source bridge='virbr0'/>
> 		 </interface>
> 	When we use 'virsh create virsh_0.xml', we can't create the vm, and got follow \
> error:  2017-11-28 12:36:56.329+0000: 17489: error : libxlDomainStart:1280 : \
> internal error: libxenlight failed to create new domain 'aap_0'  error: Failed to \
> create domain from virsh_0.xml  error: internal error: libxenlight failed to create \
> new domain 'aap_0'  and in the /var/log/libvirt/libxl/libxl-driver.log there have a \
> log:  2017-11-28 20:36:53 CST libxl: error: \
> libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/vif-bridge online \
> [17580] exited with error status 127

You need to determine why Xen's vif-bridge script failed. syslog should contain 
info about that.

Regards,
Jim


[prev in list] [next in list] [prev in thread] [next in thread]