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-devel

Re: [Xen-devel] Zombie domain when using vif rate parameter?

To: "Fischer, Anna" <anna.fischer@xxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Zombie domain when using vif rate parameter?
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 25 Apr 2008 10:13:54 +0100
Delivery-date: Fri, 25 Apr 2008 02:15:08 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <38CBA1F6A350B044AF785E63AAC3C6776497B841CD@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcimsY/rdAzsn5BjRwiHvHIzMlZOhQAAx8OU
Thread-topic: [Xen-devel] Zombie domain when using vif rate parameter?
User-agent: Microsoft-Entourage/11.4.0.080122
Hit the 'q' debug key and see how many pages the zombie domain(s) still have
allocated to them. This is probably a netback bug, holding onto resources
when it shouldn't.

 -- Keir

On 25/4/08 09:51, "Fischer, Anna" <anna.fischer@xxxxxx> wrote:

> I'm using the vif rate parameter to control outbound network bandwidth for Xen
> guests. It works fine. However, when shutting down guests that have a rate
> limit specified in the config file, then that creates zombie domains on the
> machine. When shutting down domains that don't have a rate limit set, I don't
> see any zombie domains at all, so I'm quite confident that the zombie domains
> are resulting from the rate limiting.
> 
> Is this a known issue or is there something I can do in order to prevent the
> appearance of zombie domains? I'm not seeing any error messages in the Xen or
> system logs. Please find some more details on my configuration below. I'm
> using Xen in bridged networking mode.
> 
> Thanks,
> Anna
> 
> --------------------
> 
> xm log
> [2008-04-25 09:10:10 xend] INFO (image:136) buildDomain os=linux dom=2 vcpus=1
> [2008-04-25 09:10:11 xend] INFO (XendDomain:363) Domain vm1 (2) unpaused.
> [2008-04-25 09:11:34 xend] INFO (image:136) buildDomain os=linux dom=3 vcpus=1
> [2008-04-25 09:11:34 xend] INFO (XendDomain:363) Domain vm5 (3) unpaused.
> [2008-04-25 09:16:52 xend.XendDomainInfo] INFO (XendDomainInfo:840) Domain has
> shutdown: name=vm1 id=2 reason=poweroff.
> [2008-04-25 09:17:14 xend] INFO (image:136) buildDomain os=linux dom=4 vcpus=1
> [2008-04-25 09:17:14 xend] INFO (XendDomain:363) Domain vm1 (4) unpaused.
> [2008-04-25 09:18:39 xend.XendDomainInfo] INFO (XendDomainInfo:840) Domain has
> shutdown: name=vm1 id=4 reason=poweroff.
> [2008-04-25 09:19:18 xend] INFO (image:136) buildDomain os=linux dom=5 vcpus=1
> [2008-04-25 09:19:19 xend] INFO (XendDomain:363) Domain vm2 (5) unpaused.
> [2008-04-25 09:29:18 xend.XendDomainInfo] INFO (XendDomainInfo:840) Domain has
> shutdown: name=vm2 id=5 reason=poweroff.
> [2008-04-25 09:29:28 xend] INFO (image:136) buildDomain os=linux dom=6 vcpus=1
> [2008-04-25 09:29:28 xend] INFO (XendDomain:363) Domain vm2 (6) unpaused.
> [2008-04-25 09:39:51 xend.XendDomainInfo] INFO (XendDomainInfo:840) Domain has
> shutdown: name=vm2 id=6 reason=poweroff.
> 
> 
> xm list
> Name                              ID Mem(MiB) VCPUs State  Time(s)
> Domain-0                           0     7142     2 r-----   245.3
> Zombie-vm1                         2      384     1 ---s-d    24.0
> Zombie-vm2                         6      384     1 ---s-d    43.7
> vm5                                3      384     1 ------    63.2
> 
> 
> cat vm2.cfg
> kernel = "/boot/vmlinuz-domU"
> ramdisk = "/boot/initrd-domU"
> root = "/dev/sda1 ro"
> memory = "384"
> extra = "TERM=xterm xencons=tty"
> name = "vm2"
> vif = [ 'vifname=v2,mac=00:50:56:19:a6:c2,rate=256Mb/s' ]
> disk = [ 'phy:/dev/xen_8,sda1,w' ]
> 
> 
> 
> xm info
> release                : 2.6.16.13-4-xen
> version                : #1 SMP Wed May 3 04:53:23 UTC 2006
> machine                : x86_64
> nr_cpus                : 2
> nr_nodes               : 1
> sockets_per_node       : 2
> cores_per_socket       : 1
> threads_per_core       : 1
> cpu_mhz                : 2605
> hw_caps                : 078bfbff:e3d3fbff:00000000:00000010:00000001
> total_memory           : 8024
> free_memory            : 3
> max_free_memory        : 6949
> xen_major              : 3
> xen_minor              : 0
> xen_extra              : .2_09656-4
> xen_caps               : xen-3.0-x86_64
> platform_params        : virt_start=0xffff800000000000
> xen_changeset          : 09656
> cc_compiler            : gcc version 4.1.0 (SUSE Linux)
> cc_compile_by          : abuild
> cc_compile_domain      : suse.de
> cc_compile_date        : Tue May  2 11:18:44 UTC 2006
> 
> 
> xm dmesg
>  __  __            _____  ___   ____      ___   ___   __  ____   __      _  _
>  \ \/ /___ _ __   |___ / / _ \ |___ \    / _ \ / _ \ / /_| ___| / /_    | || |
>   \  // _ \ '_ \    |_ \| | | |  __) |  | | | | (_) | '_ \___ \| '_ \ __| ||
> |_
>   /  \  __/ | | |  ___) | |_| | / __/   | |_| |\__, | (_) |__) | (_) |__|__
> _|
>  /_/\_\___|_| |_| |____(_)___(_)_____|___\___/   /_/ \___/____/ \___/      |_|
>                                     |_____|
>  http://www.cl.cam.ac.uk/netos/xen
>  University of Cambridge Computer Laboratory
> 
>  Xen version 3.0.2_09656-4 (abuild@xxxxxxx) (gcc version 4.1.0 (SUSE Linux))
> Tue May  2 11:18:44 UTC 2006
>  Latest ChangeSet: 09656
> 
> (XEN) Command line: /xen.gz  noreboot
> (XEN) Physical RAM map:
> (XEN)  0000000000000000 - 000000000009f400 (usable)
> (XEN)  000000000009f400 - 00000000000a0000 (reserved)
> (XEN)  00000000000f0000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 00000000f57f6800 (usable)
> (XEN)  00000000f57f6800 - 00000000f5800000 (ACPI data)
> (XEN)  00000000fdc00000 - 00000000fdc01000 (reserved)
> (XEN)  00000000fdc10000 - 00000000fdc11000 (reserved)
> (XEN)  00000000fec00000 - 00000000fec01000 (reserved)
> (XEN)  00000000fec10000 - 00000000fec11000 (reserved)
> (XEN)  00000000fec20000 - 00000000fec21000 (reserved)
> (XEN)  00000000fee00000 - 00000000fee10000 (reserved)
> (XEN)  00000000ff800000 - 0000000100000000 (reserved)
> (XEN)  0000000100000000 - 00000001fffff000 (usable)
> (XEN) System RAM: 8023MB (8216144kB)
> (XEN) Xen heap: 14MB (14348kB)
> (XEN) Using scheduler: Simple EDF Scheduler (sedf)
> (XEN) found SMP MP-table at 000f4fa0
> (XEN) DMI 2.3 present.
> (XEN) Using APIC driver default
> (XEN) ACPI: RSDP (v002 HP                                    ) @
> 0x00000000000f4f20
> (XEN) ACPI: XSDT (v001 HP     A02      0x00000002 \ufffd 0x0000162e) @
> 0x00000000f57f6be0
> (XEN) ACPI: FADT (v003 HP     A02      0x00000002 \ufffd 0x0000162e) @
> 0x00000000f57f6c60
> (XEN) ACPI: MADT (v001 HP     00000083 0x00000002  0x00000000) @
> 0x00000000f57f6900
> (XEN) ACPI: SPCR (v001 HP     SPCRRBSU 0x00000001 \ufffd 0x0000162e) @
> 0x00000000f57f69e0
> (XEN) ACPI: SRAT (v001 HP     A02      0x00000001  0x00000000) @
> 0x00000000f57f6a60
> (XEN) ACPI: DSDT (v001 HP         DSDT 0x00000001 MSFT 0x02000001) @
> 0x0000000000000000
> (XEN) ACPI: Local APIC address 0xfee00000
> (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> (XEN) Processor #0 15:5 APIC version 16
> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
> (XEN) Processor #1 15:5 APIC version 16
> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] disabled)
> (XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
> (XEN) ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
> (XEN) IOAPIC[0]: apic_id 4, version 17, address 0xfec00000, GSI 0-23
> (XEN) ACPI: IOAPIC (id[0x05] address[0xfec10000] gsi_base[24])
> (XEN) IOAPIC[1]: apic_id 5, version 17, address 0xfec10000, GSI 24-27
> (XEN) ACPI: IOAPIC (id[0x06] address[0xfec20000] gsi_base[28])
> (XEN) IOAPIC[2]: apic_id 6, version 17, address 0xfec20000, GSI 28-31
> (XEN) ACPI: IOAPIC (id[0x07] address[0xfdc00000] gsi_base[32])
> (XEN) IOAPIC[3]: apic_id 7, version 17, address 0xfdc00000, GSI 32-35
> (XEN) ACPI: IOAPIC (id[0x08] address[0xfdc10000] gsi_base[36])
> (XEN) IOAPIC[4]: apic_id 8, version 17, address 0xfdc10000, GSI 36-39
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
> (XEN) ACPI: IRQ0 used by override.
> (XEN) ACPI: IRQ2 used by override.
> (XEN) Enabling APIC mode:  Flat.  Using 5 I/O APICs
> (XEN) Using ACPI (MADT) for SMP configuration information
> (XEN) Initializing CPU#0
> (XEN) Detected 2605.963 MHz processor.
> (XEN) CPU0: AMD Flush Filter disabled
> (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
> (XEN) CPU: L2 Cache: 1024K (64 bytes/line)
> (XEN) Intel machine check architecture supported.
> (XEN) Intel machine check reporting enabled on CPU#0.
> (XEN) CPU0: AMD Opteron(tm) Processor 252 stepping 01
> (XEN) Booting processor 1/1 eip 90000
> (XEN) Initializing CPU#1
> (XEN) CPU1: AMD Flush Filter disabled
> (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
> (XEN) CPU: L2 Cache: 1024K (64 bytes/line)
> (XEN) AMD: Disabling C1 Clock Ramping Node #0
> (XEN) AMD: Disabling C1 Clock Ramping Node #1
> (XEN) Intel machine check architecture supported.
> (XEN) Intel machine check reporting enabled on CPU#1.
> (XEN) CPU1: AMD Opteron(tm) Processor 252 stepping 01
> (XEN) Total of 2 processors activated.
> (XEN) ENABLING IO-APIC IRQs
> (XEN)  -> Using new ACK method
> (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=0 pin2=0
> (XEN) checking TSC synchronization across 2 CPUs: passed.
> (XEN) Platform timer is 1.193MHz PIT
> (XEN) Brought up 2 CPUs
> (XEN) Machine check exception polling timer started.
> (XEN) Using IPI Shortcut mode
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Domain 0 kernel supports features = { 0000000f }.
> (XEN) Domain 0 kernel requires features = { 00000000 }.
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN)  Dom0 alloc.:   000000000e000000->0000000010000000 (1984486 pages to be
> allocated)
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN)  Loaded kernel: ffffffff80100000->ffffffff80464088
> (XEN)  Init. ramdisk: ffffffff80465000->ffffffff80be9200
> (XEN)  Phys-Mach map: ffffffff80bea000->ffffffff81b1df30
> (XEN)  Start info:    ffffffff81b1e000->ffffffff81b1f000
> (XEN)  Page tables:   ffffffff81b1f000->ffffffff81b30000
> (XEN)  Boot stack:    ffffffff81b30000->ffffffff81b31000
> (XEN)  TOTAL:         ffffffff80000000->ffffffff81c00000
> (XEN)  ENTRY ADDRESS: ffffffff80100000
> (XEN) Dom0 has maximum 2 VCPUs
> (XEN) Initrd len 0x784200, start at 0xffffffff80465000
> (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) mtrr: type mismatch for f6000000,800000 old: uncachable new:
> write-combining
> (XEN) mtrr: type mismatch for f6000000,800000 old: uncachable new:
> write-combining
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



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

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