2:19 p.m.
I have built a new kernel (kernel-2.6.32.21-167.xendom0.fc12) at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2445999 or at the
repository http://repos.fedorapeople.org/repos/myoung/dom0-kernel/
This includes the net-sched-plug feature built as a module.
Michael Young
5:02 p.m.
New subject: xen and dom0 kernel builds
I have built a new kernel (kernel-2.6.32.21-168.xendom0.fc12) at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2477887 or at the
repository http://repos.fedorapeople.org/repos/myoung/dom0-kernel/
It includes fixes for the recent x86_64 local root exploit.
There are also some new builds of xen. The Fedora packages
xen-4.0.1-3.fc15 and xen-4.0.1-3.fc14 available via
http://koji.fedoraproject.org/koji/packageinfo?packageID=7 have some IRQ
fixes that solve a problem I was having with a keyboard and mouse and the
patch that disables xsave which was causing problems with HVM (both these
are from 4.0.2-rc1-pre). It also creates a symbolic link for qemu-dm from
the place it was in 3.4.x to where it is in 4.0.x for compatibility.
I also have a temporary test build xen-4.0.1-1.fc13.1 for Fedora 13 at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2478501 . This is
slightly misnamed as it is actually of 4.0.2-rc1-pre and includes the
fixes above. Note that he build system will delete those RPMs
automatically after a week or so.
Michael Young
11:12 p.m.
New subject: xen and dom0 kernel builds
On 09/24/2010 06:02 PM, M A Young wrote:
I have built a new kernel (kernel-2.6.32.21-168.xendom0.fc12) at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2477887 or at the
repositoryhttp://repos.fedorapeople.org/repos/myoung/dom0-kernel/
It includes fixes for the recent x86_64 local root exploit.
I also have a temporary test build xen-4.0.1-1.fc13.1 for Fedora 13 at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2478501 . This is
slightly misnamed as it is actually of 4.0.2-rc1-pre and includes the
fixes above. Note that he build system will delete those RPMs
automatically after a week or so.
I'm trying these two under f13, and not getting past udev starting on
the pv_ops kernel. (Xen oops) The non-xen kernel works fine on this
hardware. A pv_ops version from back around January was working well for
me, but I wanted to grab the x86_64 multilib-problem patched version.
That brought me to upgrade my xen-* versions, and f12 to f13.
The top of the stack has 'xen_force_evtchn_callback' on it. I see
udev's [OK] message, and then it very reliably crashes (I can get it to
tell me it's going down for reboot with a three-finger salute, but
nothing really happens).
Is a serial console the only way to get a good Xen log? Looking at this
board, I think I need to take the heatsink off the CPU to get at the
serial header, so I haven't tried yet...
-Bill
--
Bill McGonigle, Owner
BFC Computing, LLC
http://bfccomputing.com/
Telephone: +1.603.448.4440
Email, IM, VOIP: bill(a)bfccomputing.com
VCard: http://bfccomputing.com/vcard/bill.vcf
Social networks: bill_mcgonigle/bill.mcgonigle
8:48 a.m.
New subject: xen and dom0 kernel builds
On Sat, 25 Sep 2010, Bill McGonigle wrote:
I'm trying these two under f13, and not getting past udev
starting on the
pv_ops kernel. (Xen oops) The non-xen kernel works fine on this hardware. A
pv_ops version from back around January was working well for me, but I wanted
to grab the x86_64 multilib-problem patched version. That brought me to
upgrade my xen-* versions, and f12 to f13.
The top of the stack has 'xen_force_evtchn_callback' on it. I see udev's
[OK] message, and then it very reliably crashes (I can get it to tell me it's
going down for reboot with a three-finger salute, but nothing really
happens).
Is a serial console the only way to get a good Xen log? Looking at this
board, I think I need to take the heatsink off the CPU to get at the serial
header, so I haven't tried yet...
In your case it might be the only way to get the relevant information. I
also have a computer without a serial port, and have tried other two
things to get debugging information though they may not help in your case.
If the computer boots far enough you can get the xen serial output with
the xm dmesg or xl dmesg commands. Adding the console_to_ring and
conring_size=65536 options to the xen boot line may give more information.
I have also booted a customized xen dom0 live CD as a KVM guest where you
can redirect the console output to a file in the parent machine. That
does have the disadvantage that some of the hardware it sees is emulated
so it may behave differently.
If you haven't already seen them it is worth looking at
http://wiki.xen.org/xenwiki/XenParavirtOps
http://wiki.xen.org/xenwiki/XenSerialConsole
Michael Young
11:59 a.m.
New subject: xen and dom0 kernel builds
On Sat, 25 Sep 2010, Bill McGonigle wrote:
> I'm trying these two under f13, and not getting past udev starting on the
> pv_ops kernel. (Xen oops) The non-xen kernel works fine on this hardware.
> A pv_ops version from back around January was working well for me, but I
> wanted to grab the x86_64 multilib-problem patched version. That brought me
> to upgrade my xen-* versions, and f12 to f13.
>
> The top of the stack has 'xen_force_evtchn_callback' on it. I see udev's
> [OK] message, and then it very reliably crashes (I can get it to tell me
> it's going down for reboot with a three-finger salute, but nothing really
> happens).
I had a further thought - can you run rpm -V xen-runtime and see if it
reports anything. In particular there are two files
/etc/udev/rules.d/xen-backend.rules and /etc/udev/rules.d/xend.rules that
are related to udev setup of xen and if you modified them prior to the
update then you might have an out-of-date configuration.
Michael Young
10:02 p.m.
New subject: xen and dom0 kernel builds
On 09/25/2010 09:48 AM, M A Young wrote:
In your case it might be the only way to get the relevant
information. I
also have a computer without a serial port, and have tried other two
things to get debugging information though they may not help in your case.
OK, after much futzing around, I realized the IDC10->DB9M adapters I had on-hand are
all improperly wired ('DTK-type' vs. needed 'AT-Everest' type) for this
mobo. I put in an order for a new one and will get back to it in a couple days (unless I
get the soldering iron out first...).
I had a further thought - can you run rpm -V xen-runtime and
see if it reports anything. In particular there are two files
/etc/udev/rules.d/xen-backend.rules and /etc/udev/rules.d/xend.rules
that are related to udev setup of xen and if you modified them prior to
the update then you might have an out-of-date configuration.
Ah, good thought - that was true but fixing it to be current with
xen-runtime-4.0.1-1.fc13.1.x86_64 didn't help this problem. I thought that if
udev/rules.d/xen* was causing a problem, removing those files might let the boot succeed.
It didn't. I don't know if that means anything or not.
I'll post the log here asap.
Thanks,
-Bill
--
Bill McGonigle, Owner
BFC Computing, LLC
http://bfccomputing.com/
Telephone: +1.603.448.4440
Email, IM, VOIP: bill(a)bfccomputing.com
VCard: http://bfccomputing.com/vcard/bill.vcf
Social networks: bill_mcgonigle/bill.mcgonigle
2:44 p.m.
New subject: xen and dom0 kernel builds
On 09/25/2010 09:48 AM, M A Young wrote:
In your case it might be the only way to get the relevant information.
OK, new backplate works like a charm, appending the serial log.
Now that the messages aren't mostly scrolled off the screen (can I get a better VGA
mode than 80x25 under Xen?), I saw more information which led me to find this thread:
http://lists.xensource.com/archives/html/xen-devel/2010-09/msg01482.html
In my case I don't really want to constrain dom0's memory on this machine, yet
(it's still running services that ideally would be moved to a DomU but the machine is
a bit core-starved).
This is an x86_64 dom0. grub for this boot is:
kernel /xen.gz dom0_max_vcpus=1 dom0_vcpus_pin loglvl=all guest_loglvl=all com1=9600,8n1
sync_console console_to_ring conring_size=65536 console=com1
module /vmlinuz-2.6.32.21-168.xendom0.fc12.x86_64 ro root=LABEL=librescu-root selinux=0
SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us rootflags=data=journal acpi=off
earlyprintk=xen console=hvc0 nomodeset
module /initramfs-2.6.32.21-168.xendom0.fc12.x86_64.img
-Bill
--
Bill McGonigle, Owner
BFC Computing, LLC
http://bfccomputing.com/
Telephone: +1.603.448.4440
Email, IM, VOIP: bill(a)bfccomputing.com
VCard: http://bfccomputing.com/vcard/bill.vcf
Social networks: bill_mcgonigle/bill.mcgonigle
---8<-----8<---- BEGIN SERIAL LOG ---8<-----8<----
Press any key to continue.
Press any key to continue.
__ __
\ \/ /___ _ __
\ // _ \ '_ \
/ \ __/ | | |
/_/\_\___|_| |_|
_ _ ___ ____ _ _ __ _ _____
| || | / _ \ |___ \ _ __ ___/ | _ __ _ __ ___ / | / _| ___/ |___ /
| || |_| | | | __) |__| '__/ __| |__| '_ \| '__/ _ \__| | | |_ / __| | |_ \
|__ _| |_| | / __/|__| | | (__| |__| |_) | | | __/__| |_| _| (__| |___) |
|_|(_)___(_)_____| |_| \___|_| | .__/|_| \___| |_(_)_| \___|_|____(_)
|_|
_
/ |
| |
| |
|_|
(XEN) Xen version 4.0.2-rc1-pre (mockbuild@(none)) (gcc version 4.4.4 20100630 (Red Hat
4.4.4-10) (GCC) ) Mon Sep 20 23:05:29 UTC 2010
(XEN) Latest ChangeSet: unavailable
(XEN) Console output is synchronous.
(XEN) Bootloader: GNU GRUB 0.97
(XEN) Command line: dom0_max_vcpus=1 dom0_vcpus_pin loglvl=all guest_loglvl=all
com1=9600,8n1 sync_console console_to_ring conring_size=65536 console=com1
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN) Found 0 MBR signatures
(XEN) Found 6 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009b800 (usable)
(XEN) 000000000009b800 - 00000000000a0000 (reserved)
(XEN) 00000000000e4000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000dff70000 (usable)
(XEN) 00000000dff70000 - 00000000dff88000 (ACPI data)
(XEN) 00000000dff88000 - 00000000dffd0000 (ACPI NVS)
(XEN) 00000000dffd0000 - 00000000e0000000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000fff00000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000220000000 (usable)
(XEN) ACPI: RSDP 000FB160, 0024 (r2 ACPIAM)
(XEN) ACPI: XSDT DFF70100, 005C (r1 A_M_I_ OEMXSDT 8000904 MSFT 97)
(XEN) ACPI: FACP DFF70290, 00F4 (r3 A_M_I_ OEMFACP 8000904 MSFT 97)
(XEN) ACPI: DSDT DFF70440, AEE4 (r1 A1276 A1276001 1 INTL 20060113)
(XEN) ACPI: FACS DFF88000, 0040
(XEN) ACPI: APIC DFF70390, 006C (r1 A_M_I_ OEMAPIC 8000904 MSFT 97)
(XEN) ACPI: MCFG DFF70400, 003C (r1 A_M_I_ OEMMCFG 8000904 MSFT 97)
(XEN) ACPI: OEMB DFF88040, 0089 (r1 A_M_I_ AMI_OEM 8000904 MSFT 97)
(XEN) ACPI: HPET DFF7B330, 0038 (r1 A_M_I_ OEMHPET 8000904 MSFT 97)
(XEN) ACPI: OSFR DFF7B370, 00B0 (r1 A_M_I_ OEMOSFR 8000904 MSFT 97)
(XEN) ACPI: SSDT DFF88550, 0A7C (r1 DpgPmm CpuPm 12 INTL 20060113)
(XEN) System RAM: 8191MB (8387628kB)
(XEN) No NUMA configuration found
(XEN) Faking a node at 0000000000000000-0000000220000000
(XEN) Domain heap initialised
(XEN) found SMP MP-table at 000ff780
(XEN) DMI present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x808
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[804,0], pm1x_evt[800,0]
(XEN) ACPI: wakeup_vec[dff8800c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 6:15 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 6:15 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled)
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) ACPI: HPET id: 0x8086a301 base: 0xfed00000
(XEN) PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
(XEN) PCI: Not using MMCONFIG.
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2133.484 MHz processor.
(XEN) Initing memory sharing.
(XEN) VMX: Supported advanced features:
(XEN) - APIC TPR shadow
(XEN) - MSR direct-access bitmap
(XEN) HVM: ASIDs disabled.
(XEN) HVM: VMX enabled
(XEN) Intel machine check reporting enabled
(XEN) I/O virtualisation disabled
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
�(XEN) Allocated console ring of 65536 KiB.
(XEN) Brought up 2 CPUs
(XEN) microcode.c:73:d32767 microcode: CPU1 resumed
(XEN) HPET: 4 timers in total, 0 timers will be used for broadcast
(XEN) ACPI sleep modes: S3
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1b36000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000208000000->0000000210000000 (1990462 pages to be
allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff81b36000
(XEN) Init. ramdisk: ffffffff81b36000->ffffffff83970c00
(XEN) Phys-Mach map: ffffffff83971000->ffffffff848e09f0
(XEN) Start info: ffffffff848e1000->ffffffff848e14b4
(XEN) Page tables: ffffffff848e2000->ffffffff8490b000
(XEN) Boot stack: ffffffff8490b000->ffffffff8490c000
(XEN) TOTAL: ffffffff80000000->ffffffff84c00000
(XEN) ENTRY ADDRESS: ffffffff817fb200
(XEN) Dom0 has maximum 1 VCPUs
(XEN) Scrubbing Free RAM: .done.
(XEN) trace.c:89:d32767 calc_tinfo_first_offset: NR_CPUs 128, offset_in_bytes 258,
t_info_first_offset 65
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) **********************************************
(XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS
(XEN) ******* This option is intended to aid debugging of Xen by ensuring
(XEN) ******* that all output is synchronously delivered on the serial line.
(XEN) ******* However it can introduce SIGNIFICANT latencies and affect
(XEN) ******* timekeeping. It is NOT recommended for production use!
(XEN) **********************************************
(XEN) 3... 2... 1...
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to
Xen)
(XEN) Freed 184kB init memory.
mapping kernel into physical memory
Xen: setup ISA identity maps
about to get started...
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.32.21-168.xendom0.fc12.x86_64 (mockbuild(a)x86-10.phx2.fedoraproject.org)
(gcc version 4.4.4 20100630 (Red Hat 4.4.4-10) (GCC) ) #1 SMP Mon Sep 20 19:32:37 UTC
2010
Command line: ro root=LABEL=librescu-root selinux=0 SYSFONT=latarcyrheb-sun16
LANG=en_US.UTF-8 KEYTABLE=us rootflags=data=journal acpi=off earlyprintk=xen console=hvc0
nomodeset
KERNEL supported cpus:
Intel GenuineIntel
AMD AuthenticAMD
Centaur CentaurHauls
xen_release_chunk: looking at area pfn e0000-fec00: 125952 pages freed
xen_release_chunk: looking at area pfn fec01-fee00: 511 pages freed
xen_release_chunk: looking at area pfn fee01-fff00: 4351 pages freed
released 130814 pages of unused memory
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 000000000009b800 (usable)
Xen: 000000000009b800 - 0000000000100000 (reserved)
Xen: 0000000000100000 - 00000000dff70000 (usable)
Xen: 00000000dff70000 - 00000000dff88000 (ACPI data)
Xen: 00000000dff88000 - 00000000dffd0000 (ACPI NVS)
Xen: 00000000dffd0000 - 00000000e0000000 (reserved)
Xen: 00000000fec00000 - 00000000fec01000 (reserved)
Xen: 00000000fee00000 - 00000000fee01000 (reserved)
Xen: 00000000fff00000 - 0000000100000000 (reserved)
Xen: 0000000100000000 - 00000001edf3e000 (usable)
bootconsole [xenboot0] enabled
DMI present.
AMI BIOS detected: BIOS may corrupt low RAM, working around it.
last_pfn = 0x1edf3e max_arch_pfn = 0x400000000
x86 PAT enabled: cpu 0, old 0x50100070406, new 0x7010600070106
last_pfn = 0xdff70 max_arch_pfn = 0x400000000
init_memory_mapping: 0000000000000000-00000000dff70000
init_memory_mapping: 0000000100000000-00000001edf3e000
RAMDISK: 01b36000 - 03970c00
No NUMA configuration found
Faking a node at 0000000000000000-00000001edf3e000
Bootmem setup node 0 0000000000000000-00000001edf3e000
NODE_DATA [0000000000010000 - 0000000000025fff]
bootmap [0000000000026000 - 0000000000063be7] pages 3e
(10 early reservations) ==> bootmem [0000000000 - 01edf3e000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [00048e2000 - 000490b000] XEN PAGETABLES ==> [00048e2000 - 000490b000]
#2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000]
#3 [0001000000 - 0001a0cfe8] TEXT DATA BSS ==> [0001000000 - 0001a0cfe8]
#4 [0001b36000 - 0003970c00] RAMDISK ==> [0001b36000 - 0003970c00]
#5 [0003971000 - 00048e2000] XEN START INFO ==> [0003971000 - 00048e2000]
#6 [0100000000 - 0151fc0000] XEN EXTRA ==> [0100000000 - 0151fc0000]
#7 [0001a0d000 - 0001a1e20c] BRK ==> [0001a0d000 - 0001a1e20c]
#8 [0000100000 - 00007d9000] PGTABLE ==> [0000100000 - 00007d9000]
#9 [000490b000 - 000507f000] PGTABLE ==> [000490b000 - 000507f000]
found SMP MP-table at [ffff8800000ff780] ff780
Zone PFN ranges:
DMA 0x00000010 -> 0x00001000
DMA32 0x00001000 -> 0x00100000
Normal 0x00100000 -> 0x001edf3e
Movable zone start PFN for each node
early_node_map[3] active PFN ranges
0: 0x00000010 -> 0x0000009b
0: 0x00000100 -> 0x000dff70
0: 0x00100000 -> 0x001edf3e
SFI: Simple Firmware Interface v0.7 http://simplefirmware.org
Intel MultiProcessor Specification v1.4
MPTABLE: OEM ID:
MPTABLE: Product ID: TURBO
MPTABLE: APIC at: 0xFEE00000
I/O APIC #2 Version 32 at 0xFEC00000.
Processors: 1
SMP: Allowing 1 CPUs, 0 hotplug CPUs
PM: Registered nosave memory: 000000000009b000 - 000000000009c000
PM: Registered nosave memory: 000000000009c000 - 0000000000100000
PM: Registered nosave memory: 00000000dff70000 - 00000000dff88000
PM: Registered nosave memory: 00000000dff88000 - 00000000dffd0000
PM: Registered nosave memory: 00000000dffd0000 - 00000000e0000000
PM: Registered nosave memory: 00000000e0000000 - 00000000fec00000
PM: Registered nosave memory: 00000000fec00000 - 00000000fec01000
PM: Registered nosave memory: 00000000fec01000 - 00000000fee00000
PM: Registered nosave memory: 00000000fee00000 - 00000000fee01000
PM: Registered nosave memory: 00000000fee01000 - 00000000fff00000
PM: Registered nosave memory: 00000000fff00000 - 0000000100000000
Allocating PCI resources starting at e0000000 (gap: e0000000:1ec00000)
Booting paravirtualized kernel on Xen
Xen version: 4.0.2-rc1-pre (preserve-AD) (dom0)
NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:1 nr_node_ids:1
PERCPU: Embedded 30 pages/cpu @ffff88000b56c000 s90392 r8192 d24296 u122880
pcpu-alloc: s90392 r8192 d24296 u122880 alloc=30*4096
pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1862479
Policy zone: Normal
Kernel command line: ro root=LABEL=librescu-root selinux=0 SYSFONT=latarcyrheb-sun16
LANG=en_US.UTF-8 KEYTABLE=us rootflags=data=journal acpi=off earlyprintk=xen console=hvc0
nomodeset
PID hash table entries: 4096 (order: 3, 32768 bytes)
Initializing CPU#0
DMA: Placing 64MB software IO TLB between ffff88000b593000 - ffff88000f593000
DMA: software IO TLB at phys 0xb593000 - 0xf593000
xen_swiotlb_fixup: buf=ffff88000b593000 size=67108864
xen_swiotlb_fixup: buf=ffff88000f5f3000 size=32768
Memory: 5981732k/8092920k available (4491k kernel code, 525332k absent, 1585856k reserved,
3580k data, 944k init)
SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:4352 nr_irqs:512
Console: colour VGA+ 80x25
console [hvc0] enabled, bootconsole disabled
console [hvc0] enabled, bootconsole disabled
allocated 76021760 bytes of page_cgroup
please try 'cgroup_disable=memory' option if you don't want memory cgroups
installing Xen timer for CPU 0
Detected 2133.484 MHz processor.
Calibrating delay loop (skipped), value calculated using timer frequency.. 4266.96
BogoMIPS (lpj=2133484)
Security Framework initialized
SELinux: Disabled at boot.
Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
Mount-cache hash table entries: 256
Initializing cgroup subsys ns
Initializing cgroup subsys cpuacct
Initializing cgroup subsys memory
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
Initializing cgroup subsys net_cls
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU 0/0x0 -> Node 0
CPU: Unsupported number of siblings 2
mce: CPU supports 6 MCE banks
Performance Events: unsupported p6 CPU model 15 no PMU driver, software events only.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 34k freed
ftrace: converting mcount calls to 0f 1f 44 00 00
ftrace: allocating 23217 entries in 92 pages
Brought up 1 CPUs
devtmpfs: initialized
Grant table initialized
regulator: core version 0.5
Time: 18:51:39 Date: 09/29/10
NET: Registered protocol family 16
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ACPI: Interpreter disabled.
xen_balloon: Initialising balloon driver with page order 0.
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Probing PCI hardware
pci 0000:00:06.0: PME# supported from D0 D3hot D3cold
pci 0000:00:06.0: PME# disabled
pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1a.7: PME# disabled
pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.0: PME# disabled
pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.2: PME# disabled
pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.5: PME# disabled
pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.7: PME# disabled
pci 0000:00:1f.0: quirk: region 0800-087f claimed by ICH6 ACPI/GPIO/TCO
pci 0000:00:1f.0: quirk: region 0500-053f claimed by ICH6 GPIO
pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0294 (mask 0003)
pci 0000:00:1f.0: ICH7 LPC Generic IO decode 3 PIO at 4700 (mask 001f)
pci 0000:00:1f.2: PME# supported from D3hot
pci 0000:00:1f.2: PME# disabled
pci 0000:01:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with
'pcie_aspm=force'
pci 0000:03:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with
'pcie_aspm=force'
pci 0000:02:00.0: PME# supported from D3hot D3cold
pci 0000:02:00.0: PME# disabled
pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with
'pcie_aspm=force'
pci 0000:00:1e.0: transparent bridge
(XEN) PCI add device 00:00.0
(XEN) PCI add device 00:06.0
(XEN) PCI add device 00:1a.0
(XEN) PCI add device 00:1a.1
(XEN) PCI add device 00:1a.2
(XEN) PCI add device 00:1a.7
(XEN) PCI add device 00:1c.0
(XEN) PCI add device 00:1c.2
(XEN) PCI add device 00:1c.5
(XEN) PCI add device 00:1d.0
(XEN) PCI add device 00:1d.1
(XEN) PCI add device 00:1d.2
(XEN) PCI add device 00:1d.7
(XEN) PCI add device 00:1e.0
(XEN) PCI add device 00:1f.0
(XEN) PCI add device 00:1f.2
(XEN) PCI add device 00:1f.3
(XEN) PCI add device 01:00.0
(XEN) PCI add device 03:00.0
(XEN) PCI add device 02:00.0
(XEN) PCI add device 05:00.0
vgaarb: device added: PCI:0000:05:00.0,decodes=io+mem,owns=io+mem,locks=none
pci 0000:00:1f.0: PIIX/ICH IRQ router [8086:3a16]
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
Switching to clocksource xen
pnp: PnP ACPI: disabled
pci 0000:05:00.0: BAR 6: address space collision on of device [0xfebe0000-0xfebfffff]
pci 0000:00:06.0: PCI bridge, secondary bus 0000:01
pci 0000:00:06.0: IO window: 0xc000-0xcfff
pci 0000:00:06.0: MEM window: 0xfca00000-0xfcdfffff
pci 0000:00:06.0: PREFETCH window: disabled
pci 0000:00:1c.0: PCI bridge, secondary bus 0000:04
pci 0000:00:1c.0: IO window: 0x1000-0x1fff
pci 0000:00:1c.0: MEM window: 0xe0000000-0xe03fffff
pci 0000:00:1c.0: PREFETCH window: 0x000000eff00000-0x000000efffffff
pci 0000:00:1c.2: PCI bridge, secondary bus 0000:03
pci 0000:00:1c.2: IO window: 0xe000-0xefff
pci 0000:00:1c.2: MEM window: 0xfcf00000-0xfcffffff
pci 0000:00:1c.2: PREFETCH window: 0x000000e0400000-0x000000e05fffff
pci 0000:00:1c.5: PCI bridge, secondary bus 0000:02
pci 0000:00:1c.5: IO window: 0xd000-0xdfff
pci 0000:00:1c.5: MEM window: 0xfce00000-0xfcefffff
pci 0000:00:1c.5: PREFETCH window: 0x000000e0600000-0x000000e07fffff
pci 0000:00:1e.0: PCI bridge, secondary bus 0000:05
pci 0000:00:1e.0: IO window: disabled
pci 0000:00:1e.0: MEM window: 0xfd000000-0xfebfffff
pci 0000:00:1e.0: PREFETCH window: 0x000000f0000000-0x000000f7ffffff
pci 0000:00:06.0: found PCI INT A -> IRQ 10
pci 0000:00:06.0: sharing IRQ 10 with 0000:00:1a.0
pci 0000:00:06.0: sharing IRQ 10 with 0000:00:1c.5
pci 0000:00:06.0: sharing IRQ 10 with 0000:01:00.0
pci 0000:00:06.0: sharing IRQ 10 with 0000:05:00.0
pci 0000:00:1c.0: enabling device (0106 -> 0107)
pci 0000:00:1c.0: found PCI INT A -> IRQ 5
pci 0000:00:1c.0: sharing IRQ 5 with 0000:02:00.0
pci 0000:00:1c.2: found PCI INT C -> IRQ 11
pci 0000:00:1c.2: sharing IRQ 11 with 0000:00:1a.2
pci 0000:00:1c.2: sharing IRQ 11 with 0000:00:1a.7
pci 0000:00:1c.2: sharing IRQ 11 with 0000:00:1d.2
pci 0000:00:1c.2: sharing IRQ 11 with 0000:00:1f.3
pci 0000:00:1c.2: sharing IRQ 11 with 0000:03:00.0
pci 0000:00:1c.5: found PCI INT B -> IRQ 10
pci 0000:00:1c.5: sharing IRQ 10 with 0000:00:06.0
pci 0000:00:1c.5: sharing IRQ 10 with 0000:00:1a.0
pci 0000:00:1c.5: sharing IRQ 10 with 0000:01:00.0
pci 0000:00:1c.5: sharing IRQ 10 with 0000:05:00.0
NET: Registered protocol family 2
IP route cache hash table entries: 262144 (order: 9, 2097152 bytes)
TCP established hash table entries: 524288 (order: 11, 8388608 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 524288 bind 65536)
TCP reno registered
NET: Registered protocol family 1
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 30955k freed
PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
DMA: Placing 64MB software IO TLB between ffff88000b593000 - ffff88000f593000
DMA: software IO TLB at phys 0xb593000 - 0xf593000
platform rtc_cmos: registered platform RTC device (no PNP device found)
audit: initializing netlink socket (disabled)
type=2000 audit(1285786302.418:1): initialized
HugeTLB registered 2 MB page size, pre-allocated 0 pages
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
msgmni has been set to 11743
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.4
acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
pci-stub: invalid id string ""
Non-volatile memory driver v1.3
Linux agpgart interface v0.103
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
brd: module loaded
loop: module loaded
input: Macintosh mouse button emulation as /devices/virtual/input/input0
ahci 0000:00:1f.2: found PCI INT B -> IRQ 15
ahci 0000:00:1f.2: sharing IRQ 15 with 0000:00:1d.1
ahci: SSS flag set, parallel bus scan disabled
ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0x3f impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo pmp pio slum part ccc ems sxs
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
scsi4 : ahci
scsi5 : ahci
ata1: SATA max UDMA/133 irq_stat 0x00400040, connection status changed irq 498
ata2: SATA max UDMA/133 irq_stat 0x00400040, connection status changed irq 498
ata3: SATA max UDMA/133 irq_stat 0x00400040, connection status changed irq 498
ata4: SATA max UDMA/133 irq_stat 0x00400040, connection status changed irq 498
ata5: SATA max UDMA/133 irq_stat 0x00400040, connection status changed irq 498
ata6: SATA max UDMA/133 abar m2048@0xfc9fe800 port 0xfc9feb80 irq 498
Fixed MDIO Bus: probed
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:1a.7: found PCI INT C -> IRQ 11
ehci_hcd 0000:00:1a.7: sharing IRQ 11 with 0000:00:1a.2
ehci_hcd 0000:00:1a.7: sharing IRQ 11 with 0000:00:1d.2
ehci_hcd 0000:00:1a.7: sharing IRQ 11 with 0000:00:1f.3
ehci_hcd 0000:00:1a.7: sharing IRQ 11 with 0000:03:00.0
ehci_hcd 0000:00:1a.7: EHCI Host Controller
ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1a.7: debug port 1
ehci_hcd 0000:00:1a.7: request interrupt 11 failed
ehci_hcd 0000:00:1a.7: USB bus 1 deregistered
ehci_hcd 0000:00:1a.7: init 0000:00:1a.7 fail, -38
ehci_hcd: probe of 0000:00:1a.7 failed with error -38
ehci_hcd 0000:00:1d.7: found PCI INT A -> IRQ 3
ehci_hcd 0000:00:1d.7: sharing IRQ 3 with 0000:00:1d.0
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: debug port 1
ehci_hcd 0000:00:1d.7: request interrupt 3 failed
ehci_hcd 0000:00:1d.7: USB bus 1 deregistered
ehci_hcd 0000:00:1d.7: init 0000:00:1d.7 fail, -38
ehci_hcd: probe of 0000:00:1d.7 failed with error -38
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
uhci_hcd: USB Universal Host Controller Interface driver
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
uhci_hcd 0000:00:1a.0: found PCI INT A -> IRQ 10
uhci_hcd 0000:00:1a.0: sharing IRQ 10 with 0000:01:00.0
uhci_hcd 0000:00:1a.0: sharing IRQ 10 with 0000:05:00.0
uhci_hcd 0000:00:1a.0: UHCI Host Controller
uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1a.0: request interrupt 10 failed
uhci_hcd 0000:00:1a.0: USB bus 1 deregistered
ata1.00: ATA-7: ST3320620AS, 3.AAK, max UDMA/133
ata1.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 31/32)
uhci_hcd 0000:00:1a.0: init 0000:00:1a.0 fail, -38
uhci_hcd: probe of 0000:00:1a.0 failed with error -38
uhci_hcd 0000:00:1a.1: found PCI INT B -> IRQ 14
uhci_hcd 0000:00:1a.1: UHCI Host Controller
uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1a.1: request interrupt 14 failed
uhci_hcd 0000:00:1a.1: USB bus 1 deregistered
uhci_hcd 0000:00:1a.1: init 0000:00:1a.1 fail, -38
uhci_hcd: probe of 0000:00:1a.1 failed with error -38
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access ATA ST3320620AS 3.AA PQ: 0 ANSI: 5
uhci_hcd 0000:00:1a.2: found PCI INT C -> IRQ 11
uhci_hcd 0000:00:1a.2: sharing IRQ 11 with 0000:00:1a.7
uhci_hcd 0000:00:1a.2: sharing IRQ 11 with 0000:00:1d.2
uhci_hcd 0000:00:1a.2: sharing IRQ 11 with 0000:00:1f.3
uhci_hcd 0000:00:1a.2: sharing IRQ 11 with 0000:03:00.0
uhci_hcd 0000:00:1a.2: UHCI Host Controller
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] 625142448 512-byte logical blocks: (320 GB/298 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or
FUA
sda:
uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 1
sda1 sda2 sda3
uhci_hcd 0000:00:1a.2: request interrupt 11 failed
uhci_hcd 0000:00:1a.2: USB bus 1 deregistered
sd 0:0:0:0: [sda] Attached SCSI disk
uhci_hcd 0000:00:1a.2: init 0000:00:1a.2 fail, -38
uhci_hcd: probe of 0000:00:1a.2 failed with error -38
uhci_hcd 0000:00:1d.0: found PCI INT A -> IRQ 3
uhci_hcd 0000:00:1d.0: sharing IRQ 3 with 0000:00:1d.7
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1d.0: request interrupt 3 failed
uhci_hcd 0000:00:1d.0: USB bus 1 deregistered
uhci_hcd 0000:00:1d.0: init 0000:00:1d.0 fail, -38
uhci_hcd: probe of 0000:00:1d.0 failed with error -38
uhci_hcd 0000:00:1d.1: found PCI INT B -> IRQ 15
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1d.1: request interrupt 15 failed
uhci_hcd 0000:00:1d.1: USB bus 1 deregistered
uhci_hcd 0000:00:1d.1: init 0000:00:1d.1 fail, -38
uhci_hcd: probe of 0000:00:1d.1 failed with error -38
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
uhci_hcd 0000:00:1d.2: found PCI INT C -> IRQ 11
uhci_hcd 0000:00:1d.2: sharing IRQ 11 with 0000:00:1a.2
uhci_hcd 0000:00:1d.2: sharing IRQ 11 with 0000:00:1a.7
uhci_hcd 0000:00:1d.2: sharing IRQ 11 with 0000:00:1f.3
uhci_hcd 0000:00:1d.2: sharing IRQ 11 with 0000:03:00.0
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1d.2: request interrupt 11 failed
uhci_hcd 0000:00:1d.2: USB bus 1 deregistered
ata2.00: ATA-7: ST3320620AS, 3.AAK, max UDMA/133
ata2.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 31/32)
uhci_hcd 0000:00:1d.2: init 0000:00:1d.2 fail, -38
uhci_hcd: probe of 0000:00:1d.2 failed with error -38
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
ata2.00: configured for UDMA/133
scsi 1:0:0:0: Direct-Access ATA ST3320620AS 3.AA PQ: 0 ANSI: 5
mice: PS/2 mouse device common for all mice
rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
sd 1:0:0:0: Attached scsi generic sg1 type 0
sd 1:0:0:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB)
rtc0: alarms up to one day, 114 bytes nvram
device-mapper: uevent: version 1.0.3
sd 1:0:0:0: [sdb] Write Protect is off
device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel(a)redhat.com
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or
FUA
cpuidle: using governor ladder
cpuidle: using governor menu
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
sdb:
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
sdb1 sdb2 sdb3
sd 1:0:0:0: [sdb] Attached SCSI disk
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
registered taskstats version 1
No TPM chip found, activating TPM-bypass!
Magic number: 10:447:899
rtc_cmos rtc_cmos: setting system clock to 2010-09-29 18:51:54 UTC (1285786314)
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Initalizing network drop monitor service
ata3.00: ATA-7: ST3320620NS, 3.AEG, max UDMA/133
ata3.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata3.00: configured for UDMA/133
scsi 2:0:0:0: Direct-Access ATA ST3320620NS 3.AE PQ: 0 ANSI: 5
sd 2:0:0:0: Attached scsi generic sg2 type 0
sd 2:0:0:0: [sdc] 625142448 512-byte logical blocks: (320 GB/298 GiB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or
FUA
sdc: sdc1
sd 2:0:0:0: [sdc] Attached SCSI disk
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4.00: ATA-7: ST3320620NS, 3.AEG, max UDMA/133
ata4.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata4.00: configured for UDMA/133
scsi 3:0:0:0: Direct-Access ATA ST3320620NS 3.AE PQ: 0 ANSI: 5
sd 3:0:0:0: Attached scsi generic sg3 type 0
sd 3:0:0:0: [sdd] 625142448 512-byte logical blocks: (320 GB/298 GiB)
sd 3:0:0:0: [sdd] Write Protect is off
sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or
FUA
sdd: sdd1
sd 3:0:0:0: [sdd] Attached SCSI disk
ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata5.00: ATA-8: ST31500341AS, CC1H, max UDMA/133
ata5.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata5.00: configured for UDMA/133
scsi 4:0:0:0: Direct-Access ATA ST31500341AS CC1H PQ: 0 ANSI: 5
sd 4:0:0:0: Attached scsi generic sg4 type 0
sd 4:0:0:0: [sde] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
sd 4:0:0:0: [sde] Write Protect is off
sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or
FUA
sde: sde1
sd 4:0:0:0: [sde] Attached SCSI disk
ata6: SATA link down (SStatus 0 SControl 300)
Freeing unused kernel memory: 944k freed
Write protecting the kernel read-only data: 6624k
dracut: dracut-005-2.fc12
udev: starting version 145
[drm] Initialized drm 1.1.0 20060810
pci 0000:05:00.0: found PCI INT A -> IRQ 10
pci 0000:05:00.0: sharing IRQ 10 with 0000:00:1a.0
pci 0000:05:00.0: sharing IRQ 10 with 0000:01:00.0
[drm] nouveau 0000:05:00.0: Detected an NV10 generation card (0x018500c1)
[drm] Initialized nouveau 0.0.15 20090420 for 0000:05:00.0 on minor 0
dracut: Starting plymouth daemon
%Gsata_sil24 0000:03:00.0: found PCI INT A -> IRQ 11
sata_sil24 0000:03:00.0: sharing IRQ 11 with 0000:00:1a.2
sata_sil24 0000:03:00.0: sharing IRQ 11 with 0000:00:1a.7
sata_sil24 0000:03:00.0: sharing IRQ 11 with 0000:00:1d.2
sata_sil24 0000:03:00.0: sharing IRQ 11 with 0000:00:1f.3
%GFusion MPT base driver 3.04.12
Copyright (c) 1999-2008 LSI Corporation
Fusion MPT SAS Host driver 3.04.12
mptsas 0000:01:00.0: found PCI INT A -> IRQ 10
mptsas 0000:01:00.0: sharing IRQ 10 with 0000:00:1a.0
mptsas 0000:01:00.0: sharing IRQ 10 with 0000:05:00.0
sata_sil24: probe of 0000:03:00.0 failed with error -38
mptbase: ioc0: Initiating bringup
ioc0: LSISAS1068E B3: Capabilities={Initiator}
mptbase: ioc0: ERROR - Unable to allocate interrupt 10!
mptbase: ioc0: ERROR - didn't initialize properly! (-16)
mptsas: probe of 0000:01:00.0 failed with error -16
dracut: Autoassembling MD Raid
md: md0 stopped.
md: bind<sdb1>
md: bind<sda1>
md: raid1 personality registered for level 1
raid1: raid set md0 active with 2 out of 2 mirrors
md0: detected capacity change from 0 to 2146697216
md0:
dracut: mdadm: /dev/md0 has been started with 2 drives.
unknown partition table
md: md1 stopped.
md: bind<sdb3>
md: bind<sda3>
raid1: raid set md1 active with 2 out of 2 mirrors
md1: detected capacity change from 0 to 300781928448
md1:
dracut: mdadm: /dev/md1 has been started with 2 drives.
unknown partition table
md: md2 stopped.
md: bind<sdb2>
md: bind<sda2>
raid1: raid set md2 active with 2 out of 2 mirrors
md2: detected capacity change from 0 to 17141399552
md2:
dracut: mdadm: /dev/md2 has been started with 2 drives.
unknown partition table
md: md3 stopped.
md: bind<sde1>
raid1: raid set md3 active with 1 out of 2 mirrors
md3: detected capacity change from 0 to 1500126183424
md3:
dracut: mdadm: /dev/md3 has been started with 1 drive (out of 2).
unknown partition table
md: md4 stopped.
md: bind<sdd1>
md: bind<sdc1>
raid1: raid set md4 active with 2 out of 2 mirrors
md4: detected capacity change from 0 to 295287390208
md4:
dracut: mdadm: /dev/md4 has been started with 2 drives.
unknown partition table
dracut: luksOpen /dev/md3 luks-94967b1a-c02d-4f48-98e8-d669baf9064a
/dev/md3 (luks-94967b1a-c02d-4f48-98e8-d669baf9064a) is password protected:******
padlock: VIA PadLock not detected.
Intel AES-NI instructions are not detected.
dracut: Autoassembling MD Raid
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with journal data mode.
data=journal
dracut: Mounted root filesystem /dev/md1
dracut: Loading SELinux policy
dracut: /sbin/load_policy: Can't load policy file
/etc/selinux/targeted/policy/policy.-1: No such file or directory
dracut: Switching root
Welcome to Fedora
Press 'I' to enter interactive startup.
Starting udev: %G[ OK ]
------------[ cut here ]------------
kernel BUG at drivers/xen/balloon.c:270!
invalid opcode: 0000 [#1] SMP
last sysfs file: /sys/kernel/uevent_seqnum
CPU 0
Modules linked in: xen_blkback(+) blkback_pagemap xen_gntdev xen_evtchn xenfs uinput atl1e
serio_raw microcode iTCO_wdt iTCO_vendor_support i2c_i801 sha256_generic cryptd aes_x86_64
aes_generic cbc dm_crypt raid1 mptsas mptscsih mptbase sata_sil24 scsi_transport_sas
nouveau ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: scsi_wait_scan]
Pid: 6, comm: events/0 Not tainted 2.6.32.21-168.xendom0.fc12.x86_64 #1 System Product
Name
RIP: e030:[<ffffffff812a7bc9>] [<ffffffff812a7bc9>]
balloon_process+0x1d4/0x5fd
RSP: e02b:ffff8801e5921d70 EFLAGS: 00010206
RAX: 00000000000a4182 RBX: 0000000000151fbf RCX: 0000000000000005
RDX: ffffffff81a15000 RSI: ffff8801e5921de0 RDI: 00000000000001bf
RBP: ffff8801e5921e30 R08: ffffea00049ef1f0 R09: ffff88000b577160
R10: 0000000000000004 R11: ffff88000b5841c8 R12: ffffea00049ef1c8
R13: ffff8801e5918000 R14: ffffea00049ef1f0 R15: 0000000000000200
FS: 00007ff6f0427700(0000) GS:ffff88000b56c000(0000) knlGS:0000000000000000
CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 000000000115acbf CR3: 00000001e241d000 CR4: 0000000000002660
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process events/0 (pid: 6, threadinfo ffff8801e5920000, task ffff8801e5918000)
Stack:
ffff88000b5841c8 ffff8801ed802980 ffffffff8100ef91 ffff8801e5921df0
<0> ffffffff8100f6c2 ffff8801e5921fd8 0000000000206c94 00000000000002c0
<0> 0000000000000200 0000000000000000 0000000000000000 ffff88000b57d8b0
Call Trace:
[<ffffffff8100ef91>] ? xen_force_evtchn_callback+0xd/0xf
[<ffffffff8100f6c2>] ? check_events+0x12/0x20
[<ffffffff8107145c>] worker_thread+0x1a9/0x237
[<ffffffff812a79f5>] ? balloon_process+0x0/0x5fd
[<ffffffff81075a87>] ? autoremove_wake_function+0x0/0x39
[<ffffffff8145c91b>] ? _spin_unlock_irqrestore+0x19/0x1b
[<ffffffff810712b3>] ? worker_thread+0x0/0x237
[<ffffffff8107579a>] kthread+0x7f/0x87
[<ffffffff81013d6a>] child_rip+0xa/0x20
[<ffffffff81012f51>] ? int_ret_from_sys_call+0x7/0x1b
[<ffffffff810136dd>] ? retint_restore_args+0x5/0x6
[<ffffffff81013d60>] ? child_rip+0x0/0x20
Code: d5 20 14 9d 81 48 0f af d8 80 3d 24 77 53 00 00 48 89 95 70 ff ff ff 75 0d 48 89 df
e8 d0 4f d6 ff 48 ff c0 75 05 45 31 ed eb 73 <0f> 0b eb fe 48 89 ce 48 89 d7 48 89
95 58 ff ff ff 48 89 8d 50
RIP [<ffffffff812a7bc9>] balloon_process+0x1d4/0x5fd
RSP <ffff8801e5921d70>
---[ end trace 9113829ac090ea20 ]---
---8<-----8<---- END SERIAL LOG ---8<-----8<----
--
Bill McGonigle, Owner
BFC Computing, LLC
http://bfccomputing.com/
Telephone: +1.603.448.4440
Email, IM, VOIP: bill(a)bfccomputing.com
VCard: http://bfccomputing.com/vcard/bill.vcf
Social networks: bill_mcgonigle/bill.mcgonigle
8 p.m.
New subject: xen and dom0 kernel builds
Quick question:
Should the libvirt stuff be updated?
Sep 27 10:47:41 seanl64 libvirtd: 10:47:41.234: error : statsErrorFunc:60 : internal error
read_bd_stats: Failed to read any block statistics
libvirt-client-0.8.2-1.fc12.x86_64
libvirt-python-0.8.2-1.fc12.x86_64
libvirt-0.8.2-1.fc12.x86_64
xen-runtime-4.0.1-1.fc12.1.x86_64
xen-devel-4.0.1-1.fc12.1.x86_64
xen-libs-4.0.1-1.fc12.1.x86_64
xen-debuginfo-4.0.1-1.fc12.1.x86_64
xen-4.0.1-1.fc12.1.x86_64
xen-doc-4.0.1-1.fc12.1.x86_64
xen-hypervisor-4.0.1-1.fc12.1.x86_64
Linux seanl64.xxxxxx.xx.xx 2.6.32.21-168.xendom0.fc12.x86_64 #1 SMP Mon Sep 20 19:32:37
UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
Cheers
Virgil
On Sat, 25 Sep 2010 08:02:00 am M A Young wrote:
I have built a new kernel (kernel-2.6.32.21-168.xendom0.fc12) at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2477887 or at the
repository http://repos.fedorapeople.org/repos/myoung/dom0-kernel/
It includes fixes for the recent x86_64 local root exploit.
There are also some new builds of xen. The Fedora packages
xen-4.0.1-3.fc15 and xen-4.0.1-3.fc14 available via
http://koji.fedoraproject.org/koji/packageinfo?packageID=7 have some IRQ
fixes that solve a problem I was having with a keyboard and mouse and the
patch that disables xsave which was causing problems with HVM (both these
are from 4.0.2-rc1-pre). It also creates a symbolic link for qemu-dm from
the place it was in 3.4.x to where it is in 4.0.x for compatibility.
I also have a temporary test build xen-4.0.1-1.fc13.1 for Fedora 13 at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2478501 . This is
slightly misnamed as it is actually of 4.0.2-rc1-pre and includes the
fixes above. Note that he build system will delete those RPMs
automatically after a week or so.
Michael Young
--
xen mailing list
xen(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
8:16 p.m.
New subject: xen and dom0 kernel builds
Further to the previous email regarding diskio stats:
It appears the ksysguardd is no longer able to gather stats either.
I'm suspecting a bug in the kernel and not libvirtd.
Cheers
V
On Sat, 25 Sep 2010 08:02:00 am M A Young wrote:
I have built a new kernel (kernel-2.6.32.21-168.xendom0.fc12) at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2477887 or at the
repository http://repos.fedorapeople.org/repos/myoung/dom0-kernel/
It includes fixes for the recent x86_64 local root exploit.
There are also some new builds of xen. The Fedora packages
xen-4.0.1-3.fc15 and xen-4.0.1-3.fc14 available via
http://koji.fedoraproject.org/koji/packageinfo?packageID=7 have some IRQ
fixes that solve a problem I was having with a keyboard and mouse and the
patch that disables xsave which was causing problems with HVM (both these
are from 4.0.2-rc1-pre). It also creates a symbolic link for qemu-dm from
the place it was in 3.4.x to where it is in 4.0.x for compatibility.
I also have a temporary test build xen-4.0.1-1.fc13.1 for Fedora 13 at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2478501 . This is
slightly misnamed as it is actually of 4.0.2-rc1-pre and includes the
fixes above. Note that he build system will delete those RPMs
automatically after a week or so.
Michael Young
--
xen mailing list
xen(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
10:59 a.m.
New subject: xen and dom0 kernel builds
On Fri, Sep 24, 2010 at 11:02:00PM +0100, M A Young wrote:
I have built a new kernel (kernel-2.6.32.21-168.xendom0.fc12) at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2477887 or at the
repository http://repos.fedorapeople.org/repos/myoung/dom0-kernel/
It includes fixes for the recent x86_64 local root exploit.
There are also some new builds of xen. The Fedora packages
xen-4.0.1-3.fc15 and xen-4.0.1-3.fc14 available via
http://koji.fedoraproject.org/koji/packageinfo?packageID=7 have some IRQ
fixes that solve a problem I was having with a keyboard and mouse and the
patch that disables xsave which was causing problems with HVM (both these
are from 4.0.2-rc1-pre). It also creates a symbolic link for qemu-dm from
the place it was in 3.4.x to where it is in 4.0.x for compatibility.
Are you planning to get xen-4.0.1-3.fc14 to F14 before it goes GA?
That would be good..
It seems the current F14 tree still has xen-4.0.1-1.fc14.src.rpm.
I also have a temporary test build xen-4.0.1-1.fc13.1 for Fedora 13
at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2478501 . This is
slightly misnamed as it is actually of 4.0.2-rc1-pre and includes the
fixes above. Note that he build system will delete those RPMs
automatically after a week or so.
Could you upload xen-4.0.1-1.fc13.1 src.rpm somewhere? I'd like to
mirror it, some people might want to get it also now when it's
removed from that koji page..
-- Pasi
12:46 p.m.
New subject: xen and dom0 kernel builds
Are you planning to get xen-4.0.1-3.fc14 to F14 before it goes GA?
That would be good..
The most recent "yum update" installs xen-4.0.1-4.fc14 on F14 ( rawhide)
Boris.
--- On Sun, 10/3/10, Pasi Kärkkäinen <pasik(a)iki.fi> wrote:
From: Pasi Kärkkäinen <pasik(a)iki.fi>
Subject: Re: [Fedora-xen] xen and dom0 kernel builds
To: "M A Young" <m.a.young(a)durham.ac.uk>
Cc: xen(a)lists.fedoraproject.org
Date: Sunday, October 3, 2010, 11:59 AM
On Fri, Sep 24, 2010 at 11:02:00PM +0100, M A Young wrote:
I have built a new kernel (kernel-2.6.32.21-168.xendom0.fc12) at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2477887 or at the
repository http://repos.fedorapeople.org/repos/myoung/dom0-kernel/
It includes fixes for the recent x86_64 local root exploit.
There are also some new builds of xen. The Fedora packages
xen-4.0.1-3.fc15 and xen-4.0.1-3.fc14 available via
http://koji.fedoraproject.org/koji/packageinfo?packageID=7 have some IRQ
fixes that solve a problem I was having with a keyboard and mouse and the
patch that disables xsave which was causing problems with HVM (both these
are from 4.0.2-rc1-pre). It also creates a symbolic link for qemu-dm from
the place it was in 3.4.x to where it is in 4.0.x for compatibility.
Are you planning to get xen-4.0.1-3.fc14 to F14 before it goes GA?
That would be good..
It seems the current F14 tree still has xen-4.0.1-1.fc14.src.rpm.
I also have a temporary test build xen-4.0.1-1.fc13.1 for Fedora 13
at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2478501 . This is
slightly misnamed as it is actually of 4.0.2-rc1-pre and includes the
fixes above. Note that he build system will delete those RPMs
automatically after a week or so.
Could you upload xen-4.0.1-1.fc13.1 src.rpm somewhere? I'd like to
mirror it, some people might want to get it also now when it's
removed from that koji page..
-- Pasi
--
xen mailing list
xen(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
12:57 p.m.
New subject: xen and dom0 kernel builds
On Sun, Oct 03, 2010 at 10:46:49AM -0700, Boris Derzhavets wrote:
> Are you planning to get xen-4.0.1-3.fc14 to F14 before it
goes GA?
> That would be good..
The most recent "yum update" installs xen-4.0.1-4.fc14 on F14 ( rawhide)
I think rawhide is currently F15.. F14 has been branched already.
But yeah, I re-checked, and I noticed xen-4.0.1-4.fc14.src.rpm
in F14 updates-testing.
So all fine.
Thanks!
-- Pasi
Boris.
--- On Sun, 10/3/10, Pasi Kärkkäinen <pasik(a)iki.fi> wrote:
From: Pasi Kärkkäinen <pasik(a)iki.fi>
Subject: Re: [Fedora-xen] xen and dom0 kernel builds
To: "M A Young" <m.a.young(a)durham.ac.uk>
Cc: xen(a)lists.fedoraproject.org
Date: Sunday, October 3, 2010, 11:59 AM
On Fri, Sep 24, 2010 at 11:02:00PM +0100, M A Young wrote:
> I have built a new kernel (kernel-2.6.32.21-168.xendom0.fc12) at
> [1]http://koji.fedoraproject.org/koji/taskinfo?taskID=2477887 or at
the
> repository [2]http://repos.fedorapeople.org/repos/myoung/dom0-kernel/
> It includes fixes for the recent x86_64 local root exploit.
>
> There are also some new builds of xen. The Fedora packages
> xen-4.0.1-3.fc15 and xen-4.0.1-3.fc14 available via
> [3]http://koji.fedoraproject.org/koji/packageinfo?packageID=7 have
some IRQ
> fixes that solve a problem I was having with a keyboard and mouse and
the
> patch that disables xsave which was causing problems with HVM (both
these
> are from 4.0.2-rc1-pre). It also creates a symbolic link for qemu-dm
from
> the place it was in 3.4.x to where it is in 4.0.x for compatibility.
>
Are you planning to get xen-4.0.1-3.fc14 to F14 before it goes GA?
That would be good..
It seems the current F14 tree still has xen-4.0.1-1.fc14.src.rpm.
> I also have a temporary test build xen-4.0.1-1.fc13.1 for Fedora 13 at
> [4]http://koji.fedoraproject.org/koji/taskinfo?taskID=2478501 . This
is
> slightly misnamed as it is actually of 4.0.2-rc1-pre and includes the
> fixes above. Note that he build system will delete those RPMs
> automatically after a week or so.
>
Could you upload xen-4.0.1-1.fc13.1 src.rpm somewhere? I'd like to
mirror it, some people might want to get it also now when it's
removed from that koji page..
-- Pasi
--
xen mailing list
[5]xen(a)lists.fedoraproject.org
[6]https://admin.fedoraproject.org/mailman/listinfo/xen
References
Visible links
1. http://koji.fedoraproject.org/koji/taskinfo?taskID=2477887
2. http://repos.fedorapeople.org/repos/myoung/dom0-kernel/
3. http://koji.fedoraproject.org/koji/packageinfo?packageID=7
4. http://koji.fedoraproject.org/koji/taskinfo?taskID=2478501
5. file:///mc/compose?to=xen@lists.fedoraproject.org
6. https://admin.fedoraproject.org/mailman/listinfo/xen
2:55 p.m.
New subject: xen and dom0 kernel builds
On Sun, 3 Oct 2010, Pasi Kärkkäinen wrote:
Are you planning to get xen-4.0.1-3.fc14 to F14 before it goes GA?
That would be good..
There has been a bit of a delay because it got built with a bad gcc.
xen-4.0.1-4.fc14 is a rebuild once gcc was fixed. As specified in
https://fedoraproject.org/wiki/Updates_Policy
I am now waiting a week before I push it to stable.
Could you upload xen-4.0.1-1.fc13.1 src.rpm somewhere? I'd like
to
mirror it, some people might want to get it also now when it's
removed from that koji page..
I could but I have now just built xen-4.0.1-1.fc13.2 at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2509285
This is the same except that I am experimenting by adding a patch from the
Fedora grub package to see if I can get ext4 support in pvgrub.
Michael Young
3 p.m.
New subject: xen and dom0 kernel builds
On Sun, Oct 03, 2010 at 08:55:15PM +0100, M A Young wrote:
On Sun, 3 Oct 2010, Pasi Kärkkäinen wrote:
> Are you planning to get xen-4.0.1-3.fc14 to F14 before it goes GA?
> That would be good..
There has been a bit of a delay because it got built with a bad gcc.
xen-4.0.1-4.fc14 is a rebuild once gcc was fixed. As specified in
https://fedoraproject.org/wiki/Updates_Policy
I am now waiting a week before I push it to stable.
Ok.
> Could you upload xen-4.0.1-1.fc13.1 src.rpm somewhere? I'd
like to
> mirror it, some people might want to get it also now when it's
> removed from that koji page..
I could but I have now just built xen-4.0.1-1.fc13.2 at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2509285
This is the same except that I am experimenting by adding a patch from
the Fedora grub package to see if I can get ext4 support in pvgrub.
Great. Thanks!
-- Pasi
3:56 p.m.
New subject: xen and dom0 kernel builds
On Sun, 3 Oct 2010, M A Young wrote:
On Sun, 3 Oct 2010, Pasi Kärkkäinen wrote:
There has been a bit of a delay because it got built with a bad gcc.
xen-4.0.1-4.fc14 is a rebuild once gcc was fixed. As specified in
https://fedoraproject.org/wiki/Updates_Policy
I am now waiting a week before I push it to stable.
xen-4.0.1-4.fc14 has now made it into the F14 release. I have also now
built xen-4.0.1-5.fc14/15 which adds the fix for ext4 in pvgrub I was
testing.
I have also done a new kernel which is at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2518648 or the
repository
http://repos.fedorapeople.org/repos/myoung/dom0-kernel/fedora-12/
with the latest xen/stable-2.6.32.x patches including the watchdog driver
(built as a module) and some IRQ and memory fixes.
Michael Young
4:02 p.m.
New subject: xen and dom0 kernel builds
On Fri, Oct 08, 2010 at 09:56:35PM +0100, M A Young wrote:
On Sun, 3 Oct 2010, M A Young wrote:
> On Sun, 3 Oct 2010, Pasi Kärkkäinen wrote:
>
> There has been a bit of a delay because it got built with a bad gcc.
> xen-4.0.1-4.fc14 is a rebuild once gcc was fixed. As specified in
> https://fedoraproject.org/wiki/Updates_Policy
> I am now waiting a week before I push it to stable.
xen-4.0.1-4.fc14 has now made it into the F14 release. I have also now
built xen-4.0.1-5.fc14/15 which adds the fix for ext4 in pvgrub I was
testing.
I have also done a new kernel which is at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2518648 or the
repository
http://repos.fedorapeople.org/repos/myoung/dom0-kernel/fedora-12/
with the latest xen/stable-2.6.32.x patches including the watchdog driver
(built as a module) and some IRQ and memory fixes.
Thanks, good work!
-- Pasi
6:08 p.m.
New subject: another xen build
I have now built xen-4.0.1-6.fc14/5 to fix a boot failure for some
hardware ( https://bugzilla.redhat.com/show_bug.cgi?id=642108 ) available
from koji at http://koji.fedoraproject.org/koji/packageinfo?packageID=7
and also a test build xen-4.0.1-1.fc13.3 built for f13
temporarily available at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2530814
with the same patch.
I should be able to get xen-4.0.1-5.fc14 into the released version on
Fedora 14, but (unless there is enough karma to speed up the process) I
believe it is too late for xen-4.0.1-6.fc14 which will probably end up as
a 0-day update (unless it has been superceded by then).
Michael Young
3:55 a.m.
New subject: another xen build
How can we increase the karma? I can add some...
Will this xen-4.0.1-1.fc13.3 work for bridged rather than routed?
Sorry I am not up on the latest xen stuff still stuck on F8 :(
If you do get it in, what would that mean for dom0 on F14?
What would be missing from a usable dom0?
Thanks for your work on this.
On 10/12/10 4:08 PM, M A Young wrote:
I have now built xen-4.0.1-6.fc14/5 to fix a boot failure for some
hardware ( https://bugzilla.redhat.com/show_bug.cgi?id=642108 ) available
from koji at http://koji.fedoraproject.org/koji/packageinfo?packageID=7
and also a test build xen-4.0.1-1.fc13.3 built for f13
temporarily available at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2530814
with the same patch.
I should be able to get xen-4.0.1-5.fc14 into the released version on
Fedora 14, but (unless there is enough karma to speed up the process) I
believe it is too late for xen-4.0.1-6.fc14 which will probably end up as
a 0-day update (unless it has been superceded by then).
Michael Young
--
xen mailing list
xen(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
7:19 a.m.
New subject: another xen build
On Wed, 13 Oct 2010, fcxen user wrote:
How can we increase the karma? I can add some...
You can vote on xen-4.0.1-5.fc14 at
https://admin.fedoraproject.org/updates/xen-4.0.1-5.fc14
though you may need to be logged in for your vote to count.
Will this xen-4.0.1-1.fc13.3 work for bridged rather than routed?
Sorry I am not up on the latest xen stuff still stuck on F8 :(
I use the virtual bridge provided by the libvirt package. I didn't have a
lot of success using a true bridge last time I tried it, but that would
have been with xen 3.x not 4.x.
If you do get it in, what would that mean for dom0 on F14?
What would be missing from a usable dom0?
I use the F12 kernel I build on F14 which seems to work (I was following
F12 because that is still on 2.6.32.x which is has the best maintained
dom0 pvops patches at present). It did have trouble with systemd but that
was dropped as the default init for F14.
Michael Young
10:32 a.m.
New subject: another xen build
On Wed, 13 Oct 2010, M A Young wrote:
On Wed, 13 Oct 2010, fcxen user wrote:
> How can we increase the karma? I can add some...
You can vote on xen-4.0.1-5.fc14 at
https://admin.fedoraproject.org/updates/xen-4.0.1-5.fc14
though you may need to be logged in for your vote to count.
xen-4.0.1-5.fc14 got enough karma and made it into the F14 release and I
have now submitted xen-4.0.1-6.fc14 for updates-testing.
Please test it (it is available from
http://koji.fedoraproject.org/koji/buildinfo?buildID=200238 and will be
in updates-testing soon) and consider reporting your results at
https://admin.fedoraproject.org/updates/xen-4.0.1-6.fc14
as it may still be possible to get it into the F14 release.
Michael Young
6:32 a.m.
New subject: another xen build
On Thu, Oct 14, 2010 at 04:32:20PM +0100, M A Young wrote:
On Wed, 13 Oct 2010, M A Young wrote:
> On Wed, 13 Oct 2010, fcxen user wrote:
>
>> How can we increase the karma? I can add some...
>
> You can vote on xen-4.0.1-5.fc14 at
> https://admin.fedoraproject.org/updates/xen-4.0.1-5.fc14
> though you may need to be logged in for your vote to count.
xen-4.0.1-5.fc14 got enough karma and made it into the F14 release and I
have now submitted xen-4.0.1-6.fc14 for updates-testing.
Please test it (it is available from
http://koji.fedoraproject.org/koji/buildinfo?buildID=200238 and will be
in updates-testing soon) and consider reporting your results at
https://admin.fedoraproject.org/updates/xen-4.0.1-6.fc14
as it may still be possible to get it into the F14 release.
4.0.1-6.fc14 works for me!
-- Pasi
6:49 p.m.
New subject: another xen build
xen-4.0.1-6.fc12 (recompiled under FC12) likewise seems to resolve all issues
here. Fingers crossed, so far so good.
Cheers
V
On Sun, 17 Oct 2010 10:32:12 pm Pasi Kärkkäinen wrote:
On Thu, Oct 14, 2010 at 04:32:20PM +0100, M A Young wrote:
> On Wed, 13 Oct 2010, M A Young wrote:
> > On Wed, 13 Oct 2010, fcxen user wrote:
> >> How can we increase the karma? I can add some...
> >
> > You can vote on xen-4.0.1-5.fc14 at
> > https://admin.fedoraproject.org/updates/xen-4.0.1-5.fc14
> > though you may need to be logged in for your vote to count.
>
> xen-4.0.1-5.fc14 got enough karma and made it into the F14 release and I
> have now submitted xen-4.0.1-6.fc14 for updates-testing.
>
> Please test it (it is available from
> http://koji.fedoraproject.org/koji/buildinfo?buildID=200238 and will be
> in updates-testing soon) and consider reporting your results at
> https://admin.fedoraproject.org/updates/xen-4.0.1-6.fc14
> as it may still be possible to get it into the F14 release.
4.0.1-6.fc14 works for me!
-- Pasi
--
xen mailing list
xen(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
5:17 a.m.
New subject: another xen build
There is less urgency to test now because 4.0.1-6.fc14 has now made it
into F14 in time for the release. You can of course continue to test if
you want to.
Michael Young
9:49 a.m.
New subject: another xen build and pvops kernel
Just wondering why kernel-2.6.32.23-170.xendom0.fc12.src.rpm cannot make itself
into F14. It seems pretty stable. Why it cannot be just a package available via "yum
install" . Anyway Fedora's Libvirt has the best compatibility with Xen 4.0.1.
It's not too late switch back to Xen with PVOPS kernel. XenLinux 2.6.34.7 aka Suse
is really dangerous . It outperforms pvops kernel about 15-20 % under Xen 4.0.1.
I don't mention KVM performance. It's not a competitor for OpenSuse 11.3 after
the
most recent "zypper update"
Boris.
--- On Mon, 10/18/10, M A Young <m.a.young(a)durham.ac.uk> wrote:
From: M A Young <m.a.young(a)durham.ac.uk>
Subject: Re: [Fedora-xen] another xen build
To: xen(a)lists.fedoraproject.org
Date: Monday, October 18, 2010, 6:17 AM
There is less urgency to test now because 4.0.1-6.fc14 has now made it
into F14 in time for the release. You can of course continue to test if
you want to.
Michael Young
--
xen mailing list
xen(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
12:42 p.m.
New subject: another xen build and pvops kernel
On Mon, Oct 18, 2010 at 07:49:29AM -0700, Boris Derzhavets wrote:
Just wondering why [1]kernel-2.6.32.23-170.xendom0.fc12.src.rpm
cannot
make itself
into F14. It seems pretty stable. Why it cannot be just a package
available via "yum install" . Anyway Fedora's Libvirt has the best
compatibility with Xen 4.0.1.
It's not too late switch back to Xen with PVOPS kernel. XenLinux 2.6.34.7
aka Suse
is really dangerous . It outperforms pvops kernel about 15-20 % under Xen
4.0.1.
- How did you measure this performance difference?
- Did you make sure kernel configuration is similar for both kernel types?
Many pvops .configs have various debugging options enabled that kill the performance..
-- Pasi
I don't mention KVM performance. It's not a competitor for
OpenSuse 11.3
after the
most recent "zypper update"
Boris.
--- On Mon, 10/18/10, M A Young <m.a.young(a)durham.ac.uk> wrote:
From: M A Young <m.a.young(a)durham.ac.uk>
Subject: Re: [Fedora-xen] another xen build
To: xen(a)lists.fedoraproject.org
Date: Monday, October 18, 2010, 6:17 AM
There is less urgency to test now because 4.0.1-6.fc14 has now made it
into F14 in time for the release. You can of course continue to test if
you want to.
Michael Young
--
xen mailing list
[2]xen(a)lists.fedoraproject.org
[3]https://admin.fedoraproject.org/mailman/listinfo/xen
References
Visible links
1.
http://fedorapeople.org/%7Emyoung/dom0/src/kernel-2.6.32.23-170.xendom0.f...
2. file:///mc/compose?to=xen@lists.fedoraproject.org
3. https://admin.fedoraproject.org/mailman/listinfo/xen
--
xen mailing list
xen(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
12:49 a.m.
New subject: another xen build and pvops kernel
- How did you measure this performance difference?
Database server running on PV DomU with intensive I/O.
Workload connected with loading and unloading tables
to/from ASCII files residing on the guest's image.
> - Did you make sure kernel configuration is similar for both kernel types?
> Many pvops .configs have various debugging options enabled that kill the
performance..
It's my personal impression. I am not an expert in PVOPS config tuning, but
try to avoid debugging options.
Boris.
--- On Wed, 10/20/10, Pasi Kärkkäinen <pasik(a)iki.fi> wrote:
From: Pasi Kärkkäinen <pasik(a)iki.fi>
Subject: Re: [Fedora-xen] another xen build and pvops kernel
To: "Boris Derzhavets" <bderzhavets(a)yahoo.com>
Cc: xen(a)lists.fedoraproject.org, xen-users(a)lists.xensource.com
Date: Wednesday, October 20, 2010, 1:42 PM
On Mon, Oct 18, 2010 at 07:49:29AM -0700, Boris Derzhavets wrote:
Just wondering why [1]kernel-2.6.32.23-170.xendom0.fc12.src.rpm
cannot
make itself
into F14. It seems pretty stable. Why it cannot be just a package
available via "yum install" . Anyway Fedora's Libvirt has the best
compatibility with Xen 4.0.1.
It's not too late switch back to Xen with PVOPS kernel. XenLinux 2.6.34.7
aka Suse
is really dangerous . It outperforms pvops kernel about 15-20 % under Xen
4.0.1.
- How did you measure this performance difference?
- Did you make sure kernel configuration is similar for both kernel types?
Many pvops .configs have various debugging options enabled that kill the performance..
-- Pasi
I don't mention KVM performance. It's not a competitor for
OpenSuse 11.3
after the
most recent "zypper update"
Boris.
--- On Mon, 10/18/10, M A Young <m.a.young(a)durham.ac.uk> wrote:
From: M A Young <m.a.young(a)durham.ac.uk>
Subject: Re: [Fedora-xen] another xen build
To: xen(a)lists.fedoraproject.org
Date: Monday, October 18, 2010, 6:17 AM
There is less urgency to test now because 4.0.1-6.fc14 has now made it
into F14 in time for the release. You can of course continue to test if
you want to.
Michael Young
--
xen mailing list
[2]xen(a)lists.fedoraproject.org
[3]https://admin.fedoraproject.org/mailman/listinfo/xen
References
Visible links
1.
http://fedorapeople.org/%7Emyoung/dom0/src/kernel-2.6.32.23-170.xendom0.f...
2. file:///mc/compose?to=xen@lists.fedoraproject.org
3. https://admin.fedoraproject.org/mailman/listinfo/xen
--
xen mailing list
xen(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
4:27 p.m.
New subject: another xen kernel
There is a new xen kernel (2.6.32.23-170.1.xendom0.fc12) available to
download at http://koji.fedoraproject.org/koji/taskinfo?taskID=2547470 and
at the repository http://repos.fedorapeople.org/repos/myoung/dom0-kernel/
It contains some patches added added to xen/stable-2.6.32.x since the last
build, including an event channels fix.
Michael Young
8:29 p.m.
New subject: another xen kernel
On Fri, Oct 22, 2010 at 7:27 PM, M A Young <m.a.young(a)durham.ac.uk> wrote:
There is a new xen kernel (2.6.32.23-170.1.xendom0.fc12) available
to
download at http://koji.fedoraproject.org/koji/taskinfo?taskID=2547470 and
at the repository http://repos.fedorapeople.org/repos/myoung/dom0-kernel/
It contains some patches added added to xen/stable-2.6.32.x since the last
build, including an event channels fix.
Michael Young
take a look
https://bugzilla.redhat.com/show_bug.cgi?id=645252#c2
--
------------
Itamar Reis Peixoto
msn, google talk: itamar(a)ispbrasil.com.br
+55 11 4063 5033 (FIXO SP)
+55 34 9158 9329 (TIM)
+55 34 8806 3989 (OI)
+55 34 3221 8599 (FIXO MG)
11:50 a.m.
New subject: another xen kernel
On Fri, 22 Oct 2010, Itamar Reis Peixoto wrote:
On Fri, Oct 22, 2010 at 7:27 PM, M A Young
<m.a.young(a)durham.ac.uk> wrote:
> There is a new xen kernel (2.6.32.23-170.1.xendom0.fc12) available to
> download at http://koji.fedoraproject.org/koji/taskinfo?taskID=2547470 and
> at the repository http://repos.fedorapeople.org/repos/myoung/dom0-kernel/
>
> It contains some patches added added to xen/stable-2.6.32.x since the last
> build, including an event channels fix.
>
> Michael Young
take a look
https://bugzilla.redhat.com/show_bug.cgi?id=645252#c2
Try xen kernel-2.6.32.25-171.rc1.xendom0.fc12 instead at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2550132 or at the
repository http://repos.fedorapeople.org/repos/myoung/dom0-kernel/ which
has a fix for that and another security hole.
Michael Young
1:37 a.m.
New subject: another xen kernel
kernel-2.6.32.25-171.rc1.xendom0.fc12
RTC went mad. 1 sec = 1mS
Top was showing hours whizzing past in minutes. Windows VM went crazy doing
stuff. FC13 VM went crazy too doing all sorts of things really quickly.
Bizzare effect.
Went back to -168 kernel. Alls well again.
Cheers
V96
On Sun, 24 Oct 2010 03:50:40 am M A Young wrote:
On Fri, 22 Oct 2010, Itamar Reis Peixoto wrote:
> On Fri, Oct 22, 2010 at 7:27 PM, M A Young <m.a.young(a)durham.ac.uk> wrote:
>> There is a new xen kernel (2.6.32.23-170.1.xendom0.fc12) available to
>> download at http://koji.fedoraproject.org/koji/taskinfo?taskID=2547470
>> and at the repository
>> http://repos.fedorapeople.org/repos/myoung/dom0-kernel/
>>
>> It contains some patches added added to xen/stable-2.6.32.x since the
>> last build, including an event channels fix.
>>
>> Michael Young
>
> take a look
>
> https://bugzilla.redhat.com/show_bug.cgi?id=645252#c2
Try xen kernel-2.6.32.25-171.rc1.xendom0.fc12 instead at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2550132 or at the
repository http://repos.fedorapeople.org/repos/myoung/dom0-kernel/ which
has a fix for that and another security hole.
Michael Young
1:03 a.m.
New subject: another xen kernel
On Sat, Oct 23, 2010 at 11:50 AM, M A Young <m.a.young(a)durham.ac.uk> wrote:
On Fri, 22 Oct 2010, Itamar Reis Peixoto wrote:
> On Fri, Oct 22, 2010 at 7:27 PM, M A Young <m.a.young(a)durham.ac.uk> wrote:
>>
>> There is a new xen kernel (2.6.32.23-170.1.xendom0.fc12) available to
>> download at http://koji.fedoraproject.org/koji/taskinfo?taskID=2547470
>> and
>> at the repository http://repos.fedorapeople.org/repos/myoung/dom0-kernel/
>>
>> It contains some patches added added to xen/stable-2.6.32.x since the
>> last
>> build, including an event channels fix.
>>
>> Michael Young
>
> take a look
>
> https://bugzilla.redhat.com/show_bug.cgi?id=645252#c2
Try xen kernel-2.6.32.25-171.rc1.xendom0.fc12 instead at
http://koji.fedoraproject.org/koji/taskinfo?taskID=2550132 or at the
repository http://repos.fedorapeople.org/repos/myoung/dom0-kernel/ which has
a fix for that and another security hole.
Anyone else seeing problems with software raid?
On a new Fedora 14 system, the distro kernel is fine, but my 4 SCSI
drive system has md devices fail with xendom0...
Oct 27 23:31:17 elm kernel: [ 40.504212] dracut: mdadm: /dev/md0 has
been started with 2 drives.
Oct 27 23:31:17 elm kernel: [ 40.590546] dracut: mdadm: /dev/md1 has
been started with 2 drives.
Oct 27 23:31:17 elm kernel: [ 40.629581] dracut: mdadm: /dev/md2 has
been started with 3 drives.
Oct 27 23:31:17 elm kernel: [ 40.709149] dracut: mdadm: /dev/md3 has
been started with 3 drives.
[snip]
Oct 27 23:39:55 elm kernel: dracut: mdadm: /dev/md0 has been started
with 2 drives.
Oct 27 23:39:55 elm kernel: dracut: mdadm: /dev/md1 has been started
with 2 drives.
Oct 27 23:39:55 elm kernel: mdadm[617]: segfault at 46 ip 006b7997 sp
bfe4b2d0 error 4 in libc-2.12.90.so[658000+18d000]
Oct 27 23:39:55 elm kernel: mdadm[636]: segfault at 46 ip 006b7997 sp
bfa19490 error 4 in libc-2.12.90.so[658000+18d000]
The "Oct 27 23:31:17" messages reflect fc14, while "Oct 27 23:39:55"
is xendom0.
The system boots fine, but just won't see the extra meta devices.
Maybe just can't be done with a .32 kernel on fc14?
jerry
8:25 p.m.
New subject: another xen kernel
On Thu, Oct 28, 2010 at 1:03 AM, Jerry Amundson <jamundso(a)gmail.com> wrote:
On Sat, Oct 23, 2010 at 11:50 AM, M A Young
<m.a.young(a)durham.ac.uk> wrote:
> Try xen kernel-2.6.32.25-171.rc1.xendom0.fc12 instead at
> http://koji.fedoraproject.org/koji/taskinfo?taskID=2550132 or at the
> repository http://repos.fedorapeople.org/repos/myoung/dom0-kernel/ which has
> a fix for that and another security hole.
Anyone else seeing problems with software raid?
On a new Fedora 14 system, the distro kernel is fine, but my 4 SCSI
drive system has md devices fail with xendom0...
Oct 27 23:31:17 elm kernel: [ 40.504212] dracut: mdadm: /dev/md0 has
been started with 2 drives.
Oct 27 23:31:17 elm kernel: [ 40.590546] dracut: mdadm: /dev/md1 has
been started with 2 drives.
Oct 27 23:31:17 elm kernel: [ 40.629581] dracut: mdadm: /dev/md2 has
been started with 3 drives.
Oct 27 23:31:17 elm kernel: [ 40.709149] dracut: mdadm: /dev/md3 has
been started with 3 drives.
[snip]
Oct 27 23:39:55 elm kernel: dracut: mdadm: /dev/md0 has been started
with 2 drives.
Oct 27 23:39:55 elm kernel: dracut: mdadm: /dev/md1 has been started
with 2 drives.
Oct 27 23:39:55 elm kernel: mdadm[617]: segfault at 46 ip 006b7997 sp
bfe4b2d0 error 4 in libc-2.12.90.so[658000+18d000]
Oct 27 23:39:55 elm kernel: mdadm[636]: segfault at 46 ip 006b7997 sp
bfa19490 error 4 in libc-2.12.90.so[658000+18d000]
The "Oct 27 23:31:17" messages reflect fc14, while "Oct 27 23:39:55"
is xendom0.
The system boots fine, but just won't see the extra meta devices.
I was tripped up by my own kernel hopping - the current mdadm.conf
wasn't present in the initramfs made with the kernel install done
earlier. A mkinitrd for the needful kernel, and poof! the raid devices
are fine.
jerry
5:47 a.m.
New subject: another xen kernel
I am having trouble with F14, and this and the previous kernel:
http://pastie.org/1242707
The problem seems to start around line 687:
xen_balloon: Initialising balloon driver with page order 0.
last_pfn = 0x444690 max_arch_pfn = 0x400000000
BUG: unable to handle kernel paging request at ffffea000e700030
IP: [<ffffffff812351b7>] __list_add+0x6c/0x81
but I am not sure.
Here is the really weird thing, I have this system:
http://www.supermicro.com/Aplus/system/2U/2022/AS-2022TG-HTRF.cfm
with 4 machines using these mbs (with 1 AMD 6172 each):
http://www.supermicro.com/Aplus/motherboard/Opteron6100/SR56x0/H8DGT-HF.cfm
lshw output here: http://pastie.org/1242726
and one of the 4 systems is able to boot the system using xen but the others
all die at the same place (using the same disks to test all 4).
I have tried changing as many BIOS settings as I can - all the ACPI ones and
many others and I can get any change. (BIOS sucks btw, you can't print or
output the full config in any useful way to diff/track/compare them - argh!)
Here:
http://pastie.org/1242727
is the output of the one that does work, unfortunately as I monkeyed around
with it I think it is now not finding the igb NICs :(
The systems come up fine with both the current F14 kernel and both the latest
and previous dom0 kernel without xen
# uname -a
Linux xentest 2.6.32.23-170.1.xendom0.fc12.x86_64 #1 SMP Thu Oct 21 19:32:14
UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
Name : xen
Arch : x86_64
Version : 4.0.1
Release : 6.fc14
I tried a number of grub configs some with various debug and acpi/apic
settings but no luck, here is a simple one when I was trying the new kernel:
title Xen
root (hd1,0)
kernel /xen.gz dom0_mem=1024M loglvl=all guest_loglvl=all
module /vmlinuz-2.6.32.23-170.1.xendom0.fc12.x86_64 ro
root=UUID=84e6a109-84c5-4288-80de-ea368a224a3a
rd_MD_UUID=c557e3e8:d9ef50b8:b5e9861f:26975533
rd_MD_UUID=5825fd8c:77ea8324:ae0c8804:8a0c248
7 rd_NO_LUKS rd_NO_LVM rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16
KEYTABLE=us nomodeset
initrd /initramfs-2.6.32.23-170.1.xendom0.fc12.x86_64.img
Maybe I missed a step somewhere but with the xen 4.0.1.x in F14 and the dom0
kernel repo, I thought that there was no more manual compiling, etc - maybe I
was mistaken.
Any help/idea would be greatly appreciated. Thanks.
On 10/22/10 2:27 PM, M A Young wrote:
There is a new xen kernel (2.6.32.23-170.1.xendom0.fc12) available
to
download at http://koji.fedoraproject.org/koji/taskinfo?taskID=2547470 and
at the repository http://repos.fedorapeople.org/repos/myoung/dom0-kernel/
It contains some patches added added to xen/stable-2.6.32.x since the last
build, including an event channels fix.
Michael Young
--
xen mailing list
xen(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
12:04 p.m.
New subject: another xen kernel
On Sat, 23 Oct 2010, fcxen user wrote:
I am having trouble with F14, and this and the previous kernel:
http://pastie.org/1242707
The problem seems to start around line 687:
xen_balloon: Initialising balloon driver with page order 0.
last_pfn = 0x444690 max_arch_pfn = 0x400000000
BUG: unable to handle kernel paging request at ffffea000e700030
IP: [<ffffffff812351b7>] __list_add+0x6c/0x81
Did earlier kernels work or not or didn't you try them? Also do you have a
log from the 170.1 kernel or the newly built 171 kernel? These still have
the debuginfo packages available which means I can get a bit more
information about the crash.
Michael Young
4:06 p.m.
New subject: another xen kernel
170, 170.1, 171 crashed the same
using:
title Xen
root (hd0,0)
kernel /xen.gz loglvl=all guest_loglvl=all sync_console
console_to_ring com2=115200,8n1 console=com2,vga lapic=debug
apic_verbosity=debug apic=debug iommu=off
module /vmlinuz-2.6.32.25-171.rc1.xendom0.fc12.x86_64 ro
root=UUID=84e6a109-84c5-4288-80de-ea368a224a3a
rd_MD_UUID=c557e3e8:d9ef50b8:b5e9861f:26975533
rd_MD_UUID=5825fd8c:77ea8324:ae0c8804:8a0c2
487 rd_NO_LUKS rd_NO_LVM rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16
KEYTABLE=us console=hvc0 earlyprintk=xen nomodeset initcall_debug debug
loglevel=10
module /initramfs-2.6.32.25-171.rc1.xendom0.fc12.x86_64.img
Latest output is:
http://pastie.org/1243649
I could give you a login on the box if that would help...
Let me know if I should try other debug options/settings, thanks.
On 10/23/10 10:04 AM, M A Young wrote:
On Sat, 23 Oct 2010, fcxen user wrote:
> I am having trouble with F14, and this and the previous kernel:
>
> http://pastie.org/1242707
>
> The problem seems to start around line 687:
> xen_balloon: Initialising balloon driver with page order 0.
> last_pfn = 0x444690 max_arch_pfn = 0x400000000
> BUG: unable to handle kernel paging request at ffffea000e700030
> IP: [<ffffffff812351b7>] __list_add+0x6c/0x81
Did earlier kernels work or not or didn't you try them? Also do you have a log
from the 170.1 kernel or the newly built 171 kernel? These still have the
debuginfo packages available which means I can get a bit more information
about the crash.
Michael Young
4928
days inactive
4983
days old
34 comments
8 participants
participants (8)
-
Bill McGonigle -
Boris Derzhavets -
fcxen user -
itamar -
Jerry Amundson -
M A Young -
Pasi Kärkkäinen -
Virgil