| View previous topic :: View next topic |
| Author |
Message |
2bbionic
Apprentice
Joined: 24 Mar 2005
Posts: 152
|
 Posted: Fri Jan 23, 2009 12:35 am Post subject: |
 |
|
Hello,
i was very surprised about the work here done by andylyon.
My XEn works with a Intel DQ35MP Board; unfortunately i can't boot with the acutal 2.6.27-7 kernel. The server complains about missing disks :
| Code: | ata1: SATA link up 3.0 GPS (SStatus 123 Scontrol 300)
ata1: 00: qc timeout (cmd 0xec)
ata1: 00: failed to IDENTIFY (I/O error err_mask 0x4)
|
This message occurs for each of my 6 disks; and after that, kernel has panic 
I tried to boot like this:
| Code: | title XEN0-linux-2.6.27-xen-r5
root (hd0,0)
kernel /xen.gz
module /kernel-2.6.27-xen-r5 root=/dev/sda3 noreboot xencons=off pci=nomsi acpi=off apic=off
savedefault 2
|
but the result was the same...
Here are some additional infos:
| Code: | 00:00.0 Host bridge: Intel Corporation DRAM Controller (rev 02)
Subsystem: Intel Corporation Device 4f4a
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information <?>
00:02.0 VGA compatible controller: Intel Corporation Integrated Graphics Control ler (rev 02) (prog-if 00 [VGA controller])
Subsystem: Intel Corporation Device 4f4a
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at e8200000 (32-bit, non-prefetchable) [size=512K]
I/O ports at 2430 [size=8]
Memory at e0000000 (32-bit, prefetchable) [size=128M]
Memory at e8100000 (32-bit, non-prefetchable) [size=1M]
Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [d0] Power Management version 2
00:03.0 Communication controller: Intel Corporation MEI Controller (rev 02)
Subsystem: Intel Corporation Device 4f4a
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at e82a6100 (64-bit, non-prefetchable) [size=16]
Capabilities: [50] Power Management version 3
Capabilities: [8c] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network Connect ion (rev 02)
Subsystem: Intel Corporation Device 0001
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at e8280000 (32-bit, non-prefetchable) [size=128K]
Memory at e82a4000 (32-bit, non-prefetchable) [size=4K]
I/O ports at 2400 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Capabilities: [e0] Vendor Specific Information <?>
Kernel driver in use: e1000e
Kernel modules: e1000e
00:1a.0 USB Controller: Intel Corporation USB UHCI Controller #4 (rev 02) (prog- if 00 [UHCI])
Subsystem: Intel Corporation Device 4f4a
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at 20e0 [size=32]
Capabilities: [50] Vendor Specific Information <?>
Kernel driver in use: uhci_hcd
00:1a.1 USB Controller: Intel Corporation USB UHCI Controller #5 (rev 02) (prog- if 00 [UHCI])
Subsystem: Intel Corporation Device 4f4a
Flags: bus master, medium devsel, latency 0, IRQ 20
I/O ports at 20c0 [size=32]
Capabilities: [50] Vendor Specific Information <?>
Kernel driver in use: uhci_hcd
00:1a.2 USB Controller: Intel Corporation USB UHCI Controller #6 (rev 02) (prog- if 00 [UHCI])
Subsystem: Intel Corporation Device 4f4a
Flags: bus master, medium devsel, latency 0, IRQ 16
I/O ports at 20a0 [size=32]
Capabilities: [50] Vendor Specific Information <?>
Kernel driver in use: uhci_hcd
00:1a.7 USB Controller: Intel Corporation USB2 EHCI Controller #2 (rev 02) (prog -if 20 [EHCI])
Subsystem: Intel Corporation Device 4f4a
Flags: bus master, medium devsel, latency 0, IRQ 16
Memory at e82a5c00 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] Vendor Specific Information <?>
Kernel driver in use: ehci_hcd
00:1b.0 Audio device: Intel Corporation HD Audio Controller (rev 02)
Subsystem: Intel Corporation Device 0013
Flags: bus master, fast devsel, latency 0, IRQ 10
Memory at e82a0000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
00:1c.0 PCI bridge: Intel Corporation PCI Express Port 1 (rev 02) (prog-if 00 [N ormal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: e8300000-e83fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [90] Subsystem: Intel Corporation PCI Express Port 1
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport-driver
00:1c.1 PCI bridge: Intel Corporation PCI Express Port 2 (rev 02) (prog-if 00 [N ormal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
Memory behind bridge: e8400000-e84fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [90] Subsystem: Intel Corporation PCI Express Port 2
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport-driver
00:1c.2 PCI bridge: Intel Corporation PCI Express Port 3 (rev 02) (prog-if 00 [N ormal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: 00001000-00001fff
Memory behind bridge: e8000000-e80fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [90] Subsystem: Intel Corporation PCI Express Port 3
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport-driver
00:1c.3 PCI bridge: Intel Corporation PCI Express Port 4 (rev 02) (prog-if 00 [N ormal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
Memory behind bridge: e8500000-e85fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [90] Subsystem: Intel Corporation PCI Express Port 4
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport-driver
00:1c.4 PCI bridge: Intel Corporation PCI Express Port 5 (rev 02) (prog-if 00 [N ormal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
Memory behind bridge: e8600000-e86fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [90] Subsystem: Intel Corporation PCI Express Port 5
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport-driver
00:1d.0 USB Controller: Intel Corporation USB UHCI Controller #1 (rev 02) (prog- if 00 [UHCI])
Subsystem: Intel Corporation Device 4f4a
Flags: bus master, medium devsel, latency 0, IRQ 21
I/O ports at 2080 [size=32]
Capabilities: [50] Vendor Specific Information <?>
Kernel driver in use: uhci_hcd
00:1d.1 USB Controller: Intel Corporation USB UHCI Controller #2 (rev 02) (prog- if 00 [UHCI])
Subsystem: Intel Corporation Device 4f4a
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at 2060 [size=32]
Capabilities: [50] Vendor Specific Information <?>
Kernel driver in use: uhci_hcd
00:1d.2 USB Controller: Intel Corporation USB UHCI Controller #3 (rev 02) (prog- if 00 [UHCI])
Subsystem: Intel Corporation Device 4f4a
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at 2040 [size=32]
Capabilities: [50] Vendor Specific Information <?>
Kernel driver in use: uhci_hcd
00:1d.7 USB Controller: Intel Corporation USB2 EHCI Controller #1 (rev 02) (prog -if 20 [EHCI])
Subsystem: Intel Corporation Device 4f4a
Flags: bus master, medium devsel, latency 0, IRQ 21
Memory at e82a5800 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] Vendor Specific Information <?>
Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92) (prog-if 01 [Sub tractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=06, subordinate=06, sec-latency=32
Capabilities: [50] Subsystem: Intel Corporation Device 4f4a
00:1f.0 ISA bridge: Intel Corporation LPC Interface Controller (rev 02)
Subsystem: Intel Corporation Device 4f4a
Flags: bus master, medium devsel, latency 0
Capabilities: [e0] Vendor Specific Information <?>
00:1f.2 SATA controller: Intel Corporation 6 port SATA AHCI Controller (rev 02) (prog-if 01 [AHCI 1.0])
Subsystem: Intel Corporation Device 4f4a
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 20
I/O ports at 2428 [size=8]
I/O ports at 243c [size=4]
I/O ports at 2420 [size=8]
I/O ports at 2438 [size=4]
I/O ports at 2020 [size=32]
Memory at e82a5000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/4 Enable-
Capabilities: [70] Power Management version 3
Capabilities: [a8] SATA HBA <?>
Capabilities: [b0] Vendor Specific Information <?>
Kernel driver in use: ahci
00:1f.3 SMBus: Intel Corporation SMBus Controller (rev 02)
Subsystem: Intel Corporation Device 4f4a
Flags: medium devsel, IRQ 10
Memory at e82a6000 (64-bit, non-prefetchable) [size=256]
I/O ports at 2000 [size=32]
03:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6101 single-port PATA13 3 interface (rev b2) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: Marvell Technology Group Ltd. 88SE6101 single-port PATA133 in terface
Flags: bus master, fast devsel, latency 0, IRQ 10
I/O ports at 1018 [size=8]
I/O ports at 1024 [size=4]
I/O ports at 1010 [size=8]
I/O ports at 1020 [size=4]
I/O ports at 1000 [size=16]
Memory at e8000000 (32-bit, non-prefetchable) [size=512]
Capabilities: [48] Power Management version 2
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [e0] Express Legacy Endpoint, MSI 00
|
I will try with different settings in kernel, hopefully awaiting some hints for fixing 
Nevertheless - great job!
2bbionic
EDIT: Found my mistake, with this grub-container it's working:
| Code: |
root (hd0,0)
kernel /xen.gz pci=nomsi
module /kernel-2.6.27-xen-r5 root=/dev/sda3 noreboot xencons=off
savedefault 2
|
|
|
| Back to top |
|
 |
sgao
Tux's lil' helper
Joined: 22 Apr 2006
Posts: 149
|
| Posted: Sun Jan 25, 2009 8:25 pm Post subject: |
|
|
| _markd wrote: | | I have 2.6.27-r5 runnung on x86 and x86_64 machines for some time now without issues. I had to play around with the kernel config to make it compile though. I used gcc 4.1.2 for compilation since it's marked stable. |
I am having problem compiling 2.6.27-xen-r5 kernel. Can you post your kernel config? |
|
| Back to top |
|
|
_markd
n00b
Joined: 03 Jan 2004
Posts: 30
Location: Austria
|
| Posted: Mon Jan 26, 2009 3:46 pm Post subject: |
|
|
This is for 64 bit unprivileged domains: https://www.icg.tugraz.at/~dokter/xen-sources-2.6.27-r5-domU-64bit.config
_________________
-- Student of Telematics at University of Technology in Graz, Austria
-- Running Linux on x86(gentoo), PPC(gentoo), ARM(familiar), SPARC64(gentoo), Alpha(gentoo), MIPS(gentoo) and soon HPPA |
|
| Back to top |
|
|
sgao
Tux's lil' helper
Joined: 22 Apr 2006
Posts: 149
|
| Posted: Mon Feb 09, 2009 10:47 pm Post subject: |
|
|
Now I have 2.6.27-xen installed and running. However, during boot up, eth0 can't be brought up. The error says:
| Quote: | Waiting for peth0 to negotiate link:
Error: either "local" is duplicate, or "inet6" is a garbage. |
I am using xen/xen-tools-3.3.0. |
|
| Back to top |
|
|
_markd
n00b
Joined: 03 Jan 2004
Posts: 30
Location: Austria
|
| Posted: Tue Feb 10, 2009 11:05 am Post subject: |
|
|
| Quote: | Waiting for peth0 to negotiate link:
Error: either "local" is duplicate, or "inet6" is a garbage.
|
This is because the xen scripts fail to migrate your IPv6 addresses. Even if you don't use IPv6, as soon as you have support for it in the kernel, your interface gets a link-local address. You can either prevent the ipv6 module from loading or hack the xen network scripts (in /etc/xen/scripts)
hth,
_________________
-- Student of Telematics at University of Technology in Graz, Austria
-- Running Linux on x86(gentoo), PPC(gentoo), ARM(familiar), SPARC64(gentoo), Alpha(gentoo), MIPS(gentoo) and soon HPPA |
|
| Back to top |
|
|
2bbionic
Apprentice
Joined: 24 Mar 2005
Posts: 152
|
| Posted: Tue Mar 10, 2009 11:00 pm Post subject: |
|
|
Yesterday, i tried to migrate a XEN-Server to this adopted kernel. Unfortunately, i have some problems with my interrupts. The server contains a PCI-NIC directed to a DOMU and a ISDN-Card connected to another DOMU ( using XEN 3.2  )
With gentoo's 2.6.18 or 2.6.21, there are no problems with interrupts, everythin is working fine. The adopted kernel seems to be ok althoug, but activating the PCI-NIC in the DOMU creates a message "Disabling IRQ 16" and the server is not operable anymore - no LAN and no keyboard...
I tried to switch ACPI on or off without success and now, im in hope of some suggestions to get rid of this "interrupting problem 
Here's the output of lspci -vv with the 2.6.18-kernel:
| Code: | 00:00.0 Host bridge: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub (rev 02)
Subsystem: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information <?>
Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. Device 7267
Flags: bus master, fast devsel, latency 0, IRQ 10
Memory at cfe80000 (32-bit, non-prefetchable) [size=512K]
I/O ports at ec00 [size=8]
Memory at e0000000 (32-bit, prefetchable) [size=256M]
Memory at cfe40000 (32-bit, non-prefetchable) [size=256K]
Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Count=1/1 Enable-
Capabilities: [d0] Power Management version 2
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Count=1/1 Enable-
Capabilities: [90] Subsystem: Micro-Star International Co., Ltd. Device 7267
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport-driver
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 0000b000-0000bfff
Memory behind bridge: cfb00000-cfbfffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Count=1/1 Enable-
Capabilities: [90] Subsystem: Micro-Star International Co., Ltd. Device 7267
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport-driver
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01) (prog-if 00 [UHCI])
Subsystem: Micro-Star International Co., Ltd. Device 7267
Flags: bus master, medium devsel, latency 0, IRQ 20
I/O ports at e880 [size=32]
Kernel driver in use: uhci_hcd
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01) (prog-if 00 [UHCI])
Subsystem: Micro-Star International Co., Ltd. Device 7267
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at e800 [size=32]
Kernel driver in use: uhci_hcd
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01) (prog-if 00 [UHCI])
Subsystem: Micro-Star International Co., Ltd. Device 7267
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at e480 [size=32]
Kernel driver in use: uhci_hcd
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 01) (prog-if 00 [UHCI])
Subsystem: Micro-Star International Co., Ltd. Device 7267
Flags: bus master, medium devsel, latency 0, IRQ 16
I/O ports at e400 [size=32]
Kernel driver in use: uhci_hcd
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01) (prog-if 20 [EHCI])
Subsystem: Micro-Star International Co., Ltd. Device 7267
Flags: bus master, medium devsel, latency 0, IRQ 20
Memory at cfe3bc00 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=32
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: cfc00000-cfcfffff
Capabilities: [50] Subsystem: Micro-Star International Co., Ltd. Device 7267
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01)
Subsystem: Micro-Star International Co., Ltd. Device 7267
Flags: bus master, medium devsel, latency 0
Capabilities: [e0] Vendor Specific Information <?>
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01) (prog-if 8a [Master SecP PriP])
Subsystem: Micro-Star International Co., Ltd. Device 7267
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at <unassigned>
I/O ports at <unassigned>
I/O ports at <ignored>
I/O ports at <ignored>
I/O ports at ffa0 [size=16]
Kernel driver in use: PIIX_IDE
00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family) SATA IDE Controller (rev 01) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: Micro-Star International Co., Ltd. Device 7267
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 19
I/O ports at e080 [size=8]
I/O ports at e000 [size=4]
I/O ports at dc00 [size=8]
I/O ports at d880 [size=4]
I/O ports at d800 [size=16]
Capabilities: [70] Power Management version 2
Kernel driver in use: ata_piix
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
Subsystem: Micro-Star International Co., Ltd. Device 7267
Flags: medium devsel, IRQ 19
I/O ports at 0400 [size=32]
Kernel driver in use: i801_smbus
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
Subsystem: Micro-Star International Co., Ltd. Device 267c
Flags: bus master, fast devsel, latency 0, IRQ 17
I/O ports at b800 [size=256]
Memory at cfbff000 (64-bit, non-prefetchable) [size=4K]
Expansion ROM at cfbc0000 [disabled] [size=128K]
Capabilities: [40] Power Management version 2
Capabilities: [48] Vital Product Data <?>
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Count=1/2 Enable-
Capabilities: [60] Express Endpoint, MSI 00
Capabilities: [84] Vendor Specific Information <?>
Kernel driver in use: r8169
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Flags: bus master, medium devsel, latency 64, IRQ 16
I/O ports at c800 [size=256]
Memory at cfcffc00 (32-bit, non-prefetchable) [size=256]
Kernel driver in use: pciback
03:01.0 Network controller: Cologne Chip Designs GmbH ISDN network controller [HFC-PCI] (rev 02)
Subsystem: Cologne Chip Designs GmbH ISDN Board
Flags: bus master, medium devsel, latency 16, IRQ 17
I/O ports at cc00 [disabled] [size=8]
Memory at cfcff800 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 1
Kernel driver in use: pciback
|
... output is identical in 2.6.27-xen-r5
As you can see, the PCI-NIC and the ISDN-Card both are using pciback...
Has anyone some suggestions?
THX in advance
2bbionic |
|
| Back to top |
|
|
andylyon
n00b
Joined: 13 Jun 2006
Posts: 74
|
| Posted: Sat Mar 14, 2009 1:09 pm Post subject: |
|
|
I have used passthrough with pci and pci express devices, are you sure you selected the same passthru mode in the kernel config that you used with 2.6.18?
I select PCI Backend Mode = Passthrough, neither virtual pci or slot worked with the devices I use (usb and nic).
Andy |
|
| Back to top |
|
|
2bbionic
Apprentice
Joined: 24 Mar 2005
Posts: 152
|
| Posted: Sat Mar 14, 2009 2:46 pm Post subject: |
|
|
I only tried the Passthrough-Mode - the same as in 2.6.18. Is it worth trying the two alternatives?
2bbionic |
|
| Back to top |
|
|
andylyon
n00b
Joined: 13 Jun 2006
Posts: 74
|
| Posted: Sat Mar 14, 2009 7:11 pm Post subject: |
|
|
I doubt it, passthrough is the mode I've had most success with, strange that it doesnt work for you as I regularly use it passing a pci express usb2 and network cards to two different windows hvm's.
Are you running 64 bit Xen and dom0?
I will be releasing a new kernel next week, actually I will probably release a final 2.6.27 version and a new 2.6.29-rcX, suse Xen patches stalled at 2.6.27 for a while probably due to the merge of more pv_ops Xen into mainline, but they have resumed with xen-patches for 2.6.29 so thats the next version I will be doing. I suggest you try the new version and if you still have problems I will look into it.
Andy |
|
| Back to top |
|
|
2bbionic
Apprentice
Joined: 24 Mar 2005
Posts: 152
|
| Posted: Sat Mar 14, 2009 10:09 pm Post subject: |
|
|
No, i'm using the 32bit version in both DOM0 and DOMU. But i think, it's more a problem with the IRQs, because i can start the DOMU an initialize the card. But when there is some activity (internet connection via ADSL), there's the message "disabling interrupt 16" and that's it.
Nevertheless, thanks for you offer to take care of my problem. I will try the new kernel (SuSe seems to be VERY fast  ) as soon as it will be available.
2bbionic |
|
| Back to top |
|
|
trikolon
Apprentice
Joined: 04 Dec 2004
Posts: 297
Location: Erlangen
|
| Posted: Thu Mar 26, 2009 7:42 am Post subject: |
|
|
hi andy,
any news about the new ebuilds?
greets ben |
|
| Back to top |
|
|
andylyon
n00b
Joined: 13 Jun 2006
Posts: 74
|
|
| Back to top |
|
|
andylyon
n00b
Joined: 13 Jun 2006
Posts: 74
|
| Posted: Mon Apr 06, 2009 10:58 am Post subject: |
|
|
Uploaded 2.6.29-r1 (2.6.29.1).
Andy |
|
| Back to top |
|
|
2bbionic
Apprentice
Joined: 24 Mar 2005
Posts: 152
|
| Posted: Wed Apr 08, 2009 8:00 pm Post subject: |
|
|
Hello andylyon,
i just tried the new kernel - with success The issues i had with the locking system are gone and everything is working fine so far (32bit systems). One of my servers has the newest kernel (r1), the other one - the one with the hardware issues - has the older .29 release from you.
But there's one thing i noticed when a DOMU is booting. I have a lot of warnings like that:
| Code: | ------------[ cut here ]------------
WARNING: at drivers/firmware/dmi_scan.c:425 dmi_matches+0x99/0xa0()
dmi check: not initialized yet.
Modules linked in:
Pid: 1, comm: swapper Tainted: G W 2.6.29-xen #1
Call Trace:
[<c0123dd9>] warn_slowpath+0x99/0xc0
[<c031e5d2>] xencons_tx+0x12/0x20
[<c031ec0f>] handle_input+0x9f/0xc0
[<c01557c4>] handle_IRQ_event+0x24/0x90
[<c01572de>] handle_level_irq+0xde/0x140
[<c010646c>] do_IRQ+0x3c/0x90
[<c02d980f>] kobject_get+0xf/0x20
[<c031b514>] evtchn_do_upcall+0xd4/0x1f0
[<c0104932>] hypervisor_callback+0x46/0x4e
[<c01200d8>] sys_sched_getparam+0x48/0xa0
[<c0340639>] dmi_matches+0x99/0xa0
[<c04d01f0>] i8042_init+0x0/0xe0
[<c0340697>] dmi_check_system+0x17/0x50
[<c04d0252>] i8042_init+0x62/0xe0
[<c0102032>] _stext+0x32/0x1a0
[<c01c97d5>] create_proc_entry+0x55/0x90
[<c0157ce0>] register_irq_proc+0xb0/0xe0
[<c04b85fa>] kernel_init+0x14a/0x1a0
[<c04b84b0>] kernel_init+0x0/0x1a0
[<c0104a53>] kernel_thread_helper+0x7/0x10
---[ end trace 4eaa2a86a8e2da66 ]---
------------[ cut here ]------------
|
...in each of my DOMUs (kernels are different; 2.6.19, 2.6.21 and 2.6.29), and i don't know what's going wrong.
Nevertheless, after a few recurrences the system boots fine...
Greetings,
2bbionic |
|
| Back to top |
|
|
andylyon
n00b
Joined: 13 Jun 2006
Posts: 74
|
| Posted: Thu Apr 09, 2009 10:29 am Post subject: |
|
|
| 2bbionic wrote: | Hello andylyon,
i just tried the new kernel - with success The issues i had with the locking system are gone and everything is working fine so far (32bit systems). One of my servers has the newest kernel (r1), the other one - the one with the hardware issues - has the older .29 release from you.
But there's one thing i noticed when a DOMU is booting. I have a lot of warnings like that:
| Code: | ------------[ cut here ]------------
WARNING: at drivers/firmware/dmi_scan.c:425 dmi_matches+0x99/0xa0()
dmi check: not initialized yet.
Modules linked in:
Pid: 1, comm: swapper Tainted: G W 2.6.29-xen #1
Call Trace:
[<c0123dd9>] warn_slowpath+0x99/0xc0
[<c031e5d2>] xencons_tx+0x12/0x20
[<c031ec0f>] handle_input+0x9f/0xc0
[<c01557c4>] handle_IRQ_event+0x24/0x90
[<c01572de>] handle_level_irq+0xde/0x140
[<c010646c>] do_IRQ+0x3c/0x90
[<c02d980f>] kobject_get+0xf/0x20
[<c031b514>] evtchn_do_upcall+0xd4/0x1f0
[<c0104932>] hypervisor_callback+0x46/0x4e
[<c01200d8>] sys_sched_getparam+0x48/0xa0
[<c0340639>] dmi_matches+0x99/0xa0
[<c04d01f0>] i8042_init+0x0/0xe0
[<c0340697>] dmi_check_system+0x17/0x50
[<c04d0252>] i8042_init+0x62/0xe0
[<c0102032>] _stext+0x32/0x1a0
[<c01c97d5>] create_proc_entry+0x55/0x90
[<c0157ce0>] register_irq_proc+0xb0/0xe0
[<c04b85fa>] kernel_init+0x14a/0x1a0
[<c04b84b0>] kernel_init+0x0/0x1a0
[<c0104a53>] kernel_thread_helper+0x7/0x10
---[ end trace 4eaa2a86a8e2da66 ]---
------------[ cut here ]------------
|
...in each of my DOMUs (kernels are different; 2.6.19, 2.6.21 and 2.6.29), and i don't know what's going wrong.
Nevertheless, after a few recurrences the system boots fine...
Greetings,
2bbionic |
I think 2.6.29-r1 is the best one so far, I've not had a single problem with it on several different servers  .
You can get rid of the DMI messages by enabling CONFIG_EMBEDDED (Configure standard kernel features) in General Setup, then in Processor Type and Features disable "Enable DMI Scanning".
Andy |
|
| Back to top |
|
|
2bbionic
Apprentice
Joined: 24 Mar 2005
Posts: 152
|
| Posted: Sun Apr 12, 2009 11:35 am Post subject: |
|
|
Hello,
i just compiled the -r1 kernel but there's one additional issue when i try to compile:
| Code: | WARNING: modpost: Found 1 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
arch/x86/kernel/built-in.o: In function `timer_interrupt':
(.text+0x5245): undefined reference to `__udivdi3'
make: *** [.tmp_vmlinux1] Fehler 1
|
That error occurs in each machine. I see the problem with "timer_interrupt" -but i don't know which switch is corresponding to that...
2bbionic |
|
| Back to top |
|
|
andylyon
n00b
Joined: 13 Jun 2006
Posts: 74
|
| Posted: Sun Apr 12, 2009 12:02 pm Post subject: |
|
|
| 2bbionic wrote: | Hello,
i just compiled the -r1 kernel but there's one additional issue when i try to compile:
| Code: | WARNING: modpost: Found 1 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
arch/x86/kernel/built-in.o: In function `timer_interrupt':
(.text+0x5245): undefined reference to `__udivdi3'
make: *** [.tmp_vmlinux1] Fehler 1
|
That error occurs in each machine. I see the problem with "timer_interrupt" -but i don't know which switch is corresponding to that...
2bbionic |
Can you upload your .config to rapidshare or somewhere similar and I will look into this.
Andy |
|
| Back to top |
|
|
2bbionic
Apprentice
Joined: 24 Mar 2005
Posts: 152
|
|
| Back to top |
|
|
andylyon
n00b
Joined: 13 Jun 2006
Posts: 74
|
| Posted: Sun Apr 12, 2009 12:57 pm Post subject: |
|
|
I take it you are trying to build a 32 bit dom0 yes?
I will need to upgrade the kernel on my 32 bit laptop before I can look into this, but I should be able to do that today.
andy |
|
| Back to top |
|
|
2bbionic
Apprentice
Joined: 24 Mar 2005
Posts: 152
|
| Posted: Sun Apr 12, 2009 1:09 pm Post subject: |
|
|
| Yes, it's a 32 bit kernel, DOM0 and DOMU; both with PAE. |
|
| Back to top |
|
|
trooper_ryan
n00b
Joined: 07 Apr 2004
Posts: 74
|
| Posted: Sat Apr 18, 2009 1:22 pm Post subject: |
|
|
This is my first attempt at getting Xen running and I'm struggling a bit.
I've used Andy's 2.6.29-r1 ebuild with the xen patches v2, however xen crashes on me:
http://www.stooorage.com/show/86/103027_18-04-09_2304.jpg
Any suggestions would be appreciated as I'm at my wits end.
Also, I noticed that portage has xen-3.3.0, not 3.3.1. If you guys using more current ebuilds could you point me in the right direction?
Cheers,
trooper |
|
| Back to top |
|
|
andylyon
n00b
Joined: 13 Jun 2006
Posts: 74
|
| Posted: Sat Apr 18, 2009 1:45 pm Post subject: |
|
|
| trooper_ryan wrote: | This is my first attempt at getting Xen running and I'm struggling a bit.
I've used Andy's 2.6.29-r1 ebuild with the xen patches v2, however xen crashes on me:
http://www.stooorage.com/show/86/103027_18-04-09_2304.jpg
Any suggestions would be appreciated as I'm at my wits end.
Also, I noticed that portage has xen-3.3.0, not 3.3.1. If you guys using more current ebuilds could you point me in the right direction?
Cheers,
trooper |
Did you select the appropriate backwards compatibility option in the kernel config for Xen 3.3.0 ?
Its easy enough to copy the ebuild to build a newer version, I am using Xen 3.4.0-rc2, I pull the code using hg, move the .hg folder out of the source tree and then tar up the source into /usr/portage/distfiles/xen-3.4.0.tar.gz, then copy the existing ebuild to /usr/local/portage/app-emulation/xen/xen-3.4.0.ebuild , ebuild digest and emerge.
I have to use 3.4 as it has viridian support which stops smp windows from crashing.
Andy |
|
| Back to top |
|
|
trooper_ryan
n00b
Joined: 07 Apr 2004
Posts: 74
|
| Posted: Sun Apr 19, 2009 1:48 am Post subject: |
|
|
I had a look at arch/x86/mm/hypervisor.c:391 and saw this:
| Code: |
#ifdef CONFIG_HIGHPTE
BUG();
#endif
|
I unset this in my kernel .config and now it boots fine.
Thanks for the tip on using more current xen source! |
|
| Back to top |
|
|
_Razorblade_
n00b
Joined: 01 Jan 2004
Posts: 33
|
| Posted: Mon Apr 20, 2009 10:30 am Post subject: |
|
|
| 2bbionic wrote: | Hello,
i just compiled the -r1 kernel but there's one additional issue when i try to compile:
| Code: | WARNING: modpost: Found 1 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
arch/x86/kernel/built-in.o: In function `timer_interrupt':
(.text+0x5245): undefined reference to `__udivdi3'
make: *** [.tmp_vmlinux1] Fehler 1
|
That error occurs in each machine. I see the problem with "timer_interrupt" -but i don't know which switch is corresponding to that...
2bbionic |
This error is related to some optimizations gcc-4.3 does. This has been fixed several times, the current (supposed) fix is:
arch/x86/kernel/time_32-xen.c
| Code: |
/*
* GCC 4.3 can turn loops over an induction variable into division. We do
* not support arbitrary 64-bit division, and so must break the induction.
*/
#define clobber_induction_variable(v) asm ( "" : "+r" (v) )
static inline void __normalize_time(time_t *sec, s64 *nsec)
{
while (*nsec >= NSEC_PER_SEC) {
clobber_induction_variable(*nsec);
(*nsec) -= NSEC_PER_SEC;
(*sec)++;
}
while (*nsec < 0) {
clobber_induction_variable(*nsec);
(*nsec) += NSEC_PER_SEC;
(*sec)--;
}
}
|
But I can confirm it doesn't work on x86 (non-x86_64). Using an older gcc might be a workaround, at least it did the trick for me. |
|
| Back to top |
|
|
2bbionic
Apprentice
Joined: 24 Mar 2005
Posts: 152
|
| Posted: Mon Apr 20, 2009 8:37 pm Post subject: |
|
|
Thanks _Razorblade_ ; i will give it a try with an older gcc
2bbionic |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
