WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] XenExpress HVM: netback grant fails

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] XenExpress HVM: netback grant fails
From: Ondrej Kraus <krauso-xen@xxxxxxx>
Date: Sun, 28 Jan 2007 15:46:29 +0100
Delivery-date: Sun, 28 Jan 2007 06:46:26 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.9 (X11/20070103)
Hello,

during this week, I have installed new Windows 2003 virtual machine
under XenExpress 3.1.0. Then I migrated web sites into this new server.
Everything worked fine, but after 20 hours virtual machine creshed and
rebooted. The same situation then repeated 2 times, so we have 3 crashes
within a day.

XenExpress is installed od Dell PowerEdge 860 with Xeon 3060 and 4GB of
memory. I installed PV drivers in VM. This VM has 2GB of memory and 3
virtual disks. There is another VM with W2003 installed, equipped with
1G of memory and 2 disks. This another VM is stable, but is not under as
high load as crashing one.

Here is log of second crash from Dom-0:

Jan 27 18:57:42 x001 HVMXEN-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx[9811]:
Warning: try write to xen platform mmio space
Jan 27 18:57:42 x001 last message repeated 8 times
Jan 27 18:57:42 x001 kernel: #### netback grant fails

this log fragment repeated at least 20 times and then VM rebooted:

Jan 27 18:57:45 x001 kernel: #### netback grant fails
Jan 27 18:57:45 x001 HVMXEN-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx[9811]:
Warning: try read from xen platform mmio space
Jan 27 18:57:45 x001 kernel: xenbr1: port 3(vif4.0) entering disabled state
Jan 27 18:57:45 x001 kernel: device vif4.0 left promiscuous mode
Jan 27 18:57:45 x001 kernel: xenbr1: port 3(vif4.0) entering disabled state
Jan 27 18:57:45 x001 net.agent[11274]: remove event not handled
Jan 27 18:57:45 x001 net.agent[11308]: remove event not handled
Jan 27 18:57:48 x001 kernel: netbk: WARNING: device 'vif5.0' has
non-zero queue length (32)!
Jan 27 18:57:48 x001 HVMXEN-[11732]: domid: 5
Jan 27 18:57:48 x001 logger: /etc/xen/scripts/vif-bridge: iptables -A
FORWARD -m physdev --physdev-in vif5.0  -j ACCEPT failed. If you are
using iptables, this may affect networking for guest domains.
Jan 27 18:57:48 x001 kernel: device vif5.0 entered promiscuous mode
Jan 27 18:57:48 x001 kernel: ADDRCONF(NETDEV_UP): vif5.0: link is not ready
Jan 27 18:57:50 x001 kernel: device tap0 entered promiscuous mode
Jan 27 18:57:50 x001 kernel: xenbr1: port 4(tap0) entering learning state
Jan 27 18:57:50 x001 kernel: xenbr1: topology change detected, propagating
Jan 27 18:57:50 x001 kernel: xenbr1: port 4(tap0) entering forwarding state
Jan 27 18:57:51 x001 HVMXEN-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx[11732]:
shared page at pfn:7feff, mfn: 29364
Jan 27 18:57:51 x001 HVMXEN-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx[11732]:
buffered io page at pfn:7fefd, mfn: 29366
Jan 27 18:57:51 x001 HVMXEN-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx[11732]:
False I/O request ... in-service already: 0, pvalid: 0, port: 0, data:
0, count: 0, size: 0
Jan 27 18:58:06 x001 HVMXEN-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx[11732]:
Disconnect IDE hard disk...
Jan 27 18:58:06 x001 HVMXEN-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx[11732]:
Disconnect netifs...
Jan 27 18:58:06 x001 HVMXEN-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx[11732]:
Shutdown taps...
Jan 27 18:58:06 x001 kernel: xenbr1: port 4(tap0) entering disabled state
Jan 27 18:58:06 x001 kernel: device tap0 left promiscuous mode
Jan 27 18:58:06 x001 kernel: xenbr1: port 4(tap0) entering disabled state
Jan 27 18:58:06 x001 HVMXEN-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx[11732]:
switching to PV shutdown mode...
Jan 27 18:58:06 x001 HVMXEN-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx[11732]:
Done.
Jan 27 18:58:19 x001 HVMXEN-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx[11732]:
Disconnect IDE hard disk...
Jan 27 18:58:19 x001 HVMXEN-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx[11732]:
Disconnect netifs...
Jan 27 18:58:19 x001 HVMXEN-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx[11732]:
Shutdown taps...
Jan 27 18:58:19 x001 HVMXEN-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx[11732]:
switching to PV shutdown mode...
Jan 27 18:58:19 x001 HVMXEN-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx[11732]:
failed to unregister watch on /local/domain/5/control/shutdown
Jan 27 18:58:19 x001 HVMXEN-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx[11732]:
Done.
Jan 27 18:58:31 x001 kernel: ADDRCONF(NETDEV_CHANGE): vif5.0: link
becomes ready
Jan 27 18:58:31 x001 kernel: xenbr1: port 3(vif5.0) entering learning state
Jan 27 18:58:31 x001 kernel: xenbr1: topology change detected, propagating
Jan 27 18:58:31 x001 kernel: xenbr1: port 3(vif5.0) entering forwarding
state

Thank you for your quick response.

Ondrej Kraus

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>