Opened 6 years ago

Last modified 17 months ago

#10198 assigned enhancement

pxe booting should take care of package management

Reported by: oco Owned by: nobody
Priority: normal Milestone: R1
Component: System/Boot Loader Version: R1/Development
Keywords: pxe Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

Booting an image through pxe and remote_disk_server stop while looking for /bin/sh in the remote image. I have not yet fully investigate what should be done. I will probably do some more work on that, but probably not before the end of the year.

At least, the netboot archive is probably not correctly configured to load packages from the remote image.

In the meantime, hints and guidelines are welcome.

Change History (8)

comment:1 Changed 5 years ago by luroh

Blocking: 7665 added

comment:2 Changed 5 years ago by pulkomandy

Blocking: 7665 removed

PXE specific issue, not relevant to the "boot failure" ticket.

comment:3 Changed 2 years ago by axeld

Owner: changed from axeld to nobody
Status: newassigned

comment:4 Changed 17 months ago by 6foot3

Can we revisit this bug? I have recently tried this method of booting and have not met with any success. There is a fairly detailed discussion of the steps I have tried here:

https://discuss.haiku-os.org/t/pxe-booting-from-an-ubuntu-server/6660/16

comment:5 in reply to:  4 Changed 17 months ago by korli

Replying to Alan Searchwell:

Can we revisit this bug? I have recently tried this method of booting and have not met with any success. There is a fairly detailed discussion of the steps I have tried here:

Debugging PXE issues on emulation first would be recommended. For instance: http://www.saminiir.com/debugging-pxe-boot/

comment:6 Changed 17 months ago by 6foot3

I have installed VirtualBox and configured a VM with a blank hard disk to boot from the network with a serial port sending output to a file. The VM gets it's IP address from the host's DHCP server, loads the haiku boot loader and proceeds to boot haiku. I have a file of debug output from an attempt to boot a pre PM build. What do i do next?

comment:7 Changed 17 months ago by korli

I don't know with VirtualBox, but one can use gdb with qemu (-s), load images and setup breakpoints to inspect registers, memory. Do you get the reboot problem as on real hardware?

comment:8 Changed 17 months ago by 6foot3

The VM does not reboot. Trying to boot the latest build I have results in the following message from VirtualBox:

"A critical error has occurred while running the virtual machine and the machine execution has been stopped."

The last line in the associated serial output file is:

"KDiskDeviceManager::_Scan(/dev/disk)"

Using the last non PM build I have, the boot process hung with all the boot icons "lit" and the last line of serial output was:

"error starting "/boot/system/servers/launch_daemon" error = -1"

Note: See TracTickets for help on using tickets.