Re: [Xen-users] help on FreeBSD using hvm

[Sergi Seira <s.seira@xxxxxxxxx>]

Hi,

I commented the line:

 vif = [ 'type=ioemu, bridge=xenbr0' ]

and the FreeBSD installation can start without a kernel panic.

leaving:

 vif = ['']

produces the kernel panic again.

I also tried with a FreeBSD 6.0, but panic-ed too.

Any idea of what causes this kernel panic?

Regards,
Sergi


Sergi Seira wrote:
> Hi,
> 
> I found that the domain was crashing because of trying to boot a freebsd
> 6.1 amd64 kernel ... an i386 kernel kind of gets a little further, until:
> 
> rlphy0: <RealTek internal media interface> on miibus0
> rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> re0: Ethernet address: 00:60:e0:e1:21:d7
> re0: diagnostic failed, failed to receive packet in loopback mode
> re0: attach aborted due to hardware diag failure
> kernel trap 12 with interrupts disabled
> 
> Fatal trap 12: page fault while in kernel mode
> fault virtual address   = 0x74
> fault code              = supervisor read, page not present
> instruction pointer     = 0x20:0xc066dd41
> stack pointer           = 0x28:0xc1020a54
> frame pointer           = 0x28:0xc1020a58
> code segment            = base 0x0, limit 0xfffff, type 0x1b
>                         = DPL 0, pres 1, def32 1, gran 1
> processor eflags        = resume, IOPL = 0
> current process         = 0 (swapper)
> trap number             = 12
> panic: page fault
> Uptime: 1s
> 
> I'm gonna try to boot a 6.0 freebsd, to see if it is something related
> to the drivers in the distribution or what.
> 
> Regards,
> Sergi
> 
> Sergi Seira wrote:
>> Hi again,
>>
>> well, sdl was not working because I was calling xm from root and Xserver
>> was started from another user.
>> I had to switch to that user and :
>>
>> xhost +local:root
>>
>> to allow root to start X applications from localhost.
>>
>> Now, at last I see a window with a FreeBSD installation going on ... but
>> not everything is good news ... the domain crashes when the countdown in
>> the freebsd splash window ends.
>>
>> Logs at /var/log/xen doesn't say much about the crash ... how can I
>> debug this deeply?
>>
>> Thanks,
>> Sergi
>>
>> Sergi Seira wrote:
>>> Hello,
>>>
>>> I've made some progress ...
>>>
>>> I found that one could set up a tap interface with:
>>>
>>> # modprobe tun
>>> # tunctl -t tap0
>>>
>>> a command included in uml-utilities package for debian (dist. I'm using).
>>>
>>> Now the domain starts and spends some CPU time but dies:
>>>
>>> # tail xend.log
>>> [2007-02-27 16:24:50 xend.XendDomainInfo 3297] WARNING
>>> (XendDomainInfo:950) Domain has crashed: name=FreeBSD60_01 id=8.
>>> [2007-02-27 16:24:50 xend.XendDomainInfo 3297] DEBUG
>>> (XendDomainInfo:1483) XendDomainInfo.destroy: domid=8
>>> [2007-02-27 16:24:50 xend.XendDomainInfo 3297] DEBUG
>>> (XendDomainInfo:1491) XendDomainInfo.destroyDomain(8)
>>> [2007-02-27 16:24:50 xend 3297] DEBUG (image:533) hvm shutdown watch
>>> unregistered
>>> [2007-02-27 16:24:50 xend 3297] DEBUG (image:572) hvm reboot feature
>>> watch unregistered
>>>
>>> It seems a problem with vnc?
>>>
>>> # tail qemu-dm.8309.log
>>> domid: 7
>>> qemu: the number of cpus is 1
>>> qemu_map_cache_init nr_buckets = 1000
>>> shared page at pfn:ffff
>>> buffered io page at pfn:fffd
>>> vncviewer execlp failed
>>> char device redirected to /dev/pts/2
>>> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
>>>
>>> I'm stuck here right now. Any ideas?
>>> Why do you think I have to do this things (tun/tap) by hand instead of
>>> been done by xm?
>>>
>>> About the cdrom issue ... I removed the cdrom part and could see the
>>> qemu log complaining about not including /dev/cdrom.
>>>
>>> Thanks,
>>> regards,
>>> Sergi
>>>
>>>
>>>
>>>
>>> Mark Williamson wrote:
>>>>> CPU time doesn't go up.
>>>> Weird.  It's strange given the guest also isn't paused...
>>>>
>>>>> I've checked /var/log/xen/qemu-dm.19594.log (I missed this files before
>>>>> posting):
>>>> I noticed that you had the physical CD-ROM drive mapped as the guests 
>>>> virtual 
>>>> CDROM.  Could you try taking that out, please?  I'm not at all convinced 
>>>> that's the source of the problem but I do remember having problems when I 
>>>> tried to do that myself (that was for an installation of Windows - I ended 
>>>> up 
>>>> ripping the CD to an ISO and using that as the virtual CD drive!)
>>>>
>>>> Cheers,
>>>> Mark
>>>>
>>>>> domid: 3
>>>>> qemu: the number of cpus is 1
>>>>> warning: could not open /dev/net/tun: no virtual network emulation
>>>>> Could not initialize device 'tap'
>>>>>
>>>>> After searching a little I found that maybe:
>>>>>
>>>>> modprobe tun
>>>>>
>>>>> would work, but I get the same error.
>>>>>
>>>>> Do I have to recompile xen with some tun/tap option?
>>>>>
>>>>> Thanks for your quick answer.
>>>>> Regards,
>>>>> Sergi
>>>>>
>>>>> Mark Williamson wrote:
>>>>>>> I'm trying to install FreeBSD 6.0 from cdrom to a fully virtualized
>>>>>>> machine. I've already run domU using xen patched kernels without a
>>>>>>> problem, but can't create a fully virtualized domU.
>>>>>>>
>>>>>>> I am running :
>>>>>>>
>>>>>>>  - AMD dual opteron with SVM Code option enabled (BIOS)
>>>>>>>  - xen 3.0.4 compiled from sources
>>>>>> OK.  It *should* work - my own test machine is an AMD-V box running
>>>>>> 3.0.4-testing
>>>>>>
>>>>>>> When issuing :
>>>>>>>
>>>>>>> # xm create xm_fbsd.hvm
>>>>>>> Using config file "./xm_fbsd.hvm".
>>>>>>> Started domain FreeBSD60_01
>>>>>>>
>>>>>>>
>>>>>>> It starts (apparently) my fbsd domU:
>>>>>>>
>>>>>>> # xm list
>>>>>>> Name                      ID   Mem VCPUs      State   Time(s)
>>>>>>> Domain-0                   0   125     4     r-----    168.5
>>>>>>> FreeBSD60_01              18   256     1     ------      0.0
>>>>>>>
>>>>>>> nothing happens, nothing really starts. It will do the same, if I remove
>>>>>>> all entries abount disks ... I don't know where to look for errors, for
>>>>>>> xend.log doesn't really tell me anything interesting.
>>>>>> Does the CPU time go up?
>>>>>>
>>>>>>> I have tried both sdl=1 and vnc=1, but no console access.
>>>>>> The SDL needs there to be an accessible X server (e.g. via SSH
>>>>>> forwarding, or you're running from a terminal on the local X server).  Do
>>>>>> you have this?
>>>>>>
>>>>>> Have you tried connecting a VNC viewer manually to port 5900 +
>>>>>> vncdisplay?
>>>>>>
>>>>>> Are you running 64-bit Xen on the host?
>>>>>>
>>>>>> Cheers,
>>>>>> Mark
>>>>>>
>>>>>>> Long output from xm list:
>>>>>>>
>>>>>>> # xm list --long
>>>>>>> (domain
>>>>>>>     (domid 0)
>>>>>>>     (on_crash restart)
>>>>>>>     (memory 125)
>>>>>>>     (uuid 00000000-0000-0000-0000-000000000000)
>>>>>>>     (bootloader_args )
>>>>>>>     (name Domain-0)
>>>>>>>     (maxmem 125)
>>>>>>>     (on_reboot restart)
>>>>>>>     (on_poweroff destroy)
>>>>>>>     (vcpus 4)
>>>>>>>     (bootloader )
>>>>>>>     (shadow_memory 0)
>>>>>>>     (cpu_weight 256)
>>>>>>>     (cpu_cap 0)
>>>>>>>     (features )
>>>>>>>     (on_xend_start ignore)
>>>>>>>     (on_xend_stop ignore)
>>>>>>>     (cpu_time 171.188784501)
>>>>>>>     (online_vcpus 4)
>>>>>>>     (status 2)
>>>>>>>     (memory_dynamic_min 125)
>>>>>>>     (memory_dynamic_max 0)
>>>>>>>     (state r-----)
>>>>>>> )
>>>>>>> (domain
>>>>>>>     (domid 19)
>>>>>>>     (on_crash destroy)
>>>>>>>     (memory 256)
>>>>>>>     (uuid 64b0c736-4736-a29b-3425-21f90f137eae)
>>>>>>>     (bootloader_args )
>>>>>>>     (name FreeBSD60_01)
>>>>>>>     (maxmem 264)
>>>>>>>     (on_reboot destroy)
>>>>>>>     (on_poweroff destroy)
>>>>>>>     (localtime 0)
>>>>>>>     (vcpus 1)
>>>>>>>     (bootloader )
>>>>>>>     (shadow_memory 8)
>>>>>>>     (cpu_weight 256)
>>>>>>>     (cpu_cap 0)
>>>>>>>     (features )
>>>>>>>     (on_xend_start ignore)
>>>>>>>     (on_xend_stop ignore)
>>>>>>>     (start_time 1172570145.59)
>>>>>>>     (cpu_time 6.4349e-05)
>>>>>>>     (online_vcpus 1)
>>>>>>>     (image
>>>>>>>         (hvm
>>>>>>>             (kernel /usr/lib/xen/boot/hvmloader)
>>>>>>>             (nographic 0)
>>>>>>>             (vnc 0)
>>>>>>>             (sdl 1)
>>>>>>>             (vncunused 1)
>>>>>>>             (device_model /usr/lib/xen/bin/qemu-dm)
>>>>>>>             (xauthority /root/.Xauthority)
>>>>>>>             (vncconsole 1)
>>>>>>>             (pae 1)
>>>>>>>             (apic 1)
>>>>>>>             (acpi 1)
>>>>>>>             (boot d)
>>>>>>>             (isa 0)
>>>>>>>             (localtime 0)
>>>>>>>             (serial pty)
>>>>>>>             (usb 0)
>>>>>>>             (vcpus 1)
>>>>>>>         )
>>>>>>>     )
>>>>>>>     (status 2)
>>>>>>>     (memory_dynamic_min 256)
>>>>>>>     (memory_dynamic_max 264)
>>>>>>>     (state ------)
>>>>>>>     (store_mfn 65534)
>>>>>>>     (device
>>>>>>>         (vif
>>>>>>>             (bridge xenbr0)
>>>>>>>             (uuid 10950eec-5eb7-94a8-b297-faa18264460d)
>>>>>>>             (script vif-bridge)
>>>>>>>             (mac 00:16:3e:00:dd:c1)
>>>>>>>             (type ioemu)
>>>>>>>             (backend 0)
>>>>>>>         )
>>>>>>>     )
>>>>>>>     (device
>>>>>>>         (vbd
>>>>>>>             (uname file:/xenvm/fbsd/freebsd_xen_INSTALL.img)
>>>>>>>             (uuid 9f100ba5-4cae-0c05-7d76-09c9c4a24c4d)
>>>>>>>             (mode w)
>>>>>>>             (dev hda:disk)
>>>>>>>             (backend 0)
>>>>>>>         )
>>>>>>>     )
>>>>>>>     (device
>>>>>>>         (vbd
>>>>>>>             (uname phy:/dev/cdrom)
>>>>>>>             (uuid 71c65447-84b2-8168-fdf4-8e4f3d795adc)
>>>>>>>             (mode r)
>>>>>>>             (dev hdc:cdrom)
>>>>>>>             (backend 0)
>>>>>>>         )
>>>>>>>     )
>>>>>>> )
>>>>>>>
>>>>>>>
>>>>>>> Thanks in advance,
>>>>>>> regards,
>>>>>>> Sergi
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Xen-users mailing list
>>>>>>> Xen-users@xxxxxxxxxxxxxxxxxxx
>>>>>>> http://lists.xensource.com/xen-users
>>>>> _______________________________________________
>>>>> Xen-users mailing list
>>>>> Xen-users@xxxxxxxxxxxxxxxxxxx
>>>>> http://lists.xensource.com/xen-users
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-users
>>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-users
>>
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users