Did anybody have success in setting up xen 3.0.2-2 with a newer kernel than 2.6.16? I ran into the same LVM problems as mentioned before on this list (not being able to lvremove a snapshot). Now I''m trying to get the 2.6.18 running from the fedora repository ( http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora ) but I didn''t have any success so far. The xen hypervisor binary tries to load the kernel, fails and performs an automatic reboot. Does anybody know where to get some documentation on this or has any experience with the fedora kernels? I''ll give the other repository (linux-2.6.17-xen) a try later; maybe that''ll work out better for me. -- Mit freundlichen Gruessen / with kind regards Rudolph Bott ------------------------------------------------------------------- Megabit Informationstechnik GmbH Karstr.25 41068 Moenchengladbach Tel: 02161/308980 mailto:info@megabit.net ftp://megabit.net Fax: 02161/3089818 mailto:support@megabit.net http://megabit.net ------------------------------------------------------------------- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I''ve tried running 2.6.17 packed up with FC5 but it just doesn''t seem stable for me. I''m running a compiled 2.6.16 from the Xen-3.0.2 base. I wish it were stable; but noone from the FC project seems to have jumped on my bug/email. Adrian On Tue, Sep 19, 2006, Rudolph Bott wrote:> > Did anybody have success in setting up xen 3.0.2-2 with a newer kernel > than 2.6.16? I ran into the same LVM problems as mentioned before on > this list (not being able to lvremove a snapshot). > > Now I''m trying to get the 2.6.18 running from the fedora repository ( > http://hg.et.redhat.com/kernel/linux-2.6-xen-fedora ) but I didn''t have > any success so far. The xen hypervisor binary tries to load the kernel, > fails and performs an automatic reboot. > > Does anybody know where to get some documentation on this or has any > experience with the fedora kernels? > > I''ll give the other repository (linux-2.6.17-xen) a try later; maybe > that''ll work out better for me. > > -- > Mit freundlichen Gruessen / with kind regards > Rudolph Bott > > ------------------------------------------------------------------- > Megabit Informationstechnik GmbH Karstr.25 41068 Moenchengladbach > Tel: 02161/308980 mailto:info@megabit.net ftp://megabit.net > Fax: 02161/3089818 mailto:support@megabit.net http://megabit.net > ------------------------------------------------------------------- > > _______________________________________________ > 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
On Tuesday 19 September 2006 11:16 am, Rudolph Bott wrote:> Did anybody have success in setting up xen 3.0.2-2 with a newer kernel > than 2.6.16? I ran into the same LVM problems as mentioned before on > this list (not being able to lvremove a snapshot).I''m running SUSE''s 2.6.18_rc6_git3 and xen-3.0.3_11440-3 just fine. LVM and HVM are working. -- James Oakley Engineering - SolutionInc Ltd. joakley@solutioninc.com http://www.solutioninc.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Am Dienstag, den 19.09.2006, 12:21 -0300 schrieb James Oakley:> I''m running SUSE''s 2.6.18_rc6_git3 and xen-3.0.3_11440-3 just fine. LVM and > HVM are working.I''ve been running 2.6.18-rc3 and -rc6 with the Fedora patch and the XEN-Hypervisor and XEN-Tools from the xen-unstable tarballs (from about the same date, 0815 and 0915). While it all usually worked well, I''ve seem some strange things sometimes. After a domain crash or some manual destroys, xm suddenly told me "Domain 0 not connected". After a restart of xend, "xm list" worked again, but any further "xm create" would fail with "hotplug not working" (for the vif device). I also had some undestroyed vif devices from destroyed domains dangling around. I don''t see how hotplug (or udev to be precicse) should suddenly fail. And what is "Domain 0 not connected" about? It seems like something suddenly forgot its state and really got confused. The vif devices should have been destroyed by xend and not hotplug, right? The only way to "fix" the problem was to reboot the machine. Has anybody else seen something like that? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Sep 19, 2006, Christophe Saout wrote:> XEN-Hypervisor and XEN-Tools from the xen-unstable tarballs (from about > the same date, 0815 and 0915). While it all usually worked well, I''ve > seem some strange things sometimes. > > After a domain crash or some manual destroys, xm suddenly told me > "Domain 0 not connected". After a restart of xend, "xm list" worked > again, but any further "xm create" would fail with "hotplug not > working" (for the vif device). I also had some undestroyed vif devices > from destroyed domains dangling around. > > I don''t see how hotplug (or udev to be precicse) should suddenly fail. > And what is "Domain 0 not connected" about? It seems like something > suddenly forgot its state and really got confused. The vif devices > should have been destroyed by xend and not hotplug, right? > > The only way to "fix" the problem was to reboot the machine. Has anybody > else seen something like that?Yeah - my 2.6.17 paravirt kernels from FC5 will crash (and I didn''t get a stack trace when this happened, but I will next time!) and they''ll actually take the networking for all other xen''s down with them. xm shutdown will successfully shut the domU environment down but it''ll zombie the kernel instead of cleanly destroying the domain. I have to reboot to recover. restarting xend doesn''t do anything (and I haven''t checked the logs to see what it failed to do, save being unable to destroy domains..) Its a bit weird that a domU crashing can take out everything else. I''d hate to find someone reliably replicating it and using it as a DoS.. :/ Adrian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Am Dienstag, den 19.09.2006, 23:43 +0800 schrieb Adrian Chadd:> On Tue, Sep 19, 2006, Christophe Saout wrote: > > > XEN-Hypervisor and XEN-Tools from the xen-unstable tarballs (from about > > the same date, 0815 and 0915). While it all usually worked well, I''ve > > seem some strange things sometimes. > > > > After a domain crash or some manual destroys, xm suddenly told me > > "Domain 0 not connected". After a restart of xend, "xm list" worked > > again, but any further "xm create" would fail with "hotplug not > > working" (for the vif device). I also had some undestroyed vif devices > > from destroyed domains dangling around. > > > > I don''t see how hotplug (or udev to be precicse) should suddenly fail. > > And what is "Domain 0 not connected" about? It seems like something > > suddenly forgot its state and really got confused. The vif devices > > should have been destroyed by xend and not hotplug, right? > > > > The only way to "fix" the problem was to reboot the machine. Has anybody > > else seen something like that? > > Yeah - my 2.6.17 paravirt kernels from FC5 will crash (and I didn''t get > a stack trace when this happened, but I will next time!) and they''ll > actually take the networking for all other xen''s down with them.That''s exactly what happened the first time. I don''t know why. After three weeks without problems this suddenly happened on two different physical machines almost at the same time and once again four hours later. I then upgraded to the 2.6.18-rc6 patch and newest hypervisor and tools, hoping that this was a bug and had been fixed. While I didn''t observe it crashing by itself (well, I updated just two days ago), I saw the phenomenon again after having destroyed all guest domains manually.> xm shutdown will successfully shut the domU environment down but it''ll > zombie the kernel instead of cleanly destroying the domain. > I have to reboot to recover. restarting xend doesn''t do anything > (and I haven''t checked the logs to see what it failed to do, save > being unable to destroy domains..)I haven''t seen anything suspicious in the logs either. Just that a domain had crashed, xend having trouble restarting it until it decided to abort, and then other domains suddenly crashing as well or staying around as zombies without network connection (still accessible via console).> Its a bit weird that a domU crashing can take out everything else. > I''d hate to find someone reliably replicating it and using it as a > DoS.. :/Do you know if this problem is known? Is there a Bugzilla bug somewhere? Is it specific to post-2.6.16.x ports? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 9/19/06, Rudolph Bott <rb@megabit.net> wrote:> > Did anybody have success in setting up xen 3.0.2-2 with a newer kernel > than 2.6.16?In general it is problematic to run unmatching combinations of xen an linux-xen and combina them at random. Still, some messages on this list (you have to look them up in the archive) said that it''s O.K. in some directions and combinations. Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Am Dienstag, den 19.09.2006, 23:43 +0800 schrieb Adrian Chadd:> Yeah - my 2.6.17 paravirt kernels from FC5 will crash (and I didn''t get > a stack trace when this happened, but I will next time!) and they''ll > actually take the networking for all other xen''s down with them. > > xm shutdown will successfully shut the domU environment down but it''ll > zombie the kernel instead of cleanly destroying the domain. > I have to reboot to recover. restarting xend doesn''t do anything > (and I haven''t checked the logs to see what it failed to do, save > being unable to destroy domains..) > > Its a bit weird that a domU crashing can take out everything else. > I''d hate to find someone reliably replicating it and using it as a > DoS.. :/After some digging through bugzilla, I saw several reports for this, and someone then left a hint, and I think I''ve identified the bug as: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=199944 The crash has been fixed some days ago in the development version (which I can possibly confirm as I haven''t seen a crash with the new version... yet). Unfortunately, it seems that a malicious user breaking in and gaining root rights on a XenU machine could still take down the whole networking (by messing around on the evtchn?). Xen should really be robust against any weird DomU behaviour in critical hypervisor/guest kernel code. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users