> I got this error starting a domU
>
> Started domain <servername>
> xen_start_info @ffffffff80837000
> shared @m00befea000 @ffffffff80107000=@ffffffffff5fd000 [0x802]
> xen_start_info: @ffffffff80837000
> cr3 0000000000101000 pml4p ffffffff80101ff8
> pml4e 0000000000103067 (real 00000004ea4f4067) pgdp ffffff8000103ff0
> pgde 0000000000105067 (real 00000004e6dca067) pmdp ffffff8000105020
> pmde 0000000000841067 (real 00000004e0dc6067) ptep ffffff80008411b8
> pte 0010000000837027 (real 0010000509c18027)
> xen_shared_info: @ffffffffff5fd000
> cr3 0000000000101000 pml4p ffffffff80101ff8
> pml4e 0000000000103067 (real 00000004ea4f4067) pgdp ffffff8000103ff8
> pgde 0000000000000000 is none
> PAGE_OFFSET+1.2: @ffffff8000001000
> cr3 0000000000101000 pml4p ffffffff80101ff8
> pml4e 0000000000103067 (real 00000004ea4f4067) pgdp ffffff8000103000
> pgde 0000000000844067 (real 00000004e0dc3067) pmdp ffffff8000844000
> pmde 0000000000845067 (real 00000004e0dc2067) ptep ffffff8000845008
> pte 0000000000001167 (real 000000055ed2c167)
> rtc: IRQ 8 is not free.
> i8042.c: No controller found.
> Kernel panic - not syncing: Attempted to kill init!
The above is the output from the domU kernel, right? Including the kernel
panic message? Did you get this from an xm create -c? Was it the complete
output from that command? It looks like there some stuff missing from this
output, maybe some got dropped somehow. Can you do xm create -c and try
again?
Was there anything new in "xm dmesg" after booting this domain?
> What I did was install the kernel-domU kernel into a real server,
> clone it with dd and boot it with this config file:
> name = "<servername>"
> maxmem = "2048"
> disk = [ 'phy:/dev/HYP11VM/DISK,sda,w', ]
> vif = ['bridge=xenbr0','bridge=xenbr1' ]
> vfb = ["type=vnc,vncunused=1"]
> bootloader="/usr/bin/pygrub"
> vcpus=2
> on_reboot = 'restart'
> on_crash = 'restart'
Well that generally looks sane to me. You could try setting vcpus=1 and
seeing if that makes a difference.
> My env is:
> dom0-> xen 3.2 on 64 bits dom0
> <servername> -> 64 bit server with kernel-xenU-2.6.9-67.0.7.EL
>
> the xen logs say:
> xc_dom_boot_xen_init: ver 3.2, caps xen-3.0-x86_64 xen-3.0-x86_32p
> hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
> xc_dom_parse_image: called
> xc_dom_find_loader: trying ELF-generic loader ... failed
> xc_dom_find_loader: trying multiboot-binary loader ... failed
> xc_dom_core.c:499: panic: xc_dom_find_loader: no loader found
>
> [2008-05-02 14:58:21 8653] ERROR (XendDomainInfo:111) Domain construction
> failed Traceback (most recent call last):
> File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
> line 109, in create_from_dict
> vm.start()
> File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
> line 420, in start
> XendTask.log_progress(31, 60, self._initDomain)
> File "/usr/lib64/python2.4/site-packages/xen/xend/XendTask.py", line
> 209, in log_progress
> retval = func(*args, **kwds)
> File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
> line 1769, in _initDomain
> raise VmError(str(exn))
> VmError: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n')
That error doesn't square as the cause of what you're seeing above. That
error suggests you tried booting a kernel at some point that was not loadable
by Xen; might you have done this earlier? If the panic message is coming
from the guest then it must have got loaded somehow, so this
xc_dom_find_loader problem shouldn't be the root cause.
Where did you get kernel-xenU-2.6.9-67.0.7.EL from? I presume you're using
RHEL? Is that a standard RHEL kernel, then? Where did you install your Xen
from? Where is your dom0 kernel from?
Cheers,
Mark
--
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home