Using CentOS 5.1 with Xen 3.2. I'm trying to install a fully virtualized system for the first time and doing this with an old Suse 9.0 (this probably would run paravirtualized, maybe it won't run, anyway, because of hardware problems). I start with virt-manager and after choosing "fully virtualized" it presents me two options for install media: iso image and CD-ROM or DVD, but the latter is grayed out. I have the install source on CDs ... Is this normal or do I yet need another patch to make it work in xen 3.2?
Kai
fyi: paravirtualized means the OS is new enough to have extensions to be virtualization-aware and support it in order to not have to emulate all of the hardware completely. The older OS would probably run fully virtualized, i.e. in a QEMU environment.
Michael
Kai Schaetzl wrote:
Using CentOS 5.1 with Xen 3.2. I'm trying to install a fully virtualized system for the first time and doing this with an old Suse 9.0 (this probably would run paravirtualized, maybe it won't run, anyway, because of hardware problems). I start with virt-manager and after choosing "fully virtualized" it presents me two options for install media: iso image and CD-ROM or DVD, but the latter is grayed out. I have the install source on CDs ... Is this normal or do I yet need another patch to make it work in xen 3.2?
Kai
Michael Will wrote on Mon, 21 Apr 2008 11:28:56 -0700:
fyi: paravirtualized means the OS is new enough to have extensions to be virtualization-aware and support it in order to not have to emulate all of the hardware completely. The older OS would probably run fully virtualized, i.e. in a QEMU environment.
Ahm, yes, sorry, that is why I wanted to try to run it fully virtualized. I made a typo and skipped the "not" in "this probably would run paravirtualized". Yes, I'm sure it won't run paravirtualized.
AFAIK Xen can also install and run fully virtualized guests. The problem is that install location. (maybe there are others, but this at least is the one I'm facing now).
Qemu: I haven't ever used it. Would you recommend using it in this case? Can I run that side-by-side with Xen? Are the rpms part of CentOS?
Kai
libvirt enables you to run that stuff side by side.
I don't know the answer about the rpms, I just have done it on fedora core 8 before. I presume you could find out quicker than my by looking for it first if it is installed:
rpm -q qemu
if not, try to install it with yum
yum install qemu
Michael
Kai Schaetzl wrote:
Michael Will wrote on Mon, 21 Apr 2008 11:28:56 -0700:
fyi: paravirtualized means the OS is new enough to have extensions to be virtualization-aware and support it in order to not have to emulate all of the hardware completely. The older OS would probably run fully virtualized, i.e. in a QEMU environment.
Ahm, yes, sorry, that is why I wanted to try to run it fully virtualized. I made a typo and skipped the "not" in "this probably would run paravirtualized". Yes, I'm sure it won't run paravirtualized.
AFAIK Xen can also install and run fully virtualized guests. The problem is that install location. (maybe there are others, but this at least is the one I'm facing now).
Qemu: I haven't ever used it. Would you recommend using it in this case? Can I run that side-by-side with Xen? Are the rpms part of CentOS?
Kai
Michael Will wrote on Mon, 21 Apr 2008 11:59:23 -0700:
if not, try to install it with yum
ok, it's in Extras. I can start the install from an iso image, but it's extremely slow. As I read this is normal without kqemu. Unfortunately, there's no kqemu or similar sounding rpm in Extras.
Kai
Kai Schaetzl wrote on Mon, 21 Apr 2008 20:15:24 +0200:
I start with virt-manager and after choosing "fully virtualized" it presents me two options for install media: iso image and CD-ROM or DVD, but the latter is grayed out.
I created an image from the first CD and tried to install from it as I needed that for qemu, anyway. That fails as well, though. The error is "Unable to complete install 'libvirt.libvirtError virDomainCreateLinux() failed POST operation failed. (xend.err 'Error creating domain: long() argument must be a string or a number')" and some more Python traceback stuff. Does this sound familiar to anyone? Some known patch to apply? Google finds only this single article and I'm not sure if it really applies: http://article.gmane.org/gmane.comp.emulators.xen.user/33078
Kai