In the last days i''ve found two heavy bugs. Is someone working on it? 1. Time stopped (Build 7398) When starting a domU the system time (in dom0) stopps for a few seconds and sometimes forever. With disabled Hyperthreading or maxcpus=1 all works fine. 2. Mounting lots of drives (Build 7398) Some device nodes (/dev/hd*) are missing in a domU. I can find in /var/log/messages an interesting thing. For all 16 configured devices i''ve found an entry like: "...xen1 logger: /etc/xen/scripts/block: bind ..." But only for 9 devices i''ve found an entry like: "...xen1 logger: /etc/xen/scripts/block: Writing backend/vbd/1/..." On the second try to start the domU i''ve found 12 "Writing backend" entries and on the third try 10 of them. If the root device (/dev/hda1) is one of them, i cannot logon to my domU. The missing /dev/hd*''s are these ones, which haven''t a "Writing backend" entry in the /var/log/messages file. Interesting thing: I had never this problem with file devices, only with lvm devices. Stephan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Thu, 2005-10-20 at 14:47 +0200, Stephan Böni wrote:> In the last days i''ve found two heavy bugs. Is someone working on it? > > 1. Time stopped (Build 7398)That''s odd. I have not seen this problem since Monday, using changesets 7396 and up.> > When starting a domU the system time (in dom0) stopps for a few > seconds and sometimes forever. With disabled Hyperthreading or > maxcpus=1 all works fine. > > 2. Mounting lots of drives (Build 7398) > > Some device nodes (/dev/hd*) are missing in a domU. I can find > in /var/log/messages an interesting thing. For all 16 configured > devices i''ve found an entry like: > "...xen1 logger: /etc/xen/scripts/block: bind ..." > But only for 9 devices i''ve found an entry like: > "...xen1 logger: /etc/xen/scripts/block: Writing backend/vbd/1/..." > On the second try to start the domU i''ve found 12 "Writing backend" > entries and on the third try 10 of them. > If the root device (/dev/hda1) is one of them, i cannot logon > to my domU. The missing /dev/hd*''s are these ones, which haven''t > a "Writing backend" entry in the /var/log/messages file. > Interesting thing: I had never this problem with file devices, only > with lvm devices. > > Stephan > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >-- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hi David> > 1. Time stopped (Build 7398) > That's odd. I have not seen this problem since Monday, using > changesets > 7396 and up.You have right. As i've tested it, it was on an older build. 7398 i've installed just later. sorry, my fault. Stephan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> 1. Time stopped (Build 7398) > > When starting a domU the system time (in dom0) stopps for a > few seconds and sometimes forever. With disabled Hyperthreading or > maxcpus=1 all works fine.Can anyone repro this? Are you using the -xen kernel config? Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian, I replied to that original message indicating that I did not see the problem anymore, since aroung changeset 7396. Stephan replied that he had been wrong, working on an older build (reply copied below). David Hi David>>> > 1. Time stopped (Build 7398) >> >> >> That''s odd. I have not seen this problem since Monday, using >> changesets >> 7396 and up. > >You have right. As i''ve tested it, it was on an older build. 7398 i''ve installed just later. sorry, my fault. Stephan Ian Pratt wrote:>>1. Time stopped (Build 7398) >> >>When starting a domU the system time (in dom0) stopps for a >>few seconds and sometimes forever. With disabled Hyperthreading or >>maxcpus=1 all works fine. >> >> > >Can anyone repro this? >Are you using the -xen kernel config? > >Ian > >_______________________________________________ >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