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
 
   
 

xci-devel

[Xci-devel] qemu-dm segfault at pv guest system

To: xci-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xci-devel] qemu-dm segfault at pv guest system
From: Kornelius Prell <kornelius.prell@xxxxxxxxxxxxxx>
Date: Tue, 1 Sep 2009 15:14:21 +0100
Delivery-date: Tue, 01 Sep 2009 07:14:21 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=hIYilIfRKlZFGxp2o0HsZMrrfiYFe7vvKJ8YUTiAkMQ=; b=kLz6bPZw6weRsDgPQMQur5JRl2HtULuZzOSRI2ISvUDY2JIR1OHW50EiIVKn1vmIax LEonFfUrbSDCm8jdan0gzdUGKPzjkOMr+15qrLu43lrUywNCJRfIf77/SDIcOIRuh2xz bbEaeK5m6R0YIVouez6BVbW/kgOvgk00Rzi8U=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=L8lvUeXboUbdkII55kkUkz3Xr3P/16t/asADQH+D7d3aITW2rOLUtOfDZijf463oz/ X7F6ziAGowYF+AmFvHkc2kxK/Cw2hj/rbSyyXBC2NuNzUxI9R1mzUNxD9w8BS5TMfGZJ t4gXgONJVv751Lm6cgumS4c7D2oUaiziRY3tk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-archive: <http://lists.xensource.com/archives/html/xci-devel>
List-help: <mailto:xci-devel-request@lists.xensource.com?subject=help>
List-id: xci-devel.lists.xensource.com
List-post: <mailto:xci-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xci-devel>, <mailto:xci-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xci-devel>, <mailto:xci-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xci-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hello,

I set the vnc option in a pv domain config file (Ubuntu 9.04 32 bit with XCI kernel/initrd) to test qemu-dm and its framebuffer support (see below for full config file).
Unfortunately it runs into a segmentation fault as soon as I try to access it via a vnc viewer (dom0 dmesg):
[  156.326275] qemu-dm[1500]: segfault at 494 ip 080c2f7a sp bff11b40 error 4 in qemu-dm[8048000+10d000]

Debugging with gdb shows the cause of the error in the function xenfb_update in /xenclient-ioemu/hw/xenfb.c
The parameter passed to the function is 0, but as it should be a pointer to the xenfb device it results later in a segmentation fault (as the height and the width of it are tested to be not 0).

Hower using xenconsole to connect to the domain reveals that xenbus tries to connect to the vfb device during the boot process, but fails (domU console):
[    5.678469] XENBUS: Waiting for devices to initialise: 295s...290s...285s...(...)...0s...
[  300.588592] XENBUS: Timeout connecting to device: device/vfb/0 (local state 3, remote state 1)

Looking at /proc/fb however shows its existence:
cat /proc/fb
0 VGA16 VGA
1 xen

pv dom config file:
uuid = 01000000-0000-0000-0000-102130000004
hvm = false
memory = 1024
debug = true
kernel = /boot/vmlinuz-xci
initrd = /boot/initrd.img-xci
cmdline = root=/dev/sda1 video=xenfb
disk = /dev/sda:file:sda:w:disk
vif = bridge=xenbr0
serial = /dev/tty2
extra-hvm = dom0-input=1
extra-hvm = intel=
extra-hvm = std-vga=

Am I missing essential parameters?

Thanks for the help!

regards,
Kornelius
_______________________________________________
Xci-devel mailing list
Xci-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xci-devel
<Prev in Thread] Current Thread [Next in Thread>