Bug 114717 - Xen does not work on x86_64
Summary: Xen does not work on x86_64
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Final
Hardware: x86-64 SUSE Other
: P2 - High : Normal
Target Milestone: ---
Assignee: Kurt Garloff
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 97395
  Show dependency tree / graph
 
Reported: 2005-09-01 14:13 UTC by Marco Michna
Modified: 2006-02-27 22:08 UTC (History)
2 users (show)

See Also:
Found By: Component Test
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Michna 2005-09-01 14:13:31 UTC 
I tried XEN on x86_64 but didn't succeed. 
The virtual console stops at: 
 
--8<-- 
xen_blk: Initializing virtual block device driver 
Registering block device major 3 
hda: 
-->8--
Comment 1 peter czanik 2005-09-02 14:46:12 UTC 
I have the same on i586 (a P4 machine).
Comment 2 Kurt Garloff 2005-09-05 22:16:01 UTC 
This is dom0 or domU booting? 
If domU: Do you export as a whole disk or as a partition? 
If dom0: Try to pass "lapic" to xen as boot param.
Comment 3 peter czanik 2005-09-06 05:18:21 UTC 
For me (P4), it was domU. I don't really know the answer, as all I did, that
after booting using the Xen kernel, I started from YaST2 the "Virtual machine
installation (Xen)" module, and this is, how it stopped.
Comment 4 Kurt Garloff 2005-09-16 22:18:30 UTC 
Xen should work much better in RC1 and RC2 and final. 
Though Jeff has reported that something broke between RC2 and RC4 :-( 
Can you please try 
- SL10.0 final 
and if this fails 
- SL10.0 RC2 
 
TIA!
Comment 5 Marco Michna 2005-09-19 12:19:07 UTC 
final: 
 
Beside that it is still highly instable (sudden reboot, freezes with X) I was 
able to start up the machine with XEN but now it seems that the module crashes 
and X gets crazy. If you start the module again then it wants to create 
domain2. 
 
Also when I try to list them with "xm list" then I just get a error: 
 
        Unexpected error: xen.xend.XendProtocol.XendError 
 
Going to install RC2 now
Comment 6 Marco Michna 2005-09-19 14:15:36 UTC 
With RC2 I have the graphic problems - half of the screen is getting black 
from time to time especially when I use "xm destroy domain1". 
 
I was able to boot into domain0 and successful created domain1 (xm list showed 
both). After that I tried to create domain2 and noticed that the kernel lines 
are missing in the config file (empty string) same for all others added later. 
 
There are also a lot of other problems like using "xm console domain1" gives 
an error: xenconsole: xs_get_domain_path(): No such file or directory
Comment 7 Stephan Böni 2005-10-17 11:35:17 UTC 
I have the same problem in the final 10.0 version (x86_64). I'm sure it was never tested before releasing. Xen (domU) on x86_64 does not work at all.
Comment 8 Stephan Böni 2005-10-18 13:45:30 UTC 
With the newest Xen build 7398 the Dom0 boots fine. Starting DomU makes allways some troubles. I found out, that the problem is arround mounting the filesystems. Often one or more device nodes such /deb/hda1 are missing. If the device node for the root filesystem is missing the boot process hangs. I think this is a problem arround udev.

Stephan
Comment 9 Kurt Garloff 2005-11-30 02:20:07 UTC 
Hmm, it indeed looks like udev trouble.
Is this still reproducible with 7608?
Comment 10 Kurt Garloff 2005-12-20 20:07:41 UTC 
Another question: Do you run out of loop devices?
You may want to boot with max_loop=64 ... The default is only 8.
Comment 11 Clyde Griffin 2006-02-27 22:08:24 UTC 
We believe that various issues (udev, loopback, x86_64 kernel port, etc) have been fixed.  Closing this defect.  Retest on recent SL 10.1.