Hi guys,
there must be something wrong, maybe with xen vif.
I have two test servers
1/ Supermicro 6015C-NT (this story isn''t Supermicro problem!)
2/ HP ML 110 G5
System CentOS 5 (x86_64 for dom0, i86 for domU)
I can perform dom0 installation on both servers, without problem.
But I can''t install domU at Supermicro (I can at HP).
Error:
Unable to retrieve http://192.168.6.100/centos/images/stage2.img
Using
virt-install -d --nographics -p -r 2048 --vcpus 1 -f /dev/lvg1/lv1 -l
http://192.168.6.100/centos/ -n test
Ok, I looking for other way. Migration domU from HP to Supermicro. Done
without problem.
But after domU boot up from Supermicro, I can ping domU, but I can''t
login via
ssh to domU.
Ok, I can login to domU at Supermicro from dom0 console. But there is still
problem with network. I can ping, dig elsewhere, but I can''t do wget,
elinks,
run network services ...
I can''t see any errors log/message.
Supermicro have eth0 + eth1 module igb, Intel 82575EB.
[root@vali2 xen]# brctl show
bridge name bridge id STP enabled interfaces
virbr0 8000.000000000000 yes
xenbr0 8000.feffffffffff no vif1.0
peth0
vif0.0
Maybe, why two vif?
[root@vali2 xen]# xm li
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 1969 4 r----- 14.4
test 1 2047 1 -b---- 12.1
xm dmesg is here
http://fx2.unihost.cz/dom0.log
boot log for domU
http://fx2.unihost.cz/domU.log
other logs
http://fx2.unihost.cz/dmesg
http://fx2.unihost.cz/messages
http://fx2.unihost.cz/xend.log
http://fx2.unihost.cz/domain-builder-ng.log
Thanks in advance
Regards Martin
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Wed, Feb 18, 2009 at 4:32 PM, Martin Fuxa <fuxa_kos@unihost.cz> wrote:> Hi guys, > there must be something wrong, maybe with xen vif. > > I have two test servers > 1/ Supermicro 6015C-NT (this story isn''t Supermicro problem!)It probably IS> 2/ HP ML 110 G5 > > System CentOS 5 (x86_64 for dom0, i86 for domU)what version of xen and kernel-xen (try rpm -q) ?> > I can perform dom0 installation on both servers, without problem. > > But I can''t install domU at Supermicro (I can at HP). > Error: > Unable to retrieve http://192.168.6.100/centos/images/stage2.img > Using > virt-install -d --nographics -p -r 2048 --vcpus 1 -f /dev/lvg1/lv1 -l > http://192.168.6.100/centos/ -n test> Ok, I can login to domU at Supermicro from dom0 console. But there is still > problem with network. I can ping, dig elsewhere, but I can''t do wget, elinks, > run network services ...Sounds like an old problem Try this http://wiki.xensource.com/xenwiki/XenFaq#head-4ce9767df34fe1c9cf4f85f7e07cb10110eae9b7 If you''re still using an old version (from Centos 5.0, for example), you should try updating it to the latest available version first (RHEL 5 is currently at xen-3.0.3-80.el5 and kernel-xen-2.6.18-128.1.1.el5).> > I can''t see any errors log/message. > > Supermicro have eth0 + eth1 module igb, Intel 82575EB. > [root@vali2 xen]# brctl show > bridge name bridge id STP enabled interfaces > virbr0 8000.000000000000 yes > xenbr0 8000.feffffffffff no vif1.0 > peth0 > vif0.0 > Maybe, why two vif?It''s normal. vif1.0 is your domU''s eth0, vif0.0 is the backend for your dom0''s eth0, peth0 is your real eth0. Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> You stop firewall (iptables -F)?Yes, on dom0 and domU. SElinux is disabled too.> what version of xen and kernel-xen (try rpm -q) ?System is up2date from CentOS repository. [fuxa@vali2 ~]$ rpm -qa |grep xen kernel-xen-2.6.18-92.el5 xen-libs-3.0.3-64.el5_2.9 kernel-xen-2.6.18-92.1.22.el5 xen-3.0.3-64.el5_2.9 xen-libs-3.0.3-64.el5_2.9 [fuxa@vali2 ~]$ uname --all Linux vali2 2.6.18-92.1.22.el5xen #1 SMP Tue Dec 16 12:26:32 EST 2008 x86_64 x86_64 x86_64 GNU/Linux> Sounds like an old problem > Try this >http://wiki.xensource.com/xenwiki/XenFaq#head-4ce9767df34fe1c9cf4f85f7e07cb10110eae9b7 great! looks like same problem. Before I post my story to mailing, I read all xen faq''s, but don''t equate to my problem, if I can recommend more description - for other users with similar problem. I tried "tcpdump -vv -n -i eth0" and read relevant posts, it''s working, but networking on domU is still very slow. tcpdump says cksum (correct) time wget -q http://www.yahoo.com/ dom0 (that''s ok) real 0m0.210s domU (slow) real 0m10.206s I''ll try RHEL 5 kernel and xen. Many thanks for pointing. Thanks in advance Regards Martin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Sounds like an old problem > Try this > http://wiki.xensource.com/xenwiki/XenFaq#head-4ce9767df34fe1c9cf4f85f7e07cb >10110eae9b7Is it problem Xen versus NIC or mainboard? If I''ll add/use PCIe NIC card (like Intel Pro 1000 PT or Broadcom NetXtreme), solve this problem? Thanks in advance Regards Martin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Feb 18, 2009 at 11:37 PM, Martin Fuxa <fuxa_kos@unihost.cz> wrote:>> Sounds like an old problem >> Try this >> http://wiki.xensource.com/xenwiki/XenFaq#head-4ce9767df34fe1c9cf4f85f7e07cb >>10110eae9b7 > > Is it problem Xen versus NIC or mainboard?Most likely NIC driver problem.> If I''ll add/use PCIe NIC card (like Intel Pro 1000 PT or Broadcom NetXtreme), > solve this problem?Well, so far I only use Broadcom (drivers tg3 and bnx2). The ones with tg3 used to have a similar problem back in the days of RHEL 5.0. It''s working correctly now without the need for any workaround (I can''t remember whether it was 5.1 or 5.2 that solved the problem). Here''s what I currently use (all onboard NIC): Ethernet controller: Broadcom Corporation NetXtreme BCM5704S Gigabit Ethernet (rev 10) Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) Ethernet controller: Broadcom Corporation NetXtreme II BCM5708S Gigabit Ethernet (rev 12) The drivers for your NIC might haven''t been widely-tested enough so using a common, well-known, old-enough NIC might solve your problems. Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users