Cannot execute a PAE-enabled kernel on a PAE-less CPU
by Filipe Miranda
Hello,
I have a Thinkpad T41 notebook and I recently installed FC6. One of the cool
features of FC6 is the virtualization through Xen, but the xen-kernel that
comes with FC6 ( 2.6.18-1.2849) causes kernel panic.
Here is the exact message:
KERNEL PANIC: Cannot execute a PAE-enabled kernel on a PAE-less CPU!
I already tried to use the swiotlb=force parameter during system boots
(Grub) but no success.
Someone on the xen channel of the Freenode told me that I would need a FC6
xen-non-PAE-kernel but I searched o the FC6 repositories and did not find
it.
Any suggestions besides compiling it from source?
Regards,
---
Filipe T Miranda
17 years, 5 months
xenguest-install & vncviewer
by George Hill
It would be nice if the vncserver that xenguest-install starts ran vncviewer (perhaps with the --nowin option so the little window does not get in the way). That way it would be easy to copy error messages, which can get quite lengthy, to a file and include them in bug reports. Or perhaps someone knows another way of copying these messages?
17 years, 5 months
X startup failure with Xen kernel
by Adam Huffman
On a system upgraded from FC5 to FC6, I find that the whole system hangs
at X startup if I boot with the Xen kernel. Even Alt-SysRq has no
effect.
X starts without any problems on a non-Xen kernel.
It's a Dell OptiPlex GX270.
lspci output:
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM
Controller/Host-Hub Interface (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated
Graphics Controller (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB
UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB
UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB
UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB
UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2
EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC
Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE
Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller
(rev 02)
00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus
Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER
(ICH5/ICH5R) AC'97 Audio Controller (rev 02)
01:0c.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet
Controller (rev 02)
I see a few other people have vaguely similar problems. Any ideas?
Adam
17 years, 5 months
RE: [Fedora-xen] scp in FC6 + Xen gets stuck in "stalled" stage
by Ranganathan, Shobha
Yes . That did it. I am able to copy files using scp.
Why does an MTU issue come up in this scenario ?
Thanks
Shobha
-----Original Message-----
From: Paul Wouters [mailto:paul@xelerance.com]
Sent: Wednesday, November 15, 2006 1:25 PM
To: Ranganathan, Shobha
Cc: fedora-xen(a)redhat.com
Subject: Re: [Fedora-xen] scp in FC6 + Xen gets stuck in "stalled" stage
On Wed, 15 Nov 2006, Ranganathan, Shobha wrote:
> I am trying to get scp to work. It gets stuck displaying "stalled"
> message.
> This happens in the Xen that I built with xen-3.0.3-rc3 which builds
it
> with 2.6.16.29 kernel in Fedora Core 6.
> I boot into Fedora provided FC6 Xen host and tried scp and it works.
Looks more like an MTU isuse. Try using clamping:
iptables -I FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS
--clamp-mss-to-pmtu
Otherwise, try pinging with different size packets until it fails, and
then use
the last successful packet size (eg 1440) to:
iptables -I FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --set-mss
1440
Paul
17 years, 5 months
scp in FC6 + Xen gets stuck in "stalled" stage
by Ranganathan, Shobha
I am trying to get scp to work. It gets stuck displaying "stalled"
message.
I did "iptables stop". But does not help.
This happens in the Xen that I built with xen-3.0.3-rc3 which builds it
with 2.6.16.29 kernel in Fedora Core 6.
I boot into Fedora provided FC6 Xen host and tried scp and it works.
What settings did I miss in configuration ?
Regards
Shobha Ranganathan
"The significant challenges we face cannot be resolved at the same level
of thinking we were at when we created them." Albert Einstein
17 years, 5 months
I got it work ---- virt-manager gives "The console is currentlyunavailable" in FC6
by Ranganathan, Shobha
Thanks Dan for all the debug .
and Thanks Robert for sharing and providing the tip.
I did cleanup the host file and some more clean up in rc.d directories.
I did get the unmodified guest up in running.
It has always been helpful to ask Qs in this mailing list...
Regards
Shobha Ranganathan
"The significant challenges we face cannot be resolved at the same level
of thinking we were at when we created them." Albert Einstein
-----Original Message-----
From: Daniel P. Berrange [mailto:berrange@redhat.com]
Sent: Tuesday, November 14, 2006 5:51 PM
To: Ranganathan, Shobha
Cc: Robert Thiem; fedora-xen(a)redhat.com
Subject: Re: [Fedora-xen] virt-manager gives "The console is
currentlyunavailable" in FC6
On Tue, Nov 14, 2006 at 05:45:17PM -0800, Ranganathan, Shobha wrote:
> Anyway I'd suggest:
> - Check that you can ping localhost
> I could ping the localhost
>
> - Check there's a localhost entry in /etc/hosts associated with
> 127.0.0.1
> (and not with ::1)
> I have two entries one with 127.0.0.1 and ::1. I went ahead and
> commented out ::1 entry
> - Run "netstat -antp" to see what ports programs are listening on
> I see various services on IP address of the local host 172.xx.xx.xx
and
> 127.0.0.1 and ::22 and ::1 and 0.0.0.0
>
> I see sshd, cupsd and hpiod running with local address as ::22, ::1
and
> 0.0.0.0.
For fully-virt / HVM guests you should see a 'qemu-dm' process
listening
on the port associated with VNC (something around 5900+). If you don't
then this is the primary problem to address - the qemu-dm*log file may
be useful. Also grabbing the command line for qemu-dm active process
should indicate what port it tried to start on. In my case:
# virsh dumpxml rhel4i386 | grep graphics
<graphics type='vnc' port='5900'/>
# ps -axuww | grep qemu
root 4005 0.0 0.1 64616 5132 ? Sl 20:05 0:00
/usr/lib64/xen/bin/qemu-dm -d 2 -m 500 -boot c -serial pty -vcpus 4
-acpi -domain-name rhel4i386 -net
nic,vlan=1,macaddr=00:16:3e:39:f9:76,model=rtl8139 -net
tap,vlan=1,bridge=xenbr0 -vncunused -k en-us -vnclisten 127.0.0.1
# netstat -t -a -n -p | grep qemu
tcp 0 0 127.0.0.1:5900 0.0.0.0:*
LISTEN 4005/qemu-dm
# virsh dumpxml rhel4i386 | grep graphics
<graphics type='vnc' port='5900'/>
Regards,
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
-=|
17 years, 5 months
3 vif NIC Limit?
by Stan Larson
First and foremost, great job with Xen in Fedora. Now, on to my question.
Are there any plans to extend the amount of vif interfaces beyond the
current limit of three in DomUs?
I realize I can use pciback to get around the current limitation. I'm
interested in a solution that doesn't require pciback.
Thanks,
--
Stan Larson
I/S Manager
Freedom Sales & Marketing
P: (727) 835-1150
F: (727) 835-1151
stan(a)freedomics.com
www.freedomics.com
17 years, 5 months
RE: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6
by Robert Thiem
When first setting up FC6 I had an issue where I could start an FC6 Xen
guest install but couldn't connect with VNC.
I don't know if it's the same (I can't remember the exact messages I was
getting), but it ended up being that "localhost" wouldn't resolve to an
IPv4 address. This was due to a nasty combination of anaconda putting IPv4
and v6 entries in /etc/hosts and system-config-network trimming the
"extra" v4 entry when run.
Anyway I'd suggest:
- Check that you can ping localhost
- Check there's a localhost entry in /etc/hosts associated with 127.0.0.1
(and not with ::1)
- Run "netstat -antp" to see what ports programs are listening on
Regards,
Robert Thiem
17 years, 5 months
RE: [Fedora-xen] virt-manager gives "The console iscurrentlyunavailable" in FC6
by Ranganathan, Shobha
Also the qemu*log files do not any errors for my latest run.
One of the previous runs I had "False I/O request ... in-service
already: 0, pvalid: 0, port: 0, data: 0, count: 0, size: 0
Thanks Dan for all your help..
I pretty much have a valid configuration as you have down here though...
-----Original Message-----
From: fedora-xen-bounces(a)redhat.com
[mailto:fedora-xen-bounces@redhat.com] On Behalf Of Ranganathan, Shobha
Sent: Tuesday, November 14, 2006 6:08 PM
To: Daniel P. Berrange
Cc: fedora-xen(a)redhat.com
Subject: RE: [Fedora-xen] virt-manager gives "The console
iscurrentlyunavailable" in FC6
# virsh dumpxml xenbox_G1FC5 | grep graphics
<graphics type='vnc' port='5900'/>
# netstat -t -a -n -p | grep qemu
tcp 0 0 127.0.0.1:5900 0.0.0.0:*
LISTEN 4517/qemu-dm
# ps -axuww | grep qemu
root 4517 0.3 0.4 32452 3324 ? Sl 17:53 0:01
/usr/lib64/xen/bin/qemu-dm -d 1 -m 256 -boot d -acpi -domain-name
xenbox_G1FC5 -net nic,vlan=1,macaddr=00:16:3e:4a:0d:50,model=rtl8139
-net tap,vlan=1,bridge=xenbr0 -vncunused -k en-us -vnclisten 127.0.0.1
I did try commenting the ::1 entry in /etc/hosts file. I still see this
issue.
Regards
Shobha Ranganathan
"The significant challenges we face cannot be resolved at the same level
of thinking we were at when we created them." Albert Einstein
-----Original Message-----
From: Daniel P. Berrange [mailto:berrange@redhat.com]
Sent: Tuesday, November 14, 2006 5:51 PM
To: Ranganathan, Shobha
Cc: Robert Thiem; fedora-xen(a)redhat.com
Subject: Re: [Fedora-xen] virt-manager gives "The console is
currentlyunavailable" in FC6
On Tue, Nov 14, 2006 at 05:45:17PM -0800, Ranganathan, Shobha wrote:
> Anyway I'd suggest:
> - Check that you can ping localhost
> I could ping the localhost
>
> - Check there's a localhost entry in /etc/hosts associated with
> 127.0.0.1
> (and not with ::1)
> I have two entries one with 127.0.0.1 and ::1. I went ahead and
> commented out ::1 entry
> - Run "netstat -antp" to see what ports programs are listening on
> I see various services on IP address of the local host 172.xx.xx.xx
and
> 127.0.0.1 and ::22 and ::1 and 0.0.0.0
>
> I see sshd, cupsd and hpiod running with local address as ::22, ::1
and
> 0.0.0.0.
For fully-virt / HVM guests you should see a 'qemu-dm' process
listening
on the port associated with VNC (something around 5900+). If you don't
then this is the primary problem to address - the qemu-dm*log file may
be useful. Also grabbing the command line for qemu-dm active process
should indicate what port it tried to start on. In my case:
# virsh dumpxml rhel4i386 | grep graphics
<graphics type='vnc' port='5900'/>
# ps -axuww | grep qemu
root 4005 0.0 0.1 64616 5132 ? Sl 20:05 0:00
/usr/lib64/xen/bin/qemu-dm -d 2 -m 500 -boot c -serial pty -vcpus 4
-acpi -domain-name rhel4i386 -net
nic,vlan=1,macaddr=00:16:3e:39:f9:76,model=rtl8139 -net
tap,vlan=1,bridge=xenbr0 -vncunused -k en-us -vnclisten 127.0.0.1
# netstat -t -a -n -p | grep qemu
tcp 0 0 127.0.0.1:5900 0.0.0.0:*
LISTEN 4005/qemu-dm
# virsh dumpxml rhel4i386 | grep graphics
<graphics type='vnc' port='5900'/>
Regards,
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
-=|
--
Fedora-xen mailing list
Fedora-xen(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen
17 years, 5 months
