September 2009 - xen - Fedora mailing-lists

No pcifront in F10?
by Jim Lutz 25 Oct '10

25 Oct '10

I have a virtual machine landscape consisting of a CentOS 5.3 Dom0 with Xen 3.1.2, some PV CentOS DomU's with PCI passthrough (same versions), and I'm trying to implement a F10 DomU with PCI passthrough. I set everything up for the passthrough, and the F10 guest can't see any of the devices with lspci. If I boot a CentOS PV machine with the same PCI passthrough configuration, the devices show up with lspci. I've seen some posts in various places about this issue, but no solutions. How do I implement this?

4 11

Dom0 kernels
by M A Young 13 Mar '10

13 Mar '10

I have built a new set of kernel packages based on fedora rawhide kernels and the xen/dom0/hackery branch of Jeremy's git repository ( http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=summary ). This batch (kernel-2.6.29-0.114.2.6.rc6.fc11) is available via the koji build system at http://koji.fedoraproject.org/koji/taskinfo?taskID=1149500 These are really for development and debugging purposes only, as I am still having problems getting them to boot, but others have reported more success at getting kernels based on this git repository working, so you might be lucky. Note to install these packages on Fedora 10 you will need to have rpm-4.6.0-1.fc10 installed (currently in updates-testing but it should be available in updates soon) because of the change to SHA-256 file digest hashing in recent Fedora 11 builds. Michael Young

12 99

Fedora 12 (rawhide) Xen domU works now, minor console keymap issue?
by Pasi Kärkkäinen 08 Nov '09

08 Nov '09

Hello, Kernel 2.6.31-0.203.rc8.git2.fc12.i686.PAE for F12/rawhide domU seems to work now on my F11 host with xen-3.4.1-3 + libvirt from F11 updates-testing + 2.6.31-rc6 pv_ops dom0 kernel. There's a minor issue with domU vfb graphical console keymap though.. The F11 host has 'fi' (Finnish) keymap, and the F12 domU/guest is also installed with 'fi' keymap. All the 'special' keys on the graphical console (virt-viewer) are broken.. I don't really know what the resulting keymap is, but it's pretty weird. Not english, not finnish, not anything I know of.. List of the important characters that are broken: * / - _ | ? \ ( ) Either you can't make them at all, or you have to press totally wrong buttons to get them.. so the console is really painful or impossible to use. Any ideas how to debug this? Or is non-US even supposed to work? Thanks! -- Pasi

1 2

f11 domU 2.6.30 will not boot on f8 dom0
by Dale Bewley 29 Oct '09

29 Oct '09

Host is a f8 dom0 running xen-3.1.2-5.fc8 and kernel 2.6.21.7-5.fc8xen.x86_64. I updated a f10 guest domU to the latest kernel update 2.6.27.30-170.2.82.fc10.x86_64 and rebooted it without problem. I updated a f11 domU to kernel-2.6.30.5-43.fc11.x86_64 and the guest crashes after grub. Cracking open the image and setting grub back to kernel-2.6.29.6-217.2.16.fc11.x86_64 got me up and running. xm dmesg shows (XEN) traps.c:405:d117 Unhandled general protection fault fault/trap [#13] in domain 117 on VCPU 0 [ec=0000] (XEN) domain_crash_sync called from entry.S (XEN) Domain 117 (vcpu#0) crashed on cpu#3: (XEN) ----[ Xen-3.1.4 x86_64 debug=n Not tainted ]---- (XEN) CPU: 3 (XEN) RIP: e033:[<ffffffff813cda87>] (XEN) RFLAGS: 0000000000000282 CONTEXT: guest (XEN) rax: 000000008000c068 rbx: 000000000000c000 rcx: 0000000000000068 (XEN) rdx: 0000000000000cf8 rsi: 0000000000000018 rdi: 0000000000000000 (XEN) rbp: ffffffff8172de48 rsp: ffffffff8172dde0 r8: 0000000000000068 (XEN) r9: ffffffff8172de60 r10: ffffffff8172de68 r11: 00000000ffffffff (XEN) r12: ffffffff81697500 r13: ffffffff8172df78 r14: ffffffffffffffff (XEN) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000006f0 (XEN) cr3: 00000002f53fe000 cr2: 0000000000000000 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 (XEN) Guest stack trace from rsp=ffffffff8172dde0: (XEN) 0000000000000068 00000000ffffffff 0000000000000000 ffffffff813cda87 (XEN) 000000010000e030 0000000000010082 ffffffff8172de28 000000000000e02b (XEN) ffffffff813cda4d ffffffff8172de88 965f5967f03da9c3 ffffffff8100a7ed (XEN) ffffffff81722b80 ffffffff8172de88 ffffffff8148f7c1 00020f5103000800 (XEN) 0000000000000000 0000302800000000 965f5967f03da9c3 ffffffffffffffff (XEN) 0000000000000018 ffffffff8172dea8 ffffffff81760bc2 ffffffff8179ca10 (XEN) 0000000000000000 ffffffff8172df58 ffffffff8175ce66 0000000000000000 (XEN) 965f5967f03da9c3 ffffffff8172dee8 ffffffff8179ca10 0000000000000000 (XEN) 0000000000000000 ffffffffffffffff 0000000000000000 ffffffff8172df58 (XEN) ffffffff81495adb ffffffff00000010 ffffffff8172df68 ffffffff8172df28 (XEN) 965f5967f03da9c3 00000000a1b58930 ffffffff8179ca10 0000000000000000 (XEN) 0000000000000000 ffffffffffffffff 0000000000000000 ffffffff8172dfa8 (XEN) ffffffff81757d0b ffffffff8172dfa8 965f5967f03da9c3 ffffffff82226000 (XEN) 0000000000000000 00000000019d0f60 0000000000000000 0000000000000000 (XEN) 0000000000000000 ffffffff8172dfd8 ffffffff817572d0 0000000000000018 (XEN) 0000000000000000 0000000000000000 ffffffff82226000 ffffffff8172dff8 (XEN) ffffffff8175b4e0 0000000000000000 0000000000000000 0000000000000000 (XEN) ffffffff82123000 ffffffff82124000 ffffffff82125000 ffffffff82126000 (XEN) ffffffff82127000 ffffffff82128000 ffffffff82129000 ffffffff8212a000 (XEN) ffffffff8212b000 ffffffff8212c000 ffffffff8212d000 ffffffff8212e000 (XEN) traps.c:405:d118 Unhandled general protection fault fault/trap [#13] in domain 118 on VCPU 0 [ec=0000] (XEN) domain_crash_sync called from entry.S

1 1

Linux 2.6.31 domU crashes very early on RHEL5 Xen hypervisor (xen_load_gdt_boot / HYPERVISOR_update_va_mapping)
by Pasi Kärkkäinen 24 Sep '09

24 Sep '09

Hello, I tried running the latest Fedora 12 rawhide kernel (2.6.31-33.fc12.x86_64) as Xen domU on RHEL5.4 x86_64 Xen dom0. domU kernel crashes very early, there's no console output at all. # /usr/lib64/xen/bin/xenctx -s System.map-2.6.31-33.fc12.x86_64 1 rip: ffffffff819f8d3f xen_load_gdt_boot+0xab rsp: ffffffff81743f08 rax: ffffffea rbx: ffffffff81822000 rcx: 0021f527 rdx: 00000000 rsi: 800000021f527061 rdi: ffffffff81822000 rbp: ffffffff81743fa8 r8: 00000000 r9: 00000000 r10: 00000000 r11: 00000000 r12: ffffffff81743fb8 r13: ffffffff81743f50 r14: 00000080 r15: 00000000 cs: 0000e033 ds: 00000000 fs: 00000000 gs: 00000000 Stack: 000000000021f527 0000000000000000 ffffffff819f8d3f 000000010000e030 0000000000010082 ffffffff81743f48 000000000000e02b ffffffff819f8d3b 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000001822 0000008000000000 ffffffff8100cb0e 0000000000000000 Code: 20 c3 78 81 31 d2 48 89 c6 48 89 df e8 85 04 61 ff 85 c0 74 04 <0f> 0b eb fe 49 63 c7 48 81 c3 00 Call Trace: [<ffffffff819f8d3f>] xen_load_gdt_boot+0xab <-- [<ffffffff819f8d3f>] xen_load_gdt_boot+0xab [<ffffffff819f8d3b>] xen_load_gdt_boot+0xa7 [<ffffffff8100cb0e>] p2m_top_index+0x9 [<ffffffff8101f209>] switch_to_new_gdt+0x31 [<ffffffff819f8a24>] xen_start_kernel+0x282 # gdb vmlinux (gdb) x/i 0xffffffff819f8d3f 0xffffffff819f8d3f <xen_load_gdt_boot+171>: ud2a (gdb) x/60i xen_load_gdt_boot 0xffffffff819f8c94 <xen_load_gdt_boot>: push %rbp 0xffffffff819f8c95 <xen_load_gdt_boot+1>: mov %rsp,%rbp 0xffffffff819f8c98 <xen_load_gdt_boot+4>: push %r15 0xffffffff819f8c9a <xen_load_gdt_boot+6>: xor %r15d,%r15d 0xffffffff819f8c9d <xen_load_gdt_boot+9>: push %r14 0xffffffff819f8c9f <xen_load_gdt_boot+11>: push %r13 0xffffffff819f8ca1 <xen_load_gdt_boot+13>: push %r12 0xffffffff819f8ca3 <xen_load_gdt_boot+15>: mov %rdi,%r12 0xffffffff819f8ca6 <xen_load_gdt_boot+18>: push %rbx 0xffffffff819f8ca7 <xen_load_gdt_boot+19>: sub $0x18,%rsp 0xffffffff819f8cab <xen_load_gdt_boot+23>: movzwl (%rdi),%eax 0xffffffff819f8cae <xen_load_gdt_boot+26>: mov 0x2(%rdi),%rbx 0xffffffff819f8cb2 <xen_load_gdt_boot+30>: inc %eax 0xffffffff819f8cb4 <xen_load_gdt_boot+32>: mov %eax,%r14d 0xffffffff819f8cb7 <xen_load_gdt_boot+35>: mov %eax,-0x34(%rbp) 0xffffffff819f8cba <xen_load_gdt_boot+38>: lea 0xfff(%r14),%rax 0xffffffff819f8cc1 <xen_load_gdt_boot+45>: shr $0xc,%rax 0xffffffff819f8cc5 <xen_load_gdt_boot+49>: lea 0x1e(,%rax,8),%rax 0xffffffff819f8ccd <xen_load_gdt_boot+57>: and $0x7f0,%eax 0xffffffff819f8cd2 <xen_load_gdt_boot+62>: sub %rax,%rsp 0xffffffff819f8cd5 <xen_load_gdt_boot+65>: lea 0xf(%rsp),%r13 0xffffffff819f8cda <xen_load_gdt_boot+70>: and $0xfffffffffffffff0,%r13 0xffffffff819f8cde <xen_load_gdt_boot+74>: test $0xfff,%ebx 0xffffffff819f8ce4 <xen_load_gdt_boot+80>: je 0xffffffff819f8d55 <xen_load_gdt_boot+193> 0xffffffff819f8ce6 <xen_load_gdt_boot+82>: ud2a 0xffffffff819f8ce8 <xen_load_gdt_boot+84>: jmp 0xffffffff819f8ce8 <xen_load_gdt_boot+84> 0xffffffff819f8cea <xen_load_gdt_boot+86>: mov %rbx,%rdi 0xffffffff819f8ced <xen_load_gdt_boot+89>: callq 0xffffffff8103ecfc <__phys_addr> 0xffffffff819f8cf2 <xen_load_gdt_boot+94>: mov %rax,%rsi 0xffffffff819f8cf5 <xen_load_gdt_boot+97>: shr $0xc,%rsi 0xffffffff819f8cf9 <xen_load_gdt_boot+101>: mov %rsi,%rdi 0xffffffff819f8cfc <xen_load_gdt_boot+104>: mov %rsi,-0x40(%rbp) 0xffffffff819f8d00 <xen_load_gdt_boot+108>: callq 0xffffffff8100b397 <pfn_to_mfn> 0xffffffff819f8d05 <xen_load_gdt_boot+113>: mov -0x40(%rbp),%rsi 0xffffffff819f8d09 <xen_load_gdt_boot+117>: mov %rax,%rcx 0xffffffff819f8d0c <xen_load_gdt_boot+120>: mov $0x8000000000000161,%rax 0xffffffff819f8d16 <xen_load_gdt_boot+130>: and -0x1e362d(%rip),%rax # 0xffffffff818156f0 <__supported_pte_mask> 0xffffffff819f8d1d <xen_load_gdt_boot+137>: mov %rsi,%rdi 0xffffffff819f8d20 <xen_load_gdt_boot+140>: shl $0xc,%rdi 0xffffffff819f8d24 <xen_load_gdt_boot+144>: or %rax,%rdi 0xffffffff819f8d27 <xen_load_gdt_boot+147>: callq *0xffffffff8178c320 0xffffffff819f8d2e <xen_load_gdt_boot+154>: xor %edx,%edx 0xffffffff819f8d30 <xen_load_gdt_boot+156>: mov %rax,%rsi 0xffffffff819f8d33 <xen_load_gdt_boot+159>: mov %rbx,%rdi 0xffffffff819f8d36 <xen_load_gdt_boot+162>: callq 0xffffffff810091c0 <hypercall_page+448> 0xffffffff819f8d3b <xen_load_gdt_boot+167>: test %eax,%eax 0xffffffff819f8d3d <xen_load_gdt_boot+169>: je 0xffffffff819f8d43 <xen_load_gdt_boot+175> 0xffffffff819f8d3f <xen_load_gdt_boot+171>: ud2a 0xffffffff819f8d41 <xen_load_gdt_boot+173>: jmp 0xffffffff819f8d41 <xen_load_gdt_boot+173> 0xffffffff819f8d43 <xen_load_gdt_boot+175>: movslq %r15d,%rax 0xffffffff819f8d46 <xen_load_gdt_boot+178>: add $0x1000,%rbx 0xffffffff819f8d4d <xen_load_gdt_boot+185>: inc %r15d 0xffffffff819f8d50 <xen_load_gdt_boot+188>: mov %rcx,0x0(%r13,%rax,8) 0xffffffff819f8d55 <xen_load_gdt_boot+193>: mov %r14,%rax 0xffffffff819f8d58 <xen_load_gdt_boot+196>: add 0x2(%r12),%rax 0xffffffff819f8d5d <xen_load_gdt_boot+201>: cmp %rax,%rbx 0xffffffff819f8d60 <xen_load_gdt_boot+204>: jb 0xffffffff819f8cea <xen_load_gdt_boot+86> 0xffffffff819f8d62 <xen_load_gdt_boot+206>: mov -0x34(%rbp),%esi 0xffffffff819f8d65 <xen_load_gdt_boot+209>: mov %r13,%rdi 0xffffffff819f8d68 <xen_load_gdt_boot+212>: shr $0x3,%esi (gdb) So that translates to: if (HYPERVISOR_update_va_mapping((unsigned long)va, pte, 0)) BUG(); return value was -EINVAL Any ideas? I also opened fedora bugzilla entry here: https://bugzilla.redhat.com/show_bug.cgi?id=525290 -- Pasi

2 1

Paravirtualization - Fedora-XEN - run windows
by Lolo Andrew 23 Sep '09

23 Sep '09

Dear Expert Got any release of Fedora-Xen that can support windows on paravirtualization. if I wanna to customized the existing feature, what direction should i go, to install to or make windows 32bit be able to run stable on bare Fedora-xen based bare metal machine? Like kernel, driver over the windows side, any many more, rather than having a enterprise solution I still newbie, I would like to have expert advice and opinion to make it be possible. Your faithfully Guy

2 1

Fedora 11 PV Xen domU (2.6.29.4-167.fc11.x86_64) crash with invalid opcode in xsave_cntxt_init (xsetbv)
by Pasi Kärkkäinen 22 Sep '09

22 Sep '09

Hello Jeremy and others, I friend of mine is trying to install x86_64 Fedora 11 Xen PV domU on CentOS 5.4 x86_64 dom0. He's getting a kernel crash.. so I was wondering if you've seen this one before. A couple of kernel boot/crash logs: http://v6.fi/misc/f11_64_kernel.debug2.txt http://v6.fi/misc/f11_64_kernel.debug4.txt (early) Kernel command line: root=/dex/xvda1 ro earlyprintk=xen (early) Initializing CPU#0 (early) invalid opcode: 0000 [#1] (early) SMP (early) (early) last sysfs file: (early) CPU 0 (early) (early) Modules linked in:(early) (early) Pid: 0, comm: swapper Not tainted 2.6.29.4-167.fc11.x86_64 #1 (early) RIP: e030:[<ffffffff81397963>] (early) [<ffffffff81397963>] xsave_cntxt_init+0xba/0x199 [root@dom0 RH]# gdb vmlinux (gdb) x/i 0xffffffff81397963 0xffffffff81397963 <xsave_cntxt_init+186>: xsetbv (gdb) x/60i xsave_cntxt_init 0xffffffff813978a9 <xsave_cntxt_init>: push %rbp 0xffffffff813978aa <xsave_cntxt_init+1>: mov %rsp,%rbp 0xffffffff813978ad <xsave_cntxt_init+4>: push %r14 0xffffffff813978af <xsave_cntxt_init+6>: push %r13 0xffffffff813978b1 <xsave_cntxt_init+8>: push %r12 0xffffffff813978b3 <xsave_cntxt_init+10>: push %rbx 0xffffffff813978b4 <xsave_cntxt_init+11>: sub $0x10,%rsp 0xffffffff813978b8 <xsave_cntxt_init+15>: callq 0xffffffff81011000 <mcount> 0xffffffff813978bd <xsave_cntxt_init+20>: lea -0x24(%rbp),%rbx 0xffffffff813978c1 <xsave_cntxt_init+24>: lea -0x28(%rbp),%r12 0xffffffff813978c5 <xsave_cntxt_init+28>: lea -0x2c(%rbp),%r13 0xffffffff813978c9 <xsave_cntxt_init+32>: lea -0x30(%rbp),%r14 0xffffffff813978cd <xsave_cntxt_init+36>: movl $0xd,-0x24(%rbp) 0xffffffff813978d4 <xsave_cntxt_init+43>: movl $0x0,-0x2c(%rbp) 0xffffffff813978db <xsave_cntxt_init+50>: mov %rbx,%rdi 0xffffffff813978de <xsave_cntxt_init+53>: mov %r12,%rsi 0xffffffff813978e1 <xsave_cntxt_init+56>: mov %r13,%rdx 0xffffffff813978e4 <xsave_cntxt_init+59>: mov %r14,%rcx 0xffffffff813978e7 <xsave_cntxt_init+62>: callq *0x1f24b3(%rip) # 0xffffffff81589da0 <pv_cpu_ops+224> 0xffffffff813978ed <xsave_cntxt_init+68>: mov -0x30(%rbp),%eax 0xffffffff813978f0 <xsave_cntxt_init+71>: mov -0x24(%rbp),%esi 0xffffffff813978f3 <xsave_cntxt_init+74>: shl $0x20,%rax 0xffffffff813978f7 <xsave_cntxt_init+78>: lea (%rax,%rsi,1),%rsi 0xffffffff813978fb <xsave_cntxt_init+82>: mov %rsi,%rax 0xffffffff813978fe <xsave_cntxt_init+85>: mov %rsi,0x4357ab(%rip) # 0xffffffff817cd0b0 <pcntxt_mask> 0xffffffff81397905 <xsave_cntxt_init+92>: and $0x3,%eax 0xffffffff81397908 <xsave_cntxt_init+95>: cmp $0x3,%rax 0xffffffff8139790c <xsave_cntxt_init+99>: je 0xffffffff81397920 <xsave_cntxt_init+119> 0xffffffff8139790e <xsave_cntxt_init+101>: mov $0xffffffff814ca823,%rdi 0xffffffff81397915 <xsave_cntxt_init+108>: xor %eax,%eax 0xffffffff81397917 <xsave_cntxt_init+110>: callq 0xffffffff813a95be <printk> 0xffffffff8139791c <xsave_cntxt_init+115>: ud2a 0xffffffff8139791e <xsave_cntxt_init+117>: jmp 0xffffffff8139791e <xsave_cntxt_init+117> ---Type <return> to continue, or q <return> to quit--- 0xffffffff81397920 <xsave_cntxt_init+119>: testb $0x4,0x26a700(%rip) # 0xffffffff81602027 <boot_cpu_data+39> 0xffffffff81397927 <xsave_cntxt_init+126>: movq $0x3,0x43577e(%rip) # 0xffffffff817cd0b0 <pcntxt_mask> 0xffffffff81397932 <xsave_cntxt_init+137>: je 0xffffffff81397966 <xsave_cntxt_init+189> 0xffffffff81397934 <xsave_cntxt_init+139>: orq $0x40000,0x423721(%rip) # 0xffffffff817bb060 <mmu_cr4_features> 0xffffffff8139793f <xsave_cntxt_init+150>: callq *0x1f23ab(%rip) # 0xffffffff81589cf0 <pv_cpu_ops+48> 0xffffffff81397945 <xsave_cntxt_init+156>: mov %eax,%edi 0xffffffff81397947 <xsave_cntxt_init+158>: or $0x40000,%edi 0xffffffff8139794d <xsave_cntxt_init+164>: callq *0x1f23a5(%rip) # 0xffffffff81589cf8 <pv_cpu_ops+56> 0xffffffff81397953 <xsave_cntxt_init+170>: mov 0x435756(%rip),%rax # 0xffffffff817cd0b0 <pcntxt_mask> 0xffffffff8139795a <xsave_cntxt_init+177>: xor %ecx,%ecx 0xffffffff8139795c <xsave_cntxt_init+179>: mov %rax,%rdx 0xffffffff8139795f <xsave_cntxt_init+182>: shr $0x20,%rdx 0xffffffff81397963 <xsave_cntxt_init+186>: xsetbv 0xffffffff81397966 <xsave_cntxt_init+189>: movl $0xd,-0x24(%rbp) 0xffffffff8139796d <xsave_cntxt_init+196>: movl $0x0,-0x2c(%rbp) 0xffffffff81397974 <xsave_cntxt_init+203>: mov %rbx,%rdi 0xffffffff81397977 <xsave_cntxt_init+206>: mov %r12,%rsi 0xffffffff8139797a <xsave_cntxt_init+209>: mov %r13,%rdx 0xffffffff8139797d <xsave_cntxt_init+212>: mov %r14,%rcx 0xffffffff81397980 <xsave_cntxt_init+215>: callq *0x1f241a(%rip) # 0xffffffff81589da0 <pv_cpu_ops+224> 0xffffffff81397986 <xsave_cntxt_init+221>: mov $0xffffffff817cd0c0,%rsi 0xffffffff8139798d <xsave_cntxt_init+228>: xor %eax,%eax 0xffffffff8139798f <xsave_cntxt_init+230>: mov $0xc,%ecx 0xffffffff81397994 <xsave_cntxt_init+235>: mov %rsi,%rdi 0xffffffff81397997 <xsave_cntxt_init+238>: mov -0x28(%rbp),%ebx 0xffffffff8139799a <xsave_cntxt_init+241>: rep stos %eax,%es:(%rdi) 0xffffffff8139799c <xsave_cntxt_init+243>: mov 0x43570d(%rip),%rax # 0xffffffff817cd0b0 <pcntxt_mask> (gdb) -- Pasi

2 7

[Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released
by Pasi Kärkkäinen 21 Sep '09

21 Sep '09

----- Forwarded message from Keir Fraser <keir.fraser(a)eu.citrix.com> ----- From: Keir Fraser <keir.fraser(a)eu.citrix.com> To: "xen-devel(a)lists.xensource.com" <xen-devel(a)lists.xensource.com>, xen-users(a)lists.xensource.com Cc: Date: Thu, 06 Aug 2009 23:35:08 +0100 Subject: [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released Folks, New releases in the 3.3 and 3.4 stable branches are now tagged and released. You can pick up the source repositories here: http://xenbits.xensource.com/xen-3.3-testing.hg (tagged RELEASE-3.3.2) http://xenbits.xensource.com/xen-3.4-testing.hg (tagged RELEASE-3.4.1) Or you can pick up tarballs from the following webpages: 3.3.2: http://www.xen.org/download/index_3.3.2.html 3.4.1: http://www.xen.org/download/ -- Keir _______________________________________________ Xen-devel mailing list Xen-devel(a)lists.xensource.com http://lists.xensource.com/xen-devel ----- End forwarded message -----

4 29

Xen 3.4.1 dom0 crash on boot
by Charles J Gruener 21 Sep '09

21 Sep '09

I have an ASRock X58 SuperComputer motherboard that refuses to boot the latest xen-3.4.1 in Rawhide. This is the motherboard: http://www.asrock.com/mb/overview.asp?Model=X58%20SuperComputer Here is a capture of the boot process: (XEN) Bad console= option 'tty' __ __ _____ _ _ _ _____ __ _ ____ \ \/ /___ _ __ |___ /| || | / | |___ / / _| ___/ |___ \ \ // _ \ '_ \ |_ \| || |_ | |__ |_ \ | |_ / __| | __) | / \ __/ | | | ___) |__ _|| |__|__) || _| (__| |/ __/ /_/\_\___|_| |_| |____(_) |_|(_)_| |____(_)_| \___|_|_____| (XEN) Xen version 3.4.1 (mockbuild@(none)) (gcc version 4.4.1 20090818 (Red Hat 4.4.1-6) (GCC) ) Wed Sep 2 08:03:46 EDT 2009 (XEN) Latest ChangeSet: unavailable (XEN) Command line: console=com1,tty com1=115200,8n1 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds (XEN) EDID info not retrieved because no DDC retrieval method detected (XEN) Disc information: (XEN) Found 0 MBR signatures (XEN) Found 2 EDD information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - 0000000000096800 (usable) (XEN) 0000000000096800 - 00000000000a0000 (reserved) (XEN) 00000000000e4000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 00000000bfe90000 (usable) (XEN) 00000000bfe90000 - 00000000bfea0000 (ACPI data) (XEN) 00000000bfea0000 - 00000000bfed0000 (ACPI NVS) (XEN) 00000000bfed0000 - 00000000bfee0000 (reserved) (XEN) 00000000bfeeb800 - 00000000c0000000 (reserved) (XEN) 00000000fee00000 - 00000000fee01000 (reserved) (XEN) 00000000ffb00000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 00000001c0000000 (usable) (XEN) System RAM: 6142MB (6289560kB) (XEN) ACPI: RSDP 000FA2B0, 0014 (r0 ACPIAM) (XEN) ACPI: RSDT BFE90000, 0040 (r1 083109 RSDT2145 20090831 MSFT 97) (XEN) ACPI: FACP BFE90200, 0084 (r1 A_M_I OEMFACP 12000601 MSFT 97) (XEN) ACPI: DSDT BFE90480, 6425 (r1 AS196 AS196246 246 INTL 20051117) (XEN) ACPI: FACS BFEA0000, 0040 (XEN) ACPI: APIC BFE90390, 00AC (r1 083109 APIC2145 20090831 MSFT 97) (XEN) ACPI: MCFG BFE90440, 003C (r1 083109 OEMMCFG 20090831 MSFT 97) (XEN) ACPI: OEMB BFEA0040, 0073 (r1 083109 OEMB2145 20090831 MSFT 97) (XEN) ACPI: AAFT BFE9A480, 0027 (r1 083109 OEMAAFT 20090831 MSFT 97) (XEN) ACPI: DMAR BFEA00C0, 0128 (r1 AMI OEMDMAR 1 MSFT 97) (XEN) ACPI: SSDT BFEA1BF0, 0363 (r1 DpgPmm CpuPm 12 INTL 20051117) (XEN) Domain heap initialised (XEN) Processor #0 7:10 APIC version 21 (XEN) Processor #2 7:10 APIC version 21 (XEN) Processor #4 7:10 APIC version 21 (XEN) Processor #6 7:10 APIC version 21 (XEN) Processor #1 7:10 APIC version 21 (XEN) Processor #3 7:10 APIC version 21 (XEN) Processor #5 7:10 APIC version 21 (XEN) Processor #7 7:10 APIC version 21 (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 2666.826 MHz processor. (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) VMX: EPT is available. (XEN) VMX: VPID is available. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging detected. (XEN) CPU0: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 (XEN) Booting processor 1/2 eip 8c000 (XEN) CPU1: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 (XEN) Booting processor 2/4 eip 8c000 (XEN) CPU2: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 (XEN) Booting processor 3/6 eip 8c000 (XEN) CPU3: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 (XEN) Booting processor 4/1 eip 8c000 (XEN) CPU4: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 (XEN) Booting processor 5/3 eip 8c000 (XEN) CPU5: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 (XEN) Booting processor 6/5 eip 8c000 (XEN) CPU6: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 (XEN) Booting processor 7/7 eip 8c000 (XEN) CPU7: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 (XEN) Total of 8 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) checking TSC synchronization across 8 CPUs: passed. (XEN) Platform timer is 3.579MHz ACPI PM Timer (XEN) Brought up 8 CPUs (XEN) I/O virtualisation disabled (XEN) CPUIDLE: disabled due to no HPET. Force enable with 'cpuidle'. (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2695000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 00000001b4000000->00000001b8000000 (1502490 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff81000000->ffffffff82695000 (XEN) Init. ramdisk: ffffffff82695000->ffffffff83006a00 (XEN) Phys-Mach map: ffffffff83007000->ffffffff83b9d8d0 (XEN) Start info: ffffffff83b9e000->ffffffff83b9e4b4 (XEN) Page tables: ffffffff83b9f000->ffffffff83bc2000 (XEN) Boot stack: ffffffff83bc2000->ffffffff83bc3000 (XEN) TOTAL: ffffffff80000000->ffffffff84000000 (XEN) ENTRY ADDRESS: ffffffff819fd820 (XEN) Dom0 has maximum 8 VCPUs (XEN) Scrubbing Free RAM: .done. (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: Errors and warnings (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen) (XEN) Freed 128kB init memory. (XEN) mm.c:1697:d0 Bad L1 flags 800000 (XEN) traps.c:437:d0 Unhandled invalid opcode fault/trap [#6] on VCPU 0 [ec=0000] (XEN) domain_crash_sync called from entry.S (XEN) Domain 0 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-3.4.1 x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e033:[<ffffffff81a017f1>] (XEN) RFLAGS: 0000000000000282 EM: 1 CONTEXT: pv guest (XEN) rax: 00000000ffffffea rbx: ffffffff8182b000 rcx: 00000000001b582b (XEN) rdx: 0000000000000000 rsi: 80000001b582b061 rdi: ffffffff8182b000 (XEN) rbp: ffffffff8174ff98 rsp: ffffffff8174fef8 r8: 0000000000000000 (XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000 (XEN) r12: ffffffff8174ffa8 r13: ffffffff8174ff40 r14: 0000000000000080 (XEN) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000026f0 (XEN) cr3: 00000001b7b9f000 cr2: 0000000000000000 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 (XEN) Guest stack trace from rsp=ffffffff8174fef8: (XEN) 00000000001b582b 0000000000000000 ffffffff81a017f1 000000010000e030 (XEN) 0000000000010082 ffffffff8174ff38 000000000000e02b ffffffff81a017ed (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 000000000000182b 0000008000000000 ffffffff8100cc87 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) ffffffff8174ffc8 ffffffff81021271 ffff8182b000007f 000000000000ffff (XEN) 0000000000000000 0000000000000000 ffffffff8174fff8 ffffffff81a01b49 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 (XEN) Domain 0 crashed: rebooting machine in 5 seconds. I've done some searches on the mailing list and on the web, but nothing seems to be helping me. Any assistance would be greatly appreciated. Charles

5 19

[Xen-devel] Announcing xen/master: pvops git trees rearranged
by Pasi Kärkkäinen 21 Sep '09

21 Sep '09

----- Forwarded message from Jeremy Fitzhardinge <jeremy(a)goop.org> ----- From: Jeremy Fitzhardinge <jeremy(a)goop.org> To: Xen-devel <xen-devel(a)lists.xensource.com> Date: Fri, 18 Sep 2009 18:19:41 -0700 Subject: [Xen-devel] Announcing xen/master: pvops git trees rearranged Well, my current pvops/dom0 tree is finally (reasonably) stable. There was a fairly nasty bug which ended up corrupting dom0 memory when doing IO on behalf of domains, but that is finally fixed. In honour of this, I've renamed the rebase/* branches to xen/* (moving the old remaining xen/* branches to xen-old/*); xen/master is now the preferred branch for fetching current dom0 work. The kernel tree is fairly featureful: * basic dom0 support * blkback * netback * ACPI power management * S3 suspend/resume (at least for some people) * microcode update * MSI support In other words, it has as much as it ever has. There are a few notable missing features: * blktap2 * netchannel2 * pci front/back * upstream Linux support * your pet feature Full coordinates are: git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git xen/master See http://wiki.xensource.com/xenwiki/XenParavirtOps for general directions on configuration, compilation and use. This is definitely a work-in-progress kernel. I'd appreciate all bug *and* success reports so I can get some idea of how many people are using this thing, and how often there are problems. Patches gratefully accepted. Thanks, J _______________________________________________ Xen-devel mailing list Xen-devel(a)lists.xensource.com http://lists.xensource.com/xen-devel ----- End forwarded message -----

1 0

Re: [Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released / 3.4.1-3 rpm available from koji / F12 problem with pygrub
by Boris Derzhavets 13 Sep '09

13 Sep '09

>However, If I do 'rpmbuild --bb xen.spec' for xen-3.4.1-3.fc12.src.rpm and > install the rebuilt rpms, pygrub works just fine! Sorry, you have noticed it already B. --- On Sun, 9/13/09, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote: From: Boris Derzhavets <bderzhavets(a)yahoo.com> Subject: Re: [Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released / 3.4.1-3 rpm available from koji / F12 problem with pygrub To: "Gerd Hoffmann" <kraxel(a)redhat.com>, "Pasi Kärkkäinen" <pasik(a)iki.fi> Cc: fedora-xen(a)redhat.com Date: Sunday, September 13, 2009, 1:01 PM >Anyway, it seems the F12/rawhide xen-3.4.1-3 rpms contain pygrub that >doesn't support ext4. Please, view :- http://www.fsdaily.com/HighEnd/Setup_Xen_3_4_1_Libvirt_on_top_F12_Alpha_raw… It's on 64-bit. Boris. --- On Sun, 9/13/09, Pasi Kärkkäinen <pasik(a)iki.fi> wrote: From: Pasi Kärkkäinen <pasik(a)iki.fi> Subject: Re: [Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released / 3.4.1-3 rpm available from koji / F12 problem with pygrub To: "Gerd Hoffmann" <kraxel(a)redhat.com> Cc: fedora-xen(a)redhat.com Date: Sunday, September 13, 2009, 12:16 PM On Wed, Sep 02, 2009 at 04:08:32PM +0300, Pasi Kärkkäinen wrote: > On Wed, Sep 02, 2009 at 03:59:31PM +0300, Pasi Kärkkäinen wrote: > > On Wed, Sep 02, 2009 at 03:41:09PM +0300, Pasi Kärkkäinen wrote: > > > On Wed, Sep 02, 2009 at 02:25:59PM +0200, Gerd Hoffmann wrote: > > > > Hi, > > > > > > > > >>Still no stubdom/pvgrub bzip2/lzma support though. I'll look more into > > > > >>it tonight. > > > > > > > > > >.. but don't wait for the final patch, since I don't know yet how long > > > > >it takes to get the stubdom/pvgrub stuff sorted out. > > > > > > > > Bits committed, koji builds done. > > > > > > > > > > Great, thanks! > > > > > > Does 3.4.1-3 end up in F12 automatically? > > > > > > > btw the url is this: > > http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/3.fc12/ > > > > Changelog: > > > > * Wed Sep 02 2009 Gerd Hoffmann <kraxel(a)redhat.com> - 3.4.1-3 > > - swap bzip2+xz linux kernel compression support patches. > > - backport one more bugfix (videoram option). > > > > * Tue Sep 01 2009 Gerd Hoffmann <kraxel(a)redhat.com> - 3.4.1-2 > > - backport bzip2+xz linux kernel compression support. > > - backport a few bugfixes. > > > > btw 3.4.1-2 and 3.4.1-3 do contain the fix for pygrub timeout=0 > handling, so F11 PV domUs/guests will work out-of-the-box. > Hello, I just noticed something weird.. I upgraded my host to F12/rawhide, so now I'm running everything straight from rawhide, except my custom pv_ops dom0 kernel. Anyway, it seems the F12/rawhide xen-3.4.1-3 rpms contain pygrub that doesn't support ext4. # /usr/bin/pygrub --output=/tmp/debug /dev/vg_dom0test/test3vm Traceback (most recent call last): File "/usr/bin/pygrub", line 680, in <module> chosencfg = run_grub(file, entry, fs, incfg["args"]) File "/usr/bin/pygrub", line 515, in run_grub g = Grub(file, fs) File "/usr/bin/pygrub", line 202, in __init__ self.read_config(file, fs) File "/usr/bin/pygrub", line 397, in read_config raise RuntimeError, "couldn't find bootloader config file in the image provided." RuntimeError: couldn't find bootloader config file in the image provided. However, If I do 'rpmbuild --bb xen.spec' for xen-3.4.1-3.fc12.src.rpm and install the rebuilt rpms, pygrub works just fine! So is there some lib missing from the build requirements or? Any ideas? -- Pasi -- Fedora-xen mailing list Fedora-xen(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen

1 0

Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
by Boris Derzhavets 09 Sep '09

09 Sep '09

I was able to get login prompt ( commit 7c62209cde5b13b81685e79b2f9e3757e293aef1 ) first time via serial console:- title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) root (hd1,0) kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1 module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=hvc0 earlyprintk=xen module /initrd-2.6.31-rc8.img Then disconnected NUL modem cable and loaded Dom0 via : title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1) root (hd1,0) kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1 module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen module /initrd-2.6.31-rc8.img Usual Grub entry drops console to stack trace. Dmesg output is attached. Boris. --- On Tue, 9/8/09, Mark Schloesser <mark.schloesser(a)rwth-aachen.de> wrote: From: Mark Schloesser <mark.schloesser(a)rwth-aachen.de> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Boris Derzhavets" <bderzhavets(a)yahoo.com> Cc: fedora-xen(a)redhat.com Date: Tuesday, September 8, 2009, 8:13 AM Top commit in my checkout is: commit 3b316bf67dcbe550e648703475e811fc0cedc705 Merge: 226206a 27a3a52 Author: Jeremy Fitzhardinge <jeremy.fitzhardinge(a)citrix.com> Date: Thu Sep 3 16:25:12 2009 -0700 Mark Boris Derzhavets wrote: > Yep ;) > > Please, run > # git log|more > in linux-2.6-xen ( obtained via git clone). > I am wondering what was the top commit for good build 2.6.31-rc8 > I am trying to bisect. > > Boris. > > > --- On Sun, 9/6/09, Mark Schloesser <mark.schloesser(a)rwth-aachen.de> wrote: > > From: Mark Schloesser <mark.schloesser(a)rwth-aachen.de> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" <bderzhavets(a)yahoo.com> > Cc: xen-devel(a)lists.xensource.com, fedora-xen(a)redhat.com > Date: Sunday, September 6, 2009, 12:17 PM > > I am on standard F11, using a fresh install and then updated all > packages before doing anything xen related. Xen build was done with > current xen-unstable checkout using only "xen" and "tools" build > targets. I have no libvirt or libvirt-preview currently. My Xorg still > does not want to come up btw :) > > Do you need anything else? > > Mark > > > > > > >

4 15

Re: [Xen-devel] Dmesg log for 2.6.31-rc8 kernel been built on F12 (rawhide) vs log for same kernel been built on F11 and installed on F12
by Boris Derzhavets 09 Sep '09

09 Sep '09

>I am not sure if I understand you correctly. Are you saying that 2.6.31-rc8 >boots without the stack-trace failure? Can you attach the dmesg please >and also 'lspci -vvv' output? If i built rc8 on F11 ( dual booting) with F12 and install kernel and modules via # mount /dev/mapper/serverfedora11-lv_root /mnt #cd /mnt/usr/src/linux-2.6-xen # make modules_install install in F12 env, then i get a stable kernel rc8 on F12. If i compile and and install on F12 kernel has stack trace and is pretty unstable at runtime. Now i am sending two dmesg reports :- 1. Kernel 2.6.31-rc8 been built on F11 and installed on F12 dmesg.log.gz (clean) 2. Kernel 2.6.31-rc8 been built on F12 and installed on F12 dmesg.1.gz ( stack trace here) "lspci -vvv" report has been also sent to you per your request, but i will repeat. This one is for C2D E8400 box. Boris. --- On Wed, 9/9/09, Konrad Rzeszutek Wilk <konrad.wilk(a)oracle.com> wrote: From: Konrad Rzeszutek Wilk <konrad.wilk(a)oracle.com> Subject: Re: [Xen-devel] Dmesg log for 2.6.31-rc8 kernel been built on F12 (rawhide) vs log for same kernel been built on F11 and installed on F12 To: "Boris Derzhavets" <bderzhavets(a)yahoo.com> Cc: "Jeremy Fitzhardinge" <jeremy(a)goop.org>, xen-devel(a)lists.xensource.com, fedora-xen(a)redhat.com Date: Wednesday, September 9, 2009, 10:10 AM On Wed, Sep 09, 2009 at 12:19:20AM -0700, Boris Derzhavets wrote: > Previous 2.6.31-rc8 kernel was built on F11 and installed with modules on F12. > Current kernel has been built on F12 (2.6.31-0.204.rc9.fc12.x86_64) and installed > on F12 before loading under Xen 3.4.1. > Dmesg log looks similar to Michael Yuong's 'rc7.git4' kernel for F12. I am not sure if I understand you correctly. Are you saying that 2.6.31-rc8 boots without the stack-trace failure? Can you attach the dmesg please and also 'lspci -vvv' output? > > Boris. > > --- On Tue, 9/8/09, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote: > > From: Boris Derzhavets <bderzhavets(a)yahoo.com> > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem > To: "Pasi Kärkkäinen" <pasik(a)iki.fi>, "Konrad Rzeszutek Wilk" <konrad..wilk(a)oracle.com> > Cc: "Jeremy Fitzhardinge" <jeremy(a)goop.org>, xen-devel(a)lists.xensource.com, fedora-xen(a)redhat.com > Date: Tuesday, September 8, 2009, 3:45 PM > > Dmesg log for rc8 under Xen 3.4.1 on F12 rawhide attached. I took a look at the dmesg and it looks fine. I did not see a stack trace in it? Maybe I was looking at the wrong one. This is the identifying timestamp at the beginning: Linux version 2.6.31-rc8 (root@ServerXen35) (gcc version 4.4.1 20090725 (Red Hat 4.4.1-2) (GCC) ) #3 SMP Tue Sep 8 04:24:43 EDT 2009 is that the right dmesg? *************************************************** Yes , this one is fine. Kernel had been built on F11 and installed on F12 *************************************************** _______________________________________________ Xen-devel mailing list Xen-devel(a)lists.xensource.com http://lists.xensource.com/xen-devel

2 1

Dmesg log for 2.6.31-rc8 kernel been built on F12 (rawhide) vs log for same kernel been built on F11 and installed on F12
by Boris Derzhavets 09 Sep '09

09 Sep '09

Previous 2.6.31-rc8 kernel was built on F11 and installed with modules on F12. Current kernel has been built on F12 (2.6.31-0.204.rc9.fc12.x86_64) and installed on F12 before loading under Xen 3.4.1. Dmesg log looks similar to Michael Yuong's 'rc7.git4' kernel for F12. Boris. --- On Tue, 9/8/09, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote: From: Boris Derzhavets <bderzhavets(a)yahoo.com> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem To: "Pasi Kärkkäinen" <pasik(a)iki.fi>, "Konrad Rzeszutek Wilk" <konrad.wilk(a)oracle.com> Cc: "Jeremy Fitzhardinge" <jeremy(a)goop.org>, xen-devel(a)lists.xensource.com, fedora-xen(a)redhat.com Date: Tuesday, September 8, 2009, 3:45 PM Dmesg log for rc8 under Xen 3.4.1 on F12 rawhide attached. Boris. --- On Tue, 9/8/09, Konrad Rzeszutek Wilk <konrad.wilk(a)oracle.com> wrote: From: Konrad Rzeszutek Wilk <konrad.wilk(a)oracle.com> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem To: "Pasi Kärkkäinen" <pasik(a)iki.fi> Cc: "Boris Derzhavets" <bderzhavets(a)yahoo.com>, xen-devel(a)lists.xensource.com, "Jeremy Fitzhardinge" <jeremy(a)goop.org>, fedora-xen(a)redhat.com Date: Tuesday, September 8, 2009, 3:34 PM On Tue, Sep 08, 2009 at 10:22:46PM +0300, Pasi Kärkkäinen wrote: > On Tue, Sep 08, 2009 at 12:14:54PM -0700, Boris Derzhavets wrote: > > Console drops into the same stack trace in both cases. > > > > Jeremy: Any ideas could some recent change in pv_ops dom0 kernel cause > usb stuff to stop working with >4096M of dom0 memory? The last set of changes in Jeremy's kernel are a set of patches I sent, so the problem is most likely caused by my work. A dmesg from both Xen and Linux kernel would be most helpfull. Also a lspci -vvv would be nice. And as Pasi suggested, booting the same kernel without Xen would be most helpful. > > dom0_mem=4096M works > dom0_mem=4097M fails with stacktrace > > Boris: What was the last kernel that worked without backtraces? > Also, does that same kernel work as baremetal (without Xen) ? _______________________________________________ Xen-devel mailing list Xen-devel(a)lists.xensource.com http://lists.xensource.com/xen-devel -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen

2 1

Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem
by Boris Derzhavets 08 Sep '09

08 Sep '09

> lspci -vvv would be nice. Attached Boris. --- On Tue, 9/8/09, Konrad Rzeszutek Wilk <konrad.wilk(a)oracle.com> wrote: From: Konrad Rzeszutek Wilk <konrad.wilk(a)oracle.com> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem To: "Pasi Kärkkäinen" <pasik(a)iki.fi> Cc: "Boris Derzhavets" <bderzhavets(a)yahoo.com>, "Jeremy Fitzhardinge" <jeremy(a)goop.org>, xen-devel(a)lists.xensource.com, fedora-xen(a)redhat.com Date: Tuesday, September 8, 2009, 3:34 PM On Tue, Sep 08, 2009 at 10:22:46PM +0300, Pasi Kärkkäinen wrote: > On Tue, Sep 08, 2009 at 12:14:54PM -0700, Boris Derzhavets wrote: > > Console drops into the same stack trace in both cases. > > > > Jeremy: Any ideas could some recent change in pv_ops dom0 kernel cause > usb stuff to stop working with >4096M of dom0 memory? The last set of changes in Jeremy's kernel are a set of patches I sent, so the problem is most likely caused by my work. A dmesg from both Xen and Linux kernel would be most helpfull. Also a lspci -vvv would be nice. And as Pasi suggested, booting the same kernel without Xen would be most helpful. > > dom0_mem=4096M works > dom0_mem=4097M fails with stacktrace > > Boris: What was the last kernel that worked without backtraces? > Also, does that same kernel work as baremetal (without Xen) ?

1 0

Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem
by Boris Derzhavets 08 Sep '09

08 Sep '09

Dmesg log for rc8 under Xen 3.4.1 on F12 rawhide attached. Boris. --- On Tue, 9/8/09, Konrad Rzeszutek Wilk <konrad.wilk(a)oracle.com> wrote: From: Konrad Rzeszutek Wilk <konrad.wilk(a)oracle.com> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem To: "Pasi Kärkkäinen" <pasik(a)iki.fi> Cc: "Boris Derzhavets" <bderzhavets(a)yahoo.com>, xen-devel(a)lists.xensource.com, "Jeremy Fitzhardinge" <jeremy(a)goop.org>, fedora-xen(a)redhat.com Date: Tuesday, September 8, 2009, 3:34 PM On Tue, Sep 08, 2009 at 10:22:46PM +0300, Pasi Kärkkäinen wrote: > On Tue, Sep 08, 2009 at 12:14:54PM -0700, Boris Derzhavets wrote: > > Console drops into the same stack trace in both cases. > > > > Jeremy: Any ideas could some recent change in pv_ops dom0 kernel cause > usb stuff to stop working with >4096M of dom0 memory? The last set of changes in Jeremy's kernel are a set of patches I sent, so the problem is most likely caused by my work. A dmesg from both Xen and Linux kernel would be most helpfull. Also a lspci -vvv would be nice. And as Pasi suggested, booting the same kernel without Xen would be most helpful. > > dom0_mem=4096M works > dom0_mem=4097M fails with stacktrace > > Boris: What was the last kernel that worked without backtraces? > Also, does that same kernel work as baremetal (without Xen) ? _______________________________________________ Xen-devel mailing list Xen-devel(a)lists.xensource.com http://lists.xensource.com/xen-devel

1 0

Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
by Mark Schloesser 08 Sep '09

08 Sep '09

Hey guys, I sadly had no luck fixing my X problem. The system seems to run fine and as the subject says I moved from 3.4.1-3 to xen-unstable. As I am already doing fairly bleeding-edge stuff here I thought this would probably make most sense. As I only have an nvs290 gfx card available right now I can't check if this is the problem. But I'll try to get my hands on some other cards for next week. Today I read through a lot of mailing list archives and PDFs trying to dig deeper into the IOMMU/PCI passthrough stuff and I want to give the graphics passthrough situation a shot myself. Sadly it is very confusing to read about the different setups and hardware environments with both positive and negative results. Also the patchsets and versions everybody is talking about do not make it any easier :) My current questions would be: - is the combination of JF git kernel with xen-unstable the right way to go for this setup? Or should I perhaps use older xen version and apply some patchset? I think some of those patches were applied in xen-unstable already but I am not quite sure... - does anyone have hints or clarification regarding the Xorg problem on dom0? As I said there are no eye-catching log entries or errors except the Xorg backtrace at the end of the log file (posted to list before). This happens regardless of which driver I enable (vesa/nv/nouveau). The nvidia binary driver compiles without problems and seems to come up but only gives me a black screen and also locks the vtys. Thanks to the great help, reports and instructions Boris and others! Mark

4 12

Re: [Xen-devel] Re: Errors when build 2.6.31-rc8
by Boris Derzhavets 07 Sep '09

07 Sep '09

Attempt to load 2.6-31-rc8 under Xen 3.4.1 , installed via xen-3.4.1-3.src.rpm along with libvirt(rawhide) , on top F12 rawhide. yum update gcc,glibc,kernel had been run. Call trace: usb_hc_died + ..... usb_add_hcd +..... usb_hcd_pci_probe + .... do_work_for_cpu + ..... local_pci_probe + ... do_work_for_cpu +.... kthread +..... child_rip+.... restore_args + ..... child_rip + ..... Code : . . . . .. . . . RIP [<ffff...c7>] usb_kick_khubd + 0x10/0x25 RSP < ffff ... e0> CR2: 00000...098 ---[ end trace 8219......]---- uhci_hcd 0000:00:1a:0 host controller process error, something bad happened ! uhci_hcd 0000:00:1a:0 host controller halted , very bad uhci_hcd 0000:00:1a:0 HC died, cleaning up 2.6.31-rc6 loads fine in same environment under Xen 3.4.1 on top of F12 rawhide Boris, --- On Sat, 9/5/09, Jeremy Fitzhardinge <jeremy(a)goop.org> wrote: From: Jeremy Fitzhardinge <jeremy(a)goop.org> Subject: [Xen-devel] Re: Errors when build 2.6.31-rc8 To: "Boris Derzhavets" <bderzhavets(a)yahoo.com> Cc: "Xen-devel" <xen-devel(a)lists.xensource.com> Date: Saturday, September 5, 2009, 11:48 AM On 09/05/09 04:18, Boris Derzhavets wrote: > After fresh git clone, git checkout tune "make menuconfig" the same > way as for RC6 > > When build :- > > In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:5, > from drivers/gpu/drm/ttm/ttm_agp_backend.c:40: > include/linux/swiotlb.h:48: warning: ‘enum dma_data_direction’ > declared inside parameter list > include/linux/swiotlb.h:48: warning: its scope is only this definition > or declaration, which is probably not what you want > include/linux/swiotlb.h:51: warning: ‘enum dma_data_direction’ > declared inside parameter list > include/linux/swiotlb.h:63: warning: ‘enum dma_data_direction’ > declared inside parameter list > include/linux/swiotlb.h:68: warning: ‘enum dma_data_direction’ > declared inside parameter list > include/linux/swiotlb.h:72: warning: ‘enum dma_data_direction’ > declared inside parameter list > include/linux/swiotlb.h:76: warning: ‘enum dma_data_direction’ > declared inside parameter list > include/linux/swiotlb.h:80: warning: ‘enum dma_data_direction’ > declared inside parameter list > include/linux/swiotlb.h:84: warning: ‘enum dma_data_direction’ > declared inside parameter list > include/linux/swiotlb.h:89: warning: ‘enum dma_data_direction’ > declared inside parameter list > include/linux/swiotlb.h:94: warning: ‘enum dma_data_direction’ > declared inside parameter list > In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:9, > from drivers/gpu/drm/ttm/ttm_agp_backend.c:40: > /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function > ‘get_dma_ops’: > /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:29: error: > dereferencing pointer to incomplete type > /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:32: error: > dereferencing pointer to incomplete type > In file included from > /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:37, > from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:9, > from drivers/gpu/drm/ttm/ttm_agp_backend.c:40: > include/asm-generic/dma-mapping-common.h: At top level: > include/asm-generic/dma-mapping-common.h:12: warning: ‘enum > dma_data_direction’ declared inside parameter list > include/asm-generic/dma-mapping-common.h:11: error: parameter 4 > (‘dir’) has incomplete type > include/asm-generic/dma-mapping-common.h: In function > ‘dma_map_single_attrs’: > include/asm-generic/dma-mapping-common.h:18: error: implicit > declaration of function ‘valid_dma_direction’ > In file included from > /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:37, > from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:9, > from drivers/gpu/drm/ttm/ttm_agp_backend.c:40: > include/asm-generic/dma-mapping-common.h:19: error: dereferencing > pointer to incomplete type > include/asm-generic/dma-mapping-common.h: At top level: > include/asm-generic/dma-mapping-common.h:31: warning: ‘enum > dma_data_direction’ declared inside parameter list > include/asm-generic/dma-mapping-common.h:30: error: parameter 4 > (‘dir’) has incomplete type > include/asm-generic/dma-mapping-common.h: In function > ‘dma_unmap_single_attrs’: > include/asm-generic/dma-mapping-common.h:36: error: dereferencing > pointer to incomplete type > include/asm-generic/dma-mapping-common.h:37: error: dereferencing > pointer to incomplete type > include/asm-generic/dma-mapping-common.h: At top level: > include/asm-generic/dma-mapping-common.h:43: warning: ‘enum > dma_data_direction’ declared inside parameter list > include/asm-generic/dma-mapping-common.h:42: error: parameter 4 > (‘dir’) has incomplete type > include/asm-generic/dma-mapping-common.h: In function ‘dma_map_sg_attrs’: > include/asm-generic/dma-mapping-common.h:52: error: dereferencing > pointer to incomplete type > include/asm-generic/dma-mapping-common.h: At top level: > include/asm-generic/dma-mapping-common.h:60: warning: ‘enum > dma_data_direction’ declared inside parameter list > include/asm-generic/dma-mapping-common.h:59: error: parameter 4 > (‘dir’) has incomplete type > include/asm-generic/dma-mapping-common.h: In function > ‘dma_unmap_sg_attrs’: > include/asm-generic/dma-mapping-common.h:66: error: dereferencing > pointer to incomplete type > include/asm-generic/dma-mapping-common.h:67: error: dereferencing > pointer to incomplete type > include/asm-generic/dma-mapping-common.h: At top level: > include/asm-generic/dma-mapping-common.h:72: warning: ‘enum > dma_data_direction’ declared inside parameter list > include/asm-generic/dma-mapping-common.h:72: error: parameter 5 > (‘dir’) has incomplete type > include/asm-generic/dma-mapping-common.h: In function ‘dma_map_page’: > include/asm-generic/dma-mapping-common.h:79: error: dereferencing > pointer to incomplete type > include/asm-generic/dma-mapping-common.h: At top level: > include/asm-generic/dma-mapping-common.h:86: warning: ‘enum > dma_data_direction’ declared inside parameter list > include/asm-generic/dma-mapping-common.h:86: error: parameter 4 > (‘dir’) has incomplete type > include/asm-generic/dma-mapping-common.h: In function ‘dma_unmap_page’: > include/asm-generic/dma-mapping-common.h:91: error: dereferencing > pointer to incomplete type > include/asm-generic/dma-mapping-common.h:92: error: dereferencing > pointer to incomplete type > include/asm-generic/dma-mapping-common.h: At top level: > include/asm-generic/dma-mapping-common.h:98: warning: ‘enum > dma_data_direction’ declared inside parameter list > include/asm-generic/dma-mapping-common.h:98: error: parameter 4 > (‘dir’) has incomplete type > include/asm-generic/dma-mapping-common.h: In function > ‘dma_sync_single_for_cpu’: > include/asm-generic/dma-mapping-common.h:103: error: dereferencing > pointer to incomplete type > include/asm-generic/dma-mapping-common.h:104: error: dereferencing > pointer to incomplete type > include/asm-generic/dma-mapping-common.h: At top level: > include/asm-generic/dma-mapping-common.h:111: warning: ‘enum > dma_data_direction’ declared inside parameter list > include/asm-generic/dma-mapping-common.h:111: error: parameter 4 > (‘dir’) has incomplete type > include/asm-generic/dma-mapping-common.h: In function > ‘dma_sync_single_for_device’: > include/asm-generic/dma-mapping-common.h:116: error: dereferencing > pointer to incomplete type > include/asm-generic/dma-mapping-common.h:117: error: dereferencing > pointer to incomplete type > include/asm-generic/dma-mapping-common.h: At top level: > include/asm-generic/dma-mapping-common.h:126: warning: ‘enum > dma_data_direction’ declared inside parameter list > include/asm-generic/dma-mapping-common.h:126: error: parameter 5 > (‘dir’) has incomplete type > include/asm-generic/dma-mapping-common.h: In function > ‘dma_sync_single_range_for_cpu’: > include/asm-generic/dma-mapping-common.h:131: error: dereferencing > pointer to incomplete type > include/asm-generic/dma-mapping-common.h:132: error: dereferencing > pointer to incomplete type > include/asm-generic/dma-mapping-common.h:137: error: type of formal > parameter 4 is incomplete > include/asm-generic/dma-mapping-common.h: At top level: > include/asm-generic/dma-mapping-common.h:144: warning: ‘enum > dma_data_direction’ declared inside parameter list > include/asm-generic/dma-mapping-common.h:144: error: parameter 5 > (‘dir’) has incomplete type > include/asm-generic/dma-mapping-common.h: In function > ‘dma_sync_single_range_for_device’: > include/asm-generic/dma-mapping-common.h:149: error: dereferencing > pointer to incomplete type > include/asm-generic/dma-mapping-common.h:150: error: dereferencing > pointer to incomplete type > include/asm-generic/dma-mapping-common.h:155: error: type of formal > parameter 4 is incomplete > include/asm-generic/dma-mapping-common.h: At top level: > include/asm-generic/dma-mapping-common.h:160: warning: ‘enum > dma_data_direction’ declared inside parameter list > include/asm-generic/dma-mapping-common.h:160: error: parameter 4 > (‘dir’) has incomplete type > include/asm-generic/dma-mapping-common.h: In function > ‘dma_sync_sg_for_cpu’: > include/asm-generic/dma-mapping-common.h:165: error: dereferencing > pointer to incomplete type > include/asm-generic/dma-mapping-common.h:166: error: dereferencing > pointer to incomplete type > include/asm-generic/dma-mapping-common.h: At top level: > include/asm-generic/dma-mapping-common.h:173: warning: ‘enum > dma_data_direction’ declared inside parameter list > include/asm-generic/dma-mapping-common.h:173: error: parameter 4 > (‘dir’) has incomplete type > include/asm-generic/dma-mapping-common.h: In function > ‘dma_sync_sg_for_device’: > include/asm-generic/dma-mapping-common.h:178: error: dereferencing > pointer to incomplete type > include/asm-generic/dma-mapping-common.h:179: error: dereferencing > pointer to incomplete type > In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:9, > from drivers/gpu/drm/ttm/ttm_agp_backend.c:40: > /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function > ‘dma_mapping_error’: > /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:42: error: > dereferencing pointer to incomplete type > /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:43: error: > dereferencing pointer to incomplete type > /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: At top level: > /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:60: warning: > ‘enum dma_data_direction’ declared inside parameter list > /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:60: error: > parameter 4 (‘dir’) has incomplete type > /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function > ‘dma_alloc_coherent_mask’: > /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:77: error: > dereferencing pointer to incomplete type > /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:79: error: > implicit declaration of function ‘DMA_BIT_MASK’ > /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function > ‘dma_alloc_coherent’: > /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:114: error: > implicit declaration of function ‘is_device_dma_capable’ > /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:117: error: > dereferencing pointer to incomplete type > /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:120: error: > dereferencing pointer to incomplete type > In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:9, > from drivers/gpu/drm/ttm/ttm_agp_backend.c:40: > /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function > ‘dma_free_coherent’: > /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:138: error: > dereferencing pointer to incomplete type > /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:139: error: > dereferencing pointer to incomplete type > make[4]: *** [drivers/gpu/drm/ttm/ttm_agp_backend.o] Error 1 > make[3]: *** [drivers/gpu/drm/ttm] Error 2 > make[2]: *** [drivers/gpu/drm] Error 2 > make[1]: *** [drivers/gpu] Error 2 > make: *** [drivers] Error 2 > Does this help? diff --git a/include/linux/swiotlb.h b/include/linux/swiotlb.h index cb1a663..f4ebffb 100644 --- a/include/linux/swiotlb.h +++ b/include/linux/swiotlb.h @@ -2,6 +2,7 @@ #define __LINUX_SWIOTLB_H #include <linux/types.h> +#include <linux/dma-mapping.h> struct device; struct dma_attrs; J _______________________________________________ Xen-devel mailing list Xen-devel(a)lists.xensource.com http://lists.xensource.com/xen-devel

3 10

xen 3.4.1 + myoung x86_64 kernel
by Mark Schloesser 04 Sep '09

04 Sep '09

Hi, I was just trying to get this combination setup up and running. I am on Fedora 11 and mostly followed Boris Derzhavets' blog to get it done. Sadly the box complains that it can not connect to the hypervisor when starting libvirtd and also xend startup fails. libvirtd screen message: ERROR Internal error: Could not obtain handle on privileged command interface (13 = Permission denied) FATAL: Failed to open connection to hypervisor: Permission denied In the kernel log I saw this: ====================================================== [ INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected ] 2.6.31-0.1.2.60.rc7.git4.xendom0.fc12.x86_64 #1 ------------------------------------------------------ See dmesg at http://p.carnivore.it/MrGxdQ for more info. Thanks for any hints or clarification! Cheers, Mark

2 5

Cross-posting to fedora-virt
by Mark McLoughlin 03 Sep '09

03 Sep '09

Hey, I think the fedora-xen mailing list is serving well as a place for all you brave souls working on getting Xen pv_ops Dom0 into shape. However, I don't think there's much point in having the separate list if people cross-post everything to fedora-virt. So, thoughts on whether we should either: a) close down the fedora-xen list or b) stop cross-posting everything to fedora-virt ? Cheers, Mark.

4 3

Re: [Fedora-xen] xen 3.4.1 + myoung x86_64 kernel
by Boris Derzhavets 02 Sep '09

02 Sep '09

I didn't suggest to install Michael Young's kernel. You may build directly via J.F. Git Repo:- # yum install mercurial gitk # git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git linux-2.6-xen # cd *-xen # git checkout origin/rebase/master -b rebase/master # copy ../config-work .config # make # make modules_install install Pvops kernel 2.6.31-rc6 should be built and installed on system. Working .config is attached (x86_64). No need run "make menuconfig" However, i got it working with both kernel. Stack trace in dmesg output of fedora's kernel seems to be harmless. Clean install with right sequence of steps seems to be important. I was unable reinstall system once been built. Try to follow blog's steps one by one. Point of kernel build doesn't matter. Boris. --- On Wed, 9/2/09, Mark Schloesser <mark.schloesser(a)rwth-aachen.de> wrote: From: Mark Schloesser <mark.schloesser(a)rwth-aachen.de> Subject: [Fedora-xen] xen 3.4.1 + myoung x86_64 kernel To: fedora-xen(a)redhat.com Date: Wednesday, September 2, 2009, 5:55 PM Hi, I was just trying to get this combination setup up and running. I am on Fedora 11 and mostly followed Boris Derzhavets' blog to get it done. Sadly the box complains that it can not connect to the hypervisor when starting libvirtd and also xend startup fails. libvirtd screen message: ERROR Internal error: Could not obtain handle on privileged command interface (13 = Permission denied) FATAL: Failed to open connection to hypervisor: Permission denied In the kernel log I saw this: ====================================================== [ INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected ] 2.6.31-0.1.2.60.rc7.git4.xendom0.fc12.x86_64 #1 ------------------------------------------------------ See dmesg at http://p.carnivore.it/MrGxdQ for more info. Thanks for any hints or clarification! Cheers, Mark -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen

1 0

moderation
by Mark Schloesser 02 Sep '09

02 Sep '09

Can some list admin look for need-to-be-moderated mails? I sent a mail with dmesg log attached and it got stuck. Should I nopaste dmesg logs instead? Thanks, Mark

2 1

Setup Libvirt 0.7.0-6 & Xen 3.4.1 Dom0 on top of Fedora 11 (64-bit)
by Jon R. 31 Aug '09

31 Aug '09

Success. From an install off the DVD with all packages in the setup deselected. I have installed an HVM and a paravirt vm and both work. My only problem is that eth0 does not come up when I reboot and I have to do a dhclient eth0 to get an address or specify one myself. I have set the IP static in the /etc/sysconf/network-scripts/ifcfg-eth0 file but it still comes up without an address. Thanks Boris for all the help!! Jon [root@localhost xen]# lspci 00:00.0 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a1) 00:01.0 ISA bridge: nVidia Corporation MCP61 LPC Bridge (rev a2) 00:01.1 SMBus: nVidia Corporation MCP61 SMBus (rev a2) 00:01.2 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a2) 00:02.0 USB Controller: nVidia Corporation MCP61 USB Controller (rev a3) 00:02.1 USB Controller: nVidia Corporation MCP61 USB Controller (rev a3) 00:04.0 PCI bridge: nVidia Corporation MCP61 PCI bridge (rev a1) 00:06.0 IDE interface: nVidia Corporation MCP61 IDE (rev a2) 00:07.0 Bridge: nVidia Corporation MCP61 Ethernet (rev a2) 00:08.0 IDE interface: nVidia Corporation MCP61 SATA Controller (rev a2) 00:08.1 IDE interface: nVidia Corporation MCP61 SATA Controller (rev a2) 00:09.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2) 00:0b.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2) 00:0c.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2) 00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] HyperTransport Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Miscellaneous Control 00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Link Control 02:00.0 VGA compatible controller: nVidia Corporation GeForce 8500 GT (rev a1) cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 16 model : 2 model name : AMD Phenom(tm) 9500 Quad-Core Processor stepping : 2 cpu MHz : 140637.186 cache size : 512 KB fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu de tsc msr pae mce cx8 apic mtrr mca cmov clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid pni cx16 popcnt hypervisor lahf_lm cmp_legacy extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch bogomips : 4420.21 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate

2 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen September 2009