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

[Xen-devel] Xen 4.0.1 & kernel Oops: 0000 [#1] SMP

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Xen 4.0.1 & kernel Oops: 0000 [#1] SMP
From: "Olivier B." <xen.list@xxxxxxxxx>
Date: Sun, 11 Jul 2010 00:42:26 +0200
Delivery-date: Sat, 10 Jul 2010 15:43:23 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.10) Gecko/20100620 Icedove/3.0.5
Hi,

I'm using Xen 4 (version 4.0.1~rc3-1 from Debian sid), with a 2.6.32.16-*-gb97a312 pv-ops kernel (the stable-2.6.32 branch) ; on a Debian Squeeze amd64 system, with udev version 158.

When I try to create a DomU, with a bridge setup, I obtain that :

# time xm create /etc/xen/slhoka.cfg
Using config file "/etc/xen/slhoka.cfg".

Message from syslogd@keron at Jul 11 00:34:38 ...
 kernel:[10802.032082] Oops: 0000 [#1] SMP

Message from syslogd@keron at Jul 11 00:34:38 ...
 kernel:[10802.032442] last sysfs file: /sys/devices/vif-1-0/uevent

Message from syslogd@keron at Jul 11 00:34:38 ...
 kernel:[10802.039632] Stack:

Message from syslogd@keron at Jul 11 00:34:38 ...
 kernel:[10802.042070] Call Trace:

Message from syslogd@keron at Jul 11 00:34:38 ...
kernel:[10802.045916] Code: 81 31 c0 48 89 ef e8 50 93 f9 ff 85 c0 74 0f 4c 89 ef bd f4 ff ff ff e8 49 2d e8 ff eb 2c 4c 89 ef e8 3f 2d e8 ff 48 89 ef 31 c0 <49> 8b 94 24 10 01 00 00 48 c7 c6 6c 0b 55 81 bd f4 ff ff ff e8

Message from syslogd@keron at Jul 11 00:34:38 ...
 kernel:[10802.047918] CR2: 0000000000000110

Error: Device 2048 (vbd) could not be connected. Hotplug scripts not working.

real    1m41.546s
user    0m0.084s
sys    0m0.040s

The "hotplug" error is probably thrown because of my udev version (158), no ? But the kernel oops seem strange to me.
If that can help, it's a "recent" CPU :

processor    : 0
vendor_id    : GenuineIntel
cpu family    : 6
model        : 44
model name    : Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz
stepping    : 2
cpu MHz        : 2666.700
cache size    : 12288 KB
fpu        : yes
fpu_exception    : yes
cpuid level    : 11
wp        : yes
flags : fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good nonstop_tsc aperfmperf pni pclmulqdq est ssse3 cx16 sse4_1 sse4_2 popcnt aes hypervisor lahf_lm ida arat
bogomips    : 5333.40
clflush size    : 64
cache_alignment    : 64
address sizes    : 40 bits physical, 48 bits virtual
power management:


Thanks for any advice,
Olivier B.


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

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