xen August 2009

xen@lists.fedoraproject.org

13 participants
18 discussions

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

25 Oct '10

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

4 11

Dom0 kernels
by M A Young 13 Mar '10

13 Mar '10

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

12 99

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

21 Sep '09

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

4 29

missing xen-debuginfo-3.4.1-1.fc11.x86_64.rpm
by Jon R. 30 Aug '09

30 Aug '09

I am following Boris guide at: http://bderzhavets.wordpress.com/2009/08/20/setup-libvirt-0-7-0-6-xen-3-4-1… And after I issue the "rpmbuild -ba ./xen.spec" command and then issue the yum install xen-3.4.1-1.fc11.x86_64.rpm \ xen-debuginfo-3.4.1-1.fc11.x86_64.rpm \ xen-devel-3.4.1-1.fc11.x86_64.rpm \ xen-doc-3.4.1-1.fc11.x86_64.rpm \ xen-hypervisor-3.4.1-1.fc11.x86_64.rpm \ xen-libs-3.4.1-1.fc11.x86_64.rpm \ xen-runtime-3.4.1-1.fc11.x86_64.rpm command, I always am missing xen-debuginfo-3.4.1-1.fc11.x86_64.rpm. Is there a certain package that needs to be installed to get this rpm and can I get by without it? Thanks for any help....again :) Jon AMD64 fc11 4core proc [root@localhost x86_64]# 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 : 2210.236 cache size : 512 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc pni monitor cx16 lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs bogomips : 4420.46 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

3 4

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

30 Aug '09

When getting the pvops kernel do I still use: # git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git linux-2.6-xen # cd linux-2.6-xen # git checkout origin/rebase/master -b rebase/master And after that, do I still need Pasi's patch for pygrub? Jon

2 1

Re: [fedora-virt] Re: [Fedora-xen] Dom0 kernels
by Boris Derzhavets 27 Aug '09

27 Aug '09

Thanks for keeping vanilla kernel alive. Boris. --- On Wed, 8/26/09, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote: From: Boris Derzhavets <bderzhavets(a)yahoo.com> Subject: Re: [fedora-virt] Re: [Fedora-xen] Dom0 kernels To: fedora-xen(a)redhat.com, fedora-virt(a)redhat.com, "M A Young" <m.a.young(a)durham.ac.uk> Date: Wednesday, August 26, 2009, 9:58 AM I've made one more clean install with repo file :- [root@ServerXen341 yum.repos.d]# cat fedora-myoung-dom0.repo [myoung-dom0] name=myoung's repository of Fedora based dom0 kernels - $basearch baseurl=http://fedorapeople.org/~myoung/dom0/$basearch/ enabled=1 gpgcheck=0 [myoung-dom0-source] name=myoung's repository of Fedora based dom0 kernels - Source baseurl=http://fedorapeople.org/~myoung/dom0/src/ enabled=1 gpgcheck=0 Then tried to load kernel been built as vanilla. Console dropped into stack trace and hanged. However, kernel loads fine and works under Xen. Dmesg report under Xen stays the same ( stack trace entries ). Boris. --- On Wed, 8/26/09, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote: From: Boris Derzhavets <bderzhavets(a)yahoo.com> Subject: Re: [fedora-virt] Re: [Fedora-xen] Dom0 kernels To: fedora-xen(a)redhat.com, fedora-virt(a)redhat.com, "M A Young" <m.a.young(a)durham.ac.uk> Date: Wednesday, August 26, 2009, 7:26 AM Upstream issues looks DomU related. Kernel 2.6.31-0.1.2.58.rc7.git1.xendom0.fc11.x86_64 works stable at runtime. Boris. --- On Wed, 8/26/09, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote: From: Boris Derzhavets <bderzhavets(a)yahoo.com> Subject: Re: [fedora-virt] Re: [Fedora-xen] Dom0 kernels To: fedora-xen(a)redhat.com, fedora-virt(a)redhat.com, "M A Young" <m.a.young(a)durham.ac.uk> Cc: xen-devel(a)xensource.com Date: Wednesday, August 26, 2009, 3:58 AM Not sure how 2.6.31-0.1.2.58.rc7.git1.xendom0.fc11.x86_64 has been built. There are pretty recent ongoing issues with 2.6.31-rc7 in upstream :- http://lkml.org/lkml/2009/8/25/347 http://patchwork.kernel.org/patch/43791/ I was able to load Xen guest under 2.6.31-0.1.2.58.rc7.git1.xendom0.fc11.x86_64 followed by kernel error with sky2 (?) and loosing vnc connection to Xen Host 3.4.1 on top of F11. I'll do some more testing. Boris. --- On Wed, 8/26/09, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote: From: Boris Derzhavets <bderzhavets(a)yahoo.com> Subject: Re: [fedora-virt] Re: [Fedora-xen] Dom0 kernels To: fedora-xen(a)redhat.com, fedora-virt(a)redhat.com, "M A Young" <m.a.young(a)durham.ac.uk> Cc: xen-devel(a)xensource.com Date: Wednesday, August 26, 2009, 2:50 AM With rpm upgraded can load Dom0. However, dmesg report contains :- Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Linux version 2.6.31-0.1.2.58.rc7.git1.xendom0.fc11.x86_64 (root@ServerXenSRC) (gcc version 4.4.0 20090506 (Red Hat 4.4.0-4) (GCC) ) #1 SMP Wed Aug 26 08:14:58 MSD 2009 Command line: root=/dev/mapper/vg_serverxensrc-LogVol00 ro console=tty0 KERNEL supported cpus: Intel GenuineIntel AMD AuthenticAMD Centaur CentaurHauls BIOS-provided physical RAM map: Xen: 0000000000000000 - 000000000009ec00 (usable) Xen: 000000000009ec00 - 0000000000100000 (reserved) Xen: 0000000000100000 - 00000000cff80000 (usable) Xen: 00000000cff80000 - 00000000cff8e000 (ACPI data) Xen: 00000000cff8e000 - 00000000cffe0000 (ACPI NVS) Xen: 00000000cffe0000 - 00000000d0000000 (reserved) Xen: 00000000fee00000 - 00000000fee01000 (reserved) Xen: 00000000ffe00000 - 0000000100000000 (reserved) Xen: 0000000100000000 - 00000001f1a6b000 (usable) DMI 2.4 present. AMI BIOS detected: BIOS may corrupt low RAM, working around it. e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved) last_pfn = 0x1f1a6b max_arch_pfn = 0x400000000 last_pfn = 0xcff80 max_arch_pfn = 0x400000000 initial memory mapped : 0 - 20000000 init_memory_mapping: 0000000000000000-00000000cff80000 0000000000 - 00cff80000 page 4k kernel direct mapping tables up to cff80000 @ 100000-785000 init_memory_mapping: 0000000100000000-00000001f1a6b000 0100000000 - 01f1a6b000 page 4k . . . . . . . ====================================================== [ INFO: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected ] 2.6.31-0.1.2.58.rc7.git1.xendom0.fc11.x86_64 #1 ------------------------------------------------------ khubd/28 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire: (&retval->lock){......}, at: [<ffffffff8112a240>] dma_pool_alloc+0x45/0x321 and this task is already holding: (&ehci->lock){-.....}, at: [<ffffffff813d4654>] ehci_urb_enqueue+0xb4/0xd5c which would create a new lock dependency: (&ehci->lock){-.....} -> (&retval->lock){......} but this new dependency connects a HARDIRQ-irq-safe lock: (&ehci->lock){-.....} ... which became HARDIRQ-irq-safe at: [<ffffffff8109908b>] __lock_acquire+0x254/0xc0e [<ffffffff81099b33>] lock_acquire+0xee/0x12e [<ffffffff8150b987>] _spin_lock+0x45/0x8e [<ffffffff813d325c>] ehci_irq+0x41/0x441 [<ffffffff813b7e5f>] usb_hcd_irq+0x59/0xcc [<ffffffff810ca810>] handle_IRQ_event+0x62/0x148 [<ffffffff810ccda3>] handle_level_irq+0x90/0xf9 [<ffffffff81017078>] handle_irq+0x9a/0xba [<ffffffff8130a0c6>] xen_evtchn_do_upcall+0x10c/0x1bd [<ffffffff8101527e>] xen_do_hypervisor_callback+0x1e/0x30 [<ffffffffffffffff>] 0xffffffffffffffff to a HARDIRQ-irq-unsafe lock: (purge_lock){+.+...} ... which became HARDIRQ-irq-unsafe at: ... [<ffffffff810990ff>] __lock_acquire+0x2c8/0xc0e [<ffffffff81099b33>] lock_acquire+0xee/0x12e [<ffffffff8150b987>] _spin_lock+0x45/0x8e [<ffffffff811233a4>] __purge_vmap_area_lazy+0x63/0x198 [<ffffffff81124c74>] vm_unmap_aliases+0x18f/0x1b2 [<ffffffff8100eeb3>] xen_alloc_ptpage+0x5a/0xa0 [<ffffffff8100ef97>] xen_alloc_pte+0x26/0x3c [<ffffffff81118381>] __pte_alloc_kernel+0x6f/0xdd [<ffffffff811241a1>] vmap_page_range_noflush+0x1c5/0x315 [<ffffffff81124332>] map_vm_area+0x41/0x6b [<ffffffff8112448b>] __vmalloc_area_node+0x12f/0x167 [<ffffffff81124553>] __vmalloc_node+0x90/0xb5 [<ffffffff811243c8>] __vmalloc_area_node+0x6c/0x167 [<ffffffff81124553>] __vmalloc_node+0x90/0xb5 [<ffffffff811247ca>] __vmalloc+0x28/0x3e [<ffffffff818504c9>] alloc_large_system_hash+0x12f/0x1fb [<ffffffff81852b4e>] vfs_caches_init+0xb8/0x140 [<ffffffff8182b061>] start_kernel+0x3ef/0x44c [<ffffffff8182a2d0>] x86_64_start_reservations+0xbb/0xd6 [<ffffffff8182e6d1>] xen_start_kernel+0x5ab/0x5b2 [<ffffffffffffffff>] 0xffffffffffffffff other info that might help us debug this: 2 locks held by khubd/28: #0: (usb_address0_mutex){+.+...}, at: [<ffffffff813b2e82>] hub_port_init+0x8c/0x7ee #1: (&ehci->lock){-.....}, at: [<ffffffff813d4654>] ehci_urb_enqueue+0xb4/0xd5c the HARDIRQ-irq-safe lock's dependencies: -> (&ehci->lock){-.....} ops: 0 { IN-HARDIRQ-W at: [<ffffffff8109908b>] __lock_acquire+0x254/0xc0e [<ffffffff81099b33>] lock_acquire+0xee/0x12e [<ffffffff8150b987>] _spin_lock+0x45/0x8e [<ffffffff813d325c>] ehci_irq+0x41/0x441 [<ffffffff813b7e5f>] usb_hcd_irq+0x59/0xcc [<ffffffff810ca810>] handle_IRQ_event+0x62/0x148 [<ffffffff810ccda3>] handle_level_irq+0x90/0xf9 . . . . . . Jeremy's current version is rc6. I believe this issue has been noticed at xen-devel. Boris -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen

1 0

Re: [fedora-virt] Re: [Fedora-xen] Dom0 kernels
by Boris Derzhavets 26 Aug '09

26 Aug '09

I've made one more clean install with repo file :- [root@ServerXen341 yum.repos.d]# cat fedora-myoung-dom0.repo [myoung-dom0] name=myoung's repository of Fedora based dom0 kernels - $basearch baseurl=http://fedorapeople.org/~myoung/dom0/$basearch/ enabled=1 gpgcheck=0 [myoung-dom0-source] name=myoung's repository of Fedora based dom0 kernels - Source baseurl=http://fedorapeople.org/~myoung/dom0/src/ enabled=1 gpgcheck=0 Then tried to load kernel been built as vanilla. Console dropped into stack trace and hanged. However, kernel loads fine and works under Xen. Dmesg report under Xen stays the same ( stack trace entries ). Boris. --- On Wed, 8/26/09, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote: From: Boris Derzhavets <bderzhavets(a)yahoo.com> Subject: Re: [fedora-virt] Re: [Fedora-xen] Dom0 kernels To: fedora-xen(a)redhat.com, fedora-virt(a)redhat.com, "M A Young" <m.a.young(a)durham.ac.uk> Date: Wednesday, August 26, 2009, 7:26 AM Upstream issues looks DomU related. Kernel 2.6.31-0.1.2.58.rc7.git1.xendom0.fc11.x86_64 works stable at runtime. Boris. --- On Wed, 8/26/09, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote: From: Boris Derzhavets <bderzhavets(a)yahoo.com> Subject: Re: [fedora-virt] Re: [Fedora-xen] Dom0 kernels To: fedora-xen(a)redhat.com, fedora-virt(a)redhat.com, "M A Young" <m.a.young(a)durham.ac.uk> Cc: xen-devel(a)xensource.com Date: Wednesday, August 26, 2009, 3:58 AM Not sure how 2.6.31-0.1.2.58.rc7.git1.xendom0.fc11.x86_64 has been built. There are pretty recent ongoing issues with 2.6.31-rc7 in upstream :- http://lkml.org/lkml/2009/8/25/347 http://patchwork.kernel.org/patch/43791/ I was able to load Xen guest under 2.6.31-0.1.2.58.rc7.git1.xendom0.fc11.x86_64 followed by kernel error with sky2 (?) and loosing vnc connection to Xen Host 3.4.1 on top of F11. I'll do some more testing. Boris. --- On Wed, 8/26/09, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote: From: Boris Derzhavets <bderzhavets(a)yahoo.com> Subject: Re: [fedora-virt] Re: [Fedora-xen] Dom0 kernels To: fedora-xen(a)redhat.com, fedora-virt(a)redhat.com, "M A Young" <m.a.young(a)durham.ac.uk> Cc: xen-devel(a)xensource.com Date: Wednesday, August 26, 2009, 2:50 AM With rpm upgraded can load Dom0. However, dmesg report contains :- Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Linux version 2.6.31-0.1.2.58.rc7.git1.xendom0.fc11.x86_64 (root@ServerXenSRC) (gcc version 4.4.0 20090506 (Red Hat 4.4.0-4) (GCC) ) #1 SMP Wed Aug 26 08:14:58 MSD 2009 Command line: root=/dev/mapper/vg_serverxensrc-LogVol00 ro console=tty0 KERNEL supported cpus: Intel GenuineIntel AMD AuthenticAMD Centaur CentaurHauls BIOS-provided physical RAM map: Xen: 0000000000000000 - 000000000009ec00 (usable) Xen: 000000000009ec00 - 0000000000100000 (reserved) Xen: 0000000000100000 - 00000000cff80000 (usable) Xen: 00000000cff80000 - 00000000cff8e000 (ACPI data) Xen: 00000000cff8e000 - 00000000cffe0000 (ACPI NVS) Xen: 00000000cffe0000 - 00000000d0000000 (reserved) Xen: 00000000fee00000 - 00000000fee01000 (reserved) Xen: 00000000ffe00000 - 0000000100000000 (reserved) Xen: 0000000100000000 - 00000001f1a6b000 (usable) DMI 2.4 present. AMI BIOS detected: BIOS may corrupt low RAM, working around it. e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved) last_pfn = 0x1f1a6b max_arch_pfn = 0x400000000 last_pfn = 0xcff80 max_arch_pfn = 0x400000000 initial memory mapped : 0 - 20000000 init_memory_mapping: 0000000000000000-00000000cff80000 0000000000 - 00cff80000 page 4k kernel direct mapping tables up to cff80000 @ 100000-785000 init_memory_mapping: 0000000100000000-00000001f1a6b000 0100000000 - 01f1a6b000 page 4k . . . . . . . ====================================================== [ INFO: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected ] 2.6.31-0.1.2.58.rc7.git1.xendom0.fc11.x86_64 #1 ------------------------------------------------------ khubd/28 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire: (&retval->lock){......}, at: [<ffffffff8112a240>] dma_pool_alloc+0x45/0x321 and this task is already holding: (&ehci->lock){-.....}, at: [<ffffffff813d4654>] ehci_urb_enqueue+0xb4/0xd5c which would create a new lock dependency: (&ehci->lock){-.....} -> (&retval->lock){......} but this new dependency connects a HARDIRQ-irq-safe lock: (&ehci->lock){-.....} ... which became HARDIRQ-irq-safe at: [<ffffffff8109908b>] __lock_acquire+0x254/0xc0e [<ffffffff81099b33>] lock_acquire+0xee/0x12e [<ffffffff8150b987>] _spin_lock+0x45/0x8e [<ffffffff813d325c>] ehci_irq+0x41/0x441 [<ffffffff813b7e5f>] usb_hcd_irq+0x59/0xcc [<ffffffff810ca810>] handle_IRQ_event+0x62/0x148 [<ffffffff810ccda3>] handle_level_irq+0x90/0xf9 [<ffffffff81017078>] handle_irq+0x9a/0xba [<ffffffff8130a0c6>] xen_evtchn_do_upcall+0x10c/0x1bd [<ffffffff8101527e>] xen_do_hypervisor_callback+0x1e/0x30 [<ffffffffffffffff>] 0xffffffffffffffff to a HARDIRQ-irq-unsafe lock: (purge_lock){+.+...} ... which became HARDIRQ-irq-unsafe at: ... [<ffffffff810990ff>] __lock_acquire+0x2c8/0xc0e [<ffffffff81099b33>] lock_acquire+0xee/0x12e [<ffffffff8150b987>] _spin_lock+0x45/0x8e [<ffffffff811233a4>] __purge_vmap_area_lazy+0x63/0x198 [<ffffffff81124c74>] vm_unmap_aliases+0x18f/0x1b2 [<ffffffff8100eeb3>] xen_alloc_ptpage+0x5a/0xa0 [<ffffffff8100ef97>] xen_alloc_pte+0x26/0x3c [<ffffffff81118381>] __pte_alloc_kernel+0x6f/0xdd [<ffffffff811241a1>] vmap_page_range_noflush+0x1c5/0x315 [<ffffffff81124332>] map_vm_area+0x41/0x6b [<ffffffff8112448b>] __vmalloc_area_node+0x12f/0x167 [<ffffffff81124553>] __vmalloc_node+0x90/0xb5 [<ffffffff811243c8>] __vmalloc_area_node+0x6c/0x167 [<ffffffff81124553>] __vmalloc_node+0x90/0xb5 [<ffffffff811247ca>] __vmalloc+0x28/0x3e [<ffffffff818504c9>] alloc_large_system_hash+0x12f/0x1fb [<ffffffff81852b4e>] vfs_caches_init+0xb8/0x140 [<ffffffff8182b061>] start_kernel+0x3ef/0x44c [<ffffffff8182a2d0>] x86_64_start_reservations+0xbb/0xd6 [<ffffffff8182e6d1>] xen_start_kernel+0x5ab/0x5b2 [<ffffffffffffffff>] 0xffffffffffffffff other info that might help us debug this: 2 locks held by khubd/28: #0: (usb_address0_mutex){+.+...}, at: [<ffffffff813b2e82>] hub_port_init+0x8c/0x7ee #1: (&ehci->lock){-.....}, at: [<ffffffff813d4654>] ehci_urb_enqueue+0xb4/0xd5c the HARDIRQ-irq-safe lock's dependencies: -> (&ehci->lock){-.....} ops: 0 { IN-HARDIRQ-W at: [<ffffffff8109908b>] __lock_acquire+0x254/0xc0e [<ffffffff81099b33>] lock_acquire+0xee/0x12e [<ffffffff8150b987>] _spin_lock+0x45/0x8e [<ffffffff813d325c>] ehci_irq+0x41/0x441 [<ffffffff813b7e5f>] usb_hcd_irq+0x59/0xcc [<ffffffff810ca810>] handle_IRQ_event+0x62/0x148 [<ffffffff810ccda3>] handle_level_irq+0x90/0xf9 . . . . . . Jeremy's current version is rc6. I believe this issue has been noticed at xen-devel. Boris -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen

1 0

Re: [fedora-virt] Re: [Fedora-xen] Dom0 kernels
by Boris Derzhavets 26 Aug '09

26 Aug '09

With rpm upgraded can load Dom0. However, dmesg report contains :- Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Linux version 2.6.31-0.1.2.58.rc7.git1.xendom0.fc11.x86_64 (root@ServerXenSRC) (gcc version 4.4.0 20090506 (Red Hat 4.4.0-4) (GCC) ) #1 SMP Wed Aug 26 08:14:58 MSD 2009 Command line: root=/dev/mapper/vg_serverxensrc-LogVol00 ro console=tty0 KERNEL supported cpus: Intel GenuineIntel AMD AuthenticAMD Centaur CentaurHauls BIOS-provided physical RAM map: Xen: 0000000000000000 - 000000000009ec00 (usable) Xen: 000000000009ec00 - 0000000000100000 (reserved) Xen: 0000000000100000 - 00000000cff80000 (usable) Xen: 00000000cff80000 - 00000000cff8e000 (ACPI data) Xen: 00000000cff8e000 - 00000000cffe0000 (ACPI NVS) Xen: 00000000cffe0000 - 00000000d0000000 (reserved) Xen: 00000000fee00000 - 00000000fee01000 (reserved) Xen: 00000000ffe00000 - 0000000100000000 (reserved) Xen: 0000000100000000 - 00000001f1a6b000 (usable) DMI 2.4 present. AMI BIOS detected: BIOS may corrupt low RAM, working around it. e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved) last_pfn = 0x1f1a6b max_arch_pfn = 0x400000000 last_pfn = 0xcff80 max_arch_pfn = 0x400000000 initial memory mapped : 0 - 20000000 init_memory_mapping: 0000000000000000-00000000cff80000 0000000000 - 00cff80000 page 4k kernel direct mapping tables up to cff80000 @ 100000-785000 init_memory_mapping: 0000000100000000-00000001f1a6b000 0100000000 - 01f1a6b000 page 4k . . . . . . . ====================================================== [ INFO: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected ] 2.6.31-0.1.2.58.rc7.git1.xendom0.fc11.x86_64 #1 ------------------------------------------------------ khubd/28 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire: (&retval->lock){......}, at: [<ffffffff8112a240>] dma_pool_alloc+0x45/0x321 and this task is already holding: (&ehci->lock){-.....}, at: [<ffffffff813d4654>] ehci_urb_enqueue+0xb4/0xd5c which would create a new lock dependency: (&ehci->lock){-.....} -> (&retval->lock){......} but this new dependency connects a HARDIRQ-irq-safe lock: (&ehci->lock){-.....} ... which became HARDIRQ-irq-safe at: [<ffffffff8109908b>] __lock_acquire+0x254/0xc0e [<ffffffff81099b33>] lock_acquire+0xee/0x12e [<ffffffff8150b987>] _spin_lock+0x45/0x8e [<ffffffff813d325c>] ehci_irq+0x41/0x441 [<ffffffff813b7e5f>] usb_hcd_irq+0x59/0xcc [<ffffffff810ca810>] handle_IRQ_event+0x62/0x148 [<ffffffff810ccda3>] handle_level_irq+0x90/0xf9 [<ffffffff81017078>] handle_irq+0x9a/0xba [<ffffffff8130a0c6>] xen_evtchn_do_upcall+0x10c/0x1bd [<ffffffff8101527e>] xen_do_hypervisor_callback+0x1e/0x30 [<ffffffffffffffff>] 0xffffffffffffffff to a HARDIRQ-irq-unsafe lock: (purge_lock){+.+...} ... which became HARDIRQ-irq-unsafe at: ... [<ffffffff810990ff>] __lock_acquire+0x2c8/0xc0e [<ffffffff81099b33>] lock_acquire+0xee/0x12e [<ffffffff8150b987>] _spin_lock+0x45/0x8e [<ffffffff811233a4>] __purge_vmap_area_lazy+0x63/0x198 [<ffffffff81124c74>] vm_unmap_aliases+0x18f/0x1b2 [<ffffffff8100eeb3>] xen_alloc_ptpage+0x5a/0xa0 [<ffffffff8100ef97>] xen_alloc_pte+0x26/0x3c [<ffffffff81118381>] __pte_alloc_kernel+0x6f/0xdd [<ffffffff811241a1>] vmap_page_range_noflush+0x1c5/0x315 [<ffffffff81124332>] map_vm_area+0x41/0x6b [<ffffffff8112448b>] __vmalloc_area_node+0x12f/0x167 [<ffffffff81124553>] __vmalloc_node+0x90/0xb5 [<ffffffff811243c8>] __vmalloc_area_node+0x6c/0x167 [<ffffffff81124553>] __vmalloc_node+0x90/0xb5 [<ffffffff811247ca>] __vmalloc+0x28/0x3e [<ffffffff818504c9>] alloc_large_system_hash+0x12f/0x1fb [<ffffffff81852b4e>] vfs_caches_init+0xb8/0x140 [<ffffffff8182b061>] start_kernel+0x3ef/0x44c [<ffffffff8182a2d0>] x86_64_start_reservations+0xbb/0xd6 [<ffffffff8182e6d1>] xen_start_kernel+0x5ab/0x5b2 [<ffffffffffffffff>] 0xffffffffffffffff other info that might help us debug this: 2 locks held by khubd/28: #0: (usb_address0_mutex){+.+...}, at: [<ffffffff813b2e82>] hub_port_init+0x8c/0x7ee #1: (&ehci->lock){-.....}, at: [<ffffffff813d4654>] ehci_urb_enqueue+0xb4/0xd5c the HARDIRQ-irq-safe lock's dependencies: -> (&ehci->lock){-.....} ops: 0 { IN-HARDIRQ-W at: [<ffffffff8109908b>] __lock_acquire+0x254/0xc0e [<ffffffff81099b33>] lock_acquire+0xee/0x12e [<ffffffff8150b987>] _spin_lock+0x45/0x8e [<ffffffff813d325c>] ehci_irq+0x41/0x441 [<ffffffff813b7e5f>] usb_hcd_irq+0x59/0xcc [<ffffffff810ca810>] handle_IRQ_event+0x62/0x148 [<ffffffff810ccda3>] handle_level_irq+0x90/0xf9 . . . . . . Jeremy's current version is rc6. I believe this issue has been noticed at xen-devel. Boris

1 2

libvir: Xen error : Domain not found: xenUnifiedDomainLookupByID while virt-installing rawhide
by Pasi Kärkkäinen 24 Aug '09

24 Aug '09

Hello again! I'm running Fedora 11 with 2.6.31-rc6 pv_ops Xen dom0 kernel and Xen 3.4.1. I'm able to succesfully install Fedora 11 and CentOS 5.3 PV guests with virt-install. I just tried installing Fedora rawhide (F12) guest with virt-install, and the installation fails. # virt-install --debug -n test3vm -r 512 --vcpus=1 -f /dev/vg_dom0test/test3vm --vnc -p -l "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/developme…" Log of the virt-install output available here: http://pasik.reaktio.net/fedora/virt-install-log-rawhide-on-f11.txt Basicly it creates the domain, but it fails to start: # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 986 2 r----- 595.1 test3vm 512 1 0.0 and virt-install gives these errors: libvir: Xen error : Domain not found: xenUnifiedDomainLookupByID libvir: Xen error : Domain not found: xenUnifiedDomainLookupByName Those are printed repeatedly over and over again.. until I cancel the installation with ctrl+c. Any ideas how to debug that? Some more debug info ("xm list --long test3vm" and "xenstore-ls") available from here: http://pasik.reaktio.net/fedora/virt-install-rawhide-on-f11-debuginfo.txt -- Pasi

4 17

Re: [Fedora-xen] BZIP2 and LZMA support patch for Xen PV domU bootloader
by Boris Derzhavets 24 Aug '09

24 Aug '09

Virt-install F12 PV hangs on 64-bit. Report attached. Boris. --- On Sun, 8/23/09, Pasi Kärkkäinen <pasik(a)iki.fi> wrote: From: Pasi Kärkkäinen <pasik(a)iki.fi> Subject: Re: [Fedora-xen] BZIP2 and LZMA support patch for Xen PV domU bootloader To: "Mark McLoughlin" <markmc(a)redhat.com> Cc: fedora-xen(a)redhat.com Date: Sunday, August 23, 2009, 12:45 PM On Thu, Aug 20, 2009 at 10:04:09PM +0300, Pasi Kärkkäinen wrote: > On Thu, Aug 20, 2009 at 07:02:12PM +0100, Mark McLoughlin wrote: > > On Thu, 2009-08-20 at 19:44 +0300, Pasi Kärkkäinen wrote: > > > On Thu, Aug 20, 2009 at 05:05:17PM +0100, Mark McLoughlin wrote: > > > > On Thu, 2009-08-20 at 18:41 +0300, Pasi Kärkkäinen wrote: > > > > > > > > > # CONFIG_KERNEL_GZIP is not set > > > > > # CONFIG_KERNEL_BZIP2 is not set > > > > > CONFIG_KERNEL_LZMA=y > > > > > > > > > > OK, so the problem is the rawhide kernel is LZMA compressed. Wasn't this > > > > > changed back to GZIP earlier? > > > > > > > > Thanks for pointing that out, see: > > > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=515831 > > > > > > > > It got disabled on a branch for the F12 Alpha release, but never got > > > > disabled on the devel/ branch. Should be fixed now. > > > > > > > > > > Thanks. Now I'll just wait for the next kernel build.. :) > > > > > > (or try applying the patch Chris sent to support BZIP2 and LZMA for Xen PV bootloader). > > > > Testing Chris's patch would certainly be a good idea. LZMA will come > > back again in Fedora 13, so we should make sure to have the patch in > > good shape by then > > > > I actually already 'ported' the patch to Xen 3.4.1 and made sure it > compiles OK. I've included it (and extra gcc 4.4.0 compilefix) to this > email, and also sent them to xen-devel. > > atm I'm trying to make the patch work/apply with Fedora xen-3.4.1-1 src.rpm .. > and sorting out some fedora/rpm specific compilation failure.. > Here's updated patch that actually works. I added it to xen-3.4.1-1.src.rpm and verified the resulting rpms are able to boot lzma compressed kernels. It's still not final patch, since the stubdom/pvgrub bzip2/lzma support is not yet included in this patch (until the proper method for Makefile hacks is determined upstream). -- Pasi -----Inline Attachment Follows----- -- Fedora-xen mailing list Fedora-xen(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen

1 0

Still can't boot Fedora rawhide xen with EL5
by Orion Poplawski 23 Aug '09

23 Aug '09

Getting different error now without LZMA: Starting install... Retrieving file .treeinfo... | 1.2 kB 00:00 Retrieving file .treeinfo... | 1.2 kB 00:00 Retrieving file vmlinuz... | 3.5 MB 00:00 Retrieving file initrd.img... | 22 MB 00:01 Creating domain... | 0 B 00:01 ERROR: It appears that your installation has crashed. You should be able to find more information in the logs [2009-08-12 09:52:30 xend.XendDomainInfo 3214] DEBUG (XendDomainInfo:200) XendDomainInfo.create(['vm', ['name', 'xenfdev64'], ['memory', '512'], ['maxmem', '512'], ['vcpus', '1'], ['uuid', '7579b650-65c7-5baa-0bc0-3502da28df6c'], ['on_poweroff', 'destroy'], ['on_reboot', 'destroy'], ['on_crash', 'destroy'], ['image', ['linux', ['kernel', '/var/lib/xen/virtinst-vmlinuz.h8bkQS'], ['ramdisk', '/var/lib/xen/virtinst-initrd.img.yoWzKP'], ['args', 'ks=http://sw.cora.nwra.com/ks/rawhide-nox64.cfg method=http://fedora.cora.nwra.com/fedora/linux/development/x86_64/os']]], ['device', ['vbd', ['dev', 'xvda'], ['uname', 'phy:/dev/rootvg/xenfdev64'], ['mode', 'w']]], ['device', ['vif', ['mac', '40:00:00:00:00:03'], ['bridge', 'xenbr0']]], ['device', ['vkbd']], ['device', ['vfb', ['type', 'vnc'], ['vncunused', '1']]]]) [2009-08-12 09:52:30 xend.XendDomainInfo 3214] DEBUG (XendDomainInfo:312) parseConfig: config is ['vm', ['name', 'xenfdev64'], ['memory', '512'], ['maxmem', '512'], ['vcpus', '1'], ['uuid', '7579b650-65c7-5baa-0bc0-3502da28df6c'], ['on_poweroff', 'destroy'], ['on_reboot', 'destroy'], ['on_crash', 'destroy'], ['image', ['linux', ['kernel', '/var/lib/xen/virtinst-vmlinuz.h8bkQS'], ['ramdisk', '/var/lib/xen/virtinst-initrd.img.yoWzKP'], ['args', 'ks=http://sw.cora.nwra.com/ks/rawhide-nox64.cfg method=http://fedora.cora.nwra.com/fedora/linux/development/x86_64/os']]], ['device', ['vbd', ['dev', 'xvda'], ['uname', 'phy:/dev/rootvg/xenfdev64'], ['mode', 'w']]], ['device', ['vif', ['mac', '40:00:00:00:00:03'], ['bridge', 'xenbr0']]], ['device', ['vkbd']], ['device', ['vfb', ['type', 'vnc'], ['vncunused', '1']]]] [2009-08-12 09:52:30 xend.XendDomainInfo 3214] DEBUG (XendDomainInfo:417) parseConfig: result is {'shadow_memory': None, 'start_time': None, 'uuid': '7579b650-65c7-5baa-0bc0-3502da28df6c', 'on_crash': 'destroy', 'on_reboot': 'destroy', 'localtime': None, 'image': ['linux', ['kernel', '/var/lib/xen/virtinst-vmlinuz.h8bkQS'], ['ramdisk', '/var/lib/xen/virtinst-initrd.img.yoWzKP'], ['args', 'ks=http://sw.cora.nwra.com/ks/rawhide-nox64.cfg method=http://fedora.cora.nwra.com/fedora/linux/development/x86_64/os']], 'on_poweroff': 'destroy', 'bootloader_args': None, 'cpus': None, 'name': 'xenfdev64', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'features': None, 'vcpu_avail': None, 'memory': 512, 'device': [('vbd', ['vbd', ['dev', 'xvda'], ['uname', 'phy:/dev/rootvg/xenfdev64'], ['mode', 'w']]), ('vif', ['vif', ['mac', '40:00:00:00:00:03'], ['bridge', 'xenbr0']]), ('vkbd', ['vkbd']), ('vfb', ['vfb', ['type', 'vnc'], ['vncunused', '1']])], 'bootloader': None, 'cpu': None, 'maxmem': 512} [2009-08-12 09:52:30 xend.XendDomainInfo 3214] DEBUG (XendDomainInfo:1427) XendDomainInfo.construct: None [2009-08-12 09:52:30 xend 3214] DEBUG (balloon:143) Balloon: 525032 KiB free; need 2048; done. [2009-08-12 09:52:30 xend.XendDomainInfo 3214] DEBUG (XendDomainInfo:1475) XendDomainInfo.initDomain: 20 1.0 [2009-08-12 09:52:30 xend.XendDomainInfo 3214] DEBUG (XendDomainInfo:1514) _initDomain:shadow_memory=0x0, maxmem=0x200, memory=0x200. [2009-08-12 09:52:30 xend 3214] DEBUG (balloon:143) Balloon: 525024 KiB free; need 524288; done. [2009-08-12 09:52:30 xend 3214] INFO (image:137) buildDomain os=linux dom=20 vcpus=1 [2009-08-12 09:52:30 xend 3214] DEBUG (image:206) domid = 20 [2009-08-12 09:52:30 xend 3214] DEBUG (image:207) memsize = 512 [2009-08-12 09:52:30 xend 3214] DEBUG (image:208) image = /var/lib/xen/virtinst-vmlinuz.h8bkQS [2009-08-12 09:52:30 xend 3214] DEBUG (image:209) store_evtchn = 1 [2009-08-12 09:52:30 xend 3214] DEBUG (image:210) console_evtchn = 2 [2009-08-12 09:52:30 xend 3214] DEBUG (image:211) cmdline = ks=http://sw.cora.nwra.com/ks/rawhide-nox64.cfg method=http://fedora.cora.nwra.com/fedora/linux/development/x86_64/os [2009-08-12 09:52:30 xend 3214] DEBUG (image:212) ramdisk = /var/lib/xen/virtinst-initrd.img.yoWzKP [2009-08-12 09:52:30 xend 3214] DEBUG (image:213) vcpus = 1 [2009-08-12 09:52:30 xend 3214] DEBUG (image:214) features = [2009-08-12 09:52:30 xend 3214] DEBUG (DevController:110) DevController: writing {'protocol': 'x86_64-abi', 'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vkbd/20/0'} to /local/domain/20/device/vkbd/0. [2009-08-12 09:52:30 xend 3214] DEBUG (DevController:112) DevController: writing {'frontend-id': '20', 'domain': 'xenfdev64', 'frontend': '/local/domain/20/device/vkbd/0', 'state': '1', 'online': '1'} to /local/domain/0/backend/vkbd/20/0. [2009-08-12 09:52:30 xend 3214] DEBUG (blkif:27) exception looking up device number for xvda: [Errno 2] No such file or directory: '/dev/xvda' [2009-08-12 09:52:30 xend 3214] DEBUG (DevController:110) DevController: writing {'virtual-device': '51712', 'device-type': 'disk', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/20/51712'} to /local/domain/20/device/vbd/51712. [2009-08-12 09:52:30 xend 3214] DEBUG (DevController:112) DevController: writing {'domain': 'xenfdev64', 'frontend': '/local/domain/20/device/vbd/51712', 'format': 'raw', 'dev': 'xvda', 'state': '1', 'params': '/dev/rootvg/xenfdev64', 'mode': 'w', 'online': '1', 'frontend-id': '20', 'type': 'phy'} to /local/domain/0/backend/vbd/20/51712. [2009-08-12 09:52:30 xend 3214] DEBUG (DevController:110) DevController: writing {'mac': '40:00:00:00:00:03', 'handle': '0', 'protocol': 'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/20/0'} to /local/domain/20/device/vif/0. [2009-08-12 09:52:30 xend 3214] DEBUG (DevController:112) DevController: writing {'bridge': 'xenbr0', 'domain': 'xenfdev64', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/20/device/vif/0', 'mac': '40:00:00:00:00:03', 'online': '1', 'frontend-id': '20'} to /local/domain/0/backend/vif/20/0. [2009-08-12 09:52:30 xend 3214] DEBUG (DevController:110) DevController: writing {'protocol': 'x86_64-abi', 'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vfb/20/0'} to /local/domain/20/device/vfb/0. [2009-08-12 09:52:30 xend 3214] DEBUG (DevController:112) DevController: writing {'vncunused': '1', 'domain': 'xenfdev64', 'frontend': '/local/domain/20/device/vfb/0', 'online': '1', 'frontend-id': '20', 'type': 'vnc', 'state': '1'} to /local/domain/0/backend/vfb/20/0. [2009-08-12 09:52:30 xend 3214] DEBUG (vfbif:70) No VNC passwd configured for vfb access [2009-08-12 09:52:30 xend 3214] DEBUG (vfbif:11) Spawn: ['/usr/lib64/xen/bin/qemu-dm', '-M', 'xenpv', '-d', '20', '-domain-name', 'xenfdev64', '-vnc', '127.0.0.1:0', '-vncunused'] [2009-08-12 09:52:30 xend.XendDomainInfo 3214] DEBUG (XendDomainInfo:797) Storing VM details: {'shadow_memory': '0', 'uuid': '7579b650-65c7-5baa-0bc0-3502da28df6c', 'on_reboot': 'destroy', 'start_time': '1250092350.98', 'on_poweroff': 'destroy', 'name': 'xenfdev64', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '512', 'on_crash': 'destroy', 'image': "(linux (kernel /var/lib/xen/virtinst-vmlinuz.h8bkQS) (ramdisk /var/lib/xen/virtinst-initrd.img.yoWzKP) (args 'ks=http://sw.cora.nwra.com/ks/rawhide-nox64.cfg method=http://fedora.cora.nwra.com/fedora/linux/development/x86_64/os'))", 'maxmem': '512'} [2009-08-12 09:52:30 xend.XendDomainInfo 3214] DEBUG (XendDomainInfo:832) Storing domain details: {'console/ring-ref': '676374', 'console/port': '2', 'name': 'xenfdev64', 'console/limit': '1048576', 'vm': '/vm/7579b650-65c7-5baa-0bc0-3502da28df6c', 'domid': '20', 'cpu/0/availability': 'online', 'memory/target': '524288', 'store/ring-ref': '676375', 'store/port': '1'} [2009-08-12 09:52:31 xend.XendDomainInfo 3214] DEBUG (XendDomainInfo:1036) XendDomainInfo.handleShutdownWatch [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:154) Waiting for devices vif. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:160) Waiting for 0. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:496) hotplugStatusCallback /local/domain/0/backend/vif/20/0/hotplug-status. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:496) hotplugStatusCallback /local/domain/0/backend/vif/20/0/hotplug-status. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:510) hotplugStatusCallback 1. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:154) Waiting for devices usb. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:154) Waiting for devices vbd. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:160) Waiting for 51712. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:496) hotplugStatusCallback /local/domain/0/backend/vbd/20/51712/hotplug-status. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:496) hotplugStatusCallback /local/domain/0/backend/vbd/20/51712/hotplug-status. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:510) hotplugStatusCallback 1. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:154) Waiting for devices irq. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:154) Waiting for devices vkbd. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:160) Waiting for 0. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:496) hotplugStatusCallback /local/domain/0/backend/vkbd/20/0/hotplug-status. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:510) hotplugStatusCallback 1. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:154) Waiting for devices vfb. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:160) Waiting for 0. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:496) hotplugStatusCallback /local/domain/0/backend/vfb/20/0/hotplug-status. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:510) hotplugStatusCallback 1. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:154) Waiting for devices pci. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:154) Waiting for devices ioports. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:154) Waiting for devices tap. [2009-08-12 09:52:31 xend 3214] DEBUG (DevController:154) Waiting for devices vtpm. [2009-08-12 09:52:31 xend 3214] INFO (XendDomain:380) Domain xenfdev64 (20) unpaused. [2009-08-12 09:52:31 xend.XendDomainInfo 3214] WARNING (XendDomainInfo:965) Domain has crashed: name=xenfdev64 id=20. [2009-08-12 09:52:31 xend.XendDomainInfo 3214] DEBUG (XendDomainInfo:1637) XendDomainInfo.destroy: domid=20 [2009-08-12 09:52:31 xend.XendDomainInfo 3214] WARNING (XendDomainInfo:965) Domain has crashed: name=xenfdev64 id=20. [2009-08-12 09:52:31 xend.XendDomainInfo 3214] DEBUG (XendDomainInfo:1637) XendDomainInfo.destroy: domid=20 [2009-08-12 09:52:31 xend.XendDomainInfo 3214] ERROR (XendDomainInfo:1645) XendDomainInfo.destroy: xc.domain_destroy failed. Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1643, in destroy xc.domain_destroy(self.domid) Error: (3, 'No such process') -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion(a)cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com

3 4

qemu-kvm glibc memory corruption?
by Tom Horsley 20 Aug '09

20 Aug '09

I added this bugzilla earlier today: https://bugzilla.redhat.com/show_bug.cgi?id=518476 Just curious if anyone else has ever seen qemu-kvm get a glibc memory corruption error? Seems to be related to the ubuntu virtual machine specifically - my theory is ubuntu does some kind of weird video mode twddling that affects it.

1 0

Fedora 11 Xen domU grub.conf timeout=0 problem with pygrub
by Pasi Kärkkäinen 20 Aug '09

20 Aug '09

Hello, I just installed Fedora 11 Xen PV domU on Fedora 11 Xen dom0, using virt-install like this: virt-install -n testvm -r 512 --vcpus=1 -f /dev/vg_dom0test/testvm --vnc -p -l "ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/releases/…" Installation goes fine, but after the installation is complete, and the domU gets rebooted, it will never come up again. I tried multiple times, and it's always the same. Installation starts and works fine, but after installation domU doesn't start anymore - not even after "xm destroy" and "xm start". I started investigating the problem, and from "xm log" I noticed the last line of output is about starting pygrub and nothing after that. I checked "ps aux" and noticed pygrub is there, waiting for something. "strace -p" shows it's waiting for something, and checking the status all the time. I tried running the same pygrub command from cmdline, and noticed I have to press enter before the kernel gets chosen by pygrub. After pressing enter pygrub copies the kernel/initrd/configuration and exists OK. I echoed the config from manual pygrub run to /var/run/xend/boot/xenbl.pid file, killed pygrub, and after that the after-installation-reboot continued normally.. When the domU got up I checked grub.conf from it: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/mapper/vg_f11domu-lv_root # initrd /initrd-version.img #boot=/dev/xvda default=0 timeout=0 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora (2.6.29.4-167.fc11.i686.PAE) root (hd0,0) kernel /vmlinuz-2.6.29.4-167.fc11.i686.PAE ro root=/dev/mapper/vg_f11domu-lv_root rhgb quiet initrd /initrd-2.6.29.4-167.fc11.i686.PAE.img timeout=0 looks suspicious.. so I changed it to 5. After that domU comes up OK on its own.. I changed timeout back to 0, and pygrub gets stuck again. Is this a bug of pygrub, or a broken default grub.conf timeout value of F11? -- Pasi

2 5

Setting up libvirt to work with Xen 3.4.1 on F11
by Boris Derzhavets 20 Aug '09

20 Aug '09

xen 3.4.1-1 src.rpm downloaded from http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/1.fc12/ rebuilt that for F11 and installed. libvirt src.rpm downloaded from ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/updates/1… and installed : "rpm -i libvirt-0.6.2-14.fc11.src.rpm" Rebuilt libvirt packages applying patch :- http://libvirt.org/git/?p=libvirt.git;a=blobdiff;f=src/xend_internal.c;h=55… Installed libvirt :- yum install libvirt-0.6.2-14.fc11.x86_64.rpm \ libvirt-debuginfo-0.6.2-14.fc11.x86_64.rpm \ libvirt-devel-0.6.2-14.fc11.x86_64.rpm \ libvirt-python-0.6.2-14.fc11.x86_64.rpm \ virt-manager virt-viewer Attempt to create any HVM via virt-manager aborts with message:- Unable to complete install '<class 'libvirt.libvirtError'> Domain not found: xenUnifiedDomainLookupByName Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/create.py", line 1501, in do_install dom = guest.start_install(False, meter = meter) File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 541, in start_install return self._do_install(consolecb, meter, removeOld, wait) File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 633, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib64/python2.6/site-packages/libvirt.py", line 974, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: Domain not found: xenUnifiedDomainLookupByName PV DomUs for F11 and CentOS 5.3 created and tested OK. Boris. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 9

virt-viewer crashing on F11 with Xen 3.4.1
by Pasi Kärkkäinen 18 Aug '09

18 Aug '09

Hello. While continuing to test pv_ops dom0 kernels I also rebuilt xen-3.4.1-1 src.rpm on F11. I'm able to virt-install new centos 5.3 domU, but it seems virt-viewer doesn't work. It segfaults on startup. vncviewer works though, and I'm able to complete the installation with vncviewer. http://pasik.reaktio.net/fedora/virt-viewer-crash.txt virt-viewer works when used with the default xen-3.3.1 (which is included in F11). Any tips? -- Pasi

2 7

[Xen-devel] pvops dom0 work roadmap
by Pasi Kärkkäinen 18 Aug '09

18 Aug '09

----- Forwarded message from Jeremy Fitzhardinge <jeremy(a)goop.org> ----- From: Jeremy Fitzhardinge <jeremy(a)goop.org> To: Xen-devel <xen-devel(a)lists.xensource.com> Date: Tue, 18 Aug 2009 11:43:38 -0700 Subject: [Xen-devel] pvops dom0 work roadmap Hi all, I know I've been a bit quiet lately; I've been working through a number of relatively small but time-consuming bugs while trying to stabilize rebase/master. The plan is: * make sure rebase/master is fairly functional and somewhat stable * rename rebase/* to xen/* * use it as the baseline dom0 and domU kernel in xen-unstable rebase/mster is currently up to 2.6.31-rc6, and I intend to track mainline fairly closely (probably no more closely than the -rc level). It also has some new features: * better acpi power management (ported from 2.6.18) * MCE (also from 2.6.18) * microcode updater (I forget whether that's in xen-tip/master) rebase/master is mostly working for me now, but I would be interested in getting some more testing (both success and bug reports welcomed). Once it seems to work, I'll do the rename and we'll work from there. What does this mean for you? * If you're itching to test something, test rebase/master * If you're doing some new development, base it on rebase/master (or if you don't have any strong dependencies on other Xen pieces, base it on mainline) o also, tell me if you're working on something, even if it isn't ready yet, so I know who's doing what It would also useful to do regression testing on plain, unpatched, mainline, to make sure that any real bugfixes get merged promptly. Thanks, J _______________________________________________ Xen-devel mailing list Xen-devel(a)lists.xensource.com http://lists.xensource.com/xen-devel ----- End forwarded message -----

1 0

Using virt-manager for managing KVM VMs running on CentOS 5
by Ranbir 13 Aug '09

13 Aug '09

Hi Everyone, Can I use virt-manager from a Fedora 11 box to manage KVM VMs running on a CentOS 5.3 host? The CentOS 5.3 machine is running KVM and related RPMs from a third party repo (http://www.lfarkas.org/linux/packages/centos/5/x86_64/virt/RPMS/) . I'm using TLS for the encryption. I followed the TLS guide on the libvirt.org website to create and install all the necessary certs and keys. I have libvirtd listening on the CentOS 5 box. When I try to connect to libvirtd with virt-manager from my Fedora 11 desktop, I see the following error on the server: error : qemudClientReadBuf:1554 : gnutls_record_recv: A TLS packet with unexpected length was received. So, that has me wondering if I can even connect to libvirtd on the CentOS 5 box from Fedora 11 in the first place. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.27.29-170.2.78.fc10.x86_64 x86_64 GNU/Linux 10:54:02 up 5 days, 9:54, 5 users, load average: 2.36, 2.38, 1.27

2 3

Possible to install Fedora Rawhide (F12) on RHEL5?
by Orion Poplawski 11 Aug '09

11 Aug '09

I'm trying to install current Fedora Rawhide on my RHEL5 box - Starting install... Retrieving file .treeinfo... | 1.2 kB 00:00 Retrieving file .treeinfo... | 1.2 kB 00:00 Retrieving file vmlinuz... | 2.9 MB 00:09 Retrieving file initrd.img... | 22 MB 01:17 virDomainCreateLinux() failed POST operation failed: (xend.err "Error creating domain: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\\n')") Domain installation may not have been successful. If it was, you can restart your domain by running 'virsh start xenfdev64'; otherwise, please restart your installation. Mon, 10 Aug 2009 11:22:28 ERROR virDomainCreateLinux() failed POST operation failed: (xend.err "Error creating domain: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\\n')") domain-builder-ng.log shows: xc_dom_kernel_file: filename="/var/lib/xen/virtinst-vmlinuz.jWnwEV" xc_dom_malloc_filemap : 2921 kB xc_dom_ramdisk_file: filename="/var/lib/xen/virtinst-initrd.img.ZWLIiQ" xc_dom_malloc_filemap : 22491 kB xc_dom_boot_xen_init: ver 3.1, caps xen-3.0-x86_64 xen-3.0-x86_32p xc_dom_parse_image: called xc_dom_find_loader: trying ELF-generic loader ... failed xc_dom_find_loader: trying Linux bzImage loader ... failed xc_dom_find_loader: trying multiboot-binary loader ... failed xc_dom_core.c:495: panic: xc_dom_find_loader: no loader found xc_dom_release: called Any hope? -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion(a)cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com

3 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen August 2009