Hello Samuel,
Thanks again for the response and offer to look into it.
Comments/questions inline.
On Tue, Aug 26, 2008 at 7:45 PM, Samuel Thibault
<samuel.thibault@xxxxxxxxxxxxx> wrote:
> Hello,
>
> Todd Deshane, le Tue 26 Aug 2008 15:57:50 -0400, a écrit :
>> a)
>> root (hd0,1)
>> setup (hd0)
>> boot (or quit)
>>
>> In this case however setup and quit are unknown commands.
>> Is that expected?
>
> Yes. The MBR of a partition is supposed to contain a real bootloader,
> not a PV bootloader, thus the setup command doesn't hold. quit only
> makes sense when running from a Unix shell, so doesn't make sense here,
> reboot or halt can be used instead.
>
So do you mean that this is fundamental to a PV guest or just under these
circumstances?
Since I am able to run the following when booted into the same guest by
passing a kernel and ramdisk.
grub> root (hd0,1)
root (hd0,1)
grub> setup (hd0)
setup (hd0)
 Checking if "/boot/grub/stage1" exists... yes
 Checking if "/boot/grub/stage2" exists... yes
 Checking if "/boot/grub/e2fs_stage1_5" exists... yes
 Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 16 sectors are embedded.
succeeded
 Running "install /boot/grub/stage1 (hd0) (hd0)1+16 p
(hd0,1)/boot/grub/stage2 /boot/grub/menu.lst"... succeeded
Done.
grub> quit
quit
>> b)
>> kernel (hd0,1)/boot/vmlinuz-2.6.18.8-xen
>> initrd (hd0,1)/boot/initrd.img-2.6.18.8-xen
>> boot
>>
>> In this case, I get
>> Page fault in pagetable walk (access to invalid memory?).
>
> Should work :/
> Could you send me your images so I can test?
>
Sent a link in a previous private mail, let me know if there are any problems.
>> It starts booting the kernel, but gets stuck during the boot process at:
>>
>> rtc: IRQ 8 is not free.
>> Non-volatile memory driver v1.2
>> RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
>> loop: loaded (max 8 devices)
>> Xen virtual console successfully installed as xvc0
>> Event-channel device installed.
>> netfront: Initialising virtual ethernet driver.
>> xen-vbd: registered block device major 3
>> hda:
>
> Is there any message in dom0's dmesg or xm dmesg?
>
Nothing is added to dmesg or xm dmesg that I can see.
I did however notice some text fly by that I hadn't before.
it is below just in case it could be useful in debugging
when running the xm create -c guest1, I get:
Using config file "/etc/xen/guest1".
Started domain guest1
 Xen Minimal OS!
start_info: 0x9ac000
 nr_pages: 16384 shared_inf: cec1c000
 pt_base: 0x9af000 mod_start: 0x0
 mod_len: 0
 flags: 0x0
 cmd_line: root=/dev/hda2 ro (hd0,1)/boot/grub/menu.lst
 stack: 0x94b860-0x96b860
MM: Init
 _text: 0x0
 _etext: 0x5cd36
 _erodata: 0x74000
 _edata: 0x7cb00
 stack start: 0x94b860
 _end: 0x98be48
 start_pfn: 9bb
 max_pfn: 4000
Mapping memory range 0xc00000 - 0x4000000
setting 0x0-0x74000 readonly
followed by the GRUB/grubdom prompt on a cleared screen.
Cheers,
Todd
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel