Problems with Xen + FC5 + Thinkpad

[Brad Smith]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello all,

I recently upgraded from FC4 to FC5 on my Thinkpad T30 laptop and am looking forward to
playing with
Xen. However, I've hit a few stumbling blocks along the way. Following the
instructions at

http://www.fedoraproject.org/wiki/FedoraXenQuickstartFC5

I installed the Xen0 kernel and booted my system with it. However it hangs, seemingly
forever, at
the "Starting xend" stage. The OS seems ok as keypresses are still printed to
the screen, but
because the daemon never completes its startup process the boot sequence never finishes.
Upon
rebooting I noticed an error that gets printed while the kernel is loading, which says
that it could
not bind IRQ2 to guest because it is in use by cascade. This happens consistently, so I
wonder if
it's a hardware problem?

I booted the system into single user mode and chkconfig'd xend off, booted normally
and attempted to
start the daemon post-boot. It printed a message about starting the Bridged Firewall,
which I had
not seen during bootup, but still seemed to hang indefinitely.

Oh, and SELinux is loaded but not enforcing. Should that be sufficient?

Does anyone have suggestions for how I might further troubleshoot this?

Thanks,
- --Brad
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>
> iD8DBQFEKrcaDvp49DvQ8kcRAv8yAJ0cHBQsP3KwEGb+x9GZTXga6e24/ACeIQG6
> MCywwa529LxnXECf2YLo4SI=
> =Z3wj
> -----END PGP SIGNATURE-----

[Daniel Veillard]

On Wed, Mar 29, 2006 at 11:34:58AM -0500, Brad Smith wrote:
>  -----BEGIN PGP SIGNED MESSAGE-----
>  Hash: SHA1
>  
>  Hello all,
>  
>  I recently upgraded from FC4 to FC5 on my Thinkpad T30 laptop and am looking forward to
> playing with
>  Xen. However, I've hit a few stumbling blocks along the way. Following the
> instructions at 
  Try to make a clean install to make sure you really have all FC5 bits.
You can check /var/log/xend.log for hints on what's going wrong.

Daniel

-- 
Daniel Veillard      | Red Hat http://redhat.com/
veillard(a)redhat.com  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/

[Robert Story]

On Wed, 29 Mar 2006 11:34:58 -0500 Brad wrote:
BS> -----BEGIN PGP SIGNED MESSAGE-----
BS> Hash: SHA1
BS> 
BS> Hello all,
BS> 
BS> I recently upgraded from FC4 to FC5 on my Thinkpad T30 laptop and am
BS> looking forward to playing with Xen. However, I've hit a few stumbling
BS> blocks along the way. Following the instructions at
BS> 
BS> http://www.fedoraproject.org/wiki/FedoraXenQuickstartFC5
BS> 
BS> I installed the Xen0 kernel and booted my system with it. However it
BS> hangs, seemingly forever, at the "Starting xend" stage.

Did you do the part about updating grub to include 'init 3' to disable X? If
so, go back and delete the 'init' (you just need '3'). This fixed the
dom0
kernel hang I had.

I asked someone in the #fedora irc channel to fix this, but it's still there.

If anyone can fix it, it also needs to be fixed on 
http://www.fedoraproject.org/wiki/FedoraXenQuickstart

[Stephen C. Tweedie]

Hi,

On Wed, 2006-03-29 at 14:33 -0500, Robert Story wrote:

>  Did you do the part about updating grub to include 'init 3'
> to disable X? If
>  so, go back and delete the 'init' (you just need '3'). This fixed the
> dom0
>  kernel hang I had. 
>  I asked someone in the #fedora irc channel to fix this, but it's
> still there. 
Please open a bugzilla for this so we can look into it.  There is
nothing fundamentally incompatible between Xen and X: my Xen desktop,
running X, had an uptime of over 8 days when I shut it down earlier
today.  init 3 is *not* needed in general; if you have a specific
hardware config that isn't working under Xen with X, then that's
something that needs debugged.

Thanks,
 Stephen

[Robert Story]

On Fri, 31 Mar 2006 21:39:25 -0500 Stephen wrote:
SCT> > Did you do the part about updating grub to include 'init 3' to
disable
SCT> > X? If so, go back and delete the 'init' (you just need '3').
This fixed
SCT> > the dom0 kernel hang I had.
SCT> 
SCT> > I asked someone in the #fedora irc channel to fix this, but it's still
SCT> > there.
SCT> 
SCT> Please open a bugzilla for this so we can look into it.  There is
SCT> nothing fundamentally incompatible between Xen and X: my Xen desktop,
SCT> running X, had an uptime of over 8 days when I shut it down earlier
SCT> today.  init 3 is *not* needed in general;


Note that I wasn't complaining about X, which does work, but about the wiki
page suggesting to add 'init 3' to the boot args to boot into run level 3.
That's wrong, and causes the kernel to hang on boot. A simple '3' is needed
to
boot into run level 3.

Still want a bug report? It should be fixed, because a newbie isn't going to
know this, and will think xen doesn't work.