Re: Xen Fli4l Frage/Problem
Marko Lueke <[email protected]>
| Newsgroups | spline.eisxen |
|---|---|
| Organization | spline |
| Message-ID | <[email protected]> |
nabend Stefan,
Am 19.02.2011 21:23, schrieb Stefan Kuhne:
> Am 19.02.2011 20:11, schrieb Marko Lueke:
>
> Hallo,
>
>> bin ausversehen auf [m]kfli4l gekommen
>>
> das macht aber nichts kaputt, sonst wer meiner stÀndig defekt.
>
>> hab aber noch ne Sicherung des ganzen, also PacketmÀÃig um es wie in der
>> RC3 beschrieben wieder aufsetzen zu können, nur selbst im MenÌ komm ich
>> schon nicht weiter
>>
>> No. Filename
>> 1 - base.txt
>
> Wo baust Du dein fli4l normalerweise?
> (in der dom0 oder extern)
>
> Stefan Kuhne
ich stehe total auf dem Schlauch,
gebaut hab ich den Fli4l immer extern, das Problem ich jetzt nur,
Name of domain [fli4l]? lh-router
.Error: Unable to connect to xend: Broken pipe.
Done.
Press ENTER to continue
das kommt ja schon beim entpacken des mitgebrachen Templates, wenn ich
wehnigstends das zum laufen kriegen wÃŒrde um das einmal zu booten um
mein gesichertes Fli4l 3.4.0 aufspielen zu können, das komische ist, es
wird zwar trotz Fehler im MenÌ die Domain angelegt, aber trotzdem komm
ich nicht weiter
es mÃŒste doch aber zumindest das Template laufen?
komm nicht weiter als bis hier
.Done.
Press ENTER to continue
Checking if xend is running ..
Management for Xen domain lh-router
Status: Domain is not running
Buildstatus: Domain is not built!
You have to run mkfli4l first
fli4l configuration file(s):
No. Filename
1 - base.txt
Boot-Order: 50
Please enter command:
run [m]kfli4l,
Enter command or [1] to edit configuration file, ENTER=Return: m
fli4l 3.4.0 - starting build process
==============================================================================
using configuration from directory 'config.lh-router'...
--- read and check the build-environment from
config.lh-router/mkfli4l.conf...
------------------------------------------------------------------------------
--- check configuration in directory "config.lh-router"
----------------------
unable to open opt/files/lib/modules/2.6.24-24-xen/modules.alias,
ignoring aliases
unable to open opt/files/lib/modules/2.6.24-24-xen/modules.symbols,
ignoring aliases
unable to open opt/files/lib/modules/2.6.24-24-xen/modules.dep,
ignoring depdendencies
Can't access 'ne2k-pci'
Can't access 'nls_cp850'
Can't access 'nls_iso8859-1'
Can't access 'ip_tables'
Can't access 'iptable_filter'
Can't access 'ipt_log_target'
Can't access 'ipt_reject_target'
Can't access 'iptable_nat'
Can't access 'ipt_masquerade_target'
Can't access 'ipt_state'
Can't access 'ipt_length'
Can't access 'ipt_comment'
Can't access 'ipt_limit'
Can't access 'ipt_conntrack'
Can't access 'ipt_udp'
Can't access 'ipt_tcp'
Warning: Your kernel (2.6.24-24-xen) is missing the speaker module
(kernel/drivers/input/misc/pcspkr.ko). Therefore the router
will not beep although you set beep='yes' or
imond_beep='yes'.
Warning: Please consider removing all config variables of the old
packetfilter section from your config file to avoid any
confusion.
Error in configuration, aborting...
An Error occured while creating fli4l-files.
============================================
unable to open opt/files/lib/modules/2.6.24-24-xen/modules.alias,
ignoring aliases
unable to open opt/files/lib/modules/2.6.24-24-xen/modules.symbols,
ignoring aliases
unable to open opt/files/lib/modules/2.6.24-24-xen/modules.dep,
ignoring depdendencies
Can't access 'ne2k-pci'
Can't access 'nls_cp850'
Can't access 'nls_iso8859-1'
Can't access 'ip_tables'
Can't access 'iptable_filter'
Can't access 'ipt_log_target'
Can't access 'ipt_reject_target'
Can't access 'iptable_nat'
Can't access 'ipt_masquerade_target'
Can't access 'ipt_state'
Can't access 'ipt_length'
Can't access 'ipt_comment'
Can't access 'ipt_limit'
Can't access 'ipt_conntrack'
Can't access 'ipt_udp'
Can't access 'ipt_tcp'
Warning: Your kernel (2.6.24-24-xen) is missing the speaker module
(kernel/drivers/input/misc/pcspkr.ko). Therefore the router
will not beep although you set beep='yes' or
imond_beep='yes'.
Warning: Please consider removing all config variables of the old
packetfilter section from your config file to avoid any
confusion.
Error in configuration, aborting...
hit RETURN to continue ...
The build of fli4l returned an error!
Press ENTER to continue