Bugzilla – Bug 151796
install-initrd missing for XEN installation with yast
Last modified: 2007-04-06 12:25:13 UTC
the "virtual machine installation" in yast doesn't work. the hd image /var/lib/xen/images/domain1/hda got created, but /var/lib/xen/images/domain1/inst-initrd was missing and the yast/xen window got closed. I noticed that the rpm "install-initrd" wasn't installed though I selected the XEN package group at installation time (clean beta3). trying again, xen installation doesn't start either (there still is no initrd image in /var/lib/xen/). y2log says 2006-02-17 14:26:31 <1> dhcp177(18258) [YCP] VM_XEN.ycp:1028 xterm command: /usr/bin/xterm -T "Xen - domain3" -e /usr/sbin/xm create -c /etc/xen/domain3 trying to run /usr/sbin/xm create -c /etc/xen/domain3 gives Using config file "/etc/xen/domain3". Error: No kernel specified # cat /etc/xen/domain3 disk = [ 'file:/var/lib/xen/images/domain3/hda,hda,w' ] memory = 256 kernel = "" ramdisk = "/var/lib/xen/images/domain3/inst-initrd" name = "domain3" dhcp = "dhcp" extra = "TERM=xterm" restart = "onreboot" right now I'm running an update of dom0 to currectn SL-OSS-Factory...
Did it say something like "Error. Cannot prepare the virtual machine environment The installation will be aborted"? This might relate to another (internal) bug.
No, there was no (obvious) message/warning. I remember the following events (not sure about the sequence) after trying to start the installation -- without any user action ("press OK" or whatever...): - there was a message like "starting the virtual machine" - the yast2 xen install setup closed - the xterm for the virtual console popped up for a very short time and immedieately closed again
(In reply to comment #1) > Did it say something like > > "Error. Cannot prepare the virtual machine environment > The installation will be aborted"? > > This might relate to another (internal) bug. update: now the update from beta-3 to (more or less current) SL-OSS-Factory is done, and now I get that error box "Fehler: Umgebung des virtuellen Computers kann nicht vorbereitet werden. Die installation wird abgebrochen. OK" anything I can change/try/test/... ??
*** Bug 151799 has been marked as a duplicate of this bug. ***
OK then it is obviously the same problem as in the other bug ;) Reassigning...
I hope the problem with different probelem occurence with Paravirtualisation/Full virtualisation is covered as well.
Could you test the latest beta, please? (and attach y2logs when it still happens)
This defect is fixed for me in the latest beta.
I have the problem in openSUSE 10.2 too. YaST doesn not install the package "install-initrd" within YaST's XEN module. After installing "install-initrd" manually I see, that there are missing dependencies to "install-initrd": $ rpm -q yast2-vm xen install-initrd yast2-vm-2.14.2-7 xen-3.0.3_11774-20 install-initrd-1.0-72 $ rpm -q --requires install-initrd rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 /usr/bin/perl rpmlib(PayloadIsBzip2) <= 3.0.5-1 $ rpm -q --provides install-initrd install-initrd = 1.0-72 $ rpm -q --whatrequires install-initrd no package requires install-initrd
It might be strange but Yast really doesn't need install-initrd package installed. The trick is that yast uses install-initrd from the installation source when creating a new VM. Using in this case means download, unpack, modify it for kernel-xen and copy it to the VM's directory. The reason is that you need install-initrd from the system which will be installed not from the running system (imagine e.g. openSUSE10.3 in VM which runs on top of SLES10 - you don't want to use install-initrd from SLES in openSUSE...) Yast needs install-initrd but it's a runtime (soft) dependency - the package is used/downloaded only when needed.