[Fedora-xen] kernel BUG w/ Dom0

2010-03-22 Thread Jerry Amundson 
Serial output of boot is attached.
Quite possible I'm crazy to think I could get this to work... :-)
Machine is a Dell Optiplex 755 (Intel Core2 Duo) running FC12.
I rebuilt the 3.4.2-2 src rpm from fc13.

kernel-2.6.32.9-1.2.89.xendom0.fc12.x86_64
kernel-firmware-2.6.32.9-1.2.89.xendom0.fc12.noarch
kernel-headers-2.6.32.9-1.2.89.xendom0.fc12.x86_64
xen-3.4.2-2.fc12.x86_64
xen-doc-3.4.2-2.fc12.x86_64
xen-hypervisor-3.4.2-2.fc12.x86_64
xen-libs-3.4.2-2.fc12.x86_64
xen-runtime-3.4.2-2.fc12.x86_64

Thanks for any guidance,
jerry
 __  ___ _  _ __  _   
 \ \/ /___ _ __   |___ /| || |  |___ \  |___ \   / _| ___/ |___ \ 
  \  // _ \ '_ \|_ \| || |_   __) |__ __) | | |_ / __| | __) |
  /  \  __/ | | |  ___) |__   _| / __/|__/ __/ _|  _| (__| |/ __/ 
 /_/\_\___|_| |_| |(_) |_|(_)_| |_(_)_|  \___|_|_|
  
(XEN) Xen version 3.4.2 (jer...@dtint.com) (gcc version 4.4.3 20100127 (Red Hat 4.4.3-4) (GCC) ) Mon Mar 22 15:09:27 CDT 2010
(XEN) Latest ChangeSet: unavailable
(XEN) Console output is synchronous.
(XEN) Command line: dom0_mem=512M loglvl=all guest_loglvl=all sync_console console_to_ring com1=115200,8n1 console=com1 lapic=debug apic_verbosity=debug apic=debug iommu=off
(XEN) Video infor
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN)  Found 2 MBR signatures
(XEN)  Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)   - 0009e400 (usable)
(XEN)  000f - 0010 (reserved)
(XEN)  0010 - 7ddff800 (usable)
(XEN)  7ddff800 - 7de53c00 (ACPI NVS)
(XEN)  7de53c00 - 7de55c00 (ACPI data)
(XEN)  7de55c00 - 7e00 (reserved)
(XEN)  e000 - f000 (reserved)
(XEN)  fec0 - fed00400 (reserved)
(XEN)  fed2 - feda (reserved)
(XEN)  fee0 - fef0 (reserved)
(XEN)  ffb0 - 0001 (reserved)
(XEN) System RAM: 2013MB (2061940kB)
(XEN) ACPI: RSDP 000FEC00, 0024 (r2 DELL  )
(XEN) ACPI: XSDT 000FC5B3, 0074 (r1 DELLB9K   15 ASL61)
(XEN) ACPI: FACP 000FC6E3, 00F4 (r3 DELLB9K   15 ASL61)
(XEN) ACPI: DSDT FFF76BF6, 4596 (r1   DELLdt_ex 1000 INTL 20050624)
(XEN) ACPI: FACS 7DDFF800, 0040
(XEN) ACPI: SSDT FFF7B2AB, 00AA (r1   DELLst_ex 1000 INTL 20050624)
(XEN) ACPI: APIC 000FC7D7, 0092 (r1 DELLB9K   15 ASL61)
(XEN) ACPI: BOOT 000FC869, 0028 (r1 DELLB9K   15 ASL61)
(XEN) ACPI: ASF! 000FC891, 0096 (r32 DELLB9K   15 ASL61)
(XEN) ACPI: MCFG 000FC927, 003E (r1 DELLB9K   15 ASL61)
(XEN) ACPI: HPET 000FC965, 0038 (r1 DELLB9K   15 ASL61)
(XEN) ACPI: TCPA 000FCBC1, 0032 (r1 DELLB9K   15 ASL61)
(XEN) ACPI: DMAR 000FCBF3, 00D0 (r1 DELLB9K   15 ASL61)
(XEN) ACPI: SLIC 000FC99D, 0176 (r1 DELLB9K   15 ASL61)
(XEN) NUMA turned off
(XEN) Faking a node at -7ddff000
(XEN) Domain heap initialised
(XEN) found SMP MP-table at 000fe710
(XEN) DMI 2.5 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[7ddff80c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee0
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 7:7 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x05] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x00] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x01] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x02] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x03] disabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1])
(XEN) ACPI: IOAPIC (id[0x08] address[0xfec0] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec0, 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: 0xfed0
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) mapped APIC to 828be000 (fee0)
(XEN) mapped IOAPIC to 828bd000 (fec0)
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 2992.552 MHz processor.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 6144K
(XEN) CPU: Physical Pr

Re: [Fedora-xen] kernel BUG w/ Dom0

2010-03-23 Thread Jerry Amundson 
On 3/23/10, M A Young  wrote:
> On Mon, 22 Mar 2010, Jerry Amundson wrote:
>
>> Serial output of boot is attached.
>> Quite possible I'm crazy to think I could get this to work... :-)
>> Machine is a Dell Optiplex 755 (Intel Core2 Duo) running FC12.
>> I rebuilt the 3.4.2-2 src rpm from fc13.
>>
>> kernel-2.6.32.9-1.2.89.xendom0.fc12.x86_64
>
> That won't help you as kernel-2.6.32.9-1.2.89.xendom0.fc12 needs at least
> 3.4.3 or 4.0.0 (or release candidates for them). There is a 4.0.0 rc6
> source RPM at
> http://myoung.fedorapeople.org/dom0/src/xen-4.0.0-0.4.rc6.fc12.src.rpm
> though I will replace that later as rc7 has just come out.

Ok, thanks, I figured it was just me being me. I'll look for rc7 later then.
Is this documented anywhere for Fedora 12/13 dom0 setup? If not, I can
add this requirement to the xen and fedora wiki's, as it didn't jump
out at me.

I assume 3.4.3 would only be from the xen-3.4-testing hg bits? Any
pros/cons between 3.4 and 4.0? You provide the 4.0 so I suppose that
is targeted to be released with the dom0 kernel, so I would be wise to
go with that, right? :-)

thank you much,
jerry
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen

Re: [Fedora-xen] kernel-2.6.32.10-1.2.92.xendom0.fc12.x86_64 X broken on MacBook

2010-03-24 Thread Jerry Amundson 
On Wed, Mar 24, 2010 at 8:05 PM, W. Michael Petullo  wrote:
> I just tried kernel-2.6.32.10-1.2.92.xendom0.fc12.x86_64 from Mike
> Young's repository on my MacBook and found that the video driver does
> not seem to work. Lspci reports:
>
> 02:00.0 VGA compatible controller: nVidia Corporation GeForce 9400M (rev b1)

Have previous versions of the xendom0 kernels worked successfully?

> The system boots fine until X is supposed to start. Once this happens,
> the console freezes. Otherwise, the system continues to operate and
> respond to network traffic.
>
> The last thing I seen in Xorg.0.log is "(II) NOUVEAU(0): Opened GPU
> channel 2." In a *working* configuration, the next message logged is
> "(II) NOUVEAU(0): [DRI2] Setup complete."
>
> There seems to be some related work here:
>
> http://lists.xensource.com/archives/html/xen-devel/2010-02/msg01105.html

What is the grub.conf entry? Have you passed nomodeset to the kernel module?

jerry
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen

[Fedora-xen] no xen/xen.h in -devel

2010-03-27 Thread Jerry Amundson 
could/should kernel-PAE-devel have xen/?
no love trying to build a kernel module against it...

make -C /lib/modules/2.6.32.10-1.2.92.xendom0.fc12.i686.PAE/build
SUBDIRS=/home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd  modules
make[2]: Entering directory
`/usr/src/kernels/2.6.32.10-1.2.92.xendom0.fc12.i686.PAE'
  CC [M]  /home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/drbd_buildtag.o
  CC [M]  /home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/drbd_bitmap.o
  CC [M]  /home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/drbd_proc.o
In file included from include/linux/scatterlist.h:8,
 from include/linux/dma-mapping.h:7,
 from include/linux/dmaengine.h:26,
 from include/linux/skbuff.h:30,
 from include/linux/if_ether.h:124,
 from include/linux/netdevice.h:29,
 from include/net/sock.h:50,
 from include/linux/connector.h:80,
 from
/home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/linux/drbd.h:29,
 from
/home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/drbd_buildtag.c:2:
/usr/src/kernels/2.6.32.10-1.2.92.xendom0.fc12.i686.PAE/arch/x86/include/asm/io.h:10:21:
error: xen/xen.h: No such file or directory
In file included from include/linux/scatterlist.h:8,
 from include/linux/dma-mapping.h:7,
 from include/linux/dmaengine.h:26,
 from include/linux/skbuff.h:30,
 from include/linux/if_ether.h:124,
 from include/linux/netdevice.h:29,
 from include/net/sock.h:50,
 from include/linux/connector.h:80,
 from
/home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/linux/drbd.h:29,
 from
/home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/drbd_bitmap.c:28:
/usr/src/kernels/2.6.32.10-1.2.92.xendom0.fc12.i686.PAE/arch/x86/include/asm/io.h:10:21:
error: xen/xen.h: No such file or directory
In file included from include/linux/scatterlist.h:8,
 from include/linux/dma-mapping.h:7,
 from include/linux/dmaengine.h:26,
 from include/linux/skbuff.h:30,
 from include/linux/if_ether.h:124,
 from include/linux/netdevice.h:29,
 from include/net/sock.h:50,
 from include/linux/connector.h:80,
 from
/home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/linux/drbd.h:29,
 from /home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/drbd_proc.c:35:
/usr/src/kernels/2.6.32.10-1.2.92.xendom0.fc12.i686.PAE/arch/x86/include/asm/io.h:10:21:
error: xen/xen.h: No such file or directory
make[3]: *** [/home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/drbd_buildtag.o]
Error 1
make[3]: *** Waiting for unfinished jobs
make[3]: *** [/home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/drbd_proc.o] Error 1
make[3]: *** [/home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd/drbd_bitmap.o] Error 1
make[2]: *** [_module_/home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd] Error 2
make[2]: Leaving directory
`/usr/src/kernels/2.6.32.10-1.2.92.xendom0.fc12.i686.PAE'
make[1]: *** [kbuild] Error 2
make[1]: Leaving directory `/home/jerry/rpmbuild/BUILD/drbd-8.3.6/drbd'
make: *** [module] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.e3hCch (%build)


RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.e3hCch (%build)
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen

Re: [Fedora-xen] another xen kernel

2010-10-27 Thread Jerry Amundson 
On Sat, Oct 23, 2010 at 11:50 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  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
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen

Re: [Fedora-xen] another xen kernel

2010-10-29 Thread Jerry Amundson 
On Thu, Oct 28, 2010 at 1:03 AM, Jerry Amundson  wrote:
> On Sat, Oct 23, 2010 at 11:50 AM, M A Young  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
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen

Re: [Fedora-xen] 2.6.37-rc1 dom0 kernel

2010-11-14 Thread Jerry Amundson 
On Sat, Nov 13, 2010 at 6:41 AM, M A Young  wrote:
> There is another kernel to play with (2.6.37-0.1.rc1.git8.xendom0.fc15)
> at http://koji.fedoraproject.org/koji/taskinfo?taskID=2598434 .
> This has patches from xen/next-2.6.37 , which includes the gntdev module,
> so it should in theory be possible to use a userspace blkback.

I still get a dom0 crash, whereas 2.6.32.25-172.xendom0.fc12.i686.PAE
works fine on the same hardware with the same command line.

jerry
 __  ___  ____   _ __ __  _ _  _
 \ \/ /___ _ __   | || |  / _ \ / |   / /_   / _| ___/ | || |
  \  // _ \ '_ \  | || |_| | | || |__| '_ \ | |_ / __| | || |_
  /  \  __/ | | | |__   _| |_| || |__| (_) ||  _| (__| |__   _|
 /_/\_\___|_| |_||_|(_)___(_)_|   \___(_)_|  \___|_|  |_|

(XEN) Xen version 4.0.1 (mockbuild@(none)) (gcc version 4.5.1 20100924
(Red Hat 4.5.1-4) (GCC) ) Tue Oct 12 22:05:55 UTC 2010
(XEN) Latest ChangeSet: unavailable
(XEN) Console output is synchronous.
(XEN) Bootloader: GNU GRUB 0.97
(XEN) Command line: console=com1 com1=38400,8n1 console=com1
sync_console loglvl=all guest_loglvl=all
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: V2; EDID transfer time: 2 seconds
(XEN) Disc information:
(XEN)  Found 4 MBR signatures
(XEN)  Found 4 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)   - 000a (usable)
(XEN)  0010 - 7ffc (usable)
(XEN)  7ffc - 7ffcfc00 (ACPI data)
(XEN)  7ffcfc00 - 7000 (reserved)
(XEN)  fec0 - fec9 (reserved)
(XEN)  fed2 - fed8 (reserved)
(XEN)  fee0 - fee1 (reserved)
(XEN)  ffb0 - 0001 (reserved)
(XEN) System RAM: 2047MB (2096512kB)
(XEN) ACPI: RSDP 000FDC40, 0014 (r0 DELL  )
(XEN) ACPI: RSDT 000FDC54, 0030 (r1 DELL   PE700   1 MSFT  10A)
(XEN) ACPI: FACP 000FDC84, 0074 (r1 DELL   PE700   1 MSFT  10A)
(XEN) ACPI: DSDT 7FFC, 1821 (r1 DELLPE7xx  1 MSFT  10E)
(XEN) ACPI: FACS 7FFCFC00, 0040
(XEN) ACPI: APIC 000FDCF8, 0074 (r1 DELL   PE700   1 MSFT  10A)
(XEN) ACPI: SPCR 000FDD6C, 0050 (r1 DELL   PE700   1 MSFT  10A)
(XEN) No NUMA configuration found
(XEN) Faking a node at -7ffc
(XEN) Xen heap: 8MB (8856kB)
(XEN) Domain heap initialised
(XEN) found SMP MP-table at 000fe710
(XEN) DMI 2.3 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[7ffcfc0c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee0
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 15:3 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] disabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 1, version 32, address 0xfec0, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec1] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 2, version 32, address 0xfec1, GSI 24-47
(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 2 I/O APICs
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2793.137 MHz processor.
(XEN) CPU: Hyper-Threading is disabled
(XEN) CPU0: Intel Extended MCE MSRs (12) available
(XEN) Intel machine check reporting enabled
(XEN) I/O virtualisation disabled
(XEN) Total of 1 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) Platform timer is 3.579MHz ACPI PM Timer
(XEN) Allocated console ring of 16 KiB.
(XEN) Brought up 1 CPUs
(XEN) CPUIDLE: disabled due to no HPET. Force enable with 'cpuidle'.
(XEN) ACPI sleep modes: S3
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 32-bit, PAE, lsb
(XEN)  Dom0 kernel: 32-bit, PAE, lsb, paddr 0x40 -> 0x15ac000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   3800->3c00 (468836 pages
to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: c040->c15ac000
(XEN)  Init. ramdisk: c15ac000->c327da00
(XEN)  Phys-Mach map: c327e000->c3457d90
(XEN)  Start info:c3458000->c345847c
(XEN)  Page tables:   c3459000->c347a000
(XEN)  Boot stack:c347a000->c347b000
(XEN)  TOTAL: c000->c380
(XEN)  ENTRY ADDRESS: c0b05000
(XEN) Dom0 has maximum 1 VCPUs
(XEN) Scrubbing Free RAM: .done.
(XEN) trace.c:89:d32767 calc_tinfo_firs

Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2

2011-01-27 Thread Jerry Amundson 
On Thu, Jan 27, 2011 at 11:51 AM, W. Michael Petullo  wrote:
>> Actually it didn't, but (2.6.38-0.rc2.git3.2.xendom0.fc15) does at
>> http://koji.fedoraproject.org/koji/taskinfo?taskID=2744376
>>
>> I also now have a build of xen-4.1.0-rc2 at
>> http://koji.fedoraproject.org/koji/taskinfo?taskID=2744030
>
> I am presently testing these Xen and kernel packages. My initial
> impression is very positive. I am able to boot into X within Dom0 on my
> previously difficult hardware. Previous experiences are documented on
> this list, beginning with [1]. My WiFi adapter also works. So, I
> agree with Marko's statement so far, "Dom0 is now usable as a desktop
> computer." I will continue to use this as my primary environment and
> will report any issues I come across.

Me too. My "Failsafe KDE" is stable over an hour now!!
Video:
01:00.0 VGA compatible controller: ATI Technologies Inc RV610 [Radeon
HD 2400 XT]
Smolt::
http://www.smolts.org/client/show/pub_10d63815-f25a-45cc-a80a-d16d3f5f4af0

However, my "standard" KDE desktop hangs X after a few minutes. Should
I report to bz.r.c? I can easily reproduce this...

thanks,
jerry

[  1336.505] [mi] EQ overflowing. The server is probably stuck in an
infinite loop.
[  1336.506]
Backtrace:
[  1336.507] 0: /usr/bin/X (xorg_backtrace+0x28) [0x4a0488]
[  1336.507] 1: /usr/bin/X (mieqEnqueue+0x1f4) [0x49f994]
[  1336.507] 2: /usr/bin/X (xf86PostMotionEventP+0xc4) [0x47c744]
[  1336.507] 3: /usr/lib64/xorg/modules/input/evdev_drv.so
(0x7ff026da1000+0x453f) [0x7ff026da553f]
[  1336.507] 4: /usr/bin/X (0x40+0x6a447) [0x46a447]
[  1336.507] 5: /usr/bin/X (0x40+0x118c43) [0x518c43]
[  1336.507] 6: /lib64/libc.so.6 (0x3a9620+0x34100) [0x3a96234100]
[  1336.507] 7: /lib64/libc.so.6 (0x3a9620+0x136400) [0x3a96336400]
[  1336.507] 8: /usr/lib64/xorg/modules/libfb.so (fbBlt+0xf8) [0x7ff027bd0118]
[  1336.507] 9: /usr/lib64/xorg/modules/libfb.so (fbBltStip+0x40)
[0x7ff027bd0ec0]
[  1336.507] 10: /usr/lib64/xorg/modules/libfb.so (fbGetImage+0x206)
[0x7ff027bd6616]
[  1336.507] 11: /usr/lib64/xorg/modules/libexa.so
(0x7ff0279a8000+0x13988) [0x7ff0279bb988]
[  1336.507] 12: /usr/lib64/xorg/modules/libexa.so
(0x7ff0279a8000+0xbef8) [0x7ff0279b3ef8]
[  1336.507] 13: /usr/bin/X (0x40+0x1560d8) [0x5560d8]
[  1336.507] 14: /usr/lib64/xorg/modules/libexa.so
(exaGetPixmapFirstPixel+0xa9) [0x7ff0279bc839]
[  1336.507] 15: /usr/lib64/xorg/modules/libexa.so
(0x7ff0279a8000+0x10731) [0x7ff0279b8731]
[  1336.507] 16: /usr/bin/X (0x40+0xd6503) [0x4d6503]
[  1336.507] 17: /usr/bin/X (0x40+0xcf219) [0x4cf219]
[  1336.507] 18: /usr/bin/X (0x40+0x2d4d1) [0x42d4d1]
[  1336.507] 19: /usr/bin/X (0x40+0x2152e) [0x42152e]
[  1336.507] 20: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x3a9621ee7d]
[  1336.507] 21: /usr/bin/X (0x40+0x210d9) [0x4210d9]
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen

[Fedora-xen] EL 6 kernel missing kernel-headers

2011-07-29 Thread Jerry Amundson 
Hi, I'm trying to install the kernel from
http://xenbits.xen.org/people/mayoung/testing/i386/ and see...

[root@xen1 ~]# rpm -ivh kernel-2.6.32-71.29.1.el6.xendom0.i686.rpm
error: Failed dependencies:
kernel-firmware >= 2.6.32-71.29.1.el6.xendom0 is needed by
kernel-2.6.32-71.29.1.el6.xendom0.i686

Can kernel-firmware be uploaded as well?
thanks,
jerry
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen

Re: [Fedora-xen] EL 6 kernel missing kernel-headers

2011-07-29 Thread Jerry Amundson 
Sorry - first reply skipped the list...

oops - four characters... /xen, /vml, /ini.

jerry

On Fri, Jul 29, 2011 at 3:44 PM, Jerry Amundson  wrote:
> On Fri, Jul 29, 2011 at 3:30 PM, M A Young  wrote:
>> On Fri, 29 Jul 2011, Jerry Amundson wrote:
>>
>>> Hi, I'm trying to install the kernel from
>>> http://xenbits.xen.org/people/mayoung/testing/i386/ and see...
>>>
>>> [root@xen1 ~]# rpm -ivh kernel-2.6.32-71.29.1.el6.xendom0.i686.rpm
>>> error: Failed dependencies:
>>>       kernel-firmware >= 2.6.32-71.29.1.el6.xendom0 is needed by
>>> kernel-2.6.32-71.29.1.el6.xendom0.i686
>>>
>>> Can kernel-firmware be uploaded as well?
>>
>> Use the kernel-firmware package in the x86_64 directory. It is noarch so
>> will be the same for both i686 and x86_64.
>
> Perfect, thanks!
> Looks like something chops three chars out of grub.conf kernel/modules lines:
> title Enterprise Linux (2.6.32-71.29.1.el6.xendom0.i686)
>        root (hd0,0)
>        kernel .gz
>        module inuz-2.6.32-71.29.1.el6.xendom0.i686 ro
> root=/dev/mapper/vg_xen1-lv_root rd_LVM_LV=vg_xen1/lv_root
> rd_LVM_LV=vg_xen1/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM
> LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us
> crashkernel=auto rhgb quiet
>        module tramfs-2.6.32-71.29.1.el6.xendom0.i686.img
>
> Love to see it trying though! :-)
>
> thank you!
> jerry
>
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen

Re: [Fedora-xen] Grubby fix isn't enough for Fedora 16: Fedora 16 uses Grub2

2011-08-16 Thread Jerry Amundson 
On Tue, Aug 16, 2011 at 1:26 PM, Pasi Kärkkäinen  wrote:
> On Tue, Aug 16, 2011 at 09:03:19PM +0300, Marko Ristola wrote:
>>
>> Hi
>>
>
> Hello,
>
>> I've experimented with a fresh Fedora 16,
>>
>
> Thanks for testing!
> I need to install F16 myself aswell..

Me too! Though I may until the Alpha is out next week...

>> I've installed Fedora 16 from nightly CD.
>> Fedora 16 uses Grub2, so grubby fix isn't enough for dom0.
>> Grub2 has Xen Dom0 config script as /etc/grub.d/20_linux_xen on Fedora 16.
>> The script searches initrd-* files from /boot.
>> It should search initramfs-* files too. Thus Dom0 will not be able to boot.
>> I've written a bug report about that, maybe it is against Rawhide now, with
>> a patch to apply.
>>
>
> bz url?

https://bugzilla.redhat.com/show_bug.cgi?id=728775

jerry
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen

Re: [Fedora-xen] F15 kernel Xen support missing PCI passthrough?

2011-08-24 Thread Jerry Amundson 
On Wed, Aug 24, 2011 at 8:51 PM, Hilton Day  wrote:
> After recently discovering 2.6.40 is secretly Kernel 3 in disguise, and

Quoting http://fedoraproject.org/wiki/Features/XenPvopsDom0
"
Current status

Targeted release: Fedora 16
Last updated: 2010-07-24
Percentage of completion: 75%

In order to implement this feature, it is necessary to get full Xen
Dom0 support upstream and in Fedora. The core Dom0 support has been
accepted upstream and was released in Linux 2.6.37. Linux 2.6.39
brought support for the Xen network backend driver. Linux 3.0 brought
the block backend driver. Linux 3.1 will bring the pci backend driver
(for pci passthru).
"

hth,
jerry
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen

Re: [Fedora-xen] F15 kernel Xen support missing PCI passthrough?

2011-08-24 Thread Jerry Amundson 
On Wed, Aug 24, 2011 at 11:16 PM, Hilton Day  wrote:
> On 25/08/2011 12:47 PM, Jerry Amundson wrote:
>>
>> On Wed, Aug 24, 2011 at 8:51 PM, Hilton Day
>>  wrote:
>>>
>>> After recently discovering 2.6.40 is secretly Kernel 3 in disguise, and
>>
>> the block backend driver. Linux 3.1 will bring the pci backend driver
>> (for pci passthru).
>>
>
> Thanks Jerry - I saw the page but missed the comment on "passthru", so as
> usual RTFM saves the day.
>
> Looks like F15 won't work for me - no worries as its just a test build for
> replacement of the actual server at some undetermined future date.
>
> I'm installing F16 rawhide on a spare machine and will follow its progress
> with interest.  Given 3.1 is in RC phase, it may yet make it into F16.  I
> was already running libvirt-0.9.0.f16 on my F15 box (rebuilt from SRPM), and
> if pciback makes it into 3.1 in time, F16 will finally be the killer
> (supported) dom0 solution I've been waiting for since FC6.

Amen to that. I don't know if the problems were political or technical
or both, but Xen really got screwed from our point of view. The
majority of hardware on Earth is currently *not* capable of full
virtualization, but commit to it anyway. Hmm.

jerry
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen

Re: [Fedora-xen] fedora 16 with xen balloning.

2011-09-28 Thread Jerry Amundson 
On Wed, Sep 28, 2011 at 3:11 PM, Itamar Reis Peixoto <
ita...@ispbrasil.com.br> wrote:

> On Wed, Sep 28, 2011 at 4:32 PM, Itamar Reis Peixoto
>  wrote:
> > On Wed, Sep 28, 2011 at 4:21 PM, Konrad Rzeszutek Wilk
> >  wrote:
> >> On Wed, Sep 28, 2011 at 04:16:52PM -0300, Itamar Reis Peixoto wrote:
> >>> hi.
> >>>
> >>> I have a fedora 16 with all updates.
> >>>
> >>> when I run xm mem-set 0 1024 the machines crashes after some seconds.
>

xm mem-set 0 1536
worked fine for me.
(My KDE workstation, so 1024 is too little RAM to do day-job :-)


> >>
> >> What is the crash (serial log please)? How much memory do you have
> initially?
> >> Does it crash if you have 'dom0_mem=max:2G' on your Xen hypervisor line?
> >>
> >> Does it crash if you use 'xl mem-set 0 1024'?
> >>
> >>
> >
> > [root@localhost ~]# uname -a
> > Linux localhost.localdomain 3.1.0-0.rc6.git0.3.fc16.x86_64 #1 SMP Fri
> > Sep 16 12:26:22 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
> >
> > [root@localhost ~]# xm list
> > NameID   Mem VCPUs  State
> Time(s)
> > Domain-0 0  3584 4 r-
> 40.4
> > [root@localhost ~]#
> >
> >
> > [root@localhost ~]# xl mem-set 0 1024
> > libxl: error: libxl.c:2114:libxl_set_memory_target cannot get memory
> > info from /local/domain/0/memory/static-max
> > : No such file or directory
> > [root@localhost ~]#
> >
> >
> > had to reboot after xm mem-set 0 1024
>

You previously said crash - which is it? They are two different things.
Did you wait a fair amount of time?
Check for disk activity? It may just need some swapping...


> also virt-manager doesn't recognize it as dom0, I see some messages in log
>
> [   22.531841] XENBUS: Unable to read cpu state
> [   22.531981] XENBUS: Unable to read cpu state
> [   22.532213] XENBUS: Unable to read cpu state
> [   22.532350] XENBUS: Unable to read cpu state
>
>
virt-manager does not log to messages, so those two things are unrelated.
What happens when you try virt-manager?
What is in /root/.virt-manager/virt-manager.log?

jerry
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen

Re: [Fedora-xen] xen build for testing

2011-11-08 Thread Jerry Amundson 
On Mon, Nov 7, 2011 at 6:56 PM, M A Young  wrote:

> I have done a temporary test build xen-4.1.2-1.1 at
> http://koji.fedoraproject.org/koji/taskinfo?taskID=3495905
> which contains patches from
> http://lists.xensource.com/archives/html/xen-devel/2011-11/msg00218.html
> http://lists.xensource.com/archives/html/xen-devel/2011-11/msg00321.html
>
> which I would like to test before putting them into a released version.
> If anyone else wants to test it, please let me know whether it works.
>
>Michael Young
> --
> xen mailing list
> xen@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/xen


Noted this during the upgrade:
  Updating   : xen-hypervisor-4.1.2-1.1.fc16.x86_64
3/12
/var/tmp/rpm-tmp.3dxNvP: line 1: [: too many arguments

postinstall scriptlet (using /bin/sh):
if [ $1 = 0 -f /sbin/grub2-mkconfig -a -f /boot/grub2/grub.cfg ]; then
  /sbin/grub2-mkconfig -o /boot/grub2/grub.cfg
fi

Missing a "-a" in there, me thinks. :-)

jerry
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen

Re: [Fedora-xen] Xen Not Displayed in Boot Menu

2012-06-27 Thread Jerry Amundson 
On Sat, Jun 9, 2012 at 6:37 AM, Pasi Kärkkäinen  wrote:
> On Fri, Jun 08, 2012 at 12:00:44AM -0700, sorabh hamirwasia wrote:
>>    Hi,
>>    I have installed "Xen" on Fedora16 host using "yum install xen" command
>>    and it has been installed properly. I can see the changes in
>>    /etc/grub2.cfg file too. But when I reboot then the entry for Xen is not
>>    listed in the boot menu. On further analyzing I found that in
>>    /etc/grub.conf there is no entry related to Xen. Do we need to modify
>>    grub.conf manually ? If yes then how to do that. ?
>>    Please help me with this.
>
> You can tweak the Xen hypervisor cmdline options in:
> /etc/default/grub file, like this:
>
> GRUB_DEFAULT="Xen"

The only thing I see in fc17 (also) is a
set default="Xen"
line in /boot/grub2/grub.cfg

I've been waiting, hoping, and did a fresh install of Fedora 17, then
"yum install xen", in anticipation (again) of Fedora/Xen/dom0 boot
magic.
Disappointment.

Thanks anyway,
jerry
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen

Re: [Fedora-xen] Xen Not Displayed in Boot Menu

2012-08-12 Thread Jerry Amundson 
On Thu, Jun 28, 2012 at 9:22 AM, Pasi Kärkkäinen  wrote:
> On Wed, Jun 27, 2012 at 10:40:01PM -0500, Jerry Amundson wrote:
>> On Sat, Jun 9, 2012 at 6:37 AM, Pasi Kärkkäinen  wrote:
>> > On Fri, Jun 08, 2012 at 12:00:44AM -0700, sorabh hamirwasia wrote:
>> >>Hi,
>> >>I have installed "Xen" on Fedora16 host using "yum install xen" command
>> >>and it has been installed properly. I can see the changes in
>> >>/etc/grub2.cfg file too. But when I reboot then the entry for Xen is 
>> >> not
>> >>listed in the boot menu. On further analyzing I found that in
>> >>/etc/grub.conf there is no entry related to Xen. Do we need to modify
>> >>grub.conf manually ? If yes then how to do that. ?
>> >>Please help me with this.
>> >
>> > You can tweak the Xen hypervisor cmdline options in:
>> > /etc/default/grub file, like this:
>> >
>> > GRUB_DEFAULT="Xen"
>>
>> The only thing I see in fc17 (also) is a
>> set default="Xen"
>> line in /boot/grub2/grub.cfg
>>
>> I've been waiting, hoping, and did a fresh install of Fedora 17, then
>> "yum install xen", in anticipation (again) of Fedora/Xen/dom0 boot
>> magic.
>> Disappointment.
>>
>
> And did you run "grub2-mkconfig -o /boot/grub2/grub.cfg" ?
>
> What's the problem?

FWIW, my original problem, being that the system in question is i686,
was that kernel-PAE had not been installed before xen-hypervisor.
However, even after that the
set default="Xen"
accomplishes nothing as "Xen" does not exactly match the entries put
in place by grub2-mkconfig.

So, getting further along, but still no Xen without manual assistance.

jerry
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen

Re: [Fedora-xen] Xen Not Displayed in Boot Menu

2012-08-13 Thread Jerry Amundson 

On 08/13/2012 12:57 PM, Konrad Rzeszutek Wilk wrote:

On Sun, Aug 12, 2012 at 10:49:15PM -0500, Jerry Amundson wrote:

On Thu, Jun 28, 2012 at 9:22 AM, Pasi Kärkkäinen  wrote:

On Wed, Jun 27, 2012 at 10:40:01PM -0500, Jerry Amundson wrote:

On Sat, Jun 9, 2012 at 6:37 AM, Pasi Kärkkäinen  wrote:

On Fri, Jun 08, 2012 at 12:00:44AM -0700, sorabh hamirwasia wrote:

Hi,
I have installed "Xen" on Fedora16 host using "yum install xen" command
and it has been installed properly. I can see the changes in
/etc/grub2.cfg file too. But when I reboot then the entry for Xen is not
listed in the boot menu. On further analyzing I found that in
/etc/grub.conf there is no entry related to Xen. Do we need to modify
grub.conf manually ? If yes then how to do that. ?
Please help me with this.

You can tweak the Xen hypervisor cmdline options in:
/etc/default/grub file, like this:

GRUB_DEFAULT="Xen"

The only thing I see in fc17 (also) is a
set default="Xen"
line in /boot/grub2/grub.cfg

I've been waiting, hoping, and did a fresh install of Fedora 17, then
"yum install xen", in anticipation (again) of Fedora/Xen/dom0 boot
magic.
Disappointment.


And did you run "grub2-mkconfig -o /boot/grub2/grub.cfg" ?

What's the problem?

FWIW, my original problem, being that the system in question is i686,
was that kernel-PAE had not been installed before xen-hypervisor.
However, even after that the
set default="Xen"
accomplishes nothing as "Xen" does not exactly match the entries put

Whoops. Did putting 'Xen 4.1.2" do it?


Nope, but
set default="Fedora, with Xen hypervisor"
does work.
At first glance, I didn't see how to fix that, but can look if I get time.

The second problem is that the grub menu entries are built from 
/boot/xen*, but they should not be, as such a list includes xen-syms* 
(not bootable), and symlinks which just repeat entries. [thought I 
brought this up or bz'd this before... hmm.]

I hacked together these changes to 20_linux_xen which worked for me

# diff -u 20_linux_xen*
--- 20_linux_xen2012-08-13 16:45:17.315983439 -0500
+++ 20_linux_xen~   2012-06-18 15:05:32.0 -0500
@@ -23,18 +23,6 @@

 . "/usr/share/grub/grub-mkconfig_lib"

-xen_grub_file_is_not_garbage ()
-{
-  if test -f "$1" -a ! -h "$1"; then
-case "$1" in
-  *-syms-*) return 1 ;;
-esac
-  else
-return 1
-  fi
-  return 0
-}
-
 export TEXTDOMAIN=grub
 export TEXTDOMAINDIR="${datarootdir}/locale"

@@ -168,10 +156,7 @@
 if [ "x${linux_list}" = "x" ] ; then
 exit 0
 fi
-xen_try=`for f in /boot/xen*; do
-if xen_grub_file_is_not_garbage "$f" ; then echo -n "$f " ; fi
-  done`
-xen_list=`for i in $xen_try; do
+xen_list=`for i in /boot/xen*; do
 if grub_file_is_not_garbage "$i" ; then echo -n "$i " ; fi
   done`
 prepare_boot_cache=

--
jerry

--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen

Re: [Fedora-xen] Xen Not Displayed in Boot Menu

2012-08-13 Thread Jerry Amundson 
On Mon, Aug 13, 2012 at 5:06 PM, Jerry Amundson  wrote:
> On 08/13/2012 12:57 PM, Konrad Rzeszutek Wilk wrote:
>> Whoops. Did putting 'Xen 4.1.2" do it?
>>
> Nope, but
> set default="Fedora, with Xen hypervisor"
> does work.
> At first glance, I didn't see how to fix that, but can look if I get time.

And it appears that was my fault to begin with as well...
/etc/default/grub contained
GRUB_DEFAULT="Xen"
which was likely added by me. The grub2-tools install owns
/etc/default/grub but does not create one at install. Weird.
Sorry this turned into a grub2 infommercial...

jerry
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen