From jonr at destar.net Tue Sep 1 04:00:17 2009 From: jonr at destar.net (Jon) Date: Mon, 31 Aug 2009 20:00:17 -0800 Subject: [Fedora-xen] Setup Libvirt 0.7.0-6 & Xen 3.4.1 Dom0 on top of Fedora 11 (64-bit) Message-ID: <1251777617.2849.6.camel@laptop-jr.destar.net> 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 at 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 From jonr at destar.net Tue Sep 1 04:05:50 2009 From: jonr at destar.net (Jon) Date: Mon, 31 Aug 2009 20:05:50 -0800 Subject: [Fedora-xen] Setup Libvirt 0.7.0-6 & Xen 3.4.1 Dom0 on top of Fedora 11 (64-bit) In-Reply-To: <1251777617.2849.6.camel@laptop-jr.destar.net> References: <1251777617.2849.6.camel@laptop-jr.destar.net> Message-ID: <1251777950.2849.8.camel@laptop-jr.destar.net> These might also be nice to see. [root at localhost xen]# xm li Name ID Mem VCPUs State Time(s) Domain-0 0 4253 4 r----- 1609.8 Nevaeh 5 1024 1 -b---- 35.1 vm1-fc11-1 4 512 1 -b---- 29.1 [root at localhost xen]# xm info host : localhost.localdomain release : 2.6.31-rc6 version : #1 SMP Sun Aug 30 21:57:09 AKDT 2009 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2210 hw_caps : 178bf3ff:efd3fbff:00000000:00000310:00802001:00000000:000007ff:00000000 virt_caps : hvm total_memory : 5886 free_memory : 5 node_to_cpu : node0:0-3 node_to_memory : node0:5 xen_major : 3 xen_minor : 4 xen_extra : .1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.4.1 20090725 (Red Hat 4.4.1-2) (GCC) cc_compile_by : root cc_compile_domain : cc_compile_date : Sat Aug 29 15:56:57 AKDT 2009 xend_config_format : 4 On Mon, 2009-08-31 at 20:00 -0800, Jon wrote: > 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 at 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 > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From bderzhavets at yahoo.com Tue Sep 1 04:26:20 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Mon, 31 Aug 2009 21:26:20 -0700 (PDT) Subject: [Fedora-xen] Setup Libvirt 0.7.0-6 & Xen 3.4.1 Dom0 on top of Fedora 11 (64-bit) In-Reply-To: <1251777617.2849.6.camel@laptop-jr.destar.net> Message-ID: <494085.69337.qm@web56106.mail.re3.yahoo.com> Jon, I have just, one question :- Are you saying that HVM install succeeded via virt-manager ? I had to run virt-install to build HVM DomUs, virt-manager gave up at the beginning , complaining 2 different libvirt errors Boris. --- On Tue, 9/1/09, Jon wrote: From: Jon Subject: [Fedora-xen] Setup Libvirt 0.7.0-6 & Xen 3.4.1 Dom0 on top of Fedora 11 (64-bit) To: fedora-xen at redhat.com Date: Tuesday, September 1, 2009, 12:00 AM 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 at 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 -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonr at destar.net Tue Sep 1 04:31:33 2009 From: jonr at destar.net (Jon) Date: Mon, 31 Aug 2009 20:31:33 -0800 Subject: [Fedora-xen] Setup Libvirt 0.7.0-6 & Xen 3.4.1 Dom0 on top of Fedora 11 (64-bit) In-Reply-To: <494085.69337.qm@web56106.mail.re3.yahoo.com> References: <494085.69337.qm@web56106.mail.re3.yahoo.com> Message-ID: <1251779493.2849.10.camel@laptop-jr.destar.net> Boris, No, same problem as you have. Virt-manager will error out on libvirt errors. I had to use virt-install to install an HVM. Does the virt-manager just call virt-install with the correct parameters or is there something else going on? Jon On Mon, 2009-08-31 at 21:26 -0700, Boris Derzhavets wrote: > Jon, > > I have just, one question :- > Are you saying that HVM install succeeded via virt-manager ? > I had to run virt-install to build HVM DomUs, virt-manager gave up > at the beginning , complaining 2 different libvirt errors > > Boris. > > --- On Tue, 9/1/09, Jon wrote: > > From: Jon > Subject: [Fedora-xen] Setup Libvirt 0.7.0-6 & Xen 3.4.1 Dom0 > on top of Fedora 11 (64-bit) > To: fedora-xen at redhat.com > Date: Tuesday, September 1, 2009, 12:00 AM > > 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 at 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 > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > From bderzhavets at yahoo.com Tue Sep 1 04:44:15 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Mon, 31 Aug 2009 21:44:15 -0700 (PDT) Subject: [Fedora-xen] Setup Libvirt 0.7.0-6 & Xen 3.4.1 Dom0 on top of Fedora 11 (64-bit) In-Reply-To: <1251779493.2849.10.camel@laptop-jr.destar.net> Message-ID: <484796.97679.qm@web56104.mail.re3.yahoo.com> Jon, My knowledge of libvirt stuff is not good enough to answer you. View:- http://www.compatdb.org/support/topics/201770_fedora_weekly_news_190.html Quote:- Daniel Berrange reported[3] "FYI, I have just installed a Fedora 12 x86_64 guest on a Fedora 11 x86_64 KVM host". "Once installed, I installed the Xen dom0 kernel from http://fedorapeople.org/~myoung/dom0/ re-configured grub, and successfully rebooted into a Xen Dom0, and was able to create paravirt guests successfully. Most of the libvirt-TCK test suite passed, and the only bugs look trivial to solve in libvirt's Xen driver." Boris. --- On Tue, 9/1/09, Jon wrote: From: Jon Subject: Re: [Fedora-xen] Setup Libvirt 0.7.0-6 & Xen 3.4.1 Dom0 on top of Fedora 11 (64-bit) To: "Boris Derzhavets" Cc: fedora-xen at redhat.com, fedora-virt at redhat.com Date: Tuesday, September 1, 2009, 12:31 AM Boris, No, same problem as you have. Virt-manager will error out on libvirt errors. I had to use virt-install to install an HVM. Does the virt-manager just call virt-install with the correct parameters or is there something else going on? Jon On Mon, 2009-08-31 at 21:26 -0700, Boris Derzhavets wrote: > Jon, > > I have just, one question :- > Are you saying that HVM install succeeded via virt-manager ? > I had to run virt-install to build HVM DomUs, virt-manager gave up > at the beginning , complaining 2 different libvirt errors > > Boris. > > --- On Tue, 9/1/09, Jon wrote: >? ? ? ??? >? ? ? ???From: Jon >? ? ? ???Subject: [Fedora-xen] Setup Libvirt 0.7.0-6 & Xen 3.4..1 Dom0 >? ? ? ???on top of Fedora 11 (64-bit) >? ? ? ???To: fedora-xen at redhat.com >? ? ? ???Date: Tuesday, September 1, 2009, 12:00 AM >? ? ? ??? >? ? ? ???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 at 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 >? ? ? ??? >? ? ? ???-- >? ? ? ???Fedora-xen mailing list >? ? ? ???Fedora-xen at redhat.com >? ? ? ???https://www.redhat.com/mailman/listinfo/fedora-xen >? ? ? ??? > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kraxel at redhat.com Tue Sep 1 13:03:23 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Tue, 01 Sep 2009 15:03:23 +0200 Subject: [Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released / 3.4.1-2 patches In-Reply-To: <20090820144514.GB19938@edu.joroinen.fi> References: <20090810170947.GC24960@edu.joroinen.fi> <4A812ABD.9050402@redhat.com> <20090820144514.GB19938@edu.joroinen.fi> Message-ID: <4A9D1B9B.7010404@redhat.com> > - fix pygrub timeout=0 handling, enable Fedora 11 PV domUs to boot: > http://xenbits.xen.org/staging/xen-3.4-testing.hg?rev/7a57911ff09e > > - fix qemu-dm memory leak on block/disk IO > http://lists.xensource.com/archives/html/xen-devel/2009-08/msg00335.html Committed, build running. > - fix qemu problem when stdvga=1 and videoram=16 are specified, starting hvm domain fails > http://lists.xensource.com/archives/html/xen-devel/2009-08/msg00281.html skipped -- ia64 only. > - fix stubdoms bridge info parsing, use correct bridge > http://lists.xensource.com/archives/html/xen-devel/2009-08/msg00393.html Patch doesn't apply cleanly. cheers, Gerd From kraxel at redhat.com Tue Sep 1 13:04:16 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Tue, 01 Sep 2009 15:04:16 +0200 Subject: [Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released / 3.4.1-2 patches In-Reply-To: <20090827151932.GE31123@reaktio.net> References: <20090810170947.GC24960@edu.joroinen.fi> <4A812ABD.9050402@redhat.com> <20090820144514.GB19938@edu.joroinen.fi> <4A8E7865.7090001@redhat.com> <20090821141604.GR19938@edu.joroinen.fi> <20090827143800.GD31123@reaktio.net> <4A969BDD.8040506@redhat.com> <20090827151932.GE31123@reaktio.net> Message-ID: <4A9D1BD0.5020105@redhat.com> Hi, > http://xenbits.xen.org/staging/xen-unstable.hg?rev/a687c4d35fdd > http://xenbits.xen.org/staging/xen-unstable.hg?rev/7dad2e23bf89 Committed. > http://xenbits.xen.org/staging/xen-unstable.hg?rev/c5125c0ea051 Doesn't apply, probably depends on other changesets ... cheers, Gerd From pasik at iki.fi Tue Sep 1 13:40:51 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 1 Sep 2009 16:40:51 +0300 Subject: [Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released / 3.4.1-2 patches In-Reply-To: <4A9D1BD0.5020105@redhat.com> References: <20090810170947.GC24960@edu.joroinen.fi> <4A812ABD.9050402@redhat.com> <20090820144514.GB19938@edu.joroinen.fi> <4A8E7865.7090001@redhat.com> <20090821141604.GR19938@edu.joroinen.fi> <20090827143800.GD31123@reaktio.net> <4A969BDD.8040506@redhat.com> <20090827151932.GE31123@reaktio.net> <4A9D1BD0.5020105@redhat.com> Message-ID: <20090901134051.GU31123@reaktio.net> On Tue, Sep 01, 2009 at 03:04:16PM +0200, Gerd Hoffmann wrote: > Hi, > > >http://xenbits.xen.org/staging/xen-unstable.hg?rev/a687c4d35fdd > >http://xenbits.xen.org/staging/xen-unstable.hg?rev/7dad2e23bf89 > > Committed. > > >http://xenbits.xen.org/staging/xen-unstable.hg?rev/c5125c0ea051 > > Doesn't apply, probably depends on other changesets ... > I'll check these and get back to you soon.. -- Pasi From pasik at iki.fi Tue Sep 1 14:13:29 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 1 Sep 2009 17:13:29 +0300 Subject: [Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released / 3.4.1-2 patches In-Reply-To: <4A9D1B9B.7010404@redhat.com> References: <20090810170947.GC24960@edu.joroinen.fi> <4A812ABD.9050402@redhat.com> <20090820144514.GB19938@edu.joroinen.fi> <4A9D1B9B.7010404@redhat.com> Message-ID: <20090901141329.GV31123@reaktio.net> On Tue, Sep 01, 2009 at 03:03:23PM +0200, Gerd Hoffmann wrote: > >- fix pygrub timeout=0 handling, enable Fedora 11 PV domUs to boot: > > http://xenbits.xen.org/staging/xen-3.4-testing.hg?rev/7a57911ff09e > > > >- fix qemu-dm memory leak on block/disk IO > > http://lists.xensource.com/archives/html/xen-devel/2009-08/msg00335.html > > Committed, build running. > > >- fix qemu problem when stdvga=1 and videoram=16 are specified, starting > >hvm domain fails > > http://lists.xensource.com/archives/html/xen-devel/2009-08/msg00281.html > > skipped -- ia64 only. > Actually no, it shouldn't be ia64 only. See: http://lists.xensource.com/archives/html/xen-devel/2009-08/msg00276.html > >- fix stubdoms bridge info parsing, use correct bridge > > http://lists.xensource.com/archives/html/xen-devel/2009-08/msg00393.html > > Patch doesn't apply cleanly. > Oh yeah, that'd need backporting to 3.4 first. I guess we can skip this at this point. -- Pasi From pasik at iki.fi Tue Sep 1 14:50:20 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 1 Sep 2009 17:50:20 +0300 Subject: [Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released / 3.4.1-2 patches In-Reply-To: <20090901134051.GU31123@reaktio.net> References: <20090810170947.GC24960@edu.joroinen.fi> <4A812ABD.9050402@redhat.com> <20090820144514.GB19938@edu.joroinen.fi> <4A8E7865.7090001@redhat.com> <20090821141604.GR19938@edu.joroinen.fi> <20090827143800.GD31123@reaktio.net> <4A969BDD.8040506@redhat.com> <20090827151932.GE31123@reaktio.net> <4A9D1BD0.5020105@redhat.com> <20090901134051.GU31123@reaktio.net> Message-ID: <20090901145020.GW31123@reaktio.net> On Tue, Sep 01, 2009 at 04:40:51PM +0300, Pasi K?rkk?inen wrote: > On Tue, Sep 01, 2009 at 03:04:16PM +0200, Gerd Hoffmann wrote: > > Hi, > > > > >http://xenbits.xen.org/staging/xen-unstable.hg?rev/a687c4d35fdd > > >http://xenbits.xen.org/staging/xen-unstable.hg?rev/7dad2e23bf89 > > > > Committed. > > > > >http://xenbits.xen.org/staging/xen-unstable.hg?rev/c5125c0ea051 > > > > Doesn't apply, probably depends on other changesets ... > > > > I'll check these and get back to you soon.. > Attached is a patch that backports the bzip2/lzma-stuff from current xen-unstable to xen-3.4.1. Please use this patch instead of the above changesets from xen-unstable (this patch replaces all of them). It applies cleanly to xen-3.4.1-1 src.rpm (with -p1) and the resulting compiled binaries seem to work. I tried with booting lzma compressed rawhide/F12 kernel. Still no stubdom/pvgrub bzip2/lzma support though. I'll look more into it tonight. -- Pasi -------------- next part -------------- A non-text attachment was scrubbed... Name: xen-341-add-bzip2-lzma-pv-bootloader-support-v2-no-stubdom-pvgrub.patch Type: text/x-diff Size: 13523 bytes Desc: not available URL: From pasik at iki.fi Tue Sep 1 15:17:21 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 1 Sep 2009 18:17:21 +0300 Subject: [Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released / 3.4.1-2 patches In-Reply-To: <20090901145020.GW31123@reaktio.net> References: <4A812ABD.9050402@redhat.com> <20090820144514.GB19938@edu.joroinen.fi> <4A8E7865.7090001@redhat.com> <20090821141604.GR19938@edu.joroinen.fi> <20090827143800.GD31123@reaktio.net> <4A969BDD.8040506@redhat.com> <20090827151932.GE31123@reaktio.net> <4A9D1BD0.5020105@redhat.com> <20090901134051.GU31123@reaktio.net> <20090901145020.GW31123@reaktio.net> Message-ID: <20090901151721.GA31123@reaktio.net> On Tue, Sep 01, 2009 at 05:50:20PM +0300, Pasi K?rkk?inen wrote: > On Tue, Sep 01, 2009 at 04:40:51PM +0300, Pasi K?rkk?inen wrote: > > On Tue, Sep 01, 2009 at 03:04:16PM +0200, Gerd Hoffmann wrote: > > > Hi, > > > > > > >http://xenbits.xen.org/staging/xen-unstable.hg?rev/a687c4d35fdd > > > >http://xenbits.xen.org/staging/xen-unstable.hg?rev/7dad2e23bf89 > > > > > > Committed. > > > > > > >http://xenbits.xen.org/staging/xen-unstable.hg?rev/c5125c0ea051 > > > > > > Doesn't apply, probably depends on other changesets ... > > > > > > > I'll check these and get back to you soon.. > > > > Attached is a patch that backports the bzip2/lzma-stuff from current xen-unstable > to xen-3.4.1. Please use this patch instead of the above changesets from > xen-unstable (this patch replaces all of them). > > It applies cleanly to xen-3.4.1-1 src.rpm (with -p1) and the resulting > compiled binaries seem to work. I tried with booting lzma compressed > rawhide/F12 kernel. > > 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. -- Pasi From kraxel at redhat.com Wed Sep 2 12:25:59 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Wed, 02 Sep 2009 14:25:59 +0200 Subject: [Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released / 3.4.1-2 patches In-Reply-To: <20090901151721.GA31123@reaktio.net> References: <4A812ABD.9050402@redhat.com> <20090820144514.GB19938@edu.joroinen.fi> <4A8E7865.7090001@redhat.com> <20090821141604.GR19938@edu.joroinen.fi> <20090827143800.GD31123@reaktio.net> <4A969BDD.8040506@redhat.com> <20090827151932.GE31123@reaktio.net> <4A9D1BD0.5020105@redhat.com> <20090901134051.GU31123@reaktio.net> <20090901145020.GW31123@reaktio.net> <20090901151721.GA31123@reaktio.net> Message-ID: <4A9E6457.6010206@redhat.com> 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. cheers, Gerd From pasik at iki.fi Wed Sep 2 12:41:09 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 2 Sep 2009 15:41:09 +0300 Subject: [Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released / 3.4.1-2 patches In-Reply-To: <4A9E6457.6010206@redhat.com> References: <4A8E7865.7090001@redhat.com> <20090821141604.GR19938@edu.joroinen.fi> <20090827143800.GD31123@reaktio.net> <4A969BDD.8040506@redhat.com> <20090827151932.GE31123@reaktio.net> <4A9D1BD0.5020105@redhat.com> <20090901134051.GU31123@reaktio.net> <20090901145020.GW31123@reaktio.net> <20090901151721.GA31123@reaktio.net> <4A9E6457.6010206@redhat.com> Message-ID: <20090902124109.GK31123@reaktio.net> 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? -- Pasi From kraxel at redhat.com Wed Sep 2 12:52:21 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Wed, 02 Sep 2009 14:52:21 +0200 Subject: [Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released / 3.4.1-2 patches In-Reply-To: <20090902124109.GK31123@reaktio.net> References: <4A8E7865.7090001@redhat.com> <20090821141604.GR19938@edu.joroinen.fi> <20090827143800.GD31123@reaktio.net> <4A969BDD.8040506@redhat.com> <20090827151932.GE31123@reaktio.net> <4A9D1BD0.5020105@redhat.com> <20090901134051.GU31123@reaktio.net> <20090901145020.GW31123@reaktio.net> <20090901151721.GA31123@reaktio.net> <4A9E6457.6010206@redhat.com> <20090902124109.GK31123@reaktio.net> Message-ID: <4A9E6A85.2000401@redhat.com> Hi, > Does 3.4.1-3 end up in F12 automatically? I think so, alpha freeze is over and beta freeze not yet active ... cheers, Gerd From pasik at iki.fi Wed Sep 2 12:59:31 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 2 Sep 2009 15:59:31 +0300 Subject: [Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released / 3.4.1-3 rpm available from koji In-Reply-To: <20090902124109.GK31123@reaktio.net> References: <20090821141604.GR19938@edu.joroinen.fi> <20090827143800.GD31123@reaktio.net> <4A969BDD.8040506@redhat.com> <20090827151932.GE31123@reaktio.net> <4A9D1BD0.5020105@redhat.com> <20090901134051.GU31123@reaktio.net> <20090901145020.GW31123@reaktio.net> <20090901151721.GA31123@reaktio.net> <4A9E6457.6010206@redhat.com> <20090902124109.GK31123@reaktio.net> Message-ID: <20090902125931.GL31123@reaktio.net> 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 - 3.4.1-3 - swap bzip2+xz linux kernel compression support patches. - backport one more bugfix (videoram option). * Tue Sep 01 2009 Gerd Hoffmann - 3.4.1-2 - backport bzip2+xz linux kernel compression support. - backport a few bugfixes. -- Pasi From pasik at iki.fi Wed Sep 2 13:08:32 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 2 Sep 2009 16:08:32 +0300 Subject: [Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released / 3.4.1-3 rpm available from koji In-Reply-To: <20090902125931.GL31123@reaktio.net> References: <20090827143800.GD31123@reaktio.net> <4A969BDD.8040506@redhat.com> <20090827151932.GE31123@reaktio.net> <4A9D1BD0.5020105@redhat.com> <20090901134051.GU31123@reaktio.net> <20090901145020.GW31123@reaktio.net> <20090901151721.GA31123@reaktio.net> <4A9E6457.6010206@redhat.com> <20090902124109.GK31123@reaktio.net> <20090902125931.GL31123@reaktio.net> Message-ID: <20090902130832.GM31123@reaktio.net> 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 - 3.4.1-3 > - swap bzip2+xz linux kernel compression support patches. > - backport one more bugfix (videoram option). > > * Tue Sep 01 2009 Gerd Hoffmann - 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. -- Pasi From mark.schloesser at rwth-aachen.de Wed Sep 2 13:32:43 2009 From: mark.schloesser at rwth-aachen.de (Mark Schloesser) Date: Wed, 02 Sep 2009 15:32:43 +0200 Subject: [Fedora-xen] moderation Message-ID: <4A9E73FB.2060901@rwth-aachen.de> 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 260 bytes Desc: OpenPGP digital signature URL: From markmc at redhat.com Wed Sep 2 16:21:54 2009 From: markmc at redhat.com (Mark McLoughlin) Date: Wed, 02 Sep 2009 17:21:54 +0100 Subject: [Fedora-xen] moderation In-Reply-To: <4A9E73FB.2060901@rwth-aachen.de> References: <4A9E73FB.2060901@rwth-aachen.de> Message-ID: <1251908514.6115.201.camel@blaa> On Wed, 2009-09-02 at 15:32 +0200, Mark Schloesser wrote: > 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? I flushed the queue earlier today and probably missed your mail amongst the ~200 spam Please re-send, using e.g. nopaste is probably a good idea with large logs Cheers, Mark. From mark.schloesser at rwth-aachen.de Wed Sep 2 21:55:58 2009 From: mark.schloesser at rwth-aachen.de (Mark Schloesser) Date: Wed, 02 Sep 2009 23:55:58 +0200 Subject: [Fedora-xen] xen 3.4.1 + myoung x86_64 kernel Message-ID: <4A9EE9EE.2050603@rwth-aachen.de> 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 260 bytes Desc: OpenPGP digital signature URL: From bderzhavets at yahoo.com Thu Sep 3 02:32:31 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Wed, 2 Sep 2009 19:32:31 -0700 (PDT) Subject: [Fedora-xen] xen 3.4.1 + myoung x86_64 kernel Message-ID: <13841.75619.qm@web56102.mail.re3.yahoo.com> ? 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 wrote: From: Mark Schloesser Subject: [Fedora-xen] xen 3.4.1 + myoung x86_64 kernel To: fedora-xen at 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 at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: config-work.gz Type: application/x-gzip Size: 23669 bytes Desc: not available URL: From bderzhavets at yahoo.com Thu Sep 3 02:51:01 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Wed, 2 Sep 2009 19:51:01 -0700 (PDT) Subject: [Fedora-xen] xen 3.4.1 + myoung x86_64 kernel In-Reply-To: <4A9EE9EE.2050603@rwth-aachen.de> Message-ID: <90220.69208.qm@web56107.mail.re3.yahoo.com> Did you build and and start services as root ? After xen-3.1.4-3.src.rpm "rpmbuild"? followed by install of generated packages run:- ? # chkconfig xend on ? # service xend start Same commands for xenstored,xenconsoled,xendomains Configure Libvirt Preview Repo and run :- # yum install libvirt libvirt-python python-virtinst virt-manager virt-viewer # chkconfig libvirtd on # service libvirtd start Next :- # rpm -qa|grep xen # rpm -qa|grep virt Make sure right packages installed on F11 Boris. --- On Wed, 9/2/09, Mark Schloesser wrote: From: Mark Schloesser Subject: [Fedora-xen] xen 3.4.1 + myoung x86_64 kernel To: fedora-xen at 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 at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: From markmc at redhat.com Thu Sep 3 09:50:26 2009 From: markmc at redhat.com (Mark McLoughlin) Date: Thu, 03 Sep 2009 10:50:26 +0100 Subject: [Fedora-xen] Cross-posting to fedora-virt Message-ID: <1251971426.3084.48.camel@blaa> 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. From berrange at redhat.com Thu Sep 3 10:41:25 2009 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 3 Sep 2009 11:41:25 +0100 Subject: [Fedora-xen] Cross-posting to fedora-virt In-Reply-To: <1251971426.3084.48.camel@blaa> References: <1251971426.3084.48.camel@blaa> Message-ID: <20090903104125.GI8626@redhat.com> On Thu, Sep 03, 2009 at 10:50:26AM +0100, Mark McLoughlin wrote: > 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 I vote for b), and keep fedora-xen soley as a place for discussion of the Dom0 pvops work until such time as that's merged upstream, when we can close it down & have everything on fedora-virt. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From Dustin.Henning at prd-inc.com Thu Sep 3 12:30:03 2009 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Thu, 3 Sep 2009 08:30:03 -0400 Subject: [Fedora-xen] Cross-posting to fedora-virt In-Reply-To: <20090903104125.GI8626@redhat.com> References: <1251971426.3084.48.camel@blaa> <20090903104125.GI8626@redhat.com> Message-ID: <003d01ca2c92$432a3f50$c97ebdf0$@Henning@prd-inc.com> Does this imply that other Xen discussion (such as choosing to use the 2.6.18 kernel to run Xen 3.4.1 on Fedora) should be discussed at fedora-virt or xen-users? I know most Fedora questions on xen-users typically get a pretty useless "Fedora isn't supporting Xen" type response as opposed to a "you will have to build it yourself since Fedora doesn't have a working kernel" or "I see that you built yourself, so let's try this" type response, so I think trying to deal with xen issues there currently hurts Fedora users. If all Xen discussion related to Fedora is carried out in fedora-xen (as opposed to just pvops), this is all fine and well, but if non-pvops xen on fedora discussion is carried out in fedora-virt and the lists aren't merged, then the ken user base for fedora is probably split up. For instance, I am not a member of fedora-virt, as I was waiting for this to be done automatically when xen went back into mainstream Fedora, but if Xen beyond the pvops business is being discussed there, then perhaps I should be. Regardless, when the time comes, will fedora-xen users automatically be placed on fedora-virt instead? Will duplicate subscriptions caused by this merge be prevented? Dustin -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Daniel P. Berrange Sent: Thursday, September 03, 2009 06:41 To: Mark McLoughlin Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] Cross-posting to fedora-virt On Thu, Sep 03, 2009 at 10:50:26AM +0100, Mark McLoughlin wrote: > 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 I vote for b), and keep fedora-xen soley as a place for discussion of the Dom0 pvops work until such time as that's merged upstream, when we can close it down & have everything on fedora-virt. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From pasik at iki.fi Thu Sep 3 15:20:31 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Thu, 3 Sep 2009 18:20:31 +0300 Subject: [Fedora-xen] Cross-posting to fedora-virt In-Reply-To: <20090903104125.GI8626@redhat.com> References: <1251971426.3084.48.camel@blaa> <20090903104125.GI8626@redhat.com> Message-ID: <20090903152031.GQ31123@reaktio.net> On Thu, Sep 03, 2009 at 11:41:25AM +0100, Daniel P. Berrange wrote: > On Thu, Sep 03, 2009 at 10:50:26AM +0100, Mark McLoughlin wrote: > > 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 > > I vote for b), and keep fedora-xen soley as a place for discussion of > the Dom0 pvops work until such time as that's merged upstream, when > we can close it down & have everything on fedora-virt. > Makes sense to me.. How about general Xen-related discussion? domU support? also on fedora-xen, or on fedora-virt? -- Pasi From mark.schloesser at rwth-aachen.de Fri Sep 4 08:48:33 2009 From: mark.schloesser at rwth-aachen.de (Mark Schloesser) Date: Fri, 04 Sep 2009 10:48:33 +0200 Subject: [Fedora-xen] xen 3.4.1 + myoung x86_64 kernel In-Reply-To: <90220.69208.qm@web56107.mail.re3.yahoo.com> References: <90220.69208.qm@web56107.mail.re3.yahoo.com> Message-ID: <4AA0D461.4090000@rwth-aachen.de> Thanks Boris, I finally have xen running! I started over with a fresh F11 install and used JF git kernel with xen-3.1.4-3.src.rpm. The system starts up just fine with or without xen enabled on this 2.6.31-rc6 kernel. The GDM/Xorg does not work though. I have an nvidia NVS290 in this machine and the nouveau driver complained about not being able to load the kernel module - directly followed by a backtrace dump in the Xorg log. I then disabled the nouveau driver trying to get it done with vesa driver - seemed to give no errors but ended up in the same kind of backtrace. on vesa: Backtrace: 0: /usr/bin/Xorg(xorg_backtrace+0x26) [0x4e89b6] 1: /usr/bin/Xorg(xf86SigHandler+0x6f) [0x47d63f] 2: /lib64/libc.so.6 [0x350fc33370] 3: /usr/lib64/xorg/modules//libint10.so(x_outl+0x25) [0x7f70cf4bde15] 4: /usr/lib64/xorg/modules//libint10.so [0x7f70cf4c43d0] 5: /usr/lib64/xorg/modules//libint10.so(X86EMU_exec+0x81) [0x7f70cf4d0e81] 6: /usr/lib64/xorg/modules//libint10.so(xf86ExecX86int10+0x55) [0x7f70cf4bf585] 7: /usr/lib64/xorg/modules//libvbe.so(VBEExtendedInit+0x96) [0x7f70cf6dd066] 8: /usr/lib64/xorg/modules/drivers//vesa_drv.so [0x7f70cfcee458] 9: /usr/bin/Xorg(InitOutput+0x507) [0x467377] 10: /usr/bin/Xorg(main+0x1fe) [0x42cf1e] 11: /lib64/libc.so.6(__libc_start_main+0xfd) [0x350fc1ea2d] 12: /usr/bin/Xorg [0x42c559] any hints on how to get X back up again? Thanks, Mark Boris Derzhavets wrote: > Did you build and and start services as root ? > After xen-3.1.4-3.src.rpm "rpmbuild" followed by install of generated packages run:- > > # chkconfig xend on > > # service xend start > Same commands for xenstored,xenconsoled,xendomains > > Configure Libvirt Preview Repo and run :- > # yum install libvirt libvirt-python python-virtinst virt-manager virt-viewer > > # chkconfig libvirtd on > > # service libvirtd start > > Next :- > # rpm -qa|grep xen > # rpm -qa|grep virt > > Make sure right packages installed on F11 > > Boris. > > --- On Wed, 9/2/09, Mark Schloesser wrote: > > From: Mark Schloesser > Subject: [Fedora-xen] xen 3.4.1 + myoung x86_64 kernel > To: fedora-xen at 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 at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 260 bytes Desc: OpenPGP digital signature URL: From mark.schloesser at rwth-aachen.de Fri Sep 4 09:44:32 2009 From: mark.schloesser at rwth-aachen.de (Mark Schloesser) Date: Fri, 04 Sep 2009 11:44:32 +0200 Subject: [Fedora-xen] xen 3.4.1 + myoung x86_64 kernel In-Reply-To: <4AA0D461.4090000@rwth-aachen.de> References: <90220.69208.qm@web56107.mail.re3.yahoo.com> <4AA0D461.4090000@rwth-aachen.de> Message-ID: <4AA0E180.3040409@rwth-aachen.de> I somehow did not search deeply enough - there was a related discussion on xen-devel mailing list. It is a little hidden in the "Vt-d not working with 3.4.1" thread. There does not seem to be a final "i got it" post though - I'll try some different solutions proposed there. Mark Mark Schloesser wrote: > Thanks Boris, I finally have xen running! > > I started over with a fresh F11 install and used JF git kernel with > xen-3.1.4-3.src.rpm. The system starts up just fine with or without xen > enabled on this 2.6.31-rc6 kernel. > > The GDM/Xorg does not work though. I have an nvidia NVS290 in this > machine and the nouveau driver complained about not being able to load > the kernel module - directly followed by a backtrace dump in the Xorg > log. I then disabled the nouveau driver trying to get it done with vesa > driver - seemed to give no errors but ended up in the same kind of > backtrace. > > on vesa: > > Backtrace: > 0: /usr/bin/Xorg(xorg_backtrace+0x26) [0x4e89b6] > 1: /usr/bin/Xorg(xf86SigHandler+0x6f) [0x47d63f] > 2: /lib64/libc.so.6 [0x350fc33370] > 3: /usr/lib64/xorg/modules//libint10.so(x_outl+0x25) [0x7f70cf4bde15] > 4: /usr/lib64/xorg/modules//libint10.so [0x7f70cf4c43d0] > 5: /usr/lib64/xorg/modules//libint10.so(X86EMU_exec+0x81) [0x7f70cf4d0e81] > 6: /usr/lib64/xorg/modules//libint10.so(xf86ExecX86int10+0x55) > [0x7f70cf4bf585] > 7: /usr/lib64/xorg/modules//libvbe.so(VBEExtendedInit+0x96) [0x7f70cf6dd066] > 8: /usr/lib64/xorg/modules/drivers//vesa_drv.so [0x7f70cfcee458] > 9: /usr/bin/Xorg(InitOutput+0x507) [0x467377] > 10: /usr/bin/Xorg(main+0x1fe) [0x42cf1e] > 11: /lib64/libc.so.6(__libc_start_main+0xfd) [0x350fc1ea2d] > 12: /usr/bin/Xorg [0x42c559] > > > any hints on how to get X back up again? > > Thanks, > Mark > > > Boris Derzhavets wrote: >> Did you build and and start services as root ? >> After xen-3.1.4-3.src.rpm "rpmbuild" followed by install of generated packages run:- >> >> # chkconfig xend on >> >> # service xend start >> Same commands for xenstored,xenconsoled,xendomains >> >> Configure Libvirt Preview Repo and run :- >> # yum install libvirt libvirt-python python-virtinst virt-manager virt-viewer >> >> # chkconfig libvirtd on >> >> # service libvirtd start >> >> Next :- >> # rpm -qa|grep xen >> # rpm -qa|grep virt >> >> Make sure right packages installed on F11 >> >> Boris. >> >> --- On Wed, 9/2/09, Mark Schloesser wrote: >> >> From: Mark Schloesser >> Subject: [Fedora-xen] xen 3.4.1 + myoung x86_64 kernel >> To: fedora-xen at 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 at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen >> >> >> >> > > > ------------------------------------------------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 260 bytes Desc: OpenPGP digital signature URL: From mark.schloesser at rwth-aachen.de Fri Sep 4 14:26:32 2009 From: mark.schloesser at rwth-aachen.de (Mark Schloesser) Date: Fri, 04 Sep 2009 16:26:32 +0200 Subject: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable Message-ID: <4AA12398.1010300@rwth-aachen.de> 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 260 bytes Desc: OpenPGP digital signature URL: From pasik at iki.fi Fri Sep 4 15:01:24 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Fri, 4 Sep 2009 18:01:24 +0300 Subject: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <4AA12398.1010300@rwth-aachen.de> References: <4AA12398.1010300@rwth-aachen.de> Message-ID: <20090904150124.GT31123@reaktio.net> On Fri, Sep 04, 2009 at 04:26:32PM +0200, Mark Schloesser wrote: > 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 :) > VGA/GFX passthrough is very much under development atm, it's very new stuff. > 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... > Some people are using http://xenbits.xen.org/linux-2.6.18-xen.hg as dom0 kernel. That's the old xenlinux kernel, the default dom0 kernel for Xen 3.4.x and earlier versions. > - 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. > Did you use the binary/proprietary nvidia driver, of the the opensource driver? I think you'll have more luck with the opensource driver. -- Pasi From bderzhavets at yahoo.com Fri Sep 4 15:07:19 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Fri, 4 Sep 2009 08:07:19 -0700 (PDT) Subject: [Fedora-xen] xen 3.4.1 + myoung x86_64 kernel In-Reply-To: <4AA0E180.3040409@rwth-aachen.de> Message-ID: <145022.44037.qm@web56108.mail.re3.yahoo.com> > I started over with a fresh F11 install and used JF git kernel with > xen-3.1.4-3.src.rpm. The system starts up just fine with or without xen > enabled on this 2.6.31-rc6 kernel. I believe, you have to enable Xen Privileged Domain Support in JF kernel to load it under Xen 3.4.X Hypervisor. Otherwise, Dom0 won't be loaded. Boris. --- On Fri, 9/4/09, Mark Schloesser wrote: From: Mark Schloesser Subject: Re: [Fedora-xen] xen 3.4.1 + myoung x86_64 kernel To: fedora-xen at redhat.com Date: Friday, September 4, 2009, 5:44 AM I somehow did not search deeply enough - there was a related discussion on xen-devel mailing list. It is a little hidden in the "Vt-d not working with 3.4.1" thread. There does not seem to be a final "i got it" post though - I'll try some different solutions proposed there. Mark Mark Schloesser wrote: > Thanks Boris, I finally have xen running! > > I started over with a fresh F11 install and used JF git kernel with > xen-3.1.4-3.src.rpm. The system starts up just fine with or without xen > enabled on this 2.6.31-rc6 kernel. > > The GDM/Xorg does not work though. I have an nvidia NVS290 in this > machine and the nouveau driver complained about not being able to load > the kernel module - directly followed by a backtrace dump in the Xorg > log. I then disabled the nouveau driver trying to get it done with vesa > driver - seemed to give no errors but ended up in the same kind of > backtrace. > > on vesa: > > Backtrace: > 0: /usr/bin/Xorg(xorg_backtrace+0x26) [0x4e89b6] > 1: /usr/bin/Xorg(xf86SigHandler+0x6f) [0x47d63f] > 2: /lib64/libc.so.6 [0x350fc33370] > 3: /usr/lib64/xorg/modules//libint10.so(x_outl+0x25) [0x7f70cf4bde15] > 4: /usr/lib64/xorg/modules//libint10.so [0x7f70cf4c43d0] > 5: /usr/lib64/xorg/modules//libint10.so(X86EMU_exec+0x81) [0x7f70cf4d0e81] > 6: /usr/lib64/xorg/modules//libint10.so(xf86ExecX86int10+0x55) > [0x7f70cf4bf585] > 7: /usr/lib64/xorg/modules//libvbe.so(VBEExtendedInit+0x96) [0x7f70cf6dd066] > 8: /usr/lib64/xorg/modules/drivers//vesa_drv.so [0x7f70cfcee458] > 9: /usr/bin/Xorg(InitOutput+0x507) [0x467377] > 10: /usr/bin/Xorg(main+0x1fe) [0x42cf1e] > 11: /lib64/libc.so.6(__libc_start_main+0xfd) [0x350fc1ea2d] > 12: /usr/bin/Xorg [0x42c559] > > > any hints on how to get X back up again? > > Thanks, > Mark > > > Boris Derzhavets wrote: >> Did you build and and start services as root ? >> After xen-3.1.4-3.src.rpm "rpmbuild"? followed by install of? generated packages run:- >>? >> # chkconfig xend on >>? >> # service xend start >> Same commands for xenstored,xenconsoled,xendomains >> >> Configure Libvirt Preview Repo and run :- >> # yum install libvirt libvirt-python python-virtinst virt-manager virt-viewer >> >> # chkconfig libvirtd on >> >> # service libvirtd start >> >> Next :- >> # rpm -qa|grep xen >> # rpm -qa|grep virt >> >> Make sure right packages installed on F11 >> >> Boris. >> >> --- On Wed, 9/2/09, Mark Schloesser wrote: >> >> From: Mark Schloesser >> Subject: [Fedora-xen] xen 3.4.1 + myoung x86_64 kernel >> To: fedora-xen at 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 at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen >> >> >> >>? ? ??? > > > ------------------------------------------------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: From pasik at iki.fi Fri Sep 4 15:11:40 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Fri, 4 Sep 2009 18:11:40 +0300 Subject: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <20090904150124.GT31123@reaktio.net> References: <4AA12398.1010300@rwth-aachen.de> <20090904150124.GT31123@reaktio.net> Message-ID: <20090904151140.GU31123@reaktio.net> On Fri, Sep 04, 2009 at 06:01:24PM +0300, Pasi K?rkk?inen wrote: > On Fri, Sep 04, 2009 at 04:26:32PM +0200, Mark Schloesser wrote: > > 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 :) > > > > VGA/GFX passthrough is very much under development atm, it's very new stuff. > > > 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... > > > > Some people are using http://xenbits.xen.org/linux-2.6.18-xen.hg as dom0 kernel. > > That's the old xenlinux kernel, the default dom0 kernel for Xen 3.4.x > and earlier versions. > And based on the recent emails on xen-devel, I think some people got it working also using pv_ops dom0 kernel. -- Pasi From bderzhavets at yahoo.com Fri Sep 4 15:13:09 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Fri, 4 Sep 2009 08:13:09 -0700 (PDT) Subject: [Fedora-xen] xen 3.4.1 + myoung x86_64 kernel In-Reply-To: <4AA0D461.4090000@rwth-aachen.de> Message-ID: <658911.93653.qm@web56105.mail.re3.yahoo.com> Setup VNC. # yum install tigervnc-server # vncserver :1 -geometry 1280x1024 -depth 16 Connect remotely via vncviewer IP-Dom0:1 Boris --- On Fri, 9/4/09, Mark Schloesser wrote: From: Mark Schloesser Subject: Re: [Fedora-xen] xen 3.4.1 + myoung x86_64 kernel To: "Boris Derzhavets" Cc: fedora-xen at redhat.com Date: Friday, September 4, 2009, 4:48 AM Thanks Boris, I finally have xen running! I started over with a fresh F11 install and used JF git kernel with xen-3.1.4-3.src.rpm. The system starts up just fine with or without xen enabled on this 2.6.31-rc6 kernel. The GDM/Xorg does not work though. I have an nvidia NVS290 in this machine and the nouveau driver complained about not being able to load the kernel module - directly followed by a backtrace dump in the Xorg log. I then disabled the nouveau driver trying to get it done with vesa driver - seemed to give no errors but ended up in the same kind of backtrace. on vesa: Backtrace: 0: /usr/bin/Xorg(xorg_backtrace+0x26) [0x4e89b6] 1: /usr/bin/Xorg(xf86SigHandler+0x6f) [0x47d63f] 2: /lib64/libc.so.6 [0x350fc33370] 3: /usr/lib64/xorg/modules//libint10.so(x_outl+0x25) [0x7f70cf4bde15] 4: /usr/lib64/xorg/modules//libint10.so [0x7f70cf4c43d0] 5: /usr/lib64/xorg/modules//libint10.so(X86EMU_exec+0x81) [0x7f70cf4d0e81] 6: /usr/lib64/xorg/modules//libint10.so(xf86ExecX86int10+0x55) [0x7f70cf4bf585] 7: /usr/lib64/xorg/modules//libvbe.so(VBEExtendedInit+0x96) [0x7f70cf6dd066] 8: /usr/lib64/xorg/modules/drivers//vesa_drv.so [0x7f70cfcee458] 9: /usr/bin/Xorg(InitOutput+0x507) [0x467377] 10: /usr/bin/Xorg(main+0x1fe) [0x42cf1e] 11: /lib64/libc.so.6(__libc_start_main+0xfd) [0x350fc1ea2d] 12: /usr/bin/Xorg [0x42c559] any hints on how to get X back up again? Thanks, Mark Boris Derzhavets wrote: > Did you build and and start services as root ? > After xen-3.1.4-3.src.rpm "rpmbuild"? followed by install of? generated packages run:- >? > # chkconfig xend on >? > # service xend start > Same commands for xenstored,xenconsoled,xendomains > > Configure Libvirt Preview Repo and run :- > # yum install libvirt libvirt-python python-virtinst virt-manager virt-viewer > > # chkconfig libvirtd on > > # service libvirtd start > > Next :- > # rpm -qa|grep xen > # rpm -qa|grep virt > > Make sure right packages installed on F11 > > Boris. > > --- On Wed, 9/2/09, Mark Schloesser wrote: > > From: Mark Schloesser > Subject: [Fedora-xen] xen 3.4.1 + myoung x86_64 kernel > To: fedora-xen at 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 at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > >? ? ??? -------------- next part -------------- An HTML attachment was scrubbed... URL: From bderzhavets at yahoo.com Fri Sep 4 18:02:07 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Fri, 4 Sep 2009 11:02:07 -0700 (PDT) Subject: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <4AA12398.1010300@rwth-aachen.de> Message-ID: <215974.89472.qm@web56106.mail.re3.yahoo.com> I did "git pull" , built 2.6.31-c8 kernel with Xen Dom0 support. However, attempt to load kernel under Xen 3.4.1 drops into stack trace and hangs on both F11 and Ubuntu 9.10. Old 2.6.31-rc6's .config file has been used without any changes. I can't set up serial console in meantime. Boris --- On Fri, 9/4/09, Mark Schloesser wrote: From: Mark Schloesser Subject: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: fedora-xen at redhat.com Date: Friday, September 4, 2009, 10:26 AM 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 -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: From bderzhavets at yahoo.com Sat Sep 5 10:14:21 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Sat, 5 Sep 2009 03:14:21 -0700 (PDT) Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <215974.89472.qm@web56106.mail.re3.yahoo.com> Message-ID: <404831.95621.qm@web56104.mail.re3.yahoo.com> Mark, Could you share your .config for JF's 2.6.31-rc8 which loads under Xen Unstable. Looks like i miss some point tuning kernel. Thanks. Boris. --- On Fri, 9/4/09, Boris Derzhavets wrote: From: Boris Derzhavets Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: fedora-xen at redhat.com, "Mark Schloesser" Cc: xen-devel at lists.xensource.com Date: Friday, September 4, 2009, 2:02 PM I did "git pull" , built 2.6.31-c8 kernel with Xen Dom0 support. However, attempt to load kernel under Xen 3.4.1 drops into stack trace and hangs on both F11 and Ubuntu 9.10. Old 2.6.31-rc6's .config file has been used without any changes. I can't set up serial console in meantime. Boris --- On Fri, 9/4/09, Mark Schloesser wrote: From: Mark Schloesser Subject: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: fedora-xen at redhat.com Date: Friday, September 4, 2009, 10:26 AM 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 -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -----Inline Attachment Follows----- _______________________________________________ Xen-devel mailing list Xen-devel at lists.xensource.com http://lists.xensource.com/xen-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeremy at goop.org Fri Sep 4 20:09:08 2009 From: jeremy at goop.org (Jeremy Fitzhardinge) Date: Fri, 04 Sep 2009 13:09:08 -0700 Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <215974.89472.qm@web56106.mail.re3.yahoo.com> References: <215974.89472.qm@web56106.mail.re3.yahoo.com> Message-ID: <4AA173E4.9050007@goop.org> On 09/04/09 11:02, Boris Derzhavets wrote: > I did "git pull" , built 2.6.31-c8 kernel with Xen Dom0 support. > However, attempt to load kernel under Xen 3.4.1 drops > into stack trace and hangs on both F11 and Ubuntu 9.10. > Old 2.6.31-rc6's .config file has been used without any changes. > I can't set up serial console in meantime. > What's the stack trace? Even of a photo of it may give some clues. Needless to say, it does work for me with current xen-unstable; there shouldn't be any new hypervisor version dependencies. J From pasik at iki.fi Sun Sep 6 12:04:05 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 6 Sep 2009 15:04:05 +0300 Subject: [Fedora-xen] Fedora 12 (rawhide) Xen domU works now, minor console keymap issue? Message-ID: <20090906120405.GW31123@reaktio.net> 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 From mark.schloesser at rwth-aachen.de Sun Sep 6 15:09:34 2009 From: mark.schloesser at rwth-aachen.de (Mark Schloesser) Date: Sun, 06 Sep 2009 17:09:34 +0200 Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <404831.95621.qm@web56104.mail.re3.yahoo.com> References: <404831.95621.qm@web56104.mail.re3.yahoo.com> Message-ID: <4AA3D0AE.2080009@rwth-aachen.de> Boris, actually I used your config. The same config as I used for -rc6 build. Works just fine for me - but I did not try booting with 3.4.1, only with xen-unstable. Mark Boris Derzhavets wrote: > Mark, > Could you share your .config for JF's 2.6.31-rc8 which loads under Xen Unstable. > Looks like i miss some point tuning kernel. > > Thanks. > Boris. > > --- On Fri, 9/4/09, Boris Derzhavets wrote: > > From: Boris Derzhavets > Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: fedora-xen at redhat.com, "Mark Schloesser" > Cc: xen-devel at lists.xensource.com > Date: Friday, September 4, 2009, 2:02 PM > > I did "git pull" , built 2.6.31-c8 kernel with Xen Dom0 support. > However, attempt to load kernel under Xen 3.4.1 drops > into stack trace and hangs on both F11 and Ubuntu 9.10. > Old 2.6.31-rc6's .config file has been used without any changes. > I can't set up serial console in meantime. > > Boris > > --- On Fri, 9/4/09, Mark Schloesser wrote: > > From: Mark Schloesser > Subject: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: fedora-xen at redhat.com > Date: Friday, September 4, 2009, 10:26 AM > > 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 > > > -----Inline Attachment Follows----- > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > -----Inline Attachment Follows----- > > _______________________________________________ > Xen-devel mailing list > Xen-devel at lists.xensource.com > http://lists.xensource.com/xen-devel > > > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-devel mailing list > Xen-devel at lists.xensource.com > http://lists.xensource.com/xen-devel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 260 bytes Desc: OpenPGP digital signature URL: From mark.schloesser at rwth-aachen.de Sun Sep 6 16:17:39 2009 From: mark.schloesser at rwth-aachen.de (Mark Schloesser) Date: Sun, 06 Sep 2009 18:17:39 +0200 Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <324257.12640.qm@web56105.mail.re3.yahoo.com> References: <324257.12640.qm@web56105.mail.re3.yahoo.com> Message-ID: <4AA3E0A3.8000902@rwth-aachen.de> 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 Boris Derzhavets wrote: > I tried to build and load on F12 rawhide with the most recent > gcc,glibc and kernel (fedoras). So, xen was installed via > xen-3.4.1-3.src.rpm along with libvirt ( via rawhide again). Please, > let me know your environment for successful build and load rc8 under > Xen 3.5. > > Boris. > BTW > Please,be advised :- > > ********** > Quote:- > ********** > >> 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 >> +#include > > >struct device; > >struct dma_attrs; > > Now kernel gets built, but still fails to load under either Xen 3.5 or Xen > 3.4.1. > Stack traces differ on C2D E8400 (Xen 3.4.1) and Q9550 (Xen 3.5 unstable )boxes. > On the last box :- > > do_one_initcall + 0x37/0x1a0 > kernel_init + 0x164/0x1ba > child_rip + 0xa/0x20 > ? int_ret_from_sys_call 0x7/0x16 > ? retint_restore_arg + 0x5/0x6 > ? child_rip 0x0/0x20 > > Two last > commands are the same on the first box. Previous differ. > > Boris. > P.S. I cannot buy or order 20 m of NUL modem cable. > Just 2.5 m . That's all > > --- On Sat, 9/5/09, Jeremy Fitzhardinge wrote: > > From: Jeremy Fitzhardinge > Subject: [Xen-devel] Re: Errors when build 2.6.31-rc8 > To: "Boris Derzhavets" > Cc: "Xen-devel" > 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 > +#include > > struct device; > struct dma_attrs; > > J > > > --- On Sun, 9/6/09, Mark Schloesser wrote: > > From: Mark Schloesser > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" > Cc: fedora-xen at redhat.com, xen-devel at lists.xensource.com > Date: Sunday, September 6, 2009, 11:09 AM > > Boris, > > actually I used your config. The same config as I used for -rc6 build. > Works just fine for me - but I did not try booting with 3.4.1, only with > xen-unstable. > > Mark > > > Boris Derzhavets wrote: >> Mark, >> Could you share your .config for JF's 2.6.31-rc8 which loads under Xen Unstable. >> Looks like i miss some point tuning kernel. >> >> Thanks. >> Boris. >> >> --- On Fri, 9/4/09, Boris Derzhavets wrote: >> >> From: Boris Derzhavets >> Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable >> To: fedora-xen at redhat.com, "Mark Schloesser" >> Cc: xen-devel at lists.xensource.com >> Date: Friday, September 4, 2009, 2:02 PM >> >> I did "git pull" , built 2.6.31-c8 kernel with Xen Dom0 support. >> However, attempt to load kernel under Xen 3.4.1 drops >> into stack trace and hangs on both F11 and Ubuntu 9.10. >> Old 2.6.31-rc6's .config file has been used without any changes. >> I can't set up serial console in meantime. >> >> Boris >> >> --- On Fri, 9/4/09, Mark Schloesser wrote: >> >> From: Mark Schloesser >> Subject: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable >> To: fedora-xen at redhat.com >> Date: Friday, September 4, 2009, 10:26 AM >> >> 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 >> >> >> -----Inline Attachment Follows----- >> >> -- >> Fedora-xen mailing list >> Fedora-xen at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen >> >> >> >> >> >> >> -----Inline Attachment Follows----- >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel at lists.xensource.com >> http://lists.xensource.com/xen-devel >> >> >> >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel at lists.xensource.com >> http://lists.xensource.com/xen-devel > > > > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-devel mailing list > Xen-devel at lists.xensource.com > http://lists.xensource.com/xen-devel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 260 bytes Desc: OpenPGP digital signature URL: From bderzhavets at yahoo.com Sun Sep 6 16:56:07 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Sun, 6 Sep 2009 09:56:07 -0700 (PDT) Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 In-Reply-To: <4AA2885E.7070400@goop.org> Message-ID: <768700.43243.qm@web56105.mail.re3.yahoo.com> 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 [] 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 wrote: From: Jeremy Fitzhardinge Subject: [Xen-devel] Re: Errors when build 2.6.31-rc8 To: "Boris Derzhavets" Cc: "Xen-devel" 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 +#include struct device; struct dma_attrs; ??? J _______________________________________________ Xen-devel mailing list Xen-devel at lists.xensource.com http://lists.xensource.com/xen-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From bderzhavets at yahoo.com Sun Sep 6 17:04:26 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Sun, 6 Sep 2009 10:04:26 -0700 (PDT) Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 In-Reply-To: <768700.43243.qm@web56105.mail.re3.yahoo.com> Message-ID: <711436.77747.qm@web56103.mail.re3.yahoo.com> I believe, that some set of CSs from Xen 3.5 has to be included as patches into xen-3.4.1-3.src.rpm, in case if it causes by 3.4.1 Hypervisor. Otherwise? , F12 release in November won't have suitable Dom0 kernel again. I would guess 2.6.31-rc6 at best. Boris. --- On Sun, 9/6/09, Boris Derzhavets wrote: From: Boris Derzhavets Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 To: "Jeremy Fitzhardinge" Cc: "Xen-devel" , fedora-xen at redhat.com Date: Sunday, September 6, 2009, 12:56 PM 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 [] 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, -------------- next part -------------- An HTML attachment was scrubbed... URL: From pasik at iki.fi Sun Sep 6 18:37:45 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 6 Sep 2009 21:37:45 +0300 Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 In-Reply-To: <4AA3ECF6.5040206@asiasoftsea.net> References: <711436.77747.qm@web56103.mail.re3.yahoo.com> <4AA3ECF6.5040206@asiasoftsea.net> Message-ID: <20090906183745.GY31123@reaktio.net> On Mon, Sep 07, 2009 at 01:10:14AM +0800, Mr. Teo En Ming (Zhang Enming) wrote: > On 09/07/2009 01:04 AM, Boris Derzhavets wrote: > >I believe, that some set of CSs from Xen 3.5 has to be included as > >patches into > >xen-3.4.1-3.src.rpm, in case if it causes by 3.4.1 Hypervisor. > >Otherwise , F12 release in November won't have suitable Dom0 kernel > >again. > >I would guess 2.6.31-rc6 at best. > > > >Boris. > > > >--- On *Sun, 9/6/09, Boris Derzhavets //* wrote: > > > > > > From: Boris Derzhavets > > Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 > > To: "Jeremy Fitzhardinge" > > Cc: "Xen-devel" , fedora-xen at redhat.com > > Date: Sunday, September 6, 2009, 12:56 PM > > > > 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 [] 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, > > > > > > > > > I thought Fedora will no longer have dom 0 kernel? > http://fedoraproject.org/wiki/Features/XenPvopsDom0 "Dom0 status: awaiting upstream kernel support" -- Pasi From bderzhavets at yahoo.com Mon Sep 7 04:49:41 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Sun, 6 Sep 2009 21:49:41 -0700 (PDT) Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 In-Reply-To: <20090906183745.GY31123@reaktio.net> Message-ID: <169290.4400.qm@web56106.mail.re3.yahoo.com> As far as Xen 3.5 tarball will be officially released kernel supporting Dom0 should be JF's pvops kernel. When? xen-3.5.0-X.src.rpm and updated libvirt ( next preview) will become available via F13 rawhide , F12 & F13 rawhide would be ready to go in text mode as 3.5 Xen Hosts with virt-install&virt-manager available via VNC connections.? Why wait until Upstream merge ? Boris --- On Sun, 9/6/09, Pasi K?rkk?inen wrote: From: Pasi K?rkk?inen Subject: Re: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 To: "Mr. Teo En Ming (Zhang Enming)" Cc: bderzhavets at yahoo.com, "Xen-devel" , "Jeremy Fitzhardinge" , fedora-xen at redhat.com Date: Sunday, September 6, 2009, 2:37 PM On Mon, Sep 07, 2009 at 01:10:14AM +0800, Mr. Teo En Ming (Zhang Enming) wrote: > On 09/07/2009 01:04 AM, Boris Derzhavets wrote: > >I believe, that some set of CSs from Xen 3.5 has to be included as > >patches into > >xen-3.4.1-3.src.rpm, in case if it causes by 3.4.1 Hypervisor. > >Otherwise? , F12 release in November won't have suitable Dom0 kernel > >again. > >I would guess 2.6.31-rc6 at best. > > > >Boris. > > > >--- On *Sun, 9/6/09, Boris Derzhavets //* wrote: > > > > > >? ? From: Boris Derzhavets > >? ? Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 > >? ? To: "Jeremy Fitzhardinge" > >? ? Cc: "Xen-devel" , fedora-xen at redhat.com > >? ? Date: Sunday, September 6, 2009, 12:56 PM > > > >? ? 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 [] 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, > > > > > > > >??? > I thought Fedora will no longer have dom 0 kernel? > http://fedoraproject.org/wiki/Features/XenPvopsDom0 "Dom0 status: awaiting upstream kernel support" -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel at lists.xensource.com http://lists.xensource.com/xen-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From bderzhavets at yahoo.com Mon Sep 7 06:33:09 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Sun, 6 Sep 2009 23:33:09 -0700 (PDT) Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 In-Reply-To: <169290.4400.qm@web56106.mail.re3.yahoo.com> Message-ID: <729489.35024.qm@web56103.mail.re3.yahoo.com> In other words,? a kind of 3.5 iteration :- http://bderzhavets.wordpress.com/2009/09/05/setup-xen-3-4-1-libvirt-on-top-f12-alpha-rawhide/ Boris. --- On Mon, 9/7/09, Boris Derzhavets wrote: From: Boris Derzhavets Subject: Re: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 To: "Pasi K?rkk?inen" Cc: "Jeremy Fitzhardinge" , "Xen-devel" , fedora-xen at redhat.com Date: Monday, September 7, 2009, 12:49 AM As far as Xen 3.5 tarball will be officially released kernel supporting Dom0 should be JF's pvops kernel. When? xen-3.5.0-X.src.rpm and updated libvirt ( next preview) will become available via F13 rawhide , F12 & F13 rawhide would be ready to go in text mode as 3.5 Xen Hosts with virt-install&virt-manager available via VNC connections.? Why wait until Upstream merge ? Boris --- On Sun, 9/6/09, Pasi K?rkk?inen wrote: From: Pasi K?rkk?inen Subject: Re: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 To: "Mr. Teo En Ming (Zhang Enming)" Cc: bderzhavets at yahoo.com, "Xen-devel" , "Jeremy Fitzhardinge" , fedora-xen at redhat.com Date: Sunday, September 6, 2009, 2:37 PM On Mon, Sep 07, 2009 at 01:10:14AM +0800, Mr. Teo En Ming (Zhang Enming) wrote: > On 09/07/2009 01:04 AM, Boris Derzhavets wrote: > >I believe, that some set of CSs from Xen 3.5 has to be included as > >patches into > >xen-3.4.1-3.src.rpm, in case if it causes by 3.4.1 Hypervisor. > >Otherwise? , F12 release in November won't have suitable Dom0 kernel > >again. > >I would guess 2.6.31-rc6 at best. > > > >Boris. > > > >--- On *Sun, 9/6/09, Boris Derzhavets //* wrote: > > > > > >? ? From: Boris Derzhavets > >? ? Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 > >? ? To: "Jeremy Fitzhardinge" > >? ? Cc: "Xen-devel" , fedora-xen at redhat.com > >? ? Date: Sunday, September 6, 2009, 12:56 PM > > > >? ? 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 [] 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, > > > > > > > >??? > I thought Fedora will no longer have dom 0 kernel? > http://fedoraproject.org/wiki/Features/XenPvopsDom0 "Dom0 status: awaiting upstream kernel support" -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel at lists.xensource.com http://lists.xensource.com/xen-devel -----Inline Attachment Follows----- _______________________________________________ Xen-devel mailing list Xen-devel at lists.xensource.com http://lists.xensource.com/xen-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From pasik at iki.fi Mon Sep 7 06:57:59 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 7 Sep 2009 09:57:59 +0300 Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 In-Reply-To: <169290.4400.qm@web56106.mail.re3.yahoo.com> References: <20090906183745.GY31123@reaktio.net> <169290.4400.qm@web56106.mail.re3.yahoo.com> Message-ID: <20090907065759.GZ31123@reaktio.net> On Sun, Sep 06, 2009 at 09:49:41PM -0700, Boris Derzhavets wrote: > As far as Xen 3.5 tarball will be officially released kernel supporting Dom0 should be > JF's pvops kernel. When? xen-3.5.0-X.src.rpm and updated libvirt ( next preview) > will become available via F13 rawhide , F12 & F13 rawhide would be ready to go > in text mode as 3.5 Xen Hosts with virt-install&virt-manager available via VNC > connections.? Why wait until Upstream merge ? > Uhm.. sorry I'm a bit confused. If I understood correctly you have a call trace on your pv_ops dom0 kernel? Does that only happen with Xen 3.4.1 or what's the problem? -- Pasi > Boris > > --- On Sun, 9/6/09, Pasi K?rkk?inen wrote: > > From: Pasi K?rkk?inen > Subject: Re: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 > To: "Mr. Teo En Ming (Zhang Enming)" > Cc: bderzhavets at yahoo.com, "Xen-devel" , "Jeremy Fitzhardinge" , fedora-xen at redhat.com > Date: Sunday, September 6, 2009, 2:37 PM > > On Mon, Sep 07, 2009 at 01:10:14AM +0800, Mr. Teo En Ming (Zhang Enming) wrote: > > On 09/07/2009 01:04 AM, Boris Derzhavets wrote: > > >I believe, that some set of CSs from Xen 3.5 has to be included as > > >patches into > > >xen-3.4.1-3.src.rpm, in case if it causes by 3.4.1 Hypervisor. > > >Otherwise? , F12 release in November won't have suitable Dom0 kernel > > >again. > > >I would guess 2.6.31-rc6 at best. > > > > > >Boris. > > > > > >--- On *Sun, 9/6/09, Boris Derzhavets //* wrote: > > > > > > > > >? ? From: Boris Derzhavets > > >? ? Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 > > >? ? To: "Jeremy Fitzhardinge" > > >? ? Cc: "Xen-devel" , fedora-xen at redhat.com > > >? ? Date: Sunday, September 6, 2009, 12:56 PM > > > > > >? ? 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 [] 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, > > > > > > > > > > > >??? > > I thought Fedora will no longer have dom 0 kernel? > > > > http://fedoraproject.org/wiki/Features/XenPvopsDom0 > > "Dom0 status: awaiting upstream kernel support" > > -- Pasi > > > _______________________________________________ > Xen-devel mailing list > Xen-devel at lists.xensource.com > http://lists.xensource.com/xen-devel > > > > From bderzhavets at yahoo.com Mon Sep 7 07:25:33 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Mon, 7 Sep 2009 00:25:33 -0700 (PDT) Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 In-Reply-To: <20090907065759.GZ31123@reaktio.net> Message-ID: <294559.47236.qm@web56106.mail.re3.yahoo.com> Pasi, I was trying to load the most recent 2.6.31-rc8 under Xen 3.4.1 ( via src.rpm) on F12 rawhide and got stack trace. Jeremy is saying that rc8 works ok under Xen Unstable. But, Libvirt 0.7.0-6 would obviously have dependencies? on xen-3.4.1 packages. If i will port Xen 3.5 directly to F12 (F11) it might work with rc8, however Libvirt 0.7.0-6 will be most probably lost again. Libvirt 0.7.0-6 has been built for 3.4.1 Hypervisor ( in my understanding) . That's why i wrote if Xen 3.5 can load rc8, the easiest way to fix issue is to backport required Xen 3.5 CSs to xen-3.4.1-X(?).src.rpm? and get it resolved before F12 November's release. Boris --- On Mon, 9/7/09, Pasi K?rkk?inen wrote: From: Pasi K?rkk?inen Subject: Re: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 To: "Boris Derzhavets" Cc: "Xen-devel" , fedora-xen at redhat.com Date: Monday, September 7, 2009, 2:57 AM On Sun, Sep 06, 2009 at 09:49:41PM -0700, Boris Derzhavets wrote: > As far as Xen 3.5 tarball will be officially released? kernel supporting Dom0 should be > JF's pvops kernel. When? xen-3.5.0-X.src.rpm and updated libvirt ( next preview) > will become available via F13 rawhide , F12 & F13 rawhide would be ready to go > in text mode as 3.5 Xen Hosts with virt-install&virt-manager available via VNC > connections.? Why wait until Upstream merge ? > Uhm.. sorry I'm a bit confused. If I understood correctly you have a call trace on your pv_ops dom0 kernel? Does that only happen with Xen 3.4.1 or what's the problem? -- Pasi > Boris > > --- On Sun, 9/6/09, Pasi K?rkk?inen wrote: > > From: Pasi K?rkk?inen > Subject: Re: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 > To: "Mr. Teo En Ming (Zhang Enming)" > Cc: bderzhavets at yahoo.com, "Xen-devel" , "Jeremy Fitzhardinge" , fedora-xen at redhat.com > Date: Sunday, September 6, 2009, 2:37 PM > > On Mon, Sep 07, 2009 at 01:10:14AM +0800, Mr. Teo En Ming (Zhang Enming) wrote: > > On 09/07/2009 01:04 AM, Boris Derzhavets wrote: > > >I believe, that some set of CSs from Xen 3.5 has to be included as > > >patches into > > >xen-3.4.1-3.src.rpm, in case if it causes by 3.4.1 Hypervisor. > > >Otherwise? , F12 release in November won't have suitable Dom0 kernel > > >again. > > >I would guess 2.6.31-rc6 at best. > > > > > >Boris. > > > > > >--- On *Sun, 9/6/09, Boris Derzhavets //* wrote: > > > > > > > > >? ? From: Boris Derzhavets > > >? ? Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 > > >? ? To: "Jeremy Fitzhardinge" > > >? ? Cc: "Xen-devel" , fedora-xen at redhat.com > > >? ? Date: Sunday, September 6, 2009, 12:56 PM > > > > > >? ? 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 [] 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, > > > > > > > > > > > >??? > > I thought Fedora will no longer have dom 0 kernel? > > > > http://fedoraproject.org/wiki/Features/XenPvopsDom0 > > "Dom0 status: awaiting upstream kernel support" > > -- Pasi > > > _______________________________________________ > Xen-devel mailing list > Xen-devel at lists.xensource.com > http://lists.xensource.com/xen-devel > > > >? ? ??? _______________________________________________ Xen-devel mailing list Xen-devel at lists.xensource.com http://lists.xensource.com/xen-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From bderzhavets at yahoo.com Mon Sep 7 07:47:42 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Mon, 7 Sep 2009 00:47:42 -0700 (PDT) Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 In-Reply-To: <294559.47236.qm@web56106.mail.re3.yahoo.com> Message-ID: <240589.70300.qm@web56103.mail.re3.yahoo.com> I lost one thing. After backport xen-libs-3.4.1 would be updated, hence libvirt might require another changes as well. B. --- On Mon, 9/7/09, Boris Derzhavets wrote: From: Boris Derzhavets Subject: Re: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 To: "Pasi K?rkk?inen" Cc: "Xen-devel" , fedora-xen at redhat.com Date: Monday, September 7, 2009, 3:25 AM Pasi, I was trying to load the most recent 2.6.31-rc8 under Xen 3.4.1 ( via src.rpm) on F12 rawhide and got stack trace. Jeremy is saying that rc8 works ok under Xen Unstable. But, Libvirt 0.7.0-6 would obviously have dependencies? on xen-3.4.1 packages. If i will port Xen 3.5 directly to F12 (F11) it might work with rc8, however Libvirt 0.7.0-6 will be most probably lost again. Libvirt 0.7.0-6 has been built for 3.4.1 Hypervisor ( in my understanding) . That's why i wrote if Xen 3.5 can load rc8, the easiest way to fix issue is to backport required Xen 3.5 CSs to xen-3.4.1-X(?).src.rpm? and get it resolved before F12 November's release. Boris --- On Mon, 9/7/09, Pasi K?rkk?inen wrote: From: Pasi K?rkk?inen Subject: Re: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 To: "Boris Derzhavets" Cc: "Xen-devel" , fedora-xen at redhat.com Date: Monday, September 7, 2009, 2:57 AM On Sun, Sep 06, 2009 at 09:49:41PM -0700, Boris Derzhavets wrote: > As far as Xen 3.5 tarball will be officially released? kernel supporting Dom0 should be > JF's pvops kernel. When? xen-3.5.0-X.src.rpm and updated libvirt ( next preview) > will become available via F13 rawhide , F12 & F13 rawhide would be ready to go > in text mode as 3.5 Xen Hosts with virt-install&virt-manager available via VNC > connections.? Why wait until Upstream merge ? > Uhm.. sorry I'm a bit confused. If I understood correctly you have a call trace on your pv_ops dom0 kernel? Does that only happen with Xen 3.4.1 or what's the problem? -- Pasi > Boris > > --- On Sun, 9/6/09, Pasi K?rkk?inen wrote: > > From: Pasi K?rkk?inen > Subject: Re: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 > To: "Mr. Teo En Ming (Zhang Enming)" > Cc: bderzhavets at yahoo.com, "Xen-devel" , "Jeremy Fitzhardinge" , fedora-xen at redhat.com > Date: Sunday, September 6, 2009, 2:37 PM > > On Mon, Sep 07, 2009 at 01:10:14AM +0800, Mr. Teo En Ming (Zhang Enming) wrote: > > On 09/07/2009 01:04 AM, Boris Derzhavets wrote: > > >I believe, that some set of CSs from Xen 3.5 has to be included as > > >patches into > > >xen-3.4.1-3.src.rpm, in case if it causes by 3.4.1 Hypervisor. > > >Otherwise? , F12 release in November won't have suitable Dom0 kernel > > >again. > > >I would guess 2.6.31-rc6 at best. > > > > > >Boris. > > > > > >--- On *Sun, 9/6/09, Boris Derzhavets //* wrote: > > > > > > > > >? ? From: Boris Derzhavets > > >? ? Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 > > >? ? To: "Jeremy Fitzhardinge" > > >? ? Cc: "Xen-devel" , fedora-xen at redhat.com > > >? ? Date: Sunday, September 6, 2009, 12:56 PM > > > > > >? ? 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 [] 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, > > > > > > > > > > > >??? > > I thought Fedora will no longer have dom 0 kernel? > > > > http://fedoraproject.org/wiki/Features/XenPvopsDom0 > > "Dom0 status: awaiting upstream kernel support" > > -- Pasi > > > _______________________________________________ > Xen-devel mailing list > Xen-devel at lists.xensource.com > http://lists.xensource.com/xen-devel > > > >? ? ??? _______________________________________________ Xen-devel mailing list Xen-devel at lists.xensource.com http://lists.xensource.com/xen-devel -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: From bderzhavets at yahoo.com Sun Sep 6 15:44:19 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Sun, 6 Sep 2009 08:44:19 -0700 (PDT) Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <4AA3D0AE.2080009@rwth-aachen.de> Message-ID: <28021.87728.qm@web56104.mail.re3.yahoo.com> ? I tried to build and load on F12 rawhide with the most recent gcc,glibc and kernel (fedoras). So, xen was installed via xen-3.4.1-3.src.rpm along with libvirt ( via rawhide again). Please, let me know your environment for successful build and load rc8 under? Xen 3.5. Boris. BTW Please,be advised :- ********** Quote:- ********** >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 >+#include >struct device; >struct dma_attrs; ? Now kernel gets built, but still fails to load under either Xen 3.5 or Xen 3.4.1. ? Stack traces differ on C2D E8400 (Xen 3.4.1)? and Q9550 (Xen 3.5 unstable )boxes. ? On the last box :- ?do_one_initcall + 0x37/0x1a0 ?kernel_init + 0x164/0x1ba ?child_rip + 0xa/0x20 ?? int_ret_from_sys_call 0x7/0x16 ?? retint_restore_arg + 0x5/0x6 ?? child_rip 0x0/0x20 ?Two last commands are the same on the first box. Previous differ. Boris. P.S. I cannot buy or order 20 m of NUL modem cable. ?????? Just 2.5 m . That's all --- On Sat, 9/5/09, Jeremy Fitzhardinge wrote: From: Jeremy Fitzhardinge Subject: [Xen-devel] Re: Errors when build 2.6.31-rc8 To: "Boris Derzhavets" Cc: "Xen-devel" 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 +#include struct device; struct dma_attrs; ??? J --- On Sun, 9/6/09, Mark Schloesser wrote: From: Mark Schloesser Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Boris Derzhavets" Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com Date: Sunday, September 6, 2009, 11:09 AM Boris, actually I used your config. The same config as I used for -rc6 build. Works just fine for me - but I did not try booting with 3.4.1, only with xen-unstable. Mark Boris Derzhavets wrote: > Mark, > Could you share your .config for JF's 2.6.31-rc8 which loads under Xen Unstable. > Looks like i miss some point tuning kernel. > > Thanks. > Boris. > > --- On Fri, 9/4/09, Boris Derzhavets wrote: > > From: Boris Derzhavets > Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: fedora-xen at redhat.com, "Mark Schloesser" > Cc: xen-devel at lists.xensource.com > Date: Friday, September 4, 2009, 2:02 PM > > I did "git pull" , built 2.6.31-c8 kernel with Xen Dom0 support. > However, attempt to load kernel under Xen 3.4.1 drops > into stack trace and hangs on both F11 and Ubuntu 9.10. > Old 2.6.31-rc6's .config file has been used without any changes. > I can't set up serial console in meantime. > > Boris > > --- On Fri, 9/4/09, Mark Schloesser wrote: > > From: Mark Schloesser > Subject: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: fedora-xen at redhat.com > Date: Friday, September 4, 2009, 10:26 AM > > 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 > > > -----Inline Attachment Follows----- > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > >? ? ??? > -----Inline Attachment Follows----- > > _______________________________________________ > Xen-devel mailing list > Xen-devel at lists.xensource.com > http://lists.xensource.com/xen-devel > > > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-devel mailing list > Xen-devel at lists.xensource.com > http://lists.xensource.com/xen-devel -----Inline Attachment Follows----- _______________________________________________ Xen-devel mailing list Xen-devel at lists.xensource.com http://lists.xensource.com/xen-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From bderzhavets at yahoo.com Sun Sep 6 15:49:51 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Sun, 6 Sep 2009 08:49:51 -0700 (PDT) Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <4AA3D0AE.2080009@rwth-aachen.de> Message-ID: <324257.12640.qm@web56105.mail.re3.yahoo.com> ? I tried to build and load on F12 rawhide with the most recent gcc,glibc and kernel (fedoras). So, xen was installed via xen-3.4.1-3.src.rpm along with libvirt ( via rawhide again). Please, let me know your environment for successful build and load rc8 under? Xen 3.5. Boris. BTW Please,be advised :- ********** Quote:- ********** >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 >+#include >struct device; >struct dma_attrs; ? Now kernel gets built, but still fails to load under either Xen 3.5 or Xen 3.4.1. ? Stack traces differ on C2D E8400 (Xen 3.4.1)? and Q9550 (Xen 3.5 unstable )boxes. ? On the last box :- ?do_one_initcall + 0x37/0x1a0 ?kernel_init + 0x164/0x1ba ?child_rip + 0xa/0x20 ?? int_ret_from_sys_call 0x7/0x16 ?? retint_restore_arg + 0x5/0x6 ?? child_rip 0x0/0x20 ?Two last commands are the same on the first box. Previous differ. Boris. P.S. I cannot buy or order 20 m of NUL modem cable. ?????? Just 2.5 m . That's all --- On Sat, 9/5/09, Jeremy Fitzhardinge wrote: From: Jeremy Fitzhardinge Subject: [Xen-devel] Re: Errors when build 2.6.31-rc8 To: "Boris Derzhavets" Cc: "Xen-devel" 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 +#include struct device; struct dma_attrs; ??? J --- On Sun, 9/6/09, Mark Schloesser wrote: From: Mark Schloesser Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Boris Derzhavets" Cc: fedora-xen at redhat.com, xen-devel at lists.xensource.com Date: Sunday, September 6, 2009, 11:09 AM Boris, actually I used your config. The same config as I used for -rc6 build. Works just fine for me - but I did not try booting with 3.4.1, only with xen-unstable. Mark Boris Derzhavets wrote: > Mark, > Could you share your .config for JF's 2.6.31-rc8 which loads under Xen Unstable. > Looks like i miss some point tuning kernel. > > Thanks. > Boris. > > --- On Fri, 9/4/09, Boris Derzhavets wrote: > > From: Boris Derzhavets > Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: fedora-xen at redhat.com, "Mark Schloesser" > Cc: xen-devel at lists.xensource.com > Date: Friday, September 4, 2009, 2:02 PM > > I did "git pull" , built 2.6.31-c8 kernel with Xen Dom0 support. > However, attempt to load kernel under Xen 3.4.1 drops > into stack trace and hangs on both F11 and Ubuntu 9.10. > Old 2.6.31-rc6's .config file has been used without any changes. > I can't set up serial console in meantime. > > Boris > > --- On Fri, 9/4/09, Mark Schloesser wrote: > > From: Mark Schloesser > Subject: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: fedora-xen at redhat.com > Date: Friday, September 4, 2009, 10:26 AM > > 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 > > > -----Inline Attachment Follows----- > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > >? ? ??? > -----Inline Attachment Follows----- > > _______________________________________________ > Xen-devel mailing list > Xen-devel at lists.xensource.com > http://lists.xensource.com/xen-devel > > > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-devel mailing list > Xen-devel at lists.xensource.com > http://lists.xensource.com/xen-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From bderzhavets at yahoo.com Sun Sep 6 16:41:38 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Sun, 6 Sep 2009 09:41:38 -0700 (PDT) Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <4AA3E0A3.8000902@rwth-aachen.de> Message-ID: <468622.27671.qm@web56101.mail.re3.yahoo.com> Thanks. --- On Sun, 9/6/09, Mark Schloesser wrote: From: Mark Schloesser Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Boris Derzhavets" Cc: xen-devel at lists.xensource.com, fedora-xen at 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 Boris Derzhavets wrote: >???I tried to build and load on F12 rawhide with the most recent > gcc,glibc and kernel (fedoras). So, xen was installed via > xen-3.4.1-3.src.rpm along with libvirt ( via rawhide again). Please, > let me know your environment for successful build and load rc8 under > Xen 3.5. > > Boris. > BTW > Please,be advised :- > > ********** > Quote:- > ********** > >> 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 >> +#include >? >? >struct device; >? >struct dma_attrs; > >???Now kernel gets built, but still fails to load under either Xen 3.5 or Xen >? 3.4.1. >???Stack traces differ on C2D E8400 (Xen 3.4.1)? and Q9550 (Xen 3.5 unstable )boxes. >???On the last box :- > >? do_one_initcall + 0x37/0x1a0 >? kernel_init + 0x164/0x1ba >? child_rip + 0xa/0x20 >? ? int_ret_from_sys_call 0x7/0x16 >? ? retint_restore_arg + 0x5/0x6 >? ? child_rip 0x0/0x20 > >? Two last >? commands are the same on the first box. Previous differ. > > Boris. > P.S. I cannot buy or order 20 m of NUL modem cable. >? ? ? ? Just 2.5 m . That's all > > --- On Sat, 9/5/09, Jeremy Fitzhardinge wrote: > > From: Jeremy Fitzhardinge > Subject: [Xen-devel] Re: Errors when build 2.6.31-rc8 > To: "Boris Derzhavets" > Cc: "Xen-devel" > 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 > +#include >? >? struct device; >? struct dma_attrs; > >? ???J > > > --- On Sun, 9/6/09, Mark Schloesser wrote: > > From: Mark Schloesser > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" > Cc: fedora-xen at redhat.com, xen-devel at lists.xensource.com > Date: Sunday, September 6, 2009, 11:09 AM > > Boris, > > actually I used your config. The same config as I used for -rc6 build. > Works just fine for me - but I did not try booting with 3.4.1, only with > xen-unstable. > > Mark > > > Boris Derzhavets wrote: >> Mark, >> Could you share your .config for JF's 2.6.31-rc8 which loads under Xen Unstable. >> Looks like i miss some point tuning kernel. >> >> Thanks. >> Boris. >> >> --- On Fri, 9/4/09, Boris Derzhavets wrote: >> >> From: Boris Derzhavets >> Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable >> To: fedora-xen at redhat.com, "Mark Schloesser" >> Cc: xen-devel at lists.xensource.com >> Date: Friday, September 4, 2009, 2:02 PM >> >> I did "git pull" , built 2.6.31-c8 kernel with Xen Dom0 support. >> However, attempt to load kernel under Xen 3.4.1 drops >> into stack trace and hangs on both F11 and Ubuntu 9.10. >> Old 2.6.31-rc6's .config file has been used without any changes. >> I can't set up serial console in meantime. >> >> Boris >> >> --- On Fri, 9/4/09, Mark Schloesser wrote: >> >> From: Mark Schloesser >> Subject: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable >> To: fedora-xen at redhat.com >> Date: Friday, September 4, 2009, 10:26 AM >> >> 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 >> >> >> -----Inline Attachment Follows----- >> >> -- >> Fedora-xen mailing list >> Fedora-xen at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen >> >> >> >> >> >>? ? ? ? >> -----Inline Attachment Follows----- >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel at lists.xensource.com >> http://lists.xensource.com/xen-devel >> >> >> >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel at lists.xensource.com >> http://lists.xensource.com/xen-devel > > > > >? ? ??? > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-devel mailing list > Xen-devel at lists.xensource.com > http://lists.xensource.com/xen-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From enming.teo at asiasoftsea.net Sun Sep 6 17:10:14 2009 From: enming.teo at asiasoftsea.net (Mr. Teo En Ming (Zhang Enming)) Date: Mon, 07 Sep 2009 01:10:14 +0800 Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 In-Reply-To: <711436.77747.qm@web56103.mail.re3.yahoo.com> References: <711436.77747.qm@web56103.mail.re3.yahoo.com> Message-ID: <4AA3ECF6.5040206@asiasoftsea.net> On 09/07/2009 01:04 AM, Boris Derzhavets wrote: > I believe, that some set of CSs from Xen 3.5 has to be included as > patches into > xen-3.4.1-3.src.rpm, in case if it causes by 3.4.1 Hypervisor. > Otherwise , F12 release in November won't have suitable Dom0 kernel > again. > I would guess 2.6.31-rc6 at best. > > Boris. > > --- On *Sun, 9/6/09, Boris Derzhavets //* wrote: > > > From: Boris Derzhavets > Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 > To: "Jeremy Fitzhardinge" > Cc: "Xen-devel" , fedora-xen at redhat.com > Date: Sunday, September 6, 2009, 12:56 PM > > 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 [] 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, > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-devel mailing list > Xen-devel at lists.xensource.com > http://lists.xensource.com/xen-devel > I thought Fedora will no longer have dom 0 kernel? -- Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering) Technical Support Engineer Information Technology Department Asiasoft Online Pte Ltd Tampines Central 1 #04-01 Tampines Plaza Singapore 529541 Republic of Singapore Company Website: http://www.asiasoft.sg/ Mobile: +65-9648-9798 MSN: teoenming at hotmail.com Alma Maters: Singapore Polytechnic, National University of Singapore -------------- next part -------------- An HTML attachment was scrubbed... URL: From bderzhavets at yahoo.com Mon Sep 7 16:06:38 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Mon, 7 Sep 2009 09:06:38 -0700 (PDT) Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 In-Reply-To: <240589.70300.qm@web56103.mail.re3.yahoo.com> Message-ID: <451955.81720.qm@web56105.mail.re3.yahoo.com> I've got the same stack trace on F11 with the most recent "yum update" under Xen Unstable for 2.6.31-rc8 ( top commit 7c62209cde5b13b81685e79b2f9e3757e293aef1) 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 [] 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 Boris. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bderzhavets at yahoo.com Mon Sep 7 18:18:17 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Mon, 7 Sep 2009 11:18:17 -0700 (PDT) Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <4AA3E0A3.8000902@rwth-aachen.de> Message-ID: <48305.42552.qm@web56102.mail.re3.yahoo.com> 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 wrote: From: Mark Schloesser Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Boris Derzhavets" Cc: xen-devel at lists.xensource.com, fedora-xen at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From pasik at iki.fi Mon Sep 7 21:11:35 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 8 Sep 2009 00:11:35 +0300 Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 / compiles and works OK In-Reply-To: <294559.47236.qm@web56106.mail.re3.yahoo.com> References: <20090907065759.GZ31123@reaktio.net> <294559.47236.qm@web56106.mail.re3.yahoo.com> Message-ID: <20090907211135.GA31123@reaktio.net> On Mon, Sep 07, 2009 at 12:25:33AM -0700, Boris Derzhavets wrote: > Pasi, > > I was trying to load the most recent 2.6.31-rc8 under Xen 3.4.1 ( via src.rpm) on F12 > rawhide and got stack trace. Jeremy is saying that rc8 works ok under Xen Unstable. > But, Libvirt 0.7.0-6 would obviously have dependencies? on xen-3.4.1 packages. > If i will port Xen 3.5 directly to F12 (F11) it might work with rc8, however Libvirt 0.7.0-6 will be most probably lost again. Libvirt 0.7.0-6 has been built for 3.4.1 Hypervisor ( in my understanding) . That's why i wrote if Xen 3.5 can load rc8, the easiest way to fix > issue is to backport required Xen 3.5 CSs to xen-3.4.1-X(?).src.rpm? and get it resolved before F12 November's release. > I just compiled latest 2.6.31-rc8 pv_ops dom0 kernel (commit 7c62209cde5b13b81685e79b2f9e3757e293aef1) and it works for me. I'm running with xen-3.4.1-3 on Fedora 11 (x86 32bit PAE). .config for my working kernel: http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.31-rc8-rebaster-master-no-highpte -- Pasi > Boris > > --- On Mon, 9/7/09, Pasi K?rkk?inen wrote: > > From: Pasi K?rkk?inen > Subject: Re: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 > To: "Boris Derzhavets" > Cc: "Xen-devel" , fedora-xen at redhat.com > Date: Monday, September 7, 2009, 2:57 AM > > On Sun, Sep 06, 2009 at 09:49:41PM -0700, Boris Derzhavets wrote: > > As far as Xen 3.5 tarball will be officially released? kernel supporting Dom0 should be > > JF's pvops kernel. When? xen-3.5.0-X.src.rpm and updated libvirt ( next preview) > > will become available via F13 rawhide , F12 & F13 rawhide would be ready to go > > in text mode as 3.5 Xen Hosts with virt-install&virt-manager available via VNC > > connections.? Why wait until Upstream merge ? > > > > Uhm.. sorry I'm a bit confused. If I understood correctly you have a > call trace on your pv_ops dom0 kernel? > > Does that only happen with Xen 3.4.1 or what's the problem? > > -- Pasi > > > Boris > > > > --- On Sun, 9/6/09, Pasi K?rkk?inen wrote: > > > > From: Pasi K?rkk?inen > > Subject: Re: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 > > To: "Mr. Teo En Ming (Zhang Enming)" > > Cc: bderzhavets at yahoo.com, "Xen-devel" , "Jeremy Fitzhardinge" , fedora-xen at redhat.com > > Date: Sunday, September 6, 2009, 2:37 PM > > > > On Mon, Sep 07, 2009 at 01:10:14AM +0800, Mr. Teo En Ming (Zhang Enming) wrote: > > > On 09/07/2009 01:04 AM, Boris Derzhavets wrote: > > > >I believe, that some set of CSs from Xen 3.5 has to be included as > > > >patches into > > > >xen-3.4.1-3.src.rpm, in case if it causes by 3.4.1 Hypervisor. > > > >Otherwise? , F12 release in November won't have suitable Dom0 kernel > > > >again. > > > >I would guess 2.6.31-rc6 at best. > > > > > > > >Boris. > > > > > > > >--- On *Sun, 9/6/09, Boris Derzhavets //* wrote: > > > > > > > > > > > >? ? From: Boris Derzhavets > > > >? ? Subject: [Fedora-xen] Re: [Xen-devel] Re: Errors when build 2.6.31-rc8 > > > >? ? To: "Jeremy Fitzhardinge" > > > >? ? Cc: "Xen-devel" , fedora-xen at redhat.com > > > >? ? Date: Sunday, September 6, 2009, 12:56 PM > > > > > > > >? ? 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 [] 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, > > > > > > > > > > > > > > > >??? > > > I thought Fedora will no longer have dom 0 kernel? > > > > > > > http://fedoraproject.org/wiki/Features/XenPvopsDom0 > > > > "Dom0 status: awaiting upstream kernel support" > > > > -- Pasi > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel at lists.xensource.com > > http://lists.xensource.com/xen-devel > > > > > > > >? ? ??? > > _______________________________________________ > Xen-devel mailing list > Xen-devel at lists.xensource.com > http://lists.xensource.com/xen-devel > > > > From mark.schloesser at rwth-aachen.de Tue Sep 8 12:13:06 2009 From: mark.schloesser at rwth-aachen.de (Mark Schloesser) Date: Tue, 08 Sep 2009 14:13:06 +0200 Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <48305.42552.qm@web56102.mail.re3.yahoo.com> References: <48305.42552.qm@web56102.mail.re3.yahoo.com> Message-ID: <4AA64A52.5010404@rwth-aachen.de> Top commit in my checkout is: commit 3b316bf67dcbe550e648703475e811fc0cedc705 Merge: 226206a 27a3a52 Author: Jeremy Fitzhardinge 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 wrote: > > From: Mark Schloesser > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" > Cc: xen-devel at lists.xensource.com, fedora-xen at 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 > > > > > > > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 260 bytes Desc: OpenPGP digital signature URL: From bderzhavets at yahoo.com Tue Sep 8 13:31:29 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Tue, 8 Sep 2009 06:31:29 -0700 (PDT) Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable Message-ID: <152900.71873.qm@web56101.mail.re3.yahoo.com> 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 wrote: From: Mark Schloesser Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Boris Derzhavets" Cc: fedora-xen at redhat.com Date: Tuesday, September 8, 2009, 8:13 AM Top commit in my checkout is: commit 3b316bf67dcbe550e648703475e811fc0cedc705 Merge: 226206a 27a3a52 Author: Jeremy Fitzhardinge 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 wrote: > > From: Mark Schloesser > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" > Cc: xen-devel at lists.xensource.com, fedora-xen at 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 > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: dmesg.log.gz Type: application/x-gzip Size: 11693 bytes Desc: not available URL: From bderzhavets at yahoo.com Tue Sep 8 15:20:54 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Tue, 8 Sep 2009 08:20:54 -0700 (PDT) Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <152900.71873.qm@web56101.mail.re3.yahoo.com> Message-ID: <392716.32538.qm@web56103.mail.re3.yahoo.com> That's a working grub entry : 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 ? 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 B. --- On Tue, 9/8/09, Boris Derzhavets wrote: From: Boris Derzhavets Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Mark Schloesser" Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com Date: Tuesday, September 8, 2009, 9:31 AM 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 wrote: From: Mark Schloesser Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Boris Derzhavets" Cc: fedora-xen at redhat.com Date: Tuesday, September 8, 2009, 8:13 AM Top commit in my checkout is: commit 3b316bf67dcbe550e648703475e811fc0cedc705 Merge: 226206a 27a3a52 Author: Jeremy Fitzhardinge 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 wrote: > > From: Mark Schloesser > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" > Cc: xen-devel at lists.xensource.com, fedora-xen at 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 > > > > > > > -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: From pasik at iki.fi Tue Sep 8 15:26:05 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 8 Sep 2009 18:26:05 +0300 Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <152900.71873.qm@web56101.mail.re3.yahoo.com> References: <152900.71873.qm@web56101.mail.re3.yahoo.com> Message-ID: <20090908152605.GE31123@reaktio.net> On Tue, Sep 08, 2009 at 06:31:29AM -0700, Boris Derzhavets wrote: > > 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 > dunno if it makes any difference, but you shouldn't have com1= and console=com1 stuff here if you use it _without_ serial console.. My grub.conf with VGA text console: title Fedora Xen pv_ops dom0-test (2.6.31-rc8) root (hd0,0) kernel /xen.gz dom0_mem=1024M loglvl=all guest_loglvl=all module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_dom0test-lv01 module /initrd-2.6.31-rc8.img -- Pasi > Usual Grub entry drops console to stack trace. > Dmesg output is attached. > > Boris. > --- On Tue, 9/8/09, Mark Schloesser wrote: > > From: Mark Schloesser > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" > Cc: fedora-xen at redhat.com > Date: Tuesday, September 8, 2009, 8:13 AM > > Top commit in my checkout is: > > commit 3b316bf67dcbe550e648703475e811fc0cedc705 > Merge: 226206a 27a3a52 > Author: Jeremy Fitzhardinge > 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 wrote: > > > > From: Mark Schloesser > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Boris Derzhavets" > > Cc: xen-devel at lists.xensource.com, fedora-xen at 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 > > > > > > > > > > > > > > > > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel at lists.xensource.com > http://lists.xensource.com/xen-devel From bderzhavets at yahoo.com Tue Sep 8 15:45:29 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Tue, 8 Sep 2009 08:45:29 -0700 (PDT) Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <392716.32538.qm@web56103.mail.re3.yahoo.com> Message-ID: <793929.48784.qm@web56101.mail.re3.yahoo.com> Finally, title Xen 3.4.1 Fedora 12? (2.6.31-rc8 ) (/dev/sdb1) root (hd1,0) kernel /xen-3.4.1.gz dom0_mem=1024M module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 module /initrd-2.6.31-rc8.img I have to specify dom0_mem, otherwise stack trace. Boris. --- On Tue, 9/8/09, Boris Derzhavets wrote: From: Boris Derzhavets Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Mark Schloesser" Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com Date: Tuesday, September 8, 2009, 11:20 AM That's a working grub entry : 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 ? 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 B. --- On Tue, 9/8/09, Boris Derzhavets wrote: From: Boris Derzhavets Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Mark Schloesser" Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com Date: Tuesday, September 8, 2009, 9:31 AM 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 wrote: From: Mark Schloesser Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Boris Derzhavets" Cc: fedora-xen at redhat.com Date: Tuesday, September 8, 2009, 8:13 AM Top commit in my checkout is: commit 3b316bf67dcbe550e648703475e811fc0cedc705 Merge: 226206a 27a3a52 Author: Jeremy Fitzhardinge 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 wrote: > > From: Mark Schloesser > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" > Cc: xen-devel at lists.xensource.com, fedora-xen at 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 > > > > > > > -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: From bderzhavets at yahoo.com Tue Sep 8 15:47:42 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Tue, 8 Sep 2009 08:47:42 -0700 (PDT) Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <20090908152605.GE31123@reaktio.net> Message-ID: <458963.58880.qm@web56105.mail.re3.yahoo.com> I've just understood. I cannot remove dom0-mem only. Thanks Boris --- On Tue, 9/8/09, Pasi K?rkk?inen wrote: From: Pasi K?rkk?inen Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Boris Derzhavets" Cc: "Mark Schloesser" , xen-devel at lists.xensource.com, fedora-xen at redhat.com Date: Tuesday, September 8, 2009, 11:26 AM On Tue, Sep 08, 2009 at 06:31:29AM -0700, Boris Derzhavets wrote: > > 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 > dunno if it makes any difference, but you shouldn't have com1= and console=com1 stuff here if you use it _without_ serial console.. My grub.conf with VGA text console: title Fedora Xen pv_ops dom0-test (2.6.31-rc8) ? ? ? ? root (hd0,0) ? ? ? ? kernel /xen.gz dom0_mem=1024M loglvl=all guest_loglvl=all ? ? ? ? module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_dom0test-lv01 ? ? ? ? module /initrd-2.6.31-rc8.img -- Pasi > Usual Grub entry drops console to stack trace. > Dmesg output is attached. > > Boris. > --- On Tue, 9/8/09, Mark Schloesser wrote: > > From: Mark Schloesser > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" > Cc: fedora-xen at redhat.com > Date: Tuesday, September 8, 2009, 8:13 AM > > Top commit in my checkout is: > > commit 3b316bf67dcbe550e648703475e811fc0cedc705 > Merge: 226206a 27a3a52 > Author: Jeremy Fitzhardinge > 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 wrote: > > > > From: Mark Schloesser > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Boris Derzhavets" > > Cc: xen-devel at lists.xensource.com, fedora-xen at 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 > > > > > > > > > > > > > > > > > > >? ? ??? > _______________________________________________ > Xen-devel mailing list > Xen-devel at lists.xensource.com > http://lists.xensource.com/xen-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From pasik at iki.fi Tue Sep 8 16:17:04 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 8 Sep 2009 19:17:04 +0300 Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <793929.48784.qm@web56101.mail.re3.yahoo.com> References: <392716.32538.qm@web56103.mail.re3.yahoo.com> <793929.48784.qm@web56101.mail.re3.yahoo.com> Message-ID: <20090908161704.GF31123@reaktio.net> On Tue, Sep 08, 2009 at 08:45:29AM -0700, Boris Derzhavets wrote: > Finally, > > title Xen 3.4.1 Fedora 12? (2.6.31-rc8 ) (/dev/sdb1) > > root (hd1,0) > > kernel /xen-3.4.1.gz dom0_mem=1024M > > module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 > > module /initrd-2.6.31-rc8.img > > I have to specify dom0_mem, otherwise stack trace. > Hmm... what kind of stack trace you get without dom0_mem specified? -- Pasi > > --- On Tue, 9/8/09, Boris Derzhavets wrote: > > From: Boris Derzhavets > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Mark Schloesser" > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com > Date: Tuesday, September 8, 2009, 11:20 AM > > That's a working grub entry : > > 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 > ? 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 > > B. > > --- On Tue, 9/8/09, Boris Derzhavets wrote: > > From: Boris Derzhavets > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Mark Schloesser" > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com > Date: Tuesday, September 8, 2009, 9:31 > AM > > 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 wrote: > > From: Mark Schloesser > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" > Cc: fedora-xen at redhat.com > Date: Tuesday, September 8, 2009, 8:13 AM > > Top commit in my checkout is: > > commit 3b316bf67dcbe550e648703475e811fc0cedc705 > Merge: 226206a 27a3a52 > Author: Jeremy Fitzhardinge > 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 wrote: > > > > From: Mark Schloesser > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Boris Derzhavets" > > Cc: xen-devel at lists.xensource.com, fedora-xen at 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 > > > > > > > > > > > > > > > > > > > > -----Inline Attachment Follows----- > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > -----Inline Attachment Follows----- > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel at lists.xensource.com > http://lists.xensource.com/xen-devel From bderzhavets at yahoo.com Tue Sep 8 17:38:08 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Tue, 8 Sep 2009 10:38:08 -0700 (PDT) Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <20090908161704.GF31123@reaktio.net> Message-ID: <314900.52971.qm@web56107.mail.re3.yahoo.com> 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 [] 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 --- On Tue, 9/8/09, Pasi K?rkk?inen wrote: From: Pasi K?rkk?inen Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Boris Derzhavets" Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com, "Mark Schloesser" Date: Tuesday, September 8, 2009, 12:17 PM On Tue, Sep 08, 2009 at 08:45:29AM -0700, Boris Derzhavets wrote: > Finally, > > title Xen 3.4.1? Fedora 12? (2.6.31-rc8 ) (/dev/sdb1) > >???root (hd1,0) > >???kernel /xen-3.4.1.gz dom0_mem=1024M > >???module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 > >???module /initrd-2.6.31-rc8.img > > I have to specify dom0_mem, otherwise stack trace. > Hmm... what kind of stack trace you get without dom0_mem specified? -- Pasi > > --- On Tue, 9/8/09, Boris Derzhavets wrote: > > From: Boris Derzhavets > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Mark Schloesser" > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com > Date: Tuesday, September 8, 2009, 11:20 AM > > That's a working grub entry : > > 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 > ? 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 > > B. > > --- On Tue, 9/8/09, Boris Derzhavets wrote: > > From: Boris Derzhavets > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Mark Schloesser" > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com > Date: Tuesday, September 8, 2009, 9:31 >? AM > > 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 wrote: > > From: Mark Schloesser > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" > Cc: fedora-xen at redhat.com > Date: Tuesday, September 8, 2009, 8:13 AM > > Top commit in my checkout is: > > commit 3b316bf67dcbe550e648703475e811fc0cedc705 > Merge: 226206a 27a3a52 > Author: Jeremy Fitzhardinge > 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 wrote: > > > > From: Mark Schloesser > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Boris Derzhavets" > > Cc: xen-devel at lists.xensource.com, fedora-xen at 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 > > > > > > > > > > > > > > > > > > >? ? ??? > -----Inline Attachment Follows----- > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > >? ? ??? > -----Inline Attachment Follows----- > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > >? ? ??? > _______________________________________________ > Xen-devel mailing list > Xen-devel at lists.xensource.com > http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel at lists.xensource.com http://lists.xensource.com/xen-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From pasik at iki.fi Tue Sep 8 17:47:00 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 8 Sep 2009 20:47:00 +0300 Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <314900.52971.qm@web56107.mail.re3.yahoo.com> References: <20090908161704.GF31123@reaktio.net> <314900.52971.qm@web56107.mail.re3.yahoo.com> Message-ID: <20090908174700.GG31123@reaktio.net> On Tue, Sep 08, 2009 at 10:38:08AM -0700, Boris Derzhavets wrote: > Call trace: OK. How much memory you have? Does it happen with dom0_mem=2048M? Does it happen with dom0_mem=4096M? -- Pasi > > > > > > > >? ? 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 [] 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 > > > --- On Tue, 9/8/09, Pasi K?rkk?inen wrote: > > From: Pasi K?rkk?inen > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com, "Mark Schloesser" > Date: Tuesday, September 8, 2009, 12:17 PM > > On Tue, Sep 08, 2009 at 08:45:29AM -0700, Boris Derzhavets wrote: > > Finally, > > > > title Xen 3.4.1? Fedora 12? (2.6.31-rc8 ) (/dev/sdb1) > > > >???root (hd1,0) > > > >???kernel /xen-3.4.1.gz dom0_mem=1024M > > > >???module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 > > > >???module /initrd-2.6.31-rc8.img > > > > I have to specify dom0_mem, otherwise stack trace. > > > > Hmm... what kind of stack trace you get without dom0_mem specified? > > -- Pasi > > > > > --- On Tue, 9/8/09, Boris Derzhavets wrote: > > > > From: Boris Derzhavets > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Mark Schloesser" > > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com > > Date: Tuesday, September 8, 2009, 11:20 AM > > > > That's a working grub entry : > > > > 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 > > ? 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 > > > > B. > > > > --- On Tue, 9/8/09, Boris Derzhavets wrote: > > > > From: Boris Derzhavets > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Mark Schloesser" > > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com > > Date: Tuesday, September 8, 2009, 9:31 > >? AM > > > > 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 wrote: > > > > From: Mark Schloesser > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Boris Derzhavets" > > Cc: fedora-xen at redhat.com > > Date: Tuesday, September 8, 2009, 8:13 AM > > > > Top commit in my checkout is: > > > > commit 3b316bf67dcbe550e648703475e811fc0cedc705 > > Merge: 226206a 27a3a52 > > Author: Jeremy Fitzhardinge > > 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 wrote: > > > > > > From: Mark Schloesser > > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > > To: "Boris Derzhavets" > > > Cc: xen-devel at lists.xensource.com, fedora-xen at 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >? ? ??? > > -----Inline Attachment Follows----- > > > > -- > > Fedora-xen mailing list > > Fedora-xen at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > >? ? ??? > > -----Inline Attachment Follows----- > > > > -- > > Fedora-xen mailing list > > Fedora-xen at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > >? ? ??? > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel at lists.xensource.com > > http://lists.xensource.com/xen-devel > > > _______________________________________________ > Xen-devel mailing list > Xen-devel at lists.xensource.com > http://lists.xensource.com/xen-devel > > > > From bderzhavets at yahoo.com Tue Sep 8 18:13:27 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Tue, 8 Sep 2009 11:13:27 -0700 (PDT) Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <20090908174700.GG31123@reaktio.net> Message-ID: <610592.33358.qm@web56102.mail.re3.yahoo.com> 8 GB Ram. I will check dom0_mem=? Boris. --- On Tue, 9/8/09, Pasi K?rkk?inen wrote: From: Pasi K?rkk?inen Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Boris Derzhavets" Cc: "Mark Schloesser" , xen-devel at lists.xensource.com, fedora-xen at redhat.com Date: Tuesday, September 8, 2009, 1:47 PM On Tue, Sep 08, 2009 at 10:38:08AM -0700, Boris Derzhavets wrote: > Call trace: OK. How much memory you have? Does it happen with dom0_mem=2048M? Does it happen with dom0_mem=4096M? -- Pasi > > > > > > > >? ? 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 [] 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 > > > --- On Tue, 9/8/09, Pasi K?rkk?inen wrote: > > From: Pasi K?rkk?inen > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com, "Mark Schloesser" > Date: Tuesday, September 8, 2009, 12:17 PM > > On Tue, Sep 08, 2009 at 08:45:29AM -0700, Boris Derzhavets wrote: > > Finally, > > > > title Xen 3.4.1? Fedora 12? (2.6.31-rc8 ) (/dev/sdb1) > > > >???root (hd1,0) > > > >???kernel /xen-3.4.1.gz dom0_mem=1024M > > > >???module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 > > > >???module /initrd-2.6.31-rc8.img > > > > I have to specify dom0_mem, otherwise stack trace. > > > > Hmm... what kind of stack trace you get without dom0_mem specified? > > -- Pasi > > > > > --- On Tue, 9/8/09, Boris Derzhavets wrote: > > > > From: Boris Derzhavets > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Mark Schloesser" > > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com > > Date: Tuesday, September 8, 2009, 11:20 AM > > > > That's a working grub entry : > > > > 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 > > ? 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 > > > > B. > > > > --- On Tue, 9/8/09, Boris Derzhavets wrote: > > > > From: Boris Derzhavets > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Mark Schloesser" > > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com > > Date: Tuesday, September 8, 2009, 9:31 > >? AM > > > > 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 wrote: > > > > From: Mark Schloesser > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Boris Derzhavets" > > Cc: fedora-xen at redhat.com > > Date: Tuesday, September 8, 2009, 8:13 AM > > > > Top commit in my checkout is: > > > > commit 3b316bf67dcbe550e648703475e811fc0cedc705 > > Merge: 226206a 27a3a52 > > Author: Jeremy Fitzhardinge > > 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 wrote: > > > > > > From: Mark Schloesser > > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > > To: "Boris Derzhavets" > > > Cc: xen-devel at lists.xensource.com, fedora-xen at 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >? ? ??? > > -----Inline Attachment Follows----- > > > > -- > > Fedora-xen mailing list > > Fedora-xen at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > >? ? ??? > > -----Inline Attachment Follows----- > > > > -- > > Fedora-xen mailing list > > Fedora-xen at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > >? ? ??? > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel at lists.xensource.com > > http://lists.xensource.com/xen-devel > > > _______________________________________________ > Xen-devel mailing list > Xen-devel at lists.xensource.com > http://lists.xensource.com/xen-devel > > > >? ? ??? _______________________________________________ Xen-devel mailing list Xen-devel at lists.xensource.com http://lists.xensource.com/xen-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From bderzhavets at yahoo.com Tue Sep 8 18:46:05 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Tue, 8 Sep 2009 11:46:05 -0700 (PDT) Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <20090908174700.GG31123@reaktio.net> Message-ID: <757502.51447.qm@web56102.mail.re3.yahoo.com> System boots up with dom0_mem=4096M. Boris. --- On Tue, 9/8/09, Pasi K?rkk?inen wrote: From: Pasi K?rkk?inen Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Boris Derzhavets" Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com, "Mark Schloesser" Date: Tuesday, September 8, 2009, 1:47 PM On Tue, Sep 08, 2009 at 10:38:08AM -0700, Boris Derzhavets wrote: > Call trace: OK. How much memory you have? Does it happen with dom0_mem=2048M? Does it happen with dom0_mem=4096M? -- Pasi > > > > > > > >? ? 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 [] 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 > > > --- On Tue, 9/8/09, Pasi K?rkk?inen wrote: > > From: Pasi K?rkk?inen > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com, "Mark Schloesser" > Date: Tuesday, September 8, 2009, 12:17 PM > > On Tue, Sep 08, 2009 at 08:45:29AM -0700, Boris Derzhavets wrote: > > Finally, > > > > title Xen 3.4.1? Fedora 12? (2.6.31-rc8 ) (/dev/sdb1) > > > >???root (hd1,0) > > > >???kernel /xen-3.4.1.gz dom0_mem=1024M > > > >???module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 > > > >???module /initrd-2.6.31-rc8.img > > > > I have to specify dom0_mem, otherwise stack trace. > > > > Hmm... what kind of stack trace you get without dom0_mem specified? > > -- Pasi > > > > > --- On Tue, 9/8/09, Boris Derzhavets wrote: > > > > From: Boris Derzhavets > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Mark Schloesser" > > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com > > Date: Tuesday, September 8, 2009, 11:20 AM > > > > That's a working grub entry : > > > > 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 > > ? 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 > > > > B. > > > > --- On Tue, 9/8/09, Boris Derzhavets wrote: > > > > From: Boris Derzhavets > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Mark Schloesser" > > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com > > Date: Tuesday, September 8, 2009, 9:31 > >? AM > > > > 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 wrote: > > > > From: Mark Schloesser > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Boris Derzhavets" > > Cc: fedora-xen at redhat.com > > Date: Tuesday, September 8, 2009, 8:13 AM > > > > Top commit in my checkout is: > > > > commit 3b316bf67dcbe550e648703475e811fc0cedc705 > > Merge: 226206a 27a3a52 > > Author: Jeremy Fitzhardinge > > 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 wrote: > > > > > > From: Mark Schloesser > > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > > To: "Boris Derzhavets" > > > Cc: xen-devel at lists.xensource.com, fedora-xen at 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >? ? ??? > > -----Inline Attachment Follows----- > > > > -- > > Fedora-xen mailing list > > Fedora-xen at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > >? ? ??? > > -----Inline Attachment Follows----- > > > > -- > > Fedora-xen mailing list > > Fedora-xen at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > >? ? ??? > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel at lists.xensource.com > > http://lists.xensource.com/xen-devel > > > _______________________________________________ > Xen-devel mailing list > Xen-devel at lists.xensource.com > http://lists.xensource.com/xen-devel > > > >? ? ??? -------------- next part -------------- An HTML attachment was scrubbed... URL: From pasik at iki.fi Tue Sep 8 18:49:27 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 8 Sep 2009 21:49:27 +0300 Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <757502.51447.qm@web56102.mail.re3.yahoo.com> References: <20090908174700.GG31123@reaktio.net> <757502.51447.qm@web56102.mail.re3.yahoo.com> Message-ID: <20090908184927.GJ31123@reaktio.net> On Tue, Sep 08, 2009 at 11:46:05AM -0700, Boris Derzhavets wrote: > System boots up with dom0_mem=4096M. > Does it boot up with dom0_mem=4097M ? How about dom0_mem=6144M ? -- Pasi > Boris. > > --- On Tue, 9/8/09, Pasi K?rkk?inen wrote: > > From: Pasi K?rkk?inen > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com, "Mark Schloesser" > Date: Tuesday, September 8, 2009, 1:47 PM > > On Tue, Sep 08, 2009 at 10:38:08AM -0700, Boris Derzhavets wrote: > > Call trace: > > > OK. How much memory you have? > > Does it happen with dom0_mem=2048M? Does it happen with dom0_mem=4096M? > > -- Pasi > > > > > > > > > > >? ? 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 [] 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 > > > > > > --- On Tue, 9/8/09, Pasi K?rkk?inen wrote: > > > > From: Pasi K?rkk?inen > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Boris Derzhavets" > > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com, "Mark Schloesser" > > Date: Tuesday, September 8, 2009, 12:17 PM > > > > On Tue, Sep 08, 2009 at 08:45:29AM -0700, Boris Derzhavets wrote: > > > Finally, > > > > > > title Xen 3.4.1? Fedora 12? (2.6.31-rc8 ) (/dev/sdb1) > > > > > >???root (hd1,0) > > > > > >???kernel /xen-3.4.1.gz dom0_mem=1024M > > > > > >???module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 > > > > > >???module /initrd-2.6.31-rc8.img > > > > > > I have to specify dom0_mem, otherwise stack trace. > > > > > > > Hmm... what kind of stack trace you get without dom0_mem specified? > > > > -- Pasi > > > > > > > > --- On Tue, 9/8/09, Boris Derzhavets wrote: > > > > > > From: Boris Derzhavets > > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > > To: "Mark Schloesser" > > > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com > > > Date: Tuesday, September 8, 2009, 11:20 AM > > > > > > That's a working grub entry : > > > > > > 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 > > > ? 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 > > > > > > B. > > > > > > --- On Tue, 9/8/09, Boris Derzhavets wrote: > > > > > > From: Boris Derzhavets > > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > > To: "Mark Schloesser" > > > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com > > > Date: Tuesday, September 8, 2009, 9:31 > > >? AM > > > > > > 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 wrote: > > > > > > From: Mark Schloesser > > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > > To: "Boris Derzhavets" > > > Cc: fedora-xen at redhat.com > > > Date: Tuesday, September 8, 2009, 8:13 AM > > > > > > Top commit in my checkout is: > > > > > > commit 3b316bf67dcbe550e648703475e811fc0cedc705 > > > Merge: 226206a 27a3a52 > > > Author: Jeremy Fitzhardinge > > > 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 wrote: > > > > > > > > From: Mark Schloesser > > > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > > > To: "Boris Derzhavets" > > > > Cc: xen-devel at lists.xensource.com, fedora-xen at 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >? ? ??? > > > -----Inline Attachment Follows----- > > > > > > -- > > > Fedora-xen mailing list > > > Fedora-xen at redhat.com > > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > > > > > >? ? ??? > > > -----Inline Attachment Follows----- > > > > > > -- > > > Fedora-xen mailing list > > > Fedora-xen at redhat.com > > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > > > > > >? ? ??? > > > _______________________________________________ > > > Xen-devel mailing list > > > Xen-devel at lists.xensource.com > > > http://lists.xensource.com/xen-devel > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel at lists.xensource.com > > http://lists.xensource.com/xen-devel > > > > > > > >? ? ??? > > > > From bderzhavets at yahoo.com Tue Sep 8 19:14:54 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Tue, 8 Sep 2009 12:14:54 -0700 (PDT) Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable In-Reply-To: <20090908184927.GJ31123@reaktio.net> Message-ID: <41057.67598.qm@web56102.mail.re3.yahoo.com> Console drops into the same stack trace in? both cases. Boris. --- On Tue, 9/8/09, Pasi K?rkk?inen wrote: From: Pasi K?rkk?inen Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable To: "Boris Derzhavets" Cc: "Mark Schloesser" , xen-devel at lists.xensource.com, fedora-xen at redhat.com Date: Tuesday, September 8, 2009, 2:49 PM On Tue, Sep 08, 2009 at 11:46:05AM -0700, Boris Derzhavets wrote: > System boots up with dom0_mem=4096M. > Does it boot up with dom0_mem=4097M ? How about dom0_mem=6144M ? -- Pasi > Boris. > > --- On Tue, 9/8/09, Pasi K?rkk?inen wrote: > > From: Pasi K?rkk?inen > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com, "Mark Schloesser" > Date: Tuesday, September 8, 2009, 1:47 PM > > On Tue, Sep 08, 2009 at 10:38:08AM -0700, Boris Derzhavets wrote: > > Call trace: > > > OK. How much memory you have? > > Does it happen with dom0_mem=2048M? Does it happen with dom0_mem=4096M? > > -- Pasi > > > > > > > > > > >? ? 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 [] 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 > > > > > > --- On Tue, 9/8/09, Pasi K?rkk?inen wrote: > > > > From: Pasi K?rkk?inen > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Boris Derzhavets" > > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com, "Mark Schloesser" > > Date: Tuesday, September 8, 2009, 12:17 PM > > > > On Tue, Sep 08, 2009 at 08:45:29AM -0700, Boris Derzhavets wrote: > > > Finally, > > > > > > title Xen 3.4.1? Fedora 12? (2.6.31-rc8 ) (/dev/sdb1) > > > > > >???root (hd1,0) > > > > > >???kernel /xen-3.4.1.gz dom0_mem=1024M > > > > > >???module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 > > > > > >???module /initrd-2.6.31-rc8.img > > > > > > I have to specify dom0_mem, otherwise stack trace. > > > > > > > Hmm... what kind of stack trace you get without dom0_mem specified? > > > > -- Pasi -------------- next part -------------- An HTML attachment was scrubbed... URL: From pasik at iki.fi Tue Sep 8 19:22:46 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 8 Sep 2009 22:22:46 +0300 Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem In-Reply-To: <41057.67598.qm@web56102.mail.re3.yahoo.com> References: <20090908184927.GJ31123@reaktio.net> <41057.67598.qm@web56102.mail.re3.yahoo.com> Message-ID: <20090908192246.GK31123@reaktio.net> 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? 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) ? -- Pasi > > --- On Tue, 9/8/09, Pasi K?rkk?inen wrote: > > From: Pasi K?rkk?inen > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" > Cc: "Mark Schloesser" , xen-devel at lists.xensource.com, fedora-xen at redhat.com > Date: Tuesday, September 8, 2009, 2:49 PM > > On Tue, Sep 08, 2009 at 11:46:05AM -0700, Boris Derzhavets wrote: > > System boots up with dom0_mem=4096M. > > > > Does it boot up with dom0_mem=4097M ? > > How about dom0_mem=6144M ? > > -- Pasi > > > Boris. > > > > --- On Tue, 9/8/09, Pasi K?rkk?inen wrote: > > > > From: Pasi K?rkk?inen > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Boris Derzhavets" > > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com, "Mark Schloesser" > > Date: Tuesday, September 8, 2009, 1:47 PM > > > > On Tue, Sep 08, 2009 at 10:38:08AM -0700, Boris Derzhavets wrote: > > > Call trace: > > > > > > OK. How much memory you have? > > > > Does it happen with dom0_mem=2048M? Does it happen with dom0_mem=4096M? > > > > -- Pasi > > > > > > > > > > > > > >? ? 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 [] 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 > > > > > > > > > --- On Tue, 9/8/09, Pasi K?rkk?inen wrote: > > > > > > From: Pasi K?rkk?inen > > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > > To: "Boris Derzhavets" > > > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com, "Mark Schloesser" > > > Date: Tuesday, September 8, 2009, 12:17 PM > > > > > > On Tue, Sep 08, 2009 at 08:45:29AM -0700, Boris Derzhavets wrote: > > > > Finally, > > > > > > > > title Xen 3.4.1? Fedora 12? (2.6.31-rc8 ) (/dev/sdb1) > > > > > > > >???root (hd1,0) > > > > > > > >???kernel /xen-3.4.1.gz dom0_mem=1024M > > > > > > > >???module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 > > > > > > > >???module /initrd-2.6.31-rc8.img > > > > > > > > I have to specify dom0_mem, otherwise stack trace. > > > > > > > > > > Hmm... what kind of stack trace you get without dom0_mem specified? > > > > > > -- Pasi > > > > > From bderzhavets at yahoo.com Tue Sep 8 19:40:29 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Tue, 8 Sep 2009 12:40:29 -0700 (PDT) Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem In-Reply-To: <20090908192246.GK31123@reaktio.net> Message-ID: <508652.81613.qm@web56102.mail.re3.yahoo.com> 2.6.31-rc6 didn't have any problems under Xen 3.4.1. I didn't test it as vanilla. Boris. --- On Tue, 9/8/09, Pasi K?rkk?inen wrote: From: Pasi K?rkk?inen 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: "Boris Derzhavets" Cc: "Jeremy Fitzhardinge" , xen-devel at lists.xensource.com, fedora-xen at redhat.com Date: Tuesday, September 8, 2009, 3:22 PM 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? 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) ? -- Pasi > > --- On Tue, 9/8/09, Pasi K?rkk?inen wrote: > > From: Pasi K?rkk?inen > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > To: "Boris Derzhavets" > Cc: "Mark Schloesser" , xen-devel at lists.xensource.com, fedora-xen at redhat.com > Date: Tuesday, September 8, 2009, 2:49 PM > > On Tue, Sep 08, 2009 at 11:46:05AM -0700, Boris Derzhavets wrote: > > System boots up with dom0_mem=4096M. > > > > Does it boot up with dom0_mem=4097M ? > > How about dom0_mem=6144M ? > > -- Pasi > > > Boris. > > > > --- On Tue, 9/8/09, Pasi K?rkk?inen wrote: > > > > From: Pasi K?rkk?inen > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > To: "Boris Derzhavets" > > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com, "Mark Schloesser" > > Date: Tuesday, September 8, 2009, 1:47 PM > > > > On Tue, Sep 08, 2009 at 10:38:08AM -0700, Boris Derzhavets wrote: > > > Call trace: > > > > > > OK. How much memory you have? > > > > Does it happen with dom0_mem=2048M? Does it happen with dom0_mem=4096M? > > > > -- Pasi > > > > > > > > > > > > > >? ? 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 [] 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 > > > > > > > > > --- On Tue, 9/8/09, Pasi K?rkk?inen wrote: > > > > > > From: Pasi K?rkk?inen > > > Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable > > > To: "Boris Derzhavets" > > > Cc: xen-devel at lists.xensource.com, fedora-xen at redhat.com, "Mark Schloesser" > > > Date: Tuesday, September 8, 2009, 12:17 PM > > > > > > On Tue, Sep 08, 2009 at 08:45:29AM -0700, Boris Derzhavets wrote: > > > > Finally, > > > > > > > > title Xen 3.4.1? Fedora 12? (2.6.31-rc8 ) (/dev/sdb1) > > > > > > > >???root (hd1,0) > > > > > > > >???kernel /xen-3.4.1.gz dom0_mem=1024M > > > > > > > >???module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 > > > > > > > >???module /initrd-2.6.31-rc8.img > > > > > > > > I have to specify dom0_mem, otherwise stack trace. > > > > > > > > > > Hmm... what kind of stack trace you get without dom0_mem specified? > > > > > > -- Pasi > > > > >? ? ??? _______________________________________________ Xen-devel mailing list Xen-devel at lists.xensource.com http://lists.xensource.com/xen-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From bderzhavets at yahoo.com Tue Sep 8 19:45:08 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Tue, 8 Sep 2009 12:45:08 -0700 (PDT) Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem Message-ID: <631826.43992.qm@web56106.mail.re3.yahoo.com> Dmesg log for rc8 under Xen 3.4.1 on F12 rawhide attached. Boris. --- On Tue, 9/8/09, Konrad Rzeszutek Wilk wrote: From: Konrad Rzeszutek Wilk 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" Cc: "Boris Derzhavets" , xen-devel at lists.xensource.com, "Jeremy Fitzhardinge" , fedora-xen at 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 at lists.xensource.com http://lists.xensource.com/xen-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: dmesg.log.gz Type: application/x-gzip Size: 11693 bytes Desc: not available URL: From bderzhavets at yahoo.com Wed Sep 9 02:53:26 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Tue, 8 Sep 2009 19:53:26 -0700 (PDT) Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem Message-ID: <824671.94929.qm@web56102.mail.re3.yahoo.com> > lspci -vvv would be nice. Attached Boris. --- On Tue, 9/8/09, Konrad Rzeszutek Wilk wrote: From: Konrad Rzeszutek Wilk 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" Cc: "Boris Derzhavets" , "Jeremy Fitzhardinge" , xen-devel at lists.xensource.com, fedora-xen at 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) ? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: lspci.vvv.gz Type: application/x-gzip Size: 4008 bytes Desc: not available URL: From bderzhavets at yahoo.com Wed Sep 9 07:19:20 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Wed, 9 Sep 2009 00:19:20 -0700 (PDT) Subject: [Fedora-xen] 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 Message-ID: <298239.22413.qm@web56105.mail.re3.yahoo.com> 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 wrote: From: Boris Derzhavets 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" , "Konrad Rzeszutek Wilk" Cc: "Jeremy Fitzhardinge" , xen-devel at lists.xensource.com, fedora-xen at 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 wrote: From: Konrad Rzeszutek Wilk 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" Cc: "Boris Derzhavets" , xen-devel at lists.xensource.com, "Jeremy Fitzhardinge" , fedora-xen at 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 at lists.xensource.com http://lists.xensource.com/xen-devel -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: dmesg.1.gz Type: application/x-gzip Size: 15354 bytes Desc: not available URL: From dlbewley at lib.ucdavis.edu Wed Sep 9 16:42:36 2009 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Wed, 09 Sep 2009 09:42:36 -0700 Subject: [Fedora-xen] f11 domU 2.6.30 will not boot on f8 dom0 Message-ID: <1252514556.27535.17.camel@tofu.lib.ucdavis.edu> 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:[] (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 From m.a.young at durham.ac.uk Thu Sep 10 19:33:15 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Thu, 10 Sep 2009 20:33:15 +0100 (BST) Subject: [Fedora-xen] Dom0 kernels In-Reply-To: References: <20090414143618.GH351@redhat.com> Message-ID: An update to 2.6.31 (kernel-2.6.31-1.2.65.xendom0.fc12) is at http://koji.fedoraproject.org/koji/taskinfo?taskID=1668140 and on the repository http://fedorapeople.org/~myoung/dom0/ . This has a few fixes since my previous kernel, though X still doesn't work for me. Michael Young From pasik at iki.fi Sun Sep 13 16:16:29 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 13 Sep 2009 19:16:29 +0300 Subject: [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 In-Reply-To: <20090902130832.GM31123@reaktio.net> References: <4A969BDD.8040506@redhat.com> <20090827151932.GE31123@reaktio.net> <4A9D1BD0.5020105@redhat.com> <20090901134051.GU31123@reaktio.net> <20090901145020.GW31123@reaktio.net> <20090901151721.GA31123@reaktio.net> <4A9E6457.6010206@redhat.com> <20090902124109.GK31123@reaktio.net> <20090902125931.GL31123@reaktio.net> <20090902130832.GM31123@reaktio.net> Message-ID: <20090913161629.GV31123@reaktio.net> 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 - 3.4.1-3 > > - swap bzip2+xz linux kernel compression support patches. > > - backport one more bugfix (videoram option). > > > > * Tue Sep 01 2009 Gerd Hoffmann - 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 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 From bderzhavets at yahoo.com Sun Sep 13 17:01:05 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Sun, 13 Sep 2009 10:01:05 -0700 (PDT) Subject: [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 In-Reply-To: <20090913161629.GV31123@reaktio.net> Message-ID: <319823.13359.qm@web56103.mail.re3.yahoo.com> >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_rawhide It's on 64-bit. Boris. --- On Sun, 9/13/09, Pasi K?rkk?inen wrote: From: Pasi K?rkk?inen 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" Cc: fedora-xen at 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 - 3.4.1-3 > > - swap bzip2+xz linux kernel compression support patches. > > - backport one more bugfix (videoram option). > > > > * Tue Sep 01 2009 Gerd Hoffmann - 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 ? ? 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 at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: From bderzhavets at yahoo.com Sun Sep 13 17:04:53 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Sun, 13 Sep 2009 10:04:53 -0700 (PDT) Subject: [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 Message-ID: <722238.14343.qm@web56103.mail.re3.yahoo.com> >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 wrote: From: Boris Derzhavets 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" , "Pasi K?rkk?inen" Cc: fedora-xen at 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_rawhide It's on 64-bit. Boris. --- On Sun, 9/13/09, Pasi K?rkk?inen wrote: From: Pasi K?rkk?inen 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" Cc: fedora-xen at 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 - 3.4.1-3 > > - swap bzip2+xz linux kernel compression support patches. > > - backport one more bugfix (videoram option). > > > > * Tue Sep 01 2009 Gerd Hoffmann - 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 ? ? 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 at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: From kraxel at redhat.com Mon Sep 14 06:55:23 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Mon, 14 Sep 2009 08:55:23 +0200 Subject: [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 In-Reply-To: <20090913161629.GV31123@reaktio.net> References: <4A969BDD.8040506@redhat.com> <20090827151932.GE31123@reaktio.net> <4A9D1BD0.5020105@redhat.com> <20090901134051.GU31123@reaktio.net> <20090901145020.GW31123@reaktio.net> <20090901151721.GA31123@reaktio.net> <4A9E6457.6010206@redhat.com> <20090902124109.GK31123@reaktio.net> <20090902125931.GL31123@reaktio.net> <20090902130832.GM31123@reaktio.net> <20090913161629.GV31123@reaktio.net> Message-ID: <4AADE8DB.4060406@redhat.com> Hi, > 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? e2fsprogs-devel most likely. cheers, Gerd From pasik at iki.fi Mon Sep 14 08:23:37 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 14 Sep 2009 11:23:37 +0300 Subject: [Fedora-xen] Fedora 12 (rawhide) Xen domU works now, minor console keymap issue? In-Reply-To: <20090906120405.GW31123@reaktio.net> References: <20090906120405.GW31123@reaktio.net> Message-ID: <20090914082337.GB31123@reaktio.net> On Sun, Sep 06, 2009 at 03:04:05PM +0300, Pasi K?rkk?inen wrote: > 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? > .. Or should I ask about this on some other mailinglist? -- Pasi From pasik at iki.fi Mon Sep 14 16:27:45 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 14 Sep 2009 19:27:45 +0300 Subject: [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 In-Reply-To: <4AADE8DB.4060406@redhat.com> References: <4A9D1BD0.5020105@redhat.com> <20090901134051.GU31123@reaktio.net> <20090901145020.GW31123@reaktio.net> <20090901151721.GA31123@reaktio.net> <4A9E6457.6010206@redhat.com> <20090902124109.GK31123@reaktio.net> <20090902125931.GL31123@reaktio.net> <20090902130832.GM31123@reaktio.net> <20090913161629.GV31123@reaktio.net> <4AADE8DB.4060406@redhat.com> Message-ID: <20090914162745.GK31123@reaktio.net> On Mon, Sep 14, 2009 at 08:55:23AM +0200, Gerd Hoffmann wrote: > Hi, > > >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? > > e2fsprogs-devel most likely. > Yeah, it seems I have e2fsprogs-devel installed on my testbox. So that explains the difference. The attached xen.spec patch fixes this issue. Please add it for xen-3.4.1-4. -- Pasi -------------- next part -------------- A non-text attachment was scrubbed... Name: xen_341-3_add_e2fsprogs_for_ext4_support.diff Type: text/x-diff Size: 352 bytes Desc: not available URL: From pasik at iki.fi Mon Sep 14 17:06:34 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 14 Sep 2009 20:06:34 +0300 Subject: [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 In-Reply-To: <20090914162745.GK31123@reaktio.net> References: <20090901134051.GU31123@reaktio.net> <20090901145020.GW31123@reaktio.net> <20090901151721.GA31123@reaktio.net> <4A9E6457.6010206@redhat.com> <20090902124109.GK31123@reaktio.net> <20090902125931.GL31123@reaktio.net> <20090902130832.GM31123@reaktio.net> <20090913161629.GV31123@reaktio.net> <4AADE8DB.4060406@redhat.com> <20090914162745.GK31123@reaktio.net> Message-ID: <20090914170634.GL31123@reaktio.net> On Mon, Sep 14, 2009 at 07:27:45PM +0300, Pasi K?rkk?inen wrote: > On Mon, Sep 14, 2009 at 08:55:23AM +0200, Gerd Hoffmann wrote: > > Hi, > > > > >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? > > > > e2fsprogs-devel most likely. > > > > Yeah, it seems I have e2fsprogs-devel installed on my testbox. So that > explains the difference. > > The attached xen.spec patch fixes this issue. Please add it for xen-3.4.1-4. > .. and it's needed to be able to boot F12 Xen PV guests. They use ext4 /boot as a default. -- Pasi > --- xen.spec.orig 2009-09-14 19:14:57.000000000 +0300 > +++ xen.spec 2009-09-14 19:16:06.000000000 +0300 > @@ -62,6 +62,8 @@ > BuildRequires: gettext > BuildRequires: gnutls-devel > BuildRequires: openssl-devel > +# For pygrub EXT4 support > +BuildRequires: e2fsprogs-devel > # For ioemu PCI passthrough > BuildRequires: pciutils-devel > # modern compressed kernels > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From cjg9411 at rit.edu Tue Sep 15 01:44:25 2009 From: cjg9411 at rit.edu (Charles Gruener) Date: Mon, 14 Sep 2009 21:44:25 -0400 Subject: [Fedora-xen] Xen 3.4.1 dom0 crash on boot Message-ID: <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu> 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:[] (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 From pasik at iki.fi Tue Sep 15 07:17:30 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 15 Sep 2009 10:17:30 +0300 Subject: [Fedora-xen] Xen 3.4.1 dom0 crash on boot In-Reply-To: <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu> References: <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu> Message-ID: <20090915071730.GP31123@reaktio.net> On Mon, Sep 14, 2009 at 09:44:25PM -0400, Charles Gruener wrote: > 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' You should remove that unsupported 'tty' option. > (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 ]---- So Xen hypervisor is fine, but it's the dom0 kernel that crashes. Please add 'console=hvc0 earlyprintk=xen' options for your Linux _kernel_ (not for Xen), assuming it's pv_ops dom0 kernel.. That should give you more output to figure out the reason for the crash. > (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. > What's your dom0 kernel version? Custom built? -- Pasi From pasik at iki.fi Tue Sep 15 07:56:13 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 15 Sep 2009 10:56:13 +0300 Subject: [Fedora-xen] Xen 3.4.1 dom0 crash on boot In-Reply-To: <20090915071730.GP31123@reaktio.net> References: <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu> <20090915071730.GP31123@reaktio.net> Message-ID: <20090915075613.GQ31123@reaktio.net> On Tue, Sep 15, 2009 at 10:17:30AM +0300, Pasi K?rkk?inen wrote: > On Mon, Sep 14, 2009 at 09:44:25PM -0400, Charles Gruener wrote: > > 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' > > You should remove that unsupported 'tty' option. > > > (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) Oh, and also enable logging.. like this: kernel /xen-3.4.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=115200,8n1 console=com1 module /vmlinuz-2.6.31 ro root=whatever console=hvc0 earlyprintk=xen module /initrd.img -- Pasi From cjg9411 at rit.edu Tue Sep 15 11:29:52 2009 From: cjg9411 at rit.edu (Charles Gruener) Date: Tue, 15 Sep 2009 07:29:52 -0400 Subject: [Fedora-xen] Xen 3.4.1 dom0 crash on boot In-Reply-To: <20090915075613.GQ31123@reaktio.net> References: <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu> <20090915071730.GP31123@reaktio.net> <20090915075613.GQ31123@reaktio.net> Message-ID: <82B3AFF8-B4F1-4347-82F3-04F100002684@rit.edu> Thanks for the help on configuring my boot options. I apologize that I forgot to mention I'm using the latest kernel from M. Young, 2.6.31-1.2.65.xendom0.fc12.x86_64. Here's what I get now that I've done all of what you've said: __ __ _____ _ _ _ _____ __ _ ____ \ \/ /___ _ __ |___ /| || | / | |___ / / _| ___/ |___ \ \ // _ \ '_ \ |_ \| || |_ | |__ |_ \ | |_ / __| | __) | / \ __/ | | | ___) |__ _|| |__|__) || _| (__| |/ __/ /_/\_\___|_| |_| |____(_) |_|(_)_| |____(_)_| \___|_|_____| (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: dom0_mem=1024M loglvl=all guest_loglvl=all console=com1 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) NUMA turned off (XEN) Faking a node at 0000000000000000-00000001c0000000 (XEN) Domain heap initialised (XEN) found SMP MP-table at 000ff780 (XEN) DMI present. (XEN) Using APIC driver default (XEN) ACPI: PM-Timer IO Port: 0x808 (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[804,0], pm1x_evt[800,0] (XEN) ACPI: wakeup_vec[bfea000c], vec_size[20] (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) (XEN) Processor #0 7:10 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) (XEN) Processor #2 7:10 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled) (XEN) Processor #4 7:10 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled) (XEN) Processor #6 7:10 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled) (XEN) Processor #1 7:10 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled) (XEN) Processor #3 7:10 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled) (XEN) Processor #5 7:10 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled) (XEN) Processor #7 7:10 APIC version 21 (XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x88] disabled) (XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x89] disabled) (XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x8a] disabled) (XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x8b] disabled) (XEN) ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) ACPI: IRQ9 used by override. (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) Using ACPI (MADT) for SMP configuration information (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Initializing CPU#0 (XEN) Detected 2666.807 MHz processor. (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 256K (XEN) CPU: L3 cache: 8192K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 0 (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) Intel machine check reporting enabled on CPU#0. (XEN) mce_init: init bank1 (XEN) CPU0: Thermal monitoring enabled (TM1) (XEN) CMCI: find owner on CPU0 (XEN) CMCI: CPU0 owner_map[6c], no_cmci_map[93] (XEN) CPU0: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 (XEN) Booting processor 1/2 eip 8c000 (XEN) Initializing CPU#1 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 256K (XEN) CPU: L3 cache: 8192K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 1 (XEN) Intel machine check reporting enabled on CPU#1. (XEN) mce_init: init bank1 (XEN) CPU1: Thermal monitoring enabled (TM1) (XEN) CMCI: find owner on CPU1 (XEN) CMCI: CPU1 owner_map[2c], no_cmci_map[93] (XEN) CPU1: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 (XEN) Booting processor 2/4 eip 8c000 (XEN) Initializing CPU#2 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 256K (XEN) CPU: L3 cache: 8192K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 2 (XEN) Intel machine check reporting enabled on CPU#2. (XEN) mce_init: init bank1 (XEN) CPU2: Thermal monitoring enabled (TM1) (XEN) CMCI: find owner on CPU2 (XEN) CMCI: CPU2 owner_map[2c], no_cmci_map[93] (XEN) CPU2: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 (XEN) Booting processor 3/6 eip 8c000 (XEN) Initializing CPU#3 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 256K (XEN) CPU: L3 cache: 8192K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 3 (XEN) Intel machine check reporting enabled on CPU#3. (XEN) mce_init: init bank1 (XEN) CPU3: Thermal monitoring enabled (TM1) (XEN) CMCI: find owner on CPU3 (XEN) CMCI: CPU3 owner_map[2c], no_cmci_map[93] (XEN) CPU3: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 (XEN) Booting processor 4/1 eip 8c000 (XEN) Initializing CPU#4 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 256K (XEN) CPU: L3 cache: 8192K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 0 (XEN) Intel machine check reporting enabled on CPU#4. (XEN) mce_init: init bank1 (XEN) CPU4: Thermal monitoring enabled (TM1) (XEN) CMCI: find owner on CPU4 (XEN) CMCI: CPU4 owner_map[0], no_cmci_map[93] (XEN) CPU4: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 (XEN) Booting processor 5/3 eip 8c000 (XEN) Initializing CPU#5 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 256K (XEN) CPU: L3 cache: 8192K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 1 (XEN) Intel machine check reporting enabled on CPU#5. (XEN) mce_init: init bank1 (XEN) CPU5: Thermal monitoring enabled (TM1) (XEN) CMCI: find owner on CPU5 (XEN) CMCI: CPU5 owner_map[0], no_cmci_map[93] (XEN) CPU5: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 (XEN) Booting processor 6/5 eip 8c000 (XEN) Initializing CPU#6 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 256K (XEN) CPU: L3 cache: 8192K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 2 (XEN) Intel machine check reporting enabled on CPU#6. (XEN) mce_init: init bank1 (XEN) CPU6: Thermal monitoring enabled (TM1) (XEN) CMCI: find owner on CPU6 (XEN) CMCI: CPU6 owner_map[0], no_cmci_map[93] (XEN) CPU6: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 (XEN) Booting processor 7/7 eip 8c000 (XEN) Initializing CPU#7 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 256K (XEN) CPU: L3 cache: 8192K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 3 (XEN) Intel machine check reporting enabled on CPU#7. (XEN) mce_init: init bank1 (XEN) CPU7: Thermal monitoring enabled (TM1) (XEN) CMCI: find owner on CPU7 (XEN) CMCI: CPU7 owner_map[0], no_cmci_map[93] (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) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) checking TSC synchronization across 8 CPUs: passed. (XEN) Platform timer is 3.579MHz ACPI PM Timer (XEN) microcode.c:73:d32767 microcode: CPU1 resumed (XEN) microcode.c:73:d32767 microcode: CPU3 resumed (XEN) microcode.c:73:d32767 microcode: CPU4 resumed (XEN) microcode.c:73:d32767 microcode: CPU6 resumed (XEN) microcode.c:73:d32767 microcode: CPU7 resumed (XEN) microcode.c:73:d32767 microcode: CPU5 resumed (XEN) microcode.c:73:d32767 microcode: CPU2 resumed (XEN) Brought up 8 CPUs (XEN) I/O virtualisation disabled (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: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2695000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 00000001b4000000->00000001b8000000 (245760 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff81000000->ffffffff82695000 (XEN) Init. ramdisk: ffffffff82695000->ffffffff83006a00 (XEN) Phys-Mach map: ffffffff83007000->ffffffff83207000 (XEN) Start info: ffffffff83207000->ffffffff832074b4 (XEN) Page tables: ffffffff83208000->ffffffff83225000 (XEN) Boot stack: ffffffff83225000->ffffffff83226000 (XEN) TOTAL: ffffffff80000000->ffffffff83400000 (XEN) ENTRY ADDRESS: ffffffff819fd820 (XEN) Dom0 has maximum 8 VCPUs (XEN) Scrubbing Free RAM: ..................................................done. (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: All (XEN) Guest Loglevel: All (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:[] (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: 00000001b7208000 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. Looking through that information, I don't see anything that really helps me out. Am I missing something? Anything else I should try BIOS level that could shed some light on the nature of the issue or is my best bet to try booting a debug version of Xen? On Sep 15, 2009, at 3:56 AM, Pasi K?rkk?inen wrote: > On Tue, Sep 15, 2009 at 10:17:30AM +0300, Pasi K?rkk?inen wrote: >> On Mon, Sep 14, 2009 at 09:44:25PM -0400, Charles Gruener wrote: >>> 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' >> >> You should remove that unsupported 'tty' option. >> >>> (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) > > Oh, and also enable logging.. like this: > > kernel /xen-3.4.gz dom0_mem=1024M loglvl=all guest_loglvl=all > com1=115200,8n1 console=com1 > module /vmlinuz-2.6.31 ro root=whatever console=hvc0 earlyprintk=xen > module /initrd.img > > -- Pasi > From pasik at iki.fi Tue Sep 15 11:39:14 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 15 Sep 2009 14:39:14 +0300 Subject: [Fedora-xen] 2.6.31-1.2.65.xendom0.fc12.x86_64 crash on boot In-Reply-To: <82B3AFF8-B4F1-4347-82F3-04F100002684@rit.edu> References: <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu> <20090915071730.GP31123@reaktio.net> <20090915075613.GQ31123@reaktio.net> <82B3AFF8-B4F1-4347-82F3-04F100002684@rit.edu> Message-ID: <20090915113914.GT31123@reaktio.net> On Tue, Sep 15, 2009 at 07:29:52AM -0400, Charles Gruener wrote: > Thanks for the help on configuring my boot options. I apologize that > I forgot to mention I'm using the latest kernel from M. Young, > 2.6.31-1.2.65.xendom0.fc12.x86_64. Here's what I get now that I've > done all of what you've said: > Ok. I've CCd Jeremy and xen-devel. Does this crash look familiar to you Jeremy? -- Pasi > __ __ _____ _ _ _ _____ __ _ ____ > \ \/ /___ _ __ |___ /| || | / | |___ / / _| ___/ |___ \ > \ // _ \ '_ \ |_ \| || |_ | |__ |_ \ | |_ / __| | __) | > / \ __/ | | | ___) |__ _|| |__|__) || _| (__| |/ __/ > /_/\_\___|_| |_| |____(_) |_|(_)_| |____(_)_| \___|_|_____| > > (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: dom0_mem=1024M loglvl=all guest_loglvl=all > console=com1 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) NUMA turned off > (XEN) Faking a node at 0000000000000000-00000001c0000000 > (XEN) Domain heap initialised > (XEN) found SMP MP-table at 000ff780 > (XEN) DMI present. > (XEN) Using APIC driver default > (XEN) ACPI: PM-Timer IO Port: 0x808 > (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[804,0], pm1x_evt[800,0] > (XEN) ACPI: wakeup_vec[bfea000c], vec_size[20] > (XEN) ACPI: Local APIC address 0xfee00000 > (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) > (XEN) Processor #0 7:10 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) > (XEN) Processor #2 7:10 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled) > (XEN) Processor #4 7:10 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled) > (XEN) Processor #6 7:10 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled) > (XEN) Processor #1 7:10 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled) > (XEN) Processor #3 7:10 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled) > (XEN) Processor #5 7:10 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled) > (XEN) Processor #7 7:10 APIC version 21 > (XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x88] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x89] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x8a] disabled) > (XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x8b] disabled) > (XEN) ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) > (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 > (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) > (XEN) ACPI: IRQ0 used by override. > (XEN) ACPI: IRQ2 used by override. > (XEN) ACPI: IRQ9 used by override. > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > (XEN) Using ACPI (MADT) for SMP configuration information > (XEN) Using scheduler: SMP Credit Scheduler (credit) > (XEN) Initializing CPU#0 > (XEN) Detected 2666.807 MHz processor. > (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K > (XEN) CPU: L2 cache: 256K > (XEN) CPU: L3 cache: 8192K > (XEN) CPU: Physical Processor ID: 0 > (XEN) CPU: Processor Core ID: 0 > (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) Intel machine check reporting enabled on CPU#0. > (XEN) mce_init: init bank1 > (XEN) CPU0: Thermal monitoring enabled (TM1) > (XEN) CMCI: find owner on CPU0 > (XEN) CMCI: CPU0 owner_map[6c], no_cmci_map[93] > (XEN) CPU0: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 > (XEN) Booting processor 1/2 eip 8c000 > (XEN) Initializing CPU#1 > (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K > (XEN) CPU: L2 cache: 256K > (XEN) CPU: L3 cache: 8192K > (XEN) CPU: Physical Processor ID: 0 > (XEN) CPU: Processor Core ID: 1 > (XEN) Intel machine check reporting enabled on CPU#1. > (XEN) mce_init: init bank1 > (XEN) CPU1: Thermal monitoring enabled (TM1) > (XEN) CMCI: find owner on CPU1 > (XEN) CMCI: CPU1 owner_map[2c], no_cmci_map[93] > (XEN) CPU1: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 > (XEN) Booting processor 2/4 eip 8c000 > (XEN) Initializing CPU#2 > (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K > (XEN) CPU: L2 cache: 256K > (XEN) CPU: L3 cache: 8192K > (XEN) CPU: Physical Processor ID: 0 > (XEN) CPU: Processor Core ID: 2 > (XEN) Intel machine check reporting enabled on CPU#2. > (XEN) mce_init: init bank1 > (XEN) CPU2: Thermal monitoring enabled (TM1) > (XEN) CMCI: find owner on CPU2 > (XEN) CMCI: CPU2 owner_map[2c], no_cmci_map[93] > (XEN) CPU2: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 > (XEN) Booting processor 3/6 eip 8c000 > (XEN) Initializing CPU#3 > (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K > (XEN) CPU: L2 cache: 256K > (XEN) CPU: L3 cache: 8192K > (XEN) CPU: Physical Processor ID: 0 > (XEN) CPU: Processor Core ID: 3 > (XEN) Intel machine check reporting enabled on CPU#3. > (XEN) mce_init: init bank1 > (XEN) CPU3: Thermal monitoring enabled (TM1) > (XEN) CMCI: find owner on CPU3 > (XEN) CMCI: CPU3 owner_map[2c], no_cmci_map[93] > (XEN) CPU3: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 > (XEN) Booting processor 4/1 eip 8c000 > (XEN) Initializing CPU#4 > (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K > (XEN) CPU: L2 cache: 256K > (XEN) CPU: L3 cache: 8192K > (XEN) CPU: Physical Processor ID: 0 > (XEN) CPU: Processor Core ID: 0 > (XEN) Intel machine check reporting enabled on CPU#4. > (XEN) mce_init: init bank1 > (XEN) CPU4: Thermal monitoring enabled (TM1) > (XEN) CMCI: find owner on CPU4 > (XEN) CMCI: CPU4 owner_map[0], no_cmci_map[93] > (XEN) CPU4: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 > (XEN) Booting processor 5/3 eip 8c000 > (XEN) Initializing CPU#5 > (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K > (XEN) CPU: L2 cache: 256K > (XEN) CPU: L3 cache: 8192K > (XEN) CPU: Physical Processor ID: 0 > (XEN) CPU: Processor Core ID: 1 > (XEN) Intel machine check reporting enabled on CPU#5. > (XEN) mce_init: init bank1 > (XEN) CPU5: Thermal monitoring enabled (TM1) > (XEN) CMCI: find owner on CPU5 > (XEN) CMCI: CPU5 owner_map[0], no_cmci_map[93] > (XEN) CPU5: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 > (XEN) Booting processor 6/5 eip 8c000 > (XEN) Initializing CPU#6 > (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K > (XEN) CPU: L2 cache: 256K > (XEN) CPU: L3 cache: 8192K > (XEN) CPU: Physical Processor ID: 0 > (XEN) CPU: Processor Core ID: 2 > (XEN) Intel machine check reporting enabled on CPU#6. > (XEN) mce_init: init bank1 > (XEN) CPU6: Thermal monitoring enabled (TM1) > (XEN) CMCI: find owner on CPU6 > (XEN) CMCI: CPU6 owner_map[0], no_cmci_map[93] > (XEN) CPU6: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 > (XEN) Booting processor 7/7 eip 8c000 > (XEN) Initializing CPU#7 > (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K > (XEN) CPU: L2 cache: 256K > (XEN) CPU: L3 cache: 8192K > (XEN) CPU: Physical Processor ID: 0 > (XEN) CPU: Processor Core ID: 3 > (XEN) Intel machine check reporting enabled on CPU#7. > (XEN) mce_init: init bank1 > (XEN) CPU7: Thermal monitoring enabled (TM1) > (XEN) CMCI: find owner on CPU7 > (XEN) CMCI: CPU7 owner_map[0], no_cmci_map[93] > (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) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 > (XEN) checking TSC synchronization across 8 CPUs: passed. > (XEN) Platform timer is 3.579MHz ACPI PM Timer > (XEN) microcode.c:73:d32767 microcode: CPU1 resumed > (XEN) microcode.c:73:d32767 microcode: CPU3 resumed > (XEN) microcode.c:73:d32767 microcode: CPU4 resumed > (XEN) microcode.c:73:d32767 microcode: CPU6 resumed > (XEN) microcode.c:73:d32767 microcode: CPU7 resumed > (XEN) microcode.c:73:d32767 microcode: CPU5 resumed > (XEN) microcode.c:73:d32767 microcode: CPU2 resumed > (XEN) Brought up 8 CPUs > (XEN) I/O virtualisation disabled > (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: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2695000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 00000001b4000000->00000001b8000000 (245760 pages > to be allocated) > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: ffffffff81000000->ffffffff82695000 > (XEN) Init. ramdisk: ffffffff82695000->ffffffff83006a00 > (XEN) Phys-Mach map: ffffffff83007000->ffffffff83207000 > (XEN) Start info: ffffffff83207000->ffffffff832074b4 > (XEN) Page tables: ffffffff83208000->ffffffff83225000 > (XEN) Boot stack: ffffffff83225000->ffffffff83226000 > (XEN) TOTAL: ffffffff80000000->ffffffff83400000 > (XEN) ENTRY ADDRESS: ffffffff819fd820 > (XEN) Dom0 has maximum 8 VCPUs > (XEN) Scrubbing Free > RAM: ..................................................done. > (XEN) Xen trace buffers: disabled > (XEN) Std. Loglevel: All > (XEN) Guest Loglevel: All > (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:[] > (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: 00000001b7208000 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. > > Looking through that information, I don't see anything that really > helps me out. Am I missing something? Anything else I should try > BIOS level that could shed some light on the nature of the issue or is > my best bet to try booting a debug version of Xen? > > On Sep 15, 2009, at 3:56 AM, Pasi K?rkk?inen wrote: > > >On Tue, Sep 15, 2009 at 10:17:30AM +0300, Pasi K?rkk?inen wrote: > >>On Mon, Sep 14, 2009 at 09:44:25PM -0400, Charles Gruener wrote: > >>>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' > >> > >>You should remove that unsupported 'tty' option. > >> > >>>(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) > > > >Oh, and also enable logging.. like this: > > > >kernel /xen-3.4.gz dom0_mem=1024M loglvl=all guest_loglvl=all > >com1=115200,8n1 console=com1 > >module /vmlinuz-2.6.31 ro root=whatever console=hvc0 earlyprintk=xen > >module /initrd.img > > > >-- Pasi > > > From m.a.young at durham.ac.uk Tue Sep 15 11:45:57 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Tue, 15 Sep 2009 12:45:57 +0100 (BST) Subject: [Fedora-xen] Xen 3.4.1 dom0 crash on boot In-Reply-To: <82B3AFF8-B4F1-4347-82F3-04F100002684@rit.edu> References: <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu> <20090915071730.GP31123@reaktio.net> <20090915075613.GQ31123@reaktio.net> <82B3AFF8-B4F1-4347-82F3-04F100002684@rit.edu> Message-ID: On Tue, 15 Sep 2009, Charles Gruener wrote: > Thanks for the help on configuring my boot options. I apologize that I > forgot to mention I'm using the latest kernel from M. Young, > 2.6.31-1.2.65.xendom0.fc12.x86_64. Here's what I get now that I've done all > of what you've said: > > ... > > (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:[] > (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: 00000001b7208000 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. > > Looking through that information, I don't see anything that really helps me > out. Am I missing something? Anything else I should try BIOS level that > could shed some light on the nature of the issue or is my best bet to try > booting a debug version of Xen? You can dig the vmlinux file out of the debuginfo rpm http://koji.fedoraproject.org/koji/getfile?taskID=1668157&name=kernel-debuginfo-2.6.31-1.2.65.xendom0.fc12.x86_64.rpm feed it into gdb and see what x/i ffffffff81a017f1 tells you about what code it was trying to run when it crashed. Michael Young From pasik at iki.fi Tue Sep 15 11:53:50 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 15 Sep 2009 14:53:50 +0300 Subject: [Fedora-xen] 2.6.31-1.2.65.xendom0.fc12.x86_64 crash on boot In-Reply-To: <20090915113914.GT31123@reaktio.net> References: <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu> <20090915071730.GP31123@reaktio.net> <20090915075613.GQ31123@reaktio.net> <82B3AFF8-B4F1-4347-82F3-04F100002684@rit.edu> <20090915113914.GT31123@reaktio.net> Message-ID: <20090915115350.GU31123@reaktio.net> On Tue, Sep 15, 2009 at 02:39:14PM +0300, Pasi K?rkk?inen wrote: > On Tue, Sep 15, 2009 at 07:29:52AM -0400, Charles Gruener wrote: > > Thanks for the help on configuring my boot options. I apologize that > > I forgot to mention I'm using the latest kernel from M. Young, > > 2.6.31-1.2.65.xendom0.fc12.x86_64. Here's what I get now that I've > > done all of what you've said: > > > > Ok. I've CCd Jeremy and xen-devel. > > Does this crash look familiar to you Jeremy? > Btw might be worth trying to add dom0_vcpus=1 parameter for Xen and see if that makes any difference.. -- Pasi > > > __ __ _____ _ _ _ _____ __ _ ____ > > \ \/ /___ _ __ |___ /| || | / | |___ / / _| ___/ |___ \ > > \ // _ \ '_ \ |_ \| || |_ | |__ |_ \ | |_ / __| | __) | > > / \ __/ | | | ___) |__ _|| |__|__) || _| (__| |/ __/ > > /_/\_\___|_| |_| |____(_) |_|(_)_| |____(_)_| \___|_|_____| > > > > (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: dom0_mem=1024M loglvl=all guest_loglvl=all > > console=com1 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) NUMA turned off > > (XEN) Faking a node at 0000000000000000-00000001c0000000 > > (XEN) Domain heap initialised > > (XEN) found SMP MP-table at 000ff780 > > (XEN) DMI present. > > (XEN) Using APIC driver default > > (XEN) ACPI: PM-Timer IO Port: 0x808 > > (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[804,0], pm1x_evt[800,0] > > (XEN) ACPI: wakeup_vec[bfea000c], vec_size[20] > > (XEN) ACPI: Local APIC address 0xfee00000 > > (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) > > (XEN) Processor #0 7:10 APIC version 21 > > (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) > > (XEN) Processor #2 7:10 APIC version 21 > > (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled) > > (XEN) Processor #4 7:10 APIC version 21 > > (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled) > > (XEN) Processor #6 7:10 APIC version 21 > > (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled) > > (XEN) Processor #1 7:10 APIC version 21 > > (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled) > > (XEN) Processor #3 7:10 APIC version 21 > > (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled) > > (XEN) Processor #5 7:10 APIC version 21 > > (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled) > > (XEN) Processor #7 7:10 APIC version 21 > > (XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x88] disabled) > > (XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x89] disabled) > > (XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x8a] disabled) > > (XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x8b] disabled) > > (XEN) ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) > > (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 > > (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > > (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) > > (XEN) ACPI: IRQ0 used by override. > > (XEN) ACPI: IRQ2 used by override. > > (XEN) ACPI: IRQ9 used by override. > > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > > (XEN) Using ACPI (MADT) for SMP configuration information > > (XEN) Using scheduler: SMP Credit Scheduler (credit) > > (XEN) Initializing CPU#0 > > (XEN) Detected 2666.807 MHz processor. > > (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K > > (XEN) CPU: L2 cache: 256K > > (XEN) CPU: L3 cache: 8192K > > (XEN) CPU: Physical Processor ID: 0 > > (XEN) CPU: Processor Core ID: 0 > > (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) Intel machine check reporting enabled on CPU#0. > > (XEN) mce_init: init bank1 > > (XEN) CPU0: Thermal monitoring enabled (TM1) > > (XEN) CMCI: find owner on CPU0 > > (XEN) CMCI: CPU0 owner_map[6c], no_cmci_map[93] > > (XEN) CPU0: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 > > (XEN) Booting processor 1/2 eip 8c000 > > (XEN) Initializing CPU#1 > > (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K > > (XEN) CPU: L2 cache: 256K > > (XEN) CPU: L3 cache: 8192K > > (XEN) CPU: Physical Processor ID: 0 > > (XEN) CPU: Processor Core ID: 1 > > (XEN) Intel machine check reporting enabled on CPU#1. > > (XEN) mce_init: init bank1 > > (XEN) CPU1: Thermal monitoring enabled (TM1) > > (XEN) CMCI: find owner on CPU1 > > (XEN) CMCI: CPU1 owner_map[2c], no_cmci_map[93] > > (XEN) CPU1: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 > > (XEN) Booting processor 2/4 eip 8c000 > > (XEN) Initializing CPU#2 > > (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K > > (XEN) CPU: L2 cache: 256K > > (XEN) CPU: L3 cache: 8192K > > (XEN) CPU: Physical Processor ID: 0 > > (XEN) CPU: Processor Core ID: 2 > > (XEN) Intel machine check reporting enabled on CPU#2. > > (XEN) mce_init: init bank1 > > (XEN) CPU2: Thermal monitoring enabled (TM1) > > (XEN) CMCI: find owner on CPU2 > > (XEN) CMCI: CPU2 owner_map[2c], no_cmci_map[93] > > (XEN) CPU2: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 > > (XEN) Booting processor 3/6 eip 8c000 > > (XEN) Initializing CPU#3 > > (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K > > (XEN) CPU: L2 cache: 256K > > (XEN) CPU: L3 cache: 8192K > > (XEN) CPU: Physical Processor ID: 0 > > (XEN) CPU: Processor Core ID: 3 > > (XEN) Intel machine check reporting enabled on CPU#3. > > (XEN) mce_init: init bank1 > > (XEN) CPU3: Thermal monitoring enabled (TM1) > > (XEN) CMCI: find owner on CPU3 > > (XEN) CMCI: CPU3 owner_map[2c], no_cmci_map[93] > > (XEN) CPU3: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 > > (XEN) Booting processor 4/1 eip 8c000 > > (XEN) Initializing CPU#4 > > (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K > > (XEN) CPU: L2 cache: 256K > > (XEN) CPU: L3 cache: 8192K > > (XEN) CPU: Physical Processor ID: 0 > > (XEN) CPU: Processor Core ID: 0 > > (XEN) Intel machine check reporting enabled on CPU#4. > > (XEN) mce_init: init bank1 > > (XEN) CPU4: Thermal monitoring enabled (TM1) > > (XEN) CMCI: find owner on CPU4 > > (XEN) CMCI: CPU4 owner_map[0], no_cmci_map[93] > > (XEN) CPU4: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 > > (XEN) Booting processor 5/3 eip 8c000 > > (XEN) Initializing CPU#5 > > (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K > > (XEN) CPU: L2 cache: 256K > > (XEN) CPU: L3 cache: 8192K > > (XEN) CPU: Physical Processor ID: 0 > > (XEN) CPU: Processor Core ID: 1 > > (XEN) Intel machine check reporting enabled on CPU#5. > > (XEN) mce_init: init bank1 > > (XEN) CPU5: Thermal monitoring enabled (TM1) > > (XEN) CMCI: find owner on CPU5 > > (XEN) CMCI: CPU5 owner_map[0], no_cmci_map[93] > > (XEN) CPU5: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 > > (XEN) Booting processor 6/5 eip 8c000 > > (XEN) Initializing CPU#6 > > (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K > > (XEN) CPU: L2 cache: 256K > > (XEN) CPU: L3 cache: 8192K > > (XEN) CPU: Physical Processor ID: 0 > > (XEN) CPU: Processor Core ID: 2 > > (XEN) Intel machine check reporting enabled on CPU#6. > > (XEN) mce_init: init bank1 > > (XEN) CPU6: Thermal monitoring enabled (TM1) > > (XEN) CMCI: find owner on CPU6 > > (XEN) CMCI: CPU6 owner_map[0], no_cmci_map[93] > > (XEN) CPU6: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 04 > > (XEN) Booting processor 7/7 eip 8c000 > > (XEN) Initializing CPU#7 > > (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K > > (XEN) CPU: L2 cache: 256K > > (XEN) CPU: L3 cache: 8192K > > (XEN) CPU: Physical Processor ID: 0 > > (XEN) CPU: Processor Core ID: 3 > > (XEN) Intel machine check reporting enabled on CPU#7. > > (XEN) mce_init: init bank1 > > (XEN) CPU7: Thermal monitoring enabled (TM1) > > (XEN) CMCI: find owner on CPU7 > > (XEN) CMCI: CPU7 owner_map[0], no_cmci_map[93] > > (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) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 > > (XEN) checking TSC synchronization across 8 CPUs: passed. > > (XEN) Platform timer is 3.579MHz ACPI PM Timer > > (XEN) microcode.c:73:d32767 microcode: CPU1 resumed > > (XEN) microcode.c:73:d32767 microcode: CPU3 resumed > > (XEN) microcode.c:73:d32767 microcode: CPU4 resumed > > (XEN) microcode.c:73:d32767 microcode: CPU6 resumed > > (XEN) microcode.c:73:d32767 microcode: CPU7 resumed > > (XEN) microcode.c:73:d32767 microcode: CPU5 resumed > > (XEN) microcode.c:73:d32767 microcode: CPU2 resumed > > (XEN) Brought up 8 CPUs > > (XEN) I/O virtualisation disabled > > (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: 64-bit, lsb, compat32 > > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2695000 > > (XEN) PHYSICAL MEMORY ARRANGEMENT: > > (XEN) Dom0 alloc.: 00000001b4000000->00000001b8000000 (245760 pages > > to be allocated) > > (XEN) VIRTUAL MEMORY ARRANGEMENT: > > (XEN) Loaded kernel: ffffffff81000000->ffffffff82695000 > > (XEN) Init. ramdisk: ffffffff82695000->ffffffff83006a00 > > (XEN) Phys-Mach map: ffffffff83007000->ffffffff83207000 > > (XEN) Start info: ffffffff83207000->ffffffff832074b4 > > (XEN) Page tables: ffffffff83208000->ffffffff83225000 > > (XEN) Boot stack: ffffffff83225000->ffffffff83226000 > > (XEN) TOTAL: ffffffff80000000->ffffffff83400000 > > (XEN) ENTRY ADDRESS: ffffffff819fd820 > > (XEN) Dom0 has maximum 8 VCPUs > > (XEN) Scrubbing Free > > RAM: ..................................................done. > > (XEN) Xen trace buffers: disabled > > (XEN) Std. Loglevel: All > > (XEN) Guest Loglevel: All > > (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:[] > > (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: 00000001b7208000 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. > > > > Looking through that information, I don't see anything that really > > helps me out. Am I missing something? Anything else I should try > > BIOS level that could shed some light on the nature of the issue or is > > my best bet to try booting a debug version of Xen? > > > > On Sep 15, 2009, at 3:56 AM, Pasi K?rkk?inen wrote: > > > > >On Tue, Sep 15, 2009 at 10:17:30AM +0300, Pasi K?rkk?inen wrote: > > >>On Mon, Sep 14, 2009 at 09:44:25PM -0400, Charles Gruener wrote: > > >>>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' > > >> > > >>You should remove that unsupported 'tty' option. > > >> > > >>>(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) > > > > > >Oh, and also enable logging.. like this: > > > > > >kernel /xen-3.4.gz dom0_mem=1024M loglvl=all guest_loglvl=all > > >com1=115200,8n1 console=com1 > > >module /vmlinuz-2.6.31 ro root=whatever console=hvc0 earlyprintk=xen > > >module /initrd.img > > > > > >-- Pasi > > > > > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From pasik at iki.fi Tue Sep 15 12:10:26 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 15 Sep 2009 15:10:26 +0300 Subject: [Fedora-xen] Xen 3.4.1 dom0 crash on boot In-Reply-To: References: <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu> <20090915071730.GP31123@reaktio.net> <20090915075613.GQ31123@reaktio.net> <82B3AFF8-B4F1-4347-82F3-04F100002684@rit.edu> Message-ID: <20090915121026.GV31123@reaktio.net> On Tue, Sep 15, 2009 at 12:45:57PM +0100, M A Young wrote: > On Tue, 15 Sep 2009, Charles Gruener wrote: > > >Thanks for the help on configuring my boot options. I apologize that I > >forgot to mention I'm using the latest kernel from M. Young, > >2.6.31-1.2.65.xendom0.fc12.x86_64. Here's what I get now that I've done > >all of what you've said: > > > >... > > > >(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:[] > >(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: 00000001b7208000 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. > > > >Looking through that information, I don't see anything that really helps > >me out. Am I missing something? Anything else I should try BIOS level > >that could shed some light on the nature of the issue or is my best bet to > >try booting a debug version of Xen? > > You can dig the vmlinux file out of the debuginfo rpm > http://koji.fedoraproject.org/koji/getfile?taskID=1668157&name=kernel-debuginfo-2.6.31-1.2.65.xendom0.fc12.x86_64.rpm > feed it into gdb and see what x/i ffffffff81a017f1 tells you about what > code it was trying to run when it crashed. > Yes, this will be definitely helpful. so just do: gdb vmlinux x/i ffffffff81a017f1 And paste the output here.. -- Pasi From m.a.young at durham.ac.uk Tue Sep 15 12:25:35 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Tue, 15 Sep 2009 13:25:35 +0100 (BST) Subject: [Fedora-xen] Xen 3.4.1 dom0 crash on boot In-Reply-To: <20090915121026.GV31123@reaktio.net> References: <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu> <20090915071730.GP31123@reaktio.net> <20090915075613.GQ31123@reaktio.net> <82B3AFF8-B4F1-4347-82F3-04F100002684@rit.edu> <20090915121026.GV31123@reaktio.net> Message-ID: > > gdb vmlinux > x/i ffffffff81a017f1 That should of course have been (gdb) x/i 0xffffffff81a017f1 0xffffffff81a017f1 : ud2a The context is (gdb) x/60i xen_load_gdt_boot 0xffffffff81a01746 : push %rbp 0xffffffff81a01747 : mov %rsp,%rbp 0xffffffff81a0174a : push %r15 0xffffffff81a0174c : xor %r15d,%r15d 0xffffffff81a0174f : push %r14 0xffffffff81a01751 : push %r13 0xffffffff81a01753 : push %r12 0xffffffff81a01755 : mov %rdi,%r12 0xffffffff81a01758 : push %rbx 0xffffffff81a01759 : sub $0x18,%rsp 0xffffffff81a0175d : movzwl (%rdi),%eax 0xffffffff81a01760 : mov 0x2(%rdi),%rbx 0xffffffff81a01764 : inc %eax 0xffffffff81a01766 : mov %eax,%r14d 0xffffffff81a01769 : mov %eax,-0x34(%rbp) 0xffffffff81a0176c : lea 0xfff(%r14),%rax 0xffffffff81a01773 : shr $0xc,%rax 0xffffffff81a01777 : lea 0x1e(,%rax,8),%rax 0xffffffff81a0177f : and $0x7f0,%eax 0xffffffff81a01784 : sub %rax,%rsp 0xffffffff81a01787 : lea 0xf(%rsp),%r13 0xffffffff81a0178c : and $0xfffffffffffffff0,%r13 0xffffffff81a01790 : test $0xfff,%ebx 0xffffffff81a01796 : je 0xffffffff81a01807 0xffffffff81a01798 : ud2a 0xffffffff81a0179a : jmp 0xffffffff81a0179a 0xffffffff81a0179c : mov %rbx,%rdi 0xffffffff81a0179f : callq 0xffffffff81040b6c <__phys_addr> 0xffffffff81a017a4 : mov %rax,%rsi 0xffffffff81a017a7 : shr $0xc,%rsi 0xffffffff81a017ab : mov %rsi,%rdi 0xffffffff81a017ae : mov %rsi,-0x40(%rbp) 0xffffffff81a017b2 : callq 0xffffffff8100b3ae 0xffffffff81a017b7 : mov -0x40(%rbp),%rsi 0xffffffff81a017bb : mov %rax,%rcx 0xffffffff81a017be : mov $0x8000000000000161,%rax 0xffffffff81a017c8 : and -0x1e351f(%rip),%rax # 0xffffffff8181e2b0 <__supported_pte_mask> 0xffffffff81a017cf : mov %rsi,%rdi 0xffffffff81a017d2 : shl $0xc,%rdi 0xffffffff81a017d6 : or %rax,%rdi 0xffffffff81a017d9 : callq *0xffffffff81798470 0xffffffff81a017e0 : xor %edx,%edx 0xffffffff81a017e2 : mov %rax,%rsi 0xffffffff81a017e5 : mov %rbx,%rdi 0xffffffff81a017e8 : callq 0xffffffff810091c0 0xffffffff81a017ed : test %eax,%eax 0xffffffff81a017ef : je 0xffffffff81a017f5 0xffffffff81a017f1 : ud2a 0xffffffff81a017f3 : jmp 0xffffffff81a017f3 0xffffffff81a017f5 : movslq %r15d,%rax 0xffffffff81a017f8 : add $0x1000,%rbx 0xffffffff81a017ff : inc %r15d 0xffffffff81a01802 : mov %rcx,0x0(%r13,%rax,8) 0xffffffff81a01807 : mov %r14,%rax 0xffffffff81a0180a : add 0x2(%r12),%rax 0xffffffff81a0180f : cmp %rax,%rbx 0xffffffff81a01812 : jb 0xffffffff81a0179c 0xffffffff81a01814 : mov -0x34(%rbp),%esi 0xffffffff81a01817 : mov %r13,%rdi 0xffffffff81a0181a : shr $0x3,%esi From pasik at iki.fi Tue Sep 15 12:46:06 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 15 Sep 2009 15:46:06 +0300 Subject: [Fedora-xen] 2.6.31-1.2.65.xendom0.fc12.x86_64 crash on boot In-Reply-To: References: <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu> <20090915071730.GP31123@reaktio.net> <20090915075613.GQ31123@reaktio.net> <82B3AFF8-B4F1-4347-82F3-04F100002684@rit.edu> <20090915121026.GV31123@reaktio.net> Message-ID: <20090915124606.GW31123@reaktio.net> Jeremy: More info about the dom0 kernel crash here.. -- Pasi On Tue, Sep 15, 2009 at 01:25:35PM +0100, M A Young wrote: > > > > >gdb vmlinux > >x/i ffffffff81a017f1 > > That should of course have been > (gdb) x/i 0xffffffff81a017f1 > 0xffffffff81a017f1 : ud2a > The context is > (gdb) x/60i xen_load_gdt_boot > 0xffffffff81a01746 : push %rbp > 0xffffffff81a01747 : mov %rsp,%rbp > 0xffffffff81a0174a : push %r15 > 0xffffffff81a0174c : xor %r15d,%r15d > 0xffffffff81a0174f : push %r14 > 0xffffffff81a01751 : push %r13 > 0xffffffff81a01753 : push %r12 > 0xffffffff81a01755 : mov %rdi,%r12 > 0xffffffff81a01758 : push %rbx > 0xffffffff81a01759 : sub $0x18,%rsp > 0xffffffff81a0175d : movzwl (%rdi),%eax > 0xffffffff81a01760 : mov 0x2(%rdi),%rbx > 0xffffffff81a01764 : inc %eax > 0xffffffff81a01766 : mov %eax,%r14d > 0xffffffff81a01769 : mov %eax,-0x34(%rbp) > 0xffffffff81a0176c : lea 0xfff(%r14),%rax > 0xffffffff81a01773 : shr $0xc,%rax > 0xffffffff81a01777 : lea 0x1e(,%rax,8),%rax > 0xffffffff81a0177f : and $0x7f0,%eax > 0xffffffff81a01784 : sub %rax,%rsp > 0xffffffff81a01787 : lea 0xf(%rsp),%r13 > 0xffffffff81a0178c : and > $0xfffffffffffffff0,%r13 > 0xffffffff81a01790 : test $0xfff,%ebx > 0xffffffff81a01796 : > je 0xffffffff81a01807 > 0xffffffff81a01798 : ud2a > 0xffffffff81a0179a : > jmp 0xffffffff81a0179a > 0xffffffff81a0179c : mov %rbx,%rdi > 0xffffffff81a0179f : > callq 0xffffffff81040b6c <__phys_addr> > 0xffffffff81a017a4 : mov %rax,%rsi > 0xffffffff81a017a7 : shr $0xc,%rsi > 0xffffffff81a017ab : mov %rsi,%rdi > 0xffffffff81a017ae : mov %rsi,-0x40(%rbp) > 0xffffffff81a017b2 : > callq 0xffffffff8100b3ae > 0xffffffff81a017b7 : mov -0x40(%rbp),%rsi > 0xffffffff81a017bb : mov %rax,%rcx > 0xffffffff81a017be : mov > $0x8000000000000161,%rax > 0xffffffff81a017c8 : > and -0x1e351f(%rip),%rax # 0xffffffff8181e2b0 > <__supported_pte_mask> > 0xffffffff81a017cf : mov %rsi,%rdi > 0xffffffff81a017d2 : shl $0xc,%rdi > 0xffffffff81a017d6 : or %rax,%rdi > 0xffffffff81a017d9 : callq *0xffffffff81798470 > 0xffffffff81a017e0 : xor %edx,%edx > 0xffffffff81a017e2 : mov %rax,%rsi > 0xffffffff81a017e5 : mov %rbx,%rdi > 0xffffffff81a017e8 : > callq 0xffffffff810091c0 > 0xffffffff81a017ed : test %eax,%eax > 0xffffffff81a017ef : > je 0xffffffff81a017f5 > 0xffffffff81a017f1 : ud2a > 0xffffffff81a017f3 : > jmp 0xffffffff81a017f3 > 0xffffffff81a017f5 : movslq %r15d,%rax > 0xffffffff81a017f8 : add $0x1000,%rbx > 0xffffffff81a017ff : inc %r15d > 0xffffffff81a01802 : mov > %rcx,0x0(%r13,%rax,8) > 0xffffffff81a01807 : mov %r14,%rax > 0xffffffff81a0180a : add 0x2(%r12),%rax > 0xffffffff81a0180f : cmp %rax,%rbx > 0xffffffff81a01812 : > jb 0xffffffff81a0179c > 0xffffffff81a01814 : mov -0x34(%rbp),%esi > 0xffffffff81a01817 : mov %r13,%rdi > 0xffffffff81a0181a : shr $0x3,%esi From cjg9411 at rit.edu Tue Sep 15 21:01:55 2009 From: cjg9411 at rit.edu (Charles Gruener) Date: Tue, 15 Sep 2009 17:01:55 -0400 Subject: [Fedora-xen] 2.6.31-1.2.65.xendom0.fc12.x86_64 crash on boot In-Reply-To: <4AAFF1D7.1060100@goop.org> References: <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu> <20090915071730.GP31123@reaktio.net> <20090915075613.GQ31123@reaktio.net> <82B3AFF8-B4F1-4347-82F3-04F100002684@rit.edu> <20090915113914.GT31123@reaktio.net> <4AAFF1D7.1060100@goop.org> Message-ID: <94EE0889-57F7-46DC-994A-7ED0F4AE79ED@rit.edu> Well, for some reason, the BIOS had NX disabled by default. After enabling, I can now get further. I've attached the output I'm now seeing. Could this now be related to the myoung kernel? Many thanks. Charles -------------- next part -------------- A non-text attachment was scrubbed... Name: nx_enabled.txt.gz Type: application/x-gzip Size: 8563 bytes Desc: not available URL: -------------- next part -------------- On Sep 15, 2009, at 3:58 PM, Jeremy Fitzhardinge wrote: > On 09/15/09 04:39, Pasi K?rkk?inen wrote: >>> (XEN) mm.c:1697:d0 Bad L1 flags 800000 >>> > > This looks like something trying to set the NX bit in a mapping, which > should be fine on this processor. Could it be disabled in BIOS or > something? > >> Jeremy: More info about the dom0 kernel crash here.. >> >> -- Pasi >> >> On Tue, Sep 15, 2009 at 01:25:35PM +0100, M A Young wrote: >> >>>> >>> >>>>>> >>>>>> gdb vmlinux >>>>>> x/i ffffffff81a017f1 >>>> >>>> >>>> That should of course have been >>>> (gdb) x/i 0xffffffff81a017f1 >>>> 0xffffffff81a017f1 : ud2a >>> > > Hm, OK. Maybe the problem is that we haven't enabled NX in EFER at > that > early point. I'll cook something up. > > J From konrad.wilk at oracle.com Tue Sep 8 19:34:33 2009 From: konrad.wilk at oracle.com (Konrad Rzeszutek Wilk) Date: Tue, 8 Sep 2009 15:34:33 -0400 Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem In-Reply-To: <20090908192246.GK31123@reaktio.net> References: <20090908184927.GJ31123@reaktio.net> <41057.67598.qm@web56102.mail.re3.yahoo.com> <20090908192246.GK31123@reaktio.net> Message-ID: <20090908193433.GA6944@phenom.dumpdata.com> 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) ? From konrad.wilk at oracle.com Wed Sep 9 14:10:38 2009 From: konrad.wilk at oracle.com (Konrad Rzeszutek Wilk) Date: Wed, 9 Sep 2009 10:10:38 -0400 Subject: [Fedora-xen] 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 In-Reply-To: <298239.22413.qm@web56105.mail.re3.yahoo.com> References: <298239.22413.qm@web56105.mail.re3.yahoo.com> Message-ID: <20090909141038.GB9418@phenom.dumpdata.com> 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 wrote: > > From: Boris Derzhavets > 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" , "Konrad Rzeszutek Wilk" > Cc: "Jeremy Fitzhardinge" , xen-devel at lists.xensource.com, fedora-xen at 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 at 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? From konrad.wilk at oracle.com Wed Sep 9 19:04:44 2009 From: konrad.wilk at oracle.com (Konrad Rzeszutek Wilk) Date: Wed, 9 Sep 2009 15:04:44 -0400 Subject: [Fedora-xen] 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 In-Reply-To: <686632.38518.qm@web56105.mail.re3.yahoo.com> References: <686632.38518.qm@web56105.mail.re3.yahoo.com> Message-ID: <20090909190444.GB9181@phenom.dumpdata.com> On Wed, Sep 09, 2009 at 07:55:34AM -0700, Boris Derzhavets wrote: > >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. You contradict yourself latter where you say that the 2.6.31-rc8 built on F12 and installed on F12 has a stack-trace. Or am I misreading it? > > ? If i compile and and install on F12 kernel has stack trace and is pretty unstable at > runtime. Is the kernel you build on F11 (that being called ServerXen35), with and without Xen producing the same dmesg? That being a dmesg that did not have a stack trace. > > 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. From jeremy at goop.org Wed Sep 9 22:35:44 2009 From: jeremy at goop.org (Jeremy Fitzhardinge) Date: Wed, 09 Sep 2009 15:35:44 -0700 Subject: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem In-Reply-To: <20090908193433.GA6944@phenom.dumpdata.com> References: <20090908184927.GJ31123@reaktio.net> <41057.67598.qm@web56102.mail.re3.yahoo.com> <20090908192246.GK31123@reaktio.net> <20090908193433.GA6944@phenom.dumpdata.com> Message-ID: <4AA82DC0.9090305@goop.org> On 09/08/09 12:34, Konrad Rzeszutek Wilk wrote: > 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. > Yes, I suspect so. Last time around, USB was good for highlighting problems in the swiotlb code. If there's a problem at 4G then generally its some physical address being accidentally truncated by an implicit cast in the middle of an expression. Or something else. (Why, yes, I am helpful today.) J > 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 at lists.xensource.com > http://lists.xensource.com/xen-devel > > From bderzhavets at yahoo.com Wed Sep 9 14:55:34 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Wed, 9 Sep 2009 07:55:34 -0700 (PDT) Subject: [Fedora-xen] 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 Message-ID: <686632.38518.qm@web56105.mail.re3.yahoo.com> >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 wrote: From: Konrad Rzeszutek Wilk 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" Cc: "Jeremy Fitzhardinge" , xen-devel at lists.xensource.com, fedora-xen at 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 wrote: > > From: Boris Derzhavets > 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" , "Konrad Rzeszutek Wilk" > Cc: "Jeremy Fitzhardinge" , xen-devel at lists.xensource.com, fedora-xen at 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 at 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 at lists.xensource.com http://lists.xensource.com/xen-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: dmesg.log.gz Type: application/x-gzip Size: 11693 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: dmesg.1.gz Type: application/x-gzip Size: 15354 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: lspci.vvv.gz Type: application/x-gzip Size: 4008 bytes Desc: not available URL: From nathan at robotics.net Tue Sep 15 14:41:42 2009 From: nathan at robotics.net (Nathan Stratton) Date: Tue, 15 Sep 2009 09:41:42 -0500 (CDT) Subject: [Xen-devel] Re: [Fedora-xen] 2.6.31-1.2.65.xendom0.fc12.x86_64 crash on boot In-Reply-To: <20090915113914.GT31123@reaktio.net> References: <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu> <20090915071730.GP31123@reaktio.net> <20090915075613.GQ31123@reaktio.net> <82B3AFF8-B4F1-4347-82F3-04F100002684@rit.edu> <20090915113914.GT31123@reaktio.net> Message-ID: On Tue, 15 Sep 2009, Pasi K?rkk?inen wrote: > Does this crash look familiar to you Jeremy? > > -- Pasi > >> (XEN) traps.c:437:d0 Unhandled invalid opcode fault/trap [#6] on VCPU >> 0 [ec=0000] I ran into the exact same thing on an install a few days ago. I did not run into it with rc-6. ><> Nathan Stratton CTO, BlinkMind, Inc. nathan at robotics.net nathan at blinkmind.com http://www.robotics.net http://www.blinkmind.com From jeremy at goop.org Tue Sep 15 19:58:15 2009 From: jeremy at goop.org (Jeremy Fitzhardinge) Date: Tue, 15 Sep 2009 12:58:15 -0700 Subject: [Fedora-xen] 2.6.31-1.2.65.xendom0.fc12.x86_64 crash on boot In-Reply-To: <20090915113914.GT31123@reaktio.net> References: <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu> <20090915071730.GP31123@reaktio.net> <20090915075613.GQ31123@reaktio.net> <82B3AFF8-B4F1-4347-82F3-04F100002684@rit.edu> <20090915113914.GT31123@reaktio.net> Message-ID: <4AAFF1D7.1060100@goop.org> On 09/15/09 04:39, Pasi K?rkk?inen wrote: >> (XEN) mm.c:1697:d0 Bad L1 flags 800000 >> This looks like something trying to set the NX bit in a mapping, which should be fine on this processor. Could it be disabled in BIOS or something? > Jeremy: More info about the dom0 kernel crash here.. > > -- Pasi > > On Tue, Sep 15, 2009 at 01:25:35PM +0100, M A Young wrote: > >> > >> >>> > > >>> > >gdb vmlinux >>> > >x/i ffffffff81a017f1 >>> >> > >> > That should of course have been >> > (gdb) x/i 0xffffffff81a017f1 >> > 0xffffffff81a017f1 : ud2a >> Hm, OK. Maybe the problem is that we haven't enabled NX in EFER at that early point. I'll cook something up. J From jeremy at goop.org Tue Sep 15 21:14:56 2009 From: jeremy at goop.org (Jeremy Fitzhardinge) Date: Tue, 15 Sep 2009 14:14:56 -0700 Subject: [Fedora-xen] 2.6.31-1.2.65.xendom0.fc12.x86_64 crash on boot In-Reply-To: <94EE0889-57F7-46DC-994A-7ED0F4AE79ED@rit.edu> References: <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu> <20090915071730.GP31123@reaktio.net> <20090915075613.GQ31123@reaktio.net> <82B3AFF8-B4F1-4347-82F3-04F100002684@rit.edu> <20090915113914.GT31123@reaktio.net> <4AAFF1D7.1060100@goop.org> <94EE0889-57F7-46DC-994A-7ED0F4AE79ED@rit.edu> Message-ID: <4AB003D0.70706@goop.org> On 09/15/09 14:01, Charles Gruener wrote: > Well, for some reason, the BIOS had NX disabled by default. After > enabling, I can now get further. OK, good to know. I'll post a patch shortly which I hope will make it work either way. > I've attached the output I'm now seeing. Could this now be related to > the myoung kernel? It's crashing because dom0 is trying to manipulate the DMAR hardware, which Xen won't allow. I think there's a fix in Xen to hide the DMAR from dom0, but in the meantime you can disable it in BIOS. J From jeremy at goop.org Tue Sep 15 22:23:14 2009 From: jeremy at goop.org (Jeremy Fitzhardinge) Date: Tue, 15 Sep 2009 15:23:14 -0700 Subject: [Fedora-xen] 2.6.31-1.2.65.xendom0.fc12.x86_64 crash on boot In-Reply-To: <20090915113914.GT31123@reaktio.net> References: <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu> <20090915071730.GP31123@reaktio.net> <20090915075613.GQ31123@reaktio.net> <82B3AFF8-B4F1-4347-82F3-04F100002684@rit.edu> <20090915113914.GT31123@reaktio.net> Message-ID: <4AB013D2.908@goop.org> On 09/15/09 04:39, Pasi K?rkk?inen wrote: > On Tue, Sep 15, 2009 at 07:29:52AM -0400, Charles Gruener wrote: > >> Thanks for the help on configuring my boot options. I apologize that >> I forgot to mention I'm using the latest kernel from M. Young, >> 2.6.31-1.2.65.xendom0.fc12.x86_64. Here's what I get now that I've >> done all of what you've said: >> >> > Ok. I've CCd Jeremy and xen-devel. > > Does this crash look familiar to you Jeremy? > Does this fix it? >From 76ca2d74040210450a670df773d760867f07d519 Mon Sep 17 00:00:00 2001 From: Jeremy Fitzhardinge Date: Tue, 15 Sep 2009 14:18:12 -0700 Subject: [PATCH] xen: check EFER for NX before setting up GDT mapping x86-64 assumes NX is available by default, so we need to explicitly check for it before using NX. Some first-generation Intel x86-64 processors didn't support NX, and even recent systems allow it to be disabled in BIOS. Signed-off-by: Jeremy Fitzhardinge diff --git a/arch/x86/mm/Makefile b/arch/x86/mm/Makefile index 72bb3a2..0088329 100644 --- a/arch/x86/mm/Makefile +++ b/arch/x86/mm/Makefile @@ -4,6 +4,7 @@ obj-y := init.o init_$(BITS).o fault.o ioremap.o extable.o pageattr.o mmap.o \ # Make sure __phys_addr has no stackprotector nostackp := $(call cc-option, -fno-stack-protector) CFLAGS_ioremap.o := $(nostackp) +CFLAGS_init.o := $(nostackp) obj-$(CONFIG_SMP) += tlb.o diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c index 03644f9..5b55c92 100644 --- a/arch/x86/xen/enlighten.c +++ b/arch/x86/xen/enlighten.c @@ -1092,6 +1092,11 @@ asmlinkage void __init xen_start_kernel(void) __supported_pte_mask |= _PAGE_IOMAP; +#ifdef CONFIG_X86_64 + /* Work out if we support NX */ + check_efer(); +#endif + xen_setup_features(); /* Get mfn list */ @@ -1132,11 +1137,6 @@ asmlinkage void __init xen_start_kernel(void) pgd = (pgd_t *)xen_start_info->pt_base; -#ifdef CONFIG_X86_64 - /* Work out if we support NX */ - check_efer(); -#endif - /* Don't do the full vcpu_info placement stuff until we have a possible map and a non-dummy shared_info. */ per_cpu(xen_vcpu, 0) = &HYPERVISOR_shared_info->vcpu_info[0]; From m.a.young at durham.ac.uk Wed Sep 16 08:47:17 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Wed, 16 Sep 2009 09:47:17 +0100 (BST) Subject: [Fedora-xen] 2.6.31-1.2.65.xendom0.fc12.x86_64 crash on boot In-Reply-To: <4AB013D2.908@goop.org> References: <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu> <20090915071730.GP31123@reaktio.net> <20090915075613.GQ31123@reaktio.net> <82B3AFF8-B4F1-4347-82F3-04F100002684@rit.edu> <20090915113914.GT31123@reaktio.net> <4AB013D2.908@goop.org> Message-ID: On Tue, 15 Sep 2009, Jeremy Fitzhardinge wrote: > On 09/15/09 04:39, Pasi K?rkk?inen wrote: >> On Tue, Sep 15, 2009 at 07:29:52AM -0400, Charles Gruener wrote: >> >>> Thanks for the help on configuring my boot options. I apologize that >>> I forgot to mention I'm using the latest kernel from M. Young, >>> 2.6.31-1.2.65.xendom0.fc12.x86_64. Here's what I get now that I've >>> done all of what you've said: >>> >>> >> Ok. I've CCd Jeremy and xen-devel. >> >> Does this crash look familiar to you Jeremy? >> > > Does this fix it? > >> From 76ca2d74040210450a670df773d760867f07d519 Mon Sep 17 00:00:00 2001 > From: Jeremy Fitzhardinge > Date: Tue, 15 Sep 2009 14:18:12 -0700 > Subject: [PATCH] xen: check EFER for NX before setting up GDT mapping kernel-2.6.31-1.2.67.xendom0.fc12.x86_64.rpm has this fix in if you want to test it, at http://koji.fedoraproject.org/koji/getfile?taskID=1681664&name=kernel-2.6.31-1.2.67.xendom0.fc12.x86_64.rpm (the other kernel packages are available via http://koji.fedoraproject.org/koji/taskinfo?taskID=1681662 ) I haven't tested it so I don't know if it boots. Michael Young From pasik at iki.fi Wed Sep 16 11:47:13 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 16 Sep 2009 14:47:13 +0300 Subject: [Fedora-xen] 2.6.31-1.2.65.xendom0.fc12.x86_64 crash on boot In-Reply-To: References: <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu> <20090915071730.GP31123@reaktio.net> <20090915075613.GQ31123@reaktio.net> <82B3AFF8-B4F1-4347-82F3-04F100002684@rit.edu> <20090915113914.GT31123@reaktio.net> <4AB013D2.908@goop.org> Message-ID: <20090916114713.GC31123@reaktio.net> On Wed, Sep 16, 2009 at 09:47:17AM +0100, M A Young wrote: > On Tue, 15 Sep 2009, Jeremy Fitzhardinge wrote: > > >On 09/15/09 04:39, Pasi K?rkk?inen wrote: > >>On Tue, Sep 15, 2009 at 07:29:52AM -0400, Charles Gruener wrote: > >> > >>>Thanks for the help on configuring my boot options. I apologize that > >>>I forgot to mention I'm using the latest kernel from M. Young, > >>>2.6.31-1.2.65.xendom0.fc12.x86_64. Here's what I get now that I've > >>>done all of what you've said: > >>> > >>> > >>Ok. I've CCd Jeremy and xen-devel. > >> > >>Does this crash look familiar to you Jeremy? > >> > > > >Does this fix it? > > > >>From 76ca2d74040210450a670df773d760867f07d519 Mon Sep 17 00:00:00 2001 > >From: Jeremy Fitzhardinge > >Date: Tue, 15 Sep 2009 14:18:12 -0700 > >Subject: [PATCH] xen: check EFER for NX before setting up GDT mapping > > kernel-2.6.31-1.2.67.xendom0.fc12.x86_64.rpm has this fix in if you want > to test it, at > http://koji.fedoraproject.org/koji/getfile?taskID=1681664&name=kernel-2.6.31-1.2.67.xendom0.fc12.x86_64.rpm > (the other kernel packages are available via > http://koji.fedoraproject.org/koji/taskinfo?taskID=1681662 > ) I haven't tested it so I don't know if it boots. > Charles: Please try this updated kernel and let us know if it works for you. Thanks! -- Pasi From cjg9411 at rit.edu Wed Sep 16 16:09:20 2009 From: cjg9411 at rit.edu (Charles Gruener) Date: Wed, 16 Sep 2009 12:09:20 -0400 Subject: [Fedora-xen] 2.6.31-1.2.65.xendom0.fc12.x86_64 crash on boot In-Reply-To: <20090916114713.GC31123@reaktio.net> References: <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu> <20090915071730.GP31123@reaktio.net> <20090915075613.GQ31123@reaktio.net> <82B3AFF8-B4F1-4347-82F3-04F100002684@rit.edu> <20090915113914.GT31123@reaktio.net> <4AB013D2.908@goop.org> <20090916114713.GC31123@reaktio.net> Message-ID: <20FE5C88-00D8-47FC-AACE-99DD211EC99E@rit.edu> This absolutely fixes my issue. With the latest patch, I can boot my system successfully if NX is enabled or disabled in the BIOS. Just a final note, I do need to make sure VT-d is disabled in the BIOS, and then I can boot. This was obviously not addressed in this patch nor was it requested to be. It would be nice to have it working at some point as this machine will hopefully have a bunch of NVidia cards in it that will need to be dedicated to each of the domU's for CUDA research. Thank you all for your prompt and courteous responses. It makes me proud to be a RHCE when I get support from a community of developers like you guys. Charles On Sep 16, 2009, at 7:47 AM, Pasi K?rkk?inen wrote: > On Wed, Sep 16, 2009 at 09:47:17AM +0100, M A Young wrote: >> On Tue, 15 Sep 2009, Jeremy Fitzhardinge wrote: >> >>> On 09/15/09 04:39, Pasi K?rkk?inen wrote: >>>> On Tue, Sep 15, 2009 at 07:29:52AM -0400, Charles Gruener wrote: >>>> >>>>> Thanks for the help on configuring my boot options. I apologize >>>>> that >>>>> I forgot to mention I'm using the latest kernel from M. Young, >>>>> 2.6.31-1.2.65.xendom0.fc12.x86_64. Here's what I get now that >>>>> I've >>>>> done all of what you've said: >>>>> >>>>> >>>> Ok. I've CCd Jeremy and xen-devel. >>>> >>>> Does this crash look familiar to you Jeremy? >>>> >>> >>> Does this fix it? >>> >>>> From 76ca2d74040210450a670df773d760867f07d519 Mon Sep 17 00:00:00 >>>> 2001 >>> From: Jeremy Fitzhardinge >>> Date: Tue, 15 Sep 2009 14:18:12 -0700 >>> Subject: [PATCH] xen: check EFER for NX before setting up GDT >>> mapping >> >> kernel-2.6.31-1.2.67.xendom0.fc12.x86_64.rpm has this fix in if you >> want >> to test it, at >> http://koji.fedoraproject.org/koji/getfile?taskID=1681664&name=kernel-2.6.31-1.2.67.xendom0.fc12.x86_64.rpm >> (the other kernel packages are available via >> http://koji.fedoraproject.org/koji/taskinfo?taskID=1681662 >> ) I haven't tested it so I don't know if it boots. >> > > Charles: Please try this updated kernel and let us know if it works > for > you. > > Thanks! > > -- Pasi > From bderzhavets at yahoo.com Thu Sep 17 18:07:08 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Thu, 17 Sep 2009 11:07:08 -0700 (PDT) Subject: [Fedora-xen] Xend doesn't start at Xen 3.4.1 Dom(2.6.31 commit ebf47a1fe1aec22756c32fdba3dd94b05d5b8a84) on top of F11 In-Reply-To: <20090914170634.GL31123@reaktio.net> Message-ID: <523127.81389.qm@web56102.mail.re3.yahoo.com> Xen 3.4.1? Dom0 has been built via xen-3.1.4-4.src.rpm on top of F11 ( yum updated) This failure didn't happen with rc8 (or rc9),? not sure. At the same time via my experience xend starts fine on? the same 3.4.1 Dom0 (same 2.6.31 kernel) been built on top of F12 rawhide (yum updated). /etc/fstab contains 'xenfs' entry (3.4.1) in both cases and in both cases message /proc/xen is busy comes to console, however on F12 xend starts on F11 doesn't. I believe it makes sense to backport via xen-3.1.4-4.src.rpm CS 20185 plus some other CSs to make patching consistent (i cannot find out which ones)? and get an option to remove 'xenfs' entry from /etc/fstab, mounting 'xenfs' at xend start up , what seems to be a default behaviour of the most recent 2.6.31 pvops enabled kernel. Boris. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pasik at iki.fi Thu Sep 17 18:45:16 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Thu, 17 Sep 2009 21:45:16 +0300 Subject: [Fedora-xen] Re: Xend doesn't start at Xen 3.4.1 Dom(2.6.31 commit ebf47a1fe1aec22756c32fdba3dd94b05d5b8a84) on top of F11 In-Reply-To: <523127.81389.qm@web56102.mail.re3.yahoo.com> References: <20090914170634.GL31123@reaktio.net> <523127.81389.qm@web56102.mail.re3.yahoo.com> Message-ID: <20090917184516.GG31123@reaktio.net> On Thu, Sep 17, 2009 at 11:07:08AM -0700, Boris Derzhavets wrote: > Xen 3.4.1? Dom0 has been built via xen-3.1.4-4.src.rpm on top of F11 ( yum updated) > This failure didn't happen with rc8 (or rc9),? not sure. > At the same time via my experience xend starts fine on? the same 3.4.1 Dom0 (same 2.6.31 kernel) been built on top of F12 rawhide (yum updated). > /etc/fstab contains 'xenfs' entry (3.4.1) in both cases and in both cases message > /proc/xen is busy comes to console, however on F12 xend starts on F11 doesn't. I haven't had problems starting xend on F11, with 2.6.31 pv_ops dom0 kernel.. > I believe it makes sense to backport via xen-3.1.4-4.src.rpm CS 20185 plus some other > CSs to make patching consistent (i cannot find out which ones)? and get an option to remove 'xenfs' entry from /etc/fstab, mounting 'xenfs' at xend start up , what seems > to be a default behaviour of the most recent 2.6.31 pvops enabled kernel. > Mounting xenfs from xend has nothing to do with the kernel. It's a feature of xen-unstable tools, not kernel -- Pasi From kraxel at redhat.com Thu Sep 17 20:53:04 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Thu, 17 Sep 2009 22:53:04 +0200 Subject: [Fedora-xen] Re: Xend doesn't start at Xen 3.4.1 Dom(2.6.31 commit ebf47a1fe1aec22756c32fdba3dd94b05d5b8a84) on top of F11 In-Reply-To: <523127.81389.qm@web56102.mail.re3.yahoo.com> References: <523127.81389.qm@web56102.mail.re3.yahoo.com> Message-ID: <4AB2A1B0.3050503@redhat.com> Hi, > /etc/fstab contains 'xenfs' entry (3.4.1) in both cases Hmm, where does that one come from? It should not be there, it is not needed. The xen packages never ever touch /etc/fstab. > mounting 'xenfs' at xend start up , what seems > to be a default behaviour of the most recent 2.6.31 pvops enabled kernel. Both F11 (3.3.x) and F12 (3.4.x) xen packages mount the filesystem automatically. Very early xen packages with pv_ops kernel support didn't do that though, so maybe the /etc/fstab entry was added manually back then and was never deleted? cheers, Gerd From bderzhavets at yahoo.com Fri Sep 18 05:14:36 2009 From: bderzhavets at yahoo.com (Boris Derzhavets) Date: Thu, 17 Sep 2009 22:14:36 -0700 (PDT) Subject: [Fedora-xen] Re: Xend doesn't start at Xen 3.4.1 Dom(2.6.31 commit ebf47a1fe1aec22756c32fdba3dd94b05d5b8a84) on top of F11 In-Reply-To: <4AB2A1B0.3050503@redhat.com> Message-ID: <411245.21269.qm@web56106.mail.re3.yahoo.com> I removed 'xenfs' entry from /etc/fstab and it brought back to life Xen 3.4.1 (via xen-3.4.1-4.src.rpm) & Libvirt on the first F11 box, and didn't help on the second. I would guess it's xen&pvops unrelated issue on second box. Thanks. Boris. --- On Thu, 9/17/09, Gerd Hoffmann wrote: From: Gerd Hoffmann Subject: Re: Xend doesn't start at Xen 3.4.1 Dom(2.6.31 commit ebf47a1fe1aec22756c32fdba3dd94b05d5b8a84) on top of F11 To: "Boris Derzhavets" Cc: "Pasi K?rkk?inen" , fedora-xen at redhat.com Date: Thursday, September 17, 2009, 4:53 PM ? Hi, > /etc/fstab contains 'xenfs' entry (3.4.1) in both cases Hmm, where does that one come from? It should not be there, it is not needed. The xen packages never ever touch /etc/fstab. >? mounting 'xenfs' at xend start up , what seems > to be a default behaviour of the most recent 2.6.31 pvops enabled kernel. Both F11 (3.3.x) and F12 (3.4.x) xen packages mount the filesystem automatically.? Very early xen packages with pv_ops kernel support didn't do that though, so maybe the /etc/fstab entry was added manually back then and was never deleted? cheers, ? Gerd -------------- next part -------------- An HTML attachment was scrubbed... URL: From pasik at iki.fi Mon Sep 21 07:56:00 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 21 Sep 2009 10:56:00 +0300 Subject: [Fedora-xen] [Xen-devel] Announcing xen/master: pvops git trees rearranged Message-ID: <20090921075600.GI31123@reaktio.net> ----- Forwarded message from Jeremy Fitzhardinge ----- From: Jeremy Fitzhardinge To: Xen-devel 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 at lists.xensource.com http://lists.xensource.com/xen-devel ----- End forwarded message ----- From jeremy at goop.org Mon Sep 21 19:07:42 2009 From: jeremy at goop.org (Jeremy Fitzhardinge) Date: Mon, 21 Sep 2009 12:07:42 -0700 Subject: [Xen-devel] Re: [Fedora-xen] 2.6.31-1.2.65.xendom0.fc12.x86_64 crash on boot In-Reply-To: <20FE5C88-00D8-47FC-AACE-99DD211EC99E@rit.edu> References: <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu> <20090915071730.GP31123@reaktio.net> <20090915075613.GQ31123@reaktio.net> <82B3AFF8-B4F1-4347-82F3-04F100002684@rit.edu> <20090915113914.GT31123@reaktio.net> <4AB013D2.908@goop.org> <20090916114713.GC31123@reaktio.net> <20FE5C88-00D8-47FC-AACE-99DD211EC99E@rit.edu> Message-ID: <4AB7CEFE.3020109@goop.org> On 09/16/09 09:09, Charles Gruener wrote: > This absolutely fixes my issue. With the latest patch, I can boot my > system successfully if NX is enabled or disabled in the BIOS. Great, thanks for the confirmation. I'll push this patch upstream. > Just a final note, I do need to make sure VT-d is disabled in the > BIOS, and then I can boot. This was obviously not addressed in this > patch nor was it requested to be. It would be nice to have it working > at some point as this machine will hopefully have a bunch of NVidia > cards in it that will need to be dedicated to each of the domU's for > CUDA research. Just to clarify this a bit: Are you saying that if you leave VT-d enabled in BIOS something bad happens? Does it crash? But ideally you'd like to enable it and have it working to allow NVidia cards work, which require it? Thanks, J From cjg9411 at rit.edu Mon Sep 21 19:24:41 2009 From: cjg9411 at rit.edu (Charles J Gruener) Date: Mon, 21 Sep 2009 15:24:41 -0400 Subject: [Xen-devel] Re: [Fedora-xen] 2.6.31-1.2.65.xendom0.fc12.x86_64 crash on boot In-Reply-To: <4AB7CEFE.3020109@goop.org> References: <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu> <20090915071730.GP31123@reaktio.net> <20090915075613.GQ31123@reaktio.net> <82B3AFF8-B4F1-4347-82F3-04F100002684@rit.edu> <20090915113914.GT31123@reaktio.net> <4AB013D2.908@goop.org> <20090916114713.GC31123@reaktio.net> <20FE5C88-00D8-47FC-AACE-99DD211EC99E@rit.edu> <4AB7CEFE.3020109@goop.org> Message-ID: <01CEE32B-3A37-415B-A2BB-8554A8B37E6C@rit.edu> This is coming from memory as I won't be in front of the machine experiencing the issue for another three weeks. Gotta love paternity leave. :) From what I recall, if I leave VT-d enabled in the BIOS, I experience the dom0 crash I had sent earlier as a .gz file. I can verify this at a later date. Ideally, I am looking to have the ability to assign the NVidia cards to the individual domU machines for CUDA development. We want to see how virtualization affects CUDA performance among other things. The patch that you provided earlier now allows the machine to boot no matter what the NX setting is in the BIOS. Does that help clarify the situation? Charles On Sep 21, 2009, at 3:07 PM, "Jeremy Fitzhardinge" wrote: > >> Just a final note, I do need to make sure VT-d is disabled in the >> BIOS, and then I can boot. This was obviously not addressed in this >> patch nor was it requested to be. It would be nice to have it >> working >> at some point as this machine will hopefully have a bunch of NVidia >> cards in it that will need to be dedicated to each of the domU's for >> CUDA research. > > Just to clarify this a bit: > > Are you saying that if you leave VT-d enabled in BIOS something bad > happens? Does it crash? > > But ideally you'd like to enable it and have it working to allow > NVidia cards work, which require it? > > Thanks, > J From pasik at iki.fi Mon Sep 21 19:48:05 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 21 Sep 2009 22:48:05 +0300 Subject: [Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released / 3.4.1-4 rpm and ext4 /boot works with pygrub In-Reply-To: <20090914170634.GL31123@reaktio.net> References: <20090901145020.GW31123@reaktio.net> <20090901151721.GA31123@reaktio.net> <4A9E6457.6010206@redhat.com> <20090902124109.GK31123@reaktio.net> <20090902125931.GL31123@reaktio.net> <20090902130832.GM31123@reaktio.net> <20090913161629.GV31123@reaktio.net> <4AADE8DB.4060406@redhat.com> <20090914162745.GK31123@reaktio.net> <20090914170634.GL31123@reaktio.net> Message-ID: <20090921194805.GO31123@reaktio.net> On Mon, Sep 14, 2009 at 08:06:34PM +0300, Pasi K?rkk?inen wrote: > On Mon, Sep 14, 2009 at 07:27:45PM +0300, Pasi K?rkk?inen wrote: > > On Mon, Sep 14, 2009 at 08:55:23AM +0200, Gerd Hoffmann wrote: > > > Hi, > > > > > > >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? > > > > > > e2fsprogs-devel most likely. > > > > > > > Yeah, it seems I have e2fsprogs-devel installed on my testbox. So that > > explains the difference. > > > > The attached xen.spec patch fixes this issue. Please add it for xen-3.4.1-4. > > > > .. and it's needed to be able to boot F12 Xen PV guests. > They use ext4 /boot as a default. > xen-3.4.1-4 rpms from f12/rawhide seem to work OK, booting f12 PV domU with /boot on ext4 works OK. -- Pasi From pasik at iki.fi Mon Sep 21 19:57:50 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 21 Sep 2009 22:57:50 +0300 Subject: [Fedora-xen] Fedora 11 PV Xen domU (2.6.29.4-167.fc11.x86_64) crash with invalid opcode in xsave_cntxt_init (xsetbv) Message-ID: <20090921195750.GQ31123@reaktio.net> 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:[] (early) [] xsave_cntxt_init+0xba/0x199 [root at dom0 RH]# gdb vmlinux (gdb) x/i 0xffffffff81397963 0xffffffff81397963 : xsetbv (gdb) x/60i xsave_cntxt_init 0xffffffff813978a9 : push %rbp 0xffffffff813978aa : mov %rsp,%rbp 0xffffffff813978ad : push %r14 0xffffffff813978af : push %r13 0xffffffff813978b1 : push %r12 0xffffffff813978b3 : push %rbx 0xffffffff813978b4 : sub $0x10,%rsp 0xffffffff813978b8 : callq 0xffffffff81011000 0xffffffff813978bd : lea -0x24(%rbp),%rbx 0xffffffff813978c1 : lea -0x28(%rbp),%r12 0xffffffff813978c5 : lea -0x2c(%rbp),%r13 0xffffffff813978c9 : lea -0x30(%rbp),%r14 0xffffffff813978cd : movl $0xd,-0x24(%rbp) 0xffffffff813978d4 : movl $0x0,-0x2c(%rbp) 0xffffffff813978db : mov %rbx,%rdi 0xffffffff813978de : mov %r12,%rsi 0xffffffff813978e1 : mov %r13,%rdx 0xffffffff813978e4 : mov %r14,%rcx 0xffffffff813978e7 : callq *0x1f24b3(%rip) # 0xffffffff81589da0 0xffffffff813978ed : mov -0x30(%rbp),%eax 0xffffffff813978f0 : mov -0x24(%rbp),%esi 0xffffffff813978f3 : shl $0x20,%rax 0xffffffff813978f7 : lea (%rax,%rsi,1),%rsi 0xffffffff813978fb : mov %rsi,%rax 0xffffffff813978fe : mov %rsi,0x4357ab(%rip) # 0xffffffff817cd0b0 0xffffffff81397905 : and $0x3,%eax 0xffffffff81397908 : cmp $0x3,%rax 0xffffffff8139790c : je 0xffffffff81397920 0xffffffff8139790e : mov $0xffffffff814ca823,%rdi 0xffffffff81397915 : xor %eax,%eax 0xffffffff81397917 : callq 0xffffffff813a95be 0xffffffff8139791c : ud2a 0xffffffff8139791e : jmp 0xffffffff8139791e ---Type to continue, or q to quit--- 0xffffffff81397920 : testb $0x4,0x26a700(%rip) # 0xffffffff81602027 0xffffffff81397927 : movq $0x3,0x43577e(%rip) # 0xffffffff817cd0b0 0xffffffff81397932 : je 0xffffffff81397966 0xffffffff81397934 : orq $0x40000,0x423721(%rip) # 0xffffffff817bb060 0xffffffff8139793f : callq *0x1f23ab(%rip) # 0xffffffff81589cf0 0xffffffff81397945 : mov %eax,%edi 0xffffffff81397947 : or $0x40000,%edi 0xffffffff8139794d : callq *0x1f23a5(%rip) # 0xffffffff81589cf8 0xffffffff81397953 : mov 0x435756(%rip),%rax # 0xffffffff817cd0b0 0xffffffff8139795a : xor %ecx,%ecx 0xffffffff8139795c : mov %rax,%rdx 0xffffffff8139795f : shr $0x20,%rdx 0xffffffff81397963 : xsetbv 0xffffffff81397966 : movl $0xd,-0x24(%rbp) 0xffffffff8139796d : movl $0x0,-0x2c(%rbp) 0xffffffff81397974 : mov %rbx,%rdi 0xffffffff81397977 : mov %r12,%rsi 0xffffffff8139797a : mov %r13,%rdx 0xffffffff8139797d : mov %r14,%rcx 0xffffffff81397980 : callq *0x1f241a(%rip) # 0xffffffff81589da0 0xffffffff81397986 : mov $0xffffffff817cd0c0,%rsi 0xffffffff8139798d : xor %eax,%eax 0xffffffff8139798f : mov $0xc,%ecx 0xffffffff81397994 : mov %rsi,%rdi 0xffffffff81397997 : mov -0x28(%rbp),%ebx 0xffffffff8139799a : rep stos %eax,%es:(%rdi) 0xffffffff8139799c : mov 0x43570d(%rip),%rax # 0xffffffff817cd0b0 (gdb) -- Pasi From jeremy at goop.org Mon Sep 21 20:29:21 2009 From: jeremy at goop.org (Jeremy Fitzhardinge) Date: Mon, 21 Sep 2009 13:29:21 -0700 Subject: [Fedora-xen] Re: Fedora 11 PV Xen domU (2.6.29.4-167.fc11.x86_64) crash with invalid opcode in xsave_cntxt_init (xsetbv) In-Reply-To: <20090921195750.GQ31123@reaktio.net> References: <20090921195750.GQ31123@reaktio.net> Message-ID: <4AB7E221.60709@goop.org> On 09/21/09 12:57, Pasi K?rkk?inen wrote: > 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:[] (early) [] xsave_cntxt_init+0xba/0x199 > This looks like the bug where Xen doesn't filter out the xsave feature flag and the kernel tries to use it, fixed in change ef7616ff29ad. Kernel change e826fe1ba15 works around the Xen bug by doing its own masking (I think it got into 2.6.30). There's also a "noxsave" kernel parameter, but that may have been added after 2.6.29. J From pasik at iki.fi Mon Sep 21 20:44:44 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 21 Sep 2009 23:44:44 +0300 Subject: [Fedora-xen] Re: Fedora 11 PV Xen domU (2.6.29.4-167.fc11.x86_64) crash with invalid opcode in xsave_cntxt_init (xsetbv) In-Reply-To: <4AB7E221.60709@goop.org> References: <20090921195750.GQ31123@reaktio.net> <4AB7E221.60709@goop.org> Message-ID: <20090921204444.GU31123@reaktio.net> On Mon, Sep 21, 2009 at 01:29:21PM -0700, Jeremy Fitzhardinge wrote: > On 09/21/09 12:57, Pasi K?rkk?inen wrote: > > 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:[] (early) [] xsave_cntxt_init+0xba/0x199 > > > > This looks like the bug where Xen doesn't filter out the xsave feature > flag and the kernel tries to use it, fixed in change ef7616ff29ad. > Kernel change e826fe1ba15 works around the Xen bug by doing its own > masking (I think it got into 2.6.30). > > There's also a "noxsave" kernel parameter, but that may have been added > after 2.6.29. > Thanks for the fast reply. I'll ask him to try "noxsave". Other than that not much to do about it.. can't really update the F11 GA installer kernel.. (and I don't think doing own custom re-spin of F11 is good solution for him). -- Pasi From jeremy at goop.org Mon Sep 21 21:10:51 2009 From: jeremy at goop.org (Jeremy Fitzhardinge) Date: Mon, 21 Sep 2009 14:10:51 -0700 Subject: [Fedora-xen] Re: [Xen-devel] Re: Fedora 11 PV Xen domU (2.6.29.4-167.fc11.x86_64) crash with invalid opcode in xsave_cntxt_init (xsetbv) In-Reply-To: <20090921204444.GU31123@reaktio.net> References: <20090921195750.GQ31123@reaktio.net> <4AB7E221.60709@goop.org> <20090921204444.GU31123@reaktio.net> Message-ID: <4AB7EBDB.7040108@goop.org> On 09/21/09 13:44, Pasi K?rkk?inen wrote: > Thanks for the fast reply. I'll ask him to try "noxsave". > > Other than that not much to do about it.. can't really update the F11 GA > installer kernel.. (and I don't think doing own custom re-spin of F11 is > good solution for him). > Oh, its a domU install? You can mask it in the domain config with the oh-so-intuitive cpuid=[] setting (leaf 1, ecx bit 26). I think that's: cpuid=['1:ecx=xxxxx0xxxxxxxxxxxxxxxxxxxxxxxxxx, eax=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' ] (I'm assuming it works for PV as well as HVM domains.) J From pasik at iki.fi Mon Sep 21 21:15:56 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 22 Sep 2009 00:15:56 +0300 Subject: [Fedora-xen] Re: Fedora 11 PV Xen domU (2.6.29.4-167.fc11.x86_64) crash with invalid opcode in xsave_cntxt_init (xsetbv) In-Reply-To: <20090921204444.GU31123@reaktio.net> References: <20090921195750.GQ31123@reaktio.net> <4AB7E221.60709@goop.org> <20090921204444.GU31123@reaktio.net> Message-ID: <20090921211556.GV31123@reaktio.net> On Mon, Sep 21, 2009 at 11:44:44PM +0300, Pasi K?rkk?inen wrote: > On Mon, Sep 21, 2009 at 01:29:21PM -0700, Jeremy Fitzhardinge wrote: > > On 09/21/09 12:57, Pasi K?rkk?inen wrote: > > > 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:[] (early) [] xsave_cntxt_init+0xba/0x199 > > > > > > > This looks like the bug where Xen doesn't filter out the xsave feature > > flag and the kernel tries to use it, fixed in change ef7616ff29ad. > > Kernel change e826fe1ba15 works around the Xen bug by doing its own > > masking (I think it got into 2.6.30). > > > > There's also a "noxsave" kernel parameter, but that may have been added > > after 2.6.29. > > > > Thanks for the fast reply. I'll ask him to try "noxsave". > It seems "noxsave" kernel parameter was added in Linux 2.6.30, so that doesn't help for 2.6.29. -- Pasi From pasik at iki.fi Mon Sep 21 21:34:50 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 22 Sep 2009 00:34:50 +0300 Subject: [Fedora-xen] Re: [Xen-devel] Re: Fedora 11 PV Xen domU (2.6.29.4-167.fc11.x86_64) crash with invalid opcode in xsave_cntxt_init (xsetbv) In-Reply-To: <4AB7EBDB.7040108@goop.org> References: <20090921195750.GQ31123@reaktio.net> <4AB7E221.60709@goop.org> <20090921204444.GU31123@reaktio.net> <4AB7EBDB.7040108@goop.org> Message-ID: <20090921213450.GW31123@reaktio.net> On Mon, Sep 21, 2009 at 02:10:51PM -0700, Jeremy Fitzhardinge wrote: > On 09/21/09 13:44, Pasi K?rkk?inen wrote: > > Thanks for the fast reply. I'll ask him to try "noxsave". > > > > Other than that not much to do about it.. can't really update the F11 GA > > installer kernel.. (and I don't think doing own custom re-spin of F11 is > > good solution for him). > > > > Oh, its a domU install? You can mask it in the domain config with the > oh-so-intuitive cpuid=[] setting (leaf 1, ecx bit 26). I think that's: > > cpuid=['1:ecx=xxxxx0xxxxxxxxxxxxxxxxxxxxxxxxxx, > eax=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' ] > > (I'm assuming it works for PV as well as HVM domains.) > Hmm.. yeah. Except I think the hypervisor in RHEL5/CentOS5 is too old to support cpuid masking.. Thanks for tip anyway :) -- Pasi From jeremy at goop.org Mon Sep 21 21:42:15 2009 From: jeremy at goop.org (Jeremy Fitzhardinge) Date: Mon, 21 Sep 2009 14:42:15 -0700 Subject: [Fedora-xen] Re: [Xen-devel] Re: Fedora 11 PV Xen domU (2.6.29.4-167.fc11.x86_64) crash with invalid opcode in xsave_cntxt_init (xsetbv) In-Reply-To: <20090921213450.GW31123@reaktio.net> References: <20090921195750.GQ31123@reaktio.net> <4AB7E221.60709@goop.org> <20090921204444.GU31123@reaktio.net> <4AB7EBDB.7040108@goop.org> <20090921213450.GW31123@reaktio.net> Message-ID: <4AB7F337.2070306@goop.org> On 09/21/09 14:34, Pasi K?rkk?inen wrote: > Hmm.. yeah. Except I think the hypervisor in RHEL5/CentOS5 is too old to > support cpuid masking.. > > Thanks for tip anyway :) BIOS options to disable the feature? Install on another machine? J From m.a.young at durham.ac.uk Mon Sep 21 22:30:53 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Mon, 21 Sep 2009 23:30:53 +0100 (BST) Subject: [Fedora-xen] Dom0 kernels In-Reply-To: References: <20090414143618.GH351@redhat.com> Message-ID: Another update (kernel-2.6.31-1.2.68.xendom0.fc12) is available at http://koji.fedoraproject.org/koji/taskinfo?taskID=1691729 and via the repository http://fedorapeople.org/~myoung/dom0/ . This update switches to the xen/master branch. Michael Young From pasik at iki.fi Tue Sep 22 12:43:50 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 22 Sep 2009 15:43:50 +0300 Subject: [Fedora-xen] Re: [Xen-devel] Re: Fedora 11 PV Xen domU (2.6.29.4-167.fc11.x86_64) crash with invalid opcode in xsave_cntxt_init (xsetbv) In-Reply-To: <4AB7F337.2070306@goop.org> References: <20090921195750.GQ31123@reaktio.net> <4AB7E221.60709@goop.org> <20090921204444.GU31123@reaktio.net> <4AB7EBDB.7040108@goop.org> <20090921213450.GW31123@reaktio.net> <4AB7F337.2070306@goop.org> Message-ID: <20090922124350.GY31123@reaktio.net> On Mon, Sep 21, 2009 at 02:42:15PM -0700, Jeremy Fitzhardinge wrote: > On 09/21/09 14:34, Pasi K?rkk?inen wrote: > > Hmm.. yeah. Except I think the hypervisor in RHEL5/CentOS5 is too old to > > support cpuid masking.. > > > > Thanks for tip anyway :) > > BIOS options to disable the feature? Install on another machine? > Didn't find anything matching from BIOS.. Installing+updating on another machine is an option, since f11 updates do contain 2.6.30 kernel, and that contains the bugfix.. Thanks! -- Pasi From linuxaxx at gmail.com Tue Sep 22 15:25:32 2009 From: linuxaxx at gmail.com (Lolo Andrew) Date: Tue, 22 Sep 2009 23:25:32 +0800 Subject: [Fedora-xen] Paravirtualization - Fedora-XEN - run windows Message-ID: <60784f5e0909220825y52b688e9o316e18e06f193d30@mail.gmail.com> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From pasik at iki.fi Wed Sep 23 09:43:35 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 23 Sep 2009 12:43:35 +0300 Subject: [Fedora-xen] Paravirtualization - Fedora-XEN - run windows In-Reply-To: <60784f5e0909220825y52b688e9o316e18e06f193d30@mail.gmail.com> References: <60784f5e0909220825y52b688e9o316e18e06f193d30@mail.gmail.com> Message-ID: <20090923094335.GH31123@reaktio.net> On Tue, Sep 22, 2009 at 11:25:32PM +0800, Lolo Andrew wrote: > Dear Expert > > Got any release of Fedora-Xen that can support windows on > paravirtualization. > Windows doesn't really support Xen paravirtualization. You can run Windows only as Xen HVM (fully virtualized) guest. > 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? > First of all you need to get the Xen dom0 (host) running. Fedora 11 (and Fedora 12 rawhide) contains Xen rpms what will work, but you need xen enabled dom0 kernel in addition to that - dom0 kernel is not included in fedora atm. Take a look at for more information about missing dom0 kernel, and where to find beta rpms to try: http://fedoraproject.org/wiki/Features/XenPvopsDom0 > Like kernel, driver over the windows side, any many more, rather than having > a enterprise solution > You might want to run GPLPV drivers in Windows to boost disk/net performance. > I still newbie, I would like to have expert advice and opinion to make it be > possible. > First I recommend you to setup your dom0/host, and make sure you're able to run Linux PV (paravirtual) guests. 1) Install Fedora 11 (or even better, Fedora 12 rawhide) on the host 2) Install xen rpms 3) Install or compile Xen dom0 kernel 4) Boot into Xen 5) Make sure you're able to run and install Linux PV (Fedora/RHEL/CentOS) guests using virt-install and/or virt-manager Then after that go for running HVM windows guests. -- Pasi From pasik at iki.fi Thu Sep 24 09:06:13 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Thu, 24 Sep 2009 12:06:13 +0300 Subject: [Fedora-xen] Linux 2.6.31 domU crashes very early on RHEL5 Xen hypervisor (xen_load_gdt_boot / HYPERVISOR_update_va_mapping) Message-ID: <20090924090613.GN31123@reaktio.net> 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: [] xen_load_gdt_boot+0xab <-- [] xen_load_gdt_boot+0xab [] xen_load_gdt_boot+0xa7 [] p2m_top_index+0x9 [] switch_to_new_gdt+0x31 [] xen_start_kernel+0x282 # gdb vmlinux (gdb) x/i 0xffffffff819f8d3f 0xffffffff819f8d3f : ud2a (gdb) x/60i xen_load_gdt_boot 0xffffffff819f8c94 : push %rbp 0xffffffff819f8c95 : mov %rsp,%rbp 0xffffffff819f8c98 : push %r15 0xffffffff819f8c9a : xor %r15d,%r15d 0xffffffff819f8c9d : push %r14 0xffffffff819f8c9f : push %r13 0xffffffff819f8ca1 : push %r12 0xffffffff819f8ca3 : mov %rdi,%r12 0xffffffff819f8ca6 : push %rbx 0xffffffff819f8ca7 : sub $0x18,%rsp 0xffffffff819f8cab : movzwl (%rdi),%eax 0xffffffff819f8cae : mov 0x2(%rdi),%rbx 0xffffffff819f8cb2 : inc %eax 0xffffffff819f8cb4 : mov %eax,%r14d 0xffffffff819f8cb7 : mov %eax,-0x34(%rbp) 0xffffffff819f8cba : lea 0xfff(%r14),%rax 0xffffffff819f8cc1 : shr $0xc,%rax 0xffffffff819f8cc5 : lea 0x1e(,%rax,8),%rax 0xffffffff819f8ccd : and $0x7f0,%eax 0xffffffff819f8cd2 : sub %rax,%rsp 0xffffffff819f8cd5 : lea 0xf(%rsp),%r13 0xffffffff819f8cda : and $0xfffffffffffffff0,%r13 0xffffffff819f8cde : test $0xfff,%ebx 0xffffffff819f8ce4 : je 0xffffffff819f8d55 0xffffffff819f8ce6 : ud2a 0xffffffff819f8ce8 : jmp 0xffffffff819f8ce8 0xffffffff819f8cea : mov %rbx,%rdi 0xffffffff819f8ced : callq 0xffffffff8103ecfc <__phys_addr> 0xffffffff819f8cf2 : mov %rax,%rsi 0xffffffff819f8cf5 : shr $0xc,%rsi 0xffffffff819f8cf9 : mov %rsi,%rdi 0xffffffff819f8cfc : mov %rsi,-0x40(%rbp) 0xffffffff819f8d00 : callq 0xffffffff8100b397 0xffffffff819f8d05 : mov -0x40(%rbp),%rsi 0xffffffff819f8d09 : mov %rax,%rcx 0xffffffff819f8d0c : mov $0x8000000000000161,%rax 0xffffffff819f8d16 : and -0x1e362d(%rip),%rax # 0xffffffff818156f0 <__supported_pte_mask> 0xffffffff819f8d1d : mov %rsi,%rdi 0xffffffff819f8d20 : shl $0xc,%rdi 0xffffffff819f8d24 : or %rax,%rdi 0xffffffff819f8d27 : callq *0xffffffff8178c320 0xffffffff819f8d2e : xor %edx,%edx 0xffffffff819f8d30 : mov %rax,%rsi 0xffffffff819f8d33 : mov %rbx,%rdi 0xffffffff819f8d36 : callq 0xffffffff810091c0 0xffffffff819f8d3b : test %eax,%eax 0xffffffff819f8d3d : je 0xffffffff819f8d43 0xffffffff819f8d3f : ud2a 0xffffffff819f8d41 : jmp 0xffffffff819f8d41 0xffffffff819f8d43 : movslq %r15d,%rax 0xffffffff819f8d46 : add $0x1000,%rbx 0xffffffff819f8d4d : inc %r15d 0xffffffff819f8d50 : mov %rcx,0x0(%r13,%rax,8) 0xffffffff819f8d55 : mov %r14,%rax 0xffffffff819f8d58 : add 0x2(%r12),%rax 0xffffffff819f8d5d : cmp %rax,%rbx 0xffffffff819f8d60 : jb 0xffffffff819f8cea 0xffffffff819f8d62 : mov -0x34(%rbp),%esi 0xffffffff819f8d65 : mov %r13,%rdi 0xffffffff819f8d68 : 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 From bonzini at gnu.org Thu Sep 24 09:53:10 2009 From: bonzini at gnu.org (Paolo Bonzini) Date: Thu, 24 Sep 2009 11:53:10 +0200 Subject: [Fedora-xen] Re: Linux 2.6.31 domU crashes very early on RHEL5 Xen hypervisor (xen_load_gdt_boot / HYPERVISOR_update_va_mapping) In-Reply-To: <20090924090613.GN31123@reaktio.net> References: <20090924090613.GN31123@reaktio.net> Message-ID: <4ABB4186.5080608@gnu.org> > I also opened fedora bugzilla entry here: https://bugzilla.redhat.com/show_bug.cgi?id=525290 For the record, the corresponding RHEL bug is 524052. Paolo