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
17 years, 1 month
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) 永康
17 years, 3 months
RE: [Fedora-xen] Old serial mouse problem
by You, Yongkang
Just have a quickly check.
The default Xen0 kernel doesn't build in Serial Mouse.
Best Regards,
Yongkang (Kangkang) 永康
>-----Original Message-----
>From: fedora-xen-bounces(a)redhat.com
>[mailto:fedora-xen-bounces@redhat.com] On Behalf Of Philip Rhoades
>Sent: 2006年4月28日 9:07
>To: fedora-xen(a)redhat.com
>Subject: [Fedora-xen] Old serial mouse problem
>
>People,
>
>I have been using a Logitech Serial Mouseman for some years quite
>happily on various RHx and now FC5 but I have to manually fix:
>
>/etc/sysconfig/mouse:
>
>FULLNAME="Generic - 3 Button Mouse (serial)"
>MOUSETYPE="Microsoft"
>XEMU3="no"
>XMOUSETYPE="Microsoft"
>IMOUSETYPE="ms"
>DEVICE=/dev/ttyS0
>
>usually /etc/X11/x.org is OK with:
>
>Section "InputDevice"
> Identifier "Mouse0"
> Driver "mouse"
> Option "Protocol" "IMPS/2"
> Option "Device" "/dev/input/mice"
> Option "ZAxisMapping" "4 5"
> Option "Emulate3Buttons" "yes"
>EndSection
>
>but when I try and boot vmlinuz-2.6.16-1.2080_FC5xen0 I don't get a
>mouse . .
>
>How do I fix this? (short of upgrading to a PS2 mouse).
>
>Thanks,
>
>Phil.
>--
>Philip Rhoades
>
>Pricom Pty Limited (ACN 003 252 275 ABN 91 003 252 275)
>GPO Box 3411
>Sydney NSW 2001
>Australia
>Mobile: +61:(0)411-185-652
>Fax: +61:(0)2-8221-9599
>E-mail: phil(a)pricom.com.au
>
>
>--
>Fedora-xen mailing list
>Fedora-xen(a)redhat.com
>https://www.redhat.com/mailman/listinfo/fedora-xen
18 years
Old serial mouse problem
by Philip Rhoades
People,
I have been using a Logitech Serial Mouseman for some years quite
happily on various RHx and now FC5 but I have to manually fix:
/etc/sysconfig/mouse:
FULLNAME="Generic - 3 Button Mouse (serial)"
MOUSETYPE="Microsoft"
XEMU3="no"
XMOUSETYPE="Microsoft"
IMOUSETYPE="ms"
DEVICE=/dev/ttyS0
usually /etc/X11/x.org is OK with:
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "yes"
EndSection
but when I try and boot vmlinuz-2.6.16-1.2080_FC5xen0 I don't get a
mouse . .
How do I fix this? (short of upgrading to a PS2 mouse).
Thanks,
Phil.
--
Philip Rhoades
Pricom Pty Limited (ACN 003 252 275 ABN 91 003 252 275)
GPO Box 3411
Sydney NSW 2001
Australia
Mobile: +61:(0)411-185-652
Fax: +61:(0)2-8221-9599
E-mail: phil(a)pricom.com.au
18 years
How to expand the file created by xenguest-install?
by Denis Forveille
Does anyone has e detailed procedure to change the size (ie increase) of
the file that is used as the "xvda" disk by a domU? This is the file
created by the "xenguest-install" script (or the one created as in
section 6.2 of the xen user's manual for the file-backed VBDs scenario).
Thanks in advance
18 years
Xen Crash at Boot on Dell PE 830 Running FC 5
by Demetri Mouratis
[cross posted to xen-users(a)lists.xensource.com]
Greetings,
I'm having some trouble getting my new workstation, a Dell PE 830, up and
running Xen on Fedora Core 5. The last step I see in the boot process is
udev which completes with the standard [OK], then my monitor turns blank and
looses any signal from my machine. If necessary, I could connect a serial
port to get additional info on exactly where it is crashing.
I'm using this machine as my desktop so I'd like to run X in the dom0 if
possible. Please let me know if doing so is considered poor form with Xen.
I've gone through the install process on an older Dell workstation
successfully following the Fedora Xen Quickstart FC 5 guide here:
http://fedoraproject.org/wiki/FedoraXenQuickstartFC5
The only way I've been able to work around this issue is to edit my
/etc/inittab and set the default run level to 3 in which case the machine
comes up clean.
I've verified that selinux is disabled as I've seen some info to the effect
that selinux and the nvidia drivers may have some issue.
I'm hoping I can pass some argument at boot time to make this work or
otherwise tweak something in the bios to get the xen kernel to boot and
support X.
Thanks in advance for any hints or tips.
Here's the output of /proc/cpuinfo:
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 4
model name : Intel(R) Pentium(R) 4 CPU 2.80GHz
stepping : 9
cpu MHz : 2800.198
cache size : 1024 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm
constant_tsc pni monitor ds_cpl cid cx16 xtpr lahf_lm
bogomips : 5606.72
processor : 1
vendor_id : GenuineIntel
cpu family : 15
model : 4
model name : Intel(R) Pentium(R) 4 CPU 2.80GHz
stepping : 9
cpu MHz : 2800.198
cache size : 1024 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm
constant_tsc pni monitor ds_cpl cid cx16 xtpr lahf_lm
bogomips : 5600.31
And my grub.conf:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol01
# initrd /initrd-version.img
#boot=/dev/sda
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.16-1.2080_FC5xen0)
root (hd0,0)
kernel /xen.gz- 2.6.16-1.2080_FC5
module /vmlinuz-2.6.16-1.2080_FC5xen0 ro
root=/dev/VolGroup00/LogVol01 rhgb quiet
module /initrd-2.6.16-1.2080_FC5xen0.img
title Fedora Core (2.6.15-1.2054_FC5smp)
root (hd0,0)
kernel /vmlinuz-2.6.15-1.2054_FC5smp ro root=/dev/VolGroup00/LogVol01
rhgb quiet
initrd /initrd-2.6.15-1.2054_FC5smp.img
18 years
Multiple virtual to physical nic setup docs PLEASE!
by Alex.Upton＠instinet.com
Hello All,
I'm using FC5 with the following setup:
2.6.16-1.2080_FC5xen0
xen-3.0.1-4
I have a dual homed system, and would like all virtual eth0 nics to
utilize the real physical eth0 nic, and would like all virtual eth1 nics
to use the real physical eth1 nic.
as of now I have this:
in my /etc/xen/host1
vif = [ 'mac=0a:00:00:00:00:01',
'mac=0b:00:00:00:00:01']
in my /etc/xen/xend-config.sxp
(network-script 'network-bridge bridge=br0 netdev=eth0')
(network-script 'network-bridge bridge=br1 netdev=eth1')
brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no peth0
vif0.0
brctl addbr xenbr1
brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no peth0
vif0.0
xenbr1 8000.000000000000 no can't get port
info: Function not implemented
On the virtual host i ssh in through the virtual eth0 interface
successfully, then when i issue a tcpdump on the virtual eth1 i see real
traffic for the real physical eth1, however when assigning an address on
the virtual eth1, i can not access it from outside the virtual
environment.
Any direction to specific setup docs or any advice would be greatly
appreciated!
Thanks,
-Alex
*****************************************************************
<<<Disclaimer>>>
In compliance with applicable rules and regulations, Instinet
reviews and archives incoming and outgoing email communications,
copies of which may be produced at the request of regulators.
This message is intended only for the personal and confidential
use of the recipients named above. If the reader of this email
is not the intended recipient, you have received this email in
error and any review, dissemination, distribution or copying is
strictly prohibited. If you have received this email in error,
please notify the sender immediately by return email and
permanently delete the copy you received.
Instinet accepts no liability for any content contained in the
email, or any errors or omissions arising as a result of email
transmission. Any opinions contained in this email constitute
the sender's best judgment at this time and are subject to change
without notice. Instinet does not make recommendations of a
particular security and the information contained in this email
should not be considered as a recommendation, an offer or a
solicitation of an offer to buy and sell securities.
*****************************************************************
18 years
RE: [Fedora-xen] File operation causes kernel panic
by Alex.Upton＠instinet.com
I recently experienced the same issue and noticed that it was related to
my snmpd flipping out.
I'm not sure if its just a buggy version of snmpd that ships with FC5 or
if it's an overall issue with SNMPD and virtualized environments.
Disabling snmpd resolved it for me, however I'm hoping this issue is
resolved some day.
Hope this helps.
-Alex
-----Original Message-----
From: fedora-xen-bounces(a)redhat.com [mailto:fedora-xen-bounces@redhat.com]
On Behalf Of EJacobsh(a)connectknowledge.com
Sent: Wednesday, April 26, 2006 1:17 PM
To: fedora-xen(a)redhat.com
Subject: [Fedora-xen] File operation causes kernel panic
Hello,
I'm having a problem with a Dell server (PowerEdge 2850) and a recently
installed Fedora Core 5 with Xen kernel (2.6.16-1.2096_FC5xen0). Whenever
I try to copy a larger file (128MB) to the server over the network, the
server crashes (register dump on the console, remote sessions stop
responding).
This happens consistently with Anaconda, Samba and WinSCP3. It has
happened with yum twice, although it works most of the time.
When I reboot the server with a kernel that does not include Xen
(2.6.16-1.2096_FC5), the copying works.
I need some help figuring out what my next steps should be. I don't see
anything unusual in the xend.log (see below). The xend-debug.log is
empty. Is there some other place I should look? Are there any other
diagnostic tools to use?
Thanks for you help.
Eric Jacobshagen
CONNECT: The Knowledge Network
xend.log:
[xend] INFO (SrvDaemon:285) Xend Daemon started [xend] INFO
(SrvDaemon:289) Xend changeset: unavailable .
[xend.XendDomainInfo] DEBUG (XendDomainInfo:199)
XendDomainInfo.recreate({'paused': 0, 'cpu_time': 24271818792L, 'ssidref':
0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, , 0, 0, 0, 0, 0, 0],
'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 524288, 'maxmem_kb':
-4, 'max_vcpu_id': 1, 'crashed': 0, 'running': 1, 'shutdown': 0,
'online_vcpus': 2, 'blocked': 0})
[xend.XendDomainInfo] INFO (XendDomainInfo:211) Recreating domain 0, UUID
00000000-0000-0000-0000-000000000000.
[xend.XendDomainInfo] WARNING (XendDomainInfo:233) No vm path in store for
existing domain 0 [xend.XendDomainInfo] DEBUG (XendDomainInfo:667) Storing
VM details:
{'ssidref': '0', 'uuid': '00000000-0000-0000-0000-000000000000',
'on_reboot': 'restart', on_poweroff': 'destroy', 'name': 'Domain-0',
'vcpus': '2', 'vcpu_avail': '3', 'memory': '512', 'on_crash': 'restart',
'maxmem': '512'}
[xend.XendDomainInfo] DEBUG (XendDomainInfo:692) Storing domain details:
{'cpu/0/availability': 'online', 'memory/target': '524288',
'cpu/1/availability': 'online', 'name': 'Domain-0', 'console/limit':
'1048576', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid':'0'}
[xend] DEBUG (XendDomain:151) number of vcpus to use is 0 [xend] INFO
(SrvServer:114) unix path=/var/lib/xend/xend-socket
--
Fedora-xen mailing list
Fedora-xen(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen
*****************************************************************
<<<Disclaimer>>>
In compliance with applicable rules and regulations, Instinet
reviews and archives incoming and outgoing email communications,
copies of which may be produced at the request of regulators.
This message is intended only for the personal and confidential
use of the recipients named above. If the reader of this email
is not the intended recipient, you have received this email in
error and any review, dissemination, distribution or copying is
strictly prohibited. If you have received this email in error,
please notify the sender immediately by return email and
permanently delete the copy you received.
Instinet accepts no liability for any content contained in the
email, or any errors or omissions arising as a result of email
transmission. Any opinions contained in this email constitute
the sender's best judgment at this time and are subject to change
without notice. Instinet does not make recommendations of a
particular security and the information contained in this email
should not be considered as a recommendation, an offer or a
solicitation of an offer to buy and sell securities.
*****************************************************************
18 years
File operation causes kernel panic
by Eric Jacobshagen
Hello,
I'm having a problem with a Dell server (PowerEdge 2850) and a recently
installed Fedora Core 5 with Xen kernel (2.6.16-1.2096_FC5xen0). Whenever
I try to copy a larger file (128MB) to the server over the network, the
server crashes (register dump on the console, remote sessions stop
responding).
This happens consistently with Anaconda, Samba and WinSCP3. It has
happened with yum twice, although it works most of the time.
When I reboot the server with a kernel that does not include Xen
(2.6.16-1.2096_FC5), the copying works.
I need some help figuring out what my next steps should be. I don't see
anything unusual in the xend.log (see below). The xend-debug.log is
empty. Is there some other place I should look? Are there any other
diagnostic tools to use?
Thanks for you help.
Eric Jacobshagen
CONNECT: The Knowledge Network
xend.log:
[xend] INFO (SrvDaemon:285) Xend Daemon started
[xend] INFO (SrvDaemon:289) Xend changeset: unavailable .
[xend.XendDomainInfo] DEBUG (XendDomainInfo:199)
XendDomainInfo.recreate({'paused': 0, 'cpu_time': 24271818792L, 'ssidref':
0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, , 0, 0, 0, 0, 0, 0],
'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 524288, 'maxmem_kb':
-4, 'max_vcpu_id': 1, 'crashed': 0, 'running': 1, 'shutdown': 0,
'online_vcpus': 2, 'blocked': 0})
[xend.XendDomainInfo] INFO (XendDomainInfo:211) Recreating domain 0, UUID
00000000-0000-0000-0000-000000000000.
[xend.XendDomainInfo] WARNING (XendDomainInfo:233) No vm path in store for
existing domain 0
[xend.XendDomainInfo] DEBUG (XendDomainInfo:667) Storing VM details:
{'ssidref': '0', 'uuid': '00000000-0000-0000-0000-000000000000',
'on_reboot': 'restart', on_poweroff': 'destroy', 'name': 'Domain-0',
'vcpus': '2', 'vcpu_avail': '3', 'memory': '512', 'on_crash': 'restart',
'maxmem': '512'}
[xend.XendDomainInfo] DEBUG (XendDomainInfo:692) Storing domain details:
{'cpu/0/availability': 'online', 'memory/target': '524288',
'cpu/1/availability': 'online', 'name': 'Domain-0', 'console/limit':
'1048576', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid':'0'}
[xend] DEBUG (XendDomain:151) number of vcpus to use is 0
[xend] INFO (SrvServer:114) unix path=/var/lib/xend/xend-socket
18 years
RE: [Fedora-xen] PAE and FC5 Xen on 32-bit system
by You, Yongkang
You can achieve this by rebuild Xen source with PAE enabled. The command is: "make XEN_TARGET_X86_PAE=y"
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月24日 15:38
>To: fedora-xen(a)redhat.com
>Subject: [Fedora-xen] PAE and FC5 Xen on 32-bit system
>
>Hi,
>
>i have a 32-bit FC5 system running with default xen from FC5
>(kernel-xen0-2.6.16-1.2096_FC5 & xen-3.0.1-4).
>my system has 4GB of memory but xm info only shows 3584MB available.
>i know i need PAE support but the question is if there is a PAE enabled kernel
>from FC5 32-bit xen systems available already or if i can turn on PAE support
>easily somehow. for me it's important to stay 'supported' and use only 'officialy
>availbale' packages.
>
>if there is no such a PAE enabled version available can somebody explain
>what exactly needs to be done to turn PAE support on, i searched the web and
>found lots of different instructions but i am not sure which one is the 'correct'
>one ?
>
>thanks for any help !
>
>regards,
>Matthias
>
>
>______________________________________________________________
>_
>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
18 years
