HP Proliant DL380 issue
by Alex Barger
I have bee using Xen for a few months now on different systems. Kernel
2.6.15 with xen-3.0.1-4 has been stable for me on a few test machines and a
Dell Power Edge server. Today I installed FC5+xen on one of our beefier
machines the Proliant G3 DL380, dual Xeon 3ghz with 2GB ram. I keep having
kernel crashes with the following error below... any tips or advice would be
greatly apretiated. I tried kernel 2.6.20xxx and had kernel crashes with
that version as well. This machine has been running fine on CentOS 4.3 for
severval months.
Installed versions:
xen-3.0.1-4
kernel-xenU-2.6.15-1.2054_FC5
kernel-xen0-2.6.15-1.2054_FC5
Thanks!
------------[ cut here ]------------
kernel BUG at mm/mmap.c:2050!
invalid opcode: 0000 [#1]
SMP
Modules linked in: bridge nls_utf8 ipv6 ppdev autofs4 hidp rfcomm l2cap
bluetooth sunrpc sr_mod sg ip_conntrack_netbios_ns ipt_REJECT xt_state
ip_conntrack nfnetlink xt_tcpudp iptable_filter ip_tables x_tables video
button battery ac lp parport_pc parport nvram usb_storage ehci_hcd uhci_hcd
tg3 hw_random e752x_edac edac_mc dm_snapshot dm_zero dm_mirror dm_mod ext3
jbd cciss sd_mod scsi_mod
CPU: 0
EIP: 0061:[<c014b790>] Not tainted VLI
EFLAGS: 00210202 (2.6.15-1.2054_FC5xen0 #1)
EIP is at exit_mmap+0xe0/0xee
eax: 00000000 ebx: c1eef260 ecx: f3ff3b80 edx: fbc16000
esi: 00000000 edi: f2146dc0 ebp: f2432430 esp: f2459e4c
ds: 007b es: 007b ss: 0069
Process xenstored (pid: 2414, threadinfo=f2458000 task=f2432430)
Stack: <0>0000006f c1eef260 f2146dc0 f2146dc0 f2146df8 c011a514 f2146dc0
f24328f8
f2146dc0 c011de70 f2146dc0 f2432430 f2432430 0000000b f2459eac
c011f579
0000000b 00000001 ffffffff ffffffff 00000001 f2458000 c0ef60c0
0000000b
Call Trace:
[<c011a514>] mmput+0x1e/0x93
[<c011de70>] exit_mm+0x112/0x118
[<c011f579>] do_exit+0x1a5/0x6f4
[<c011fb51>] sys_exit_group+0x0/0x11
[<c03c764c>] inflate_dynamic+0x20/0x53d
[<c0127813>] get_signal_to_deliver+0x467/0x490
[<c03c7a84>] inflate_dynamic+0x458/0x53d
[<c011323d>] do_page_fault+0x0/0x6a8
[<c01042c7>] do_notify_resume+0x8b/0x623
[<c0168e97>] do_ioctl+0x4f/0x5f
[<c0113384>] do_page_fault+0x147/0x6a8
[<c01137da>] do_page_fault+0x59d/0x6a8
[<c016914c>] sys_ioctl+0x48/0x64
[<c011323d>] do_page_fault+0x0/0x6a8
[<c0104bfb>] work_notifysig+0x13/0x18
Code: 47 00 00 c7 43 04 00 00 00 00 58 5a 57 e8 6a 73 fb ff 58 eb 09 89 f0
e8 e1 fe ff ff 89 c6 85 f6 75 f3 83 bf 98 00 00 00 00 74 08 <0f> 0b 02 08 40
05 31 c0 5b 5e 5b 5e 5f c3 55 57 56 53 83 ec 0c
<1>Fixing recursive fault but reboot is needed!
--
**Alex Barger*
*WebXtreme, Inc
16 years, 11 months
Installing RHEL5 Paravirt on top of RHEL 5 hangs!
by Samuel Abreu de Paula
Hi, i dont know i here is the right place to ask, but im doing some
tests on RHEL 5 and didn´t find any other place to ask!
Im trying to install RHEL 5 as guest OS on a VM using virt-manager on
a RHEL 5...
I install xen packages, virt-manager, put 2GB ram for the main domain
and im trying to create a VM.
I get all RPMS from 5 cdroms of RHEL 5, put in a directory, copy the
images directory of CD 1 too, run createrepo in that directory using
the /Server/repodata/comps-rhel5-server-core.xml from CD 1.
put that directory on a place where i can reach by apache.
Start virt-manager, create new, using a file as a disk to vm and start
the installation, first hangs right after set root password, i find in
some release note that RHEL 5 need more than 1 GB ram to installation.
I try again, put 2GB (the server have 8GB ram) and he reach the next
step, selecting the packages! I let the default option and hit next.
Than take about 1:30 hours to complete the dependency check on files
selected to install, and then hangs!
The problem is im totally stuck, i look all files on system, all
commands i could use on xen to get some information and nothing.
Anyone have any idea what can i do to fix it, or to get more
information about what is the problem?
Thanks.
16 years, 11 months
TCP checksum corruption
by Mike McGrath
We're using xen heavily in Fedora's Infrastructure and presently a
number of the xen domU hosts are experiencing terrible checksum issues.
I've tried the ethtool -K eth0 tx off fix and it didn't work.
dom0: 2.6.19-1.2911.fc6xen x86_64
domU: 2.6.20-1.2933.fc6xen x86_64
Anyone have any ideas?
-Mike
16 years, 11 months
Copying Disk with Xen Partitions (dom0 and domU) to new Disk (machine swap)
by Christian Reiter
Hello!
I have to migrate my Xen Setup from an old machine to a new one.
The old has one 80GB SATA Disk, the new has one 250 GB SATA Disk.
This is my partition Table:
=================Partition Table=================
[root@m1 ~]# fdisk -l /dev/sda
Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 1318 10482412+ 8e Linux LVM
/dev/sda3 1319 9729 67561357+ 5 Extended
/dev/sda5 1319 5234 31455238+ 83 Linux
/dev/sda6 5235 6480 10008463+ 83 Linux
============================================
sda1 and sda2 is dom0
sda5 is the virtual disk for the first domU
sda6 is the virtual disk for the second domU
sda5 and sda6 have their own partion maps as created by virt-manager:
=================Partition Table=================
[root@m1 ~]# fdisk -l /dev/sda5
Disk /dev/sda5: 32.2 GB, 32210164224 bytes
255 heads, 63 sectors/track, 3915 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda5p1 * 1 13 104391 83 Linux
/dev/sda5p2 14 3915 31342815 8e Linux LVM
============================================
What is the easiest way to copy the whole disk (the dom0 and all domUs)
to my
new disk?
I think a simple "dd if=/dev/olddisk of=/dev/newdisk" won't do the job?
Mit freundlichen Grüßen, /// Kind Regards,
Christian Reiter
--
Christian Reiter ||| c.reiter(a)gmx.net
16 years, 11 months
DomU from physical disk FC6-2911
by marc+fcxen＠milestonerdl.com
I'm trying to get xen working on FC6 using
vmlinuz-2.6.19-1.2911.6.5.fc6xen as other newer images result in the machine locking up.
I have 3 disks in the system - two IDE drives (master/slave - hda/hdb) and one SATA (sdb)
All 3 drives have a bootable FC6 setup. One is to be the Dom0 and the other (hdb and sdb) are to be the 2 DomU's. Thus the virt-manager and associated scripts are not helpful. Most of the docs use the .img files.
The system seems to have allocated /dev/sda for Xen. (Am I making the proper guess here?)
Results from xm create -n apps
Using config file "/etc/xen/apps".
(vm
(name apps)
(memory 1024)
(vcpus 1)
(image (linux (kernel /boot/vmlinuz-2.6.19-1.2911.6.5.fc6xen) (args 4)))
(device (vbd (uname phy:vg/AppsVG) (dev sda1) (mode w)))
(device (vif (ip 192.168.1.8) (mac 00:16:3e:00:00:08) (bridge xenbr0)))
)
The text of /etc/xen/apps
kernel = "/boot/vmlinuz-2.6.19-1.2911.6.5.fc6xen"
memory = 1024
name = "apps"
vif = [ 'ip=192.168.1.8,mac=00:16:3e:00:00:08,bridge=xenbr0' ]
disk = [ 'phy:vg/AppsVG,sda1,w' ]
extra = "4"
The Error I get after some time is
Error: Device 2049 (vbd) could not be connected.
Email lists talk about how Device 2049 (vdb) errors are corrected with a modprobe loop command - but FC6 has netloop so I'm guessing I have some other config problem(s).
So....what am I doing wrong with my configs?
16 years, 11 months
pause installation, when selecting the compilation of the partition.
by 植松健
I want to done the construction of the mechanism of automatic
operation installation of XenU environment.
The command of virt-install is executed as description below
virt-install -r 256 -n system4 -f /var/lib/xen/images/system4 -s 4 -l
http://192.168.1.10/cdrom -x "text
ks=http://192.168.1.10/cdrom/ks.cfg" --nographics
And,Description of portion of the ks.cfg file is as description below.
clearpart --linux --drives=xvda
part /boot --fstype ext3 --size=100 --ondisk=xvda
part pv.2 --size=0 --grow --ondisk=xvda
volgroup VolGroup00 --pesize=32768 pv.2
logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow
logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=272 --grow
It paused installation, when selecting the compilation of the partition.
Something probably is problem?
16 years, 11 months
kernel OoPs after updating to 2.6.20-1.2933.fc6xen
by Asrai khn
Hi,
Today after updating kernel-xen to 2.6.20-1.2933.fc6xen on one of our host I
got kernel oops and machine rebooted, when it come back again i have no
other choice but to edit grub.conf and make the last working kernel '
2.6.19-1.2911.6.5.fc6xen' the default one which working fine.
DemU(s) working fine with with same kernel 2.6.20-1.2933.fc6xen, we use
loopback mounted fs for domU(s)
Here are the messages i found on screen before machine got rebooted (Note:
machine is remote to me thousands of miles away therefore i can't check its
boot screen :-S )
Now I am reluctant to update kernel-xen on our other remote hosts, never
got into such issue on FC6 while updated kernel-xen. In help/suggestion will
be greatly appreciated.
------
[root@xxxxx ~]#
Message from syslogd@xxxxx at Mon Mar 26 20:17:02 2007 ...
xxxxx kernel: Oops: 0003 [#1]
Message from syslogd@xxxxx at Mon Mar 26 20:17:02 2007 ...
xxxxx kernel: SMP
Message from syslogd@xxxxx at Mon Mar 26 20:17:02 2007 ...
xxxxx kernel: CPU: 0
Message from syslogd@xxxxx at Mon Mar 26 20:17:02 2007 ...
xxxxx kernel: EIP: 0061:[<c0548ceb>] Not tainted VLI
Message from syslogd@xxxxx at Mon Mar 26 20:17:02 2007 ...
xxxxx kernel: EFLAGS: 00010017 (2.6.20-1.2933.fc6xen #1)
Message from syslogd@xxxxx at Mon Mar 26 20:17:02 2007 ...
xxxxx kernel: EIP is at evtchn_do_upcall+0x55/0x97
Message from syslogd@xxxxx at Mon Mar 26 20:17:02 2007 ...
xxxxx kernel: eax: 00000010 ebx: 00000000 ecx: eaa35fe4 edx: ffffffec
Message from syslogd@xxxxx at Mon Mar 26 20:17:02 2007 ...
xxxxx kernel: esi: 00000001 edi: f5416000 ebp: fffffffe esp: eaa35fc4
Message from syslogd@xxxxx at Mon Mar 26 20:17:02 2007 ...
xxxxx kernel: ds: 007b es: 007b ss: 0069
Message from syslogd@xxxxx at Mon Mar 26 20:17:02 2007 ...
xxxxx kernel: Process find (pid: 4000, ti=eaa35000 task=ed7b12f0
task.ti=eaa35000)
Message from syslogd@xxxxx at Mon Mar 26 20:17:03 2007 ...
xxxxx kernel: Stack: 00000000 00000000 00000003 eaa35fac eaa35fe4 eaa35000
c0404ff2 eaa35fe4
Message from syslogd@xxxxx at Mon Mar 26 20:17:03 2007 ...
xxxxx kernel: b7ff0402 00000073 00000212 bf93c920 0000007b 00000000
00000000
Message from syslogd@xxxxx at Mon Mar 26 20:17:03 2007 ...
xxxxx kernel: Call Trace:
Message from syslogd@xxxxx at Mon Mar 26 20:17:03 2007 ...
xxxxx kernel: =======================
Message from syslogd@xxxxx at Mon Mar 26 20:17:03 2007 ...
xxxxx kernel: [<c0404ff2>] hypervisor_callback+0x46/0x50
Message from syslogd@xxxxx at Mon Mar 26 20:17:03 2007 ...
xxxxx kernel: Code: bd fe ff ff ff 88 d9 89 d8 c1 e0 05 d3 c5 89 04 24 eb 29
0f bc c0 03 04 24 8b 14 85 80 f0 6f c0 83 fa ff 74 12 8b 4c 24 1c f7 d2 <89>
51 28 89 c8 e8 16 db eb ff eb 05 e8 22 2e 00 00 8b 44 24 04
Message from syslogd@xxxxx at Mon Mar 26 20:17:03 2007 ...
xxxxx kernel: EIP: [<c0548ceb>] evtchn_do_upcall+0x55/0x97 SS:ESP
0069:eaa35fc4
Read from remote host xxxxx.xxxx.com: Connection reset by peer
Connection to xxxxx.xxxx.com closed.
16 years, 11 months
Xen 64 bit Kernel issue
by guru prasad
I am facing one issue in XEN 64 bit kernel.
Description: After installation of guest OS I am unable to start the guest.
Even "virsh#list --all" unable to list my inactive domains. I am using
2.6.18 kernel (64 Bit). I have used Fedora core 6 32 bit version. In that I
could install Solaris as a guest apart from all other Linux Distro.
Please suggest me the right solution.
16 years, 11 months
[ANNOUNCE] paravirt_ops i686 Fedora rawhide kernel packages
by chrisw＠sous-sol.org
If you are interested in trying the new paravirt_ops kernels, I've
created some packages and uploaded them to:
http://et.redhat.com/~chrisw/paravirt_ops/
There you'll find a yum repo (see yum.README for details) and an
INSTALL file for getting started. With this package you can use a
single kernel[1] for both native (w/out a hypervisor, or under a full
virt hypervisor), domU paravirt under Xen, and a VMI guest. There is no
support for dom0 kernels ATM. Running the kernel native is as simple as
installing and rebooting. However, it requires some manual intervention
to get a domU started (see INSTALL for details).
thanks,
-chris
[1] It's not quite a single kernel. It's two separate binaries built from
the identical vmlinux. This is due to the Xen domain builder's inability
to boot a bzImage format kernel binary. Fixing this is on the todo list.
16 years, 11 months
