Mailinglist Archive: opensuse-bugs (2746 mails)

< Previous Next >
[Bug 826374] New: Xen domU chrashes with high network load
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 24 Jun 2013 10:33:37 +0000
  • Message-id: <>

Summary: Xen domU chrashes with high network load
Classification: openSUSE
Product: openSUSE 12.3
Version: Final
Platform: x86-64
OS/Version: openSUSE 12.3
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Kernel
AssignedTo: kernel-maintainers@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: g.w.kant@xxxxxxxxxx
QAContact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---

Created an attachment (id=545304)
--> (
Kernel oops captured in syslog of chrashed domU

User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:21.0)
Gecko/20100101 Firefox/21.0

I observed on two different machines domU chrashes under high network load.

With one dom0, running two domU's, logged in on domU_A, scp large_file domU_B:,
chrashes domU_B within little time.

Using 100 MbE connectivity from a remote host does not trigger this BUG in
reasonable time. However transferring data using 1 GbE connectivity from a
remote host does trigger this within say 30 seconds.

makes domU_B

Reproducible: Always

Steps to Reproduce:
1. Start domU;
2. scp large file to domU, e.g. from other domU on the same dom0 or from remote
host with at least 1 GbE connectivity
3. Wait until domU chrashes or hangs
Actual Results:
I have observed two error states:
1. The domU seems to be unresponsive;
2. The domU is rebooted (I have on_crash="restart" in config file)

In both cases on dom0 console a kernel OOPS similar to the attachment is
logged. The trace starts with lines similar to:

BUG: unable to handle kernel paging request at 000005a8000000bb
IP: [<ffffffff8028e6c6>] memcpy+0x6/0x110
Oops: 0002 [#1] SMP

Expected Results:
A stable system

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >