You are not logged in.
I've spent many hours trying to sort this out and have failed (including a complete reinstall of the base OS). The answer I hope is something easy.
I have followed the wiki page for the build and install of Xen 4.2 as closely as possible. Everything seems to build ok and I create the various files as directed. Yet dom0 will not boot. I think this is something to do with the grub.cfg as best I can tell from googling yet I have tried many variations of the modules lines yet none work:
From the top - booting Xen the first screen flys by last thing is something about 'scrubbing ram' and then I get this:
[Firmware Bug]: cpu0, try to use APIC500 (LVT offset 0) for vector 0x9f, but the register is already in use for fector 0x0 on this cpu
[Firmware Bug]: cpu 0, failed to setup threshold interrupt for bank 4, block 1 (MSRC0000408=0xc0000000010000000)
Failed to access perfctr msr (MSR c0010004 is fff934b9273a)
:: running early hook[udev]
:: running hook [udev]
:: Triggering uevents...
<long wait>
Waiting 10 seconds for device /dev/disk/by-uuid/7c48ae0a-adff-4338-ad8d-c87833454c3a ...
ERROR: device 'UUID=7c48ae0a-adff-4338-ad8d-c87833454c3a' not found. Skipping fsck
<dropped to recovery shell.. but cant type anything>
<very long wait, eventually get>
[rootfs /] INFO: task khubd:61 blocked for more than 120 seconds
"echo 0> /proc/sys/kernel/hung_task_timeout_secs" disables this message
It seems not to matter what is inserted for "root=" in the module /vmlinuz line of the grub.cfg. They all bomb out with the same message saying whatever you put in for root is not found. Here is the section of the grub.cfg Note: sda2 is the /boot and sda4 is / The UUID used is for sda4
menuentry 'Xen Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry\
_id_option 'xenlinux-core repo kernel-true-7c48ae0a-adff-4338-ab8d-c87833454c3a' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 \
fd1f2428-4bd5-4c90-9d1a-d07e4479a046
else
search --no-floppy --fs-uuid --set=root fd1f2428-4bd5-4c90-9d1a-d07e4479a046
fi
echo 'Loading Xen kernel ...'
multiboot /xen-4.2.0.gz dummy=dummy dom0_mem=1024M,max:1024M loglvl=all guest_loglvl=all dom0_max_vcpus=2 dom0_vc
pus_pin
module (hd0,gpt2)/vmlinuz-linux dummy=dummy root=UUID=7c48ae0a-adff-4338-ab8d-c87833454c3a ro
module (hd0,gpt2)/initramfs-linux.img
}
I'll add further, though I doubt this has anything to do with it - if I try to go back to the regular kernel boot I need to comment out the proc entry for xen from the /etc/fstab to get a somewhat clean boot. After that, I do get a login prompt but it is for singlue user. Looking at the output of systemctl I see that 'graphical.target' and 'multi-user.target' are marked both inactive and dead (in addition to the three xen services which fail to start) After a few minutes I get a console message about systemd-logind.service entered the failed state.
This has been a pretty dreadful expereince and I have 10 years of slakcware and more recently 5 years of BSD usage.
Thanks for your assistance.
Offline