I''ve been working on a xen-unstable tree from mid-April. I wanted to upgrade to the latest version, so here is what I did: - Clone a fresh copy of xeno-unstable.bk (1.1507) - "make world" - Change the .config of linux-2.6.11-xen0 to include my ethernet card (CONFIG_FORCEDETH=y) - Add localversion files to linux-2.6.11-xen0 and linux-2.6.11-xenU - rm -rf the existing dist directory - "make kernels" - "make dist" - Tar the dist directory (plus subdirectories), transfer the tar file to the destination dom0 and untar there - On the destination dom0, cd into the dist directory and "./install.sh" - Reboot I''m now seeing a lot of problems which all seem to be related to xend. When running "xm console mydomU" on dom0, output is garbled. Shutting down or destroying a domain using xm frequently results in the domain still being listed by "xm list", although with a 0 memory size. After recreating a domain in that state, "xm list" will show two lines with the same domid (but the domain won''t get created). My guess is I messed something up during the upgrade. I just can''t figure out what... All help appreciated, Gé van Geldorp. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> I''ve been working on a xen-unstable tree from mid-April. I > wanted to upgrade to the latest version, so here is what I did: > > - Clone a fresh copy of xeno-unstable.bk (1.1507) > - "make world" > - Change the .config of linux-2.6.11-xen0 to include my ethernet card > (CONFIG_FORCEDETH=y) > - Add localversion files to linux-2.6.11-xen0 and linux-2.6.11-xenU > - rm -rf the existing dist directory > - "make kernels" > - "make dist" > - Tar the dist directory (plus subdirectories), transfer the > tar file to the destination dom0 and untar there > - On the destination dom0, cd into the dist directory and > "./install.sh" > - RebootI''m guessing that this is due to you having an old version of the tools on your search path (the default location was changed). try "rm -rf /usr/lib/python/xen /usr/lib/python2.*/site-packages/xen" or look at the "make unistall" target. Ian> I''m now seeing a lot of problems which all seem to be related > to xend. When running "xm console mydomU" on dom0, output is > garbled. Shutting down or destroying a domain using xm > frequently results in the domain still being listed by "xm > list", although with a 0 memory size. After recreating a > domain in that state, "xm list" will show two lines with the > same domid (but the domain won''t get created). > > My guess is I messed something up during the upgrade. I just > can''t figure out what... > > All help appreciated, Gé van Geldorp. > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> From: Ian Pratt [mailto:m+Ian.Pratt@cl.cam.ac.uk] > > I''m guessing that this is due to you having an old version of > the tools on your search path (the default location was changed). > > 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. So, I ended up blowing away the root partition on my domU 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 0123456789012345678901234567890123456789012345678901234567892345678901234567 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? Gé van Geldorp. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/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? > > Gé van Geldorp. > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> From: Mark Williamson > > 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.I ended up trying a fresh Linux install in dom0, including mkfs()''ing the filesystem. So all traces of the previous Xen should be gone in dom0. I rebuilt Xen from scratch and installed it in this new filesystem. All problems I saw before were gone, except for the console problem.> 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.I''ve done it in two ways: log into dom0 on the physical console, then use "xm create -c" to create the domU and watch it. The other way was to ssh (from a Windows box, using PuTTy) into dom0 and then use "xm create -c" again. Ending the initial domU console session and reattaching using "xm console" gives the same result. Since I seem the only one having this problem it must be something I''m doing wrong. I guess it''s time for me to dig into xend. Gé van Geldorp. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel