Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 1 Feb 2010 22:36:35 +0100
From:      G VM <drums_gvm@hotmail.com>
To:        <info@deployis.eu>
Cc:        freebsd-xen@freebsd.org
Subject:   Re: Kernel panic on FreeBSD 8.0 RELEASE when starting kernel
Message-ID:  <SNT130-w118D540BB49F215E74B64291580@phx.gbl>

next in thread | raw e-mail | index | archive | help

G VM wrote:
> Deploy IS INFO wrote:
>  =20
>> G VM wrote:
>>    =20
>>>   Deploy IS INFO wrote:
>>>      =20
>>>> Hi=2C
>>>>
>>>> You can run (in theory) any FreeBSD on a hardware that has HVM
>>>> support. You can check that with xm info. You can only run FreeBSD 8
>>>> as a PV guest with 32bit arch and hvm-pv with amd64. For the pv or
>>>>        =20
>>> the
>>>      =20
>>>> hvm-pv mode you have to compile the XEN (for 32bit) or XENHVM (amd64)
>>>> kernel config.
>>>>
>>>> You'll have to install FreeBSD as a hvm guest and after a successful
>>>> install you may go on with the above mentioned kernels.
>>>>
>>>> For pv mode use only 1 vcpu and max 2 for hvm-pv.
>>>>
>>>> Regards=2C
>>>> Andras
>>>>
>>>> G VM wrote:
>>>>        =20
>>>>> Justin T. Gibbs wrote:
>>>>>          =20
>>>>>> On 1/24/2010 4:54 PM=2C G VM wrote:
>>>>>>
>>>>>>            =20
>>>>>>> Hi all=2C
>>>>>>>
>>>>>>> I wanted to try running FreeBSD as a guest os.
>>>>>>>
>>>>>>>              =20
>>>>> I followed the instructions on this url.
>>>>> http://www.ita.com.ua/eng/articles.htm?id=3D34
>>>>>
>>>>> I am not sure what Xen exactly does. Does it uses the kernel on the
>>>>> dom0? Or does it both uses the bsd kernel on the dom0 and a modified
>>>>> kernel on domU?
>>>>> I do not have a done:
>>>>>
>>>>> make buildkernel KERNCONF=3D/XEN
>>>>>
>>>>> Is this necessary? I thought xen support was included in the kernel.
>>>>>
>>>>> Do note the instructions I followed. I used those.
>>>>> /
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> freebsd-xen@freebsd.org mailing list
>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-xen
>>>>> To unsubscribe=2C send any mail to
>>>>>          =20
>>> "freebsd-xen-unsubscribe@freebsd.org"
>>>      =20
>>>>        =20
>>> # xm info
>>> host : backupserver
>>> release : 2.6.18-164.9.1.el5xen
>>> version : #1 SMP Tue Dec 15 21:31:37 EST 2009
>>> machine : x86_64
>>> nr_cpus : 2
>>> nr_nodes : 1
>>> cores_per_socket : 2
>>> threads_per_core : 1
>>> cpu_mhz : 2210
>>> hw_caps :
>>> 178bf3ff:ebd3fbff:00000000:00000010:00002001:00000000:0
>>> 000001f:00000000
>>> virt_caps : hvm
>>> total_memory : 2046
>>> free_memory : 512
>>> node_to_cpu : node0:0-1
>>> node_to_memory : node0:512
>>> xen_major : 3
>>> xen_minor : 4
>>> xen_extra : .2
>>> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
>>> hvm-3.0-x
>>> 86_32p hvm-3.0-x86_64
>>> xen_scheduler : credit
>>> xen_pagesize : 4096
>>> platform_params : virt_start=3D0xffff800000000000
>>> xen_changeset : unavailable
>>> cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)
>>> cc_compile_by : root
>>> cc_compile_domain : gitco.tld
>>> cc_compile_date : Wed Nov 11 21:16:28 CET 2009
>>> xend_config_format : 4
>>>
>>> So this seems ok.
>>>
>>> My dom0 is x86_64.
>>> Does this mean I have to use hvm-pv (XENHVM) -> FreeBSD amd64 install?
>>> Or can I run the i386 pv (XEN) on a 64 bit dom0 too?
>>> Does this also needs a copy of the compiled kernel to the dom0?
>>>
>>> Do note that the default 8.0-RELEASE cd does panic (this is part of the
>>> config=2C when trying to do a normal install to compile the new kernel
>>> (that is why I used VMware to compile the kernel)):
>>> ...
>>>
>>> builder =3D "hvm"
>>> kernel =3D "/usr/lib/xen/boot/hvmloader"
>>> device_model =3D "/usr/lib64/xen/bin/qemu-dm"
>>>
>>> ...
>>>
>>>      =20
>> Hi=2C
>>
>> You can any guests arch that fits into the xm info's xen cap line=2C so
>> a 32bit pv guest is not a problem for you. We use the following
>> example config:
>>
>> kernel =3D "/usr/lib/xen/boot/hvmloader"
>> #kernel =3D "/path/to/pvkernel"
>> builder=3D'hvm'
>> memory =3D 1024
>> name =3D "FreeBSD8"
>> vif =3D [ '' ]
>> disk =3D [ 'phy:/dev/volgroup/freebsd-lv-rootfs=2Chda=2Cw'=2C
>> 'file:/path/to/8.0-RELEASE-amd64-disc1.iso=2Chdd:cdrom=2Cr' ]
>> boot=3D"cda"
>> vnc=3D1
>> vncpasswd=3D'ihavepassword'
>> #vcpus=3D'2'
>>
>> The commented parts are should be tried only after a succesful install
>> and of course the amd64 iso could be an i386 also. Under 3.3.1 Xen it
>> works one a X2270 test server and a x2250 prod server.
>>
>> Regards=2C
>> Andras
>>
>>
>>    =20
> I used the config you provided and have a 8.0-RELEASE x86 cd.
> When I boot from the CD the kernel panics:
> AMD Features2=3D....
> real memory =3D ... 500MB
> avail memory =3D ... 471MB
> panic: vm_fault: fault on nofault entry=2C addr: c3253000
> cpuid =3D 0
>
> :S That is the reason I compiled the kernel in VMware as I can install
> FreeBSD there.
> BUt then I got the panic I have in the beginning of this mailling list
> topic.
> If I am not mistaken I also tried the AMD64 cd and that did fail also.
> However when using 7.2 it just works ok.
>
> Anyone an idea?
> BTW=2C thanks so far for your help guys!
>
>  		 	   		  _______________________________________________
> freebsd-xen@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-xen
> To unsubscribe=2C send any mail to "freebsd-xen-unsubscribe@freebsd.org"
>
>
>  =20
Anyone has an idea? About the problem starting a XEN kernel OR the
problem starting the normal kernel with hvmloader?
Is this probably a kernel bug? And if so=2C where can I report it? Is it
likely Xen is the problem or FreeBSD is the problem?
Do I need more information than this? I can provide everything(even
memory dump if that would help).

Kind regards

 		 	   		  =



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?SNT130-w118D540BB49F215E74B64291580>