Mac Address Confusion
by thingsmith@comcast.net
I am confused about XEN mac addresses. The Xen wiki is confusing it said not to use mac address starting with 00 but the default is 00:16:3e
What is the correct mac address range to use?
--
Harry Smith
thingsmith(a)comcast.net
18 years, 1 month
Xen and LVM
by Felipe Alfaro Solana
Hello.
I'm having problems using xenguest-install.py when trying to install a
FC5 DomU into an LVM volume:
# xm create -c Download
Using config file "/etc/xen/Download".
Traceback (most recent call last):
File "/usr/bin/pygrub", line 256, in ?
cf = get_config(file, isconfig)
File "/usr/bin/pygrub", line 119, in get_config
fs = fstype.open_fs(fn, offset)
File "/usr/lib/python2.4/site-packages/grub/fsys/ext2/__init__.py",
line 35, in open_fs
return Ext2Fs(fn, offset = offset)
ValueError: unable to open file
Error: Boot loader didn't return any data!
The volume was formatted by using mkfs.ext3.
# stat /dev/Main/Download
File: `/dev/Main/Download' -> `/dev/mapper/Main-Download'
Size: 25 Blocks: 0 IO Block: 4096 symbolic link
Device: fh/15d Inode: 5571 Links: 1
Access: (0777/lrwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2006-04-15 18:51:46.000000000 +0200
Modify: 2006-04-15 18:36:13.501729841 +0200
Change: 2006-04-15 18:36:13.501729841 +0200
This is the domain configuration file:
# Automatically generated xen config file
name = "Download"
memory = "256"
disk = [ 'phy:Main/Download,xvda,w' ]
#disk = [ 'phy:/dev/Main/Download,xvda,w' ]
vif = [ 'mac=00:16:3e:0c:b1:ef' ]
bootloader="/usr/bin/pygrub"
on_reboot = 'restart'
on_crash = 'restart'
Any ideas?
Thanks.
18 years, 1 month
Need 6 VIF in a DomU but not succeeding
by thingsmith@comcast.net
I am trying to have figure Xen 3.0 / FC 5 but seem to be having network problems.
I need to confiure DomU to have 6 network interfaces (vif). 4 of the interfaces need to communication in one network but 6 differnt sub nets 2 interfaces in a completely different network. For example, there would one interface each of the four subnets in192.168.1.0/26. The other two would be in 192.168.2.0/25.
In the configuration file I have the 4 vifs 192.168.1.0/26 into a single xenbr0. Each of the 192.168.2.0/25 are in differnt briges.
In a non-Xen environment I have used overlays on a single NIC. I tried the same in Xen but it seems to count the overlays as vifs.
The best that I have been able to do is 3 vifs
Any suggestion would be greatly appreciated.
--
Harry Smith
thingsmith(a)comcast.net
18 years, 1 month
Xen and GFS
by Jim Klein
I'm trying to get Xen to work in a using GFS on a SAN and FC5, but am
not having much luck. It looks like GFS can't get a lock on the xvd
file, for some reason, and I can't figure it out. I am able to read
and write to GFS in any other way, from all the nodes, without
problem. Can't install directly to the GFS volume, and if I install
on a local drive, copy to GFS volume, and load, I end up with a read
only file system. Log below. Any assistance would be greatly
appreciated.
Apr 14 10:47:36 blade1 kernel: GFS: fsid=alpha:gfs1.1: time =
1145036856
Apr 14 10:55:42 blade1 kernel: GFS: fsid=alpha:gfs1.1: warning:
assertion "gfs_glock_is_locked_by_me(ip->i_gl)" failed
Apr 14 10:55:42 blade1 kernel: GFS: fsid=alpha:gfs1.1: function =
gfs_prepare_write
Apr 14 10:55:42 blade1 kernel: GFS: fsid=alpha:gfs1.1: file = /usr/
src/build/729060-x86_64/BUILD/xen0/src/gfs/ops_address.c, line = 329
18 years, 1 month
no eth0 in guest
by Rainer Fuegenstein
Hi,
I'm running FC5 with the current 2.6.16-1.2080_FC5xen0 kernel in Dom0. I
managed to set up several guests:
1) image-file based FC5 installed via xenguest-install.py. this one has
the eth0 device and a working network, but I don't want to use the image
file, but LVM volumes (which seems not possible with xenguest-install.py)
2) a centos 4.2 based on an image file I downloaded from a web site.
this one has no eth0 device in the guest, therefore networking doesn't work.
3) FC4 using LVM volumes, installed via "yum -c
http://people.redhat.com/~katzj/yum-xen.conf --installroot=/mnt -y
groupinstall Base". this one also has no eth0 device in the guest.
4) FC5 using LVM volumes, installed via "yum --installroot=/mnt/ -y
groupinstall base". this one also has no eth0 device in the guest.
in the latter case, ifconfig in Dom0 looks like this:
eth0 Link encap:Ethernet HWaddr 00:01:02:B5:F8:90
inet addr:192.168.5.10 Bcast:192.168.5.255 Mask:255.255.255.0
inet6 addr: fe80::201:2ff:feb5:f890/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:855425 errors:0 dropped:0 overruns:0 frame:0
TX packets:995199 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:568177794 (541.8 MiB) TX bytes:467490312 (445.8 MiB)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:855428 errors:0 dropped:0 overruns:1 frame:0
TX packets:995245 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:568177957 (541.8 MiB) TX bytes:468158849 (446.4 MiB)
Interrupt:9 Base address:0xe000
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:995199 errors:0 dropped:0 overruns:0 frame:0
TX packets:855427 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:467490312 (445.8 MiB) TX bytes:568177962 (541.8 MiB)
vif6.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:2715 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:359 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:41441 (40.4 KiB) TX bytes:468 (468.0 b)
domain config file:
name = "fc5"
memory = "128"
kernel="/boot/vmlinuz-2.6.16-1.2080_FC5xenU"
vif = [ 'mac=00:16:3e:4c:77:fa' ]
disk = [ 'phy:/dev/vg_data/lv_fc5_root,sda1,w',
'phy:/dev/vg_data/lv_fc5_data,sda2,w',
'phy:/dev/vg_data/lv_fc5_swap,sda3,w' ]
root="/dev/sda1"
extra = "ro selinux=0 3"
on startup, the FC5 domain doesn't complain about missing kernel modules
etc. I also installed the kernel-xenU-2.6.16-1.2080_FC5.i686.rpm in the
guest, but that didn't help.
any idea what I have to do to get an eth0 in the guest ?
tnx in advance.
18 years, 1 month
FC5 Xen and GFS
by Jim Klein
I'm trying to get Xen to work in a using GFS on a SAN and FC5, but am
not having much luck. It looks like GFS can't get a lock on the xvd
file, for some reason, and I can't figure it out. I am able to read
and write to GFS in any other way, from all the nodes, without
problem. Can't install directly to the GFS volume, and if I install
on a local drive, copy to GFS volume, and load, I end up with a read
only file system. Log below. Any assistance would be greatly
appreciated.
Apr 14 10:47:36 blade1 kernel: GFS: fsid=alpha:gfs1.1: time =
1145036856
Apr 14 10:55:42 blade1 kernel: GFS: fsid=alpha:gfs1.1: warning:
assertion "gfs_glock_is_locked_by_me(ip->i_gl)" failed
Apr 14 10:55:42 blade1 kernel: GFS: fsid=alpha:gfs1.1: function =
gfs_prepare_write
Apr 14 10:55:42 blade1 kernel: GFS: fsid=alpha:gfs1.1: file = /usr/
src/build/729060-x86_64/BUILD/xen0/src/gfs/ops_address.c, line = 329
18 years, 1 month
xen + lvm + backup ?
by Rainer Fuegenstein
Hi,
I wonder how to perform a backup (in Dom0) of several DomU's running in
a Dom0.
fact: a filesystem that is used by a DomU should not be mounted in Dom0
when the DomU is running and accessing it/writing to it. possible
solution would be to shutdown DomU, backup its file systems in Dom0 and
restart DomU.
If the DomU uses devices which are LVM volumes in dom0, a possible
scenario could be:
- create a snapshot in Dom0 of the LVM volume which is used by DomU
- mount the snapshot volume in Dom0
- back it up in Dom0
- unmount & remove the snapshot in Dom0.
could this work ?
regards,
rainer.
18 years, 1 month
Re: [Fedora-xen] How to configure eth0 via xen config files
by Walter Souto
Hi,
> I think you can either configure the guest with static information or
> use DHCP. I may have missed something in the question though.
>
No you didn't. Maybe my question don't make sense...
But It's exactly what I'm doing now. So, if I need to replicate about
20 guests, each one with your own static IP, I can use DHCP and
enforce IP's using mac addr. But, is it possible to do this using the
Xen configuration files for the vm's? Just to get somethings a bit
simple avoiding DHCP.
And thanks for your answer.
--
Walter.
18 years, 1 month
RE: [Fedora-xen] two fully virtualized systems crashing
by Matthias Bayer
done !
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=188948 [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=188948]
thanks again for all the help and hints !
Matthias
*Von:* "Stephen C. Tweedie" <SCT(a)REDHAT.COM>
*Gesendet:* 13.04.06 21:43:53
*An:* Matthias Bayer <MATBAYER.WEB(a)WEB.DE>
*CC:* "You, Yongkang" <YONGKANG.YOU(a)INTEL.COM>, fedora-xen(a)redhat.com, Stephen Tweedie <SCT(a)REDHAT.COM>
*Betreff:* RE: [Fedora-xen] two fully virtualized systems crashing
Hi,
On Thu, 2006-04-13 at 10:03 +0200, Matthias Bayer wrote:
> setting my Dom0 memory with dom0_mem=2G as kernel parameter fixed the problem !!
> before i haven't specified anything - so if i understand it right all the memory would belong to Dom0 and every DomU that starts 'grabs' a bit until Dom0-min-mem is reached.
> so does this behaviour then indicate that something with balooning is buggy ??
Yes, it might do: could you open a bugzilla with exact steps to
reproduce this so that we can track it, please?
Many thanks,
Stephen
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, 1 month
RE: [Fedora-xen] two fully virtualized systems crashing
by Matthias Bayer
OK - found the problem !
setting my Dom0 memory with dom0_mem=2G as kernel parameter fixed the problem !!
before i haven't specified anything - so if i understand it right all the memory would belong to Dom0 and every DomU that starts 'grabs' a bit until Dom0-min-mem is reached.
so does this behaviour then indicate that something with balooning is buggy ??
thanks Stephen and Yongkang for the help so far !
Matthias
> -----Ursprüngliche Nachricht-----
> Von: "You, Yongkang" <yongkang.you(a)intel.com>
> Gesendet: 13.04.06 09:35:54
> An: "Stephen C. Tweedie" <sct(a)redhat.com>
> CC: <fedora-xen(a)redhat.com>
> Betreff: RE: [Fedora-xen] two fully virtualized systems crashing
> Hi Matthias,
>
> >Mem: 3501056 684452 2816604 0 69520
> I am not quite clear about the dom0 memory. Is it 3.5G?
>
> How large the memory apply to dom0? I mean how about dom0_mem=.
>
> Best Regards,
> Yongkang (Kangkang) ÓÀ¿µ
>
> >-----Original Message-----
> >From: fedora-xen-bounces(a)redhat.com
> >[mailto:fedora-xen-bounces@redhat.com] On Behalf Of Matthias Bayer
> >Sent: 2006Äê4ÔÂ13ÈÕ 15:30
> >To: Stephen C. Tweedie
> >Cc: fedora-xen(a)redhat.com
> >Subject: RE: [Fedora-xen] two fully virtualized systems crashing
> >
> >
> >
> >I have 4 GB of RAM, each DomU has 512 MB and i only try to run 2
> >windows DomU's !
> >
> > total used free shared buffers
> >cached
> >Mem: 3501056 684452 2816604 0 69520
> >347260
> >-/+ buffers/cache: 267672 3233384
> >Swap: 2096440 0 2096440
> >
> >do i need to configure something elswhere to give the hypervisor more
> >memory ?
> >can i create any other debugs that may be helpful to find the problem ?
> >
> >regards,
> >Matthias
> >
> >> Hi,
> >>
> >> On Wed, 2006-04-12 at 17:29 +0200, Matthias Bayer wrote:
> >> >
> >> > (0 of 1)XEN) DOM
> >> > (XEN) Couldn't alloc shadow page! dom3 count=893o map I/O space
> >> > 000f03
> >> > (XEN) Shadow table counts: l1=0 l2=0 hl2=0
> >>
> >> This looks like the hypervisor ran out of memory. How much memory do
> >> you have, and how much is being given to each domain?
> >>
> >> --Stephen
> >>
> >>
> >
> >
> >______________________________________________________________
> >_
> >SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
> >kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
> >
> >--
> >Fedora-xen mailing list
> >Fedora-xen(a)redhat.com
> >https://www.redhat.com/mailman/listinfo/fedora-xen
_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
18 years, 1 month