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

Re: [Xen-devel] Re: pv_ops dom0 USB fixed

To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Re: pv_ops dom0 USB fixed
From: "Todd Deshane" <deshantm@xxxxxxxxx>
Date: Sat, 13 Dec 2008 13:20:31 -0500
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Aviv Grafi <aviv@xxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Delivery-date: Sat, 13 Dec 2008 10:21:15 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:cc:in-reply-to:mime-version:content-type:references; bh=fSMOHshmNIGwyhCXOJDglkTYJW9Psqz8rAdBULDuJtA=; b=TzUuAlfB3dvXOLJG+zjDorUrvKxdTN106DWp2KKjoSRDLsq+enVN6zDu+zwty+TN2t EY7euqosJufk51wj8jOpbg0wmULBRdEYjcwPt55FHe/350ZeT/32a49IZp7TsjeL8fcg qNsgdvCWufn/wDLt4e/R2fLH9ydDIDywywY2I=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:references; b=u774gmxh56N1Oak5SVTUPsTo8E27dGKolJFtGC0J3a75nIiaFhBsfxaRW0SkPqS9Hz 59VOIdfcvj2VYFcMN78qvCFB01OOwVcAs0h65+O1OT/yKdVJtM0NM2s4zvL8CoqlrYD+ BsqETT4tE4ejeeaUayhnwVrY79OrBlgjLEZK4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4941967C.2020801@xxxxxxxx>
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>
References: <4940210C.1060401@xxxxxxxx> <1e16a9ed0812111147h3416cbb5uc11a8b9f5f0d0e80@xxxxxxxxxxxxxx> <1229025794.2770.32.camel@xxxxxxxxxxxxxxxxxxxxx> <1e16a9ed0812111220h40e62ee1ma27f48c5207bc735@xxxxxxxxxxxxxx> <49417755.4050703@xxxxxxxx> <1e16a9ed0812111312p2547884cgf4020eb9ea92ddde@xxxxxxxxxxxxxx> <1229030361.2770.36.camel@xxxxxxxxxxxxxxxxxxxxx> <1e16a9ed0812111323k60f4404ekd367f3d24f8b2bc2@xxxxxxxxxxxxxx> <1e16a9ed0812111339rd084ed7md1e6d9e7346ab18f@xxxxxxxxxxxxxx> <4941967C.2020801@xxxxxxxx>
Reply-to: deshantm@xxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Dec 11, 2008 at 5:38 PM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
> Todd Deshane wrote:
>>
>> disk only, took out vif and dhcp options.
>>
>> Still didn't boot, same error.
>>
>> Log attached.
>>
>> Also changing for 20 to 256 memory gave problems.
>>
>> Looks like some sort of memory problem too.
>>
>
> Hm, seems to be trying to shrink dom0 too much.  What's your domain config
> file?
>

kernel = "/boot/vmlinuz-2.6.28-rc8-tip"
ramdisk = "/boot/initrd.img-2.6.28-rc8-tip"
memory = "256"
name = "ubuntu-hardy-jailtime"
disk = ['tap:aio:/home/deshantm/ubuntu.8-04.64.img,sda1,w']
root = "/dev/sda1 ro"
extra = "xencons=tty"

I also tried file:/ for the disk

Same errors.

I poke around a little more in the xen logs to see if I can find any more
useful info on the guest problem

> mem=3G is probably overkill.  There's no problem in Xen using all your
> memory, but you should set dom0_mem=1G or something (less than 3G, but you
> probably don't need all that much).  How much memory does your system have?
>

I put the dom0_mem down to 512M for now, that should do.

I think that mem=3G is still necessary. I'll send some vtd logs that show it
crash without mem=3G and not crash with mem=3G


>> Also, it looks like I am getting a number of errors in
>> xend-debug.log to do with scsi commands.
>>
>> I will try to track down potentially missing packages.
>>
>> Any idea on what dependencies there might be?
>>
>
> Looks like you're missing lsscsi and udev (though I would have thought
> Ubuntu would be using udev).
>

I fixed the lsscsi problem previously (earlier testing).
udev is installed. There may be some issue with its working with
the dom0 kernel though. I have seen the error messages
of /sbin/scsi_id: not found


> BTW, I just pushed up a patch which should clear up the warnings in your
> boot messages (they could potentially result in a system-locking deadlock,
> so its probably worthwhile).
>

I just pulled the latest patches. The vga is closer to working. I don't see
the kernel boot messages, but I do get a login prompt (text only).
Which works.

My Xorg logs (a working one and a non working one) are attached.

Cheers,
Todd


-- 
Todd Deshane
http://todddeshane.net
http://runningxen.com

Attachment: Xorg-errorlog1
Description: Binary data

Attachment: Xorg.0.log
Description: Text Data

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