initscripts, xen and bonding
by Axel Thimm
Hi,
I'm having a hard time getting bonding to work on FC5t3. It looks like
the bond0 interface bond0 is renamed to pbond0 by xen [*] and the
enslaving does not work anymore then. It works if I log on the
terminal and ifenslave the devices to pbond0 instead of bond0 after
the boot process has finished.
But I want this to be handled automatically during reboots, so I tried
assigning the bonding slaves to pbond0 as a master in the
ifcfg-eth{0,1} scripts, but that doesn't work.
What is causing the bond0 rename and should this renaming be
considered by initscript? Is this a user error or should I file this
against bugzilla? xen or initscripts?
Thanks!
[*] The only reference I found was a Japanese site and google's
translation of it.
http://translate.google.com/translate?hl=en&sl=ja&u=http://hoop.euqset.or...
--
Axel.Thimm at ATrpms.net
16 years, 7 months
Re: [Fedora-xen] VLANs on DomU domains
by Bertho Stultiens
> I am setting up a box with FC6 + xen with FC6 for the DomU guests.
> I have a server with 4 gigabit ports and I want to use 802.1Q vlans on
> one of the gig ports.
> I have the VLANs configured in Dom0 without any addresses attached to
> them.
> How do I make the VLANs available to the guests? I want to make 4
> VLANs available to each guest. I have thought of a few alternatives
> but I cannot get any to work.
The easy way; I have installed FC6 with 802.1Q and 4 guests. It works
very nicely. For each guest do:
1 - You need to enable vlans /etc/sysconfig/network.
NETWORKING=yes
VLAN=yes
NETWORKING_IPV6=no
HOSTNAME=xenbox2.example.com
GATEWAY=192.168.42.1
2 - create a subinterface by file editting
/etc/sysconfig/network-scripts/ifcfg-eth0.42:
DEVICE=eth0.42
BOOTPROTO=static
ONBOOT=yes
IPADDR=192.168.42.102
NETMASK=255.255.255.0
TYPE=Ethernet
3 - depending on whether you want untagged packets on the same
interface, you need to edit the /etc/.../ifcfg-eth0 file too. (note: the
parent interface must be up for the tagged interface to work.) The lines
commented out will assign an IP address to the untagged interface:
DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
TYPE=Ethernet
# BOOTPROTO=static
# IPADDR=172.16.42.102
# NETMASK=255.255.255.0
4 - make sure that your /etc/hosts setup is correct. If you have DNS
available 24/7, then only define localhost[.localdomain} as 127.0.0.1
and not the hostname itself.
When you restart the network in the guest, then your guest will default
to use the tagged interface vlan 42 (above example). If you want the
untagged interface as default, then you can change the gateway and
assign an IP address to it.
On the host, you need to do a similar thing. Create a subinterface
eth0.42 and assign an IP address to it. Once that is done, you can talk
to your guests via dot1Q from your host.
Beware of iptables! If you have a firewall setup, then you need to make
sure that it is done right. Doing it right, though, is a though job with
dot1Q in place. I have the firewall completely disabled on the host and
guests. My firewall is placed physically separated on another box.
> 1. Bridge the tagged 802.1Q stream from the Gig port through to the
> guests and configure eth0.x. on the guests
This would be above scenario.
> 2. Create a bridge on Dom0 for each VLAN so that they appear as
> eth0...eth3 on the guests.
The xenbrX interfaces on the host already transport all packets because
they are L2 bridges (see brctl). The bridge does not care whether the
packets are .1Q tagged or not. The only thing you need is to instruct
the kernel to look for/act on specifics by creating (sub-)interfaces.
Now, if you want the guests not to know that they are connected to a
VLAN, then you need a brigde-interface to do (un-)tagging for you. That
means that you need to create a dot1Q subinterface on the host's
physical peth[0-3] and add the subinterface to a new bridge.
Normal scenario:
peth0 -> xenbr0 -> vif0.0(host eth0)
vif1.0(guest1 eth0)
Dot1Q scenario:
peth0.42 -> xenbr42 -> vif1.0(guest1 eth0)
i.e.:
# brctl addbr xenbr42
# ip link set xenbr42 up
# vconfig add peth0 42
# ip link set peth0.42 up
# brctl addif xenbr42 peth0.42
In the VM config you have now something like:
vif = [ 'mac=00:16:3e:11:22:33, bridge=xenbr42', ]
The VM's eth0 interface is created as part of bridge that will fowrard
to a subinterface. The kernel will now do the tagging/untagging (note:
slow) and the VM cannot see that it is attached to a VLAN.
Theoretically it should work, but I was not able to make this scenario
work as expected though. I suspect that the hosts peth0 -> eth0 bridge
is interfering (which has a tagged interface too in my setup). Or maybe
my fingers were too fast at typing and I forgot a simple thing...
> The xen documentation is minimal for configuring VLANs. Is there a
> (FC6) supported way of configuring them?
Vlans is a no-issue for xen. It is layered in the network and xen only
passes the packets.
--
Greetings Bertho
Bertho Stultiens
Senior Systems Manager
Mobilethink A/S
16 years, 7 months
Simple testing results for Xen and VMX on FC5-test2.
by You, Yongkang
Hi all,
I have done a simple checking for Xen and VMX on FC5-test2. Basically, I can create VMX on FC5-test2 IA32. But FC5-test2 IA32e (x86-64) doesn't provide Xen and Xen0 kernel, so didn't do Xen and VMX testing for it.
Beside of testing Xen and VMX, I also found some issues about installation, which I have updated the bug #179078 as a NB. The following is the testing results only for Xen and VMX.
=========================
1. *** IA32E hasn't RPMS about Xen hypervisor and Xen0/XenU kernels. __FAIL__
2. *** In order to boot up IA32 Xen0, I have to add pci=noacpi as the boot
parameters of Xen0 kernel, or system will hang when initial PCI. I don't know if it is only related to my Machine. __FAIL__
3. After install IA32 Xen RPMs, I can see /boot/grub/grub.conf has been changed
with Xen kernels. __PASS__
4. *** /usr/lib/xen/boot/vmxloader isn't in the RPM package, so VMX Guest
couldn't be created. I suspected build system hasn't bcc, it is from DEV86
package. __FAIL__
5. After copy a useable vmxloader to the destination, IA32 VMX Guest can be
created successfully! __PASS__
6. VMX has good network connection and Xwindows started. __PASS__
7. XenU can be created and works well. __PASS__
8. Couldn't get Xen Changeset by "xm info" or "xm dmesg".
9. The new kernel names of Xen/Xen0/XenU seemed a little confused. E.g. the Xen0 name is like vmlinuz-2.6.15-1.29_FC5hypervisor. I thought hypervisor is for Xen.gz. Xen0 is the Service OS.
==========================
Any comments please let me know. But I will have 8 days holiday from tomorrow, so emails reply might be slow and occasional.
[FYI] We are planning to do more testing for FC5-test3.
Best Regards,
Yongkang (Kangkang) 永康
16 years, 8 months
Using large disk in DomU
by Robin Bowes
Hi,
I'm running Xen 3.0.3 on FC6 with FC6 DomU guests.
On the Dom0 machine, I have 8 x 500GB disks running as a RAID6 array
with lvm on top of that. There is one partition available:
/dev/vg_media/lv_media which has an ext3 FS on it.
I want to make this available to a DomU guest, so I put this in the xen
config file:
disk = [ 'phy:/dev/vg_host/lv_slim,xvda,w',
'phy:/dev/vg_media/lv_media,sda1,w', ]
The disk appears in the DomU guest, but if I fsck it, this is what I see:
# fsck /dev/sda1
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
The filesystem size (according to the superblock) is 732575744 blocks
The physical size of the device is 195704832 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? yes
Any idea what's going on here? Am I doing something wrong?
R.
16 years, 9 months
cobbler problem virt_mem virt_file_size
by Mario Verbelen
Hi,
As you can see below there is a bug when you don't use the default
virt_ram virt_file_size
Even when I give it to the profile add the settings are correctly saved
(/var/lib/cobbler/profiles)
but when cobbler list you don't see your setting
when using koan he also doesn't see the setting
my problem is that i don't have 512MB free memory so it fails
cobbler profile add --name=fc6test --distro=fc6test --virt-file-size=3
--virt-ram=96
cobbler list
defaults
kernel options : append devfs=nomount ramdisk_size=16438 lang= vga=788
ksdevice=eth0
distro 1 : fc6test
kernel : /boot/vmlinuz-2.6.18-1.2798.fc6xen
initrd : /boot/initrd-2.6.18-1.2798.fc6xen.img
kernel options :
architecture : x86
ks metadata :
distro 2 : var_www_cobbler_localmirror_fc6_images_pxeboot
kernel : /var/www/cobbler/localmirror/fc6/images/pxeboot/vmlinuz
initrd : /var/www/cobbler/localmirror/fc6/images/pxeboot/initrd.img
kernel options :
architecture : x86
ks metadata :
profile 1 : fc6test
distro : fc6test
kickstart : /etc/cobbler/default.ks
kernel options :
ks metadata :
virt name : fc6test
virt file size :
virt ram :
virt paravirt :
profile 2 : var_www_cobbler_localmirror_fc6_images_pxeboot
distro : var_www_cobbler_localmirror_fc6_images_pxeboot
kickstart : /etc/cobbler/kickstart_fc5.ks
kernel options :
ks metadata : tree=http://127.0.0.1/localmirror/fc6
virt name : var_www_cobbler_localmirror_fc6_images_pxeboot
virt file size :
virt ram :
virt paravirt :
There are no configured System records.
koan --virt --profile=fc6test --server=localhost
- processing profile: fc6test
- fetching configuration for profile: fc6test
- url=http://localhost/cobbler/profiles/fc6test
- {'kickstart': 'http://127.0.0.1/cobbler/kickstarts/fc6test/ks.cfg',
'name': 'fc6test', 'virt_ram': '', 'virt_paravirt': '',
'kernel_options': 'lang ksdevice=eth0 vga=788 devfs=nomount
ramdisk_size=16438', 'virt_name': 'fc6test', 'virt_file_size': '',
'distro': 'fc6test', 'ks_meta': ''}
- fetching configuration for distro: fc6test
- url=http://localhost/cobbler/distros/fc6test
- {'kernel': '/boot/vmlinuz-2.6.18-1.2798.fc6xen', 'ks_meta': '',
'kernel_options': 'lang ksdevice=eth0 vga=788 devfs=nomount
ramdisk_size=16438', 'initrd': '/boot/initrd-2.6.18-1.2798.fc6xen.img',
'arch': 'x86', 'name': 'fc6test'}
- downloading initrd initrd-2.6.18-1.2798.fc6xen.img
to /tmp/initrd-2.6.18-1.2798.fc6xen.img
-
url=http://localhost/cobbler/images/fc6test/initrd-2.6.18-1.2798.fc6xen.img
- downloading kernel vmlinuz-2.6.18-1.2798.fc6xen
to /tmp/vmlinuz-2.6.18-1.2798.fc6xen
-
url=http://localhost/cobbler/images/fc6test/vmlinuz-2.6.18-1.2798.fc6xen
- kernel saved = /tmp/vmlinuz-2.6.18-1.2798.fc6xen
- initrd saved = /tmp/initrd-2.6.18-1.2798.fc6xen.img
- invalid RAM size specified, defaulting to 256 MB
- invalid file size specified, defaulting to 1 GB
libvir: Xen Daemon error : GET operation failed: No such domain 6
libvir: Xen Daemon error : POST operation failed: (xend.err 'Error
creating domain: I need 262144 KiB, but dom0_min_mem is 262144 and
shrinking to 262144 KiB would leave only -15940 KiB free.')
Failed to create domain fc6test
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/koan/app.py", line 96, in main
k.run()
File "/usr/lib/python2.4/site-packages/koan/app.py", line 154, in run
self.do_virt()
File "/usr/lib/python2.4/site-packages/koan/app.py", line 295, in
do_virt
return self.do_net_install("/tmp",after_download)
File "/usr/lib/python2.4/site-packages/koan/app.py", line 253, in
do_net_install
after_download(self, distro_data, profile_data)
File "/usr/lib/python2.4/site-packages/koan/app.py", line 294, in
after_download
self.do_virt_net_install(profile_data, distro_data)
File "/usr/lib/python2.4/site-packages/koan/app.py", line 574, in
do_virt_net_install
extra=kextra
File "/usr/lib/python2.4/site-packages/koan/virtcreate.py", line 196,
in start_paravirt_install
dom = conn.createLinux(cfgxml, 0)
File "/usr/lib/python2.4/site-packages/libvirt.py", line 249, in
createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed')
libvirtError: virDomainCreateLinux() failed
cat /var/lib/cobbler/profiles
---
-
distro: &1 var_www_cobbler_localmirror_fc6_images_pxeboot
kernel_options: ''
kickstart: /etc/cobbler/kickstart_fc5.ks
ks_meta: 'tree=http://127.0.0.1/localmirror/fc6'
name: *1
virt_file_size: ''
virt_name: *1
virt_paravirt: ''
virt_ram: ''
-
distro: fc6test
kernel_options: ''
kickstart: /etc/cobbler/default.ks
ks_meta: ''
name: fc6test
virt_file_size: 3
virt_name: virtguest
virt_paravirt: True
virt_ram: 96
16 years, 9 months
Networking inside DomU
by Ian Patton
Does anyone know what is required to get networking working inside of a
DomU?
I have only one running, and it is using the default network-bridge setup
from virt-manager
I am running Vista in the domain and it sees the virtual NIC, but gives it
one of those auto-config IP addresses from the 169.254.x.x range
Thanks in advance
--
Ian Patton
16 years, 10 months
Mouse out of sync on guest machines
by Filipe Miranda
Hello,
After installing FC6 and the virtualization pack, I managed to install a FC6
as guest OS. No problem at all (just the fact that I had to set xm mem-set 0
256, and them xm mem-max 0 256 for the the virtual manager to let me create
the guest machines *my machine has 512RAM)
Anyway, everything worked just fine, but I noticed the the my mouse pointer
is totally out of sync in either text mode or graphic mode.
Is anyone having the same issue? Or is it a bug? or a misconfiguration?
Regards,
--
---
Filipe T Miranda
16 years, 10 months
RE: [Fedora-xen] Mouse out of sync on guest machines
by Spuhler, Peter
Yes I've been experiencing the same mouse problem although less
noticeably when using SDL and have also had the keyboard lock up. Sofar
I haven't seen a solution to this problem.
My setup in a 2cpu dual-core machine running FC6-64. I've had this
problem with both FC6 and windows as an unmodified guest OS.
________________________________
From: fedora-xen-bounces(a)redhat.com
[mailto:fedora-xen-bounces@redhat.com] On Behalf Of Filipe Miranda
Sent: Thursday, November 30, 2006 12:52 PM
To: fedora xen
Subject: [Fedora-xen] Mouse out of sync on guest machines
Hello,
After installing FC6 and the virtualization pack, I managed to install a
FC6 as guest OS. No problem at all (just the fact that I had to set xm
mem-set 0 256, and them xm mem-max 0 256 for the the virtual manager to
let me create the guest machines *my machine has 512RAM)
Anyway, everything worked just fine, but I noticed the the my mouse
pointer is totally out of sync in either text mode or graphic mode.
Is anyone having the same issue? Or is it a bug? or a misconfiguration?
Regards,
--
---
Filipe T Miranda
16 years, 10 months
Error Xen
by Thiago Morais
Hello,
I'm trying start one guest OS, Fedora 5, on Xen 3 in Fedora Core 6, but
during the booting process I get this error:
VFS: Cannot open root device "sda1" 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)
My configuration file:
kernel = "/boot/vmlinuz-2.6.18-1.2849.fc6xen"
memory = 64
name = "vm1"
disk = [ 'phy:/dev/volgrp/vmdisk1,sda1,w','phy:/dev/volgrp/swdisk1,sda2,w' ]
root = "/dev/sda1 ro"
extra = "4"
What can I do?
Thanks!
Thiago
16 years, 10 months
