Maurice Meeden
2005-Mar-17 12:36 UTC
[Xen-devel] problems with console in domU if physdev access enabled
Hi,
I am trying to build a working domU kernel with CONFIG_XEN_PHYSDEV_ACCESS=y. But
if this enabled, domU fails to boot with different errors about the console.
With kernel 2.6.10 and xen 2.0.5 this error occurs if I try to start the Domain:
..
WARNING: Failed to register Xen virtual console driver as
''tty1''
..
Warning: unable to open an initial console.
Unable to handle kernel NULL pointer dereference at virtual address 00000000
printing eip:
c0264852
*pde = ma 00000000 pa 55555000
[<c0264a41>] vc_allocate+0xa1/0x1b0
[<c0268028>] con_open+0x48/0xc0
[<c02578dd>] tty_open+0x24d/0x2d0
[<c0257690>] tty_open+0x0/0x2d0
[<c015e8da>] chrdev_open+0xea/0x1d0
[<c01547ba>] dentry_open+0x15a/0x240
[<c0154658>] filp_open+0x68/0x70
[<c01548d9>] get_unused_fd+0x39/0xe0
[<c0154a49>] sys_open+0x49/0x90
[<c0109648>] syscall_call+0x7/0xb
Oops: 0000 [#1]
PREEMPT
Modules linked in:
CPU: 0
EIP: 0061:[<c0264852>] Not tainted VLI
EFLAGS: 00010246 (2.6.10-xenU)
EIP is at visual_init+0x72/0x1c0
eax: 00000000 ebx: c00c4e00 ecx: 00000000 edx: c00c4e00
esi: 00000000 edi: 00000001 ebp: 00000000 esp: c10a9e94
ds: 007b es: 007b ss: 0069
Process init (pid: 1, threadinfo=c10a8000 task=c00139e0)
Stack: 00000000 000000d0 c00c4e00 00000000 c0264a41 00000000 00000001 00000000
c009bc20 00000000 00000000 c115e000 00400000 c0268028 00000000 c03c6e00
c00ab880 00000001 c02578dd c115e000 c00ab880 c10a9ef0 00000102 c115e000
Call Trace:
[<c0264a41>] vc_allocate+0xa1/0x1b0
[<c0268028>] con_open+0x48/0xc0
[<c02578dd>] tty_open+0x24d/0x2d0
[<c0257690>] tty_open+0x0/0x2d0
[<c015e8da>] chrdev_open+0xea/0x1d0
[<c01547ba>] dentry_open+0x15a/0x240
[<c0154658>] filp_open+0x68/0x70
[<c01548d9>] get_unused_fd+0x39/0xe0
[<c0154a49>] sys_open+0x49/0x90
[<c0109648>] syscall_call+0x7/0xb
Code: 40 b8 39 c0 a1 2c b8 39 c0 89 42 28 8b 14 b5 80 c9 39 c0 85 d2 74 0a 8b 04
b5 40 b8 39 c0 89 50 28 8b 14 b5 40 b8 39 c0 8b 42 28 <8b> 18 85 db 74 35
89 1c
24 e8 90 bd ec ff 85 c0 0f 84 09 01 00
<0>Kernel panic - not syncing: Attempted to kill init!
<0>Rebooting in 1 seconds..
With 2.0-testing (snapshot from yesterday) there is no output if I try to start
the domain:
Using config file "tty.cfg".
Started domain ttylinux, console on port 9608
************ REMOTE CONSOLE: CTRL-] TO QUIT ********
Ive tried various kernel-configurations an also played with the xencons Options,
but in any cases the Domain does not booting. If I switch physdev access off,
the domain runs with the same kernelconfig without problems. I''m using
Gentoo
Linux stable with gcc-3.3.5, glibc 2.3.4.20040808-r1 without ntpl. Xen was build
from Source as it is described in the documentation.
Is here anybody who has xen running with physdev acces in one of the
domU''s? Or
is there anything what must make different when physdev-access is enabled?
Thanks in advance and please excuse my bad english ;-)
Maurice
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel
Ian Pratt
2005-Mar-19 09:28 UTC
RE: [Xen-devel] problems with console in domU if physdev access enabled
> I am trying to build a working domU kernel with > CONFIG_XEN_PHYSDEV_ACCESS=y. But > if this enabled, domU fails to boot with different errors > about the console. > With kernel 2.6.10 and xen 2.0.5 this error occurs if I try > to start the Domain: > .. > WARNING: Failed to register Xen virtual console driver as ''tty1'' > .. > Warning: unable to open an initial console. > Unable to handle kernel NULL pointer dereference at virtualIt sounds like you might be building in a serial UART (8250) into your domU kernel which is grabbing the tty. Ian ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Maurice Meeden
2005-Mar-19 13:11 UTC
[Xen-devel] Re: problems with console in domU if physdev access enabled
Ian Pratt <m+Ian.Pratt <at> cl.cam.ac.uk> writes:> > > I am trying to build a working domU kernel with > > CONFIG_XEN_PHYSDEV_ACCESS=y. But > > if this enabled, domU fails to boot with different errors > > about the console. > > With kernel 2.6.10 and xen 2.0.5 this error occurs if I try > > to start the Domain: > > .. > > WARNING: Failed to register Xen virtual console driver as ''tty1'' > > .. > > Warning: unable to open an initial console. > > Unable to handle kernel NULL pointer dereference at virtual > > It sounds like you might be building in a serial UART (8250) into your > domU kernel which is grabbing the tty.CONFIG_SERIAL_8250 was not set, I''ve also tried with set it to y, but it makes no difference. It would be very helpful if someone who use xen with physdev-access enabled could send me his/her kernel-config. Thanks Maurice ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Ian Pratt
2005-Mar-19 22:40 UTC
RE: [Xen-devel] Re: problems with console in domU if physdev access enabled
> > > I am trying to build a working domU kernel with > > > CONFIG_XEN_PHYSDEV_ACCESS=y. But > > > if this enabled, domU fails to boot with different errors > > > about the console. > > > With kernel 2.6.10 and xen 2.0.5 this error occurs if I try > > > to start the Domain: > > > .. > > > WARNING: Failed to register Xen virtual console driver as ''tty1'' > > > .. > > > Warning: unable to open an initial console. > > > Unable to handle kernel NULL pointer dereference at virtual > > > > It sounds like you might be building in a serial UART > (8250) into your > > domU kernel which is grabbing the tty. > > CONFIG_SERIAL_8250 was not set, I''ve also tried with set it > to y, but it makes > no difference. > > It would be very helpful if someone who use xen with > physdev-access enabled > could send me his/her kernel-config.If you post the full boot messages it will probably be possible to spot what you''re doing wrong. Ian ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Maurice
2005-Mar-20 21:06 UTC
RE: [Xen-devel] Re: problems with console in domU if physdev access enabled
> > > > I am trying to build a working domU kernel with > > > > CONFIG_XEN_PHYSDEV_ACCESS=y. But > > > > if this enabled, domU fails to boot with different errors > > > > about the console. > > > > With kernel 2.6.10 and xen 2.0.5 this error occurs if I try > > > > to start the Domain: > > > > .. > > > > WARNING: Failed to register Xen virtual console driver as ''tty1'' > > > > .. > > > > Warning: unable to open an initial console. > > > > Unable to handle kernel NULL pointer dereference at virtual > > > > > > It sounds like you might be building in a serial UART > > (8250) into your > > > domU kernel which is grabbing the tty. > > > > CONFIG_SERIAL_8250 was not set, I''ve also tried with set it > > to y, but it makes > > no difference. > > > > It would be very helpful if someone who use xen with > > physdev-access enabled > > could send me his/her kernel-config. > > If you post the full boot messages it will probably be possible to spot > what you''re doing wrong.No Problem: -------------------------------------------------------------------- Started domain ttylinux, console on port 9646 ************ REMOTE CONSOLE: CTRL-] TO QUIT ******** Linux version 2.6.10-moe-r6-gaga (root@server.moe.sb) (gcc-Version 3.3.5 (Gentoo Linux 3.3.5-r1, ssp-3.3.2-3, pie-8.7.7.1)) #26 Sat Mar 19 12:59:11 CET 2005 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000008000000 (usable) 128MB LOWMEM available. DMI not present. IRQ lockup detection disabled Built 1 zonelists Kernel command line: root=/dev/hda1 ro xencons=tty console=tty devfs=nomount Initializing CPU#0 PID hash table entries: 1024 (order: 10, 16384 bytes) Xen reported: 1002.303 MHz processor. Using tsc for high-res timesource Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 127104k/131072k available (1578k kernel code, 3796k reserved, 444k data, 120k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Mount-cache hash table entries: 512 (order: 0, 4096 bytes) CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 256K CPU: Intel Pentium III (Coppermine) stepping 0a Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking ''hlt'' instruction... disabled NET: Registered protocol family 16 xen_mem: Initialising balloon driver. Initializing Cryptographic API inotify device minor=63 i8042.c: Can''t read CTR while initializing i8042. Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize WARNING: Failed to register Xen virtual console driver as ''tty1'' Event-channel device installed. xen_blk: Initialising virtual block device driver elevator: using anticipatory as default io scheduler xen_net: Initialising virtual ethernet driver. mice: PS/2 mouse device common for all mice NET: Registered protocol family 2 IP: routing cache hash table of 1024 buckets, 8Kbytes TCP: Hash tables configured (established 8192 bind 16384) NET: Registered protocol family 1 NET: Registered protocol family 17 kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 120k freed Warning: unable to open an initial console. Unable to handle kernel NULL pointer dereference at virtual address 00000000 printing eip: c01f6262 *pde = ma 00000000 pa 55555000 [<c01f6451>] vc_allocate+0xa1/0x1b0 [<c01f9a38>] con_open+0x48/0xc0 [<c01e7e1d>] tty_open+0x24d/0x2d0 [<c01e7bd0>] tty_open+0x0/0x2d0 [<c015ecca>] chrdev_open+0xea/0x1d0 [<c01549ca>] dentry_open+0x15a/0x240 [<c0154868>] filp_open+0x68/0x70 [<c0115fa0>] default_wake_function+0x0/0x20 [<c0154ae9>] get_unused_fd+0x39/0xe0 [<c0154c54>] sys_open+0x44/0xd0 [<c0109758>] syscall_call+0x7/0xb Oops: 0000 [#1] PREEMPT Modules linked in: CPU: 0 EIP: 0061:[<c01f6262>] Not tainted VLI EFLAGS: 00010246 (2.6.10-moe-r6-gaga) EIP is at visual_init+0x72/0x1c0 eax: 00000000 ebx: c03ff800 ecx: 00000000 edx: c03ff800 esi: 00000000 edi: 00000001 ebp: 00000000 esp: c0361e90 ds: 007b es: 007b ss: 0069 Process init (pid: 1, threadinfo=c0360000 task=c00389e0) Stack: 00000000 000000d0 c03ff800 00000000 c01f6451 00000000 00000001 00000000 c03f3960 00000000 00000000 c1266000 00400000 c01f9a38 00000000 c005a000 c00886a0 00000001 c01e7e1d c1266000 c00886a0 c0361eec 00008800 c1266000 Call Trace: [<c01f6451>] vc_allocate+0xa1/0x1b0 [<c01f9a38>] con_open+0x48/0xc0 [<c01e7e1d>] tty_open+0x24d/0x2d0 [<c01e7bd0>] tty_open+0x0/0x2d0 [<c015ecca>] chrdev_open+0xea/0x1d0 [<c01549ca>] dentry_open+0x15a/0x240 [<c0154868>] filp_open+0x68/0x70 [<c0115fa0>] default_wake_function+0x0/0x20 [<c0154ae9>] get_unused_fd+0x39/0xe0 [<c0154c54>] sys_open+0x44/0xd0 [<c0109758>] syscall_call+0x7/0xb Code: 60 bb 32 c0 a1 4c bb 32 c0 89 42 28 8b 14 b5 a0 cc 32 c0 85 d2 74 0a 8b 04 b5 60 bb 32 c0 89 50 28 8b 14 b5 60 bb 32 c0 8b 42 28 <8b> 18 85 db 74 35 89 1c 24 e8 a0 a4 f3 ff 85 c0 0f 84 09 01 00 <0>Kernel panic - not syncing: Attempted to kill init! <0>Rebooting in 1 seconds.. -------------------------------------------------------------------- THX for help, Maurice ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Daniel Heemann
2005-Apr-09 18:15 UTC
[Xen-devel] Re: problems with console in domU if physdev access enabled
Maurice Meeden <tux <at> gmx.info> writes:> I am trying to build a working domU kernel with CONFIG_XEN_PHYSDEV_ACCESS=y.But> if this enabled, domU fails to boot with different errors about the console. > With kernel 2.6.10 and xen 2.0.5 this error occurs if I try to start theDomain:> .. > WARNING: Failed to register Xen virtual console driver as ''tty1'' > .. > Warning: unable to open an initial console. > Unable to handle kernel NULL pointer dereference at virtual address 00000000 > printing eip:...> With 2.0-testing (snapshot from yesterday) there is no output if I try tostart> the domain: > Using config file "tty.cfg". > Started domain ttylinux, console on port 9608 > ************ REMOTE CONSOLE: CTRL-] TO QUIT ******** >...> Is here anybody who has xen running with physdev acces in one of the domU''s?Or> is there anything what must make different when physdev-access is enabled?Is there any update on this problem? I can confirm both problems (stable and testing), also on a gentoo system. Running the dom0 kernel and a domU kernel w/o setting CONFIG_XEN_PHYSDEV=y seems to work fine. Regards Daniel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel