I tried with latest Xen unstable (c/s 19833) with latest pvops dom0 (commit
384a55c0). Booting will hang, following is the serial console output:
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch input to Xen
)
(XEN) Freed 128kB init memory.
mapping kernel into physical memory
Xen: setup ISA identity maps
about to get started...
(XEN) ioapic_guest_write: apic=0, pin=2, old_irq=0, new_irq=-1
(XEN) ioapic_guest_write: old_entry=000009f0, new_entry=00010900
(XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=-1
(XEN) ioapic_guest_write: old_entry=000009f1, new_entry=00010900
(XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=0, old_irq=-1, new_irq=0
(XEN) ioapic_guest_write: old_entry=00010900, new_entry=000009f0
(XEN) ioapic_guest_write: Attempt to add IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19
(XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19
(XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=23, old_irq=23, new_irq=23
(XEN) ioapic_guest_write: old_entry=0000a9d0, new_entry=0001a9d0
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19
(XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=16, old_irq=16, new_irq=16
(XEN) ioapic_guest_write: old_entry=0000a9b8, new_entry=0001a9b8
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=18, old_irq=18, new_irq=18
(XEN) ioapic_guest_write: old_entry=0000a921, new_entry=0001a921
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
Did anyone meet this issue? Is there any difference on build and installation
between pvops dom0 and 2.6.18 dom0? Following is my instructions, pls correct me
if something is wrong. Appreciate in advance.
My build and installation instructions:
- cd xen-unstable.hg
- make world (linux-2.6-pvops.git will be cloned)
- make install
My grub entry:
title Xen - pvops
root (hd0,2)
kernel /boot/xen.gz dom0_mem=512m
module /boot/vmlinuz-2.6-30.rc3-tip ro root=/dev/sda3 console=tty0
console=ttyS0
I also tried build pvops dom0 manually as follows, but it doesn''t help.
- cd linux-2.6-pvops.git
- make
- make modules_install
- make install
Regards,
Weidong
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
On Thu, Jun 25, 2009 at 6:20 PM, Han, Weidong<weidong.han@intel.com> wrote:> I tried with latest Xen unstable (c/s 19833) with latest pvops dom0 (commit 384a55c0). Booting will hang, following is the serial console output: > > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen > ) > (XEN) Freed 128kB init memory. > mapping kernel into physical memory > Xen: setup ISA identity maps > about to get started... > (XEN) ioapic_guest_write: apic=0, pin=2, old_irq=0, new_irq=-1 > (XEN) ioapic_guest_write: old_entry=000009f0, new_entry=00010900 > (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use IRQ! > (XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=-1 > (XEN) ioapic_guest_write: old_entry=000009f1, new_entry=00010900 > (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use IRQ! > (XEN) ioapic_guest_write: apic=0, pin=0, old_irq=-1, new_irq=0 > (XEN) ioapic_guest_write: old_entry=00010900, new_entry=000009f0 > (XEN) ioapic_guest_write: Attempt to add IO-APIC pin for in-use IRQ! > (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19 > (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0 > (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19 > (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0 > (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > (XEN) ioapic_guest_write: apic=0, pin=23, old_irq=23, new_irq=23 > (XEN) ioapic_guest_write: old_entry=0000a9d0, new_entry=0001a9d0 > (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19 > (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0 > (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > (XEN) ioapic_guest_write: apic=0, pin=16, old_irq=16, new_irq=16 > (XEN) ioapic_guest_write: old_entry=0000a9b8, new_entry=0001a9b8 > (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > (XEN) ioapic_guest_write: apic=0, pin=18, old_irq=18, new_irq=18 > (XEN) ioapic_guest_write: old_entry=0000a921, new_entry=0001a921 > (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > > > Did anyone meet this issue? Is there any difference on build and installation between pvops dom0 and 2.6.18 dom0? Following is my instructions, pls correct me if something is wrong. Appreciate in advance. > > My build and installation instructions: > - cd xen-unstable.hg > - make world (linux-2.6-pvops.git will be cloned) > - make install > > My grub entry: > title Xen - pvops > root (hd0,2) > kernel /boot/xen.gz dom0_mem=512m > module /boot/vmlinuz-2.6-30.rc3-tip ro root=/dev/sda3 console=tty0 console=ttyS0 > > I also tried build pvops dom0 manually as follows, but it doesn''t help. > - cd linux-2.6-pvops.git > - make > - make modules_install > - make install >I am not quite sure if that is the correct way to recompile kernel, as sometimes I have some problems with Dom0 booting after that. I usually recompile Dom0 kernel this way: (from the root directory) # make linux-2.6-xen-config (to configure kernel options) # make linux-2.6-xen-build # make linux-2.6-xen-install Then dont forget to "mkinitramfs", of course Thanks, J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I don''t think this is an issue with out the kernel was compiled. In fact, all of the ways mentioned will build the pvops kernel properly. I have run into a similar problem with the kernel trying to add/remove/modify ioapic stuff as well (and have tried to compile the kernel in every possible way, but still get the same problem). I have a feeling it is an issue with the pvops kernel ioapic code and have spent some time trying to track it down, but haven''t found anything yet. The XCI 2.6.27 kernel works, though, so if you''re just looking for a more modern kernel than 2.6.18, then I suggest using that. Hopefully this issue can be resolved soon, though. I would prefer to develop against the pvops kernel now that it''s been selected as the xen-unstable default kernel. Patrick Jun Koi wrote:> On Thu, Jun 25, 2009 at 6:20 PM, Han, Weidong<weidong.han@intel.com> wrote: >> I tried with latest Xen unstable (c/s 19833) with latest pvops dom0 (commit 384a55c0). Booting will hang, following is the serial console output: >> >> (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen >> ) >> (XEN) Freed 128kB init memory. >> mapping kernel into physical memory >> Xen: setup ISA identity maps >> about to get started... >> (XEN) ioapic_guest_write: apic=0, pin=2, old_irq=0, new_irq=-1 >> (XEN) ioapic_guest_write: old_entry=000009f0, new_entry=00010900 >> (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use IRQ! >> (XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=-1 >> (XEN) ioapic_guest_write: old_entry=000009f1, new_entry=00010900 >> (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use IRQ! >> (XEN) ioapic_guest_write: apic=0, pin=0, old_irq=-1, new_irq=0 >> (XEN) ioapic_guest_write: old_entry=00010900, new_entry=000009f0 >> (XEN) ioapic_guest_write: Attempt to add IO-APIC pin for in-use IRQ! >> (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19 >> (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0 >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19 >> (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0 >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> (XEN) ioapic_guest_write: apic=0, pin=23, old_irq=23, new_irq=23 >> (XEN) ioapic_guest_write: old_entry=0000a9d0, new_entry=0001a9d0 >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19 >> (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0 >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> (XEN) ioapic_guest_write: apic=0, pin=16, old_irq=16, new_irq=16 (and in fact, doing a make world/install will >> (XEN) ioapic_guest_write: old_entry=0000a9b8, new_entry=0001a9b8 >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> (XEN) ioapic_guest_write: apic=0, pin=18, old_irq=18, new_irq=18 >> (XEN) ioapic_guest_write: old_entry=0000a921, new_entry=0001a921 >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >> >> >> Did anyone meet this issue? Is there any difference on build and installation between pvops dom0 and 2.6.18 dom0? Following is my instructions, pls correct me if something is wrong. Appreciate in advance. >> >> My build and installation instructions: >> - cd xen-unstable.hg >> - make world (linux-2.6-pvops.git will be cloned) >> - make install >> >> My grub entry: >> title Xen - pvops >> root (hd0,2) >> kernel /boot/xen.gz dom0_mem=512m >> module /boot/vmlinuz-2.6-30.rc3-tip ro root=/dev/sda3 console=tty0 console=ttyS0 >> >> I also tried build pvops dom0 manually as follows, but it doesn''t help. >> - cd linux-2.6-pvops.git >> - make >> - make modules_install >> - make install >> > > I am not quite sure if that is the correct way to recompile kernel, as > sometimes I have some problems with Dom0 booting after that. > > I usually recompile Dom0 kernel this way: (from the root directory) > > # make linux-2.6-xen-config (to configure kernel options) > # make linux-2.6-xen-build > # make linux-2.6-xen-install > > Then dont forget to "mkinitramfs", of course > > Thanks, > 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
Jun Koi wrote:> On Thu, Jun 25, 2009 at 6:20 PM, Han, Weidong<weidong.han@intel.com> > wrote: >> I tried with latest Xen unstable (c/s 19833) with latest pvops dom0 >> (commit 384a55c0). Booting will hang, following is the serial >> console output: >> >> (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch >> input to Xen ) (XEN) Freed 128kB init memory. >> mapping kernel into physical memory >> Xen: setup ISA identity maps >> about to get started... >> (XEN) ioapic_guest_write: apic=0, pin=2, old_irq=0, new_irq=-1 >> (XEN) ioapic_guest_write: old_entry=000009f0, new_entry=00010900 >> (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use >> IRQ! (XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=-1 >> (XEN) ioapic_guest_write: old_entry=000009f1, new_entry=00010900 >> (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use >> IRQ! (XEN) ioapic_guest_write: apic=0, pin=0, old_irq=-1, new_irq=0 >> (XEN) ioapic_guest_write: old_entry=00010900, new_entry=000009f0 >> (XEN) ioapic_guest_write: Attempt to add IO-APIC pin for in-use IRQ! >> (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19 >> (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0 >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use >> IRQ! (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19 >> (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0 >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use >> IRQ! (XEN) ioapic_guest_write: apic=0, pin=23, old_irq=23, new_irq=23 >> (XEN) ioapic_guest_write: old_entry=0000a9d0, new_entry=0001a9d0 >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use >> IRQ! (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19 >> (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0 >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use >> IRQ! (XEN) ioapic_guest_write: apic=0, pin=16, old_irq=16, new_irq=16 >> (XEN) ioapic_guest_write: old_entry=0000a9b8, new_entry=0001a9b8 >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use >> IRQ! (XEN) ioapic_guest_write: apic=0, pin=18, old_irq=18, new_irq=18 >> (XEN) ioapic_guest_write: old_entry=0000a921, new_entry=0001a921 >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use >> IRQ! >> >> >> Did anyone meet this issue? Is there any difference on build and >> installation between pvops dom0 and 2.6.18 dom0? Following is my >> instructions, pls correct me if something is wrong. Appreciate in >> advance. >> >> My build and installation instructions: >> - cd xen-unstable.hg >> - make world (linux-2.6-pvops.git will be cloned) >> - make install >> >> My grub entry: >> title Xen - pvops >> root (hd0,2) >> kernel /boot/xen.gz dom0_mem=512m >> module /boot/vmlinuz-2.6-30.rc3-tip ro root=/dev/sda3 >> console=tty0 console=ttyS0 >> >> I also tried build pvops dom0 manually as follows, but it doesn''t >> help. >> - cd linux-2.6-pvops.git >> - make >> - make modules_install >> - make install >> > > I am not quite sure if that is the correct way to recompile kernel, as > sometimes I have some problems with Dom0 booting after that. > > I usually recompile Dom0 kernel this way: (from the root directory) > > # make linux-2.6-xen-config (to configure kernel options) > # make linux-2.6-xen-build > # make linux-2.6-xen-install >I also tried this way (make linux-2.6-pvops-build), the problem is still there.> Then dont forget to "mkinitramfs", of courseYes, I always mkinitrd for it through "mkinitrd initrd-2.6-xen.img 2.6.18.8-xen". It can boot with manually built pvops dom0 on my another platform, but I found xend cannot be started, there is no directory xen under /proc. That means drivers/xen are not installed, althrough they are built. I just want to know anyone has successfully made Xen with pvops work, and can you share your instructions? Thanks. Regards, Weidong> > Thanks, > J_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Han, Weidong wrote:> It can boot with manually built pvops dom0 on my another platform, but I found xend cannot be started, there is no directory xen under /proc. That means drivers/xen are not installed, althrough they are built.Out of curiosity (and with the hope of being able to track down the problem, as I also suspect this a platform/cpu specific problem), what are the platforms you used: both the one that boots pvops and the one that doesn''t? Patrick _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Patrick Colp wrote:> Han, Weidong wrote: >> It can boot with manually built pvops dom0 on my another platform, >> but I found xend cannot be started, there is no directory xen under >> /proc. That means drivers/xen are not installed, althrough they are >> built. > > Out of curiosity (and with the hope of being able to track down the > problem, as I also suspect this a platform/cpu specific problem), > what are > the platforms you used: both the one that boots pvops and the one > that doesn''t? >I found the boot issue on my Q35, it can boot on my Nehalem. Regards, Weidong _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Han, Weidong wrote:> Patrick Colp wrote: >> Han, Weidong wrote: >>> It can boot with manually built pvops dom0 on my another platform, >>> but I found xend cannot be started, there is no directory xen under >>> /proc. That means drivers/xen are not installed, althrough they are >>> built. >> Out of curiosity (and with the hope of being able to track down the >> problem, as I also suspect this a platform/cpu specific problem), >> what are >> the platforms you used: both the one that boots pvops and the one >> that doesn''t? >> > > I found the boot issue on my Q35, it can boot on my Nehalem.What are the motherboard chipsets? Patrick _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Patrick Colp wrote:>> I found the boot issue on my Q35, it can boot on my Nehalem. > > What are the motherboard chipsets?Q35 *is* the chipset, for Nehalem its a Tylersburg chipset (either X58 or 55x0) Best regards, Christian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
hi, all, can you try to revert following two patches to see if any help? If it do fix the issue, I will look it tomorrow when back to office. --jyh changeset: 19809:16c2806b09c6 user: Keir Fraser <keir.fraser@citrix.com> date: Tue Jun 23 11:11:46 2009 +0100 files: xen/arch/x86/irq.c description: x86: Another assign_irq_vector() cleanup. Signed-off-by: Yunhong Jiang <yunhong.jiang@intel.com> changeset: 19804:07fea69baadc user: Keir Fraser <keir.fraser@citrix.com> date: Fri Jun 19 08:43:58 2009 +0100 files: xen/arch/x86/irq.c description: x86: Fix legacy irq allocation issue When try to assign vector for irq, we should not assign vector for legacy irq, which has fixed mapped irq<->vector relationship. Signed-off-by: Jiang, Yunhong <yunhong.jiang@intel.com>>-----Original Message----- >From: xen-devel-bounces@lists.xensource.com >[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of >Christian Tramnitz >Sent: 2009年6月25日 20:09 >To: xen-devel@lists.xensource.com >Subject: [Xen-devel] Re: Xen cannot boot with pvops dom0 > >Patrick Colp wrote: >>> I found the boot issue on my Q35, it can boot on my Nehalem. >> >> What are the motherboard chipsets? > >Q35 *is* the chipset, for Nehalem its a Tylersburg chipset (either X58 >or 55x0) > >Best regards, > Christian > > >_______________________________________________ >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
I tried reverting those two changesets with no real effect (I got an extra error message from Xen to do with something about the timer). I still have a sneaking suspicion the problem is with the Linux kernel and not Xen, but I could be wrong. Patrick Jiang, Yunhong wrote:> hi, all, can you try to revert following two patches to see if any help? > If it do fix the issue, I will look it tomorrow when back to office. > > --jyh > > > changeset: 19809:16c2806b09c6 > user: Keir Fraser <keir.fraser@citrix.com> > date: Tue Jun 23 11:11:46 2009 +0100 > files: xen/arch/x86/irq.c > description: > x86: Another assign_irq_vector() cleanup. > > Signed-off-by: Yunhong Jiang <yunhong.jiang@intel.com> > > > changeset: 19804:07fea69baadc > user: Keir Fraser <keir.fraser@citrix.com> > date: Fri Jun 19 08:43:58 2009 +0100 > files: xen/arch/x86/irq.c > description: > x86: Fix legacy irq allocation issue > > When try to assign vector for irq, we should not assign vector for > legacy irq, which has fixed mapped irq<->vector relationship. > > Signed-off-by: Jiang, Yunhong <yunhong.jiang@intel.com> >> -----Original Message----- >> From: xen-devel-bounces@lists.xensource.com >> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of >> Christian Tramnitz >> Sent: 2009年6月25日 20:09 >> To: xen-devel@lists.xensource.com >> Subject: [Xen-devel] Re: Xen cannot boot with pvops dom0 >> >> Patrick Colp wrote: >>>> I found the boot issue on my Q35, it can boot on my Nehalem. >>> What are the motherboard chipsets? >> Q35 *is* the chipset, for Nehalem its a Tylersburg chipset (either X58 >> or 55x0) >> >> Best regards, >> Christian >> >> >> _______________________________________________ >> 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
I think detailed output of dmesg (both xen and dom0) will be helpful. I checked the log again, and noticed following output. Seems there is IRQ source override for timer in the platform and dom0/xen have different idea of timer source in check_timer().>> (XEN) ioapic_guest_write: apic=0, pin=2, old_irq=0, new_irq=-1 >> (XEN) ioapic_guest_write: old_entry=000009f0, new_entry=00010900 >> (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use IRQ! >> (XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=-1 >> (XEN) ioapic_guest_write: old_entry=000009f1, new_entry=00010900 >> (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use IRQ! >> (XEN) ioapic_guest_write: apic=0, pin=0, old_irq=-1, new_irq=0 >> (XEN) ioapic_guest_write: old_entry=00010900, new_entry=000009f0Thanks Yunhong Jiang>-----Original Message----- >From: Patrick Colp [mailto:Patrick.Colp@citrix.com] >Sent: 2009年6月26日 17:38 >To: Jiang, Yunhong >Cc: Christian Tramnitz; xen-devel@lists.xensource.com >Subject: Re: [Xen-devel] Re: Xen cannot boot with pvops dom0 > >I tried reverting those two changesets with no real effect (I >got an extra error >message from Xen to do with something about the timer). > >I still have a sneaking suspicion the problem is with the >Linux kernel and not >Xen, but I could be wrong. > > >Patrick > > >Jiang, Yunhong wrote: >> hi, all, can you try to revert following two patches to see >if any help? >> If it do fix the issue, I will look it tomorrow when back to office. >> >> --jyh >> >> >> changeset: 19809:16c2806b09c6 >> user: Keir Fraser <keir.fraser@citrix.com> >> date: Tue Jun 23 11:11:46 2009 +0100 >> files: xen/arch/x86/irq.c >> description: >> x86: Another assign_irq_vector() cleanup. >> >> Signed-off-by: Yunhong Jiang <yunhong.jiang@intel.com> >> >> >> changeset: 19804:07fea69baadc >> user: Keir Fraser <keir.fraser@citrix.com> >> date: Fri Jun 19 08:43:58 2009 +0100 >> files: xen/arch/x86/irq.c >> description: >> x86: Fix legacy irq allocation issue >> >> When try to assign vector for irq, we should not assign vector for >> legacy irq, which has fixed mapped irq<->vector relationship. >> >> Signed-off-by: Jiang, Yunhong <yunhong.jiang@intel.com> >>> -----Original Message----- >>> From: xen-devel-bounces@lists.xensource.com >>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of >>> Christian Tramnitz >>> Sent: 2009年6月25日 20:09 >>> To: xen-devel@lists.xensource.com >>> Subject: [Xen-devel] Re: Xen cannot boot with pvops dom0 >>> >>> Patrick Colp wrote: >>>>> I found the boot issue on my Q35, it can boot on my Nehalem. >>>> What are the motherboard chipsets? >>> Q35 *is* the chipset, for Nehalem its a Tylersburg chipset >(either X58 >>> or 55x0) >>> >>> Best regards, >>> Christian >>> >>> >>> _______________________________________________ >>> 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
On 06/25/09 02:20, Han, Weidong wrote:> I tried with latest Xen unstable (c/s 19833) with latest pvops dom0 (commit 384a55c0). Booting will hang, following is the serial console output: > > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen > ) > (XEN) Freed 128kB init memory. > mapping kernel into physical memory > Xen: setup ISA identity maps > about to get started... > (XEN) ioapic_guest_write: apic=0, pin=2, old_irq=0, new_irq=-1 > (XEN) ioapic_guest_write: old_entry=000009f0, new_entry=00010900 > (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use IRQ! > (XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=-1 > (XEN) ioapic_guest_write: old_entry=000009f1, new_entry=00010900 > (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use IRQ! > (XEN) ioapic_guest_write: apic=0, pin=0, old_irq=-1, new_irq=0 > (XEN) ioapic_guest_write: old_entry=00010900, new_entry=000009f0 > (XEN) ioapic_guest_write: Attempt to add IO-APIC pin for in-use IRQ! > (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19 > (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0 > (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19 > (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0 > (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > (XEN) ioapic_guest_write: apic=0, pin=23, old_irq=23, new_irq=23 > (XEN) ioapic_guest_write: old_entry=0000a9d0, new_entry=0001a9d0 > (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19 > (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0 > (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > (XEN) ioapic_guest_write: apic=0, pin=16, old_irq=16, new_irq=16 > (XEN) ioapic_guest_write: old_entry=0000a9b8, new_entry=0001a9b8 > (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! > (XEN) ioapic_guest_write: apic=0, pin=18, old_irq=18, new_irq=18 > (XEN) ioapic_guest_write: old_entry=0000a921, new_entry=0001a921 > (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >The ioapic_guest_write messages are just noise, and have no bearing on the problem. Are there no more messages from the kernel after "about to get started"? The ioapic messages at least tell us it is getting quite a distance into the boot and discovering devices.> Did anyone meet this issue? Is there any difference on build and installation between pvops dom0 and 2.6.18 dom0? Following is my instructions, pls correct me if something is wrong. Appreciate in advance. > > My build and installation instructions: > - cd xen-unstable.hg > - make world (linux-2.6-pvops.git will be cloned) > - make install > > My grub entry: > title Xen - pvops > root (hd0,2) > kernel /boot/xen.gz dom0_mem=512m > module /boot/vmlinuz-2.6-30.rc3-tip ro root=/dev/sda3 console=tty0 console=ttyS0 >What happens if you have "console=hvc0 earlyprintk=xen ignore_loglevel" on the "module" line? You should get more output from the kernel. You might also want "console=com1,vga" on the Xen line. J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 06/25/09 02:37, Patrick Colp wrote:> I don''t think this is an issue with out the kernel was compiled. In > fact, all of the ways mentioned will build the pvops kernel properly. > I have run into a similar problem with the kernel trying to > add/remove/modify ioapic stuff as well (and have tried to compile the > kernel in every possible way, but still get the same problem). > > I have a feeling it is an issue with the pvops kernel ioapic code and > have spent some time trying to track it down, but haven''t found > anything yet.Those messages are just noise, and are harmless. They''re the kernel''s core drivers trying to take over various pieces of important hardware that Xen already owns. So far it has just been easier to let the kernel try and fail to take over the interrupts than to try to suppress the messages. J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge wrote:> On 06/25/09 02:20, Han, Weidong wrote: >> I tried with latest Xen unstable (c/s 19833) with latest pvops dom0 >> (commit 384a55c0). Booting will hang, following is the serial >> console output: >> >> (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch >> input to Xen ) (XEN) Freed 128kB init memory. >> mapping kernel into physical memory >> Xen: setup ISA identity maps >> about to get started... >> (XEN) ioapic_guest_write: apic=0, pin=2, old_irq=0, new_irq=-1 >> (XEN) ioapic_guest_write: old_entry=000009f0, new_entry=00010900 >> (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use >> IRQ! (XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=-1 >> (XEN) ioapic_guest_write: old_entry=000009f1, new_entry=00010900 >> (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use >> IRQ! (XEN) ioapic_guest_write: apic=0, pin=0, old_irq=-1, new_irq=0 >> (XEN) ioapic_guest_write: old_entry=00010900, new_entry=000009f0 >> (XEN) ioapic_guest_write: Attempt to add IO-APIC pin for in-use IRQ! >> (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19 >> (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0 >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use >> IRQ! (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19 >> (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0 >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use >> IRQ! (XEN) ioapic_guest_write: apic=0, pin=23, old_irq=23, new_irq=23 >> (XEN) ioapic_guest_write: old_entry=0000a9d0, new_entry=0001a9d0 >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use >> IRQ! (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19 >> (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0 >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use >> IRQ! (XEN) ioapic_guest_write: apic=0, pin=16, old_irq=16, new_irq=16 >> (XEN) ioapic_guest_write: old_entry=0000a9b8, new_entry=0001a9b8 >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use >> IRQ! (XEN) ioapic_guest_write: apic=0, pin=18, old_irq=18, new_irq=18 >> (XEN) ioapic_guest_write: old_entry=0000a921, new_entry=0001a921 >> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use >> IRQ! >> > > The ioapic_guest_write messages are just noise, and have no bearing on > the problem. Are there no more messages from the kernel after "about > to get started"? The ioapic messages at least tell us it is getting > quite a distance into the boot and discovering devices.Actually, pv-ops dom0 boot successfully. I remotely access my machine via serial console. Normally after dom0 boot, it display "login:" line. But serial console stops at ioapic_guest_write messages when boot pv_ops, I thought it''s hung. But I found xend still cannot be started. I got the following messages when I start it: [root@vt-randy ~]# xend start ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory) Traceback (most recent call last): File "/usr/sbin/xend", line 36, in ? from xen.xend.server import SrvDaemon File "usr/lib64/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 26, in ? File "usr/lib64/python2.4/site-packages/xen/xend/server/relocate.py", line 28, in ? File "usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line 35, in ? File "usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 20, in ? File "usr/lib64/python2.4/site-packages/xen/xend/image.py", line 46, in ? xen.lowlevel.xc.Error: (1, ''Internal error'', ''Could not obtain handle on privileged command interface (2 = No such file or directory)'')> >> Did anyone meet this issue? Is there any difference on build and >> installation between pvops dom0 and 2.6.18 dom0? Following is my >> instructions, pls correct me if something is wrong. Appreciate in >> advance. >> >> My build and installation instructions: >> - cd xen-unstable.hg >> - make world (linux-2.6-pvops.git will be cloned) >> - make install >> >> My grub entry: >> title Xen - pvops >> root (hd0,2) >> kernel /boot/xen.gz dom0_mem=512m >> module /boot/vmlinuz-2.6-30.rc3-tip ro root=/dev/sda3 >> console=tty0 console=ttyS0 >> > > What happens if you have "console=hvc0 earlyprintk=xen > ignore_loglevel" on the "module" line? You should get more output > from the kernel. You might also want "console=com1,vga" on the Xen > line. > > J_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
For what its worth, I''ve recently had significant issues building a good pvops Dom0 kernel. At first it wouldn''t boot (kernel oops) then it had an odd permission issue with /dev/pts/* that stopped xterm/bash from working. I went through the mud and found a configuration [1] that avoids whatever issues I was hitting. I thought about running a diff against this and whatever the default was, but there would be lots of noise due to many preference-specific changes (ex: built in all options specifically matching my hardware). Tom [1] http://web.cecs.pdx.edu/~dubuisst/pvops_dom0.config On Tue, Jun 30, 2009 at 7:43 PM, Han, Weidong<weidong.han@intel.com> wrote:> Jeremy Fitzhardinge wrote: >> On 06/25/09 02:20, Han, Weidong wrote: >>> I tried with latest Xen unstable (c/s 19833) with latest pvops dom0 >>> (commit 384a55c0). Booting will hang, following is the serial >>> console output: >>> >>> (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch >>> input to Xen ) (XEN) Freed 128kB init memory. >>> mapping kernel into physical memory >>> Xen: setup ISA identity maps >>> about to get started... >>> (XEN) ioapic_guest_write: apic=0, pin=2, old_irq=0, new_irq=-1 >>> (XEN) ioapic_guest_write: old_entry=000009f0, new_entry=00010900 >>> (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use >>> IRQ! (XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=-1 >>> (XEN) ioapic_guest_write: old_entry=000009f1, new_entry=00010900 >>> (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use >>> IRQ! (XEN) ioapic_guest_write: apic=0, pin=0, old_irq=-1, new_irq=0 >>> (XEN) ioapic_guest_write: old_entry=00010900, new_entry=000009f0 >>> (XEN) ioapic_guest_write: Attempt to add IO-APIC pin for in-use IRQ! >>> (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19 >>> (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0 >>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use >>> IRQ! (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19 >>> (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0 >>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use >>> IRQ! (XEN) ioapic_guest_write: apic=0, pin=23, old_irq=23, new_irq=23 >>> (XEN) ioapic_guest_write: old_entry=0000a9d0, new_entry=0001a9d0 >>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use >>> IRQ! (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19 >>> (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0 >>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use >>> IRQ! (XEN) ioapic_guest_write: apic=0, pin=16, old_irq=16, new_irq=16 >>> (XEN) ioapic_guest_write: old_entry=0000a9b8, new_entry=0001a9b8 >>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use >>> IRQ! (XEN) ioapic_guest_write: apic=0, pin=18, old_irq=18, new_irq=18 >>> (XEN) ioapic_guest_write: old_entry=0000a921, new_entry=0001a921 >>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use >>> IRQ! >>> >> >> The ioapic_guest_write messages are just noise, and have no bearing on >> the problem. Are there no more messages from the kernel after "about >> to get started"? The ioapic messages at least tell us it is getting >> quite a distance into the boot and discovering devices. > > Actually, pv-ops dom0 boot successfully. I remotely access my machine via serial console. Normally after dom0 boot, it display "login:" line. But serial console stops at ioapic_guest_write messages when boot pv_ops, I thought it''s hung. > > But I found xend still cannot be started. I got the following messages when I start it: > > [root@vt-randy ~]# xend start > ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory) > Traceback (most recent call last): > File "/usr/sbin/xend", line 36, in ? > from xen.xend.server import SrvDaemon > File "usr/lib64/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 26, in ? > File "usr/lib64/python2.4/site-packages/xen/xend/server/relocate.py", line 28, in ? > File "usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line 35, in ? > File "usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 20, in ? > File "usr/lib64/python2.4/site-packages/xen/xend/image.py", line 46, in ? > xen.lowlevel.xc.Error: (1, ''Internal error'', ''Could not obtain handle on privileged command interface (2 = No such file or directory)'') > > >> >>> Did anyone meet this issue? Is there any difference on build and >>> installation between pvops dom0 and 2.6.18 dom0? Following is my >>> instructions, pls correct me if something is wrong. Appreciate in >>> advance. >>> >>> My build and installation instructions: >>> - cd xen-unstable.hg >>> - make world (linux-2.6-pvops.git will be cloned) >>> - make install >>> >>> My grub entry: >>> title Xen - pvops >>> root (hd0,2) >>> kernel /boot/xen.gz dom0_mem=512m >>> module /boot/vmlinuz-2.6-30.rc3-tip ro root=/dev/sda3 >>> console=tty0 console=ttyS0 >>> >> >> What happens if you have "console=hvc0 earlyprintk=xen >> ignore_loglevel" on the "module" line? You should get more output >> from the kernel. You might also want "console=com1,vga" on the Xen >> line. >> >> 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
Han, Weidong wrote:> Jeremy Fitzhardinge wrote: >> On 06/25/09 02:20, Han, Weidong wrote: >>> I tried with latest Xen unstable (c/s 19833) with latest pvops dom0 >>> (commit 384a55c0). Booting will hang, following is the serial >>> console output: >>> >>> (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch >>> input to Xen ) (XEN) Freed 128kB init memory. >>> mapping kernel into physical memory >>> Xen: setup ISA identity maps >>> about to get started... >>> (XEN) ioapic_guest_write: apic=0, pin=2, old_irq=0, new_irq=-1 >>> (XEN) ioapic_guest_write: old_entry=000009f0, new_entry=00010900 >>> (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use >>> IRQ! (XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=-1 >>> (XEN) ioapic_guest_write: old_entry=000009f1, new_entry=00010900 >>> (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use >>> IRQ! (XEN) ioapic_guest_write: apic=0, pin=0, old_irq=-1, new_irq=0 >>> (XEN) ioapic_guest_write: old_entry=00010900, new_entry=000009f0 >>> (XEN) ioapic_guest_write: Attempt to add IO-APIC pin for in-use IRQ! >>> (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19 >>> (XEN) ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0 >>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use >>> IRQ! (XEN) ioapic_guest_write: apic=0, pin=19, old_irq=19, >>> new_irq=19 (XEN) ioapic_guest_write: old_entry=0000a9c0, >>> new_entry=0001a9c0 (XEN) ioapic_guest_write: Attempt to modify >>> IO-APIC pin for in-use IRQ! (XEN) ioapic_guest_write: apic=0, >>> pin=23, old_irq=23, new_irq=23 (XEN) ioapic_guest_write: >>> old_entry=0000a9d0, new_entry=0001a9d0 (XEN) ioapic_guest_write: >>> Attempt to modify IO-APIC pin for in-use IRQ! (XEN) >>> ioapic_guest_write: apic=0, pin=19, old_irq=19, new_irq=19 (XEN) >>> ioapic_guest_write: old_entry=0000a9c0, new_entry=0001a9c0 (XEN) >>> ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! >>> (XEN) ioapic_guest_write: apic=0, pin=16, old_irq=16, new_irq=16 >>> (XEN) ioapic_guest_write: old_entry=0000a9b8, new_entry=0001a9b8 >>> (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use >>> IRQ! (XEN) ioapic_guest_write: apic=0, pin=18, old_irq=18, >>> new_irq=18 (XEN) ioapic_guest_write: old_entry=0000a921, >>> new_entry=0001a921 (XEN) ioapic_guest_write: Attempt to modify >>> IO-APIC pin for in-use IRQ! >>> >> >> The ioapic_guest_write messages are just noise, and have no bearing >> on the problem. Are there no more messages from the kernel after >> "about to get started"? The ioapic messages at least tell us it is >> getting quite a distance into the boot and discovering devices. > > Actually, pv-ops dom0 boot successfully. I remotely access my machine > via serial console. Normally after dom0 boot, it display "login:" > line. But serial console stops at ioapic_guest_write messages when > boot pv_ops, I thought it''s hung. > > But I found xend still cannot be started. I got the following > messages when I start it: > > [root@vt-randy ~]# xend start > ERROR Internal error: Could not obtain handle on privileged command > interface (2 = No such file or directory) > Traceback (most recent call last): > File "/usr/sbin/xend", line 36, in ? > from xen.xend.server import SrvDaemon > File > "usr/lib64/python2.4/site-packages/xen/xend/server/SrvDaemon.py", > line 26, in ? File > "usr/lib64/python2.4/site-packages/xen/xend/server/relocate.py", > line 28, in ? File > "usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line 35, > in ? File > "usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line > 20, in ? File "usr/lib64/python2.4/site-packages/xen/xend/image.py", > line 46, in ? > xen.lowlevel.xc.Error: (1, ''Internal error'', ''Could not obtain handle > on privileged command interface (2 = No such file or directory)'') >After reading pv_ops wiki (http://wiki.xensource.com/xenwiki/XenParavirtOps), I solved it. It requires to add a line to /etc/fstab: none /proc/xen xenfs defaults 0 0. Now pv_ops dom0 works for me. Thanks. Regards, Weidong> >> >>> Did anyone meet this issue? Is there any difference on build and >>> installation between pvops dom0 and 2.6.18 dom0? Following is my >>> instructions, pls correct me if something is wrong. Appreciate in >>> advance. >>> >>> My build and installation instructions: >>> - cd xen-unstable.hg >>> - make world (linux-2.6-pvops.git will be cloned) >>> - make install >>> >>> My grub entry: >>> title Xen - pvops >>> root (hd0,2) >>> kernel /boot/xen.gz dom0_mem=512m >>> module /boot/vmlinuz-2.6-30.rc3-tip ro root=/dev/sda3 >>> console=tty0 console=ttyS0 >>> >> >> What happens if you have "console=hvc0 earlyprintk=xen >> ignore_loglevel" on the "module" line? You should get more output >> from the kernel. You might also want "console=com1,vga" on the Xen >> line. >> >> J_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hmmm, OK. Well, something is still going wrong. I find that adding things like irqpoll and/or acpi=noirq seems to help a bit. By that I mean that it gets further into the boot process before stalling. If I wait a while and press random keys/buttons (like Num Lock or the power button), then that seems to coax it into booting a little bit more, but I''ve never managed to get it to completely boot. The furthest I got was to where it tries to read the root filesystem. I could give you a dump of the boot-up messages, but aside from the ioapic stuff, there''s nothing out of the ordinary. Patrick Jeremy Fitzhardinge wrote:> On 06/25/09 02:37, Patrick Colp wrote: >> I don''t think this is an issue with out the kernel was compiled. In >> fact, all of the ways mentioned will build the pvops kernel properly. >> I have run into a similar problem with the kernel trying to >> add/remove/modify ioapic stuff as well (and have tried to compile the >> kernel in every possible way, but still get the same problem). >> >> I have a feeling it is an issue with the pvops kernel ioapic code and >> have spent some time trying to track it down, but haven''t found >> anything yet. > > Those messages are just noise, and are harmless. They''re the kernel''s > core drivers trying to take over various pieces of important hardware > that Xen already owns. So far it has just been easier to let the kernel > try and fail to take over the interrupts than to try to suppress the > messages. > > J_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 07/01/09 00:32, Patrick Colp wrote:> Hmmm, OK. Well, something is still going wrong. I find that adding > things like irqpoll and/or acpi=noirq seems to help a bit. By that I > mean that it gets further into the boot process before stalling. If I > wait a while and press random keys/buttons (like Num Lock or the power > button), then that seems to coax it into booting a little bit more, > but I''ve never managed to get it to completely boot. The furthest I > got was to where it tries to read the root filesystem. > > I could give you a dump of the boot-up messages, but aside from the > ioapic stuff, there''s nothing out of the ordinary.Well, it suggests something is going wrong with interrupt routing. It would be useful to get a full boot log for the kernel running both native and as dom0 for comparison purposes. J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 06/30/09 22:29, Han, Weidong wrote:> After reading pv_ops wiki (http://wiki.xensource.com/xenwiki/XenParavirtOps), I solved it. It requires to add a line to /etc/fstab: none /proc/xen xenfs defaults 0 0. > > Now pv_ops dom0 works for me. Thanks. >Good, thanks for letting me know. J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I''ve attached the boot logs for a normal boot and a xen boot. Patrick Jeremy Fitzhardinge wrote:> On 07/01/09 00:32, Patrick Colp wrote: >> Hmmm, OK. Well, something is still going wrong. I find that adding >> things like irqpoll and/or acpi=noirq seems to help a bit. By that I >> mean that it gets further into the boot process before stalling. If I >> wait a while and press random keys/buttons (like Num Lock or the power >> button), then that seems to coax it into booting a little bit more, >> but I''ve never managed to get it to completely boot. The furthest I >> got was to where it tries to read the root filesystem. >> >> I could give you a dump of the boot-up messages, but aside from the >> ioapic stuff, there''s nothing out of the ordinary. > > Well, it suggests something is going wrong with interrupt routing. It > would be useful to get a full boot log for the kernel running both > native and as dom0 for comparison purposes. > > J_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 07/01/09 00:32, Patrick Colp wrote:> Hmmm, OK. Well, something is still going wrong. I find that adding > things like irqpoll and/or acpi=noirq seems to help a bit. By that I > mean that it gets further into the boot process before stalling. If I > wait a while and press random keys/buttons (like Num Lock or the power > button), then that seems to coax it into booting a little bit more, > but I''ve never managed to get it to completely boot. The furthest I > got was to where it tries to read the root filesystem. > > I could give you a dump of the boot-up messages, but aside from the > ioapic stuff, there''s nothing out of the ordinary.Yeah, from those logs it looks OK. Was that a "coaxed" Xen boot? It certainly looks like lots of interrupts are being received properly (drives detected, usb probed, etc). Also, for a more direct comparison, what happens when you boot native with pci=nomsi? I assume it will work, but it will make the logs directly comparable; or maybe the system just doesn''t work without MSI?> Write protecting the kernel read-only data: 7936k > Loading, please wait... > Couldnt get a file descriptor referring to the consoleIs your initrd set up right? J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Here''s the boot log for a normal boot with pci=nomsi. The initrd should be setup properly. I built the kernel using the latest unstable and the normal linux make commands (make linux-2.6-pvops config|build|install), which should do the right thing. The Xen boot was an uncoaxed boot. It usually gets up to the point of loading Alsa (but this message doesn''t manage to get printed to the serial console, just to the screen attached to my test box). After that, it''s a matter of waiting and pushing keys/buttons to try to get it to keep going. It seems to have issues trying to read the harddrives as well. Patrick Jeremy Fitzhardinge wrote:> On 07/01/09 00:32, Patrick Colp wrote: >> Hmmm, OK. Well, something is still going wrong. I find that adding >> things like irqpoll and/or acpi=noirq seems to help a bit. By that I >> mean that it gets further into the boot process before stalling. If I >> wait a while and press random keys/buttons (like Num Lock or the power >> button), then that seems to coax it into booting a little bit more, >> but I''ve never managed to get it to completely boot. The furthest I >> got was to where it tries to read the root filesystem. >> >> I could give you a dump of the boot-up messages, but aside from the >> ioapic stuff, there''s nothing out of the ordinary. > > Yeah, from those logs it looks OK. Was that a "coaxed" Xen boot? It > certainly looks like lots of interrupts are being received properly > (drives detected, usb probed, etc). > > Also, for a more direct comparison, what happens when you boot native > with pci=nomsi? I assume it will work, but it will make the logs > directly comparable; or maybe the system just doesn''t work without MSI? > >> Write protecting the kernel read-only data: 7936k >> Loading, please wait... >> Couldnt get a file descriptor referring to the console > Is your initrd set up right? > > J_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel