Re: [Fedora-xen] monitoring tools/ statistical information about Xen
by Matthias Bayer
Thanks Karel for these links, i will look into them soon !
Matthias
> -----Ursprüngliche Nachricht-----
> Von: Karel Zak <kzak(a)redhat.com>
> Gesendet: 18.04.06 22:15:25
> An: Matthias Bayer <matbayer.web(a)web.de>
> CC: fedora-xen(a)redhat.com
> Betreff: Re: [Fedora-xen] monitoring tools/ statistical information about Xen
>
> Se also http://skaya.enix.org/wiki/XenStats
>
> Karel
>
> On Tue, Apr 18, 2006 at 05:43:37PM +0200, Matthias Bayer wrote:
> >
> >
> > Hi,
> >
> > i'd like to do some performance tests as well as collect statistical information about usage of my xen system.
> >
> > i know there are the 'native' tools like 'xm' commands or some native linux commands like vmstat,top...
> >
> > xentop gives very good information but does somebody know how to track xentop output over time (days) to a file ?
> >
> > what i want to achive is collecting data about the usage of each DomU, network statistics, performance statistics of the DomU's, CPU/memory usage of each DomU as well as from Dom0.
> >
> > any recommendations about tools ? any ideas about the xentop/top output catching ?
> >
> > regards,
> >
> > Matthias
> >
> >
> >
> >
> >
> > SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
> > kostenguenstig. Jetzt gleich testen! *http://f.web.de/?mc=021192* [http://f.web.de/?mc=021192]
>
> > --
> > Fedora-xen mailing list
> > Fedora-xen(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-xen
>
>
> --
> Karel Zak <kzak(a)redhat.com>
_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
18 years
Running FC4 on FC5
by Robert Mortimer
I am attempting to run an FC4 image on an FC5 machine
I have prepped the image as per the FC4 quick start
my xen config is as follows
kernel ="/boot/vmlinuz-2.6.13-1.1532_FC4xenU"
memory = 100
name = "vm01"
vcpus = 1
vif= ['mac=FE:FD:25:63:74:49']
disk = [ 'file:/root/VM/fedora.img,sda1,w' ]
root = "/dev/sda1"
extra = "ro selinux=0 3"
All I get is
# xm create vm01
Using config file "vm01".
Error: Error creating domain: (22, 'Invalid argument')
Has anyone got a simple 1 NIC guest config for FC4 on FC5
I see that the new FC5 uses
An init image as part of the boot
A python based boot loader
and a python based install script
Is there any way to hack this lot to do an install like the FC5/FC5 one?
How are the init images built?
Will the new installer do other guest OS's in the future?
Robert
18 years
General question on running guests in FC5/Xen
by Srinivasan S
Hi
First of all apologies for making all of you read this long email. I
have posted to multiple lists to get my setup running. Inspite of
enthusiastic help I have not got it running yet and hence this
fundamental doubt.
I had a system running FC4 and Xen 2.x. The same system had normal
installations of Suse and Ubuntu. I had a running setup wherin I
started xen0 in FC4 and was able to run the installed Suse and Ubuntu
as guests within FC4. (This worked perfectly and I was able to
connect to the guests using both RealVNC and FreeNX.)
I have now upgraded to FC and have been attempting to get the same
setup running. I first tried with the official Xen tarballs. Not
successful, I then tried yesterday with the FC5 xen kernels. No
success. The problem in both cases is that Suse and Ubuntu guests
load but virtual networking does not work. Only lo interface is up.
On the main FC5 xen0 domain, I am able to see vifx.x being added as
and when a guest boots up, but the guest itself is without an
interface.
Various searches on Google finally got me one hint on loading module
xennet (for FC5) which I did in modprobe.conf. Same result.
Search on web got me guides to load guests from images, starting
guest installs from fedora, debian etc but could not find any info on
running already installed linux distros within Xen. The closet was
in the xen manual which explains how to make an image of an installed
linux distro and then running the image within xen.
Question: Is what Iam trying to achieve possibly with Xen 3.x (since
it worked with 2.x) ? If yes can anyone help ? My guest config file
is a very simple one :
kernel = << Tried both the xen kernel and the FC5 xenU kernel >>
memory = 100
name = "suseguest"
vif= ['mac=aa:00:10:00:00:10, bridge=xenbr0, ip=192.168.2.2']
Also tried vif= ['']
gateway = "192.168.1.1"
netmask = "255.255.255.0"
disk = ['phy:hdc3,hdc3,w']
Also tried disk = ['file:/dev/hdc3,hdc3,w']
root = "/dev/hdc3 rw"
Please note that OpenSUSE is installed on /dev/hdc3
All help is appreciated in resolving this.
Thanks and Best Regards
Srini
--
_______________________________________________
Check out the latest SMS services @ http://www.linuxmail.org
This allows you to send and receive SMS through your mailbox.
Powered by Outblaze
18 years
domU dhcp failure with default bridging
by Daniel Messina
I'm trying to walk through the FC5Xen Quickstart, but keep running into this
problem,
I've come accross the same problem on a x86_64 and seperate i386 machine.
After anaconda launches, I reach the Configure TCP/IP screen. My home
network is setup for DHCP.
I can't proceed past here.
Here's the output of brctl show:
xenbr0 8000.feffffffffff yes peth0
vif0.0
vif1.0
I have uninstalled iptables and selinux is set to permissive, trying to
duplicate conditions from previous posts to no avail.
Thanks for any help!
18 years
PCI devices in domU
by Timo Wendt
Hi,
I am trying to use PCI devices in guests. My grub.conf includes the
following:
title Fedora Core (2.6.16-1.2080_FC5xen0)
root (hd0,4)
kernel /xen.gz-2.6.16-1.2080_FC5
module /vmlinuz-2.6.16-1.2080_FC5xen0 ro root=/dev/
VolGroup00/LogVol00 rhgb pciback.hide=(02:09.0)(02:0e.0)
module /initrd-2.6.16-1.2080_FC5xen0.img
It doesn't work though:
Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb
pciback.hide=(02:09.0)(02:0e.0)
Unknown boot option `pciback.hide=(02:09.0)(02:0e.0)': ignoring
Is something not compiled into the kernel that is needed here?
I would appreciate any help.
Timo
18 years
monitoring tools/ statistical information about Xen
by Matthias Bayer
Hi,
i'd like to do some performance tests as well as collect statistical information about usage of my xen system.
i know there are the 'native' tools like 'xm' commands or some native linux commands like vmstat,top...
xentop gives very good information but does somebody know how to track xentop output over time (days) to a file ?
what i want to achive is collecting data about the usage of each DomU, network statistics, performance statistics of the DomU's, CPU/memory usage of each DomU as well as from Dom0.
any recommendations about tools ? any ideas about the xentop/top output catching ?
regards,
Matthias
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! *http://f.web.de/?mc=021192* [http://f.web.de/?mc=021192]
18 years
xm save/migrate doesn't work
by George
Hi,
I tried to use the "xm save" and "xm migrate" feature of Xen on FC5
(all updates installed, kernel is 2.6.16-1.2080_FC5xen0) but a "xm
save" fails with the message (from the xend.log):
--------------------------
[2006-04-16 20:39:12 xend] DEBUG (XendCheckpoint:79) [xc_save]:
/usr/lib64/xen/bin/xc_save 10 17 27 0 0 0
[2006-04-16 20:39:12 xend] ERROR (XendCheckpoint:226) Unable to get
platform info.: 9
[2006-04-16 20:39:12 xend] ERROR (XendCheckpoint:98) Save failed on
domain fc5test (27).
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py",
line 92, in save
forkHelper(cmd, fd, saveInputHandler, False)
File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py",
line 217, in forkHelper
raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib64/xen/bin/xc_save 10 17 27 0 0 0 failed
--------------------------
The same problem exists with "xm migrate" because it calls a "xm
save". It looks like this problem is releated to FC5 and Xen because
on other (non FC5) platforms it works.
Are there any workarounds for this problem?
18 years
Re: [Fedora-xen] FC5/Xen -> Running other OS as Guest within FC5
by Srinivasan S
I just tried ..
Message is: FATAL Module xennet not found
Any idea where I can get this from ?
Cheers
Srini
> ----- Original Message -----
> From: "Todd Deshane" <deshantm(a)gmail.com>
> To: "Srinivasan S" <ssrini(a)linuxmail.org>
> Subject: Re: [Fedora-xen] FC5/Xen -> Running other OS as Guest within FC5
> Date: Mon, 17 Apr 2006 09:54:10 -0400
>
>
> did you try: modprobe xennet
>
> On 4/17/06, Srinivasan S <ssrini(a)linuxmail.org> wrote:
> >
> > Hi Folks,
> >
> > I have FC5 installed with Xen 3.x from the official
> > xensource.comtarball. The dom0 boots perfectly. I have a
> > multiboot system with FC5
> > installed on /dev/sda6, OpenSUSE installed on /dev/hdc3 and Ubuntu on
> > /dev/hdc1.
> >
> > Goal: I am trying to get Ubuntu and Suse to run within my FC5/Xen box. (I
> > had this working earlier in FC4 and Xen 2.x without issues)
> >
> > The configuration file I use is : /etc/xen/suseguest (contents)
> >
> > kernel = "/boot/vmlinuz-2.6.16-xen"
> > memory = 100
> > name = "suseguest"
> > vif= ['mac=aa:00:10:00:00:10, bridge=xenbr0, ip=192.168.2.2']
> > gateway = "192.168.1.1"
> > netmask = "255.255.255.0"
> > disk = ['file:/dev/hdc3,hdc3,w']
> > root = "/dev/hdc3 rw"
> >
> > (As a variation to the above I also tried vif=[''] etc with no avail)
> >
> > On running /usr/sbin/xm create -c /etc/xen/suseguest I get a number of
> > errors
> > on module load that modules.dep file is not found etc .. However the boot
> > process continues uninterrupted and Iam finally provided the terminal
> > login
> > prompt. Iam also able to successfully login.
> >
> > After logging in, however an ifconfig reveals that the virtual if
> > 192.168.2.2 is not setup .. only loopback is enabled (127.x.x.x) ..
> >
> > I tried ubuntuguest (same config as above, disk is /dev/hdc1) but with the
> > same
> > result.
> >
> > (To remove the modules.dep problem, I also copied the files from my FC5
> > /lib/modules/2.6.16-xen/ folder to Suse and tried, no errors but networking
> > still does not work)
> >
> > The dom0 ifconfig reveals that the bridge and peth0 etc are all setup
> > properly.
> > All help to get this "networking issue" resolved is appreciated.
> >
> > Regards
> > Srini
> >
> > --
> > _______________________________________________
> > Check out the latest SMS services @ http://www.linuxmail.org
> > This allows you to send and receive SMS through your mailbox.
> >
> > Powered by Outblaze
> >
> > --
> > Fedora-xen mailing list
> > Fedora-xen(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-xen
> >
>
--
_______________________________________________
Check out the latest SMS services @ http://www.linuxmail.org
This allows you to send and receive SMS through your mailbox.
Powered by Outblaze
18 years
FC5/Xen -> Running other OS as Guest within FC5
by Srinivasan S
Hi Folks,
I have FC5 installed with Xen 3.x from the official xensource.com tarball. The dom0 boots perfectly. I have a multiboot system with FC5 installed on /dev/sda6, OpenSUSE installed on /dev/hdc3 and Ubuntu on /dev/hdc1.
Goal: I am trying to get Ubuntu and Suse to run within my FC5/Xen box. (I had this working earlier in FC4 and Xen 2.x without issues)
The configuration file I use is : /etc/xen/suseguest (contents)
kernel = "/boot/vmlinuz-2.6.16-xen"
memory = 100
name = "suseguest"
vif= ['mac=aa:00:10:00:00:10, bridge=xenbr0, ip=192.168.2.2']
gateway = "192.168.1.1"
netmask = "255.255.255.0"
disk = ['file:/dev/hdc3,hdc3,w']
root = "/dev/hdc3 rw"
(As a variation to the above I also tried vif=[''] etc with no avail)
On running /usr/sbin/xm create -c /etc/xen/suseguest I get a number of errors
on module load that modules.dep file is not found etc .. However the boot
process continues uninterrupted and Iam finally provided the terminal login
prompt. Iam also able to successfully login.
After logging in, however an ifconfig reveals that the virtual if
192.168.2.2 is not setup .. only loopback is enabled (127.x.x.x) ..
I tried ubuntuguest (same config as above, disk is /dev/hdc1) but with the same
result.
(To remove the modules.dep problem, I also copied the files from my FC5 /lib/modules/2.6.16-xen/ folder to Suse and tried, no errors but networking still does not work)
The dom0 ifconfig reveals that the bridge and peth0 etc are all setup properly.
All help to get this "networking issue" resolved is appreciated.
Regards
Srini
--
_______________________________________________
Check out the latest SMS services @ http://www.linuxmail.org
This allows you to send and receive SMS through your mailbox.
Powered by Outblaze
18 years
Error creating Domain
by shyamal thatte
Hi,
Need help please
XEN 3.0.1 on FC4 is domain 0.
Installed FC4 on /dev/hda8 separate installation.
When trying to 'xm create ' fails with error 0
There does not seem to be a Xen 3 User kernel. Can one create it ?
Attached please find the xend logs and configuration file
Thanks in advance for your help.
Regards
Shyamal
# -*- 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.
#============================================================================
#----------------------------------------------------------------------------
# Kernel image file.
kernel = "/boot/vmlinuz-2.6.12-1.1390_FC4xenU"
# Optional ramdisk.
#ramdisk = "/boot/initrd-2.6.12-1.1390_FC4xenU.img"
# The domain build function. Default is 'linux'.
#builder='linux'
# Initial memory allocation (in megabytes) for the new domain.
memory = 64
# A name for your domain. All domains must have different names.
name = "Oratest"
# 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
# Number of Virtual CPUS to use, default is 1
#vcpus = 1
#----------------------------------------------------------------------------
# Define network interfaces.
# By default, no network interfaces are configured. You may have one created
# with sensible defaults using an empty vif clause:
#
# vif = [ '' ]
#
# or optionally override backend, bridge, ip, mac, script, type, or vifname:
#
# vif = [ 'mac=00:16:3e:00:00:11, bridge=xenbr0' ]
#
# or more than one interface may be configured:
#
# vif = [ '', 'bridge=xenbr1' ]
vif = [ '' ]
#----------------------------------------------------------------------------
# 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:hda8,hda8,w' ]
disk = [ 'phy:hda6,hda6,w' ]
#----------------------------------------------------------------------------
# Define to which TPM instance the user domain should communicate.
# The vtpm entry is of the form 'instance=INSTANCE,backend=DOM'
# where INSTANCE indicates the instance number of the TPM the VM
# should be talking to and DOM provides the domain where the backend
# is located.
# Note that no two virtual machines should try to connect to the same
# TPM instance. The handling of all TPM instances does require
# some management effort in so far that VM configration files (and thus
# a VM) should be associated with a TPM instance throughout the lifetime
# of the VM / VM configuration file. The instance number must be
# greater or equal to 1.
#vtpm = [ 'instance=1,backend=0' ]
#----------------------------------------------------------------------------
# Set the kernel command line for the new domain.
# You only need to define the IP parameters and hostname if the domain's
# IP config doesn't, e.g. in ifcfg-eth0 or via DHCP.
# You can use 'extra' to set the runlevel and custom environment
# variables used by custom rc scripts (e.g. VMID=, usr= ).
# Set if you want dhcp to allocate the IP address.
#dhcp="dhcp"
# Set netmask.
#netmask=255.255.255.0
# Set default gateway.
#gateway=192.168.5.7
# Set the hostname.
#hostname= "vm%d" % vmid
#hostname= "oratest"
vmid=1
# Set root device.
root = "/dev/hda8 ro"
# Root device for nfs.
#root = "/dev/nfs"
# The nfs server.
#nfs_server = '169.254.1.0'
# Root directory on the nfs server.
#nfs_root = '/full/path/to/root/directory'
# Sets runlevel 4.
extra = "4"
#----------------------------------------------------------------------------
# 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'
#============================================================================
18 years
