This was reported on the forums too:
http://ubuntuforums.org/showthread.php?t=2215103 where directhex2
mentioned:
I've tracked down the problem to a change in debian-installer-utils 1.98
Looking at the changelog
(https://launchpad.net/ubuntu/saucy/+source/debian-installer-utils/+
I have a feisty host that has X running. From an ssh session into that machine
I run xen-tools's xen-create-image to creating a feisty domU.
When that runs debootstrap (in the host, not the guest), and installs
console-setup, that corrupts video ram on X. I image the same thing could
happen if y
This just bit me too. One of the xen-tools shell scripts does an "rm tty[^1]",
to remove all ttys except tty1, which works in bash, but in dash the result is
the opposite: tty1 is removed, and none of the others are.
This silent mis-behaviour then later means you cannot log into your
newly-creat
