Yes that is one of them. virt-manager is not listed in Gslapt but version 0.9.0 is available in sourcery.

There is also virt-manager 0.9.1 released 31 Jan 2012 - I found that one earlier in a Slackware repository somewhere but can locate it at the moment. Question is if I go with the latest virt ...

gapan wrote:What does "will not boot" mean?

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,3)

Despite doing a new GUI install which wrote uuid to lilo.conf and editing fstab to use uuids , system still will not boot.
fstab
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
UUID=0f0a95fe-8559-4d7f-9443-b7c11c210d05 swap swap defaults 0 0 ...

Ok booted SalixLive CD and mounted root of installed system:

su
mkdir /mnt/myroot
mount /dev/sda3 /mnt/myroot
cd /mnt/myroot
nano fstab

But I can't edit the file due to lack of permissions. Any suggestions.

Edit:
Ignore that just rebooted, tried again and now able to edit fstab. Not sure what I ...

I understand there is a new version of virt-manager available but how do I install this? virt-manager is not available from Gslapt package manager. How do I also ensure that I have the latest versions of all dependent packages. Is there a seperate repository I should be adding or something like that ...

If you can't access Salix anymore you could boot with SalixLive and execute LiloSetup who will setup UUIDs correctly for you and give you back access to all the OSs that are on your machine.
Thats very interesting, are you saying that LiloSetup in SalixLive is different to the LiloSetup which ...

Just had a thought about creating an extra lilo entry for booting when I have the other disks in the system - /dev/sdc3. Unfortunately lilo will not let me create a spare entry like that, when I try to save it I get: Fatal: Illegal root= specification.

If you change your drive setup you have to use UUIDs instead /dev/sdx names:
1. change everything in /etc/fstab
2. of course your boot disk still must hold the boot loader
3. the bootloader must tell the kernel where the root partition is by UUID, not by dev name

Maybe related info is in this ...

gapan wrote:Yes, you're right, lxrandr doesn't support that apparently. I thought it did, sorry.

Open sourcery and install arandr. That will do it. Make sure you refresh the slackbuild cache if you don't find the package in the list at first.

Thats it works fine, thanks.

I now add another drive with the intention of changing the boot order in the BIOS to select which drive to boot from.
What for? Lilo and other boot managers can boot fine different systems from different disk. You just have to install it on the boot disk and create a working configuration. You can ...