Hi,
I've seen this happen with both iPXE and GRUB now.
For example if I load tboot+linux like this in GRUB:
multiboot boot/tboot.gz logging=vga,serial,memory
module boot/Ubuntu-TXT-16.04-x86_64-linux interface=auto
url=http://something.somewhere ramdisk_size=10800 root=/dev/rd/0 rw auto
hostname=test BOOTIF=${net_pxe_mac} console-setup/ask_detect=false
console-setup/layout=USA console-setup/variant=USA
keyboard-configuration/layoutcode=us localechooser/translation/warn-light=true
localechooser/translation/warn-severe=true locale=en_US brm
module boot/Ubuntu-TXT-16.04-x86_64-initrd.gz
System loads fine, but /proc/cmdline contains ~20 characters of random garbage
appended to the original cmdline contents.
I first saw it wheb trying to load Foreman Discovery Image - a ramdisk based on
CentOS 7.
I decided to ignore it then and switched to GRUB, this fixed booting the
Discovery Image (no /cmdline corruption).
Next step is provisioning = booting Ubuntu preseed, and /proc/cmdline is
corrupted there now.
So I'm pretty sure that it is tboot corrupting the cmdline (is it terminated
differently in PXE environment? Some padding needed?)
I'm not sure how reproducible it is. While I can trigger it every time in those
combinations, apparently with some modules it boots fine (because FDI boots
fine...)
Has anybody encountered this before? Any PXE users here?
Thanks
Jan
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
tboot-devel mailing list
tboot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tboot-devel
