I''ve just upgraded a machine to debian ''etch'', and seem to be using gcc 4.0.1. Are there any known incompatibilities between gcc 4.0.1 and xen? The kernel seems to compile okay (lots of new warnings though), but xen just reboots. I seem to be able to use an older xen with the newly compiled kernel successfully. Alternatively, are there any known problems with the latest xen-unstable (4 days old to present)? Thanks James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 25 Sep 2005, at 08:26, James Harper wrote:> I''ve just upgraded a machine to debian ''etch'', and seem to be using gcc > 4.0.1. Are there any known incompatibilities between gcc 4.0.1 and xen? > The kernel seems to compile okay (lots of new warnings though), but xen > just reboots. I seem to be able to use an older xen with the newly > compiled kernel successfully. > > Alternatively, are there any known problems with the latest > xen-unstable > (4 days old to present)?gcc 4.0.0 has worked for me, except for some non-fatal crashes in the proc filesystem during boot (these crashes aren''t xen-specific). I haven''t tried 4.0.1. In general, unless you want to fix bugs you are better off with gcc 3.2.x, 3.3.x or 3.4.x. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> gcc 4.0.0 has worked for me, except for some non-fatal crashes in the > proc filesystem during boot (these crashes aren''t xen-specific). I > haven''t tried 4.0.1. > > In general, unless you want to fix bugs you are better off with gcc > 3.2.x, 3.3.x or 3.4.x.I tried 3.3 and 3.4 (I seem to have those installed in addition to 4.0.1... go figure!) too. 3.4 did the same thing (perpetual reboot), and 3.3 hung on reboot. I''m remote from the machine so I''ll have to wait until I drop by the office to take a look. So I guess it isn''t the gcc version after all. I wonder what else I''m doing wrong... James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> I tried 3.3 and 3.4 (I seem to have those installed in addition to > 4.0.1... go figure!) too. 3.4 did the same thing (perpetual reboot),and> 3.3 hung on reboot. I''m remote from the machine so I''ll have to wait > until I drop by the office to take a look.On closer inspection, it hasn''t actually started to boot with the gcc 3.3 compiled xen, it has instead failed to reboot from a previously working kernel, so I can''t completely rule out a gcc problem. James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 25 Sep 2005, at 11:59, James Harper wrote:> On closer inspection, it hasn''t actually started to boot with the gcc > 3.3 compiled xen, it has instead failed to reboot from a previously > working kernel, so I can''t completely rule out a gcc problem.Unless it''s a new bug fairly specific to your machine, it sounds like a setup snafu. Noone else has reported things being *that* broken. :-) -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> Unless it''s a new bug fairly specific to your machine, it sounds likea> setup snafu. Noone else has reported things being *that* broken. :-)I have finally gotten into the office to visit the machine. It had actually stopped at the bios with ''date/time not set'', but another reboot made that error go away. If I take ''noreboot'' out, I can see that xen is hanging after it scrubs the memory. Any suggestions as to where to look? Thanks James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
>> Unless it''s a new bug fairly specific to your machine, it sounds like >a >> setup snafu. Noone else has reported things being *that* broken. :-) > >I have finally gotten into the office to visit the machine. It had >actually stopped at the bios with ''date/time not set'', but another >reboot made that error go away. > >If I take ''noreboot'' out, I can see that xen is hanging after it scrubs >the memory. Any suggestions as to where to look?Are your xen and dom0 builds from the same tree? A hang or reboot at the point you mention implies something is quite screwed (e.g. incompatible notions of shared info between xen and dom0)... cheers, S. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> Are your xen and dom0 builds from the same tree? A hang or reboot at > the point you mention implies something is quite screwed (e.g. > incompatible > notions of shared info between xen and dom0)...I was sure they were the same, but I rebuilt everything and sure enough it all works now, so that was probably it. My system load sits at 1.0 at idle in both dom0 and domu, which is why I rebuilt in the first place before all of this started. Is this normal? Thanks James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel