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