Comment 6 for bug 93338

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 you run debootstrap for a chroot setup, but have not tested that.

Perhaps console-setup should use "pidof X" instead of checking $DISPLAY? I think that would have helped Simonics too.

But I imagine the real problem here is that console-setup runs from the debootstrap, affecting the host instead of the target. Please advise.