xen October 2010

xen@lists.fedoraproject.org

11 participants
6 discussions

execute commands from dom0 into domU
by silviu d 06 Jun '15

06 Jun '15

Hello, I was wondering if there is a way to execute commands from dom0 into domU without loging into domU with ssh. thanks

3 2

Xen dom0 (core) merged to upstream Linux 2.6.37 and other new features
by Pasi Kärkkäinen 31 Oct '10

31 Oct '10

Hello, People here might be interested to know that Xen pvops dom0 core was merged to upstream Linux kernel during the 2.6.37 merge window! This has been in the works for a long time, so it's good news. Note that this is the core/initial merge, there's more upstreaming needed to get for example the Xen dom0 backend drivers merged to be able to run other domains using the upstream kernel. Xen developers are working on upstreaming more of the missing bits in the next Linux versions. Recently in addition to the Xen dom0 bits there has been other upstreamed features aswell: - Xen PV-on-HVM drivers for fully virtualized (HVM) Linux guests in 2.6.36, and optimizations for the drivers in 2.6.37. - Xen PCI front driver in Linux 2.6.37 for PCI passthru to Xen PV guests (works also with hardware where VT-d/IOMMU is not available). There will also be a git kernel tree based on 2.6.37 with the backend drivers and other not-yet-upstreamed patches included. -- Pasi

5 6

Re: [Fedora-xen] Xen dom0 (core) merged to upstream Linux 2.6.37 and other new features
by Boris Derzhavets 31 Oct '10

31 Oct '10

Kernel tested OK under Xen 4.0.1 on F14. I captured some info. It's attached. Is anything else required ? Boris. --- On Sat, 10/30/10, M A Young <m.a.young(a)durham.ac.uk> wrote: From: M A Young <m.a.young(a)durham.ac.uk> Subject: Re: [Fedora-xen] Xen dom0 (core) merged to upstream Linux 2.6.37 and other new features To: "Pasi Kärkkäinen" <pasik(a)iki.fi> Cc: xen(a)lists.fedoraproject.org Date: Saturday, October 30, 2010, 7:39 PM I have built a test kernel (2.6.37-0.1.rc0.git13.xendom0.fc15) from upstream linux after the xen patches went in at http://koji.fedoraproject.org/koji/taskinfo?taskID=2566143 I haven't tested it yet but it should in theory boot as a dom0 kernel though it won't support guests. This is very much a first attempt and it might be completely broken. Michael Young -- xen mailing list xen(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen

1 0

dom0 kernel
by M A Young 29 Oct '10

29 Oct '10

I have built a new kernel (kernel-2.6.32.21-167.xendom0.fc12) at http://koji.fedoraproject.org/koji/taskinfo?taskID=2445999 or at the repository http://repos.fedorapeople.org/repos/myoung/dom0-kernel/ This includes the net-sched-plug feature built as a module. Michael Young

8 34

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

Crash from balloon_init in latest stable-2.6.32.x
by M A Young 23 Oct '10

23 Oct '10

Are there any ideas about this crash last_pfn = 0x42fe0c max_arch_pfn = 0x400000000 BUG: unable to handle kernel paging request at ffffea000e700030 IP: [<ffffffff812352e7>] __list_add+0x6c/0x81 PGD 1a37067 PUD 1a38067 PMD 226f8f067 PTE 0 Oops: 0002 [#1] SMP last sysfs file: CPU 5 Modules linked in: Pid: 1, comm: swapper Tainted: G W 2.6.32.25-171.rc1.xendom0.fc12.x86_64 #1 H8DGT RIP: e030:[<ffffffff812352e7>] [<ffffffff812352e7>] __list_add+0x6c/0x81 RSP: e02b:ffff8803e3491e50 EFLAGS: 00010246 RAX: 000000000e700000 RBX: ffffea000e6ffff0 RCX: 0000000000000a2d RDX: ffffea000e6ffff0 RSI: ffffffff816dc030 RDI: ffffea000e700028 RBP: ffff8803e3491e70 R08: ffffea000e6ffff0 R09: 0000000000000001 R10: 0000000000000008 R11: 00000000e3491d78 R12: ffffffff816dc030 R13: ffffea000e700028 R14: 0000000000000100 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff8802270e4000(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: ffffea000e700030 CR3: 0000000001001000 CR4: 0000000000000660 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process swapper (pid: 1, threadinfo ffff8803e3490000, task ffff8802170b8000) Stack: 0000000000000100 0000000000420000 ffffea0000000000 000000000042fe0c <0> ffff8803e3491ea0 ffffffff8182ac21 ffffffff8182aa4e ffffffff8182aa4e <0> 0000000000000000 00000000294d99f2 ffff8803e3491ed0 ffffffff8100a069 Call Trace: [<ffffffff8182ac21>] balloon_init+0x1d3/0x213 [<ffffffff8182aa4e>] ? balloon_init+0x0/0x213 [<ffffffff8182aa4e>] ? balloon_init+0x0/0x213 [<ffffffff8100a069>] do_one_initcall+0x5e/0x159 [<ffffffff817fa75f>] kernel_init+0x1fd/0x257 [<ffffffff81013d6a>] child_rip+0xa/0x20 [<ffffffff81012f51>] ? int_ret_from_sys_call+0x7/0x1b [<ffffffff810136dd>] ? retint_restore_args+0x5/0x6 [<ffffffff81013d60>] ? child_rip+0x0/0x20 Code: 04 24 49 39 d8 74 20 4d 89 e1 48 89 d9 48 c7 c2 65 10 60 81 be 1e 00 00 00 48 c7 c7 cd 0f 60 81 31 c0 e8 67 23 e2 ff 4c 89 6b 08 <4d> 89 65 08 49 89 5d 00 4d 89 2c 24 5b 5b 41 5c 41 5d c9 c3 90 RIP [<ffffffff812352e7>] __list_add+0x6c/0x81 RSP <ffff8803e3491e50> CR2: ffffea000e700030 ---[ end trace a7919e7f17c0a726 ]--- The full serial console output is at the provided link. I did some tracing myself and the problem seems to be happening at the list_add call in __balloon_append called from balloon_init in drivers/xen/ballon.c. This is with a kernel I built today (at http://koji.fedoraproject.org/koji/taskinfo?taskID=2550132 ) with the latest stable-2.6.32.x , the 170.1 kernel was built on Thursday (21st Oct) and 170 on 6th October and would have used stable-2.6.32.x at those dates. Michael Young ---------- Forwarded message ---------- Date: Sat, 23 Oct 2010 14:06:56 -0700 From: fcxen user <fcxen(a)itsbeen.sent.com> To: M A Young <m.a.young(a)durham.ac.uk>, xen(a)lists.fedoraproject.org Subject: Re: [Fedora-xen] another xen kernel 170, 170.1, 171 crashed the same using: title Xen root (hd0,0) kernel /xen.gz loglvl=all guest_loglvl=all sync_console console_to_ring com2=115200,8n1 console=com2,vga lapic=debug apic_verbosity=debug apic=debug iommu=off module /vmlinuz-2.6.32.25-171.rc1.xendom0.fc12.x86_64 ro root=UUID=84e6a109-84c5-4288-80de-ea368a224a3a rd_MD_UUID=c557e3e8:d9ef50b8:b5e9861f:26975533 rd_MD_UUID=5825fd8c:77ea8324:ae0c8804:8a0c2 487 rd_NO_LUKS rd_NO_LVM rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us console=hvc0 earlyprintk=xen nomodeset initcall_debug debug loglevel=10 module /initramfs-2.6.32.25-171.rc1.xendom0.fc12.x86_64.img Latest output is: http://pastie.org/1243649

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen October 2010