Re: [Xen-users] Upgrade 3.0.3 to 3.2.1

[Markus Hochholdinger <Markus@xxxxxxxxxxxxxxxxx>]

Hi,

Am Samstag, 9. August 2008 21:00 schrieb Markus Hochholdinger:
> i thought 32 bit PV domU is working on 64 bit hypervisor as seen on
> http://wiki.xensource.com/xenwiki/XenFaq#head-5f7176b3909cb0382cece43a6a8fc
>25a3a114e93
> Am Samstag, 9. August 2008 17:27 schrieb Markus Hochholdinger:
> [..]
> > configuration and old domU kernel. But it fails to access the disks and i
> > don't know what am i missing!? The disks are accessible from the new xen
> > host with e.g. blockdev --getsize64 /dev/xbd/test1.sda2
> But as i read the mail "[Xen-devel] [PATCH][XEN] PV blk backend: Make 32bit
> PV guests work on 64bit PV Dom0" (28.07.2008 13:46) i get the impression
> that no block device is working in this combination till this patch!?
> Can someone confirm this?

with linux-image-2.6.18-xen-3.1-2-amd64 
from "http://kernel-archive.buildserver.net/debian-kernel/waldi/xen-extra all 
main" my old domU kernel is booting correctly and can access the disks. But i 
get a wierd kernel message on my xen host:
BUG: warning at lib/kref.c:32/kref_get()

Call Trace:
 [<ffffffff80237b05>] kref_get+0x2e/0x33
 [<ffffffff80257e03>] kobject_get+0x12/0x17
 [<ffffffff80249492>] blk_get_queue+0x1f/0x25
 [<ffffffff80372bf8>] dispatch_rw_block_io+0x50d/0x5d2
 [<ffffffff80265efb>] __switch_to+0x338/0x434
 [<ffffffff8027e80e>] find_busiest_group+0x1d9/0x46d
 [<ffffffff8025faed>] thread_return+0x0/0x13e
 [<ffffffff8025faed>] thread_return+0x0/0x13e
 [<ffffffff8037303e>] blkif_schedule+0x381/0x473
 [<ffffffff8027de3c>] __wake_up_common+0x3e/0x68
 [<ffffffff80292a01>] keventd_create_kthread+0x0/0x61
 [<ffffffff80372cbd>] blkif_schedule+0x0/0x473
 [<ffffffff80292a01>] keventd_create_kthread+0x0/0x61
 [<ffffffff80233802>] kthread+0xd4/0x107
 [<ffffffff8025db40>] child_rip+0xa/0x12
 [<ffffffff80292a01>] keventd_create_kthread+0x0/0x61
 [<ffffffff8023372e>] kthread+0x0/0x107
 [<ffffffff8025db36>] child_rip+0x0/0x12

BUG: warning at lib/kref.c:32/kref_get()

Call Trace:
 [<ffffffff80237b05>] kref_get+0x2e/0x33
 [<ffffffff80257e03>] kobject_get+0x12/0x17
 [<ffffffff80249492>] blk_get_queue+0x1f/0x25
 [<ffffffff80372bf8>] dispatch_rw_block_io+0x50d/0x5d2
 [<ffffffff80265efb>] __switch_to+0x338/0x434
 [<ffffffff8027e80e>] find_busiest_group+0x1d9/0x46d
 [<ffffffff8025faed>] thread_return+0x0/0x13e
 [<ffffffff8025faed>] thread_return+0x0/0x13e
 [<ffffffff8037303e>] blkif_schedule+0x381/0x473
 [<ffffffff8027de3c>] __wake_up_common+0x3e/0x68
 [<ffffffff80292a01>] keventd_create_kthread+0x0/0x61
 [<ffffffff80372cbd>] blkif_schedule+0x0/0x473
 [<ffffffff80292a01>] keventd_create_kthread+0x0/0x61
 [<ffffffff80233802>] kthread+0xd4/0x107
 [<ffffffff8025db40>] child_rip+0xa/0x12
 [<ffffffff80292a01>] keventd_create_kthread+0x0/0x61
 [<ffffffff8023372e>] kthread+0x0/0x107
 [<ffffffff8025db36>] child_rip+0x0/0x12

So it seems i only need a newer dom0 kernel. I will now build my own kernel 
based on http://bits.xensource.com/oss-xen/release/3.2.1/xen-3.2.1.tar.gz ...


-- 
greetings

eMHa

Attachment: pgpUArOXKpaMJ.pgp
Description: PGP signature

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