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-users

[Xen-users] Problem booting 32bit DomU with Kernel 2.6.24 on Xen 3.2 64b

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Problem booting 32bit DomU with Kernel 2.6.24 on Xen 3.2 64bit Dom0
From: Tobias Weber <tobi-weber@xxxxxx>
Date: Fri, 29 Feb 2008 13:24:38 +0100
Delivery-date: Fri, 29 Feb 2008 04:25:30 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.7
Hello!

I'm trying to boot a 32bit DomU Kernel on Xen 3.2 with a 64bit Dom0.
The Kernel is booting, but I get an error with the virtual disks.
I have tried 2.6.24 and 2.6.25-rc3. Both the same problem.
PAE is enabled.

My Xen-Config:
kernel  = '/boot/xen/vmlinuz-2.6.24-1-xen-686'
ramdisk = '/boot/xen/initrd.img-2.6.24-1-xen-686'
memory  = '256'
extra="console=hvc0"
root    = '/dev/xvda1 ro'
name    = 'test'
dhcp = 'dhcp'
vif  = [ '' ]
on_poweroff = 'destroy'
on_reboot   = 'restart'
on_crash    = 'restart'

disk    = [
                'phy:data/test-disk,xvda1,w',
                'phy:data/test-swap,xvda2,w'
                ]

#disk    = [
#               'phy:data/test-disk,0x20201,w',
#               'phy:data/test-swap,0x20202,w'
#               ]


The Kernel-Messages:
SMP alternatives: switching to UP code
Freeing SMP alternatives: 11k freed
Brought up 1 CPUs
net_namespace: 64 bytes
Booting paravirtualized kernel on Xen
Hypervisor signature: xen-3.0-x86_32p
Grant table initialized
NET: Registered protocol family 16
Setting up standard PCI resources
NET: Registered protocol family 8
NET: Registered protocol family 20
NET: Registered protocol family 2
Time: xen clocksource has been installed.
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 6344k freed
audit: initializing netlink socket (disabled)
audit(1204287180.290:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
Initialising Xen virtual ethernet driver.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
cpuidle: using governor ladder
cpuidle: using governor menu
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
registered taskstats version 1
XENBUS: Device with no driver: device/console/0
Freeing unused kernel memory: 192k freed
Loading, please wait...
Begin: Loading essential drivers... ...
Done.
Begin: Running /scripts/init-premount ...
end_request: I/O error, dev xvda1, sector 20971392
Buffer I/O error on device xvda1, logical block 2621424
BUG: unable to handle kernel paging request at virtual address e8405cc4
printing eip: c021533c *pdpt = 00000000010d8027 *pde = 0000000000000000
Oops: 0000 [#1] SMP
Modules linked in:

Pid: 385, comm: vol_id Not tainted (2.6.24-1-xen-686 #1)
EIP: 0061:[<c021533c>] EFLAGS: 00010887 CPU: 0
EIP is at blkif_interrupt+0x5d/0x197
EAX: 19389c00 EBX: cf07c000 ECX: 00000200 EDX: 00000002
ESI: 00000000 EDI: cf0500ac EBP: ca020100 ESP: cf123ccc
 DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0069
Process vol_id (pid: 385, ti=cf122000 task=cf0872d0 task.ti=cf122000)
Stack: c0100007 00000000 00000200 00000001 00000002 00000200 00000000 00000001
       cf07f940 00000000 00000000 00000006 c0150c99 c0317e40 00000006 00000000
       c0317e70 c0152071 00000240 c0317e40 00000000 00000006 c010977d 00000000
Call Trace:
 [<c0150c99>] handle_IRQ_event+0x23/0x51
 [<c0152071>] handle_level_irq+0x74/0xb7
 [<c010977d>] do_IRQ+0x55/0x70
 [<c01d0744>] elv_next_request+0x179/0x189
 [<c0103b6d>] xen_evtchn_do_upcall+0x6c/0xa2
 [<c0107b54>] xen_hypervisor_callback+0x3c/0x44
 [<c01034ea>] force_evtchn_callback+0xa/0xc
 [<c01d46ca>] generic_unplug_device+0x27/0x2b
 [<c01d2528>] blk_unplug+0x72/0x7a
 [<c0192a67>] block_read_full_page+0x2d6/0x2e7
 [<c01551ee>] sync_page+0x0/0x3b
 [<c018f8ff>] block_sync_page+0x31/0x32
 [<c0155221>] sync_page+0x33/0x3b
 [<c02880f9>] __wait_on_bit_lock+0x2a/0x52
 [<c01551e0>] __lock_page+0x58/0x5e
 [<c01341ba>] wake_bit_function+0x0/0x3c
 [<c01558fd>] do_generic_mapping_read+0x257/0x3b2
 [<c0154f9c>] file_read_actor+0x0/0xcc
 [<c0157131>] generic_file_aio_read+0x16b/0x1a6
 [<c0154f9c>] file_read_actor+0x0/0xcc
 [<c01749af>] do_sync_read+0xc7/0x10a
 [<c0134185>] autoremove_wake_function+0x0/0x35
 [<c01941d1>] block_llseek+0xad/0xb9
 [<c01748e8>] do_sync_read+0x0/0x10a
 [<c0175235>] vfs_read+0x9f/0x14b
 [<c017569e>] sys_read+0x41/0x67
 [<c0106ed6>] syscall_call+0x7/0xb
 =======================
Code: 8b 43 20 89 44 24 0c 89 44 24 1c e9 eb 00 00 00 8b 43 24 31 f6 48 23 44 
24 0c 6b c0 6c 8d 78 40 03 7b 28 8b 2f 69 c5 9c 00 00 00 <8b> 94 18 c4 00 00 
00 8d 44 18 58 89 44 24 18 89 54 24 08 eb 12
EIP: [<c021533c>] blkif_interrupt+0x5d/0x197 SS:ESP 0069:cf123ccc
Kernel panic - not syncing: Fatal exception in interrupt


Sometimes the I/O error is on xvda1, and sometimes on xvda2.


Thanks
Tobi

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

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