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, 9 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, 11 months
Heads-up: Requiring PAE for running Xen
by Jeremy Katz
As we move forward with Xen enablement, there's a desire for
being able to access more than 4 gigs of RAM on 32-bit Xen hosts. The
options for handling this are
1) Another kernel. This is bad due to
a) we're running out of CD space already
b) keeping things matched up between the HV and the guest kernels
c) migration is worlds of pain with two types of kernels
2) Switch the 32-bit xen kernels to require PAE. For most "current"
non-laptop hardware, this is a non-issue. It does mean that xen won't
work a lot of earlier PentiumM laptops
3) Do nothing, tell people to use 64bit if they want more than 4 gigs of
RAM
4) Make the PAE code handled at runtime. This is a pretty non-trivial
amount of work :)
Given these, we're looking at going with #2 and thus only having Xen
work on PAE-capable hardware in the development tree. And we're
planning to try to execute this switchover the beginning of next week.
Note that this will not affect bare metal installs at all.
Jeremy
17 years, 4 months
Problem starting a full virtualized Windows Guest
by Sven Oehme
Hi ,
i am running xen 3.0.2 on FC5 and try to setup a full virtualized Windows
Guest .
the installation Program starts , but as soon as it shows the text Windows
is starting in the left bottom, nothing more happens .
i am attaching all needed information's :
and a pic of the screen :
any ideas ??
i tried with the newest version today :
kernel-xen0-2.6.16-1.2202_FC6
kernel-xen0-devel-2.6.16-1.2200_FC6
xen-3.0.2-4
when i start the guest , the system freezes and just reboots .
Sven
17 years, 6 months
RE: [Fedora-xen] FW: [IA64]We have successfully booted dom0/domU/domVTI (xen/ia64) on FC5
by Zhang, Xiantao
>> After some hard debug and work around, now we've got xen/ia64
> dom0/domU/domVTI both up on FC5-IA64. Attached is the snapshot.
> Woohoo! :-)
>> We still use python2.4.2 contained in FC5 for test.
>> We need following changes to make things happen:
>> - xen-tools is not built and integrated into the RPM package.
>> Typically we know there're 3 major directories on
>> xen-ia64-unstable.hg: xen,linux-sparse and tools. All three
>> need to be kept consistence with each other. However current
>> fedora-kernel-ia64 only incorporates former two and tools is
>> totally missed. We tried to build the tools individually from
>> xen-ia64-unstable under same Rev (10150), and then install to
>> target box manually.
> You need to install the xen rpm which is available from my yum
> repository. See here for instructions:
> https://www.redhat.com/archives/fedora-xen/2006-May/msg00140.html
OK, we will do a try.
>> - The configuration files for dom0/domU seems a big difference
>> compared to xen-ia64-unstable.hg. (Why?) Currently the ext3 is
>> compiled as module, however initrd doesn't work for domU even
>> when we add "ramdisk=" in config file. So we change ext3 to be
>> kernel built-in, and then domU can boot up immediately.
>
> Ok, I'll fix that in the rpm.
OK.
>> - Xen-ia64-unstable.hg doesn't have IDE devices configured for
>> domU, however fedora-kernel-ia64 does, which wastes much time
>> for probe. If the configuration file can be kept consistence
>> with xen-ia64-unstable.hg, above issues are gone.
> That's my mistake too. I'll fix it.
OK too:)
>> After above 2 changes, both domU and domVTI can be boot
successfully.
>>
>> Following are other tricky issues we've observed:
>> - brctl package is not integrated into FC5 and so vnif is not
>> available now. People need to install brctl manually and we'll
>> try network later. Is it possible to add dependency check upon
>> brctl in spec file?
>
> The dependency is in the xen rpm...
Clear now.
>> - When installing xen0 rpm package, it depends on xen rpm
>> package. However we didn't find the xen rpm package, and had
>> to install with "nodeps". Actually xen image has been included
>> in xen0 rpm package.
> This is a confusing misnomer in Fedora. The xen rpm contains the xen
> tools, not the xen hypervisor. Does this make things clearer?
See now. Different viewpoint to it:)
>> - Is it possible to use same configuration file for xen0/xenU
>> just like current xen-ia64-unstable.hg? Or at least give
>> a configuration option to user in spec.
> Right now the build follows the pattern of the other architectures in
> the spec file. If Juan is interested in pursuing a -xen kernel
> instead of -xen0/-xenU, I'd be happy to go that route.
Good news! If done, it will largely save build time.
Thanks
Xiantao
17 years, 6 months
XENBUS timeout
by Rainer Fuegenstein
Hi,
I guess since I upgraded to kernel 2.6.16-1.2122_FC5xen0, a booting DomU
reports a timeout:
[...]
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
[system hangs for about 3 seconds, but continues ]
XENBUS: Timeout connecting to devices!
md: Autodetecting RAID arrays.
md: autorun ...
[...]
Is this something I should be worried about ? everything seems to work
as usual in DomU.
hardware is a Dual Xeon 2.4 GHz machine with 1 GB memory. DomU config is:
kernel = "/boot/vmlinuz-2.6.16-1.2122_FC5xenU"
memory = 128
name = "test"
vif = [ '' ]
disk = ['phy:/dev/vg_virtual/lv_test_root,sda1,w',
'phy:/dev/vg_virtual/lv_test_swap,sda2,w',
'phy:/dev/vg_virtual/lv_test_var,sda3,w',
'phy:/dev/vg_virtual/lv_test_web,sda4,w']
root = "/dev/sda1 ro"
OS is the Fedora Core 5 image from jailtime.org
just in case, dmesg output from DomU:
Linux version 2.6.16-1.2122_FC5xenU
(bhcompile(a)hs20-bc1-3.build.redhat.com) (gcc
version 4.1.0 20060304 (Red Hat 4.1.0-3)) #1 SMP Sun May 21 15:52:00
EDT 2006
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000008000000 (usable)
0MB HIGHMEM available.
136MB LOWMEM available.
Using x86 segment limits to approximate NX protection
On node 0 totalpages: 34816
DMA zone: 34816 pages, LIFO batch:7
DMA32 zone: 0 pages, LIFO batch:0
Normal zone: 0 pages, LIFO batch:0
HighMem zone: 0 pages, LIFO batch:0
IRQ lockup detection disabled
Built 1 zonelists
Kernel command line: root=/dev/sda1 ro
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 16384 bytes)
Xen reported: 2399.318 MHz processor.
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Software IO TLB disabled
vmalloc area: c9000000-fb3fe000, maxmem 33ffe000
Memory: 125508k/139264k available (1655k kernel code, 5400k reserved,
618k data,
132k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 6003.27 BogoMIPS
(lpj=12006559)
Security Framework v1.0.0 initialized
SELinux: Initializing.
SELinux: Starting in permissive mode
selinux_register_security: Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 512
CPU: After generic identify, caps: bfebc3f1 00000000 00000000 00000000
00004400
00000000 00000000
CPU: After vendor identify, caps: bfebc3f1 00000000 00000000 00000000
00004400 0
0000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: After all inits, caps: bfebc3f1 00000000 00000000 00000080 00004400
0000000
0 00000000
Checking 'hlt' instruction... OK.
Brought up 1 CPUs
0
Grant table initialized
NET: Registered protocol family 16
Brought up 1 CPUs
xen_mem: Initialising balloon driver.
audit: initializing netlink socket (disabled)
audit(1149106044.358:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
SELinux: Registering netfilter hooks
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key 43645308A4C9E5AD
- User ID: Red Hat, Inc. (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
rtc: IRQ 8 is not free.
i8042.c: No controller found.
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
Probing IDE interface ide0...
Registering block device major 8
Probing IDE interface ide1...
Probing IDE interface ide2...
Probing IDE interface ide3...
Probing IDE interface ide4...
Probing IDE interface ide5...
ide-floppy driver 0.99.newide
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 5, 163840 bytes)
TCP bind hash table entries: 8192 (order: 5, 163840 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
XENBUS: Timeout connecting to devices!
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 132k freed
SELinux: Disabled at runtime.
SELinux: Unregistering netfilter hooks
Non-volatile memory driver v1.2
EXT3 FS on sda1, internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 524280k swap on /dev/sda2. Priority:-1 extents:1 across:524280k
netfront: Initialising virtual ethernet driver.
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 132k freed
SELinux: Disabled at runtime.
SELinux: Unregistering netfilter hooks
Non-volatile memory driver v1.2
EXT3 FS on sda1, internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 524280k swap on /dev/sda2. Priority:-1 extents:1 across:524280k
netfront: Initialising virtual ethernet driver.
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
eth0: no IPv6 routers present
17 years, 6 months
Xen VM boot garbage (cursor jump to top of console)
by Jos Vos
Hi,
Is there a way to prevent the cursor jump to the top of the screen
after the Xen VM boot "(XEN) ..." messages, after which the Linux
domain 0 boot messages (starting with "Red Hat nash ...") are
overlaying the Xen boot messages and thus create garbled output?
Earlier, the Xen boot messages were just followed by the Linux
boot messages.
Thanks,
--
-- Jos Vos <jos(a)xos.nl>
-- X/OS Experts in Open Systems BV | Phone: +31 20 6938364
-- Amsterdam, The Netherlands | Fax: +31 20 6948204
17 years, 6 months
device names in DomU
by Rainer Fuegenstein
Hi,
I like to use harddisk device names other than hdx/sdx in DomU (because
I'm about to migrate a legacy system (which uses /dev/mdX devices) into
a xen DomU and I like to make sure that one day I won't mistake DomU's
/dev/hda1 with /dev/hda1 in Dom0 when running a mkfs ...)
if I specify
disk = ['file:/virtual/guest-root.img,sda1,w']
in DomU's cfg file, it works. but if I specify
disk = ['file:/virtual/guest-root.img,vxd1,w']
(or something like "md1") then xm create reports "Error: int argument
required".
any ideas ?
17 years, 6 months
kernel 2.6.16-1.2111_FC5xen0 breaks xen ?!
by Matthias Bayer
Hi everybody,
i just installed the new kernel 2.6.16-1.2111_FC5xen0 via yum update.
now xen seems to be broken !
everything woked with 2.6.16-1.2107_FC5xen before but now if i try 'xm list' i get 'Error: Error connecting to xend: Connection refused. Is xend running?'
this is the same for x86 and x86_64 system.
also xen debug output on serial console shows XEN3.0.0 instead of XEN3.0.2-2 as before the upgrade !
looks like some old stuff was integrated suddenly - can anybody confirm this ? if yes i will enter a bugzilla immediately !
regards,
Matthias
_________________________________________________________________________
Mit der Gruppen-SMS von WEB.DE FreeMail können Sie eine SMS an alle
Freunde gleichzeitig schicken: http://freemail.web.de/features/?mc=021179
17 years, 6 months
