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])
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)
Richard W.M. Jones
2007-Jun-27 03:54 UTC
Re: [Fedora-xen] Domain 0 reboot when network flow is heavy
Xin Chen wrote:> Hi All, > > I am not sure about this, just wondering anyone has the similar > situation with me::Is this similar? https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=190636 Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903
Xin Chen
2007-Jun-27 05:23 UTC
Re: [Fedora-xen] Domain 0 reboot when network flow is heavy
Thanks for quick response, Richard. Yes, it is similar but two differences: 1, instead of cpu lock, my domain 0 simply just reboot itself~~ 2, I can''t find any error message in the log, it is like a power off the machine. I thought it might be network I/O, but if using ftp, then there is no errors~, maybe a disk I/O, then I try cp a 10gb file to local drive on domain 0, it works as well. I would try to find usb in bios and turn it off later. Thanks! x Richard W.M. Jones wrote:> Xin Chen wrote: > >> Hi All, >> >> I am not sure about this, just wondering anyone has the similar >> situation with me:: > > > Is this similar? > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=190636 > > Rich. >
Richard W.M. Jones
2007-Jun-27 08:25 UTC
Re: [Fedora-xen] Domain 0 reboot when network flow is heavy
Xin Chen wrote:> Thanks for quick response, Richard. > > Yes, it is similar but two differences: > > 1, instead of cpu lock, my domain 0 simply just reboot itself~~The default configuration of Xen is that it will reboot if it detects that dom0 has crashed. To stop it doing this (so you can see any console messages), add noreboot to the Xen hypervisor command line. ie. in /boot/grub/menu.lst, locate the line which says: kernel /xen.gz-XXX.fc6 and add: kernel /xen.gz-XXX.fc6 noreboot> 2, I can''t find any error message in the log, it is like a power off the > machine. > > I thought it might be network I/O, but if using ftp, then there is no > errors~, maybe a disk I/O, then I try cp a 10gb file to local drive on > domain 0, it works as well.From the other reports, it does look like it has something to do with network I/O. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903