[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] unable to boot from cdrom using OVMF in latest xen-unstable

Il 29/07/2015 12:44, Wei Liu ha scritto:
On Wed, Jul 29, 2015 at 12:42:41PM +0200, Fabio Fantoni wrote:
Il 29/07/2015 11:58, Wei Liu ha scritto:
On Wed, Jul 29, 2015 at 11:31:30AM +0200, Fabio Fantoni wrote:
Today I retried ovmf after long time from previous, I tried old fedora 20
uefi domUs and still boot correctly but trying to boot from cdrom using
boot='dc' or boot='d' don't boot from cdrom (seems didn't try) but boot from
harddisk (even with boot='d').
After booting fedora I checked the cdrom and see it correctly, the problem
seems only about boot order.
xen is build from staging git based on commit
44313ab77f3e3c5b566ea4f23b0e32bfd5eafa29 and ovmf is from debian package

If you need more informations/tests tell me and I'll post them.

Thanks for any reply and sorry for my bad english.
OK, the commit you tested contains the fix to booting OVMF.

Do you have serial log?

You mean ovmf serial log? probably I did it in past but I not remember how
and with a fast search I not found (probably was some years ago when I
started to try ovmf and initially with xen domUs was not working at all)
I found only serial="pty" commented in my tests domUs cfg probably related
but I don't remember how to see/store the output, can you tell me it please?
I meant Xen serial log. And you probably need to increase your log level
in Xen command line.

Sorry for my stupid question, what xen serial log you mean? serial of dom0 for debug domU's internal boot seems very strange to me.

this is my actual dom0 grub entry is:
menuentry 'RAID - Debian 7.8 (wheezy) con Linux 3.16.0-0.bpo.4-amd64 e XEN 4.6-unstable' --class debian --class gnu-linux --class gnu --class os --class xen {
        set fallback="1"
        set root='(RAID-ROOT)'
        echo    'Caricamento Hypervisor Xen 4.6-unstable...'
        multiboot       /boot/xen.gz placeholder dom0_mem=2G,max:3G
        echo    'Caricamento Linux 3.16.0-0.bpo.4-amd64 ...'
module /boot/vmlinuz-3.16.0-0.bpo.4-amd64 placeholder root=/dev/mapper/RAID-ROOT ro swiotlb=65762 quiet
        echo    'Caricamento ramdisk iniziale...'
        module  /boot/initrd.img-3.16.0-0.bpo.4-amd64

this is an old entry I used for debug dom0 boot problem:
menuentry 'Wheezy con Linux 3.2.0-4-amd64 e XEN 4.4 - RAID - Debug su Seriale' --class debian --class gnu-linux --class gnu --class os {
    set root='(RAID-ROOT)'
    echo    'Caricamento Hypervisor Xen 4.4...'
multiboot /boot/xen-4.4-amd64.gz placeholder dom0_mem=2G,max:2G swiotlb=65762 loglvl=all guest_loglvl=all sync_console console_to_ring com2=19200,8n1 console=com2
    echo    'Caricamento Linux 3.2.0-4-amd64...'
linux /boot/vmlinuz-3.2.0-4-amd64 placeholder root=/dev/mapper/RAID-ROOT ro console=hvc0 earlyprintk=xen nomodeset
    echo    'Caricamento ramdisk iniziale...'
    initrd    /boot/initrd.img-3.2.0-4-amd64

About dom0 you mean add only "loglvl=all guest_loglvl=all" or also other thing?
And about domU?

Thanks for any reply.

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.