xen September 2010

xen@lists.fedoraproject.org

7 participants
7 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

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

Re: [Fedora-xen] [Xen-devel] Re: [Xen-users] Step-by-step tutorial: Installing Xen 4.0.1 rpms on Fedora 13 with pvops Linux 2.6.32.x dom0 kernel
by Boris Derzhavets 07 Sep '10

07 Sep '10

It's done for e2fsprogs-devel on F13. I should care only about :- # yum install e2fsprogs-devel The last is mentioned in XenWiki 4.0 in section - Packages required to build Xen 4.0 from source on Fedora 11, 12, or 13, in addition to all the usual development tools and libraries: yum groupinstall "Development Libraries" yum groupinstall "Development Tools" yum install transfig wget texi2html libaio-devel dev86 \ glibc-devel e2fsprogs-devel gitk mkinitrd iasl xz-devel \ bzip2-devel pciutils-libs pciutils-devel SDL-devel \ libX11-devel gtk2-devel bridge-utils PyXML \ qemu-common qemu-img mercurial glibc-devel.i686Boris --- On Tue, 9/7/10, Michal Novotny <minovotn(a)redhat.com> wrote: From: Michal Novotny <minovotn(a)redhat.com> Subject: Re: [Xen-devel] Re: [Xen-users] Step-by-step tutorial: Installing Xen 4.0.1 rpms on Fedora 13 with pvops Linux 2.6.32.x dom0 kernel To: "Boris Derzhavets" <bderzhavets(a)yahoo.com> Cc: "Pasi Kärkkäinen" <pasik(a)iki.fi>, "Jeremy Fitzhardinge" <jeremy(a)goop.org>, xen(a)lists.fedoraproject.org, virt(a)lists.fedoraproject.org, xen-devel(a)lists.xensource.com, xen-users(a)lists.xensource.com Date: Tuesday, September 7, 2010, 6:38 AM On 09/07/2010 12:28 PM, Boris Derzhavets wrote: > > Note about disk partitioning: Make /boot partition the primary (first) > >> partition and choose the filesystem type as "ext3" (not "ext4" - which is > >> the default) > > It was written concerning Dom0 set-up on top F13 not DomU > Well, you need to have ext4 support in your dom0's e2fsprogs or directly implement in libfsimage in order to have pygrub (I don't know how are the things with pvgrub) working for PV domUs that have ext4 boot partition and this resides always in dom0. Michal -- Michal Novotny<minovotn(a)redhat.com>, RHCE Virtualization Team (xen userspace), Red Hat

1 0

Step-by-step tutorial: Installing Xen 4.0.1 rpms on Fedora 13 with pvops Linux 2.6.32.x dom0 kernel
by Pasi Kärkkäinen 07 Sep '10

07 Sep '10

Hello, I just wrote a step-by-step tutorial how to install the latest Xen 4.0.1 hypervisor on Fedora 13 (x86_64) host from src.rpm packages, and the pvops dom0 kernel from git repository. Check it out: http://wiki.xensource.com/xenwiki/Fedora13Xen4Tutorial It also shows how to install various Xen PV guests using the native distro installers: - CentOS 5.5 - Fedora 13 - Ubuntu 10.04 LTS Hopefully this is helpful to someone! :) -- Pasi

3 5

Re: [Fedora-xen] Xen Dom0 and Fedora 14
by Boris Derzhavets 03 Sep '10

03 Sep '10

/usr/lib64/python2.7/site-packages/xen/util/pci.py stays untouched Dmesg log attached [root@fedora14 ~]# xm info Traceback (most recent call last): File "/usr/sbin/xm", line 5, in <module> from xen.xm import main File "/usr/lib64/python2.7/site-packages/xen/xm/main.py", line 41, in <module> from xen.util.pci import * File "/usr/lib64/python2.7/site-packages/xen/util/pci.py", line 937 pos = 0 ^ IndentationError: expected an indented block Convert /usr/lib64/python2.7/site-packages/xen/util/pci.py back as it was [root@fedora14 ~]# vi /usr/lib64/python2.7/site-packages/xen/util/pci.py [root@fedora14 ~]# service xend start Starting xend daemon: [ OK ] [root@fedora14 ~]# service xenconsoled start Starting xenconsoled daemon: [ OK ] [root@fedora14 ~]# xm info host : fedora14 release : 2.6.32.19-xen version : #4 SMP Fri Sep 3 22:10:56 MSD 2010 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2833 hw_caps : bfebfbff:20100800:00000000:00000940:0408e3fd:00000000:00000001:00000000 virt_caps : hvm total_memory : 8190 free_memory : 1671 node_to_cpu : node0:0-3 node_to_memory : node0:1671 node_to_dma32_mem : node0:841 max_node_id : 0 xen_major : 4 xen_minor : 0 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 xen_commandline : cc_compiler : gcc version 4.5.1 20100812 (Red Hat 4.5.1-1) (GCC) cc_compile_by : root cc_compile_domain : cc_compile_date : Fri Sep 3 21:16:54 MSD 2010 xend_config_format : 4 Boris. --- On Wed, 9/1/10, W. Michael Petullo <mike(a)flyn.org> wrote: From: W. Michael Petullo <mike(a)flyn.org> Subject: [Fedora-xen] Xen Dom0 and Fedora 14 To: xen(a)lists.fedoraproject.org Date: Wednesday, September 1, 2010, 2:42 PM I have been investigating the use of Xen with a Fedora 14 (devel)-based Dom0. Until now, I have always used Michael Young's Dom0 kernels. The first thing I did was try to build the current Fedora 14 kernel with Xen Dom0 support. I began porting Michael's RPM specification to the Fedora 14 specification. What I found was that the Xen pvops work seems to be targeting 2.6.32 and possibly 2.6.36. As a result, I was unable to find a straightforward way to create a patch for 2.6.35.4. Am I missing something here? Is building a 2.6.35.4-based kernel difficult in this way? Next, I tried to use Michael's latest Fedora 12 kernel on Fedora 14. Of course, Fedora 14 uses some features that are not available in this kernel. Most notably, I had to provide the kernel with the "init=/sbin/upstart" option to avoid the use of systemd. Once I booted the system, I found that xend would not start because it did not find what it expected in /sys/bus/pci/devices/0000\:00\:03.2/config: [...] File "/usr/lib/python2.7/site-packages/xen/util/pci.py", line 1050, in detect_dev_info pos = self.find_cap_offset(PCI_CAP_ID_EXP) File "/usr/lib/python2.7/site-packages/xen/util/pci.py", line 933, in find_cap_offset id = ord(os.read(fd, 1)) TypeError: ord() expected a character, but string of length 0 found I "fixed" this by editing pci.py and changing: id = ord(os.read(fd, 1)) to: try: id = ord(os.read(fd, 1)) except: pos = 0 break; Of course, this might not be a good fix, but it was quick and it allowed me to continue and experiment. Does anyone know what is going on here? At this point, I was able to boot a DomU image, although I need to do a lot more testing. Has anyone else experimented with Fedora 14? What is your experience? I am especially interested in hearing about Fedora 14 Dom0 kernels. -- Mike :wq -- xen mailing list xen(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen

1 0

Xen Dom0 and Fedora 14
by W. Michael Petullo 01 Sep '10

01 Sep '10

I have been investigating the use of Xen with a Fedora 14 (devel)-based Dom0. Until now, I have always used Michael Young's Dom0 kernels. The first thing I did was try to build the current Fedora 14 kernel with Xen Dom0 support. I began porting Michael's RPM specification to the Fedora 14 specification. What I found was that the Xen pvops work seems to be targeting 2.6.32 and possibly 2.6.36. As a result, I was unable to find a straightforward way to create a patch for 2.6.35.4. Am I missing something here? Is building a 2.6.35.4-based kernel difficult in this way? Next, I tried to use Michael's latest Fedora 12 kernel on Fedora 14. Of course, Fedora 14 uses some features that are not available in this kernel. Most notably, I had to provide the kernel with the "init=/sbin/upstart" option to avoid the use of systemd. Once I booted the system, I found that xend would not start because it did not find what it expected in /sys/bus/pci/devices/0000\:00\:03.2/config: [...] File "/usr/lib/python2.7/site-packages/xen/util/pci.py", line 1050, in detect_dev_info pos = self.find_cap_offset(PCI_CAP_ID_EXP) File "/usr/lib/python2.7/site-packages/xen/util/pci.py", line 933, in find_cap_offset id = ord(os.read(fd, 1)) TypeError: ord() expected a character, but string of length 0 found I "fixed" this by editing pci.py and changing: id = ord(os.read(fd, 1)) to: try: id = ord(os.read(fd, 1)) except: pos = 0 break; Of course, this might not be a good fix, but it was quick and it allowed me to continue and experiment. Does anyone know what is going on here? At this point, I was able to boot a DomU image, although I need to do a lot more testing. Has anyone else experimented with Fedora 14? What is your experience? I am especially interested in hearing about Fedora 14 Dom0 kernels. -- Mike :wq

4 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen September 2010