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/
Home Products Support Community News


[Xen-users] TX/RX ring buffer allocation (xen-unstable)

To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] TX/RX ring buffer allocation (xen-unstable)
From: Birger Toedtmann <btoedtmann@xxxxxxxxxxxxxx>
Date: Tue, 08 Nov 2005 19:57:03 +0100
Delivery-date: Tue, 08 Nov 2005 18:57:19 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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

I did not find any hints in the web where to configure/setup/manipulate
the rx/tx ring buffer allocation within dom0 for xen-unstable, maybe
someone here can nudge me towards the right knob.

The problem: when booting a handful of domUs and connecting them
(comprising a small experimental IP network with links and nodes etc.),
some interfaces that have been given by the configuration files won't be
set up properly inside the domUs.

Example config snippet for such a domU:

  name = "node03"
  kernel = "/boot/vmlinuz-"
  memory = 24
  disk = [ 'phy:mapper/xenrootfs.node03,sda1,w' ]
  hostname = "node03"
  root = "/dev/sda1 ro"
  vif = [ 'bridge=hub01','bridge=hub02','bridge=hub03','bridge=hub04', ]
  nics = 4

Result (dmesg from booted "node03"):

  xen_net: Initialising virtual ethernet driver.
  #### netfront can't alloc rx grant refs
  vif: probe of vif-3 failed with error -12

- so the first three got set up properly and the fourth failed.  The
nodes (domU) and the networking for dom0/domUs works perfect, however, I
cannot configure as much interfaces as I want inside the domUs.

Skimming through the code the above error message seems to suggest that
the ring buffers are exhausted and another (the fourth) interface cannot
be set up for the domU in question.  However, this happens reproducible
with any main memory configuration for dom0/domU (extended both to
256/48, same error comes up).  So I guess the buffer allocation has to
be configured somehwere else - the question is: where?

I appreciate any suggestions.  xm dmesg/info are attached below.

Birger Tödtmann                   email:btoedtmann@xxxxxxxxxxxxxx
Technik der Rechnernetze, Institut für Experimentelle Mathematik
Universität Duisburg-Essen, Campus Essen, Germany.
skype:birger.toedtmann  pgp:0x6FB166C9  phone: +49-(0)201-1837662

        1 x dom0:    128MB
        6 x domU: 6 x 24MB

# xm info
system                 : Linux
host                   : IsidorP
release                :
version                : #1 Mon Nov 7 10:00:53 CET 2005
machine                : i686
nr_cpus                : 1
nr_nodes               : 1
sockets_per_node       : 1
cores_per_socket       : 1
threads_per_core       : 1
cpu_mhz                : 1156
hw_caps                : 0383fbff:c1c3fbff:00000000:00000020
memory                 : 511
free_memory            : 221
xen_major              : 3
xen_minor              : 0
xen_extra              : -devel
xen_caps               : xen_3.0_x86_32
xen_params             : virt_start=0xfc000000
xen_changeset          : Sun Nov  6 18:50:33 2005 +0100
cc_compiler            : gcc version 3.4.4 (Gentoo 3.4.4-r1,
ssp-3.4.4-1.0, pie-8.7.8)
cc_compile_by          : root
cc_compile_domain      : (none)
cc_compile_date        : Mon Nov  7 09:37:18 CET 2005

# xm dmesg
 Xen version 3.0-devel (root@) (gcc version 3.4.4 (Gentoo 3.4.4-r1,
ssp-3.4.4-1.0, pie-8.7.8)) Mon N ov  7 09:37:18 CET 2005
 Latest ChangeSet: Sun Nov  6 18:50:33 2005 +0100 7628:270469d40f02

(XEN) Physical RAM map:
(XEN)  0000000000000000 - 000000000009fc00 (usable)
(XEN)  000000000009fc00 - 00000000000a0000 (reserved)
(XEN)  00000000000f0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 000000001fff0000 (usable)
(XEN)  000000001fff0000 - 000000001fff3000 (ACPI NVS)
(XEN)  000000001fff3000 - 0000000020000000 (ACPI data)
(XEN)  00000000fec00000 - 00000000fec01000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ffff0000 - 0000000100000000 (reserved)
(XEN) System RAM: 511MB (523836kB)
(XEN) Xen heap: 10MB (10668kB)
(XEN) PAE disabled.
(XEN) DMI 2.2 present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP (v000 KT400                                 ) @
(XEN) ACPI: RSDT (v001 KT400  AWRDACPI 0x42302e31 AWRD 0x00000000) @
(XEN) ACPI: FADT (v001 KT400  AWRDACPI 0x42302e31 AWRD 0x00000000) @
(XEN) ACPI: DSDT (v001 KT400  AWRDACPI 0x00001000 MSFT 0x0100000d) @
(XEN) Found and enabled local APIC!
(XEN) Initializing CPU#0
(XEN) Detected 1156.402 MHz processor.
(XEN) Using scheduler: Simple EDF Scheduler (sedf)
(XEN) CPU: CLK_CTL MSR was 60031223. Reprogramming to 20031223
(XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
(XEN) CPU: L2 Cache: 256K (64 bytes/line)
(XEN) CPU0: AMD Athlon(tm)  stepping 01
(XEN) SMP motherboard not detected.
(XEN) spurious 8259A interrupt: IRQ7.
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 1 CPUs
(XEN) mtrr: v2.0 (20020519)
(XEN) Xen-ELF header found:
(XEN)  Dom0 alloc.:   02000000->04000000 (24576 pages to be allocated)
(XEN)  Loaded kernel: c0100000->c0660904
(XEN)  Init. ramdisk: c0661000->c1025000
(XEN)  Phys-Mach map: c1025000->c1045000
(XEN)  Start info:    c1045000->c1046000
(XEN)  Page tables:   c1046000->c104c000
(XEN)  Boot stack:    c104c000->c104d000
(XEN)  TOTAL:         c0000000->c1400000
(XEN)  ENTRY ADDRESS: c0100000
(XEN) Initrd len 0x9c4000, start at 0xc0661000
(XEN) Scrubbing Free RAM: ......done.
(XEN) Xen trace buffers: disabled
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
input to Xen).

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] TX/RX ring buffer allocation (xen-unstable), Birger Toedtmann <=