java触发器linux,IDE-R - Triggering a Remote ISO boot from a linux / java environment

Hi,

The problem seems to be related to the Linux library initiating the IDE-R session, and not so much the ISO being used. (I also tried it with a 3.0.21 kernel and I'm getting the same behavior).

If I start the IDE-R session from a C# app (code based on http://communities.intel.com/community/vproexpert/blog/2010/12/02/remote-iso-launcher), where I just do the following to start an IDE-R session.

InitAMTSystem();

string floppyImage = "C:\\Users\\Davy\\Downloads\\Dos6.22.img";

string ISOImage = "C:\\Users\\Davy\\Downloads\\Memtest86_4.0a.iso";

_system.RedirectionIDER.StartIDER(ISOImage,floppyImage);

The system is able to boot fine into the memtest ISO without human intervention.

When I do the same with an IDE-R session started from a linux box (again using the same memtest ISO), I need to enter the bios and select the virtual cd device before being able to boot into memtest.

If I don't override the boot in the BIOS I get this :

Some details on how the Linux stuff is setup. I have a couple of ISOs and disk images on the linux bos using the control loopback devices :

ubuntu@ubuntu-H55N-USB3:~/Downloads$ sudo losetup -a

/dev/loop0: [0805]:9457912 (/home/ubuntu/isos/memtest86+-4.20.iso)

/dev/loop1: [0805]:9457911 (/home/ubuntu/isos/floppy.img)

/dev/loop2: [0805]:8011044 (/home/ubuntu/Downloads/Windows98.img)

/dev/loop3: [0805]:8011060 (/home/ubuntu/Downloads/Dos6.22.img)

/dev/loop4: [0805]:9457702 (/home/ubuntu/Downloads/Acronis.iso)

And I use the imrcli sample from the Intel AMT SDK to start the IDE-R session :

Options:

a. Delete Client

b. Open SOL Session

c. Open IDER Session

x. Exit

Choose an option> c

Enter user name: admin

Enter password:

Configure proxy settings? [Yes|No] no

Enter floppy device: [/dev/fd0] /dev/loop3

Enter cdrom device: [/dev/cdrom] /dev/loop0

Handling Client 192.168.1.103

IDER Session Open (Registers Enabled)