On 11/16/2015 12:44 PM, Richard Weinberger wrote: > Am 16.11.2015 um 10:43 schrieb Vegard Nossum: >> Starting UML like this: >> >> ./vmlinux rootfstype=hostfs rw ignore_console_loglevel con=xterm >> init=/bin/bash >> >> Results in unpredictable behaviour, most of the time an xterm flashes on >> my screen but the process aborts with only "Aborted" on the console >> where I ran the command, sometimes the xterm remains there but frozen, >> sometimes the xterm spews this warning non-stop: > > Hmm, is this a new regression? > I bet it only happens with con=xterm, right?
It's the first UML kernel I compile in a few years, so I don't know if it's old or new, sorry. Yes, only con=xterm triggers this. (For the record, I also couldn't con=pty or con=pts to work either, it just results in "Aborted." on the console where I ran ./vmlinux -- if I try con1=pty or con1=pts it boots normally, but there is no message in the kernel log indicating the host device that was used for the console. But this could be a PEBKAC, I only mention it in case it might be relevant. Also, normal ./vmlinux without any con*= arguments works fine, but I only get the plain stdin/stdout console.) Thanks, Vegard ------------------------------------------------------------------------------ Presto, an open source distributed SQL query engine for big data, initially developed by Facebook, enables you to easily query your data on Hadoop in a more interactive manner. Teradata is also now providing full enterprise support for Presto. Download a free open source copy now. http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140 _______________________________________________ User-mode-linux-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
