Re: [Xen-users] Fwd: xl can't create and boot vm when with on hard disk assignment

[Tuan Pengfei <pengfeituan@xxxxxxxxx>]

HI, I increased the loglevel as possible as i can, and found that

NET: Registered protocol family 17

initcall 0xffffffff818d52b7 returned 0 after 7 usecs

calling Â0xffffffff818d52f4 @ 1

initcall 0xffffffff818d52f4 returned 0 after 0 usecs

calling Â0xffffffff818d5300 @ 1

NET: Registered protocol family 15

initcall 0xffffffff818d5300 returned 0 after 5 usecs

calling Â0xffffffff818d547f @ 1

initcall 0xffffffff818d547f returned 0 after 13 usecs

calling Â0xffffffff818d5616 @ 1

Key type dns_resolver registered

initcall 0xffffffff818d5616 returned 0 after 10 usecs

calling Â0xffffffff818aa78b @ 1

initcall 0xffffffff818aa78b returned -5 after 0 usecs

initcall 0xffffffff818aa78b returned with error code -5Â

calling Â0xffffffff818aa87a @ 1

initcall 0xffffffff818aa87a returned 0 after 0 usecs

calling Â0xffffffff818ac3df @ 1

initcall 0xffffffff818ac3df returned 1 after 0 usecs

initcall 0xffffffff818ac3df returned with error code 1Â

calling Â0xffffffff818ae31a @ 1

initcall 0xffffffff818ae31a returned 0 after 0 usecs

calling Â0xffffffff818aedc0 @ 1

initcall 0xffffffff818aedc0 returned -1 after 0 usecs

initcall 0xffffffff818aedc0 returned with error code -1Â

calling Â0xffffffff818af800 @ 1

initcall 0xffffffff818af800 returned 0 after 0 usecs

calling Â0xffffffff818afdeb @ 1

printing PIC contents

... PIC ÂIMR: ffff

... PIC ÂIRR: ffff

... PIC ÂISR: ffff

... PIC ELCR: ffff

initcall 0xffffffff818afdeb returned 0 after 19 usecs

calling Â0xffffffff818b3024 @ 1

initcall 0xffffffff818b3024 returned 0 after 0 usecs

calling Â0xffffffff8103c28c @ 1

initcall 0xffffffff8103c28c returned 0 after 2 usecs

calling Â0xffffffff818b4faa @ 1

initcall 0xffffffff818b4faa returned 0 after 0 usecs

calling Â0xffffffff818b6608 @ 1

initcall 0xffffffff818b6608 returned 0 after 38 usecs

calling Â0xffffffff81065368 @ 1

initcall 0xffffffff81065368 returned -2 after 0 usecs

initcall 0xffffffff81065368 returned with error code -2Â

calling Â0xffffffff818b83a7 @ 1

registered taskstats version 1

initcall 0xffffffff818b83a7 returned 0 after 9 usecs

calling Â0xffffffff818bacf0 @ 1

initcall 0xffffffff818bacf0 returned 0 after 0 usecs

calling Â0xffffffff810c490a @ 1

initcall 0xffffffff810c490a returned 0 after 0 usecs

calling Â0xffffffff818bef7b @ 1

initcall 0xffffffff818bef7b returned 0 after 3 usecs

calling Â0xffffffff818bf39b @ 1

initcall 0xffffffff818bf39b returned 0 after 1 usecs

calling Â0xffffffff818bf6cc @ 1

initcall 0xffffffff818bf6cc returned 0 after 1 usecs

calling Â0xffffffff818c4eb5 @ 1

Setting capacity to 102400

xvda: detected capacity change from 0 to 52428800

initcall 0xffffffff818c4eb5 returned 0 after 95050 usecs

calling Â0xffffffff818c69a8 @ 1

initcall 0xffffffff818c69a8 returned 0 after 9 usecs

calling Â0xffffffff8125ee5f @ 1

initcall 0xffffffff8125ee5f returned 0 after 69 usecs

calling Â0xffffffff818cadcb @ 1

drivers/rtc/hctosys.c: unable to open rtc device (rtc0)

initcall 0xffffffff818cadcb returned -19 after 15 usecs

calling Â0xffffffff818cb8d0 @ 1

initcall 0xffffffff818cb8d0 returned 0 after 0 usecs

calling Â0xffffffff818ccd36 @ 1

initcall 0xffffffff818ccd36 returned 0 after 28 usecs

calling Â0xffffffff818d0f1e @ 1

initcall 0xffffffff818d0f1e returned 0 after 0 usecs

calling Â0xffffffff818d2e22 @ 1

initcall 0xffffffff818d2e22 returned 0 after 10 usecs

calling Â0xffffffff818d4256 @ 1

initcall 0xffffffff818d4256 returned 0 after 1 usecs

calling Â0xffffffff818d42ba @ 1

initcall 0xffffffff818d42ba returned 0 after 10 usecs

calling Â0xffffffff818d30e5 @ 1

initcall 0xffffffff818d30e5 returned 0 after 1 usecs

Freeing unused kernel memory: 632k freed

Write protecting the kernel read-only data: 8192k

Freeing unused kernel memory: 1784k freed

Freeing unused kernel memory: 872k freed

calling Â0xffffffffa0004000 @ 85

input: PC Speaker as /devices/platform/pcspkr/input/input0

initcall 0xffffffffa0004000 returned 0 after 99 usecs

calling Â0xffffffffa000b000 @ 94

microcode: CPU0 sig=0x10676, pf=0x1, revision=0x60c

Oops: 0000 [#1] SMPÂ

Modules linked in: microcode(+) pcspkr

CPU 0Â

Pid: 101, comm: modprobe Not tainted 3.8.13-tinycore64 #1 Â

RIP: e030:[<ffffffff81076085>] Â[<ffffffff81076085>] 0xffffffff81076085

RSP: e02b:ffff880002613e40 ÂEFLAGS: 00010297

RAX: ffff880006c00000 RBX: 0000000000000000 RCX: 000000010000060c

RDX: 0000000000000000 RSI: 0000000000000008 RDI: 0000000000000000

RBP: ffff88000242a940 R08: ffffffff81884b28 R09: 00000000fffffff7

R10: 0000000000000000 R11: 0000000000000246 R12: ffffffffa0009230

R13: ffffffffa0009230 R14: ffffffffa00093c8 R15: 00000000a0009238

FS: Â00007f447bf16700(0000) GS:ffff880006c00000(0000) knlGS:0000000000000000

CS: Âe033 DS: 0000 ES: 0000 CR0: 000000008005003b

CR2: ffff880106c00614 CR3: 0000000002529000 CR4: 0000000000000660

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000

DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400

Process modprobe (pid: 101, threadinfo ffff880002612000, task ffff880006299320)

Stack:

Âffffffffa0009238 ffff88000242a940 ffff880002613f58 ffffffff8107618f

Âffff880002613f58 0000000000000000 0000000000000400 ffff880002613f58

Âffff88000242a940 ffff88000618ca80 ffffffff810e0fa9 00007f447bf18000

Call Trace:

Â[<ffffffff8107618f>] ? 0xffffffff8107618f

Â[<ffffffff810e0fa9>] ? 0xffffffff810e0fa9

Â[<ffffffff811088b2>] ? 0xffffffff811088b2

Â[<ffffffff810c94cb>] ? 0xffffffff810c94cb

Â[<ffffffff810c9619>] ? 0xffffffff810c9619

Â[<ffffffff8143c4e9>] ? 0xffffffff8143c4e9

Code: ff c2 be 08 00 00 00 48 63 d2 e8 d7 1b 15 00 3b 05 49 fb 80 00 89 c2 7d 19 48 98 49 8b 8c 24 c8 01 00 00 48 8b 04 c5 50 48 88 81 <48> 03 5c 01 08 eb c7 83 ca ff 31 ed 48 8b 3d 58 e4 58 00 ff c2Â

RIP Â[<ffffffff81076085>] 0xffffffff81076085

ÂRSP <ffff880002613e40>

CR2: ffff880106c00614

---[ end trace e28fcc19c837c1a6 ]---

microcode: Microcode Update Driver: v2.00 <tigran@xxxxxxxxxxxxxxxxxxxx>, Peter Oruba

initcall 0xffffffffa000b000 returned 0 after 4932614 usecs

It shows that it is a problem of xen's built-in pcspkr driver. Am I right??

But I have no way to disable it for a test. My guest is pv guest, I can't blacklist the driver in my guest. And I don't find any way to disable it in domain0.

Anyone can help ?

Pengfei

On Mon, Apr 21, 2014 at 10:48 AM, Wei Liu <wei.liu2@xxxxxxxxxx> wrote:

On Mon, Apr 21, 2014 at 09:32:17AM -0400, Tuan Pengfei wrote:
> Hi, Liu!
> I found something error, when I got a successful boot, Âi see
>
> drivers/rtc/hctosys.c: unable to open rtc device (rtc0) Â Â Â Â Â //most
> time guest freezes here when unable to boot
> Freeing unused kernel memory: 672k freed
> Write protecting the kernel read-only data: 8192k
> Freeing unused kernel memory: 1612k freed
> Freeing unused kernel memory: 864k freed
> input: PC Speaker as /devices/platform/pcspkr/input/input0 //some time it
> also freezes here
>
> Does anyone know why?
>

Have you increased kernel log level?

The above log doesn't look very useful to me...

Wei.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users