No pcifront in F10?
by Jim Lutz
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?
12 years, 11 months
Dom0 kernels
by M A Young
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
13 years, 6 months
Success with Fedora 10 Xen pv_ops 2.6.29-rc8 dom0
by Pasi Kärkkäinen
Hello!
I've used a lot of time trying to get my custom Xen pv_ops dom0 kernel working with
virt-install and/or virt-manager on Fedora 10, and now it seems I got things
working.
If you want to play with this you need:
1) New enough pv_ops dom0 kernel (2.6.29-rc8 or newer) so it has /sys/hypervisor support included
- Compile with CONFIG_HIGHPTE=n since it seems to be broken still
2) libvirt 0.6.1 and related packages from Fedora 10 updates-testing
In addition to those I'm using Xen 3.3.1-9 packages from rawhide/F11 rebuilt for F10.
With the older Fedora 10 libvirt packages libvirtd was crashing often for me, and
I had some other issues with virt-install console window not opening but stalling etc..
Today I was able to run the following on Fedora 10 32bit PAE pv_ops dom0:
- CentOS 5.3 32bit PAE PV domU
- Fedora 10 32bit PAE PV domU
- Use virt-install to install Fedora 10 32bit PAE PV domU (using custom kickstart
to force PAE kernel installation to avoid the anaconda BUG which installs
wrong non-PAE kernel as a default).
Fedora 11 (rawhide) installation most probably works too.
I'm using LVM volumes for domU disks (tap:aio is not yet supported by pv_ops
dom0 kernel).
Network seems to work after running "ifdown eth0 && ifup eth0"
on the guest.. dunno why that's needed. That's something to figure out later:)
Graphical domU console works with virt-viewer and virt-install during installation.
Issues:
- virt-manager complains about default network (virbr0) being inactive and
asks if I want to start it. If I click Yes, then I get error: "libvirtError: cannot create bridge 'virbr0': File exists"
virbr0 works just fine with virt-install. So dunno what's the problem with that..
have to look into that later.
Thanks to everyone involved for helping me with this!
-- Pasi
14 years, 2 months
Configuring Xen on FC10
by Samir Selman
Hi,
I am working at Stanford on a research project and I have installed Fedora
Core 10. Can someone help me on what are the steps to configure Xen on FC10.
Thanks
14 years, 2 months
debian
by mattias
Can i install debian with virt-install
I meen para-virt
14 years, 4 months
[Xen-devel] [ANNOUNCE] Xen 3.4.0 released!
by Pasi Kärkkäinen
----- 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: Mon, 18 May 2009 05:26:28 -0700
Subject: [Xen-devel] [ANNOUNCE] Xen 3.4.0 released!
Folks,
We're pleased to announce the official release of Xen 3.4.0!
This release contains a number of important new features and updates
including:
- Device passthrough improvements, with particular emphasis on support for
client devices (further support is available as part of the XCI project at
http://xenbits.xensource.com/xenclient/)
- RAS features: cpu and memory offlining
- Power management - improved frequency/voltage controls and deep-sleep
support. Scheduler and timers optimised for peak power savings.
- Support for the Viridian (Hyper-V) enlightenment interface
- Many other x86 and ia64 enhancements and fixes
You can get the source using mercurial from:
http://xenbits.xensource.com/xen-3.4-testing.hg
A pre-prepared source tarball is available from:
http://www.xen.org/download/
Cheers,
Keir (on behalf of the whole Xen dev team)
_______________________________________________
Xen-devel mailing list
Xen-devel(a)lists.xensource.com
http://lists.xensource.com/xen-devel
----- End forwarded message -----
14 years, 4 months
How to build Xen with my own Linux sources?
by Michael Crawford
I asked about this on the xen-devel list a few days ago, but no one
responded. I just asked a second time, but it has been my experience
that the other xen-devel subscribers just ignore pleas for help.
I'm an experienced developer, and I've tried searching the list
archives as well as Google. I've done my best to ask intelligent
questions - but still I am *completely* stymied.
What I want to do is to build the xen and linux kernels without having
the xen build download the linux source tarball from kernel.org.
I have used git to get the tip/master branch of Linux - that's the
version of Linux that is in development from the Xen folks. I can
build a working kernel from it if I only build linux itself, without
trying to also build xen.
What I want to do is to get xen to build, but when it wants to build
the Dom0 and DomU kernels, I want it to use my tip/master branch of
the Linux sources that I retrieved with git.
I have seen documentation that says I should be able to do this by
rolling a .tar.bz2 of the kernel source, and then setting the
environment variable XEN_LINUX_SOURCE=tarball, but it simply does not
work - the kernel tarball is still downloaded with wget.
I am incredibly frustrated.
I'm grateful for any help you can give me.
Mike
--
Michael David Crawford
mdcrawford at gmail dot com
GoingWare's Bag of Programming Tricks
http://www.goingware.com/tips/
14 years, 4 months
Xen HVM Wink2k3 guest network problem
by shoom
I have a pain-staking problem with network on Win2k3 guest on IA64 host with
Red Hat 5.3 - by default it uses Realtek 8139 which is not supported on
Win2k3 in any way, and changing the model (model=whatever in vif=...)
doesn't change anything - it always ends with *!@#! Realtek ... now, I am
very tired of trying out different things (compiling Xen from src.rpm, from
xensource xen-unstable.hg, trying vfirmware from xensource, different
parameters in guest specification, I don't know ..) - nothing helps. Thing
is that I am trying to make the proof of concept in my company for RHEL5.3
as platform for Itanium virtualization (BL380c) in order to get full support
contract with Red Hat as a breakthrough ... but it seems that Microsoft
always has to win, I vae tried to ring every bell available, but nothing
came and now I am tired and worn out completely ... If anyone has any idea,
hint, something, please tell me.
shoom013(a)gmail.com
--
View this message in context: http://www.nabble.com/Xen-HVM-Wink2k3-guest-network-problem-tp23475221p23...
Sent from the Fedora Xen mailing list archive at Nabble.com.
14 years, 4 months
Fedora 11 (rawhide) success with Xen pv_ops dom0 kernel (2.6.30-rc3)
by Pasi Kärkkäinen
Hello!
Earlier I was testing Xen pv_ops dom0 kernel with Fedora 10, and after I got it
working I decided to repeat the tests with Fedora 11 (rawhide).
There was problems with the latest pv_ops dom0 xen-tip/next kernel tree for a while,
but those problems are now resolved, and I got my Fedora 11 testbox working,
so I decided to write here about my success.
My setup:
- Fedora 11 (rawhide as of 2009-05-05)
- Xen included in F11, no external patches (xen-3.3.1-11.fc11)
- xen-tip/next pv_ops dom0 kernel as of 2009-05-06, Linux 2.6.30-rc3.
- All the rest was standard stuff included in Fedora 11 aswell
With this setup I'm able to run Xen paravirtual (PV) domUs, install new
domUs using virt-install and also install and manage domains with virt-manager.
Current limitations:
- Xen HVM support is not yet working with pv_ops dom0 kernel
Earlier problems with VGA text console have also been fixed, so grub
menu.lst entry like this now works:
title Fedora Xen pv_ops dom0-test (2.6.30-rc3-tip)
root (hd0,0)
kernel /xen-3.3.gz dom0_mem=1024M loglvl=all guest_loglvl=all
module /vmlinuz-2.6.30-rc3-tip ro root=/dev/vg00/lv01
module /initrd-2.6.30-rc3-tip.img
Or if you want to have serial console, use this:
title Fedora Xen pv_ops dom0-test (2.6.30-rc3-tip) / serial console
root (hd0,0)
kernel /xen-3.3.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1
module /vmlinuz-2.6.30-rc3-tip ro root=/dev/vg00/lv01 console=hvc0 earlyprintk=xen
module /initrd-2.6.30-rc3-tip.img
Hopefully someone finds this information interesting! :)
-- Pasi
14 years, 4 months
Problems rebuilding fedora xen-3.3.1-11.fc11.src.rpm with debug enabled
by Pasi Kärkkäinen
Hello.
I'm trying to rebuild xen-3.3.1-11.fc11.src.rpm with debug enabled to be
able to get more debug information from pv_ops dom0 kernels.
.. and I have a problem. Has someone else seen this problem?
I modified xen.spec and added "debug=y verbose=y crash_debug=y" options to
"%if %{hv_build}" section to make command.
Running "rpmbuild -bb xen.spec" gives this error:
traps.c: Assembler messages:
traps.c:1343: Error: bad register name `%sil'
make[4]: *** [traps.o] Error 1
make[4]: Leaving directory `/root/rpmbuild/BUILD/xen-3.3.1/xen/arch/x86'
Based on some googling it could be a gcc problem? I'm running:
# rpm -qa|grep gcc
gcc-gfortran-4.4.0-3.i586
libgcc-4.4.0-3.i586
gcc-c++-4.4.0-3.i586
gcc-debuginfo-4.3.2-7.i386
gcc-4.4.0-3.i586
-- Pasi
14 years, 5 months
