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

[Xen-devel] NetBSD qemu-dm problem

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] NetBSD qemu-dm problem
From: Adam Hamsik <haaaad@xxxxxxxxx>
Date: Mon, 8 Mar 2010 19:47:31 +0100
Cc: "Fourman Jr." <sfourman@xxxxxxxxx>, Ian.Jackson@xxxxxxxxxxxxx
Delivery-date: Mon, 08 Mar 2010 10:48:18 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:content-type :content-transfer-encoding:subject:date:message-id:cc:to :mime-version:x-mailer; bh=H9F7bl3oAUskdGp/NbKKJgAmGmJRX85YE5JTigep3ZY=; b=F/rL4V4VnAZVNn1nbWFiUNhDJoP3tF+6z5TZ1/n7LKCxhu/rAQGSz1RU5BFk2Z3y3l Arm+Z5684hV1CDgwbPOR/2Hf/OqBETWDTSUatb3UgiBBqPZp6QjRptNMcp6FQCqB8oVJ 3U14WbAGIL+YI6R/P/klRtzzwV2o9TxJlqb9k=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version:x-mailer; b=aaAOkRL4fmq0RHmQGAZCpGWK69CMNDUg75KjXnd8V2hbc2RYfDmzu1wGrweIKgRw7w FscdicLnLF0dTLxOXHkiG/sncwK0lw+QCrD+yAU89eSqeIyUvo0gPGOYfdM8rAjmPN72 Zz+/AiYLPNd+FVx83F2WO0lQqA+luIExCMtco=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi folks, 

As you probably know NetBSD can supports dom0, domU in i386, i386PAE, amd64 
modes. I have found one bug which I would like to fix in our implementation, 
but I need some guidance to be able to identify what's wrong.

If I create HVM domain with disk located on hw device or Logical Volume 

disk = [ 'file:/home/xenstuff/FreeBSD.img,ioemu:hda,w', 
         'phy:/dev/mapper/rvg00-testlv,ioemu:hdb,w'
        ]

disk hdb(size 20Gb) is detected as this (from xm dmesg)

(XEN) HVM27: ata0-0: PCHS=14563/16/63 translation=none LCHS=1024/16/63
(XEN) HVM27: ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (7168 MBytes)
(XEN) HVM27: ata0-1: PCHS=81/16/63 translation=none LCHS=81/16/63
(XEN) HVM27: ata0  slave: QEMU HARDDISK ATA-7 Hard-Disk (  40 MBytes)
(XEN) HVM27: 
(XEN) HVM27: Press F10 to select boot device.
(XEN) HVM27: Booting from Hard Disk...
(XEN) HVM27: int13_harddisk: function 08, unmapped device for ELDL=82
(XEN) HVM27: int13_harddisk: function 08, unmapped device for ELDL=83
(XEN) HVM27: int13_harddisk: function 08, unmapped device for ELDL=84
(XEN) HVM27: int13_harddisk: function 08, unmapped device for ELDL=85
(XEN) HVM27: int13_harddisk: function 08, unmapped device for ELDL=86
(XEN) HVM27: int13_harddisk: function 08, unmapped device for ELDL=87
(XEN) io.c:199:d27 MMIO emulation failed @ 0020:c0bab5d0: 0f ae 3b 01 d3 01

In qemu.log(I have added some fprintfs to raw_open) I can find this.

# less qemu-dm-FreeBSD8.log                                                     
                                                                                
   
domid: 27
qemu: the number of cpus is 1
CAlling bdrv_open2 /home/xenstuff/FreeBSD.img
raw open called /home/xenstuff/FreeBSD.img
open syscall errno 2 -- open_flags 2 - |/home/xenstuff/FreeBSD.img|
CAlling bdrv_open2 /dev/mapper/rvg00-testlv
raw open called /dev/mapper/rvg00-testlv
open syscall errno 2 -- open_flags 2 - |/dev/mapper/rvg00-testlv|
Watching /local/domain/0/device-model/27/logdirty/next-active
Watching /local/domain/0/device-model/27/command
Opening device /home/xenstuff/FreeBSD.img
Opening device /dev/mapper/rvg00-testlv
qemu_map_cache_init nr_buckets = 10000 size 3145728
shared page at pfn 17ffe
buffered io page at pfn 17ffc
Time offset set 0
Register xen platform.
Done register platform.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0

I have changed raw_getlength to support NetBSD, so there shouldn't be problem 
in device size detection. I think that problem is somewhere in NetBSD but I 
need some guidance where to look in xen source tree to find out what can be 
wrong. This problem was found on xen-3.3.2 and xen-unstable. Do you have any 
ideas where I should look to fix this problem ?

Regards

Adam.


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

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