Bug#428685: kernel bugs when running xen in HVM mode

2007-06-29 Thread Markus Hochholdinger 
Hi,

have you tried to set dom0 memory to a fixed value? Perhaps the explanation in 
this bug could help:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=414040

The message "Error: Device 5696 (vbd) could not be connected. Backend device 
not found." can occur if the device is (still) in use. I've found this 
sometimes if a domU was not normally shutdown.
Possible solutions:
+ kill processe(s) accessing this device
+ restart xend
+ if a block device has really a problem (io blocking) you have to reboot


-- 
greetings

eMHa


pgpq3u4MM0pCs.pgp
Description: PGP signature

Bug#428685: kernel bugs when running xen in HVM mode

2007-06-13 Thread Henning Sprang 

Package: xen

when trying to run xen in hvm mode, I experience quite un strange behaviour.

Basically, each start (of exactly the same config) results in a 
different error.


sometimes it "just works", sometimes, without any change in the system, 
just trying again, it's just a message:


"Error: Device 5696 (vbd) could not be connected. Backend device not found."

and now I just got:


Message from [EMAIL PROTECTED] at Wed Jun 13 14:27:24 2007 ...
filet kernel: [ cut here ]

Message from [EMAIL PROTECTED] at Wed Jun 13 14:27:24 2007 ...
filet kernel: kernel BUG at mm/memory.c:2245!

Message from [EMAIL PROTECTED] at Wed Jun 13 14:27:24 2007 ...
filet kernel: invalid opcode:  [#1]

Message from [EMAIL PROTECTED] at Wed Jun 13 14:27:24 2007 ...
filet kernel: SMP

Message from [EMAIL PROTECTED] at Wed Jun 13 14:27:24 2007 ...
filet kernel: CPU:0

Message from [EMAIL PROTECTED] at Wed Jun 13 14:27:24 2007 ...
filet kernel: EIP is at __handle_mm_fault+0x37d/0xb12

Message from [EMAIL PROTECTED] at Wed Jun 13 14:27:24 2007 ...
filet kernel: eax: c02dce14   ebx: 00030dc0   ecx: 0014   edx: df4f6b54

Message from [EMAIL PROTECTED] at Wed Jun 13 14:27:24 2007 ...
filet kernel: esi: df4f6b54   edi: f1377a54   ebp: a54f9000   esp: f080df1c

Message from [EMAIL PROTECTED] at Wed Jun 13 14:27:24 2007 ...
filet kernel: ds: 007b   es: 007b   ss: 0069

Message from [EMAIL PROTECTED] at Wed Jun 13 14:27:24 2007 ...
filet kernel: Process qemu-dm (pid: 526, ti=f080c000 task=d6b5c000 
task.ti=f080c000)


Message from [EMAIL PROTECTED] at Wed Jun 13 14:27:24 2007 ...
filet kernel: Stack:   df4f6b78 a54f9000 df4f6b54 
da57f200 03e4 f1377a54


Message from [EMAIL PROTECTED] at Wed Jun 13 14:27:24 2007 ...
filet kernel:f0dc03e4 c014948d df4f6b54 0800 8d790029 
a54f9000  08314680


Message from [EMAIL PROTECTED] at Wed Jun 13 14:27:24 2007 ...
filet kernel:c02dcda0 c3b04600 bf8a3ef8 00145003 0002 
df4f6b54 da57f234 0006


Message from [EMAIL PROTECTED] at Wed Jun 13 14:27:24 2007 ...
filet kernel: Call Trace:

Message from [EMAIL PROTECTED] at Wed Jun 13 14:27:24 2007 ...
filet kernel: Code: 8b 44 24 20 89 38 b0 01 86 45 00 e9 81 07 00 00 89 
f0 e8 98 a9 ff ff eb ed 8b 54 24 10 c7 44 24 50 02 00 00 00 f6 42 15 04 
74 08 <0f> 0b c5 08 33 b7 29 c0 8b 74 24 10 8b 46 48 85 c0 75 12 c7 44


Message from [EMAIL PROTECTED] at Wed Jun 13 14:27:24 2007 ...
filet kernel: EIP: [] __handle_mm_fault+0x37d/0xb12 SS:ESP 
0069:f080df1c



are there any things one can do, to get the Xen hvm in Etch working 
smoothly, or is the hypervisor 3.0.3 too broken?


(I guess the latter, but if the developers know a workaround, I'd be 
happy to hear)


Let me know if any further information is needed...

Henning



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]