Boris Derzhavets
2009-Mar-16 18:21 UTC
Fw: Re: [Xen-devel] tip.git regression from "vsprintf: unify the format decoding layer for its 3 users"
>>Boris Derzhavets wrote: > >Performed:- > > > >root@ServerIntrepid:/usr/src/linux-2.6-xen# git reset --hard remotes/origin/xen/dom0/hackery > HEAD is now at a38db50 Merge commit ''tip/core/printk'' into xen/dom0/hackery > >make clean > >make >> make modules_install install > >mkinitramfs -o /boot/initrd-2.6.29-rc7-tip.img 2.6.29-rc7-tip > > > >Booted with new kernel under Xen (19355) and get same bug in place. >> Cannot shutdown any PV DomU . Xen Host dies. > >OK, so we''re talking about a new bug now, right?>When you say "Xen Host dies", do you mean that Xen itself crashes? Or that >the dom0 kernel crashes? Hangs? Non-responsive?******************************************* It stops responding at all as 3 days ago. Just the same picture :- PV DomU CentOS 5.2 has been tested with new kernel During shutdown mentioned DomU usual sequence of daemon''s messages drops into stack trace with following messages at the end:- xenbus_dev_shutdown: device/vif/0 timeout closing device xenbus_dev_shutdown: device/vbd/51712 timeout closing device System halted. *******************************************> Do you have a serial console?> J Jeremy, Bellow follows my message to you sent on 3/14/09 The bug is old. I do have null modem cable ( 2 m.) . Setting up serial is quite possible, but not right now. Boxes are located in different places. Boris --- On Sat, 3/14/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: Re: [Xen-devel] tip.git regression from "vsprintf: unify the format decoding layer for its 3 users" To: "Jeremy Fitzhardinge" <jeremy@goop.org> Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Saturday, March 14, 2009, 5:43 AM Two PV DomUs (CentOS 5.2 , F10) have been tested with new kernel During shutdown of any one of mentioned DomUs usual sequence of daemon''s messages drops into stack trace with following messages at the end:- xenbus_dev_shutdown: device/vif/0 timeout closing device xenbus_dev_shutdown: device/vbd/51712 timeout closing device System halted. After that Xen Host stop responding at all, just dies. Boris --- On Sat, 3/14/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote: From: Jeremy Fitzhardinge <jeremy@goop.org> Subject: [Xen-devel] tip.git regression from "vsprintf: unify the format decoding layer for its 3 users" To: "Frederic Weisbecker" <fweisbec@gmail.com> Cc: "Xen-devel" <xen-devel@lists.xensource.com>, "Ingo Molnar" <mingo@elte.hu>, "the arch/x86 maintainers" <x86@kernel.org>, "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org> Date: Saturday, March 14, 2009, 3:04 AM Change fef20d9c1380f04ba9492d6463148db07b413708, "vsprintf: unify the format decoding layer for its 3 users", causes a regression in xenbus which results in no devices getting attached to a new domain. Reverting fef20d9c1380f04ba9492d6463148db07b413708 and 39e874f8afbdb3745e2406ce4ecbde9ac4cbaa78 fixes the problem. I haven''t identified what format string is being handled wrongly, so I don''t know what the precise bug is. The most complex looking format in use seems to be %.*s; there''s also "%s/%s", "%i" and "%lX". J _______________________________________________ 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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Andrew Lyon
2009-Mar-16 18:44 UTC
Re: Fw: Re: [Xen-devel] tip.git regression from "vsprintf: unify the format decoding layer for its 3 users"
2009/3/16 Boris Derzhavets <bderzhavets@yahoo.com>:>>>Boris Derzhavets wrote: >> >Performed:- >> > >> >root@ServerIntrepid:/usr/src/linux-2.6-xen# git reset --hard >> > remotes/origin/xen/dom0/hackery >> HEAD is now at a38db50 Merge commit ''tip/core/printk'' into >> xen/dom0/hackery >> >make clean >> >make >>> make modules_install install >> >mkinitramfs -o /boot/initrd-2.6.29-rc7-tip.img 2.6.29-rc7-tip >> > >> >Booted with new kernel under Xen (19355) and get same bug in place. >>> Cannot shutdown any PV DomU . Xen Host dies. >> >>OK, so we''re talking about a new bug now, right? > >>When you say "Xen Host dies", do you mean that Xen itself crashes? Or that >> >the dom0 kernel crashes? Hangs? Non-responsive? > ******************************************* > It stops responding at all as 3 days ago. > Just the same picture :- > > PV DomU CentOS 5.2 has been tested with new kernel > During shutdown mentioned DomU usual sequence of daemon''s messages drops > into stack trace with following messages at the end:- > > xenbus_dev_shutdown: device/vif/0 timeout closing device > xenbus_dev_shutdown: device/vbd/51712 timeout closing device > System halted. > > ******************************************* >> Do you have a serial console? > > > J > > Jeremy, > > Bellow follows my message to you sent on 3/14/09 > The bug is old. > I do have null modem cable ( 2 m.) . Setting up serial is quite possible, > but not right now. Boxes are located in different places. > > BorisI often use serial over ethernet devices to gain remote access to a serial console, I''ve used several different devices: Tibbo www.tibbo.com they use a proprietary protocol and require client side software to be loaded on the client (linux or windows), not sure if data can be encrypted. Portbox http://www.hw-group.com/products/converter/index_en.html very good , uses RFC2217 NVT protocol, client software is windows only but can also be configured as tcp server, supports encryption, quite expensive. eNET http://www.audon.co.uk/enet100.html I think they use a proprietary protocol but they can also be configured as tcp server, no encryption. When the device is configured as a tcp server I simply use netcat as a client, its sufficient for logging and sending sysrq keys. One worry might be that some do not support encryption, so its possible for data to be sniffed. You can also get large devices with many serial ports, some hosting providers offer this as a service. Andy> > --- On Sat, 3/14/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: > > From: Boris Derzhavets <bderzhavets@yahoo.com> > Subject: Re: [Xen-devel] tip.git regression from "vsprintf: unify the format > decoding layer for its 3 users" > To: "Jeremy Fitzhardinge" <jeremy@goop.org> > Cc: "Xen-devel" <xen-devel@lists.xensource.com> > Date: Saturday, March 14, 2009, 5:43 AM > > Two PV DomUs (CentOS 5.2 , F10) have been tested with new kernel > During shutdown of any one of mentioned DomUs usual sequence of daemon''s > messages drops into stack trace with following messages at the end:- > > xenbus_dev_shutdown: device/vif/0 timeout closing device > xenbus_dev_shutdown: device/vbd/51712 timeout closing device > System halted. > > After that Xen Host stop responding at all, just dies. > > Boris > > > --- On Sat, 3/14/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote: > > From: Jeremy Fitzhardinge <jeremy@goop.org> > Subject: [Xen-devel] tip.git regression from "vsprintf: unify the format > decoding layer for its 3 users" > To: "Frederic Weisbecker" <fweisbec@gmail.com> > Cc: "Xen-devel" <xen-devel@lists.xensource.com>, "Ingo Molnar" > <mingo@elte.hu>, "the arch/x86 maintainers" <x86@kernel.org>, "Linux Kernel > Mailing List" <linux-kernel@vger.kernel.org> > Date: Saturday, March 14, 2009, 3:04 AM > > Change fef20d9c1380f04ba9492d6463148db07b413708, "vsprintf: unify the > format decoding layer for its 3 users", causes a regression in xenbus which > results in no devices getting attached to a new domain. Reverting > fef20d9c1380f04ba9492d6463148db07b413708 and > 39e874f8afbdb3745e2406ce4ecbde9ac4cbaa78 fixes the problem. > > I haven''t identified what format string is being handled wrongly, so I > don''t know what the precise bug is. The most complex looking format in use > seems to be %.*s; there''s also "%s/%s", "%i" and > "%lX". > > J > > _______________________________________________ > 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 > > > _______________________________________________ > 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
Jeremy Fitzhardinge
2009-Mar-16 18:51 UTC
Re: Fw: Re: [Xen-devel] tip.git regression from "vsprintf: unify the format decoding layer for its 3 users"
Boris Derzhavets wrote:> >>Boris Derzhavets wrote: > > >Performed:- > > > > > >root@ServerIntrepid:/usr/src/linux-2.6-xen# git reset --hard > remotes/origin/xen/dom0/hackery > > HEAD is now at a38db50 Merge commit ''tip/core/printk'' into > xen/dom0/hackery > > >make clean > > >make > >> make modules_install install > > >mkinitramfs -o /boot/initrd-2.6.29-rc7-tip.img 2.6.29-rc7-tip > > > > > >Booted with new kernel under Xen (19355) and get same bug in place. > >> Cannot shutdown any PV DomU . Xen Host dies. > > > >OK, so we''re talking about a new bug now, right? > > >When you say "Xen Host dies", do you mean that Xen itself crashes? > Or that >the dom0 kernel crashes? Hangs? Non-responsive? > ******************************************* > It stops responding at all as 3 days ago. > Just the same picture :- > > PV DomU CentOS 5.2 has been tested with new kernel > During shutdown mentioned DomU usual sequence of daemon''s messages > drops into stack trace with following messages at the end:- > > xenbus_dev_shutdown: device/vif/0 timeout closing device > xenbus_dev_shutdown: device/vbd/51712 timeout closing device > System halted. >OK, so this appears on the domU console? And at the same time, the host becomes non-responsive? Are there any other symptoms?> > Bellow follows my message to you sent on 3/14/09 > The bug is old. > I do have null modem cable ( 2 m.) . Setting up serial is quite possible, > but not right now. Boxes are located in different places. >If the host just stops responding, then getting the Xen serial console may be the best way to diagnose it. Does it also happen if you remove the vifs from the domU config? Does reverting changes 8c7e11b6b89b3054623bc26bf6bbbda3ffa0ee18, 8b0ddbff9bf6cd8acb881a6296ca5069723f61b1 and 043854ee604d2b49d4def5ac215925296b64b391 help? J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2009-Mar-16 19:03 UTC
Re: Fw: Re: [Xen-devel] tip.git regression from "vsprintf: unify the format decoding layer for its 3 users"
--- On Mon, 3/16/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote: From: Jeremy Fitzhardinge <jeremy@goop.org> Subject: Re: Fw: Re: [Xen-devel] tip.git regression from "vsprintf: unify the format decoding layer for its 3 users" To: bderzhavets@yahoo.com Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Monday, March 16, 2009, 2:51 PM Boris Derzhavets wrote:> >>Boris Derzhavets wrote: > > >Performed:- > > > > > >root@ServerIntrepid:/usr/src/linux-2.6-xen# git reset --hardremotes/origin/xen/dom0/hackery> > HEAD is now at a38db50 Merge commit ''tip/core/printk'' intoxen/dom0/hackery> > >make clean > > >make > >> make modules_install install > > >mkinitramfs -o /boot/initrd-2.6.29-rc7-tip.img 2.6.29-rc7-tip > > > > > >Booted with new kernel under Xen (19355) and get same bug inplace.> >> Cannot shutdown any PV DomU . Xen Host dies. > > > >OK, so we''re talking about a new bug now, right? > > >When you say "Xen Host dies", do you mean that Xen itselfcrashes? Or that >the dom0 kernel crashes? Hangs? Non-responsive?> ******************************************* > It stops responding at all as 3 days ago. > Just the same picture :- > > PV DomU CentOS 5.2 has been tested with new kernel > During shutdown mentioned DomU usual sequence of daemon''s messagesdrops into stack trace with following messages at the end:-> > xenbus_dev_shutdown: device/vif/0 timeout closing device > xenbus_dev_shutdown: device/vbd/51712 timeout closing device > System halted. >OK, so this appears on the domU console? And at the same time, the host becomes non-responsive? Are there any other symptoms? ****** NO ******> > Bellow follows my message to you sent on 3/14/09 > The bug is old. > I do have null modem cable ( 2 m.) . Setting up serial is quite possible, > but not right now. Boxes are located in different places. >If the host just stops responding, then getting the Xen serial console may be the best way to diagnose it. ****************************** I''ll do that as soon as i can ******************************* Does it also happen if you remove the vifs from the domU config? ********************* I can try right now ********************* Does reverting changes 8c7e11b6b89b3054623bc26bf6bbbda3ffa0ee18, 8b0ddbff9bf6cd8acb881a6296ca5069723f61b1 and 043854ee604d2b49d4def5ac215925296b64b391 help? ************************************** Please, type an exact git command i am supposed to run to revert change. ************************************** J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2009-Mar-16 19:14 UTC
Re: Fw: Re: [Xen-devel] tip.git regression from "vsprintf: unify the format decoding layer for its 3 users"
Removing vif from profile fixes the problemBoris --- On Mon, 3/16/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote: From: Jeremy Fitzhardinge <jeremy@goop.org> Subject: Re: Fw: Re: [Xen-devel] tip.git regression from "vsprintf: unify the format decoding layer for its 3 users" To: bderzhavets@yahoo.com Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Monday, March 16, 2009, 2:51 PM Boris Derzhavets wrote:> >>Boris Derzhavets wrote: > > >Performed:- > > > > > >root@ServerIntrepid:/usr/src/linux-2.6-xen# git reset --hardremotes/origin/xen/dom0/hackery> > HEAD is now at a38db50 Merge commit ''tip/core/printk'' intoxen/dom0/hackery> > >make clean > > >make > >> make modules_install install > > >mkinitramfs -o /boot/initrd-2.6.29-rc7-tip.img 2.6.29-rc7-tip > > > > > >Booted with new kernel under Xen (19355) and get same bug inplace.> >> Cannot shutdown any PV DomU . Xen Host dies. > > > >OK, so we''re talking about a new bug now, right? > > >When you say "Xen Host dies", do you mean that Xen itselfcrashes? Or that >the dom0 kernel crashes? Hangs? Non-responsive?> ******************************************* > It stops responding at all as 3 days ago. > Just the same picture :- > > PV DomU CentOS 5.2 has been tested with new kernel > During shutdown mentioned DomU usual sequence of daemon''s messagesdrops into stack trace with following messages at the end:-> > xenbus_dev_shutdown: device/vif/0 timeout closing device > xenbus_dev_shutdown: device/vbd/51712 timeout closing device > System halted. >OK, so this appears on the domU console? And at the same time, the host becomes non-responsive? Are there any other symptoms?> > Bellow follows my message to you sent on 3/14/09 > The bug is old. > I do have null modem cable ( 2 m.) . Setting up serial is quite possible, > but not right now. Boxes are located in different places. >If the host just stops responding, then getting the Xen serial console may be the best way to diagnose it. Does it also happen if you remove the vifs from the domU config? ********************************************** Removing vif from profile fixes the problem ********************************************** Does reverting changes 8c7e11b6b89b3054623bc26bf6bbbda3ffa0ee18, 8b0ddbff9bf6cd8acb881a6296ca5069723f61b1 and 043854ee604d2b49d4def5ac215925296b64b391 help? J _______________________________________________ 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
Jeremy Fitzhardinge
2009-Mar-16 19:14 UTC
Re: Fw: Re: [Xen-devel] tip.git regression from "vsprintf: unify the format decoding layer for its 3 users"
Boris Derzhavets wrote:> > > > > Bellow follows my message to you sent on 3/14/09 > > The bug is old. > > I do have null modem cable ( 2 m.) . Setting up serial is quite possible, > > but not right now. Boxes are located in different places. > > > > If the host just stops responding, then getting the Xen serial console may be > the best way to diagnose it. > > ****************************** > I''ll do that as soon as i can > ******************************* > >(BTW, it would be better if you use the normal convention of quoting my text with > and inserting your comments appropriately. When you use this style, I''m quite likely to not notice your response.)> Does it also happen if you remove the vifs from the domU config? > > ********************* > I can try right now > ********************* > > Does reverting changes > 8c7e11b6b89b3054623bc26bf6bbbda3ffa0ee18, > 8b0ddbff9bf6cd8acb881a6296ca5069723f61b1 and > 043854ee604d2b49d4def5ac215925296b64b391 help? > > ************************************** > Please, type an exact git command > i am supposed to run to revert change. > ************************************** > >$ git revert 8c7e11b6b89b3054623bc26bf6bbbda3ffa0ee18 $ git revert 8b0ddbff9bf6cd8acb881a6296ca5069723f61b1 $ git revert 043854ee604d2b49d4def5ac215925296b64b391 J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2009-Mar-16 21:15 UTC
Re: Fw: Re: [Xen-devel] tip.git regression from "vsprintf: unify the format decoding layer for its 3 users"
Building kernel:- # git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git linux-2.6-xen # cd linux-2.6-xen # git checkout origin/xen/dom0/hackery -b xen/dom0/hackery # git reset --hard remotes/origin/xen/dom0/hackery HEAD is now at a38db50 Merge commit ''tip/core/printk'' into xen/dom0/hackery # git revert 8c7e11b6b89b3054623bc26bf6bbbda3ffa0ee18 # git revert 8b0ddbff9bf6cd8acb881a6296ca5069723f61b1 # git revert 043854ee604d2b49d4def5ac215925296b64b391 make menuconfig make make modules_install install mkinitramfs -o /boot/initrd-2.6.29-rc7-tip.img 2.6.29-rc7-tip Kernel, has been built, loaded under Xen Unstable (19355) creates a stable Xen Host, been able to manage CentOS 5.2, F10, SNV_106 PV DomUs. Moreover SNV_106 was installed on ZFS .As appears the most recent updates to Xen Unstable allow to load PV DomU SNV_106 with ZFS image via pygrub. Boris -- On Mon, 3/16/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote: From: Jeremy Fitzhardinge <jeremy@goop.org> Subject: Re: Fw: Re: [Xen-devel] tip.git regression from "vsprintf: unify the format decoding layer for its 3 users" To: bderzhavets@yahoo.com Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Monday, March 16, 2009, 3:14 PM Boris Derzhavets wrote:> > > > Bellow follows my message to you sent on 3/14/09 > > The bug is old. > > I do have null modem cable ( 2 m.) . Setting up serial is quitepossible,> > but not right now. Boxes are located in different places. > > > If the host just stops responding, then getting the Xen serial consolemay be> the best way to diagnose it. > > ****************************** > I''ll do that as soon as i can > ******************************* >(BTW, it would be better if you use the normal convention of quoting my text with > and inserting your comments appropriately. When you use this style, I''m quite likely to not notice your response.)> Does it also happen if you remove the vifs from the domU config? > > ********************* > I can try right now > ********************* > > Does reverting changes > 8c7e11b6b89b3054623bc26bf6bbbda3ffa0ee18, > 8b0ddbff9bf6cd8acb881a6296ca5069723f61b1 and > 043854ee604d2b49d4def5ac215925296b64b391 help? > > ************************************** > Please, type an exact git command > i am supposed to run to revert change. > ************************************** >$ git revert 8c7e11b6b89b3054623bc26bf6bbbda3ffa0ee18 $ git revert 8b0ddbff9bf6cd8acb881a6296ca5069723f61b1 $ git revert 043854ee604d2b49d4def5ac215925296b64b391 J _______________________________________________ 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
Boris Derzhavets
2009-Mar-20 10:25 UTC
Re: Fw: Re: [Xen-devel] tip.git regression from "vsprintf: unify the format decoding layer for its 3 users"
What would be an approved procedure to build pvops kernel in meantime ? I would guess "ParavirtOps" WIKI''s instruction might confuse people. Boris --- On Mon, 3/16/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: Re: Fw: Re: [Xen-devel] tip.git regression from "vsprintf: unify the format decoding layer for its 3 users" To: "Jeremy Fitzhardinge" <jeremy@goop.org> Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Monday, March 16, 2009, 5:15 PM Building kernel:- # git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git linux-2.6-xen # cd linux-2.6-xen # git checkout origin/xen/dom0/hackery -b xen/dom0/hackery # git reset --hard remotes/origin/xen/dom0/hackery HEAD is now at a38db50 Merge commit ''tip/core/printk'' into xen/dom0/hackery # git revert 8c7e11b6b89b3054623bc26bf6bbbda3ffa0ee18 # git revert 8b0ddbff9bf6cd8acb881a6296ca5069723f61b1 # git revert 043854ee604d2b49d4def5ac215925296b64b391 make menuconfig make make modules_install install mkinitramfs -o /boot/initrd-2.6.29-rc7-tip.img 2.6.29-rc7-tip Kernel, has been built, loaded under Xen Unstable (19355) creates a stable Xen Host, been able to manage CentOS 5.2, F10, SNV_106 PV DomUs. Moreover SNV_106 was installed on ZFS .As appears the most recent updates to Xen Unstable allow to load PV DomU SNV_106 with ZFS image via pygrub. Boris -- On Mon, 3/16/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote: From: Jeremy Fitzhardinge <jeremy@goop.org> Subject: Re: Fw: Re: [Xen-devel] tip.git regression from "vsprintf: unify the format decoding layer for its 3 users" To: bderzhavets@yahoo.com Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Monday, March 16, 2009, 3:14 PM Boris Derzhavets wrote:> > > > Bellow follows my message to you sent on 3/14/09 > > The bug is old. > > I do have null modem cable ( 2 m.) . Setting up serial is quitepossible,> > but not right now. Boxes are located in different places. > > > If the host just stopsresponding, then getting the Xen serial console may be> the best way to diagnose it. > > ****************************** > I''ll do that as soon as i can > ******************************* >(BTW, it would be better if you use the normal convention of quoting my text with > and inserting your comments appropriately. When you use this style, I''m quite likely to not notice your response.)> Does it also happen if you remove the vifs from the domU config? > > ********************* > I can try right now > ********************* > > Does reverting changes > 8c7e11b6b89b3054623bc26bf6bbbda3ffa0ee18, > 8b0ddbff9bf6cd8acb881a6296ca5069723f61b1 and > 043854ee604d2b49d4def5ac215925296b64b391 help? > > ************************************** > Please, typean exact git command> i am supposed to run to revert change. > ************************************** >$ git revert 8c7e11b6b89b3054623bc26bf6bbbda3ffa0ee18 $ git revert 8b0ddbff9bf6cd8acb881a6296ca5069723f61b1 $ git revert 043854ee604d2b49d4def5ac215925296b64b391 J _______________________________________________ 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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2009-Mar-20 17:30 UTC
Re: Fw: Re: [Xen-devel] tip.git regression from "vsprintf: unify the format decoding layer for its 3 users"
Sorry , "ParavirtOps" WIKI''s instruction works. Boris. --- On Fri, 3/20/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: Re: Fw: Re: [Xen-devel] tip.git regression from "vsprintf: unify the format decoding layer for its 3 users" To: "Jeremy Fitzhardinge" <jeremy@goop.org> Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Friday, March 20, 2009, 6:25 AM What would be an approved procedure to build pvops kernel in meantime ? I would guess "ParavirtOps" WIKI''s instruction might confuse people. Boris --- On Mon, 3/16/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: Re: Fw: Re: [Xen-devel] tip.git regression from "vsprintf: unify the format decoding layer for its 3 users" To: "Jeremy Fitzhardinge" <jeremy@goop.org> Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Monday, March 16, 2009, 5:15 PM Building kernel:- # git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git linux-2.6-xen # cd linux-2.6-xen # git checkout origin/xen/dom0/hackery -b xen/dom0/hackery # git reset --hard remotes/origin/xen/dom0/hackery HEAD is now at a38db50 Merge commit ''tip/core/printk'' into xen/dom0/hackery # git revert 8c7e11b6b89b3054623bc26bf6bbbda3ffa0ee18 # git revert 8b0ddbff9bf6cd8acb881a6296ca5069723f61b1 # git revert 043854ee604d2b49d4def5ac215925296b64b391 make menuconfig make make modules_install install mkinitramfs -o /boot/initrd-2.6.29-rc7-tip.img 2.6.29-rc7-tip Kernel, has been built, loaded under Xen Unstable (19355) creates a stable Xen Host, been able to manage CentOS 5.2, F10, SNV_106 PV DomUs. Moreover SNV_106 was installed on ZFS .As appears the most recent updates to Xen Unstable allow to load PV DomU SNV_106 with ZFS image via pygrub. Boris -- On Mon, 3/16/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote: From: Jeremy Fitzhardinge <jeremy@goop.org> Subject: Re: Fw: Re: [Xen-devel] tip.git regression from "vsprintf: unify the format decoding layer for its 3 users" To: bderzhavets@yahoo.com Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Monday, March 16, 2009, 3:14 PM Boris Derzhavets wrote:> > > > Bellow follows my message to you sent on 3/14/09 > > The bug is old. > > I do have null modem cable ( 2 m.) . Setting up serial is quitepossible,> > but not right now. Boxes are located in different places. > > > If the host just stopsresponding, then getting the Xen serial console may be> the best way to diagnose it. > > ****************************** > I''ll do that as soon as i can > ******************************* >(BTW, it would be better if you use the normal convention of quoting my text with > and inserting your comments appropriately. When you use this style, I''m quite likely to not notice your response.)> Does it also happen if you remove the vifs from the domU config? > > ********************* > I can try right now > ********************* > > Does reverting changes > 8c7e11b6b89b3054623bc26bf6bbbda3ffa0ee18, > 8b0ddbff9bf6cd8acb881a6296ca5069723f61b1 and > 043854ee604d2b49d4def5ac215925296b64b391 help? > > ************************************** > Please,type an exact git command> i am supposed to run to revert change. > ************************************** >$ git revert 8c7e11b6b89b3054623bc26bf6bbbda3ffa0ee18 $ git revert 8b0ddbff9bf6cd8acb881a6296ca5069723f61b1 $ git revert 043854ee604d2b49d4def5ac215925296b64b391 J _______________________________________________ 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 _______________________________________________ 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
Boris Derzhavets
2009-Mar-21 17:28 UTC
[Xen-devel] The most recent attempt to build 2.6.29-rc8
AS arch/x86/lib/copy_user_nocache_64.o
AS arch/x86/lib/csum-copy_64.o
CC arch/x86/lib/csum-partial_64.o
CC arch/x86/lib/csum-wrappers_64.o
CC arch/x86/lib/delay.o
AS arch/x86/lib/getuser.o
AS arch/x86/lib/memcpy_64.o
CC arch/x86/lib/memmove_64.o
AS arch/x86/lib/memset_64.o
AS arch/x86/lib/putuser.o
AS arch/x86/lib/rwlock_64.o
AS arch/x86/lib/thunk_64.o
CC arch/x86/lib/usercopy_64.o
AR arch/x86/lib/lib.a
LD vmlinux.o
MODPOST vmlinux.o
WARNING: modpost: Found 3 section mismatch(es).
To see full details build your kernel with:
''make CONFIG_DEBUG_SECTION_MISMATCH=y''
GEN .version
CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
drivers/built-in.o: In function `xenbus_register_frontend'':
/home/boris/linux-2.6-xen/include/xen/xenbus.h:115: undefined reference to
`__xenbus_register_frontend''
/home/boris/linux-2.6-xen/include/xen/xenbus.h:115: undefined reference to
`__xenbus_register_frontend''
make: *** [.tmp_vmlinux1] Error 1
Boris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2009-Mar-22 04:28 UTC
Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8
Boris Derzhavets wrote:> AS arch/x86/lib/copy_user_nocache_64.o > AS arch/x86/lib/csum-copy_64.o > CC arch/x86/lib/csum-partial_64.o > CC arch/x86/lib/csum-wrappers_64.o > CC arch/x86/lib/delay.o > AS arch/x86/lib/getuser.o > AS arch/x86/lib/memcpy_64.o > CC arch/x86/lib/memmove_64.o > AS arch/x86/lib/memset_64.o > AS arch/x86/lib/putuser.o > AS arch/x86/lib/rwlock_64.o > AS arch/x86/lib/thunk_64.o > CC arch/x86/lib/usercopy_64.o > AR arch/x86/lib/lib.a > LD vmlinux.o > MODPOST vmlinux.o > WARNING: modpost: Found 3 section mismatch(es). > To see full details build your kernel with: > ''make CONFIG_DEBUG_SECTION_MISMATCH=y'' > GEN .version > CHK include/linux/compile.h > UPD include/linux/compile.h > CC init/version.o > LD init/built-in.o > LD .tmp_vmlinux1 > drivers/built-in.o: In function `xenbus_register_frontend'': > /home/boris/linux-2.6-xen/include/xen/xenbus.h:115: undefined > reference to `__xenbus_register_frontend'' > /home/boris/linux-2.6-xen/include/xen/xenbus.h:115: undefined > reference to `__xenbus_register_frontend'' > make: *** [.tmp_vmlinux1] Error 1 >This is xen/dom0/hackery? Are you using modules for your Xen config? J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2009-Mar-22 07:02 UTC
Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git linux-2.6-xen $ cd linux-2.6-xen $ git checkout origin/xen/dom0/hackery -b xen/dom0/hackery Yes. Same build as yesterday just on an other box. Boris. --- On Sun, 3/22/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote: From: Jeremy Fitzhardinge <jeremy@goop.org> Subject: Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8 To: bderzhavets@yahoo.com Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Sunday, March 22, 2009, 12:28 AM Boris Derzhavets wrote:> AS arch/x86/lib/copy_user_nocache_64.o > AS arch/x86/lib/csum-copy_64.o > CC arch/x86/lib/csum-partial_64.o > CC arch/x86/lib/csum-wrappers_64.o > CC arch/x86/lib/delay.o > AS arch/x86/lib/getuser.o > AS arch/x86/lib/memcpy_64.o > CC arch/x86/lib/memmove_64.o > AS arch/x86/lib/memset_64.o > AS arch/x86/lib/putuser.o > AS arch/x86/lib/rwlock_64.o > AS arch/x86/lib/thunk_64.o > CC arch/x86/lib/usercopy_64.o > AR arch/x86/lib/lib.a > LD vmlinux.o > MODPOST vmlinux.o > WARNING: modpost: Found 3 section mismatch(es). > To see full details build your kernel with: > ''make CONFIG_DEBUG_SECTION_MISMATCH=y'' > GEN .version > CHK include/linux/compile.h > UPD include/linux/compile.h > CC init/version.o > LD init/built-in.o > LD .tmp_vmlinux1 > drivers/built-in.o: In function `xenbus_register_frontend'': > /home/boris/linux-2.6-xen/include/xen/xenbus.h:115: undefined reference to`__xenbus_register_frontend''> /home/boris/linux-2.6-xen/include/xen/xenbus.h:115: undefined reference to`__xenbus_register_frontend''> make: *** [.tmp_vmlinux1] Error 1 >This is xen/dom0/hackery? Are you using modules for your Xen config? J _______________________________________________ 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
Boris Derzhavets
2009-Mar-22 08:16 UTC
Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8
Build was successful without 5 recent commits :- ab0d988fcd8fc00eb638cbc65fb4a3196b9e4886 d46ab5a742e9cfab89d72dbae3e2864a5ef1febe 7a9e8bed8a756b1c07a92af20b6276bbe4cb4ed7 bd4a7874716d1b1f69cacfef4adf9f94050ecd82 cfb667260eb7f6dd26ceb6d49da818978396757d Boris --- On Sun, 3/22/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8 To: "Jeremy Fitzhardinge" <jeremy@goop.org> Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Sunday, March 22, 2009, 3:02 AM $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git linux-2.6-xen $ cd linux-2.6-xen $ git checkout origin/xen/dom0/hackery -b xen/dom0/hackery Yes. Same build as yesterday just on an other box. Boris. --- On Sun, 3/22/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote: From: Jeremy Fitzhardinge <jeremy@goop.org> Subject: Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8 To: bderzhavets@yahoo.com Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Sunday, March 22, 2009, 12:28 AM Boris Derzhavets wrote:> ASarch/x86/lib/copy_user_nocache_64.o> AS arch/x86/lib/csum-copy_64.o > CC arch/x86/lib/csum-partial_64.o > CC arch/x86/lib/csum-wrappers_64.o > CC arch/x86/lib/delay.o > AS arch/x86/lib/getuser.o > AS arch/x86/lib/memcpy_64.o > CC arch/x86/lib/memmove_64.o > AS arch/x86/lib/memset_64.o > AS arch/x86/lib/putuser.o > AS arch/x86/lib/rwlock_64.o > AS arch/x86/lib/thunk_64.o > CC arch/x86/lib/usercopy_64.o > AR arch/x86/lib/lib.a > LD vmlinux.o > MODPOST vmlinux.o > WARNING: modpost: Found 3 section mismatch(es). > To see full details build your kernel with: > ''make CONFIG_DEBUG_SECTION_MISMATCH=y'' > GEN .version > CHK include/linux/compile.h > UPD include/linux/compile.h > CC init/version.o > LDinit/built-in.o> LD .tmp_vmlinux1 > drivers/built-in.o: In function `xenbus_register_frontend'': > /home/boris/linux-2.6-xen/include/xen/xenbus.h:115: undefined reference to`__xenbus_register_frontend''> /home/boris/linux-2.6-xen/include/xen/xenbus.h:115: undefined reference to`__xenbus_register_frontend''> make: *** [.tmp_vmlinux1] Error 1 >This is xen/dom0/hackery? Are you using modules for your Xen config? J _______________________________________________ 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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2009-Mar-22 10:16 UTC
Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8
I failed to revert commits. Is there any chance to rollback ( git bisect ?) to:- commit 43dc5d909d20fc86c4f1cfbec55e78f73f4ffa00 Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> Date: Wed Mar 18 16:39:11 2009 -0700 xen/apic: add new parameter for setup_ioapic_entry() setup_ioapic_entry() now takes the pin as well. Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> commit 10a04b072ec4cc877d7c1746cc92c728a3d144b0 Merge: 0ed3109... 6aafa6c... Boris. --- On Sun, 3/22/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8 To: "Jeremy Fitzhardinge" <jeremy@goop.org> Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Sunday, March 22, 2009, 4:16 AM Build was successful without 5 recent commits :- ab0d988fcd8fc00eb638cbc65fb4a3196b9e4886 d46ab5a742e9cfab89d72dbae3e2864a5ef1febe 7a9e8bed8a756b1c07a92af20b6276bbe4cb4ed7 bd4a7874716d1b1f69cacfef4adf9f94050ecd82 cfb667260eb7f6dd26ceb6d49da818978396757d Boris --- On Sun, 3/22/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8 To: "Jeremy Fitzhardinge" <jeremy@goop.org> Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Sunday, March 22, 2009, 3:02 AM $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git linux-2.6-xen $ cd linux-2.6-xen $ git checkout origin/xen/dom0/hackery -b xen/dom0/hackery Yes. Same build as yesterday just on an other box. Boris. --- On Sun, 3/22/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote: From: Jeremy Fitzhardinge <jeremy@goop.org> Subject: Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8 To: bderzhavets@yahoo.com Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Sunday, March 22, 2009, 12:28 AM Boris Derzhavets wrote:> ASarch/x86/lib/copy_user_nocache_64.o> AS arch/x86/lib/csum-copy_64.o > CC arch/x86/lib/csum-partial_64.o > CC arch/x86/lib/csum-wrappers_64.o > CC arch/x86/lib/delay.o > AS arch/x86/lib/getuser.o > AS arch/x86/lib/memcpy_64.o > CC arch/x86/lib/memmove_64.o > AS arch/x86/lib/memset_64.o > AS arch/x86/lib/putuser.o > AS arch/x86/lib/rwlock_64.o > AS arch/x86/lib/thunk_64.o > CC arch/x86/lib/usercopy_64.o > AR arch/x86/lib/lib.a > LD vmlinux.o > MODPOST vmlinux.o > WARNING: modpost: Found 3 section mismatch(es). > To see full details build your kernel with: > ''make CONFIG_DEBUG_SECTION_MISMATCH=y'' > GEN .version > CHKinclude/linux/compile.h> UPD include/linux/compile.h > CC init/version.o > LDinit/built-in.o> LD .tmp_vmlinux1 > drivers/built-in.o: In function `xenbus_register_frontend'': > /home/boris/linux-2.6-xen/include/xen/xenbus.h:115: undefined reference to`__xenbus_register_frontend''> /home/boris/linux-2.6-xen/include/xen/xenbus.h:115: undefined reference to`__xenbus_register_frontend''> make: *** [.tmp_vmlinux1] Error 1 >This is xen/dom0/hackery? Are you using modules for your Xen config? J _______________________________________________ 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 _______________________________________________ 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
M A Young
2009-Mar-22 12:32 UTC
Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8
On Sat, 21 Mar 2009, Boris Derzhavets wrote:> ... > LD .tmp_vmlinux1 > drivers/built-in.o: In function `xenbus_register_frontend'': > /home/boris/linux-2.6-xen/include/xen/xenbus.h:115: undefined reference to > `__xenbus_register_frontend'' > /home/boris/linux-2.6-xen/include/xen/xenbus.h:115: undefined reference to > `__xenbus_register_frontend'' > make: *** [.tmp_vmlinux1] Error 1What XEN configuration options are you using? I think there are certain combinations of module and non-module configurations that don''t work. Michael Young _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2009-Mar-22 14:55 UTC
Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8
File .config is attached. It''s always the same. Just now i did everything from scratch :- # rm -fr linux-2.6-xen # git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git linux-2.6-xen # cd linux-2.6-xen # git checkout origin/xen/dom0/hackery -b xen/dom0/hackery and was able to build working rc8 kernel. I''ve also compared saved "git log > log.1" with new one "git log > log.2". They are identical all recent commits are there. Would it be possible to download via git some inconsistent state of original repository ? I am not sure. Boris --- On Sun, 3/22/09, M A Young <m.a.young@durham.ac.uk> wrote: From: M A Young <m.a.young@durham.ac.uk> Subject: Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8 To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>, "Xen-devel" <xen-devel@lists.xensource.com> Date: Sunday, March 22, 2009, 8:32 AM On Sat, 21 Mar 2009, Boris Derzhavets wrote:> ... > LD .tmp_vmlinux1 > drivers/built-in.o: In function `xenbus_register_frontend'': > /home/boris/linux-2.6-xen/include/xen/xenbus.h:115: undefined reference to > `__xenbus_register_frontend'' > /home/boris/linux-2.6-xen/include/xen/xenbus.h:115: undefined reference to > `__xenbus_register_frontend'' > make: *** [.tmp_vmlinux1] Error 1What XEN configuration options are you using? I think there are certain combinations of module and non-module configurations that don''t work. Michael Young_______________________________________________ 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
M A Young
2009-Mar-22 15:06 UTC
Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8
On Sun, 22 Mar 2009, Boris Derzhavets wrote:> File .config is attached. It''s always the same. > Just now i did everything from scratch :-Set CONFIG_XEN_XENBUS_FRONTEND=y and it should build (or at least get past your current problem). Michael Young _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2009-Mar-22 15:46 UTC
Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8
If CONFIG_XEN_NETDEV_FRONTEND=m then i can build kernel in both cases:- 1) CONFIG_XEN_XENBUS_FRONTEND=y 2) CONFIG_XEN_XENBUS_FRONTEND=m If CONFIG_XEN_NETDEV_FRONTEND=y then i cannot build kernel in both cases:- 1) CONFIG_XEN_XENBUS_FRONTEND=y 2) CONFIG_XEN_XENBUS_FRONTEND=m Yesterday, i occasionally set CONFIG_XEN_NETDEV_FRONTEND=y and got a problem:- WARNING: modpost: Found 3 section mismatch(es). To see full details build your kernel with: ''make CONFIG_DEBUG_SECTION_MISMATCH=y'' GEN .version CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 drivers/built-in.o: In function `xenbus_register_frontend'': /usr/src/linux-2.6-xen/include/xen/xenbus.h:115: undefined reference to `__xenbus_register_frontend'' make: *** [.tmp_vmlinux1] Error 1 Thank you. Boris. --- On Sun, 3/22/09, M A Young <m.a.young@durham.ac.uk> wrote: From: M A Young <m.a.young@durham.ac.uk> Subject: Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8 To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>, "Xen-devel" <xen-devel@lists.xensource.com> Date: Sunday, March 22, 2009, 11:06 AM On Sun, 22 Mar 2009, Boris Derzhavets wrote:> File .config is attached. It''s always the same. > Just now i did everything from scratch :-Set CONFIG_XEN_XENBUS_FRONTEND=y and it should build (or at least get past your current problem). Michael Young _______________________________________________ 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
M A Young
2009-Mar-22 17:09 UTC
Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8
On Sun, 22 Mar 2009, Boris Derzhavets wrote:> If CONFIG_XEN_NETDEV_FRONTEND=m then > i can build kernel in both cases:- > > 1) CONFIG_XEN_XENBUS_FRONTEND=y > 2) CONFIG_XEN_XENBUS_FRONTEND=m > > If CONFIG_XEN_NETDEV_FRONTEND=y then > i cannot build kernel in both cases:- > > 1) CONFIG_XEN_XENBUS_FRONTEND=y > 2) CONFIG_XEN_XENBUS_FRONTEND=mI suspect that if you checked the .config file, on both these last two you would have found that it contained CONFIG_XEN_XENBUS_FRONTEND=m, which is what I found when I tried it just now, which means that something is resetting the value. Michael Young _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
M A Young
2009-Mar-22 18:03 UTC
Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8
On Sun, 22 Mar 2009, M A Young wrote:> I suspect that if you checked the .config file, on both these last two you > would have found that it contained CONFIG_XEN_XENBUS_FRONTEND=m, which is > what I found when I tried it just now, which means that something is > resetting the value.And to answer my own implied question, XEN_XENBUS_FRONTEND is set automatically to whatever the larger of XEN_BLKDEV_FRONTEND (in drivers/block/Kconfig) or NETXEN_NIC (in drivers/net/Kconfig) is via the select command. Comparing this with the code and Makefiles, this is correct for XEN_BLKDEV_FRONTEND, but NETXEN_NIC has no direct requirement for XEN_XENBUS_FRONTEND (though it should require XEN_NETDEV_FRONTEND). Also XEN_KBDDEV_FRONTEND (in drivers/input/Kconfig), XEN_NETDEV_FRONTEND (in drivers/net/Kconfig) and CONFIG_XEN_FBDEV_FRONTEND (in drivers/video/Kconfig) should all select XEN_XENBUS_FRONTEND to set the value of this field correctly. Michael Young _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2009-Mar-22 18:22 UTC
Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8
Yes, i''ve noticed also that after build completed CONFIG_XEN_XENBUS_FRONTEND gets reset to "m" Boris. --- On Sun, 3/22/09, M A Young <m.a.young@durham.ac.uk> wrote: From: M A Young <m.a.young@durham.ac.uk> Subject: Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8 To: "Boris Derzhavets" <bderzhavets@yahoo.com> Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>, "Xen-devel" <xen-devel@lists.xensource.com> Date: Sunday, March 22, 2009, 1:09 PM On Sun, 22 Mar 2009, Boris Derzhavets wrote:> If CONFIG_XEN_NETDEV_FRONTEND=m then > i can build kernel in both cases:- > > 1) CONFIG_XEN_XENBUS_FRONTEND=y > 2) CONFIG_XEN_XENBUS_FRONTEND=m > > If CONFIG_XEN_NETDEV_FRONTEND=y then > i cannot build kernel in both cases:- > > 1) CONFIG_XEN_XENBUS_FRONTEND=y > 2) CONFIG_XEN_XENBUS_FRONTEND=mI suspect that if you checked the .config file, on both these last two you would have found that it contained CONFIG_XEN_XENBUS_FRONTEND=m, which is what I found when I tried it just now, which means that something is resetting the value. Michael Young_______________________________________________ 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
M A Young
2009-Mar-22 21:25 UTC
Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8
On Sun, 22 Mar 2009, Boris Derzhavets wrote:> Yes, i''ve noticed also that after build completed > > CONFIG_XEN_XENBUS_FRONTEND > gets reset to "m"I think the attached patch fixes the XEN_XENBUS_FRONTEND configuration dependencies. Michael Young _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2009-Mar-25 08:22 UTC
Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8
M A Young wrote:> On Sun, 22 Mar 2009, Boris Derzhavets wrote: > >> Yes, i''ve noticed also that after build completed >> >> CONFIG_XEN_XENBUS_FRONTEND >> gets reset to "m" > > I think the attached patch fixes the XEN_XENBUS_FRONTEND configuration > dependencies.(This patch was full of ^M''s) Unfortunately this didn''t help me; it still ended up making this ''m'', which doesn''t work. The simple fix is, I think, to make this a "bool", so it gets built in. Its not really big enough to bother with. J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
M A Young
2009-Mar-25 08:52 UTC
Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8
On Wed, 25 Mar 2009, Jeremy Fitzhardinge wrote:> M A Young wrote: >> On Sun, 22 Mar 2009, Boris Derzhavets wrote: >> >>> Yes, i''ve noticed also that after build completed >>> >>> CONFIG_XEN_XENBUS_FRONTEND >>> gets reset to "m" >> >> I think the attached patch fixes the XEN_XENBUS_FRONTEND configuration >> dependencies. > > (This patch was full of ^M''s)That''s strange because it wasn''t when I sent it. I wonder if it got mangled in-transit.> Unfortunately this didn''t help me; it still ended up making this ''m'', which > doesn''t work. The simple fix is, I think, to make this a "bool", so it gets > built in. Its not really big enough to bother with.I have been using XEN_XENBUS_FRONTEND=m on some of my kernels so it didn''t cause me a problem, though of course if any of the dependent modules were "y" then that would indeed be incorrect. I did have an alternate way of doing it that I could try. Michael Young _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
M A Young
2009-Mar-25 09:12 UTC
Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8
On Wed, 25 Mar 2009, M A Young wrote:> On Wed, 25 Mar 2009, Jeremy Fitzhardinge wrote: > >> M A Young wrote: >>> On Sun, 22 Mar 2009, Boris Derzhavets wrote: >>> >>>> Yes, i''ve noticed also that after build completed >>>> >>>> CONFIG_XEN_XENBUS_FRONTEND >>>> gets reset to "m" >>> >>> I think the attached patch fixes the XEN_XENBUS_FRONTEND configuration >>> dependencies. >> >> (This patch was full of ^M''s) > > That''s strange because it wasn''t when I sent it. I wonder if it got mangled > in-transit. > >> Unfortunately this didn''t help me; it still ended up making this ''m'', which >> doesn''t work. The simple fix is, I think, to make this a "bool", so it >> gets built in. Its not really big enough to bother with. > > I have been using XEN_XENBUS_FRONTEND=m on some of my kernels so it didn''t > cause me a problem, though of course if any of the dependent modules were "y" > then that would indeed be incorrect. I did have an alternate way of doing it > that I could try.I should probably have said that the alternate idea was to remove the selects, then make XEN_XENBUS_FRONTEND default y and depends on XEN_FBDEV_FRONTEND || XEN_NETDEV_FRONTEND || XEN_BLKDEV_FRONTEND || XEN_KBDDEV_FRONTEND I haven''t tested this. Michael Young _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2009-Mar-25 17:28 UTC
Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8
M A Young wrote:> That''s strange because it wasn''t when I sent it. I wonder if it got > mangled in-transit.It was an attachment, so it should have been resistant. Though it also had a ''\0'' on the end for good measure.>> Unfortunately this didn''t help me; it still ended up making this ''m'', >> which doesn''t work. The simple fix is, I think, to make this a >> "bool", so it gets built in. Its not really big enough to bother with. > > I have been using XEN_XENBUS_FRONTEND=m on some of my kernels so it > didn''t cause me a problem, though of course if any of the dependent > modules were "y" then that would indeed be incorrect. I did have an > alternate way of doing it that I could try.Hm. I wonder if there''s a bunch of symbol exports missing. Or perhaps it''s a secondary problem, like mkinitrd is not putting the right modules in place. J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2009-Mar-25 17:45 UTC
Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8
M A Young wrote:> On Wed, 25 Mar 2009, M A Young wrote: > >> On Wed, 25 Mar 2009, Jeremy Fitzhardinge wrote: >> >>> M A Young wrote: >>>> On Sun, 22 Mar 2009, Boris Derzhavets wrote: >>>> >>>>> Yes, i''ve noticed also that after build completed >>>>> >>>>> CONFIG_XEN_XENBUS_FRONTEND >>>>> gets reset to "m" >>>> >>>> I think the attached patch fixes the XEN_XENBUS_FRONTEND >>>> configuration dependencies. >>> >>> (This patch was full of ^M''s) >> >> That''s strange because it wasn''t when I sent it. I wonder if it got >> mangled in-transit. >> >>> Unfortunately this didn''t help me; it still ended up making this >>> ''m'', which doesn''t work. The simple fix is, I think, to make this a >>> "bool", so it gets built in. Its not really big enough to bother with. >> >> I have been using XEN_XENBUS_FRONTEND=m on some of my kernels so it >> didn''t cause me a problem, though of course if any of the dependent >> modules were "y" then that would indeed be incorrect. I did have an >> alternate way of doing it that I could try. > > I should probably have said that the alternate idea was to remove the > selects, then make XEN_XENBUS_FRONTEND default y and depends on > XEN_FBDEV_FRONTEND || XEN_NETDEV_FRONTEND || XEN_BLKDEV_FRONTEND || > XEN_KBDDEV_FRONTENDDoesn''t scale very well as we add more frontends though. I don''t see a huge benefit in making it separately compilable anyway; it''s pretty small, and I can''t think of much plausible use for a Xen kernel without frontends. (On the other hand, making all of xenbus a single module might be useful, so that a non-Xen boot doesn''t have to carry it.) J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2009-Mar-25 18:37 UTC
Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8
With the most recent update i was able to build kernel with attached .config CONFIG_XEN_NETDEV_FRONTEND=y CONFIG_XEN_XENBUS_FRONTEND=y root@ServerXen331:/usr/src/linux-2.6-xen# git pull remote: Counting objects: 34, done. remote: Compressing objects: 100% (19/19), done. remote: Total 19 (delta 16), reused 0 (delta 0) Unpacking objects: 100% (19/19), done.>From git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xence44abd..10a340b xen/dom0/hackery -> origin/xen/dom0/hackery Updating ce44abd..10a340b Fast forward drivers/input/Kconfig | 1 + drivers/net/Kconfig | 2 +- drivers/video/Kconfig | 1 + 3 files changed, 3 insertions(+), 1 deletions(-) Boris --- On Wed, 3/25/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote: From: Jeremy Fitzhardinge <jeremy@goop.org> Subject: Re: [Xen-devel] The most recent attempt to build 2.6.29-rc8 To: "M A Young" <m.a.young@durham.ac.uk> Cc: "Boris Derzhavets" <bderzhavets@yahoo.com>, "Xen-devel" <xen-devel@lists.xensource.com> Date: Wednesday, March 25, 2009, 1:45 PM M A Young wrote:> On Wed, 25 Mar 2009, M A Young wrote: > >> On Wed, 25 Mar 2009, Jeremy Fitzhardinge wrote: >> >>> M A Young wrote: >>>> On Sun, 22 Mar 2009, Boris Derzhavets wrote: >>>> >>>>> Yes, i''ve noticed also that after build completed >>>>> >>>>> CONFIG_XEN_XENBUS_FRONTEND >>>>> gets reset to "m" >>>> >>>> I think the attached patch fixes the XEN_XENBUS_FRONTENDconfiguration dependencies.>>> >>> (This patch was full of ^M''s) >> >> That''s strange because it wasn''t when I sent it. I wonder ifit got mangled in-transit.>> >>> Unfortunately this didn''t help me; it still ended up makingthis ''m'', which doesn''t work. The simple fix is, I think, to make this a "bool", so it gets built in. Its not really big enough to bother with.>> >> I have been using XEN_XENBUS_FRONTEND=m on some of my kernels so itdidn''t cause me a problem, though of course if any of the dependent modules were "y" then that would indeed be incorrect. I did have an alternate way of doing it that I could try.> > I should probably have said that the alternate idea was to remove theselects, then make XEN_XENBUS_FRONTEND default y and depends on XEN_FBDEV_FRONTEND || XEN_NETDEV_FRONTEND || XEN_BLKDEV_FRONTEND || XEN_KBDDEV_FRONTEND Doesn''t scale very well as we add more frontends though. I don''t see a huge benefit in making it separately compilable anyway; it''s pretty small, and I can''t think of much plausible use for a Xen kernel without frontends. (On the other hand, making all of xenbus a single module might be useful, so that a non-Xen boot doesn''t have to carry it.) J _______________________________________________ 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