Bug 556255 - Creation of new VM with yast2 not possible. Message: No kernel was found. The installation may have failed
Summary: Creation of new VM with yast2 not possible. Message: No kernel was found. Th...
Status: RESOLVED DUPLICATE of bug 551664
Alias: None
Product: openSUSE 11.2
Classification: openSUSE
Component: Xen (show other bugs)
Version: Final
Hardware: x86-64 openSUSE 11.2
: P5 - None : Major with 2 votes (vote)
Target Milestone: ---
Assignee: Charles Arnold
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-17 19:43 UTC by rob steiger
Modified: 2010-02-10 23:02 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description rob steiger 2009-11-17 19:43:36 UTC
User-Agent:       Opera/9.80 (Windows NT 5.1; U; de) Presto/2.2.15 Version/10.01

i went to yast2 - virtualization, create virtual maschines.
after just entering an installtion source (virtual disk phy:/dev/sr0), letting the other infos on default i press ok
- i see the vm is started and a thigthvmc display comes on, but disapears with an error in a new window:

Error
No kernel was found.  The installation may have failed

problem did not arise in openSUSE 11.0 (X86-64) but in 11.1 x86-64 (so i waited for 11.2)

Reproducible: Always

Steps to Reproduce:
1. install opensuse 11.2 on server with xen host-sw
2. start yast
3. create a new ve
Actual Results:  
error No kernel was found.  The installation may have failed

Expected Results:  
process going on...

/etc/xen/vm/opensuse11-2 at this point:
name="opensuse11-2"
uuid="351cbf92-82dd-d17a-b9e5-1b63b5a1f52d"
memory=512
maxmem=512
vcpus=1
on_poweroff="destroy"
on_reboot="destroy"
on_crash="destroy"
localtime=0
builder="linux"
kernel="/tmp/kernel.RkmJvY"
ramdisk="/tmp/install-initrd.8Up8OP"
extra=" install=hd:/dev/xvdb "
disk=[ 'file:/var/lib/xen/images/opensuse11-2/disk0,xvda,w', 'phy:/dev/sr0,xvdb:cdrom,r', ]
vif=[ 'bridge=br0', ]
vfb=['type=vnc,vncunused=1']
Comment 1 Charles Arnold 2009-11-17 20:08:47 UTC
You will need to use a network install source to get around this problem.

*** This bug has been marked as a duplicate of bug 551664 ***
Comment 2 Charles Arnold 2009-11-17 21:52:02 UTC
You can also use the following work around with an ISO file after launching 'Create Virtual Machine" and getting to the "Summary" screen.

Step 1: From the "Summary" screen, Select "Operating System Installation".
Step 2: From the "Operating System Installation" screen, select "Virtual Disk" and then "Add".
Step 3: From the "Virtual Disk" Screen, select your ISO file.
Step 4: Press "Ok" and "Apply" to return to the "Summary" screen.
Step 5: From the "Summary" screen, select "Disks".
Step 6: From the "Disks" screen highlight the ISO you just added as an installation source and Select "Remove".
Step 7: From the "Disks" screen select "Harddisk".
Step 8: From the "Virtual Disks" screen select your ISO file.  Check the "Read-Only Access" box.
Step 9: Press "Ok" and "Apply" to return to the "Summary" screen.
Step 10: From the "Summary" screen Press "Ok" to start the installation (assuming other settings are correct).

During the installation of the guest, you may see a warning on the "Installation Settings" screen under the "Booting" section that says "It was not possible to determine the exact order of disks for device map. The order of disks can be changed in "Boot Loader Installation Details".  So far, we have not seen any adverse effects from this warning by simply ignoring it.
Comment 3 rob steiger 2009-11-19 10:05:48 UTC
thanks for fast response!

>You will need to use a network install source to get around this problem.

i tested this (had to open the fw, as it does not use a proxy at this stage).
worked properly.

>ou can also use the following work around with an ISO file after launching
>Create Virtual Machine" and getting to the "Summary" screen...

i'll test and comment this within the next week.
Comment 4 rob steiger 2009-12-11 23:36:55 UTC
hello
tested the workaround form "charles arnold" above. works ok - saw the warning.
so that's at least a way to bring a para-virtual-guest up.
thanks.

rob
Comment 5 Masim Sugianto 2010-02-10 23:02:23 UTC
Thanks. The workaround also saved my time. Is this possible to make the above workaround as 11.2 update?