xen January 2010

xen@lists.fedoraproject.org

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

Fedora 12 Xen guests (domU) and hosts (dom0)
by Pasi Kärkkäinen 30 Mar '10

30 Mar '10

Hello, I thought of writing some information about running Fedora 12 Xen guests and also Fedora 12 Xen hosts/dom0. Fedora 12 includes the upstream Linux pv_ops Xen domU support in the default kernel. By using virt-install or virt-manager you can install Fedora 12 Xen PV (paravirtual) guests directly from network, for example on RHEL 5.4, CentOS 5.4, or Fedora Xen dom0/host. If you want to run Fedora 12 Xen dom0 (host), there are some extra steps needed. Fedora 12 ships with Xen hypervisor and management tools (Xen 3.4.1, and Xen 3.4.2 in the F12 updates), but the required Xen dom0 capable host kernel is not included in Fedora atm/yet. General information about Xen dom0 status in Fedora: http://fedoraproject.org/wiki/Features/XenPvopsDom0 There are a couple of different ways to get and install a Xen dom0 capable kernel to Fedora 12 host: - By using pre-packaged pv_ops xendom0 kernel rpms by M A Young. his repository: http://fedorapeople.org/~myoung/dom0/ - Compiling and installing Xen dom0 capable kernel yourself/manually. There are many options to choose from, full list of the available Xen dom0 capable kernels is here: http://wiki.xensource.com/xenwiki/XenDom0Kernels The recommended dom0 kernel is the pv_ops kernel, which is in the process of being cleaned up for upstream/mainline Linux inclusion. More information about pv_ops dom0 kernel, including the status reports: http://wiki.xensource.com/xenwiki/XenParavirtOps Xen developers are interested of both the success and failure reports when using the Xen pv_ops dom0 kernel. Tips for running Xen with Fedora 12: - Make sure you install all the latest Fedora 12 updates, since they have an updated Xen version (3.4.2), and also fix a bug in python-virtinst tool to make Xen guest console keymaps work properly: https://bugzilla.redhat.com/show_bug.cgi?id=533707 - Recent versions of Xen pv_ops dom0 kernel renamed some xen backend driver modules to have "xen-" prefix in them, for example evtchn module became xen-evtchn. Fedora Xen 3.4.2 init scripts take care of this, and load the correct modules, but Xen 3.4.1 doesn't do this automatically, causing xend fail to start in dom0/host before the modules are loaded manually. - There are some upcoming apic-related changes coming in pv_ops dom0 kernel, which will require a patch to Xen hypervisor. This patch is not yet included in the Fedora Xen rpms. The patch will be added to Fedora Xen rpms when the upstream pv_ops kernel starts to require/use it. - pv_ops dom0 kernel currently lacks blktap2 support, so using tap:aio: backend disk image files is not yet possible. Xen file: backend image files work though. At the moment it's recommended to use LVM volumes for guest disks (Xen phy: backend). - virt-manager seems to work OK on Fedora 12 Xen dom0. - If you experience problems related to Fedora 12 guests (domU) kernel crashing (especially related to save/restore/migration), install the latest Fedora updates to the guest. There has been a lot of Xen guest related fixes in the upstream Linux recently. These fixes will appear in Fedora when the kernel gets updated to include the latest stable upstream fixes. Hopefully that helps :) -- Pasi

2 4

blktap driver for xen-dom0
by 서지혜 30 Mar '10

30 Mar '10

I installed xen 3.4.1 & M.young's xendom0 kernel on fedora 12 beta. Everying works smoothly for me except that I can't use "tap:aio" for PV guest. It seems that blktap driver is not installed (not supported) on dom0 kernel. I think performance of guest OS is better when is mounted by blktap. Is there anyway I can use this option?

2 2

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

Re: [Fedora-xen] Dom0 kernels Xen Host connected via remote VNC Session
by Boris Derzhavets 02 Jan '10

02 Jan '10

Switched to initdefault 3 in /etc/inittab and logged into Xen 3.4.2 host with your kernel. Set up VNC session and got the nice dmesg report, which is attached. Yes , [drm] entries for Radeon HD 4650 look good , but via remote VNC session. [drm] Initialized drm 1.1.0 20060810 [drm] radeon defaulting to kernel modesetting. [drm] radeon kernel modesetting enabled. xen: registering gsi 16 triggering 0 polarity 1 xen_allocate_pirq: returning irq 16 for gsi 16 xen: --> irq=16 xen_set_ioapic_routing: irq 16 gsi 16 vector 152 ioapic 0 pin 16 triggering 1 polarity 1 radeon 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 radeon 0000:01:00.0: setting latency timer to 64 [drm] radeon: Initializing kernel modesetting. [drm] register mmio base: 0xFE8E0000 [drm] register mmio size: 65536 ATOM BIOS: 11X [drm] Clocks initialized ! mtrr: type mismatch for d0000000,10000000 old: write-back new: write-combining [drm] Detected VRAM RAM=256M, BAR=256M [drm] RAM width 128bits DDR [TTM] Zone kernel: Available graphics memory: 4074962 kiB. [TTM] Zone dma32: Available graphics memory: 2097152 kiB. [drm] radeon: 256M of VRAM memory ready [drm] radeon: 512M of GTT memory ready. [drm] Loading RV730 CP Microcode platform radeon_cp.0: firmware: requesting radeon/RV730_pfp.bin platform radeon_cp.0: firmware: requesting radeon/RV730_me.bin [drm] GART: num cpu pages 131072, num gpu pages 131072 [drm] ring test succeeded in 1 usecs [drm] radeon: ib pool ready. [drm] ib test succeeded in 0 usecs [drm] Radeon Display Connectors [drm] Connector 0: [drm] HDMI-A [drm] DDC: 0x7f10 0x7f10 0x7f14 0x7f14 0x7f18 0x7f18 0x7f1c 0x7f1c [drm] Encoders: [drm] DFP2: INTERNAL_UNIPHY1 [drm] Connector 1: [drm] VGA [drm] DDC: 0x7e20 0x7e20 0x7e24 0x7e24 0x7e28 0x7e28 0x7e2c 0x7e2c [drm] Encoders: [drm] CRT2: INTERNAL_KLDSCP_DAC2 [drm] Connector 2: [drm] DVI-I [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [drm] Encoders: [drm] CRT1: INTERNAL_KLDSCP_DAC1 [drm] DFP1: INTERNAL_UNIPHY [drm] fb mappable at 0xD0141000 [drm] vram apper at 0xD0000000 [drm] size 5242880 [drm] fb depth is 24 [drm] pitch is 5120 executing set pll executing set crtc timing [drm] TV-11: set mode 1280x1024 19 Console: switching to colour frame buffer device 160x64 fb0: radeondrmfb frame buffer device registered panic notifier [drm] Initialized radeon 2.0.0 20080528 for 0000:01:00.0 on minor 0 Attempt to run startx locally fails. Keyboard dies. Please, advise. Boris.

2 10

Re: [Fedora-xen] Dom0 kernels
by Boris Derzhavets 01 Jan '10

01 Jan '10

I've rebuilt your your rpms via xendom0.src.rpm on another F12 instance. Xend starts now, but this is the last what i can see on the screen, before it freeze. I can't get X started when kms is set Boris. --- On Thu, 12/31/09, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote: From: Boris Derzhavets <bderzhavets(a)yahoo.com> Subject: Re: [Fedora-xen] Dom0 kernels To: fedora-xen(a)redhat.com, "M A Young" <m.a.young(a)durham.ac.uk> Date: Thursday, December 31, 2009, 2:07 PM I've tried to load your kernel under Xen 3.4.2 installed via xen-3.4..2.-2.fc13.src.rpm. It installed kms for Radeon HD 4650 ( high resolution on the screen), xend failed to start and screen output got frozen before login prompt. Kernel 2.6.31.6 been built via JF's Git Repo failes with kms for Radeon ( probe error 22) but gets successfully loaded under Xen 3.4.2 providing stable Dom0 on top of F12. Looks like i am missing something trying to work with your rpms. Boris. --- On Mon, 9/21/09, 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] Dom0 kernels To: fedora-xen(a)redhat.com Date: Monday, September 21, 2009, 6:30 PM 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 -- Fedora-xen mailing list Fedora-xen(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen January 2010