<br><br><div><span class="gmail_quote">On 7/12/07, <b class="gmail_sendername">Asrai khn</b> <<a href="mailto:asraikhn@gmail.com">asraikhn@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>We have recently update kernel-xen <span id="st" name="st" class="st">on</span> all of our hosts (3) and its vms all <span id="st" name="st" class="st">running</span> fc6. kernel-xen <span id="st" name="st" class="st">
2</span>.6.2<span id="st" name="st" class="st">0</span>-1.<span id="st" name="st" class="st">2962</span>.<span id="st" name="st" class="st">fc6xen</span> is doing good <span id="st" name="st" class="st">on</span> two hosts and all its vms (1
<span id="st" name="st" class="st">0</span>), however its giving lot of problem <span id="st" name="st" class="st">on</span> third <span id="st" name="st" class="st">host</span>.
<br><br>when i reboots the <span id="st" name="st" class="st">host</span> into latest kernel-xen the <span id="st" name="st" class="st">domUs</span> <span id="st" name="st" class="st">become</span> <span id="st" name="st" class="st">
unaccessible</span> in a while hardly run for 1<span id="st" name="st" class="st">0</span> minutes, 'xm list' still shows there status but i can't access it from outside.<br><br>We are using loop back files for
<span id="st" name="st" class="st">domUs</span> File system, for testing i rebooted <span id="st" name="st" class="st">host</span> into last working kernel
<span id="st" name="st" class="st">2</span>.6.2<span id="st" name="st" class="st">0</span>-1.2952.<span id="st" name="st" class="st">fc6xen</span> and <span id="st" name="st" class="st">domUs</span> into latest kernel-xen and its doing pretty good, which mean latest kernel-xen is only giving problem at
<span id="st" name="st" class="st">host</span> side.<br><br>when <span id="st" name="st" class="st">running</span> <span id="st" name="st" class="st">2</span>.6.2<span id="st" name="st" class="st">0</span>-1.<span id="st" name="st" class="st">
2962</span> <span id="st" name="st" class="st">on</span> <span id="st" name="st" class="st">host</span> it giving this in /var/log/messages
<br><br>Jul 12 1<span id="st" name="st" class="st">0</span>:42:45 xxxx kernel: xen_net: Memory squeeze in netback driver.<br>Jul 12 1<span id="st" name="st" class="st">0</span>:42:5<span id="st" name="st" class="st">0</span>
xxxx kernel: printk: 4 messages suppressed.<br>Jul 12 1<span id="st" name="st" class="st">0</span>:42:5<span id="st" name="st" class="st">0</span> xxxx kernel: xen_net: Memory squeeze in netback driver.<br>
Jul 12 1<span id="st" name="st" class="st">0</span>:42:55 xxxx kernel: printk: 4 messages suppressed.</blockquote><div>(...)<br><br>Same thing happen again when today i updated host kernel-xen from
<span id="st" name="st" class="st">2</span>.6.2<span id="st" name="st" class="st">0</span>-1.2952.<span id="st" name="st" class="st">fc6xen To </span>2.6.20-1.2999.fc6xen. It working fine at domUs but when I reboot the domO into
2.6.20-1.2999.fc6xen it start giving these errors in <br><br>Aug 23 18:41:52 xxxx kernel: printk: 4 messages suppressed.<br>Aug 23 18:41:52 xxxx kernel: xen_net: Memory squeeze in netback driver.<br>Aug 23 18:41:57 xxxxl kernel: printk: 4 messages suppressed.
<br>Aug 23 18:41:57 xxxx kernel: xen_net: Memory squeeze in netback driver.<br>Aug 23 18:42:02 xxxxxl kernel: printk: 4 messages suppressed.<br>Aug 23 18:42:02 xxx kernel: xen_net: Memory squeeze in netback driver.<br><br>
and all domUs become unaccessible, in end I have to revert back to <span id="st" name="st" class="st">2</span>.6.2<span id="st" name="st" class="st">0</span>-1.2952.<span id="st" name="st" class="st">fc6xen at domO (host) :-s
<br><br>Any help in this regard will be highly appreciated.<br><br>Regards. Askar<br></span><br></div></div><br>