Запуск Linux через pvops в домене 0 Xen
Материал из Xgu.ru
From: Todd Deshane <firstname.lastname@example.org> To: xen-devel mailing list <email@example.com> Subject: [Xen-devel] pv_ops dom0 testing I am trying to get a pv_ops dom0 working for testing, but I am running into an elf_init error: (XEN) *** LOADING DOMAIN 0 *** (XEN) elf_init: not an ELF binary Full output attached. >From what I have read on the mailing lists, it seems that it is usually a problem with either grub or a corrupt dom0 kernel. Attached is my kernel config (2.6.28-rc6-tip). I followed the instructions on: http://wiki.xensource.com/xenwiki/XenParavirtOps Then I did make menuconfig and added: XEN_DOM0 XEN_BLKDEV_BACKEND here are the two grub entries I tried title Xen 3.4-unstable / Ubuntu 8.10, kernel 2.6.28-rc6-tip root (hd0,0) kernel /boot/xen-3.4-unstable.gz loglvl=all guest_loglvl=all dom0_max_vcpus=1 com1=115200,8n1 console=com1 noreboot dom0_mem=512M module /boot/vmlinuz-2.6.28-rc6-tip root=/dev/sda1 ro console=tty0 xencons=ttyS0,115200 module /boot/initrd.img-2.6.28-rc6-tip title Xen 3.4-unstable / Ubuntu 8.10, kernel 2.6.28-rc6-tip uuid 30596923-1435-4516-809d-ef8cd2958532 kernel /boot/xen-3.4-unstable.gz module /boot/vmlinuz-2.6.28-rc6-tip root=UUID=30596923-1435-4516-809d-ef8cd2958532 ro console=tty0 module /boot/initrd.img-2.6.28-rc6-tip The error was reported by others (unanswered), but they might be unrelated: http://xen.markmail.org/message/grqiejrlax6tyutn?q=elf_init http://xen.markmail.org/message/r5y32q5yyuv4okgj?q=elf_init Any suggestions on what went wrong and/or what else to try?
From: Aviv Grafi <firstname.lastname@example.org> I had the same issue few days ago: try to boot the vmlinux (and not vmlinuz) image that you can find in your kernel build directory. You can verify that you are booting the right image file by using the readelf tool.
Thanks for the tip Aviv. That got me a little farther. The debug output now ends with: (XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=4 (XEN) ioapic_guest_write: old_entry=000009f1, new_entry=000189f1 (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! Full output attached. Do I need to either modify more of the default kernel settings or pass some more options to Xen or the dom0 kernel? When running non-debug mode, I don't see any dom0 output on the screen,. I tried a few different console= lines tty0, xvc0, hvc0.... but only Xen hypervisor output ending with: (XEN) Xen is relinquishing VGA console Can someone post a working .config and grub config and/or the instructions to get to that point beyond the default setup? Cheers, Todd
I solved this one by adding "console=hvc0 earlyprintk=xen" to the dom0 kernel boot line (thanks to Jeremy Fitzhardinge [email@example.com]).
On Sat, Nov 29, 2008 at 5:32 PM, Aviv Grafi <firstname.lastname@example.org> wrote: > I solved this one by adding "console=hvc0 earlyprintk=xen" to the dom0 > kernel boot line (thanks to Jeremy Fitzhardinge [email@example.com]). Thanks again Aviv. I am really close now. The screen still shows nothing, but the debug output has the dom0 kernel boot. (Not sure why that would be... any thoughts?) In the debug output however I successfully get to the the (initramfs) prompt. Full output attached, but some interesting parts inline: (initramfs)cat /proc/cmdline root=/dev/sda1 ro console=tty0 xencons=ttyS0,115200 console=hvc0 earlyprintk=xen (initramfs) cat /proc/modules ata_piix 33586 1 - Loading 0xffffffffa0127000 libata 196576 1 ata_piix, Live 0xffffffffa00f5000 scsi_mod 184792 1 libata, Live 0xffffffffa00c5000 r8169 46084 0 - Live 0xffffffffa00b7000 mii 14464 1 r8169, Live 0xffffffffa00b1000 tg3 139396 0 - Live 0xffffffffa008c000 libphy 32896 1 tg3, Live 0xffffffffa007e000 ehci_hcd 46726 1 - Loading 0xffffffffa0070000 uhci_hcd 34037 1 - Loading 0xffffffffa0062000 usbcore 174512 3 ehci_hcd,uhci_hcd, Live 0xffffffffa0035000 thermal 27552 0 - Live 0xffffffffa002c000 processor 55224 1 thermal, Live 0xffffffffa0019000 fan 13832 0 - Live 0xffffffffa0013000 fuse 65728 1 - Live 0xffffffffa0000000 a listing of /dev doesn't show any sd* devices. So I am guessing I am running into a driver issue at this point. I will dig around more and compare my working vanilla linux config with the dom0 kernel to see if there is something missing in my dom0 kernel. Thanks for the help so far and if anything comes to mind why I don't see console output on the screen (and only in the debug output) that would be helpful to me. I'll report back on progress. If there are any obvious known workarounds, problems, bugs etc. let me know. I know that the pv_ops dom0 kernel is very much in development, but I am willing to try to work through that.