I was trying tonight to transfer a large file to one of my domU''s (from a source computer that is not part of my Xen cluster). Partway through the transfer, the domU in question crashed. See the attached file with the console output. After this console output, the domU was frozen. I did this twice, with the same outcome each time. Other domU''s on the same box continued to run just fine. I''m running Xen 3.1 / Ubuntu 7.10, kernel 2.6.22-14-xen, on an AMD Athlon XP 2700+ box with 3 GB of RAM. There were no errors of any sort logged on the dom0 at the time of the domU crash. Any ideas or suggestions? -- Rich Wales === Palo Alto, CA, USA === richw@richw.org http://www.richw.org === http://en.wikipedia.org/wiki/User:Richwales _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I posted this question earlier, but after doing so, I realized a setting on my desktop system might have caused my initial posting to be flagged (in error) as spam. So, just in case some people didn''t get my earlier e-mail, here it is again . . . . I was trying last night to transfer a large file to one of my domU''s (from a source computer that is not part of my Xen cluster). Partway through the transfer, the domU in question crashed. See the attached file containing the console output. After this console output, the domU was frozen. I did this twice, with the same outcome each time. Other domU''s on the same box continued to run just fine. I''m running Xen 3.1 / Ubuntu 7.10, kernel 2.6.22-14-xen, on an AMD Athlon XP 2700+ box with 3 GB of RAM. There were no errors of any sort logged on the dom0 at the time of the domU crash. Any ideas or suggestions? In case it matters, I did a recursive comparison of the /lib/modules files on both the "crashing" domU and another domU that runs fine, and the modules are all identical between the working and broken domU''s. -- Rich Wales === Palo Alto, CA, USA === richw@richw.org http://www.richw.org === http://en.wikipedia.org/wiki/User:Richwales _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
It appears this problem has been reported before on xen-users. Look in this list''s archives for November 2007, subject "Crashing PV DomU, Can''t find the reason". It is also the basis of an open bug in the Ubuntu bug tracking system: https://bugs.launchpad.net/bugs/156600 No one seems to have come up with a fix yet -- though one of the people who discussed it on xen-users last November said he seemed to have been able to work around the problem by abandoning Ubuntu, so it might be specifically an Ubuntu problem. Is there anyone reading this list who is successfully running Xen 3.1 on Ubuntu 7.10 (Gutsy Gibbon), in paravirtualization mode, without any random crashes or data corruption? -- Rich Wales === Palo Alto, CA, USA === richw@richw.org http://www.richw.org === http://en.wikipedia.org/wiki/User:Richwales _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yesterday, I wrote:> Is there anyone reading this list who is successfully running Xen 3.1 > on Ubuntu 7.10 (Gutsy Gibbon), in paravirtualization mode, without any > random crashes or data corruption?And today, I would add the following: Is there anyone reading this list who is successfully running Xen 3.0.x on Debian Etch, in paravirtualization mode, without any random crashes or data corruption? I brought up Debian on my test box last night, and then installed Xen from the default package (I think it was 3.0.3) -- and when I tried to transfer a large file onto the Dom0, the copy of the file on the Dom0 was corrupted -- and then shortly afterwards, the Dom0 encountered file system problems and switched the file system into read-only mode. When I repeated this experiment running straight Debian (not Xen), everything worked perfectly. As far as I''m aware, my hardware is OK -- no disk errors logged, and an extended memory test (memtest86+) has not revealed any problems. It really looks to me like there''s something wrong with Xen. Any ideas? -- Rich Wales === Palo Alto, CA, USA === richw@richw.org http://www.richw.org === http://en.wikipedia.org/wiki/User:Richwales _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Jan 16, 2008 2:36 PM, Rich Wales <richw@richw.org> wrote:> Yesterday, I wrote: > > > Is there anyone reading this list who is successfully running Xen 3.1 > > on Ubuntu 7.10 (Gutsy Gibbon), in paravirtualization mode, without any > > random crashes or data corruption? > > And today, I would add the following: > > Is there anyone reading this list who is successfully running Xen 3.0.x > on Debian Etch, in paravirtualization mode, without any random crashes > or data corruption? > > I brought up Debian on my test box last night, and then installed Xen > from the default package (I think it was 3.0.3) -- and when I tried to > transfer a large file onto the Dom0, the copy of the file on the Dom0 > was corrupted -- and then shortly afterwards, the Dom0 encountered file > system problems and switched the file system into read-only mode. When > I repeated this experiment running straight Debian (not Xen), everything > worked perfectly. > > As far as I''m aware, my hardware is OK -- no disk errors logged, and an > extended memory test (memtest86+) has not revealed any problems. It > really looks to me like there''s something wrong with Xen. Any ideas?Are you using any network block device storage such as AoE or iSCSI? Did you accidentally mount the file system read write in more than one place at a time? Did uncleaning (i.e. xm destroy) shutdown the guest? I have noticed that read-only mounting thing just the other day when a guest was imporperly shutdown (xm destroy or similar). Regards, Todd> > -- > Rich Wales === Palo Alto, CA, USA === richw@richw.org > http://www.richw.org === http://en.wikipedia.org/wiki/User:Richwales > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Todd Deshane wrote:> Are you using any network block device storage such as AoE or iSCSI?No. The one and only disk drive was a SATA drive, directly connected to the system via a Promise PCI card (and visible as /dev/sda).> Did you accidentally mount the file system read write in more than > one place at a time?No. This was the root file system, mounted automatically at boot time.> Did uncleaning (i.e. xm destroy) shutdown the guest?There weren''t any guests. What I described happened in dom0, without any domU''s running. -- Rich Wales === Palo Alto, CA, USA === richw@richw.org http://www.richw.org === http://en.wikipedia.org/wiki/User:Richwales _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users