Hi Norman,
-----Ursprüngliche Nachricht----- From: Norman Feske Sent: Friday, May 2, 2014 11:33 AM To: genode-main@lists.sourceforge.net Subject: Re: Booting genode/nova
For testing, it is very helpful to have Genode's LOG output available, which is directed to the comport. Unfortunately, modern PCs don't have a comport anymore. However, on most Intel-based PCs, there exists a feature called AMT that allows for sending comport output over the network. If you are interested in exploring this, it is worthwhile to search for 'amtterm'.
Finally got the x201 you supposed and tried to configure amt.
I tried the following: on the x201 enable AMT, setup a new user wolfgang with password and enable SOL. I set a IP4 adress of 10.1.1.2. With the username and password i can log into the AMT web site of the computer.
On a hp i tried the commands from http://genode.org/documentation/release-notes/13.05 (On the client i installed amtterm 1.3 from repository.) export AMT_TEST_MACHINE_IP=10.1.1.2 export AMT_TEST_MACHINE_PWD=Test$$44$$ (yep i know, but the machine cannot connect to the outside world)
and tried RUN_OPT="--target amt" make run/printf
The x201 does not seem to get touched - even with disconnected network cable the test is succesful.
I honestly does not understand amt. I tried to use amtterm instead to try out the connection. With amtterm i get a "amtterm: AUTH - ERROR (failure) amtterm: ERROR: session authentification failed". I know that amtterm has nothing to do with genode directly, but if you are using it could you give a hint for the right direction?
Best regards, Wolfgang
Hi,
On 15.06.2014 20:07, w_schmidt@...181... wrote:
I tried the following: on the x201 enable AMT, setup a new user wolfgang with password and enable SOL. I set a IP4 adress of 10.1.1.2. With the username and password i can log into the AMT web site of the computer.
Good.
On a hp i tried the commands from http://genode.org/documentation/release-notes/13.05 (On the client i installed amtterm 1.3 from repository.) export AMT_TEST_MACHINE_IP=10.1.1.2 export AMT_TEST_MACHINE_PWD=Test$$44$$ (yep i know, but the machine cannot connect to the outside world)
and tried RUN_OPT="--target amt" make run/printf
The x201 does not seem to get touched - even with disconnected network cable the test is succesful.
This looks like that the run script doesn't recognize that you wanted to use Intel's AMT. Can you please have a look (or post the log) in the log for something like "No support for Intel's AMT detected."
I honestly does not understand amt. I tried to use amtterm instead to try out the connection. With amtterm i get a "amtterm: AUTH - ERROR (failure) amtterm: ERROR: session authentification failed". I know that amtterm has nothing to do with genode directly, but if you are using it could you give a hint for the right direction?
Make sure that you also have enabled in the AMT menu an option called "Legacy redirection mode" - without we had no luck to get SOL working and that you "active the network p
The best is first to try and to get the amttool and amtterm working in general. For example try
user> AMT_PASSWORD=<your password> amttool 10.1.1.2 powerup user> AMT_PASSWORD=<your password> amttool 10.1.1.2 reset user> AMT_PASSWORD=<your password> amttool 10.1.1.2 powerdown
in a shell. If this works our run script support should be able to reset the machine (we use only "reset" - so you have to power on the machine by your own before using it.)
If this works amtterm can be invoked by
user> amtterm 10.1.1.2 -u admin -p <your password>
and should give you a connection.
Cheers,
Alex B.
Hello Wolfgang,
On Sun, Jun 15, 2014 at 08:07:59PM +0200, w_schmidt@...181... wrote:
export AMT_TEST_MACHINE_IP=10.1.1.2 export AMT_TEST_MACHINE_PWD=Test$$44$$ (yep i know, but the machine cannot
Could you please try a more simple password like "Test!4" without the quotes. It may be, that the $$44$$ is interpreted by your shell. My shell behaves like follows
me@...246...:~> export FOO=Test$$44$$; echo $FOO Test198734419873
It seems the shell properly expands $$ (from bash.info)
`$' Expands to the process ID of the shell. In a `()' subshell, it expands to the process ID of the invoking shell, not the subshell.
To prevent variable expansion in bash you may also wrap your string with single quotes '
Greets
Hi,
Still no luck.
what is meant with "active the network p"?
I have linked both machines directly with fixed ips.
I enabled the following settings on the x201: Username&Password (also tried to disable it, but no change), SOL, IDER, Legacy Redirection Mode, KVM,
AMT_PASSWORD=<your password> amttool 10.1.1.2 info gave only: '401 Unauthorized at /usr/bin/amttool line 126' AMT_PASSWORD=Test4ls! echo $AMT_PASSWORD showed nothing.
In a root console i can set and get with echo the passwort.
But also in root console it fails with same error.
I looked in the AMTTOOL script. In the script i changed the user to the one i created in the web ui. Also nothing changed.
Funnily i can do the following:
amtterm 10.1.1.2 -u admin -p 'verysecretpasswortNarf!' or amtterm 10.1.1.2 -u specialuser -p 'Test4ls!'
this says that redirection is okay. So username seems to be correct, but there is no conenction with amttool
Oh, and it does not work if i enter the paswort manually, only with quotes and parameter -p.
At the moment I'm a little bit frustrated by AMT.
Finally the following worked to get the amttool working: I har coded the passowrd in the AMTTOOL script. Security at it's best...
So thanks for the direction. The thing with the script i try over the long weekend.
Best regards, Wolfgang
-----Ursprüngliche Nachricht----- From: Alexander Boettcher Sent: Monday, June 16, 2014 9:08 AM To: genode-main@lists.sourceforge.net Subject: Re: Fw: Booting genode/nova
Hi,
On 15.06.2014 20:07, w_schmidt@...181... wrote:
I tried the following: on the x201 enable AMT, setup a new user wolfgang with password and enable SOL. I set a IP4 adress of 10.1.1.2. With the username and password i can log into the AMT web site of the computer.
Good.
On a hp i tried the commands from http://genode.org/documentation/release-notes/13.05 (On the client i installed amtterm 1.3 from repository.) export AMT_TEST_MACHINE_IP=10.1.1.2 export AMT_TEST_MACHINE_PWD=Test$$44$$ (yep i know, but the machine cannot connect to the outside world)
and tried RUN_OPT="--target amt" make run/printf
The x201 does not seem to get touched - even with disconnected network cable the test is succesful.
This looks like that the run script doesn't recognize that you wanted to use Intel's AMT. Can you please have a look (or post the log) in the log for something like "No support for Intel's AMT detected."
I honestly does not understand amt. I tried to use amtterm instead to try out the connection. With amtterm i get a "amtterm: AUTH - ERROR (failure) amtterm: ERROR: session authentification failed". I know that amtterm has nothing to do with genode directly, but if you are using it could you give a hint for the right direction?
Make sure that you also have enabled in the AMT menu an option called "Legacy redirection mode" - without we had no luck to get SOL working and that you "active the network p
The best is first to try and to get the amttool and amtterm working in general. For example try
user> AMT_PASSWORD=<your password> amttool 10.1.1.2 powerup user> AMT_PASSWORD=<your password> amttool 10.1.1.2 reset user> AMT_PASSWORD=<your password> amttool 10.1.1.2 powerdown
in a shell. If this works our run script support should be able to reset the machine (we use only "reset" - so you have to power on the machine by your own before using it.)
If this works amtterm can be invoked by
user> amtterm 10.1.1.2 -u admin -p <your password>
and should give you a connection.
Cheers,
Alex B.
------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hi Christian,
thanks, Test4! is to short for passwort policy of AMT. longer has also not worked. amtterm now works with -p and passwort in paraprasses (like -p 'Test4!4!')
Nunja. Ãber Fronleichnam probiere ich das weiter.
Best regards, Wolfgang
-----Ursprüngliche Nachricht----- From: Christian Helmuth Sent: Monday, June 16, 2014 9:10 AM To: Genode OS Framework Mailing List Subject: Re: Fw: Booting genode/nova
Hello Wolfgang,
On Sun, Jun 15, 2014 at 08:07:59PM +0200, w_schmidt@...181... wrote:
export AMT_TEST_MACHINE_IP=10.1.1.2 export AMT_TEST_MACHINE_PWD=Test$$44$$ (yep i know, but the machine cannot
Could you please try a more simple password like "Test!4" without the quotes. It may be, that the $$44$$ is interpreted by your shell. My shell behaves like follows
me@...246...:~> export FOO=Test$$44$$; echo $FOO Test198734419873
It seems the shell properly expands $$ (from bash.info)
`$' Expands to the process ID of the shell. In a `()' subshell, it expands to the process ID of the invoking shell, not the subshell.
To prevent variable expansion in bash you may also wrap your string with single quotes '
Greets
Hello Wolfgang,
On Tue, Jun 17, 2014 at 08:47:01PM +0200, w_schmidt@...181... wrote:
Nunja. Über Fronleichnam probiere ich das weiter.
Ich wünsche Dir viel Erfolg ,-)
Regards
Hi,
Following now works - restart with amttool.
Also RUN_OPT="--target amt" make run/printf now seems to try to connect to remote pc.
Nevertheless the simple printf fails. (output attached below inline.)
It seems like remote machine gets connected, restarts. Afterwards it boots normally. In the output file there are two lines amtterm: RUN_SOL -> ERROR (failure) amtterm: ERROR: redir_data: unknown r->buf 0x29 After I read http://osdir.com/ml/general/2012-07/msg20818.html it seems like expected that SOL breaks over reboot. It also seems that the genode script tries to connect shortly afterwards. amtterm: CONNECT -> INIT (redirection initialization) the thing is,that the other computer boots its os while the script is still running and does not seem to boot genode over lan. I also tried to change the boot sequence of the x201 to LAN/CD/HARDDISC.
Should it work in that way or is something additional needed.
---
I also tried the following: - I created a partition with genode on the x201 where the demo boots from. - from first I triggered RUN_OPT="--target amt" make run/demo - on the x201 i manually selcted the genode demo in grub and started it. On the first pc the last output which is seen is: serial-over-lan redirection ok connected now, use ^] to escape And nothing afterwards.
If this works amtterm can be invoked by user> amtterm 10.1.1.2 -u admin -p <your password> and should give you a connection.
Must something be configured while building a genode/nova system so that output COM3 is used?
Best regards, Wolfgang
building targets: core init test/printf spawn make core init test/printf make[1]: Betrete Verzeichnis '/home/wolfgang/genrep/build.cc' checking library dependencies... Library platform Library cxx Library syscall Library startup Library base-common Library base Library init_pd_args Library config Program init/init Program test/printf/test-printf Program core/core COMPILE version.o LINK core make[1]: Verlasse Verzeichnis '/home/wolfgang/genrep/build.cc' genode build completed using NOVA kernel at /home/wolfgang/genrep/build.cc/kernel/hypervisor creating ISO image... Warning: -follow-links does not always work correctly; be careful. Size of boot image is 4 sectors -> No emulation Total translation table size: 2048 Total rockridge attributes bytes: 2066 Total directory bytes: 8192 Path table size(bytes): 64 Max brk space used 1b000 1508 extents written (2 MB) spawn amttool 10.1.1.2 reset host x201me., reset [y/N] ? y execute: reset result: pt_status: successspawn amtterm -u admin -p Test4ls! -v 10.1.1.2 amtterm: NONE -> CONNECT (connection to host) ipv4 10.1.1.2 [10.1.1.2] 16994 open amtterm: CONNECT -> INIT (redirection initialization) amtterm: INIT -> AUTH (session authentication) amtterm: AUTH -> INIT_SOL (serial-over-lan initialization) amtterm: INIT_SOL -> RUN_SOL (serial-over-lan active) serial-over-lan redirection ok connected now, use ^] to escape amtterm: RUN_SOL -> ERROR (failure) amtterm: ERROR: redir_data: unknown r->buf 0x29 spawn amtterm -u admin -p Test4ls! -v 10.1.1.2 amtterm: NONE -> CONNECT (connection to host) ipv4 10.1.1.2 [10.1.1.2] 16994 open amtterm: CONNECT -> INIT (redirection initialization) amtterm: INIT -> AUTH (session authentication) amtterm: AUTH -> INIT_SOL (serial-over-lan initialization) amtterm: INIT_SOL -> RUN_SOL (serial-over-lan active) serial-over-lan redirection ok connected now, use ^] to escape xð~xð~Error: Test execution timed out make: *** [run/printf] Fehler 254
Hello,
On 20.06.2014 21:08, w_schmidt@...181... wrote:
I also tried the following:
- I created a partition with genode on the x201 where the demo boots from.
- from first I triggered RUN_OPT="--target amt" make run/demo
- on the x201 i manually selcted the genode demo in grub and started it.
On the first pc the last output which is seen is: serial-over-lan redirection ok connected now, use ^] to escape And nothing afterwards.
If this works amtterm can be invoked by user> amtterm 10.1.1.2 -u admin -p <your password> and should give you a connection.
Must something be configured while building a genode/nova system so that output COM3 is used?
We use 'bender' part of 'morbo'[0] which detects at runtime the I/O ports of the Intel/AMT SOL device on the target x201 machine and reports it via the BDA (BIOS data area) to the Nova kernel and Genode's 'core'. So there is no need to configure something manually.
To sanity check this - you may comment out everything beside 'bender' in the grub menu.lst respectively in the pulsar config file (see repos/base-nova/run/env - there the files get generated). Then you should see on the x201 display the output of bender - hopefully - reporting about a serial device and the respective I/O ports.
By any chance - can you check that you have the latest BIOS version of the x201 installed? We use 1.40 and updated all our x201 test boxes accordingly.
From you description it sounds like that you close to be done. If nothing helps you may also try some newer versions of the amttools [1] - according to the changelog they fixed some issues. However, we at Genode use until now just version 1.3 with no major problems so far.
Hope it helps - good look,
Alex B.
[0] https://github.com/TUD-OS/morbo [1] http://sourceforge.net/projects/amttool-tng/files/1.7
HI,
somehow can't read your email offline. Therefore no quotation.
I originally updated both the BIOS and the AMT Firmware of the x201 because without the update some of the menus where only shown as not available. The BIOS version is 1.40 (6QET70WW) (2012-10-11) with embedded controller 1.15 and Boot agent 1.3.51 / PXE-2.1 089. The IME BIOS version is 6.1.0.006 / ME 6.2.60.1066
To sanity check this - you may comment out everything beside 'bender' in the grub menu.ls
Maybe that is the core of the problem. I have no bender in the grub entry.
On the x201 I have ubuntu12.04 with grub2. I tired to use the menu.lst which was in var/run/demo/boot/grub/menu.lst, but it hasn't worked. (and as the "legacy/classic mode seems to made problems, i decided to create a grub 2 entry.)
Therefore i created an boot entry for grub2 for genode like :
#!/bin/sh cat << EOF menuentry "Genode" { insmod ext2 multiboot /genode/hypervisor iommu serial ... } which bootet the genode demo on nova without an error.
The kernel command from grub1 is no longer supported. So I tried now : cat << EOF menuentry "Genode" { insmod ext2 linux /genode/bender multiboot /genode/hypervisor iommu serial ... }
Which results only in "invalid magic number".
Also tried things like "linux /genode/bender root=/dev/sda6" ( i put the morbo file in a /genode directory which is on sda6, root is on sda9, boot on sda5).
ATM i found no hint how to include bender in grub2. ( i found the 50_genode file from you ( http://sourceforge.net/p/genode/mailman/genode-main/?viewmonth=201211&pa... ) - also no bender) Are there files needed at a special place?
Best regards, Wolfgang
-----Ursprüngliche Nachricht----- From: Alexander Boettcher Sent: Saturday, June 21, 2014 10:57 AM To: genode-main@lists.sourceforge.net Subject: Re: Booting genode/nova
------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems
_______________________________________________ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
On 21.06.2014 18:42, w_schmidt@...181... wrote:
To sanity check this - you may comment out everything beside 'bender' in the grub menu.ls
Maybe that is the core of the problem. I have no bender in the grub entry.
Ok, than it can not work with Intel/AMT SOL automatically.
I have no bender in the grub entry.
Why not ? Whenever you invoke a run script it is added automatically to the resulting grub menu.lst respectively pulsar config file.
Without it the feature using our run script in conjunction with Intel/AMT and switching easily between different test boxes (having potentially all different I/O ports for serial devices) becomes pointless.
On the x201 I have ubuntu12.04 with grub2. I tired to use the menu.lst which was in var/run/demo/boot/grub/menu.lst, but it hasn't worked. (and as the "legacy/classic mode seems to made problems, i decided to create a grub 2 entry.)
Therefore i created an boot entry for grub2 for genode like :
#!/bin/sh cat << EOF menuentry "Genode" { insmod ext2 multiboot /genode/hypervisor iommu serial ... } which bootet the genode demo on nova without an error.
The kernel command from grub1 is no longer supported. So I tried now : cat << EOF menuentry "Genode" { insmod ext2 linux /genode/bender multiboot /genode/hypervisor iommu serial ... }
:-) - Don't make things complicated. Just stay close to the original grub menu.lst - for me works this on a recent Ubuntu 12.04 LTS grub 2 installation:
cat << EOF menuentry "Genode" { insmod ext2 multiboot /genode/bender module /genode/hypervisor module /genode/core module /genode/config config module /genode/init init ... }
and if you just want to see the output of bender :
cat << EOF menuentry "Genode" { insmod ext2 multiboot /genode/bender }
Cheers,
Alex B.
On 21.06.2014 18:42, w_schmidt@...52... wrote:
I have no bender in the grub entry.
Why not ? Whenever you invoke a run script it is added automatically to the resulting grub menu.lst respectively pulsar config file.
In this grub menu.lst bender is included. If i try to start the remote X201, the machine only gets restarted, but boots its normal os using grub2. Therefore i created an own grub2 and start the genode program manually.
Without it the feature using our run script in conjunction with Intel/AMT and switching easily between different test boxes (having potentially all different I/O ports for serial devices) becomes pointless.
Should the run script transfer code and start it automatically? On my machines it only seems to restart the other box and tries to connect to serial. That would be wonderful, ATM I 'm glad to see anything. :-)
:-) - Don't make things complicated. Just stay close to the original grub menu.lst - for me works this on a recent Ubuntu 12.04 LTS grub 2 installation:
cat << EOF menuentry "Genode" { insmod ext2 multiboot /genode/bender module /genode/hypervisor ... }
Oh, i haven't tried to make it complicated... as you may have noticed Linux &grub are something quite unfamiliar to me. So i just "translated".. okay googleed grub-kernel is now grub2 linux ... After i compiled it now for nova_x86_64 and changed to your grub2 info i can see something with amtterm.
Thanxs & Best regards, Wolfgang
Hi,
On 22.06.2014 16:00, w_schmidt@...181... wrote:
Without it the feature using our run script in conjunction with Intel/AMT and switching easily between different test boxes (having potentially all different I/O ports for serial devices) becomes pointless.
Should the run script transfer code and start it automatically? On my
Please read the chapter "Targeting real hardware via the run tool" of the 13.05 release notes [0]. In a nutshell - you may setup your network infrastructure (dhcp, tftp server) and your test machine to support booting via network. Our run tool takes care to generate and put all files in place so that they can be loaded by your test box without manual intervention. If you once successfully managed to setup this it is really really handy during for developing.
That means whatever scenario - described as a run script - you invoke on your developer machine gets loaded and started on your test machine. This even works cross platform (ARM, x86) and cross kernel (base-hw, NOVA, Fiasco.OC, OKL4, Fiasco/L4, Pistachio) if you crafted your run script carefully.
After i compiled it now for nova_x86_64 and changed to your grub2 info i can see something with amtterm.
Good :-)
Alex B.
Hi,
More informal:
i have now a dhcp & ftp server. I put configured to start pulsar as PXE.
Result - it doesn't work as expected. In more detail: I linked a /nova subdirectory to build. (or to build/nove_x86_64) in the nova directory the runscript created a link named nova_x86_64 -> the path in the config_00... is therefore wrong). I manually corrected it and linked correctly. Pulsar with PXE was still not working.
Therefore i cheated. Instead of linking i inserted in the tool/run script a rm -r nova/var and a cp to copy the correct var directory to nova/var. That worked.
Link to same directory -> boot not possible, copy of the var directory to /tftp.../nova/var-> remote system boots.
Best regards, Wolfgang
On Sun, 29 Jun 2014 21:02:48 +0200 w_schmidt@...181... (WD) wrote:
WD> Link to same directory -> boot not possible, copy of the var directory to WD> /tftp.../nova/var-> remote system boots.
Most TFTP servers use a specific "secure" directory and the sub-directories underneath it. They don't support symlinks to something outside that directory that would allow someone with write access to read or write any file they can create a symlink to.
- Udo
-
unknown＠example.com -
Alexander Boettcher -
Christian Helmuth -
Udo Steinberg