Hi all,
I have the strangest issue here: I upgraded my Dell T300 system
("[i]server[/i]") from 8GiB to 16 GiB memory. When I boot snv 130 (and
at least 127) with more than 8 GiB of installed memory outbound network traffic
is impossible.
[b]memory[/b]
- 2 * 2 GiB Module
- 2 * 2 GiB Module
- 2 * 4 GiB Module
[b]grub[/b]
title snv_130
findroot (pool_rpool,0,a)
bootfs rpool/ROOT/snv_130
kernel$ /boot/$ISADIR/xen.gz console=vga dom0_mem=4096M dom0_vcpus_pin=false
watchdog=false
module$ /platform/i86xpv/kernel/$ISADIR/unix
/platform/i86xpv/kernel/$ISADIR/unix -B $ZFS-BOOTFS
module$ /platform/i86pc/$ISADIR/boot_archive
[b]network[/b]
When I ping the [i]server[/i] the following happens:
On the [i]server[/i] the arp entry for the [i]client[/i] is set.
On the [i]client[/i] the arp entry for the [i]server[/i] is [b]never[/b] set.
Networking between dom0 and domU and between dom0 and zones works. Networking
between [i]client[/i] and domU/zones shows the errors described above.
[b]tests[/b]
I tried snv 130 and 127 (XVM). Both showed the same behavior: No network with 12
or 16 GiB, stable network with 8 GiB. snv 130 [i]without[/i] xvm works with 16
GiB of RAM installed.
Swapping the memory modules does not alter the effect.
Has anybody experienced this? What can I do to get it to work?
Regards,
Jens
--
This message posted from opensolaris.org
Jens Neuhalfen wrote:> Hi all, > > I have the strangest issue here: I upgraded my Dell T300 system ("[i]server[/i]") from 8GiB to 16 GiB memory. When I boot snv 130 (and at least 127) with more than 8 GiB of installed memory outbound network traffic is impossible. > > [b]memory[/b] > - 2 * 2 GiB Module > - 2 * 2 GiB Module > - 2 * 4 GiB Module > > [b]grub[/b] > title snv_130 > findroot (pool_rpool,0,a) > bootfs rpool/ROOT/snv_130 > kernel$ /boot/$ISADIR/xen.gz console=vga dom0_mem=4096M dom0_vcpus_pin=false watchdog=false > module$ /platform/i86xpv/kernel/$ISADIR/unix /platform/i86xpv/kernel/$ISADIR/unix -B $ZFS-BOOTFS > module$ /platform/i86pc/$ISADIR/boot_archive > > [b]network[/b] > When I ping the [i]server[/i] the following happens: > > On the [i]server[/i] the arp entry for the [i]client[/i] is set. > > On the [i]client[/i] the arp entry for the [i]server[/i] is [b]never[/b] set. > > > Networking between dom0 and domU and between dom0 and zones works. Networking between [i]client[/i] and domU/zones shows the errors described above.What about client <=> dom0?> [b]tests[/b] > I tried snv 130 and 127 (XVM). Both showed the same behavior: No network with 12 or 16 GiB, stable network with 8 GiB. snv 130 [i]without[/i] xvm works with 16 GiB of RAM installed. > > Swapping the memory modules does not alter the effect. > > Has anybody experienced this? What can I do to get it to work?No. What is the dom0 NIC? Have you tried snooping on the vnic to see what is moving through? I am guessing the NIC your using doesn''t support 64-bit DMA addresses and there isn''t enough low memory in dom0? MRJ
Hi mrj, thank you for your quick reply.> What about client dom0?This is (was, see below) the problem: all communication ways ''leaving'' the server were somehow blocked. I "kind-of-solved" the problem by partitioning the available memory: title snv_130 XEN, 16 GiB RAM findroot (pool_rpool,0,a) bootfs rpool/ROOT/snv_130 kernel$ /boot/$ISADIR/xen.gz console=vga dom0_mem=8G mem=16G dom0_vcpus_pin=false watchdog=false module$ /platform/i86xpv/kernel/$ISADIR/unix /platform/i86xpv/kernel/$ISADIR/unix -B $ZFS-BOOTFS module$ /platform/i86pc/$ISADIR/boot_archive That is 8GB dom0 and 8GB for Xen. This did the trick and I have network again. Jens -- This message posted from opensolaris.org
On 7 Jan 2010, at 11:23pm, Jens Neuhalfen wrote:> This is (was, see below) the problem: all communication ways ''leaving'' the server were somehow blocked. > > I "kind-of-solved" the problem by partitioning the available memory:Which NIC is this?