- Is domU <-> dom0 slow aswell?
No its working well the throughput is around 2000 to 3000 Mbps in this case
- Is domU <-> internet slow?
No, Its working well.
- Do you have errors on domU ethX interfaces?
No such errors seen.
- Do you have errors no dom0 interfaces (pethx, all bridges, all vifs).
No, errors
- Does domU or dom0 have high CPU-usage? What does "top" show in dom0,
and in domU?
To the max 10 to 20% while running netperf
- What does "xm top" say about CPU usage?
cpu usage 10 to 20%
- Do you have errors in the logs? Please check
- dom0 dmesg
NO such messages
- dom0 /var/log/messages
No messages else
this
Sep 14 14:37:09 HPCNL-SR-2 kernel:
vif1.0 (vif): not using net_device_ops yet
Sep 14 14:37:09 HPCNL-SR-2
NetworkManager: nm_device_ethernet_new: assertion `driver != NULL'
failed
Sep 14 14:37:10 HPCNL-SR-2 kernel:
device vif1.0 entered promiscuous mode
Sep 14 14:37:10 HPCNL-SR-2 kernel:
eth0: topology change detected, propagating
Sep 14 14:37:10 HPCNL-SR-2 kernel:
eth0: port 2(vif1.0) entering forwarding state
Sep 14 14:37:10 HPCNL-SR-2 logger:
/etc/xen/scripts/vif-bridge: iptables setup failed. This may affect
guest networking.
Sep 14 14:37:11 HPCNL-SR-2
avahi-daemon[1439]: Registering new address record for
fe80::fcff:ffff:feff:ffff on vif1.0.*.
Sep 14 14:37:11 HPCNL-SR-2 kernel:
blkback: ring-ref 8, event-channel 9, protocol 1 (x86_32-abi)
Sep 14 14:37:14 HPCNL-SR-2
nm-system-settings: Added default wired connection 'Auto vif1.0' for
/org/freedesktop/Hal/devices/net_fe_ff_ff_ff_ff_ff
- Xen log: "xm log"
- Xen dmesg: "xm dmesg"
- domU dmesg
- domU /var/log/messaegs
What does that mean. I am trying all the other logs as well. thanks for your concern.
Regards,
Fasiha