On Mon, Dec 19, 2016 at 10:35 AM, Stephen John Smoogen <smooge@xxxxxxxxx> wrote: > On 19 December 2016 at 10:36, John Florian <john.florian@xxxxxxxx> wrote: >> On Fri, 2016-12-16 at 15:49 -0600, Pete Travis wrote: >> >> All the DRAC/iLO/BMC systems I play with these days mount a remote ISO and >> present it as optical media. The feature is basically only used for >> emergencies where regular networking won't do, >> >> >> My co-workers use iDRAC installs for non-emergency cases. We need to ships >> servers around the world and sometimes the import laws are such a PITA >> that's easier to have the facility make the hardware purchase locally and >> then said co-workers install Fedora remotely via the DRAC. > > The iDRAC/iLO/BMC/IMM mounting systems seems to work in the same way > that the qemu uses the iso image to boot. Whatever causes 'real' > hardware to fail in certain cases does not seem to affect the remote > mounting systems or the qemu. Qemu CD/DVD device and actual optical drives should have the same dependency. I know the example case [1] it was a BIOS bug that syslinux was able to work around with an update. We'd never find such a thing unless someone runs into it with affected hardware, which did happen and that's how it ended up getting fixed in the same release cycle. Whereas a more recent problem, where both ISO file attached to a qemu cd/dvd device and also burned to an optical disk would work, but imaged using dd to a USB stick would not, was due to a missing boot.img/stage 1 bootloader. If that same ISO were attached with a qemu hard drive device instead, it too would fail. How the bootloader is located by the firmware differs depending on whether it's an optical device (El Torito provides the hint) or a disk drive, and a USB stick is treated as a disk drive. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1148087 -- Chris Murphy _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
