[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Live migration problem



I am using the 2.6.11 kernel.

I used the binary installs with the exception of 'xfrd' which I had to build on my fedore core 4 boxes (since the binary install is linked with versions of libcurl, libssl, and libcrypto that aren't there -- all other tools and kernels are from the binary install). I got the same problem when migrating. I was successfully 8 times, but on the 9th migrate it failed. Attached is the output of 'xm dmesg' on the source host. I will keep everything as it is now if you need more information from the logs.

Thanks,
Steven


Ian Pratt wrote:

I downloaded 2.0.7 and did a make world; make install

Please can you try using our binary installs.

Also, are you using the 2.6.11 kernel or the 2.4?

After the failed migrate, what does 'xm dmesg' show on the source host.

Ian

If you need anymore information, just let me know...

Thanks much,
Steven

Ian Pratt wrote:



I think I am having a similar problem as this:

http://lists.xensource.com/archives/html/xen-users/2005-04/msg
00251.html

on xen 2.0.7

I can live migrate successfully 90% of the time, but I do
hit this.
Is there an update on the status of a fix?
This is nasty -- the domain is probably crashing during the
migrate. We
have never seen this failure mode on 2.0.7, even after many
thousands
of migrates.

Have you compiled your own kernel or are you using one of ours? (I presume 2.6.11 ?)

What are you running in the guest?

What does 'xm dmesg' show?

Ian



The last part of the xfer log:

[1123789954.329159] Saving memory pages: iter 28   0%
Saving memory pages: iter 28   0%^M 28: sent 34, skipped 0,
^M 28: sent 34, skipped 0, [DEBUG] Conn_sxpr> (xfr.err 22)[DEBUG] Conn_sxpr< err=0 Retry suspend domain (0) (repeated 350
times or so)
Retry suspend domain (0) Unable to suspend domain. (0) Unable to suspend domain. (0) Domain appears not to have suspended: 0 Domain appears not to have
suspended: 0
4155 [WRN] XFRD> Transfer errors:
4155 [WRN] XFRD> state=XFR_STATE    err=1
4155 [INF] XFRD> Xfr service err=1

Thanks much for any help.

Steven


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
ERROR: cannot use unconfigured serial port COM1
 __  __            ____    ___  _____ 
 \ \/ /___ _ __   |___ \  / _ \|___  |
  \  // _ \ '_ \    __) || | | |  / / 
  /  \  __/ | | |  / __/ | |_| | / /  
 /_/\_\___|_| |_| |_____(_)___(_)_/   
                                      
 http://www.cl.cam.ac.uk/netos/xen
 University of Cambridge Computer Laboratory

 Xen version 2.0.7 (xenod@xxxxxxxxxxxx) (gcc version 3.3.3 20040412 (Red Hat 
Linux 3.3.3-7)) Thu Aug  4 00:37:06 BST 2005
 Latest ChangeSet: Thu Aug  4 00:24:27 2005 
973a2d3c7a63c17d318332b65cb3fc5f8d104cd3

(XEN) Physical RAM map:
(XEN)  0000000000000000 - 00000000000a0000 (usable)
(XEN)  0000000000100000 - 000000003ffd7000 (usable)
(XEN)  000000003ffd7000 - 000000003ffefc00 (ACPI data)
(XEN)  000000003ffefc00 - 000000003ffff000 (reserved)
(XEN)  00000000fec00000 - 00000000fec10000 (reserved)
(XEN)  00000000fee00000 - 00000000fee10000 (reserved)
(XEN)  00000000fff80000 - 0000000100000000 (reserved)
(XEN) System RAM: 1023MB (1048028kB)
(XEN) Xen heap: 10MB (10764kB)
(XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
(XEN) CPU#0: Hyper-Threading is disabled
(XEN) CPU caps: bfebfbff 00000000 00000000 00000000
(XEN) found SMP MP-table at 000fe710
(XEN) ACPI: RSDP (v000 DELL                                      ) @ 0x000fdc30
(XEN) ACPI: RSDT (v001 DELL   PE1750   0x00000001 MSFT 0x0100000a) @ 0x000fdc44
(XEN) ACPI: FADT (v001 DELL   PE1750   0x00000001 MSFT 0x0100000a) @ 0x000fdc74
(XEN) ACPI: MADT (v001 DELL   PE1750   0x00000001 MSFT 0x0100000a) @ 0x000fdce8
(XEN) ACPI: SPCR (v001 DELL   PE1750   0x00000001 MSFT 0x0100000a) @ 0x000fdd7a
(XEN) ACPI: DSDT (v001 DELL     PE1750 0x00000001 MSFT 0x0100000a) @ 0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 Pentium 4(tm) XEON(tm) APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] disabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
(XEN) Using ACPI for processor (LAPIC) configuration information
(XEN) Intel MultiProcessor Specification v1.4
(XEN)     Virtual Wire compatibility mode.
(XEN) OEM ID: DELL     Product ID: PE 014A      APIC at: 0xFEE00000
(XEN) I/O APIC #8 Version 17 at 0xFEC00000.
(XEN) I/O APIC #9 Version 17 at 0xFEC01000.
(XEN) I/O APIC #10 Version 17 at 0xFEC02000.
(XEN) Enabling APIC mode: Flat. Using 3 I/O APICs
(XEN) Processors: 1
(XEN) Using scheduler: Borrowed Virtual Time (bvt)
(XEN) Initializing CPU#0
(XEN) Detected 2782.686 MHz processor.
(XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
(XEN) CPU#0: Hyper-Threading is disabled
(XEN) CPU caps: bfebfbff 00000000 00000000 00000000
(XEN) CPU0 booted
(XEN) enabled ExtINT on CPU#0
(XEN) ESR value before enabling vector: 00000000
(XEN) ESR value after enabling vector: 00000000
(XEN) Error: only one processor found.
(XEN) ENABLING IO-APIC IRQs
(XEN) Setting 8 in the phys_id_present_map
(XEN) ...changing IO-APIC physical APIC ID to 8 ... ok.
(XEN) Setting 9 in the phys_id_present_map
(XEN) ...changing IO-APIC physical APIC ID to 9 ... ok.
(XEN) Setting 10 in the phys_id_present_map
(XEN) ...changing IO-APIC physical APIC ID to 10 ... ok.
(XEN) init IO_APIC IRQs
(XEN) ..TIMER: vector=0x41 pin1=2 pin2=0
(XEN) ..MP-BIOS bug: 8254 timer not connected to IO-APIC
(XEN) ...trying to set up timer (IRQ0) through the 8259A ... 
(XEN) ..... (found pin 0) ...works.
(XEN) Using local APIC timer interrupts.
(XEN) Calibrating APIC timer for CPU0...
(XEN) ..... CPU speed is 2782.7369 MHz.
(XEN) ..... Bus speed is 132.5111 MHz.
(XEN) ..... bus_scale = 0x000087B3
(XEN) Time init:
(XEN) .... System Time: 11407347ns
(XEN) .... cpu_freq:    00000000:A5DC6E50
(XEN) .... scale:       00000001:6FFD5B13
(XEN) .... Wall Clock:  1124100693s 130000us
(XEN) PCI: PCI BIOS revision 2.10 entry at 0xfc91e, last bus=4
(XEN) PCI: Using configuration type 1
(XEN) PCI: Probing PCI hardware
(XEN) PCI: Probing PCI hardware (bus 00)
(XEN) PCI: Ignoring BAR0-3 of IDE controller 00:0f.1
(XEN) PCI: Discovered primary peer bus 01 [IRQ]
(XEN) PCI: Discovered primary peer bus 02 [IRQ]
(XEN) PCI: Discovered primary peer bus 03 [IRQ]
(XEN) PCI: Discovered primary peer bus 04 [IRQ]
(XEN) PCI: Using IRQ router ServerWorks [1166/0201] at 00:0f.0
(XEN) PCI->APIC IRQ transform: (B2,I0,P0) -> 16
(XEN) PCI->APIC IRQ transform: (B2,I0,P1) -> 17
(XEN) PCI->APIC IRQ transform: (B4,I5,P0) -> 18
(XEN) PCI->APIC IRQ transform: (B4,I5,P1) -> 19
(XEN) mtrr: v2.0 (20020519)
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen-ELF header found: 
'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=2.0,VIRT_BASE=0xC0000000,LOADER=generic,PT_MODE_WRITABLE'
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Kernel image:  00c00000->010328cc
(XEN)  Initrd image:  01033000->01359e00
(XEN)  Dom0 alloc.:   01400000->09400000
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: c0100000->c0560ac4
(XEN)  Init. ramdisk: c0561000->c0887e00
(XEN)  Phys-Mach map: c0888000->c08a8000
(XEN)  Page tables:   c08a8000->c08ac000
(XEN)  Start info:    c08ac000->c08ad000
(XEN)  Boot stack:    c08ad000->c08ae000
(XEN)  TOTAL:         c0000000->c0c00000
(XEN)  ENTRY ADDRESS: c0100000
(XEN) Scrubbing DOM0 RAM: ..done.
(XEN) Initrd len 0x326e00, start at 0xc0561000
(XEN) Scrubbing Free RAM: ...........done.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to 
Xen).

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.