Fedora 8 - Linux HVM Guest - PV Drivers
by Emre Erenoglu
Hi,
I'm trying to use a linux HVM guest (DomU) with Paravirtual drivers for
network and disk access on my updated Fedora 8 setup.
In order to achieve this, I've downloaded the source package of appropriate
(same version) Xen Hypervisor from redhat website, then copied this source
to my DomU and compiled the unmodified_drivers folder following the steps
mentioned in the README file.
Everything went fine and I got my xen-platform-pci, xen-baloon, xen-vnif and
xen-vbd (.ko) drivers.
They modprobe fine, however, after some time, the DomU freezes up.
Specifically, system freezes quicker (usually) with only vbd, and takes more
time to free with only xen-vnif loaded into memory. When I say only,
xen-platform-pci always loaded, but only the mentioned driver is netfront or
block-front, others are ioemu.
xen-vnif also complains about a memory leak when it's rmmod 'ed.
Shall I file a bug report?
Thanks,
Emre Erenoglu
erenoglu(a)gmail.com
16 years, 4 months
Network Problem after update 3.0 -> 3.1: blkback
by kadafax
Hello,
I have a big problem:
Dom0 is centos5.1, domU are centos5.1. My setup is really simple, the
only thing is that I give 3 nics to the domU so I use a modified network
script (which has worked since january... since fedora 6):
"
#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0
"$dir/network-bridge" "$@" vifnum=1
"$dir/network-bridge" "$@" vifnum=2
"
So I have updated my xen dom0 from 3.0.3-rc5-8.1.15.el5 to
3.1.0-53.1.4.el5 (and kernel-xen 2.6.18-8.1.15.el5xen to
2.6.18-53.1.4.el5xen) and now my domU cant access the network. The
interfaces are good in the domU, all seems to be ok but there are no
connectivity at all (no arp entries). This message shows up on the dom0
each time I launch a domU:
blkback: ring-ref 9, event-channel 7, protocol 1 (x86_64-abi)
Do someone know what is happening ? this is very embarrassing after a
simple upgrade... Hopefully I have another identical server (Centos 5.0
with 5.1 domUs) which is still in 3.0 but I cant stay not updated.
Thanks for any help.
xm info:
host : host.foo.com
release : 2.6.18-53.1.4.el5xen
version : #1 SMP Fri Nov 30 01:21:23 EST 2007
machine : x86_64
nr_cpus : 4
nr_nodes : 1
sockets_per_node : 2
cores_per_socket : 1
threads_per_core : 2
cpu_mhz : 2992
hw_caps : bfebfbff:20100800:00000000:00000180:0000641d
total_memory : 4095
free_memory : 3246
xen_major : 3
xen_minor : 1
xen_extra : .0-53.1.4.el5
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
cc_compiler : gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)
cc_compile_by : mockbuild
cc_compile_domain :
cc_compile_date : Fri Nov 30 00:37:12 EST 2007
xend_config_format : 2
16 years, 4 months
xen-unstable => 3.2, binary packages
by Ian Jackson
We hope to be releasing upstream Xen 3.2 soon. As you'll know, we've
been in the habit of producing binary packages for our releases,
including for Fedora.
It seemed to me that the best approach would be, where possible, to
use a distro's own packaging setup. That would be more likely to
generate packages which integrate well with the distro and behave more
like the distro's own Xen packaging arrangements.
I haven't looked at the FC6 srpm in detail yet but what would you
think about it if we were to generate our 3.2 binary rpms based on
that ?
Regards,
Ian.
16 years, 4 months
(no subject)
by Gary Catalano
Greetings!
I'm having a problem with fedora8 and Xen 3.1.0. I'm trying to get Windows to run under Xen (I've been using these instructions http://www.xensource.com/files/xen_install_windows.pdf) and I get all the way to the last steps but when I start my virtual machine I get an error saying it can't find a bootable drive:
CDROM boot failure code : 0002
Boot from CD-Rom failed: could not read the boot disk
FATAL: No bootable device.
Here's the .hvm I'm using to launch my virtual machine:
# -*- mode: python; -*-
#============================================================================
# Python configuration setup for 'xm create'.
# This script sets the parameters used when a domain is created using 'xm create'.
# You use a separate script for each domain you want to create, or
# you can set the parameters for the domain on the xm command line.
#============================================================================
import os, re
arch = os.uname()[4]
if re.search('64', arch):
arch_libdir = 'lib64'
else:
arch_libdir = 'lib'
#----------------------------------------------------------------------------
# Kernel image file.
kernel = "/usr/lib/xen/boot/hvmloader"
# The domain build function. HVM domain uses 'hvm'.
builder='hvm'
# Initial memory allocation (in megabytes) for the new domain.
#
# WARNING: Creating a domain with insufficient memory may cause out of
# memory errors. The domain needs enough memory to boot kernel
# and modules. Allocating less than 32MBs is not recommended.
memory = 1024
# Shadow pagetable memory for the domain, in MB.
# Should be at least 2KB per MB of domain memory, plus a few MB per vcpu.
# shadow_memory = 8
# A name for your domain. All domains must have different names.
name = "win2k3-001"
# 128-bit UUID for the domain. The default behavior is to generate a new UUID
# on each call to 'xm create'.
#uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9"
#-----------------------------------------------------------------------------
# The number of cpus guest platform has, default=1
#vcpus=1
# Enable/disable HVM guest PAE, default=1 (enabled)
#pae=1
# Enable/disable HVM guest ACPI, default=1 (enabled)
#acpi=1
# Enable/disable HVM APIC mode, default=1 (enabled)
# Note that this option is ignored if vcpus > 1
#apic=1
# List of which CPUS this domain is allowed to use, default Xen picks
#cpus = "" # leave to Xen to pick
#cpus = "0" # all vcpus run on CPU0
#cpus = "0-3,5,^1" # run on cpus 0,2,3,5
# Optionally define mac and/or bridge for the network interfaces.
# Random MACs are assigned if not given.
#vif = [ 'type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0, model=ne2k_pci' ]
# type=ioemu specify the NIC is an ioemu device not netfront
vif = [ 'type=ioemu, mac=00:16:3e:00:00:94, bridge=xenbr0' ]
#----------------------------------------------------------------------------
# Define the disk devices you want the domain to have access to, and
# what you want them accessible as.
# Each disk entry is of the form phy:UNAME,DEV,MODE
# where UNAME is the device, DEV is the device name the domain will see,
# and MODE is r for read-only, w for read-write.
disk = [ 'phy:/dev/VGGuests/w2k3-001,ioemu:hda,w' ]
#disk = [ 'file:/.img,hda,w', ',hdc:cdrom,r' ]
#----------------------------------------------------------------------------
# Configure the behaviour when a domain exits. There are three 'reasons'
# for a domain to stop: poweroff, reboot, and crash. For each of these you
# may specify:
#
# "destroy", meaning that the domain is cleaned up as normal;
# "restart", meaning that a new domain is started in place of the old
# one;
# "preserve", meaning that no clean-up is done until the domain is
# manually destroyed (using xm destroy, for example); or
# "rename-restart", meaning that the old domain is not cleaned up, but is
# renamed and a new domain started in its place.
#
# The default is
#
# on_poweroff = 'destroy'
# on_reboot = 'restart'
# on_crash = 'restart'
#
# For backwards compatibility we also support the deprecated option restart
#
# restart = 'onreboot' means on_poweroff = 'destroy'
# on_reboot = 'restart'
# on_crash = 'destroy'
#
# restart = 'always' means on_poweroff = 'restart'
# on_reboot = 'restart'
# on_crash = 'restart'
#
# restart = 'never' means on_poweroff = 'destroy'
# on_reboot = 'destroy'
# on_crash = 'destroy'
#on_poweroff = 'destroy'
#on_reboot = 'restart'
#on_crash = 'restart'
#============================================================================
# New stuff
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
#-----------------------------------------------------------------------------
# Disk image for
cdrom= "/tmp/win2k3srv.iso"
#-----------------------------------------------------------------------------
# boot on floppy (a), hard disk (c), Network (n) or CD-ROM (d)
# default: hard disk, cd-rom, floppy
boot="d"
#-----------------------------------------------------------------------------
# write to temporary files instead of disk image files
#snapshot=1
#----------------------------------------------------------------------------
# enable SDL library for graphics, default = 0
sdl=1
#----------------------------------------------------------------------------
# enable VNC library for graphics, default = 1
vnc=0
#----------------------------------------------------------------------------
# address that should be listened on for the VNC server if vnc is set.
# default is to use 'vnc-listen' setting from /etc/xen/xend-config.sxp
#vnclisten="127.0.0.1"
#----------------------------------------------------------------------------
# set VNC display number, default = domid
#vncdisplay=1
#----------------------------------------------------------------------------
# try to find an unused port for the VNC server, default = 1
#vncunused=1
#----------------------------------------------------------------------------
# enable spawning vncviewer for domain's console
# (only valid when vnc=1), default = 0
#vncconsole=0
#----------------------------------------------------------------------------
# set password for domain's VNC console
# default is depents on vncpasswd in xend-config.sxp
vncpasswd=''
#----------------------------------------------------------------------------
# no graphics, use serial port
#nographic=0
#----------------------------------------------------------------------------
# enable stdvga, default = 0 (use cirrus logic device model)
#stdvga=0
#-----------------------------------------------------------------------------
# serial port re-direct to pty deivce, /dev/pts/n
# set password for domain's VNC console
# default is depents on vncpasswd in xend-config.sxp
vncpasswd=''
#----------------------------------------------------------------------------
# no graphics, use serial port
#nographic=0
#----------------------------------------------------------------------------
# enable stdvga, default = 0 (use cirrus logic device model)
#stdvga=0
#-----------------------------------------------------------------------------
# serial port re-direct to pty deivce, /dev/pts/n
# then xm console or minicom can connect
#serial='pty'
#-----------------------------------------------------------------------------
# Qemu Monitor, default is disable
# Use ctrl-alt-2 to connect
#monitor=1
#-----------------------------------------------------------------------------
# enable sound card support, [sb16|es1370|all|..,..], default none
#soundhw='sb16'
#-----------------------------------------------------------------------------
# set the real time clock to local time [default=0 i.e. set to utc]
#localtime=1
#-----------------------------------------------------------------------------
# set the real time clock offset in seconds [default=0 i.e. same as dom0]
#rtc_timeoffset=3600
#-----------------------------------------------------------------------------
# start in full screen
#full-screen=1
#-----------------------------------------------------------------------------
# Enable USB support (specific devices specified at runtime through the
# monitor window)
#usb=1
# Enable USB mouse support (only enable one of the following, `mouse' for
# PS/2 protocol relative mouse, `tablet' for
# absolute mouse)
#usbdevice='mouse'
#usbdevice='tablet'
#-----------------------------------------------------------------------------
# Set keyboard layout, default is en-us keyboard.
#keymap='ja'
Any help would be appreciated.
Gary Catalano
IT Manager
Cryptic Studios
(408) 399 -1969 x150 (office)
(650) 776-2500 (cell)
www.crypticstudios.com
16 years, 4 months
Panic with 32bit RHEL4 on 64bit RHEL5
by Jim Klein
Am experiencing a domU panic when running 32bit RHEL4 (2.6.9-67.ELxenU) on 64bit RHEL5 (2.6.18-53.el5xen) under high load conditions. Problem has not occurred (so far) when hosting the same domU on 32bit RHEL5, so I'm a little stumped. Any ideas or recommendations would be greatly appreciated. Thanks in advance!
Unable to handle kernel NULL pointer dereference at virtual address 00000000
printing eip:
c01496c9
2c84c000 -> *pde = 00000000:9a3e9027
1b3eb000 -> *pme = 00000000:bfd81067
1c064000 -> *pte = 00000000:00000000
Oops: 0000 [#1]
SMP
Modules linked in: md5 ipv6 autofs4 sunrpc dm_mirror xennet ext3 jbd dm_mod xenblk sd_mod scsi_mod
CPU: 0
EIP: 0061:[<c01496c9>] Not tainted VLI
EFLAGS: 00010287 (2.6.9-67.ELxenU)
EIP is at zap_pte_range+0x279/0x489
eax: 00046000 ebx: 00000000 ecx: f5392000 edx: 00000000
esi: 000b0b21 edi: c1f75bc0 ebp: 00000000 esp: e5aa3e04
ds: 007b es: 007b ss: 0068
Process amavisd (pid: 30894, threadinfo=e5aa3000 task=e54146c0)
Stack: b0b21067 00000000 00000000 00000000 00000000 00000000 00046000 0a800000
c202d2a0 e548a2a8 0a846000 00000000 0a800000 c0149980 c202d2a0 e548a2a0
0a800000 00046000 00000000 0a7c6000 e5486008 0a846000 00000000 c01499e5
Call Trace:
[<c0149980>] zap_pmd_range+0xa7/0xcb
[<c01499e5>] unmap_page_range+0x41/0x65
[<c0149ad6>] unmap_vmas+0xcd/0x1e8
[<c014ec19>] exit_mmap+0x85/0x15b
[<c011a2d9>] mmput+0x52/0x77
[<c011a74b>] copy_mm+0x36c/0x396
[<c011b26a>] copy_process+0x6b5/0xb0b
[<c011b7ad>] do_fork+0x8a/0x16b
[<c0105cff>] sys_clone+0x24/0x28
[<c010734f>] syscall_call+0x7/0xb
Code: 8b 4c 24 14 8b 41 04 85 c0 75 0a 83 39 00 0f 45 c1 89 44 24 14 c7 44 24 10 00 00 00 00 8b 44 24 18 39 44 24 10 0f 83 08 02 00 00 <8b> 55 00 8b 4d 04 85 d2 75 08 85 c9 0f 84 e6 01 00 00 88 d0 a8
16 years, 4 months
Update to Xen 3.1.2 available for testing
by Daniel P. Berrange
FYI, in both Fedora 7 & and Fedora 8, I have got new updates of the Xen
userspace to be sync to the latest Xen 3.1.2 bugfix release available for
testing. If you wish to test this, you can do
yum --enablerepo=updates-testing update xen
If there are no major problems reported I will push these to 'updates' in
about a week.
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
16 years, 4 months
fedora 8 : exit a windows VM
by nooroon
Hi,
I'm testing a fedora 8 and it was a good surprise for me : virtualization
tools are more usable, and virtualization with xen seems more stable.
I'm using xen to create a windows xp VM.
the only issue that I have, is when i ask windows to stop the machine, with
traditionnal windows tools : start>shutdown computer
the windows OS is stopping but the VM doesn't stop. It hangs on a windows
screen that says "you can now safely stop the computer".
With xen and fedora 7, I didn't have this issue. Does anyone have an
explanation?
16 years, 4 months
Problem booting Fedora 8 guest on FC6 host
by Robin Bowes
Hi,
I'm trying to get a Fedora 8 para-virtual guest to run on a FC6 host.
I had problems with the install because of the bugs in the 0.200 release
of virtinst. I fixed this by doing a source install of virtinst-0.300.
The F8 install completed succesfully, but when the guest boots I get
this msg:
<snip initial boot msgs>
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device "vg_skeggles/lv_root" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
Has anyone got any ideas about how to fix this?
I am currently using kernel-xen-2.6.20-1.2952.fc6 and xen 3.0.3-9.fc6
(I've upgraded to kernel-xen-2.6.20-1.3002.fc6 and xen-3.0.3-13.fc6 but
not rebooted yet).
My xen config file (created automatically by virt-install) is as follows:
name = "skeggles"
uuid = "a8912edd-ea7c-f324-f1bb-fdbc0c1a4b65"
maxmem = 512
memory = 512
vcpus = 1
bootloader = "/usr/bin/pygrub"
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
sdl = 0
vnc = 0
vncunused = 0
disk = [ "phy:/dev/vg_guests/lv_skeggles,xvda,w" ]
vif = [ "mac=00:16:3e:4c:82:c7,bridge=xenbr0" ]
Thanks,
R.
16 years, 4 months
recompile for using sdl and vnc
by nooroon
Hello,
I'm using fedora 7 with xen 3.1 from binaries rpm.
I try to use the sdl display, but when i configure my VM with
*<graphics type='sdl'/>
*
no window pops up.
Thanks to goolgle, I've found someone how got the same issue, and it
seems that qemu-dm was not compile whith sdl support.
What is the best way to recompile qemu-dm whith sdl support?
In fact, I'd like to have sdl for local display of my VM, and vnc for
remote access to it.
What configuration should I use to do so?
Thanks
16 years, 4 months
Guest Image File Size
by Aaron Metzger
virt-install has a checkbox which suggests that you can avoid
preallocating the entire guest image size -- that the guest image file
will grow on demand.
Does this work for Xen or is it only supported for KVM and the QEMU COW
files?
My experience when creating Xen guests as regular files is that I end up
with a file that is the full size even when I pick the option to not
preallocate the entire image.
--
Thanks,
Aaron
16 years, 4 months
