Preview Xen 3.2 rc* packages
by Ian Jackson
I've merged the patches and so on from xen-3.1.0-13.fc8.src.rpm with a
recent xen-unstable tip (16635:9d447ba0c99a). With a bit of work I
have managed to get a set of packages which appear to be able to work
at least in my simple `does this work at all' test.
I'm mentioning it here so that you can have a look at what I've done
and comment on it. We'll probably be making official upstream rpms
for Fedora 8. Please send me feedback either here on-list or
privately.
Most of the patches from -13.fc8 have been incorporated upstream so I
just deleted them from my srpm. A couple of these patches I've
included I have also submitted upstream and they'll be in
xen-unstable.hg soon if they're not already.
There were two patches that looked like they would be useful upstream:
xen-qemu-bootmenu.patch
pygrub-manykernels.patch
but I wasn't able to find clear attribution for the source of this
code. Xen upstream operates a `Signed-off-by' protocol to ensure that
we don't get bitten by copyright problems. Where should I look to try
to find the authors/contributors to check on the copyright status ?
In my package I have included the hypervisor in the xen-*.rpm rather
than making a kernel package too. This is more in line with practice
upstream. The new hypervisor seems to work for me with the
2.6.21-2952.fc8xen kernel.
I have not included xen-net-bridge.patch which seemed quite a
surprising set of changes to me.
I was rather puzzled by the part of xen-initscript.patch which removes
most of xend's startup code. I agree that xend's arrangements are not
entirely ideal but is there really much to be gained by making that
changes, which obviously makes the patchset much more fragile ?
You can find the actual files here:
http://www.chiark.greenend.org.uk/~ijackson/xen-3.2rc-fedora8/
THESE PACKAGES SHOULD NOT BE USED FOR PRODUCTION - they're previews,
and Xen 3.2 is still unreleased and in need of more testing.
Please check the SHA256's before installing them:
1209de4470cf505113e684fe8f1f5c13faad40ad8eb4c456e8741eddbe5b6254 xen-3.1.9-0.fc8.i386.rpm
18ad4f2b35c6918ab3070e43d238487f6cbaf10a682cfc90b1d11c4640957395 xen-3.1.9-0.fc8.src.rpm
428da514ccf9064244017a5068c399ec0e7c5816c2d2f4ded17e9af031d50759 xen-debuginfo-3.1.9-0.fc8.i386.rpm
98305f6fc7de7c965b7cb0426a0bed4cb977394a8fce1cedf6fb35d6780df0c5 xen-devel-3.1.9-0.fc8.i386.rpm
f45e0ed7ff40bf7ef4e8cd236f639060caba27d3573003745bfa37f3ae0f4943 xen-libs-3.1.9-0.fc8.i386.rpm
Regards,
Ian.
16 years, 4 months
- 2
- 5
Using old F7 guests in F8?
by Philip Rhoades
People,
It looks like the configuration stuff has changed from F7 to F8? - I
still have the F7 kernel, guest cfg and disk files but I couldn't find
anything about how to use them in F8. It is not important, I just
thought it would be an interesting exercise . .
Thanks,
Phil.
--
Philip Rhoades
Pricom Pty Limited (ACN 003 252 275 ABN 91 003 252 275)
GPO Box 3411
Sydney NSW 2001
Australia
Fax: +61:(0)2-8221-9599
E-mail: phil(a)pricom.com.au
16 years, 4 months
- 1
- 0
General confusion
by Gerhardus Geldenhuis
Hi
My goal is to create a xen domain using lvm backed storage. It sounds simple
and probably is but I am getting caught down in the details. I am using RH5
which I am hopefull will be similar enough to be able to ask on this list.
Its the only list on https://www.redhat.com/mailman/listinfo with xen in the
name.
Up to now I have been using virt-install to create new domains. It takes
care of a lot of detail but this is a lot like spoon feeding and you learn
nothing plus it is limited in capabilities at the moment.
Confusion one:
When creating a new domain it creates a config file that xm can use:
name = "test03"
uuid = "80bd6bda-c559-3a68-643c-df0f29d672b9"
maxmem = 200
memory = 200
vcpus = 1
bootloader = "/usr/bin/pygrub"
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
vfb = [ ]
disk = [ "tap:aio:/root/temppart/test03.img,xvda,w" ]
vif = [ "mac=00:16:3e:24:15:79,bridge=virbr0" ]
When I dump the config using virsh it adds some additinal paramters:
<os>
<type>linux</type>
<kernel>/var/lib/xen/boot_kernel.nNlfNC</kernel>
<initrd>/var/lib/xen/boot_ramdisk.jV4otH</initrd>
<cmdline>ro root=/dev/VolGroup00/LogVol00 console=xvc0</cmdline>
This names changes every time you restart the xen domain. What creates this
<random> kernel and initrd and would using the following config be the same
thing:
<kernel>/boot/vmlinuz-2.6.18-53.el5xen</kernel>
<initrd>/boot/initrd-2.6.18-53.el5xen.img</initrd>
I am also a bit confused about the <cmdline> value and how it is used and
what it should be. If anybody has a brief explanation of how this fits into
the greater scheme of things it would be really appreciated.
Lastly, I have managed to create a xml config file for virsh which does not
immediatly complain about any errors. However I am still unsure how/where to
specify the installation (http) source. I dont want to copy a existing
installation I want to create a new one, would this just be a kernel
parameter?
The config file I am using:
<domain type='xen' id='3'>
<name>test-a-01</name>
<os>
<type>linux</type>
<kernel>/boot/vmlinuz-2.6.18-53.el5xen</kernel>
<initrd>/boot/initrd-2.6.18-53.el5xen.img</initrd>
<cmdline>ro root=/dev/VolGroup00/LogVol00 console=xvc0</cmdline>
</os>
<memory>202144</memory>
<vcpu>1</vcpu>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<interface type='bridge'>
<source bridge='virbr0'/>
<script path='vif-bridge'/>
</interface>
<disk type='phy' device='disk'>
<driver name='tap' type='aio'/>
<source file='/root/parts/test-a-01.img'/>
<target dev='xvda'/>
</disk>
<console tty='/dev/pts/2'/>
</devices>
</domain>
Regards
--
Gerhardus Geldenhuis
Registered Linux User #193352
16 years, 4 months
- 1
- 0