Re: [Xen-devel] Problem upgrading xen-unstable - Mark Williamson - com.xensource.lists.xen-devel

5 messages in com.xensource.lists.xen-develRe: [Xen-devel] Problem upgrading xen...

From	Sent On	Attachments
Ge van Geldorp	22 May 2005 14:59
Ian Pratt	23 May 2005 00:20
Ge van Geldorp	24 May 2005 01:46
Mark Williamson	24 May 2005 16:21
Ge van Geldorp	25 May 2005 03:18

Subject:	Re: [Xen-devel] Problem upgrading xen-unstable
From:	Mark Williamson (mark...@cl.cam.ac.uk)
Date:	05/24/2005 04:21:54 PM
List:	com.xensource.lists.xen-devel

try "rm -rf /usr/lib/python/xen /usr/lib/python2.*/site-packages/xen" or look at the "make unistall" target.

Thanks for your tip, unfortunately, even after trying this I still had problems with console output being garbled.

There are some more files you can try deleting (lucky you!), in addition to what Ian suggested: /usr/lib/libxc* /usr/lib/libxutil* /usr/sbin/{xcs,xend,xentrace,xencons,xm}

Just for paranoia you could delete the contents of /var/xen (you might have to recreate some directories later for Xend to work) and /etc/xen (assuming you've nothing valuable in there).

Once you've deleted all those, and the original suggestions, make mrproper in the Xen distribution (this deletes a whole load of stuff so watch out you don't blow away any files you've added). Then make world to build from scratch.

The guess I'm working with is that there's some sort of weird incompatibility crept in between two changesets in unstable, which you may have been unlucky enough to tickle. You may want to repull to get up to date, just in case it got fixed later on...

If all this doesn't help, it's a bit mysterious. What are you using for a console? xm create -c, xm console and xencons should all behave properly. If you use telnet to connect to a domain console it sometimes gets confused.

Cheers, Mark

and reinstalling Linux (does it show I have a Windows background? <g>). Then I did a fresh build of xen (only change from defaults was to config in my Ethernet card). Unfortunately, the console problem is still there. So now I'm wondering if maybe I've hit a bug in Xen. If I create a domU, "xm console" to it and run the following program a few times, most of the times it will produce the correct output, but sometimes it will garble up:

#include <stdio.h>

int main(int argc, char *argv[]) { unsigned Line, Col; char Buf[61];

for (Line = 0; Line < 10; Line++) { for (Col = 0; Col < sizeof(Buf) - 1; Col++) { Buf[Col] = '0' + (Line + Col) % 10; } Buf[sizeof(Buf) - 1] = '\0'; printf("%s\n", Buf); fflush(stdout); }

return 0; }

Correct, expected output:

012345678901234567890123456789012345678901234567890123456789 123456789012345678901234567890123456789012345678901234567890 234567890123456789012345678901234567890123456789012345678901 345678901234567890123456789012345678901234567890123456789012 456789012345678901234567890123456789012345678901234567890123 567890123456789012345678901234567890123456789012345678901234 678901234567890123456789012345678901234567890123456789012345 789012345678901234567890123456789012345678901234567890123456 890123456789012345678901234567890123456789012345678901234567 901234567890123456789012345678901234567890123456789012345678

Sometimes I see things like this:

123456789012345678901234567890123456789012345678901234567890

012345678901234567890123456789012345678901234567890123456789234567890123456 7 89012345678901234567890123456789012345678901 345678901234567890123456789012345678901234567890123456789012 456789012345678901234567890123456789012345678901234567890123 567890123456789012345678901234567890123456789012345678901234 678901234567890123456789012345678901234567890123456789012345 789012345678901234567890123456789012345678901234567890123456 890123456789012345678901234567890123456789012345678901234567 901234567890123456789012345678901234567890123456789012345678

I get the garbled output in about 1 out of 10 runs. Vi'ing a file and then pressing Ctrl-L a few times also messes up the display.

Can anyone confirm this behaviour?