Boot fails with 2.6.20-2925.5.fc7xen
by Langdon Stevenson
I have just completed a clean install of FC7 test 4 on a custom built
machine:
MB: Gigabyte GA-965P-DQ6
CPU: Intel Core 2 Duo E6600
Video: Asus EN7900GS
RAM: Veritech DDR2 800 1 Gig x 2
HD: Pair of Maxtor 120 Gig SATA drives running as a mirrored RAID array
through the hardware controller on the motherboard
The install ran fine, but when I boot the Fedora xen kernel
(2.6.20-2925.5.fc7xen) it crashes during the boot process.
If I boot "Fedora base (2.6.20-1.3104.fc7)", then it boots fine.
When booting the Fedora xen kernel the last output in the console is:
Kernel panic: Not syncing - Aiee, killing interupt handler!
I have seen a thread in this list talking about problems with the
2.6.20-2925.5.fc7xen kernel. Can anyone suggest what I may be able to
do to work around this problem? Is there a different xen kernel that I
could be using with FC7? If so, where would I get it from?
I am new to virtualisation and average with Linux, so would greatly
appreciate any assistance.
Regards,
Langdon
16 years, 11 months
domU crash whith auto-boot
by Frederic Saint-Marcel
Hello,
I have a Dell 2950 with :
kernel-xen.i686 2.6.18-1.2798.fc6
installed xen.i386
3.0.3-8.fc6 installed
xen-libs.i386 3.0.3-8.fc6 installed
When I restart domU with dom0 reboot or /etc/init.d/xendomains script I
have this error
in my xend.log :
[2007-05-14 14:20:07 xend.XendDomainInfo 7870] WARNING
(XendDomainInfo:882) Domain has crashed: name=xxxx id=21.
[2007-05-14 14:20:08 xend.XendDomainInfo 7870] ERROR
(XendDomainInfo:1675) VM xxxx restarting too fast (7.688173 seconds
since the last restart). Refusing to restart to avoid loops.
on eight domU I have only six which restart normally and two with this
error.
An idea ?
16 years, 11 months
Re: [Fedora-xen] Boot fails with 2.6.20-2925.5.fc7xen
by Daniel P. Berrange
On Thu, May 10, 2007 at 12:45:59PM +1000, Langdon Stevenson wrote:
> Hi Daniel
>
> Daniel P. Berrange wrote:
> >On Thu, May 10, 2007 at 11:57:07AM +1000, Langdon Stevenson wrote:
> >>I have just completed a clean install of FC7 test 4 on a custom built
> >>machine:
> >>
> >>MB: Gigabyte GA-965P-DQ6
> >>CPU: Intel Core 2 Duo E6600
> >>Video: Asus EN7900GS
> >>RAM: Veritech DDR2 800 1 Gig x 2
> >>HD: Pair of Maxtor 120 Gig SATA drives running as a mirrored RAID array
> >>through the hardware controller on the motherboard
> >>
> >>The install ran fine, but when I boot the Fedora xen kernel
> >>(2.6.20-2925.5.fc7xen) it crashes during the boot process.
> >>
> >>If I boot "Fedora base (2.6.20-1.3104.fc7)", then it boots fine.
> >>
> >>When booting the Fedora xen kernel the last output in the console is:
> >>
> >>Kernel panic: Not syncing - Aiee, killing interupt handler!
> >>
> >>
> >>I have seen a thread in this list talking about problems with the
> >>2.6.20-2925.5.fc7xen kernel. Can anyone suggest what I may be able to
> >>do to work around this problem? Is there a different xen kernel that I
> >>could be using with FC7? If so, where would I get it from?
> >
> >You don't mention what architecture you're installing ? i686 or x86_64 ?
> >We just built a new kernel into rawhide which 2.6.20-2925.7.fc7xen which
> >fixes a bunch of things, including checksum corruption in networking and
> >SMP support in 64-bit. This still has a major outstanding problem which
> >affects many 32-bit machines though - debugging is ongoing & trying to
> >get it resolved before F7 GA. So anyway, if you're using the 32-bit
> >kernel I imagine you've hit the known panic problems we're investigating.
>
> Sorry, should have mentioned, it is i686. So as you say I am hitting
> the known panic problems.
>
> Thanks for the explanation, I guess that I will put this aside until you
> get the new kernel running for F7 GA.
FYI, we think we've got the problem fixed & have a new build available.
If anyone is running rawhide with Xen and seeing crashes/hangs/wierd
behaviour, please give the 2.6.20-2925.8.fc7 kernel a try. Its not in
rawhide YUM repos yet, but you can it from Koji
http://koji.fedoraproject.org/packages/kernel-xen-2.6/2.6.20/2925.8.fc7/
NB. this requires xen-3.1.0-0.rc7.1.fc7 userspace.
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
16 years, 11 months
Fwd: [Fedora-xen] Boot fails with 2.6.20-2925.5.fc7xen
by Deependra Singh Shekhawat
Hi,
I can confirm it that it works on Fedora7. Just finished testing it.
Thanks alot!
On 5/11/07, Itamar Reis Peixoto < itamar(a)ispbrasil.com.br> wrote:
>
> I will make some test's in next 2 day's
>
> this kernel is using the next version of xen (3.1) ?
>
> thanks for the update
>
>
> --------------------
>
> Itamar Reis Peixoto
>
> e-mail: itamar(a)ispbrasil.com.br
> msn: itamarjp(a)starmedia.com
> skype: itamarjp
> icq: 81053601
> +55 34 3238 3845
> +55 11 4063 5033
> >> get the new kernel running for F7 GA.
> >
> > FYI, we think we've got the problem fixed & have a new build available.
> > If anyone is running rawhide with Xen and seeing crashes/hangs/wierd
> > behaviour, please give the 2.6.20-2925.8.fc7 kernel a try. Its not in
> > rawhide YUM repos yet, but you can it from Koji
> >
> > http://koji.fedoraproject.org/packages/kernel-xen-2.6/2.6.20/2925.8.fc7/
> >
> >
> > NB. this requires xen-3.1.0-0.rc7.1.fc7 userspace.
> >
> > Dan.
> > --
> > |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392
> > 2496 -=|
> > |=- Perl modules:
> > .cpan.org/~danberr/ -=|
> > |=- Projects:
> > at.net/~danielpb/ <http://at.net/%7Edanielpb/> -=|
> > |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B
> > 505 -=|
>
> --
> Fedora-xen mailing list
> Fedora-xen(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
--
Enjoy Life !
--
Enjoy Life !
16 years, 11 months
Re: [Fedora-xen] [patch] GUI for spacifying additional kernel parameters
by Alexander Todorov
Daniel P. Berrange wrote:
> On Wed, May 09, 2007 at 02:46:44PM +0200, Alexander Todorov wrote:
>> Hello list,
>> I needed to use additional kernel parameters when installing a Xen
>> guest. I was testing modifications of anaconda.
>
> Could you give an example of the kind of kernel parameters you are
> needing to provide.
In my case it was dogtail=<url>.
This is new option to allow passing url of dogtail testcase to anaconda.
I was testing the patch that will parse kernel parameters and provide
them as command line parameters to the installer.
See:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=239024
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172891
> Traditionally the most common need was for various
> hardware workarounds, which shouldn't be neccessary in paravirt case.
> So I'd be interested to know what you're using and thus figure out if
> there is a higher level UI we could provide to accomplish the same
> thing instead of kernel params.
Having a general purpose way to specify additional kernel params is a
good thing anyway. You can not predict if somebody will need it and for
what reason (different from already implemented).
>
>> This patch provides a page where the user can supply any parameters that
>> should be passed to the kernel. Write the parameters as you would do it
>> on the command line for a physical machine.
>> The new page is shown after settings for paravirtualized install.
>>
>> Changes are in vmm-create.glade and virtManager/create.py.
>
> If we do decide add such a UI it shouldn't be a separate page - simply
> another text box below the existing kickstart URL field.
>
I agree, I can correct it. This will minimize code changes as well.
Q: Will the next "hg bundle myfeature.hg" be enough for you as described
in the README?
>> Q: Why there is an option to pass additional kernel parameters only for
>> paravirtualized installs? Is this possible for fully virtualized installs?
>
> With Xen no - the way full virt works with Xen is that we run an actual
> BIOS. This BIOS boots off a CDROM so there's no way to provide any kernel
> parameters there. Of course the syslinux / grub screen that the BIOS
> launches would let you enter kernel parameters fairly easily.
>
> With QEMU/KVM, fullvirt can either boot off a CDROM, or directl from a
> kernel+initrd pair. In the latter case we'd be able to provide kenrel
> parameters in same way as Xen paravirt. We currently don't allow the
> use of kernel+initrd in the UI for QEMU/KVM though because it has bugs
> which cause it to hang.
>
Thanks for the answer.
Greetings,
Alexander.
> Regards,
> Dan.
16 years, 11 months
Re: [Fedora-xen] [patch] GUI for spacifying additional kernel parameters
by Alexander Todorov
Hello,
Here is a revised version:
removed new page, moved widgets to PVInstall page.
A little bit of code cleanup.
Daniel P. Berrange wrote:
> 'hg export' makes reviewing via email a little easier if its just simple
> patches. I should update the README really :-)
>
Thanks for this hint. I am mercurial newbie.
Will use it next time.
> Regards,
> Dan.
16 years, 11 months
Problem on kernel 2.6.20-1.29*
by wmmaz
Hi ,
I had a fresh box xen installed with kernel 2.6.20-1.29*.fc6xen but with this kernel guest startup will had problem and system message as below:
But it didn't had problem on kernel 2.6.18-1.2798.fc6xen
Thanks
kernel: CPU: 0
May 9 20:52:15 hkb2-xen3 kernel: EIP: 0061:[<c054936b>] Not tainted VLI
May 9 20:52:15 hkb2-xen3 kernel: EFLAGS: 00210013 (2.6.20-1.2948.fc6xen #1)
May 9 20:52:15 hkb2-xen3 kernel: EIP is at evtchn_do_upcall+0x55/0x97
May 9 20:52:15 hkb2-xen3 kernel: eax: 00000001 ebx: 00000000 ecx: d4de8fe4 edx: fffffeff
May 9 20:52:15 hkb2-xen3 kernel: esi: 00000001 edi: f5416000 ebp: fffffffe esp: d4de8fc4
May 9 20:52:15 hkb2-xen3 kernel: ds: 007b es: 007b ss: 0069
May 9 20:52:15 hkb2-xen3 kernel: Process qemu-dm (pid: 4797, ti=d4de8000 task=ecb21730 task.ti=d4de8000)
May 9 20:52:15 hkb2-xen3 kernel: Stack: 00000000 00000000 0000000e d4de8fac d4de8fe4 d4de8000 c0404ff2 d4de8fe4
May 9 20:52:15 hkb2-xen3 kernel: 00216402 00000073 00200246 bfd4f548 0000007b 00000000 00000000
May 9 20:52:15 hkb2-xen3 kernel: Call Trace:
May 9 20:52:15 hkb2-xen3 kernel: [<c0404ff2>] hypervisor_callback+0x46/0x50
May 9 20:52:15 hkb2-xen3 kernel: =======================
May 9 20:52:15 hkb2-xen3 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 40 d4 eb ff eb 05 e8 22 2e 00 00 8b 44 24 04
May 9 20:52:15 hkb2-xen3 kernel: EIP: [<c054936b>] evtchn_do_upcall+0x55/0x97 SS:ESP 0069:d4de8fc4
kernel: CPU: 1
Apr 25 15:31:53 localhost kernel: EIP: 0061:[<c04143ee>] Not tainted VLI
Apr 25 15:31:53 localhost kernel: EFLAGS: 00010286 (2.6.20-1.2944.fc6xen #1)
Apr 25 15:31:53 localhost kernel: EIP is at direct_remap_area_pte_fn+0x16/0x6c
Apr 25 15:31:53 localhost kernel: eax: 00000000 ebx: 00000000 ecx: ee640000 edx: c15af940
Apr 25 15:31:53 localhost kernel: esi: ed7ca200 edi: c15af940 ebp: ec2ece68 esp: ec2ecdc8
Apr 25 15:31:53 localhost kernel: ds: 007b es: 007b ss: 0069
Apr 25 15:31:53 localhost gdm[3615]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Apr 25 15:31:53 localhost kernel: Process Xorg (pid: 3616, ti=ec2ec000 task=ebf38e70 task.ti=ec2ec000)
Apr 25 15:31:53 localhost kernel: Stack: 00000000 00000000 c15af940 ee640000 c045381f ec2ece68 93bca067 00000000
Apr 25 15:31:53 localhost kernel: c06e3080 c0fd6018 ee680000 ee680000 ebf38e70 ed7ca200 c1000000 c0fdab98
Apr 25 15:31:53 localhost kernel: 06fda001 00000000 00000000 000204d0 93bca067 00000000 93bca067 00000000
Apr 25 15:31:53 localhost kernel: Call Trace:
Apr 25 15:31:53 localhost kernel: [<c045381f>] apply_to_page_range+0x3ed/0x45e
Apr 25 15:31:53 localhost kernel: [<c0413fdf>] __direct_remap_pfn_range+0x13b/0x17d
Apr 25 15:31:53 localhost kernel: [<c04143d8>] direct_remap_area_pte_fn+0x0/0x6c
Apr 25 15:31:53 localhost kernel: [<c04141cb>] __ioremap+0x1aa/0x1cc
Apr 25 15:31:53 localhost kernel: [<ee5cd222>] drm_addmap_core+0x1a4/0x3fd [drm]
Apr 25 15:31:53 localhost kernel: [<c041766e>] __might_sleep+0x21/0xc1
Apr 25 15:31:53 localhost kernel: [<ee5cd4ee>] drm_addmap_ioctl+0x73/0xb1 [drm]
Apr 25 15:31:53 localhost kernel: [<c0613625>] do_page_fault+0x767/0xc2e
Apr 25 15:31:53 localhost kernel: [<ee5cd47b>] drm_addmap_ioctl+0x0/0xb1 [drm]
Apr 25 15:31:53 localhost kernel: [<ee5cffda>] drm_ioctl+0x150/0x196 [drm]
Apr 25 15:31:53 localhost kernel: [<c041766e>] __might_sleep+0x21/0xc1
Apr 25 15:31:53 localhost kernel: [<c047075c>] do_ioctl+0x4c/0x62
Apr 25 15:31:53 localhost kernel: [<c04709b6>] vfs_ioctl+0x244/0x256
Apr 25 15:31:53 localhost kernel: [<c0470a14>] sys_ioctl+0x4c/0x64
Apr 25 15:31:53 localhost kernel: [<c0404e3c>] syscall_call+0x7/0xb
Apr 25 15:31:53 localhost kernel: =======================
Apr 25 15:31:53 localhost kernel: Code: 5b 5b 5e 5f 5d e9 d7 fa ff ff 5a b8 ea ff ff ff 5b 5e 5f 5d c3 55 57 56 89 c6 53 8b 6c 24 14 83 3e 00 8b 40 04 75 04 85 c0 74 04 <0f> 0b eb fe 2b 15 84 f6 7d c0 8b 7d 00 c1 fa 05 80 3d a2 e5 72
Apr 25 15:31:53 localhost kernel: EIP: [<c04143ee>] direct_remap_area_pte_fn+0x16/0x6c SS:ESP 0069:ec2ecdc8
Apr 25 15:31:53 localhost kernel: <0>------------[ cut here ]------------
Apr 25 15:31:53 localhost kernel: kernel BUG at arch/i386/mm/hypervisor.c:197!
Apr 25 15:31:53 localhost kernel: invalid opcode: 0000 [#2]
Apr 25 15:31:53 localhost kernel: SMP
16 years, 11 months
Xen Guest Installation question
by Willemann, Phil
Hello Everyone:
I'm new to Xen and have some Linux experience. I have installed Fedora
Core 6 on a Intel 3.2 GHZ machine. (Note: I have 1 machine to test
with.) I have 6GB of RAM. My ultimate goal is to install a few
versions of Fedora Core 3 on the box. (I have an old application that
uses FC3) I can start up the virt-install GUI with no problems. My
questions revolve around the location of FC3.
1. I know it can't be installed from a FC3 Install CD. <-- I don't
understand why this is not supported. It would seem to be the easiest
thing to do.
2. I know I can use NFS or HTTP.
3. I have Apache Web Server running and NFS is enabled.
Here are the questions
1. If I want to use http or NFS, do I copy the entire FC3 Install CD to
some place on the hard drive? Is the copy a *.iso file or is it the
individual files from the CD? This has never been clear for
me. I have seen conflicting information on the net about this
2. If I use http where do I put the files. (under /var/www/...??)
3. I made a directory called /tmptest and copied the iso image to it.
I edited the /etc/exports file and added a line like this
/tmptest 192.168.107.14(rw,sync) <-- I assumed this means
192.168.107.14 has rw write access to /tmptest. This seems to make
sense but the installation seems to always say invalid NFS source.
Any help would be greatly appreciated.
Thanks
Phil Willemann
16 years, 11 months
VM freezes
by Brian Lavender
I am using Fedora Core 6. My VM freezes and on the console I see the
message
blk_tap: Can't get UE info!
My system has 4 Gigs of ram. My VM is a file backed vm using a non
sparse file. I used the following virt install to install it.
virt-install --nonsparse -l http://192.168.1.114/fc6/ -f
/var/lib/xen/images/ossim.img -s 5 --nographics -n ossim -r 512
Any ideas what is causing this blocking?
brian
--
Brian Lavender
http://www.brie.com/brian/
16 years, 11 months
What do I do after guest install?
by fedora-xen＠jks.tupari.net
I successfully ran the CentOS 5 installer. I got the point where it said
"remove install media and reboot machine" and then the guest disappeared.
How do I start up my new guest?
16 years, 11 months
