Hi All,
I am not sure about this, just wondering anyone has the similar
situation with me::
I was using scp command on a remote server, copying a 20G file into
Domain 0 server.
the speed displayed is around 8Mb/s
waiting...
waiting...
at 67%, it stopped, why? because Domain 0 reboot.....
I check the log, nothing useful. I guess it is because the network flowing,
because the domain 0 has been running for 3 weeks until today I do the
copying.
I attached some info, please give me some advice, thanks a lot!!
xin
[root@XenServer xen]# uname -a
Linux XenServer 2.6.18-1.2798.fc6xen #1 SMP Mon Oct 16 15:11:19 EDT 2006
i686 i686 i386 GNU/Linux
[root@XenServer xen]# xm info
host : XenServer
release : 2.6.18-1.2798.fc6xen
version : #1 SMP Mon Oct 16 15:11:19 EDT 2006
machine : i686
nr_cpus : 4
nr_nodes : 1
sockets_per_node : 1
cores_per_socket : 4
threads_per_core : 1
cpu_mhz : 1600
hw_caps :
bfebfbff:20100000:00000000:00000140:0004e33d:00000000:00000001
total_memory : 4094
free_memory : 0
xen_major : 3
xen_minor : 0
xen_extra : .3-rc3-1.2798.f
xen_caps : xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p
xen_pagesize : 4096
platform_params : virt_start=0xf5800000
xen_changeset : unavailable
cc_compiler : gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)
cc_compile_by : brewbuilder
cc_compile_domain : build.redhat.com
cc_compile_date : Mon Oct 16 14:34:31 EDT 2006
xend_config_format : 2
/var/log/xend.log
[2007-06-24 01:08:55 xend 3125] DEBUG (DevController:149) Waiting for 51712.
[2007-06-24 01:08:55 xend 3125] DEBUG (DevController:472)
hotplugStatusCallback
/local/domain/0/backend/tap/6/51712/hotplug-status.
[2007-06-24 01:08:55 xend 3125] DEBUG (DevController:486)
hotplugStatusCallback
1.
[2007-06-24 01:08:55 xend 3125] DEBUG (DevController:143) Waiting for
devices vt
pm.
[2007-06-24 01:08:55 xend 3125] INFO (XendDomain:370) Domain stimpy (6)
unpaused
.
*[2007-06-26 17:18:55 xend 3154] INFO (SrvDaemon:283) Xend Daemon
started -> here is the place reboot.*
[2007-06-26 17:18:55 xend 3154] INFO (SrvDaemon:287) Xend changeset:
unavailable
.
[2007-06-26 17:18:55 xend.XendDomainInfo 3154] DEBUG
(XendDomainInfo:212) XendDo
mainInfo.recreate({''paused'': 0, ''cpu_time'':
29578464995L, ''ssidref'': 0,
''handle''
: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0],
''shutdown_reason'':
0, ''dying
'': 0, ''dom'': 0, ''mem_kb'': 4012156,
''maxmem_kb'': -4, ''max_vcpu_id'': 3,
''crashed'':
0, ''running'': 1, ''shutdown'': 0,
''online_vcpus'': 4, ''blocked'': 0})
[2007-06-26 17:18:55 xend.XendDomainInfo 3154] INFO (XendDomainInfo:224)
Recreat
ing domain 0, UUID 00000000-0000-0000-0000-000000000000.
[2007-06-26 17:18:55 xend.XendDomainInfo 3154] WARNING
(XendDomainInfo:246) No v
m path in store for existing domain 0
[2007-06-26 17:18:55 xend.XendDomainInfo 3154] DEBUG
(XendDomainInfo:715) Storin
g VM details: {''shadow_memory'': ''0'',
''uuid'':
''00000000-0000-0000-0000-0000000000
00'', ''on_reboot'': ''restart'',
''on_poweroff'': ''destroy'',
''name'':
''Domain-0'', ''xend
/restart_count'': ''0'', ''vcpus'':
''4'', ''vcpu_avail'': ''15'',
''memory'':
''3919'', ''on_cr
ash'': ''restart'', ''maxmem'':
''3919''}
[2007-06-26 17:18:56 xend.XendDomainInfo 3154] DEBUG
(XendDomainInfo:750) Storin
g domain details: {''cpu/1/availability'':
''online'', ''cpu/3/availability'':
''online
'', ''name'': ''Domain-0'',
''console/limit'': ''1048576'',
''cpu/2/availability'':
''online
'', ''vm'':
''/vm/00000000-0000-0000-0000-000000000000'',
''domid'': ''0'',
''cpu/0/availa
bility'': ''online'', ''memory/target'':
''4013056''}
[2007-06-26 17:18:56 xend 3154] DEBUG (XendDomain:153) number of vcpus
to use is
0
[2007-06-26 17:18:56 xend 3154] INFO (SrvServer:116) unix
path=/var/lib/xend/xen
d-socket
/var/log/message:
Jun 26 17:14:58 XenServer kernel: peth1: received packet with own
address as so
urce address
Jun 26 17:15:57 XenServer last message repeated 2 times
Jun 26 17:15:57 XenServer kernel: peth0: received packet with own
address as so
urce address
Jun 26 17:16:01 XenServer kernel: peth1: received packet with own
address as so
urce address
Jun 26 17:17:00 XenServer kernel: peth1: received packet with own
address as so
urce address
*Jun 26 17:18:38 XenServer syslogd 1.4.1: restart. --> here is the place
reboot*
Jun 26 17:18:38 XenServer kernel: klogd 1.4.1, log source = /proc/kmsg
started.
Jun 26 17:18:38 XenServer kernel: Linux version 2.6.18-1.2798.fc6xen
(brewbuilde
r@hs20-bc2-4.build.redhat.com) (gcc version 4.1.1 20061011 (Red Hat
4.1.1-30)) #
1 SMP Mon Oct 16 15:11:19 EDT 2006
Jun 26 17:18:38 XenServer kernel: BIOS-provided physical RAM map:
Jun 26 17:18:38 XenServer kernel: Xen: 0000000000000000 -
00000000f575f000 (usa
ble)
Jun 26 17:18:38 XenServer kernel: 3199MB HIGHMEM available.
Jun 26 17:18:38 XenServer kernel: 727MB LOWMEM available.
Jun 26 17:18:38 XenServer kernel: NX (Execute Disable) protection: active
Jun 26 17:18:38 XenServer kernel: found SMP MP-table at 000f5f20
Jun 26 17:18:38 XenServer kernel: DMI present.
Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x00]
lapic_id[0x00] enab
led)
Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x01]
lapic_id[0x01] enab
led)
Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x02]
lapic_id[0x02] enab
led)
Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x03]
lapic_id[0x03] enab
led)
Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high
edge lint[
0x1])
Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high
edge lint[
0x1])
Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high
edge lint[
0x1])
Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high
edge lint[
0x1])
Jun 26 17:18:38 XenServer kernel: ACPI: IOAPIC (id[0x04]
address[0xfec00000] gsi
_base[0])
Jun 26 17:18:38 XenServer kernel: IOAPIC[0]: apic_id 4, version 32,
address 0xfe
c00000, GSI 0-23
Jun 26 17:18:38 XenServer kernel: ACPI: IOAPIC (id[0x05]
address[0xfec80000] gsi
_base[24])
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
attach the network details of domain 0:
[root@XenServer ~]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:30:48:32:4F:94
inet addr:192.168.200.120 Bcast:192.168.200.255
Mask:255.255.255.0
inet6 addr: fe80::230:48ff:fe32:4f94/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2286450 errors:0 dropped:0 overruns:0 frame:0
TX packets:1118771 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3457059468 (3.2 GiB) TX bytes:74013507 (70.5 MiB)
eth1 Link encap:Ethernet HWaddr 00:30:48:32:4F:95
inet addr:192.168.200.121 Bcast:192.168.200.255
Mask:255.255.255.0
inet6 addr: fe80::230:48ff:fe32:4f95/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4211 errors:0 dropped:0 overruns:0 frame:0
TX packets:39 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:410017 (400.4 KiB) TX bytes:8485 (8.2 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1008 (1008.0 b) TX bytes:1008 (1008.0 b)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:2282062 errors:0 dropped:0 overruns:0 frame:0
TX packets:1116125 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:3458070625 (3.2 GiB) TX bytes:78308773 (74.6 MiB)
Base address:0x2000 Memory:d8400000-d8420000
peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:7627 errors:0 dropped:0 overruns:0 frame:0
TX packets:4103 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:893944 (872.9 KiB) TX bytes:523855 (511.5 KiB)
Base address:0x2020 Memory:d8420000-d8440000
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:1118785 errors:0 dropped:0 overruns:0 frame:0
TX packets:2286472 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:74014879 (70.5 MiB) TX bytes:3457092776 (3.2 GiB)
vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:39 errors:0 dropped:0 overruns:0 frame:0
TX packets:4211 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8485 (8.2 KiB) TX bytes:410017 (400.4 KiB)
vif0.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif0.3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:4100 errors:0 dropped:0 overruns:0 frame:0
TX packets:5265 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:440557 (430.2 KiB) TX bytes:652881 (637.5 KiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:472 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:59881 (58.4 KiB) TX bytes:0 (0.0 b)
xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:1348 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:96255 (93.9 KiB) TX bytes:0 (0.0 b)
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
I tried the same thing again, using scp copying..... this time even worse, 16%... domain 0 reboots..... ok, I will try using ftp to copy the 20Gb file now... Xin Chen wrote:> Hi All, > > I am not sure about this, just wondering anyone has the similar > situation with me:: > > I was using scp command on a remote server, copying a 20G file into > Domain 0 server. > the speed displayed is around 8Mb/s > > waiting... > waiting... > > at 67%, it stopped, why? because Domain 0 reboot..... > > I check the log, nothing useful. I guess it is because the network > flowing, > because the domain 0 has been running for 3 weeks until today I do the > copying. > > I attached some info, please give me some advice, thanks a lot!! > > xin > > [root@XenServer xen]# uname -a > Linux XenServer 2.6.18-1.2798.fc6xen #1 SMP Mon Oct 16 15:11:19 EDT > 2006 i686 i686 i386 GNU/Linux > > [root@XenServer xen]# xm info > host : XenServer > release : 2.6.18-1.2798.fc6xen > version : #1 SMP Mon Oct 16 15:11:19 EDT 2006 > machine : i686 > nr_cpus : 4 > nr_nodes : 1 > sockets_per_node : 1 > cores_per_socket : 4 > threads_per_core : 1 > cpu_mhz : 1600 > hw_caps : > bfebfbff:20100000:00000000:00000140:0004e33d:00000000:00000001 > total_memory : 4094 > free_memory : 0 > xen_major : 3 > xen_minor : 0 > xen_extra : .3-rc3-1.2798.f > xen_caps : xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p > xen_pagesize : 4096 > platform_params : virt_start=0xf5800000 > xen_changeset : unavailable > cc_compiler : gcc version 4.1.1 20061011 (Red Hat 4.1.1-30) > cc_compile_by : brewbuilder > cc_compile_domain : build.redhat.com > cc_compile_date : Mon Oct 16 14:34:31 EDT 2006 > xend_config_format : 2 > > /var/log/xend.log > [2007-06-24 01:08:55 xend 3125] DEBUG (DevController:149) Waiting for > 51712. > [2007-06-24 01:08:55 xend 3125] DEBUG (DevController:472) > hotplugStatusCallback > /local/domain/0/backend/tap/6/51712/hotplug-status. > [2007-06-24 01:08:55 xend 3125] DEBUG (DevController:486) > hotplugStatusCallback > 1. > [2007-06-24 01:08:55 xend 3125] DEBUG (DevController:143) Waiting for > devices vt > pm. > [2007-06-24 01:08:55 xend 3125] INFO (XendDomain:370) Domain stimpy > (6) unpaused > . > *[2007-06-26 17:18:55 xend 3154] INFO (SrvDaemon:283) Xend Daemon > started -> here is the place reboot.* > [2007-06-26 17:18:55 xend 3154] INFO (SrvDaemon:287) Xend changeset: > unavailable > . > [2007-06-26 17:18:55 xend.XendDomainInfo 3154] DEBUG > (XendDomainInfo:212) XendDo > mainInfo.recreate({''paused'': 0, ''cpu_time'': 29578464995L, ''ssidref'': > 0, ''handle'' > : [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], ''shutdown_reason'': > 0, ''dying > '': 0, ''dom'': 0, ''mem_kb'': 4012156, ''maxmem_kb'': -4, ''max_vcpu_id'': 3, > ''crashed'': > 0, ''running'': 1, ''shutdown'': 0, ''online_vcpus'': 4, ''blocked'': 0}) > [2007-06-26 17:18:55 xend.XendDomainInfo 3154] INFO > (XendDomainInfo:224) Recreat > ing domain 0, UUID 00000000-0000-0000-0000-000000000000. > [2007-06-26 17:18:55 xend.XendDomainInfo 3154] WARNING > (XendDomainInfo:246) No v > m path in store for existing domain 0 > [2007-06-26 17:18:55 xend.XendDomainInfo 3154] DEBUG > (XendDomainInfo:715) Storin > g VM details: {''shadow_memory'': ''0'', ''uuid'': > ''00000000-0000-0000-0000-0000000000 > 00'', ''on_reboot'': ''restart'', ''on_poweroff'': ''destroy'', ''name'': > ''Domain-0'', ''xend > /restart_count'': ''0'', ''vcpus'': ''4'', ''vcpu_avail'': ''15'', ''memory'': > ''3919'', ''on_cr > ash'': ''restart'', ''maxmem'': ''3919''} > [2007-06-26 17:18:56 xend.XendDomainInfo 3154] DEBUG > (XendDomainInfo:750) Storin > g domain details: {''cpu/1/availability'': ''online'', > ''cpu/3/availability'': ''online > '', ''name'': ''Domain-0'', ''console/limit'': ''1048576'', > ''cpu/2/availability'': ''online > '', ''vm'': ''/vm/00000000-0000-0000-0000-000000000000'', ''domid'': ''0'', > ''cpu/0/availa > bility'': ''online'', ''memory/target'': ''4013056''} > [2007-06-26 17:18:56 xend 3154] DEBUG (XendDomain:153) number of vcpus > to use is > 0 > [2007-06-26 17:18:56 xend 3154] INFO (SrvServer:116) unix > path=/var/lib/xend/xen > d-socket > > > /var/log/message: > Jun 26 17:14:58 XenServer kernel: peth1: received packet with own > address as so > urce address > Jun 26 17:15:57 XenServer last message repeated 2 times > Jun 26 17:15:57 XenServer kernel: peth0: received packet with own > address as so > urce address > Jun 26 17:16:01 XenServer kernel: peth1: received packet with own > address as so > urce address > Jun 26 17:17:00 XenServer kernel: peth1: received packet with own > address as so > urce address > *Jun 26 17:18:38 XenServer syslogd 1.4.1: restart. --> here is the > place reboot* > Jun 26 17:18:38 XenServer kernel: klogd 1.4.1, log source = /proc/kmsg > started. > Jun 26 17:18:38 XenServer kernel: Linux version 2.6.18-1.2798.fc6xen > (brewbuilde > r@hs20-bc2-4.build.redhat.com) (gcc version 4.1.1 20061011 (Red Hat > 4.1.1-30)) # > 1 SMP Mon Oct 16 15:11:19 EDT 2006 > Jun 26 17:18:38 XenServer kernel: BIOS-provided physical RAM map: > Jun 26 17:18:38 XenServer kernel: Xen: 0000000000000000 - > 00000000f575f000 (usa > ble) > Jun 26 17:18:38 XenServer kernel: 3199MB HIGHMEM available. > Jun 26 17:18:38 XenServer kernel: 727MB LOWMEM available. > Jun 26 17:18:38 XenServer kernel: NX (Execute Disable) protection: active > Jun 26 17:18:38 XenServer kernel: found SMP MP-table at 000f5f20 > Jun 26 17:18:38 XenServer kernel: DMI present. > Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x00] > lapic_id[0x00] enab > led) > Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x01] > lapic_id[0x01] enab > led) > Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x02] > lapic_id[0x02] enab > led) > Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x03] > lapic_id[0x03] enab > led) > Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high > edge lint[ > 0x1]) > Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high > edge lint[ > 0x1]) > Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high > edge lint[ > 0x1]) > Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high > edge lint[ > 0x1]) > Jun 26 17:18:38 XenServer kernel: ACPI: IOAPIC (id[0x04] > address[0xfec00000] gsi > _base[0]) > Jun 26 17:18:38 XenServer kernel: IOAPIC[0]: apic_id 4, version 32, > address 0xfe > c00000, GSI 0-23 > Jun 26 17:18:38 XenServer kernel: ACPI: IOAPIC (id[0x05] > address[0xfec80000] gsi > _base[24]) > >------------------------------------------------------------------------ > >_______________________________________________ >Xen-users mailing list >Xen-users@lists.xensource.com >http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
well, ftp works , domain 0 didn''t reboot. ftp takes: in 1.9e+03 seconds (5.1e-07 Kbytes/s) <I don''t really know 1.9e_03 = how long, and 5.1e-07 Kb = how fast..> Xin Chen wrote:> I tried the same thing again, using scp copying..... > this time even worse, 16%... domain 0 reboots..... > > ok, I will try using ftp to copy the 20Gb file now... > > Xin Chen wrote: > >> Hi All, >> >> I am not sure about this, just wondering anyone has the similar >> situation with me:: >> >> I was using scp command on a remote server, copying a 20G file into >> Domain 0 server. >> the speed displayed is around 8Mb/s >> >> waiting... >> waiting... >> >> at 67%, it stopped, why? because Domain 0 reboot..... >> >> I check the log, nothing useful. I guess it is because the network >> flowing, >> because the domain 0 has been running for 3 weeks until today I do >> the copying. >> >> I attached some info, please give me some advice, thanks a lot!! >> >> xin >> >> [root@XenServer xen]# uname -a >> Linux XenServer 2.6.18-1.2798.fc6xen #1 SMP Mon Oct 16 15:11:19 EDT >> 2006 i686 i686 i386 GNU/Linux >> >> [root@XenServer xen]# xm info >> host : XenServer >> release : 2.6.18-1.2798.fc6xen >> version : #1 SMP Mon Oct 16 15:11:19 EDT 2006 >> machine : i686 >> nr_cpus : 4 >> nr_nodes : 1 >> sockets_per_node : 1 >> cores_per_socket : 4 >> threads_per_core : 1 >> cpu_mhz : 1600 >> hw_caps : >> bfebfbff:20100000:00000000:00000140:0004e33d:00000000:00000001 >> total_memory : 4094 >> free_memory : 0 >> xen_major : 3 >> xen_minor : 0 >> xen_extra : .3-rc3-1.2798.f >> xen_caps : xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p >> xen_pagesize : 4096 >> platform_params : virt_start=0xf5800000 >> xen_changeset : unavailable >> cc_compiler : gcc version 4.1.1 20061011 (Red Hat 4.1.1-30) >> cc_compile_by : brewbuilder >> cc_compile_domain : build.redhat.com >> cc_compile_date : Mon Oct 16 14:34:31 EDT 2006 >> xend_config_format : 2 >> >> /var/log/xend.log >> [2007-06-24 01:08:55 xend 3125] DEBUG (DevController:149) Waiting for >> 51712. >> [2007-06-24 01:08:55 xend 3125] DEBUG (DevController:472) >> hotplugStatusCallback >> /local/domain/0/backend/tap/6/51712/hotplug-status. >> [2007-06-24 01:08:55 xend 3125] DEBUG (DevController:486) >> hotplugStatusCallback >> 1. >> [2007-06-24 01:08:55 xend 3125] DEBUG (DevController:143) Waiting for >> devices vt >> pm. >> [2007-06-24 01:08:55 xend 3125] INFO (XendDomain:370) Domain stimpy >> (6) unpaused >> . >> *[2007-06-26 17:18:55 xend 3154] INFO (SrvDaemon:283) Xend Daemon >> started -> here is the place reboot.* >> [2007-06-26 17:18:55 xend 3154] INFO (SrvDaemon:287) Xend changeset: >> unavailable >> . >> [2007-06-26 17:18:55 xend.XendDomainInfo 3154] DEBUG >> (XendDomainInfo:212) XendDo >> mainInfo.recreate({''paused'': 0, ''cpu_time'': 29578464995L, ''ssidref'': >> 0, ''handle'' >> : [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], >> ''shutdown_reason'': 0, ''dying >> '': 0, ''dom'': 0, ''mem_kb'': 4012156, ''maxmem_kb'': -4, ''max_vcpu_id'': 3, >> ''crashed'': >> 0, ''running'': 1, ''shutdown'': 0, ''online_vcpus'': 4, ''blocked'': 0}) >> [2007-06-26 17:18:55 xend.XendDomainInfo 3154] INFO >> (XendDomainInfo:224) Recreat >> ing domain 0, UUID 00000000-0000-0000-0000-000000000000. >> [2007-06-26 17:18:55 xend.XendDomainInfo 3154] WARNING >> (XendDomainInfo:246) No v >> m path in store for existing domain 0 >> [2007-06-26 17:18:55 xend.XendDomainInfo 3154] DEBUG >> (XendDomainInfo:715) Storin >> g VM details: {''shadow_memory'': ''0'', ''uuid'': >> ''00000000-0000-0000-0000-0000000000 >> 00'', ''on_reboot'': ''restart'', ''on_poweroff'': ''destroy'', ''name'': >> ''Domain-0'', ''xend >> /restart_count'': ''0'', ''vcpus'': ''4'', ''vcpu_avail'': ''15'', ''memory'': >> ''3919'', ''on_cr >> ash'': ''restart'', ''maxmem'': ''3919''} >> [2007-06-26 17:18:56 xend.XendDomainInfo 3154] DEBUG >> (XendDomainInfo:750) Storin >> g domain details: {''cpu/1/availability'': ''online'', >> ''cpu/3/availability'': ''online >> '', ''name'': ''Domain-0'', ''console/limit'': ''1048576'', >> ''cpu/2/availability'': ''online >> '', ''vm'': ''/vm/00000000-0000-0000-0000-000000000000'', ''domid'': ''0'', >> ''cpu/0/availa >> bility'': ''online'', ''memory/target'': ''4013056''} >> [2007-06-26 17:18:56 xend 3154] DEBUG (XendDomain:153) number of >> vcpus to use is >> 0 >> [2007-06-26 17:18:56 xend 3154] INFO (SrvServer:116) unix >> path=/var/lib/xend/xen >> d-socket >> >> >> /var/log/message: >> Jun 26 17:14:58 XenServer kernel: peth1: received packet with own >> address as so >> urce address >> Jun 26 17:15:57 XenServer last message repeated 2 times >> Jun 26 17:15:57 XenServer kernel: peth0: received packet with own >> address as so >> urce address >> Jun 26 17:16:01 XenServer kernel: peth1: received packet with own >> address as so >> urce address >> Jun 26 17:17:00 XenServer kernel: peth1: received packet with own >> address as so >> urce address >> *Jun 26 17:18:38 XenServer syslogd 1.4.1: restart. --> here is the >> place reboot* >> Jun 26 17:18:38 XenServer kernel: klogd 1.4.1, log source = >> /proc/kmsg started. >> Jun 26 17:18:38 XenServer kernel: Linux version 2.6.18-1.2798.fc6xen >> (brewbuilde >> r@hs20-bc2-4.build.redhat.com) (gcc version 4.1.1 20061011 (Red Hat >> 4.1.1-30)) # >> 1 SMP Mon Oct 16 15:11:19 EDT 2006 >> Jun 26 17:18:38 XenServer kernel: BIOS-provided physical RAM map: >> Jun 26 17:18:38 XenServer kernel: Xen: 0000000000000000 - >> 00000000f575f000 (usa >> ble) >> Jun 26 17:18:38 XenServer kernel: 3199MB HIGHMEM available. >> Jun 26 17:18:38 XenServer kernel: 727MB LOWMEM available. >> Jun 26 17:18:38 XenServer kernel: NX (Execute Disable) protection: >> active >> Jun 26 17:18:38 XenServer kernel: found SMP MP-table at 000f5f20 >> Jun 26 17:18:38 XenServer kernel: DMI present. >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x00] >> lapic_id[0x00] enab >> led) >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x01] >> lapic_id[0x01] enab >> led) >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x02] >> lapic_id[0x02] enab >> led) >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x03] >> lapic_id[0x03] enab >> led) >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high >> edge lint[ >> 0x1]) >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high >> edge lint[ >> 0x1]) >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high >> edge lint[ >> 0x1]) >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high >> edge lint[ >> 0x1]) >> Jun 26 17:18:38 XenServer kernel: ACPI: IOAPIC (id[0x04] >> address[0xfec00000] gsi >> _base[0]) >> Jun 26 17:18:38 XenServer kernel: IOAPIC[0]: apic_id 4, version 32, >> address 0xfe >> c00000, GSI 0-23 >> Jun 26 17:18:38 XenServer kernel: ACPI: IOAPIC (id[0x05] >> address[0xfec80000] gsi >> _base[24]) >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, 2007-06-26 at 19:09 +1000, Xin Chen wrote:> well, ftp works , domain 0 didn''t reboot. > ftp takes: > in 1.9e+03 seconds (5.1e-07 Kbytes/s) > <I don''t really know 1.9e_03 = how long, and 5.1e-07 Kb = how fast..>I completely lost dom-0 seeing similar things, however guests that didn''t get I/O at all were still sputtering to a syslog server and my setup was different. It (dom-0) just went ''poof''. When I power cycled the server, most of dom-0''s root file system (ext3) was in an existentially challenged state of being, including logs. I don''t have logs, or anything else which is why I didn''t ship a bug report to xen-devel. Not quite the same experience, but I have been getting _weird_ results with 3.1 on AMD-V machines using 32P kernel and HV with all PV guests. Some frequent crashes with 64 bit HV and dom-0 also. I have yet to try mixing them. I''m not even sure how I could go about filing such a bug report. Hi, yes, Xen Devel? The Bermuda triangle moved into my desktop and disrupted your software, I just thought you ought to know ... Should such things be reported? I''m really not saying anything other than ''I think it might be broken, somehow." Best, --Tim> Xin Chen wrote: > > > I tried the same thing again, using scp copying..... > > this time even worse, 16%... domain 0 reboots..... > > > > ok, I will try using ftp to copy the 20Gb file now... > > > > Xin Chen wrote: > > > >> Hi All, > >> > >> I am not sure about this, just wondering anyone has the similar > >> situation with me:: > >> > >> I was using scp command on a remote server, copying a 20G file into > >> Domain 0 server. > >> the speed displayed is around 8Mb/s > >> > >> waiting... > >> waiting... > >> > >> at 67%, it stopped, why? because Domain 0 reboot..... > >> > >> I check the log, nothing useful. I guess it is because the network > >> flowing, > >> because the domain 0 has been running for 3 weeks until today I do > >> the copying. > >> > >> I attached some info, please give me some advice, thanks a lot!! > >> > >> xin > >> > >> [root@XenServer xen]# uname -a > >> Linux XenServer 2.6.18-1.2798.fc6xen #1 SMP Mon Oct 16 15:11:19 EDT > >> 2006 i686 i686 i386 GNU/Linux > >> > >> [root@XenServer xen]# xm info > >> host : XenServer > >> release : 2.6.18-1.2798.fc6xen > >> version : #1 SMP Mon Oct 16 15:11:19 EDT 2006 > >> machine : i686 > >> nr_cpus : 4 > >> nr_nodes : 1 > >> sockets_per_node : 1 > >> cores_per_socket : 4 > >> threads_per_core : 1 > >> cpu_mhz : 1600 > >> hw_caps : > >> bfebfbff:20100000:00000000:00000140:0004e33d:00000000:00000001 > >> total_memory : 4094 > >> free_memory : 0 > >> xen_major : 3 > >> xen_minor : 0 > >> xen_extra : .3-rc3-1.2798.f > >> xen_caps : xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p > >> xen_pagesize : 4096 > >> platform_params : virt_start=0xf5800000 > >> xen_changeset : unavailable > >> cc_compiler : gcc version 4.1.1 20061011 (Red Hat 4.1.1-30) > >> cc_compile_by : brewbuilder > >> cc_compile_domain : build.redhat.com > >> cc_compile_date : Mon Oct 16 14:34:31 EDT 2006 > >> xend_config_format : 2 > >> > >> /var/log/xend.log > >> [2007-06-24 01:08:55 xend 3125] DEBUG (DevController:149) Waiting for > >> 51712. > >> [2007-06-24 01:08:55 xend 3125] DEBUG (DevController:472) > >> hotplugStatusCallback > >> /local/domain/0/backend/tap/6/51712/hotplug-status. > >> [2007-06-24 01:08:55 xend 3125] DEBUG (DevController:486) > >> hotplugStatusCallback > >> 1. > >> [2007-06-24 01:08:55 xend 3125] DEBUG (DevController:143) Waiting for > >> devices vt > >> pm. > >> [2007-06-24 01:08:55 xend 3125] INFO (XendDomain:370) Domain stimpy > >> (6) unpaused > >> . > >> *[2007-06-26 17:18:55 xend 3154] INFO (SrvDaemon:283) Xend Daemon > >> started -> here is the place reboot.* > >> [2007-06-26 17:18:55 xend 3154] INFO (SrvDaemon:287) Xend changeset: > >> unavailable > >> . > >> [2007-06-26 17:18:55 xend.XendDomainInfo 3154] DEBUG > >> (XendDomainInfo:212) XendDo > >> mainInfo.recreate({''paused'': 0, ''cpu_time'': 29578464995L, ''ssidref'': > >> 0, ''handle'' > >> : [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], > >> ''shutdown_reason'': 0, ''dying > >> '': 0, ''dom'': 0, ''mem_kb'': 4012156, ''maxmem_kb'': -4, ''max_vcpu_id'': 3, > >> ''crashed'': > >> 0, ''running'': 1, ''shutdown'': 0, ''online_vcpus'': 4, ''blocked'': 0}) > >> [2007-06-26 17:18:55 xend.XendDomainInfo 3154] INFO > >> (XendDomainInfo:224) Recreat > >> ing domain 0, UUID 00000000-0000-0000-0000-000000000000. > >> [2007-06-26 17:18:55 xend.XendDomainInfo 3154] WARNING > >> (XendDomainInfo:246) No v > >> m path in store for existing domain 0 > >> [2007-06-26 17:18:55 xend.XendDomainInfo 3154] DEBUG > >> (XendDomainInfo:715) Storin > >> g VM details: {''shadow_memory'': ''0'', ''uuid'': > >> ''00000000-0000-0000-0000-0000000000 > >> 00'', ''on_reboot'': ''restart'', ''on_poweroff'': ''destroy'', ''name'': > >> ''Domain-0'', ''xend > >> /restart_count'': ''0'', ''vcpus'': ''4'', ''vcpu_avail'': ''15'', ''memory'': > >> ''3919'', ''on_cr > >> ash'': ''restart'', ''maxmem'': ''3919''} > >> [2007-06-26 17:18:56 xend.XendDomainInfo 3154] DEBUG > >> (XendDomainInfo:750) Storin > >> g domain details: {''cpu/1/availability'': ''online'', > >> ''cpu/3/availability'': ''online > >> '', ''name'': ''Domain-0'', ''console/limit'': ''1048576'', > >> ''cpu/2/availability'': ''online > >> '', ''vm'': ''/vm/00000000-0000-0000-0000-000000000000'', ''domid'': ''0'', > >> ''cpu/0/availa > >> bility'': ''online'', ''memory/target'': ''4013056''} > >> [2007-06-26 17:18:56 xend 3154] DEBUG (XendDomain:153) number of > >> vcpus to use is > >> 0 > >> [2007-06-26 17:18:56 xend 3154] INFO (SrvServer:116) unix > >> path=/var/lib/xend/xen > >> d-socket > >> > >> > >> /var/log/message: > >> Jun 26 17:14:58 XenServer kernel: peth1: received packet with own > >> address as so > >> urce address > >> Jun 26 17:15:57 XenServer last message repeated 2 times > >> Jun 26 17:15:57 XenServer kernel: peth0: received packet with own > >> address as so > >> urce address > >> Jun 26 17:16:01 XenServer kernel: peth1: received packet with own > >> address as so > >> urce address > >> Jun 26 17:17:00 XenServer kernel: peth1: received packet with own > >> address as so > >> urce address > >> *Jun 26 17:18:38 XenServer syslogd 1.4.1: restart. --> here is the > >> place reboot* > >> Jun 26 17:18:38 XenServer kernel: klogd 1.4.1, log source = > >> /proc/kmsg started. > >> Jun 26 17:18:38 XenServer kernel: Linux version 2.6.18-1.2798.fc6xen > >> (brewbuilde > >> r@hs20-bc2-4.build.redhat.com) (gcc version 4.1.1 20061011 (Red Hat > >> 4.1.1-30)) # > >> 1 SMP Mon Oct 16 15:11:19 EDT 2006 > >> Jun 26 17:18:38 XenServer kernel: BIOS-provided physical RAM map: > >> Jun 26 17:18:38 XenServer kernel: Xen: 0000000000000000 - > >> 00000000f575f000 (usa > >> ble) > >> Jun 26 17:18:38 XenServer kernel: 3199MB HIGHMEM available. > >> Jun 26 17:18:38 XenServer kernel: 727MB LOWMEM available. > >> Jun 26 17:18:38 XenServer kernel: NX (Execute Disable) protection: > >> active > >> Jun 26 17:18:38 XenServer kernel: found SMP MP-table at 000f5f20 > >> Jun 26 17:18:38 XenServer kernel: DMI present. > >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x00] > >> lapic_id[0x00] enab > >> led) > >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x01] > >> lapic_id[0x01] enab > >> led) > >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x02] > >> lapic_id[0x02] enab > >> led) > >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x03] > >> lapic_id[0x03] enab > >> led) > >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high > >> edge lint[ > >> 0x1]) > >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high > >> edge lint[ > >> 0x1]) > >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high > >> edge lint[ > >> 0x1]) > >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high > >> edge lint[ > >> 0x1]) > >> Jun 26 17:18:38 XenServer kernel: ACPI: IOAPIC (id[0x04] > >> address[0xfec00000] gsi > >> _base[0]) > >> Jun 26 17:18:38 XenServer kernel: IOAPIC[0]: apic_id 4, version 32, > >> address 0xfe > >> c00000, GSI 0-23 > >> Jun 26 17:18:38 XenServer kernel: ACPI: IOAPIC (id[0x05] > >> address[0xfec80000] gsi > >> _base[24]) > >> > >> ------------------------------------------------------------------------ > >> > >> _______________________________________________ > >> Xen-users mailing list > >> Xen-users@lists.xensource.com > >> http://lists.xensource.com/xen-users > >> > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Petersson, Mats
2007-Jun-26 09:38 UTC
RE: [Xen-users] Domain 0 reboot when network flow is heavy
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Tim Post > Sent: 26 June 2007 10:20 > To: Xin Chen > Cc: xen-users > Subject: Re: [Xen-users] Domain 0 reboot when network flow is heavy > > On Tue, 2007-06-26 at 19:09 +1000, Xin Chen wrote: > > > > well, ftp works , domain 0 didn''t reboot. > > ftp takes: > > in 1.9e+03 seconds (5.1e-07 Kbytes/s) > > <I don''t really know 1.9e_03 = how long, and 5.1e-07 Kb = > how fast..> > > I completely lost dom-0 seeing similar things, however guests that > didn''t get I/O at all were still sputtering to a syslog server and my > setup was different. It (dom-0) just went ''poof''. > > When I power cycled the server, most of dom-0''s root file > system (ext3) > was in an existentially challenged state of being, including logs. > > I don''t have logs, or anything else which is why I didn''t ship a bug > report to xen-devel. > > Not quite the same experience, but I have been getting _weird_ results > with 3.1 on AMD-V machines using 32P kernel and HV with all PV guests. > Some frequent crashes with 64 bit HV and dom-0 also. I have yet to try > mixing them. > > I''m not even sure how I could go about filing such a bug report. Hi, > yes, Xen Devel? The Bermuda triangle moved into my desktop > and disrupted > your software, I just thought you ought to know ... > > Should such things be reported? I''m really not saying anything other > than ''I think it might be broken, somehow."Yes, I think this type of bug should be reported, for two reasons: 1. If there''s some statistics of how often and when this happens, there''s a better chance of someone looking at it because it''s "important". 2. If there''s some pattern (e.g. certain network cards, certain variants of the kernel or some such) that can help the debug process, that will become more noticable when there''s multiple reporters of the problem. The fact that it''s "difficult to debug/describe" shouldn''t really prevent a bug-report. -- Mats> > Best, > --Tim > > > Xin Chen wrote: > > > > > I tried the same thing again, using scp copying..... > > > this time even worse, 16%... domain 0 reboots..... > > > > > > ok, I will try using ftp to copy the 20Gb file now... > > > > > > Xin Chen wrote: > > > > > >> Hi All, > > >> > > >> I am not sure about this, just wondering anyone has the similar > > >> situation with me:: > > >> > > >> I was using scp command on a remote server, copying a > 20G file into > > >> Domain 0 server. > > >> the speed displayed is around 8Mb/s > > >> > > >> waiting... > > >> waiting... > > >> > > >> at 67%, it stopped, why? because Domain 0 reboot..... > > >> > > >> I check the log, nothing useful. I guess it is because > the network > > >> flowing, > > >> because the domain 0 has been running for 3 weeks until > today I do > > >> the copying. > > >> > > >> I attached some info, please give me some advice, thanks a lot!! > > >> > > >> xin > > >> > > >> [root@XenServer xen]# uname -a > > >> Linux XenServer 2.6.18-1.2798.fc6xen #1 SMP Mon Oct 16 > 15:11:19 EDT > > >> 2006 i686 i686 i386 GNU/Linux > > >> > > >> [root@XenServer xen]# xm info > > >> host : XenServer > > >> release : 2.6.18-1.2798.fc6xen > > >> version : #1 SMP Mon Oct 16 15:11:19 EDT 2006 > > >> machine : i686 > > >> nr_cpus : 4 > > >> nr_nodes : 1 > > >> sockets_per_node : 1 > > >> cores_per_socket : 4 > > >> threads_per_core : 1 > > >> cpu_mhz : 1600 > > >> hw_caps : > > >> bfebfbff:20100000:00000000:00000140:0004e33d:00000000:00000001 > > >> total_memory : 4094 > > >> free_memory : 0 > > >> xen_major : 3 > > >> xen_minor : 0 > > >> xen_extra : .3-rc3-1.2798.f > > >> xen_caps : xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p > > >> xen_pagesize : 4096 > > >> platform_params : virt_start=0xf5800000 > > >> xen_changeset : unavailable > > >> cc_compiler : gcc version 4.1.1 20061011 (Red > Hat 4.1.1-30) > > >> cc_compile_by : brewbuilder > > >> cc_compile_domain : build.redhat.com > > >> cc_compile_date : Mon Oct 16 14:34:31 EDT 2006 > > >> xend_config_format : 2 > > >> > > >> /var/log/xend.log > > >> [2007-06-24 01:08:55 xend 3125] DEBUG > (DevController:149) Waiting for > > >> 51712. > > >> [2007-06-24 01:08:55 xend 3125] DEBUG (DevController:472) > > >> hotplugStatusCallback > > >> /local/domain/0/backend/tap/6/51712/hotplug-status. > > >> [2007-06-24 01:08:55 xend 3125] DEBUG (DevController:486) > > >> hotplugStatusCallback > > >> 1. > > >> [2007-06-24 01:08:55 xend 3125] DEBUG > (DevController:143) Waiting for > > >> devices vt > > >> pm. > > >> [2007-06-24 01:08:55 xend 3125] INFO (XendDomain:370) > Domain stimpy > > >> (6) unpaused > > >> . > > >> *[2007-06-26 17:18:55 xend 3154] INFO (SrvDaemon:283) > Xend Daemon > > >> started -> here is the place reboot.* > > >> [2007-06-26 17:18:55 xend 3154] INFO (SrvDaemon:287) > Xend changeset: > > >> unavailable > > >> . > > >> [2007-06-26 17:18:55 xend.XendDomainInfo 3154] DEBUG > > >> (XendDomainInfo:212) XendDo > > >> mainInfo.recreate({''paused'': 0, ''cpu_time'': > 29578464995L, ''ssidref'': > > >> 0, ''handle'' > > >> : [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], > > >> ''shutdown_reason'': 0, ''dying > > >> '': 0, ''dom'': 0, ''mem_kb'': 4012156, ''maxmem_kb'': -4, > ''max_vcpu_id'': 3, > > >> ''crashed'': > > >> 0, ''running'': 1, ''shutdown'': 0, ''online_vcpus'': 4, > ''blocked'': 0}) > > >> [2007-06-26 17:18:55 xend.XendDomainInfo 3154] INFO > > >> (XendDomainInfo:224) Recreat > > >> ing domain 0, UUID 00000000-0000-0000-0000-000000000000. > > >> [2007-06-26 17:18:55 xend.XendDomainInfo 3154] WARNING > > >> (XendDomainInfo:246) No v > > >> m path in store for existing domain 0 > > >> [2007-06-26 17:18:55 xend.XendDomainInfo 3154] DEBUG > > >> (XendDomainInfo:715) Storin > > >> g VM details: {''shadow_memory'': ''0'', ''uuid'': > > >> ''00000000-0000-0000-0000-0000000000 > > >> 00'', ''on_reboot'': ''restart'', ''on_poweroff'': ''destroy'', ''name'': > > >> ''Domain-0'', ''xend > > >> /restart_count'': ''0'', ''vcpus'': ''4'', ''vcpu_avail'': ''15'', > ''memory'': > > >> ''3919'', ''on_cr > > >> ash'': ''restart'', ''maxmem'': ''3919''} > > >> [2007-06-26 17:18:56 xend.XendDomainInfo 3154] DEBUG > > >> (XendDomainInfo:750) Storin > > >> g domain details: {''cpu/1/availability'': ''online'', > > >> ''cpu/3/availability'': ''online > > >> '', ''name'': ''Domain-0'', ''console/limit'': ''1048576'', > > >> ''cpu/2/availability'': ''online > > >> '', ''vm'': ''/vm/00000000-0000-0000-0000-000000000000'', > ''domid'': ''0'', > > >> ''cpu/0/availa > > >> bility'': ''online'', ''memory/target'': ''4013056''} > > >> [2007-06-26 17:18:56 xend 3154] DEBUG (XendDomain:153) number of > > >> vcpus to use is > > >> 0 > > >> [2007-06-26 17:18:56 xend 3154] INFO (SrvServer:116) unix > > >> path=/var/lib/xend/xen > > >> d-socket > > >> > > >> > > >> /var/log/message: > > >> Jun 26 17:14:58 XenServer kernel: peth1: received packet > with own > > >> address as so > > >> urce address > > >> Jun 26 17:15:57 XenServer last message repeated 2 times > > >> Jun 26 17:15:57 XenServer kernel: peth0: received packet > with own > > >> address as so > > >> urce address > > >> Jun 26 17:16:01 XenServer kernel: peth1: received packet > with own > > >> address as so > > >> urce address > > >> Jun 26 17:17:00 XenServer kernel: peth1: received packet > with own > > >> address as so > > >> urce address > > >> *Jun 26 17:18:38 XenServer syslogd 1.4.1: restart. --> > here is the > > >> place reboot* > > >> Jun 26 17:18:38 XenServer kernel: klogd 1.4.1, log source = > > >> /proc/kmsg started. > > >> Jun 26 17:18:38 XenServer kernel: Linux version > 2.6.18-1.2798.fc6xen > > >> (brewbuilde > > >> r@hs20-bc2-4.build.redhat.com) (gcc version 4.1.1 > 20061011 (Red Hat > > >> 4.1.1-30)) # > > >> 1 SMP Mon Oct 16 15:11:19 EDT 2006 > > >> Jun 26 17:18:38 XenServer kernel: BIOS-provided physical RAM map: > > >> Jun 26 17:18:38 XenServer kernel: Xen: 0000000000000000 - > > >> 00000000f575f000 (usa > > >> ble) > > >> Jun 26 17:18:38 XenServer kernel: 3199MB HIGHMEM available. > > >> Jun 26 17:18:38 XenServer kernel: 727MB LOWMEM available. > > >> Jun 26 17:18:38 XenServer kernel: NX (Execute Disable) > protection: > > >> active > > >> Jun 26 17:18:38 XenServer kernel: found SMP MP-table at 000f5f20 > > >> Jun 26 17:18:38 XenServer kernel: DMI present. > > >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x00] > > >> lapic_id[0x00] enab > > >> led) > > >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x01] > > >> lapic_id[0x01] enab > > >> led) > > >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x02] > > >> lapic_id[0x02] enab > > >> led) > > >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x03] > > >> lapic_id[0x03] enab > > >> led) > > >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI > (acpi_id[0x00] high > > >> edge lint[ > > >> 0x1]) > > >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI > (acpi_id[0x01] high > > >> edge lint[ > > >> 0x1]) > > >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI > (acpi_id[0x02] high > > >> edge lint[ > > >> 0x1]) > > >> Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI > (acpi_id[0x03] high > > >> edge lint[ > > >> 0x1]) > > >> Jun 26 17:18:38 XenServer kernel: ACPI: IOAPIC (id[0x04] > > >> address[0xfec00000] gsi > > >> _base[0]) > > >> Jun 26 17:18:38 XenServer kernel: IOAPIC[0]: apic_id 4, > version 32, > > >> address 0xfe > > >> c00000, GSI 0-23 > > >> Jun 26 17:18:38 XenServer kernel: ACPI: IOAPIC (id[0x05] > > >> address[0xfec80000] gsi > > >> _base[24]) > > >> > > >> > -------------------------------------------------------------- > ---------- > > >> > > >> _______________________________________________ > > >> Xen-users mailing list > > >> Xen-users@lists.xensource.com > > >> http://lists.xensource.com/xen-users > > >> > > > > > > > > > _______________________________________________ > > > Xen-users mailing list > > > Xen-users@lists.xensource.com > > > http://lists.xensource.com/xen-users > > > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Tom Mornini
2007-Jun-26 14:38 UTC
Re: [Xen-users] Domain 0 reboot when network flow is heavy
This sounds very similar to bugs we''ve seen with Xen version before 3.1 We believe the problem to be disk I/O related, but in our environment, disk I/O is also network I/O, so it''s hard to tell. We believe this problem to be corrected in 3.1, but we still haven''t done enough testing to satisfy ourselves entirely on this. See this previous thread: http://lists.xensource.com/archives/html/xen-users/2007-03/msg00073.html -- -- Tom Mornini, CTO -- Engine Yard, Ruby on Rails Hosting -- Support, Scalability, Reliability -- (866) 518-YARD (9273) On Jun 26, 2007, at 12:46 AM, Xin Chen wrote:> Hi All, > > I am not sure about this, just wondering anyone has the similar > situation with me:: > > I was using scp command on a remote server, copying a 20G file > into Domain 0 server. > the speed displayed is around 8Mb/s > > waiting... > waiting... > > at 67%, it stopped, why? because Domain 0 reboot..... > > I check the log, nothing useful. I guess it is because the network > flowing, > because the domain 0 has been running for 3 weeks until today I do > the copying. > > I attached some info, please give me some advice, thanks a lot!! > > xin > > [root@XenServer xen]# uname -a > Linux XenServer 2.6.18-1.2798.fc6xen #1 SMP Mon Oct 16 15:11:19 EDT > 2006 i686 i686 i386 GNU/Linux > > [root@XenServer xen]# xm info > host : XenServer > release : 2.6.18-1.2798.fc6xen > version : #1 SMP Mon Oct 16 15:11:19 EDT 2006 > machine : i686 > nr_cpus : 4 > nr_nodes : 1 > sockets_per_node : 1 > cores_per_socket : 4 > threads_per_core : 1 > cpu_mhz : 1600 > hw_caps : bfebfbff: > 20100000:00000000:00000140:0004e33d:00000000:00000001 > total_memory : 4094 > free_memory : 0 > xen_major : 3 > xen_minor : 0 > xen_extra : .3-rc3-1.2798.f > xen_caps : xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0- > x86_32p > xen_pagesize : 4096 > platform_params : virt_start=0xf5800000 > xen_changeset : unavailable > cc_compiler : gcc version 4.1.1 20061011 (Red Hat 4.1.1-30) > cc_compile_by : brewbuilder > cc_compile_domain : build.redhat.com > cc_compile_date : Mon Oct 16 14:34:31 EDT 2006 > xend_config_format : 2 > > /var/log/xend.log > [2007-06-24 01:08:55 xend 3125] DEBUG (DevController:149) Waiting > for 51712. > [2007-06-24 01:08:55 xend 3125] DEBUG (DevController:472) > hotplugStatusCallback > /local/domain/0/backend/tap/6/51712/hotplug-status. > [2007-06-24 01:08:55 xend 3125] DEBUG (DevController:486) > hotplugStatusCallback > 1. > [2007-06-24 01:08:55 xend 3125] DEBUG (DevController:143) Waiting > for devices vt > pm. > [2007-06-24 01:08:55 xend 3125] INFO (XendDomain:370) Domain stimpy > (6) unpaused > . > [2007-06-26 17:18:55 xend 3154] INFO (SrvDaemon:283) Xend Daemon > started -> here is the place reboot. > [2007-06-26 17:18:55 xend 3154] INFO (SrvDaemon:287) Xend > changeset: unavailable > . > [2007-06-26 17:18:55 xend.XendDomainInfo 3154] DEBUG > (XendDomainInfo:212) XendDo > mainInfo.recreate({''paused'': 0, ''cpu_time'': 29578464995L, > ''ssidref'': 0, ''handle'' > : [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], > ''shutdown_reason'': 0, ''dying > '': 0, ''dom'': 0, ''mem_kb'': 4012156, ''maxmem_kb'': -4, ''max_vcpu_id'': > 3, ''crashed'': > 0, ''running'': 1, ''shutdown'': 0, ''online_vcpus'': 4, ''blocked'': 0}) > [2007-06-26 17:18:55 xend.XendDomainInfo 3154] INFO (XendDomainInfo: > 224) Recreat > ing domain 0, UUID 00000000-0000-0000-0000-000000000000. > [2007-06-26 17:18:55 xend.XendDomainInfo 3154] WARNING > (XendDomainInfo:246) No v > m path in store for existing domain 0 > [2007-06-26 17:18:55 xend.XendDomainInfo 3154] DEBUG > (XendDomainInfo:715) Storin > g VM details: {''shadow_memory'': ''0'', ''uuid'': > ''00000000-0000-0000-0000-0000000000 > 00'', ''on_reboot'': ''restart'', ''on_poweroff'': ''destroy'', ''name'': > ''Domain-0'', ''xend > /restart_count'': ''0'', ''vcpus'': ''4'', ''vcpu_avail'': ''15'', ''memory'': > ''3919'', ''on_cr > ash'': ''restart'', ''maxmem'': ''3919''} > [2007-06-26 17:18:56 xend.XendDomainInfo 3154] DEBUG > (XendDomainInfo:750) Storin > g domain details: {''cpu/1/availability'': ''online'', ''cpu/3/ > availability'': ''online > '', ''name'': ''Domain-0'', ''console/limit'': ''1048576'', ''cpu/2/ > availability'': ''online > '', ''vm'': ''/vm/00000000-0000-0000-0000-000000000000'', ''domid'': ''0'', > ''cpu/0/availa > bility'': ''online'', ''memory/target'': ''4013056''} > [2007-06-26 17:18:56 xend 3154] DEBUG (XendDomain:153) number of > vcpus to use is > 0 > [2007-06-26 17:18:56 xend 3154] INFO (SrvServer:116) unix path=/var/ > lib/xend/xen > d-socket > > > /var/log/message: > Jun 26 17:14:58 XenServer kernel: peth1: received packet with own > address as so > urce address > Jun 26 17:15:57 XenServer last message repeated 2 times > Jun 26 17:15:57 XenServer kernel: peth0: received packet with own > address as so > urce address > Jun 26 17:16:01 XenServer kernel: peth1: received packet with own > address as so > urce address > Jun 26 17:17:00 XenServer kernel: peth1: received packet with own > address as so > urce address > Jun 26 17:18:38 XenServer syslogd 1.4.1: restart. --> here is the > place reboot > Jun 26 17:18:38 XenServer kernel: klogd 1.4.1, log source = /proc/ > kmsg started. > Jun 26 17:18:38 XenServer kernel: Linux version > 2.6.18-1.2798.fc6xen (brewbuilde > r@hs20-bc2-4.build.redhat.com) (gcc version 4.1.1 20061011 (Red Hat > 4.1.1-30)) # > 1 SMP Mon Oct 16 15:11:19 EDT 2006 > Jun 26 17:18:38 XenServer kernel: BIOS-provided physical RAM map: > Jun 26 17:18:38 XenServer kernel: Xen: 0000000000000000 - > 00000000f575f000 (usa > ble) > Jun 26 17:18:38 XenServer kernel: 3199MB HIGHMEM available. > Jun 26 17:18:38 XenServer kernel: 727MB LOWMEM available. > Jun 26 17:18:38 XenServer kernel: NX (Execute Disable) protection: > active > Jun 26 17:18:38 XenServer kernel: found SMP MP-table at 000f5f20 > Jun 26 17:18:38 XenServer kernel: DMI present. > Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x00] > lapic_id[0x00] enab > led) > Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x01] > lapic_id[0x01] enab > led) > Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x02] > lapic_id[0x02] enab > led) > Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x03] > lapic_id[0x03] enab > led) > Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x00] > high edge lint[ > 0x1]) > Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x01] > high edge lint[ > 0x1]) > Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x02] > high edge lint[ > 0x1]) > Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x03] > high edge lint[ > 0x1]) > Jun 26 17:18:38 XenServer kernel: ACPI: IOAPIC (id[0x04] address > [0xfec00000] gsi > _base[0]) > Jun 26 17:18:38 XenServer kernel: IOAPIC[0]: apic_id 4, version 32, > address 0xfe > c00000, GSI 0-23 > Jun 26 17:18:38 XenServer kernel: ACPI: IOAPIC (id[0x05] address > [0xfec80000] gsi > _base[24]) > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks Tom, I did these experiments on domain 0 today: First, I shutdown the guest systems running on domain 0, in case domain 0 reboots. 1, write a script: !#/bin/sh while [ 1 ] do /proc/slabinfo >> ./slabinfo.txt end then keep this script running around 20 mins, until slabinfo.txt about 4gb, domain 0 still running ok. 2, choose a 10gb file called temp, and do scp #scp temp localhost:/tmp/temp copying speed: 25mb/s, domain 0 still running ok. 3, again, like yesterday, scp a large file from remote server to domain 0. I did it twice, and domain 0 still running ok. I am not sure what it tells, I need to test again. Just may give a idea that it only happens when there is a guest running??? xin Tom Mornini wrote:> This sounds very similar to bugs we''ve seen with Xen version before 3.1 > > We believe the problem to be disk I/O related, but in our > environment, disk I/O is also network I/O, so it''s hard to tell. > > We believe this problem to be corrected in 3.1, but we still haven''t > done enough testing to satisfy ourselves entirely on this. > > See this previous thread: > > http://lists.xensource.com/archives/html/xen-users/2007-03/msg00073.html >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Tom Mornini
2007-Jun-28 00:05 UTC
Re: [Xen-users] Domain 0 reboot when network flow is heavy
Hello Xin. In our case, the disk I/O load was always in the DomU (via a passthrough block device from Dom0), and was always associated with high network traffic, as our SAN is ethernet attached (AoE, not iSCSI). We can crash the system through DomU disk I/O and associated network traffic alone. Accessing /proc/slabinfo greatly exacerbated the problem. P.S. You''re missing ''cat'' in the script your showed: !#/bin/sh while [ 1 ] do cat /proc/slabinfo >> ./slabinfo.txt end -- -- Tom Mornini, CTO -- Engine Yard, Ruby on Rails Hosting -- Support, Scalability, Reliability -- (866) 518-YARD (9273) On Jun 27, 2007, at 3:39 AM, Xin Chen wrote:> Thanks Tom, > > I did these experiments on domain 0 today: > First, I shutdown the guest systems running on domain 0, in case > domain 0 reboots. > > 1, write a script: > !#/bin/sh > while [ 1 ] do > /proc/slabinfo >> ./slabinfo.txt > end > > then keep this script running around 20 mins, until slabinfo.txt > about 4gb, domain 0 still running ok. > > 2, choose a 10gb file called temp, and do scp > #scp temp localhost:/tmp/temp > copying speed: 25mb/s, domain 0 still running ok. > > 3, again, like yesterday, scp a large file from remote server to > domain 0. I did it twice, and domain 0 still running ok. > > I am not sure what it tells, I need to test again. Just may give a > idea that it only happens when there is a guest running??? > > xin > > > > Tom Mornini wrote: > >> This sounds very similar to bugs we''ve seen with Xen version >> before 3.1 >> >> We believe the problem to be disk I/O related, but in our >> environment, disk I/O is also network I/O, so it''s hard to tell. >> >> We believe this problem to be corrected in 3.1, but we still >> haven''t done enough testing to satisfy ourselves entirely on this. >> >> See this previous thread: >> >> http://lists.xensource.com/archives/html/xen-users/2007-03/ >> msg00073.html >> >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Steven Dugway
2007-Aug-31 23:56 UTC
Re: [Xen-users] Domain 0 reboot when network flow is heavy
Tom Mornini wrote:> Hello Xin. > > In our case, the disk I/O load was always in the DomU (via a > passthrough block device from Dom0), and was always associated with > high network traffic, as our SAN is ethernet attached (AoE, not iSCSI). > > We can crash the system through DomU disk I/O and associated network > traffic alone. Accessing /proc/slabinfo greatly exacerbated the problem. > > P.S. You''re missing ''cat'' in the script your showed: > > !#/bin/sh > while [ 1 ] do > cat /proc/slabinfo >> ./slabinfo.txt > end >Hi, Did you find a solution? I have the same problem when transfering large files too, I am testing with selinux off and it seems so far not to crash. My dom0 and domU are all CentOs 5 which runs Xen 3.03 from the distro. Also, I use aoe and I changed the defaulf network interface used by the aoe instantiator from aoe-stat e9.0 10.737GB xenbr0,eth1,eth0 up to aoe-stat e9.0 10.737GB eth1 up So far it seems to have fixed the crashes. What have you done to fix the issue ? Regards, -- Virtual Space International Inc. Steven Dugway USA 206-734-HOST Canada 514-939-HOST (4678) ext 5 Skype:stevenvsi; savetimehosting.net 911hosting.net goodprivacy.net -------------------------------------------------------------- Internet Is Here To Stay, Make Sure Your Business Is! -------------------------------------------------------------- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users