<br><br><div class="gmail_quote">2012/3/14 Andrew Vagin <span dir="ltr"><<a href="mailto:avagin@parallels.com">avagin@parallels.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 03/14/2012 11:26 AM, Maoke wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
yes but we still have other troubles with the 2.6.32-042stab044.11. :P so we are trying to understand the problem first.<br>
</blockquote></div>
I don't suggest to move on 2.6.32 kernel. I said about 2.6.18-028stabXXX.Y. You can find a last stable 2.6.18 kernel here: <a href="http://download.openvz.org/kernel/branches/rhel5-2.6.18/stable/" target="_blank">http://download.openvz.org/kernel/branches/rhel5-2.6.18/stable/</a><br>
<br>
This issue may be already fixed.<br></blockquote><div><br></div><div>thanks for the information! then is this a known bug of the old kernel? is there a way to repeat it so that we may test before putting the new kernel to the production environment. thanks again!</div>
<div><br></div><div>maoke</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- maoke<br>
<br>
2012/3/14 Andrew Vagin <<a href="mailto:avagin@parallels.com" target="_blank">avagin@parallels.com</a> <mailto:<a href="mailto:avagin@parallels.com" target="_blank">avagin@parallels.com</a>>><div><div class="h5">
<br>
<br>
2.6.18-194.3.1.el5.028stab069.6xen is a very old version. Could<br>
you update it?<br>
<br>
<br>
On 03/14/2012 10:28 AM, Maoke wrote:<br>
<br>
sorry if this is more of a Xen problem.<br>
<br>
we are running openvz in Xen PVs (kernel<br>
2.6.18-194.3.1.el5.028stab069.6xen), and occasionally the<br>
network of a PV, as well as the PV's hosted containers, at a<br>
virtual interface is lost. sometimes restarting the network<br>
can solve the problem but in most cases we have to restart the<br>
PV. the PVs another virtual interface was working and other<br>
PVs and the HV keeps working.<br>
<br>
detailed observation through tcpdump at the trouble time shows:<br>
1. the inbound traffics can be delivered correctly through<br>
eth0 of the PV until venet0;<br>
2. it looks the venet0 is also correctly functioned because<br>
TCP sync may get response from container and this sync ack can<br>
be seen at venet0;<br>
3. but at the eth0 of PV, we only have seen the TCP sync<br>
request towards the containers while the sync ack is missing,<br>
thus TCP state of the container's application remains SYNC_RECV<br>
4. if ping the PV, at the eth0, we only have seen the ICMP<br>
echo requests but the replies are missing.<br>
<br>
we didn't encounter the same problem when those openvz stuffs<br>
were running over physical machine instead of xen.<br>
<br>
does anyone have any hints or ideas? thanks a lot in advance.<br>
<br>
- maoke<br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br></div></div>
<a href="mailto:Users@openvz.org" target="_blank">Users@openvz.org</a> <mailto:<a href="mailto:Users@openvz.org" target="_blank">Users@openvz.org</a>><br>
<a href="https://openvz.org/mailman/listinfo/users" target="_blank">https://openvz.org/mailman/listinfo/users</a><br>
<br>
<br>
<br>
</blockquote>
<br>
</blockquote></div><br>