On Tue, 17 Feb 2009 20:55:01 jdd wrote:
Rodney Baker a écrit :
Dumb question, but have you installed the kernel source for the xen kernel? What directory does the symlink /usr/src/linux point to?
I don't know, I see only one kernel source from YaST. I installed "kernel-source" (still with YaST) and had the error given.
usually I had no problem (without xen), but here I changed HDD and have to reinstall all
I think there is another repository that you will need to add that will have extra kernel sources; the xen kernel is not the same as the standard kernel and the kernel sources need to match the running kernel in order for kernel modules to compile and load.
as an option, is it possible to read virtualbox disks with xen? first test didn't work (I have important things on a xp disk)
No - xen is not like virtualbox or vmware. Xen is a "hypervisor" - a lower level virtualisation system that operates below kernel level in "ring 0" or priveleged mode. The primary OS that you have installed is effectively a guest OS even though it is the first OS booted. Then xen (or kvm) hypervisor intercepts all priveleged instructions from the OS to the hardware so that multiple instances of the OS (or multiple OS's) can access the same hardware without conflicts. VMWare, Bochs, virtualbox etc. are effectively applications that emulate a complete pc but run on the host OS alongside other applications. This is very different to what xen does. Some CPU's (AMD-V and Intel-VT) support hardware-level virtualisation using either xen or kvm hypervisors that then allow the running of non-modified guest OS's. If you don't have one of these CPU's xen runs in a "paravirtualisation" mode and requires the guest OS to be xen-aware (hence the xen kernel). You cannot virtualise a standard build of WinXP or Vista (or any other Windows OS) whilst running in paravirtualisation mode. You can read the XP disk directly using ntfs-3g if you only want to retrieve data. -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ===================================================