Per Jessen wrote:
jdd,
I though I'd write up what I do when I install a xen host, just in case you spot a difference. Apart from installing over pxe+ssh+http, it's pretty standard stuff :
boot leap42 installation, from local copy of repo. ssh login start yast select additional repos (leap updates) partitioning - (10G for Dom0, 1Gb swap, the rest for LVM). dom0 root filesystem, either ext4 or jfs. minimum server selection. software selection: add kernel-xen, remove kernel-default, add xen, add xen-tools.
That's all I do. Interestingly, I think I have just reproduced your situation - on a Fujitsu desktop machine, I left the installation to finish by itself at around 16:15. When I got back around 17, it was in some weird state, but responding. I think I hit enter a couple of times and then it looked like I had a working system, just very slow. I've just now rebooted it, and it's now also just blank screen. I'm going to wait it out and see what happens - next thing is to fiddle with the grub options and get some more output.
On my machine, I saw numerous stalls: rcu_sched self-detected stall on cpu ... For the first boot-up, be patient, maybe wait 10minutes, then go and hit Esc and you should see some output. I pressed enter a few times which got the process moving and I finally got a login-prompt. The machine was still sluggish though. I amended the grub cmdline - I think it said "noresume resume=/dev/sda2 splash=silent ...." I changed this to "noresume". I don't know where to put "dom0_mem=512M". When you boot with that and you see the machine halting, just press Enter a couple of times. Something is clearly wrong, but at least you get a system up and running. -- Per Jessen, Zürich (3.6°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org