Hello. Can anyone answer my newbie questions? When i try to boot xen image it halts after string ide: Assuming 33MHz system bus... I have NVIDIA nForce2 chip and use Gentoo Linux. I looked for same problem in archives but didn''t find anything useful. What''s wrong? Is this hardware supported? With best regards, Konstantin. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
It may be some ACPI related issue that will be fixed in the not too
distant future. Try enabling debug and verbose in xen - that *might*
tell you more.
-Kip
On 5/7/05, Konstantin Selivanov <konstantin.selivanov@gmail.com>
wrote:> Hello.
>
> Can anyone answer my newbie questions? When i try to boot xen image it
> halts after string
> ide: Assuming 33MHz system bus...
>
> I have NVIDIA nForce2 chip and use Gentoo Linux. I looked for same problem
> in archives but
> didn''t find anything useful. What''s wrong? Is this
hardware supported?
>
> With best regards, Konstantin.
>
> _______________________________________________
> 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
Alas, debug mode give me nothing. Same error and same logs. Normal booting of my 2.6.11 kernel goes like this kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx kernel: NFORCE2: IDE controller at PCI slot 0000:00:09.0 kernel: NFORCE2: chipset revision 162 kernel: NFORCE2: not 100%% native mode: will probe irqs later kernel: NFORCE2: BIOS didn''t set cable bits correctly. Enabling workaround. kernel: NFORCE2: 0000:00:09.0 (rev a2) UDMA133 controller ... but if i try xen-patched 2.6.10 it says following and halt kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx I want to try 2.6.11 kernel to work with xen. Is there way to do that? Where can i get xen patches? Konstantin. On 5/8/05, Kip Macy <kip.macy@gmail.com> wrote:> > It may be some ACPI related issue that will be fixed in the not too > distant future. Try enabling debug and verbose in xen - that *might* > tell you more. > > -Kip > > On 5/7/05, Konstantin Selivanov <konstantin.selivanov@gmail.com> wrote: > > Hello. > > > > Can anyone answer my newbie questions? When i try to boot xen image it > > halts after string > > ide: Assuming 33MHz system bus... > > > > I have NVIDIA nForce2 chip and use Gentoo Linux. I looked for same > problem > > in archives but > > didn''t find anything useful. What''s wrong? Is this hardware supported? > > > > With best regards, Konstantin. > > > > _______________________________________________ > > 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
> Alas, debug mode give me nothing. Same error and same logs. Normal booting > of my 2.6.11 kernel goes like this > > kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with > idebus=xx > kernel: NFORCE2: IDE controller at PCI slot 0000:00:09.0 > kernel: NFORCE2: chipset revision 162 > kernel: NFORCE2: not 100%% native mode: will probe irqs later > kernel: NFORCE2: BIOS didn''t set cable bits correctly. Enabling workaround. > kernel: NFORCE2: 0000:00:09.0 (rev a2) UDMA133 controller > ... > > but if i try xen-patched 2.6.10 it says following and halt > > kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with > idebus=xxHrrrm. Might be fixed by the ACPI changes in the unstable tree. You could try that out - those fixes look unlikely to go into a release until 3.0 itself.> I want to try 2.6.11 kernel to work with xen. Is there way to do that? > Where can i get xen patches?The -testing and -unstable trees both use 2.6.11 by default. Cheers, Mark> Konstantin. > > On 5/8/05, Kip Macy <kip.macy@gmail.com> wrote: > > It may be some ACPI related issue that will be fixed in the not too > > distant future. Try enabling debug and verbose in xen - that *might* > > tell you more. > > > > -Kip > > > > On 5/7/05, Konstantin Selivanov <konstantin.selivanov@gmail.com> wrote: > > > Hello. > > > > > > Can anyone answer my newbie questions? When i try to boot xen image it > > > halts after string > > > ide: Assuming 33MHz system bus... > > > > > > I have NVIDIA nForce2 chip and use Gentoo Linux. I looked for same > > > > problem > > > > > in archives but > > > didn''t find anything useful. What''s wrong? Is this hardware supported? > > > > > > With best regards, Konstantin. > > > > > > _______________________________________________ > > > 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
Alliluia, it works! Thanks a lot for responses. Booting from unstable prebuild packages goes fine. Unfortunately building from source cause some errors: cpu.o(.text+0xa62): In function `bx_cpu_c::cpu_loop(int)'': : undefined reference to `xc_evtchn_send'' main.o(.text+0x59d0): In function `bx_init_main(int, char**)'': : undefined reference to `xc_interface_open'' ../memory/libmemory.a(misc_mem.o)(.text+0x3fb): In function `bx_mem_c::init_memory(int)'': : undefined reference to `xc_get_pfn_list'' ../memory/libmemory.a(misc_mem.o)(.text+0x44c): In function `bx_mem_c::init_memory(int)'': : undefined reference to `xc_map_foreign_batch'' ../memory/libmemory.a(misc_mem.o)(.text+0x4b3): In function `bx_mem_c::init_memory(int)'': : undefined reference to `xc_map_foreign_range'' collect2: ld returned 1 exit status If anyone can shed the light, i''ll be very happy :). Thanks, Konstantin. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Alliluia, it works! Thanks a lot for responses.Good news! Perhaps it''ll work on my desktop now too :-)> Booting from unstable prebuild packages goes fine. Unfortunately building > from source cause > some errors:The errors appear to be in the device model code. I''m sure it''ll get fixed but in the meantime you can do: XEN_NO_IOEMU=y make <whatever> In the repository root. Not building the ioemu package won''t matter to you, since I imagine you don''t have VT hardware (given it''s not on sale yet :-p). Cheers, Mark> cpu.o(.text+0xa62): In function `bx_cpu_c::cpu_loop(int)'': > : undefined reference to `xc_evtchn_send'' > > main.o(.text+0x59d0): In function `bx_init_main(int, char**)'': > : undefined reference to `xc_interface_open'' > > ../memory/libmemory.a(misc_mem.o)(.text+0x3fb): In function > > `bx_mem_c::init_memory(int)'': > : undefined reference to `xc_get_pfn_list'' > > ../memory/libmemory.a(misc_mem.o)(.text+0x44c): In function > > `bx_mem_c::init_memory(int)'': > : undefined reference to `xc_map_foreign_batch'' > > ../memory/libmemory.a(misc_mem.o)(.text+0x4b3): In function > > `bx_mem_c::init_memory(int)'': > : undefined reference to `xc_map_foreign_range'' > > collect2: ld returned 1 exit status > > If anyone can shed the light, i''ll be very happy :). > > Thanks, Konstantin._______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello. I had no internet access last three days, so wasn''t able to reply. Great, it fixed my problems. However, sometimes appears some instabilities. I''ll post about them some times later. In any case, thanks for support %). Konstantin. On 5/9/05, Mark Williamson <mark.williamson@cl.cam.ac.uk> wrote:> > > Alliluia, it works! Thanks a lot for responses. > > Good news! Perhaps it''ll work on my desktop now too :-) > > > Booting from unstable prebuild packages goes fine. Unfortunately > building > > from source cause > > some errors: > > The errors appear to be in the device model code. I''m sure it''ll get fixed > but in the meantime you can do: > > XEN_NO_IOEMU=y make <whatever> > > In the repository root. Not building the ioemu package won''t matter to > you, > since I imagine you don''t have VT hardware (given it''s not on sale yet > :-p). > > Cheers, > Mark > > > cpu.o(.text+0xa62): In function `bx_cpu_c::cpu_loop(int)'': > > : undefined reference to `xc_evtchn_send'' > > > > main.o(.text+0x59d0): In function `bx_init_main(int, char**)'': > > : undefined reference to `xc_interface_open'' > > > > ../memory/libmemory.a(misc_mem.o)(.text+0x3fb): In function > > > > `bx_mem_c::init_memory(int)'': > > : undefined reference to `xc_get_pfn_list'' > > > > ../memory/libmemory.a(misc_mem.o)(.text+0x44c): In function > > > > `bx_mem_c::init_memory(int)'': > > : undefined reference to `xc_map_foreign_batch'' > > > > ../memory/libmemory.a(misc_mem.o)(.text+0x4b3): In function > > > > `bx_mem_c::init_memory(int)'': > > : undefined reference to `xc_map_foreign_range'' > > > > collect2: ld returned 1 exit status > > > > If anyone can shed the light, i''ll be very happy :). > > > > Thanks, Konstantin. >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
So, from what it looks like (on my servers and the docs), all my domains get their time from DomO. Which I have setting itself through NTP, and the dom0 looks good. However, All of the domains are 1.5 seconds off, and won''t ntp themselves on, also, an identical server, all the domains are .768 seconds off (off of the server i''m ntping to) , but both domO''s are withing (.02) and seem to narrow in as NTP is supposed to. So, question is, 1) what is going on here, and 2) can anything be done about it? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, May 12, 2005 at 10:42:53AM -0700, andrew mathes wrote:> So, from what it looks like (on my servers and the docs), all my domains > get their time from DomO. Which I have setting itself through NTP, and > the dom0 looks good. However, All of the domains are 1.5 seconds off, and > won''t ntp themselves on, also, an identical server, all the domains are > .768 seconds off (off of the server i''m ntping to) , but both domO''s are > withing (.02) and seem to narrow in as NTP is supposed to. > > So, question is, 1) what is going on here, and 2) can anything be done > about it?Are you using OpenNTPD by any chance? My machines suffered from inaccurate clocks in DomU''s, even though the clock was very accurate in Dom0. Switching to regular ntpd solved this, DomU immediately used the correct time shortly after starting ntpd. -- Alex Tomkins <tomkins@darkzone.net> _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
don''t the DomU''s just get their time from DomO? Ie. ... even if they weren''t running ntp they''d always be synced with whatever DomO thought about system time? Maybe i''m way off On Thu, 12 May 2005, Alex Tomkins wrote:> On Thu, May 12, 2005 at 10:42:53AM -0700, andrew mathes wrote: >> So, from what it looks like (on my servers and the docs), all my domains >> get their time from DomO. Which I have setting itself through NTP, and >> the dom0 looks good. However, All of the domains are 1.5 seconds off, and >> won''t ntp themselves on, also, an identical server, all the domains are >> .768 seconds off (off of the server i''m ntping to) , but both domO''s are >> withing (.02) and seem to narrow in as NTP is supposed to. >> >> So, question is, 1) what is going on here, and 2) can anything be done >> about it? > Are you using OpenNTPD by any chance? > My machines suffered from inaccurate clocks in DomU''s, even though the > clock was very accurate in Dom0. Switching to regular ntpd solved this, > DomU immediately used the correct time shortly after starting ntpd. > -- > Alex Tomkins <tomkins@darkzone.net> >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 5/12/05, andrew mathes <amathes@backnine.org> wrote:> don''t the DomU''s just get their time from DomO? Ie. ... even if they > weren''t running ntp they''d always be synced with whatever DomO thought > about system time? > > Maybe i''m way off > > On Thu, 12 May 2005, Alex Tomkins wrote: > > > On Thu, May 12, 2005 at 10:42:53AM -0700, andrew mathes wrote: > >> So, from what it looks like (on my servers and the docs), all my domains > >> get their time from DomO. Which I have setting itself through NTP, and > >> the dom0 looks good. However, All of the domains are 1.5 seconds off, and > >> won''t ntp themselves on, also, an identical server, all the domains are > >> .768 seconds off (off of the server i''m ntping to) , but both domO''s are > >> withing (.02) and seem to narrow in as NTP is supposed to. > >> > >> So, question is, 1) what is going on here, and 2) can anything be done > >> about it? > > Are you using OpenNTPD by any chance? > > My machines suffered from inaccurate clocks in DomU''s, even though the > > clock was very accurate in Dom0. Switching to regular ntpd solved this, > > DomU immediately used the correct time shortly after starting ntpd. > > -- > > Alex Tomkins <tomkins@darkzone.net>Andrew, Please remember, you allways shoult treat each virtual machine like a completely separated host! So far, you shoul configure ntpd to get time from -possibly- the same host as you dom0 is getting time. Try that. It won''t hurt :) And I bet you will feel happy with the result :) -- Bye, Fernando Maior LPIC/1 31908 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
yeah, i''m already doing that, I was just saying, it *seemed* like they were getting their time from domain0, and weren''t actually changing their own clocks in accordance with syncing with the same ntpd server. especially since they''re all off by exactly the same amount ... and running ntpdate doesn''t seem to have any effect whatsoever? On Thu, 12 May 2005, Fernando Maior wrote:> On 5/12/05, andrew mathes <amathes@backnine.org> wrote: >> don''t the DomU''s just get their time from DomO? Ie. ... even if they >> weren''t running ntp they''d always be synced with whatever DomO thought >> about system time? >> >> Maybe i''m way off >> >> On Thu, 12 May 2005, Alex Tomkins wrote: >> >>> On Thu, May 12, 2005 at 10:42:53AM -0700, andrew mathes wrote: >>>> So, from what it looks like (on my servers and the docs), all my domains >>>> get their time from DomO. Which I have setting itself through NTP, and >>>> the dom0 looks good. However, All of the domains are 1.5 seconds off, and >>>> won''t ntp themselves on, also, an identical server, all the domains are >>>> .768 seconds off (off of the server i''m ntping to) , but both domO''s are >>>> withing (.02) and seem to narrow in as NTP is supposed to. >>>> >>>> So, question is, 1) what is going on here, and 2) can anything be done >>>> about it? >>> Are you using OpenNTPD by any chance? >>> My machines suffered from inaccurate clocks in DomU''s, even though the >>> clock was very accurate in Dom0. Switching to regular ntpd solved this, >>> DomU immediately used the correct time shortly after starting ntpd. >>> -- >>> Alex Tomkins <tomkins@darkzone.net> > > Andrew, > > Please remember, you allways shoult treat each virtual machine > like a completely separated host! So far, you shoul configure ntpd > to get time from -possibly- the same host as you dom0 is getting > time. Try that. It won''t hurt :) And I bet you will feel happy with > the result :) > > -- > Bye, > Fernando Maior > LPIC/1 31908 > > _______________________________________________ > 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