Bug 158367

Did you get any Xen output on the serial console ?

I have Xen running on several systems here, without the problem you are seeing.

Btw, I have the latest Xen RPMs up on: http://people.redhat.com/riel/xen_for_fc4/

No further output on the serial console.
Looked at the XenDemo CD and noticed that it configures the hypervisor to run
with the noht (no hyperthreading) option.
Tried that option and am now able to successfully boot Xen VMs under both
runlevel  3 and runlevel 5.
noht should be considered for a default xen configuration option.

Exactly what system are you running on?

I am using Xen with hyperthreading on a 3GHz Pentium IV and it's working just fine.

Also, what output do Xen and xenolinux give?
At what stage in the boot does it hang?

Created attachment 114679 [details]
Output of xm dmesg

Here is the output from the Xen kernel.  I do not see any messages when the
guest OS is booting and hyperthreading is enabled, I get "Using configfile
rawhide" and then it locks solid.  System is an Asus P4R800vm with an ATI 9100
IGP chipset.  everything is integrated on the motherboard with no additional
PCI cards.  I strongly suspect it is a quirk in the chipset, it did not come
out very long after Intel announced Hyperthreading.

Btw, do you need to specify the "noht" option on the Xen boot line, or is it
enough to specify that on the domain 0 kernel boot options?

I specify it in the grub.conf file on the xen kernel line:
kernel /boot/xen.gz com1=115200,8n1 noht

In that case some ACPI workaround might work - and that will be automatically
imported from Linux once I upgrade to a newer version of Xen, in which all
things ACPI are implemented in domain 0 instead of the hypervisor.

I tried upgrading to such a version already, but the upstream xen tree didn't
boot on my test system when I tried, so FC4 will still have an older version of Xen.

I'll let you know when I've upgraded rawhide to a newer Xen with ACPI in domain
0 (post FC4).

If it is an ACPI problem that would fit in with another symptom I've seen.  When
I boot with the Xen kernel, the system does not automatically power off when I
shut down domain 0.  It powers off fine when I use a regular kernel.

I simply assumed that is a limitation of the current Xen implementation, or do
you have systems that can automatically power off domain 0?

Same problem seen with:

xen-2-20050522
kernel-xenU-2.6.11-1.1341_FC4
kernel-xen0-2.6.11-1.1341_FC4

I get this too.
The problem seems to be related to the init.d xendomains failing to start.
The xendomains script fails when trying to call "log_success_msg" which is a
function that doesn't exist.

*** Bug 163468 has been marked as a duplicate of this bug. ***

Any luck with getting ACPI into domain 0? or any workarounds?
Thanks.

Same problem here with:

xen-2-20050522
kernel-xenU-2.6.12-1.1398_FC4
kernel-xen0-2.6.12-1.1398_FC4

The host is running: Intel(R) Pentium(R) 4 CPU 2.60GHz

Are you getting the crash in exactly the same place?
i.e. strace xm create -c xen1
 send(3, "POST /xend/domain HTTP/1.1\rHost"..., 149, 0) = 149
 send(3, "config=%28vm%28name+xen1%29+%28"..., 403, 0
(from bug 163468)

I have the same problem 

I have tested with the lasted rpm version of xen in FC4

xen-2-20050522
kernel-xenU-2.6.12-1.1398_FC4
kernel-xen0-2.6.12-1.1398_FC4

I have tested with noht and same problem, when I do a xm create the machine 
crash!

Rik van Riel - any update on this? Should I hang around with Fedora for Xen, or
get something else installed to test it?

I built a new Xen package for FC4 recently, which will be pushed out together
with the next kernel update.  That should fix this issue.

From User-Agent: XML-RPC

A new Xen version has been pushed to Fedora Core 4 updates.  This version of Xen (combined with the latest kernel update) should fix this issue.

Please reopen this bug if the problems continue with the latest Xen and kernel updates.

Created attachment 118220 [details]
cat /proc/cpuinfo

Booting kernel-xen0-2.6.12-1.1447_FC4, I get:

***
CPU0 fatal trap: vector = 6 (invalid operand)
[error_code=0000]
Aieee! CPU0 is toast...
***

There's a stack trace above that. If needed, I'll take a photo of it.

You also need a newer Xen package, xen-2-20050823.

Bad dependency then? I've installed xen-2-20050823 from testing, and it fixes
the Aieee!, but boot won't finish.
First networking fails to start properly - it can't get an ip from my dsl router
(it can't even ping the router).
After starting bluetooth, the computer hangs.

Last lines in /var/log/messages:
 Aug 29 20:23:30 localhost kernel: Bluetooth: HCI socket layer initialized
 Aug 29 20:23:30 localhost kernel: Bluetooth: L2CAP ver 2.7
 Aug 29 20:23:30 localhost kernel: Bluetooth: L2CAP socket layer initialized

# lspci -v|grep -i net
02:08.0 Ethernet controller: 3Com Corporation 3Com 3C920B-EMB-WNM Integrated
Fast Ethernet Controller (rev 40)

I've seen this on my test system here, once or twice.  I haven't managed to
reliably reproduce this problem though ;(((

Just to rule out the vsyscall page (where I made some changes), could you try
booting with "vdso=0" ?

No such luck unfortunately :(

I tried moving /lib/tls to /lib/tls.disabled, but I still got the warning, and I
still got the hang.

I have an onboard video card which I think shares the main ram. Could that be
the problem? Any ideas?

lspci -v|grep -i vga
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon 9100 IGP (prog-if
00 [VGA])

From User-Agent: XML-RPC

A new Xen version has been pushed to Fedora Core 4 updates.  This version of Xen (together with kernel 2.6.12-1.1435 or newer) should fix this issue.

Please reopen this bug if the problems continue with the latest Xen and kernel updates.

Now My machine is booted with 

[root@router ~]# rpm -qa |grep xen
kernel-xenU-2.6.12-1.1447_FC4
kernel-xen0-2.6.12-1.1447_FC4
xen-2-20050823
[root@router ~]#

but When I do 

[root@router ~]# service xend start
Exception connecting to xenstored: (2, 'No such file or directory')
Trying again...
Exception connecting to xenstored: (2, 'No such file or directory')
Trying again...
[root@router ~]# Exc

xend don´t start

(In reply to comment #21)
I'm seeing the same problem with my system, and it looks like I have the same
hardware (ASUS P4R800vm, ATI 9100 IGP chipset)

I was able to get the system to finish booting by disabling th OpenCT daemon. 
No network and no USB mouse.

about the comment #25 

 I have created /var/run/xenstored and /var/lib/xenstored and xend started fine.

I select the xen0 kernel, and my computer reboots.

kernel-xen0-2.6.12-1.1456_FC4

use

kernel-xen0-2.6.12-1.1456_FC4 
and
kernel-xenU-2.6.12-1.1456_FC4

and xen 3.0 from 

http://people.redhat.com/riel/xen_for_fc4/

for me is working.

Not for me. Crashes this time, just after starting bluetooth.

Tried 1526 kernel, got an error about not enough space on CPU0 or something.