# Problem with SUSE 12.1 JeOS image (Vmware)

**URL:** <https://forums.suse.com/t/problem-with-suse-12-1-jeos-image-vmware/28271>\
**Category:** SLES Install-Boot\
**Created:** [June 10, 2016, 10:49pm UTC](https://forums.suse.com/t/problem-with-suse-12-1-jeos-image-vmware/28271 "2016-06-10T22:49:03Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![dgersic](https://avatars.discourse-cdn.com/v4/letter/d/8491ac/32.png) [@dgersic](https://forums.suse.com/u/dgersic)\
**Post date:** [June 10, 2016, 10:49pm UTC](https://forums.suse.com/t/problem-with-suse-12-1-jeos-image-vmware/28271/1 "2016-06-10T22:49:03Z")

</div>

I downloaded the JeOS image for Vmware from:

[https://www.suse.com/eval/download?event\_id=SGDGNTD20639&event\_name=Eval:](https://www.suse.com/eval/download?event_id=SGDGNTD20639&event_name=Eval:)  
+JeOS&icid=SGDGNTD20640&icname=Eval:+JeOS  
+Nurture&build=xXfp0Cx4V1M~&login\_required=1#

I verified that the download was good, and the MD5 checksum matches the  
available one from that page.

In VMware, then, I make a new VM, use existing VMDK, and start the VM. I  
see the Grub boot screen, and the initial OS load begins, but then ends  
with:

```auto
+ export'biosBootDevice=No devices matches MBR ID: 0x9806f0f7 !'
+ biosBootDevice='No devices matches MBR ID: 0x9806f0f7 !'
+ sleep 1
+ true
+ ifix=0
+ match_count=0
+ try_count=15
+ '[' 15 -eq 15 ']'
+ export 'biosBootDevice=Failed to find boot device !'
+ biosBootDevice='Failed to find boot device !'
+ return 1
+ systemExcption 'Failed to find boot device !' reboot
+ local 'IFS=
'
+ set +x
+ echo -e '[20.734726] Failed to find boot device !'
+ '[' 0 = 0 ']'
+ set +x
+ case "$what" in
+ cat /var/log/boot.kiwi
[21.439475] rebootException: reboot in 120 sec...
```

Is this image actually known to be good?

–  
David Gersic  
Knowledge Partner [http://forums.microfocus.com](http://forums.microfocus.com)  
If you find this post helpful, please click on the star below.

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [June 11, 2016, 7:55pm UTC](https://forums.suse.com/t/problem-with-suse-12-1-jeos-image-vmware/28271/2 "2016-06-11T19:55:14Z")

</div>

Hi  
That error "biosBootDevice=No devices matches MBR ID: normally indicates boot order, check the VM boot order and make sure it’s pointing at the image.

---

<div class="post-metadata">

**Author:** ![dgersic](https://avatars.discourse-cdn.com/v4/letter/d/8491ac/32.png) [@dgersic](https://forums.suse.com/u/dgersic)\
**Post date:** [June 13, 2016, 6:00pm UTC](https://forums.suse.com/t/problem-with-suse-12-1-jeos-image-vmware/28271/3 "2016-06-13T18:00:02Z")

</div>

On Sat, 11 Jun 2016 17:04:01 +0000, malcolmlewis wrote:  
[color=blue]

> Hi  
> That error "biosBootDevice=No devices matches MBR ID: normally indicates  
> boot order, check the VM boot order and make sure it’s pointing at the  
> image.[/color]

I don’t see anything interesting in the BIOS options, but I moved “Hard  
Disk” ahead of “Removable Devices” to see if that would help. It didn’t.

In the VM settings, there is only one disk, this 24G VMDK.

It seems to be connected correctly, because I get the Grub boot ok with  
two options:

```auto
SLES12-SP1-JeOS-for-VMware [VMX]
Failsafe -- SLES12-SP1-JeOS-for-VMware [VMX]
```

which seems to be correct for this image. It’s after Grub, with the  
actual OS loading where it doesn’t seem to be able to figure out what to  
do.

I tried booting from an OpenSUSE Live CD, which works, and it looks to me  
like the disk is there. fdisk -l reports:

```auto
Disk /dev/sda: 24 GiB, 25769803776 bytes, 50331648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4378BEB3-7E8F-4887-AF19-9A128869DA59

Device Start End Sectors Size Type
/dev/sda1 2048 6147 4100 2M BIOS boot
/dev/sda2 8192 417795 409604 200M EFI System
/dev/sda3 419840 50331520 49911681 23.8G Linux filesystem

Disk /dev/loop0: 466.2 MiB, 488833024 bytes, 954752 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
```

I can successfully mount the EFI and root partitions without errors, so I  
think the file systems are ok.

All of which leads me back to my original question. Is this image  
actually good?

–  
David Gersic  
Knowledge Partner [http://forums.microfocus.com](http://forums.microfocus.com)  
If you find this post helpful, please click on the star below.

---

<div class="post-metadata">

**Author:** ![smflood](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/smflood/32/10576_2.png) [@smflood](https://forums.suse.com/u/smflood)\
**Post date:** [June 13, 2016, 7:26pm UTC](https://forums.suse.com/t/problem-with-suse-12-1-jeos-image-vmware/28271/4 "2016-06-13T19:26:06Z")

</div>

On 10/06/16 20:49, David Gersic wrote:  
[color=blue]

> I downloaded the JeOS image for Vmware from:
> 
> [https://www.suse.com/eval/download?event\_id=SGDGNTD20639&event\_name=Eval:](https://www.suse.com/eval/download?event_id=SGDGNTD20639&event_name=Eval:)  
> +JeOS&icid=SGDGNTD20640&icname=Eval:+JeOS  
> +Nurture&build=xXfp0Cx4V1M~&login\_required=1#
> 
> I verified that the download was good, and the MD5 checksum matches the  
> available one from that page.
> 
> In VMware, then, I make a new VM, use existing VMDK, and start the VM. I  
> see the Grub boot screen, and the initial OS load begins, but then ends  
> with:
> 
> ```auto
> + export'biosBootDevice=No devices matches MBR ID: 0x9806f0f7 !'
> + biosBootDevice='No devices matches MBR ID: 0x9806f0f7 !'
> + sleep 1
> + true
> + ifix=0
> + match_count=0
> + try_count=15
> + '[' 15 -eq 15 ']'
> + export 'biosBootDevice=Failed to find boot device !'
> + biosBootDevice='Failed to find boot device !'
> + return 1
> + systemExcption 'Failed to find boot device !' reboot
> + local 'IFS=
> '
> + set +x
> + echo -e '[20.734726] Failed to find boot device !'
> + '[' 0 = 0 ']'
> + set +x
> + case "$what" in
> + cat /var/log/boot.kiwi
> [21.439475] rebootException: reboot in 120 sec...
> ```
> 
> Is this image actually known to be good?[/color]

Which VMware product (and version) are you trying this with? ESXi,  
Workstation, Player, Fusion, etc.

Having just downloaded it to my Macbook I appear to be seeing the same  
behaviour as you with Fusion Professional 7.1.3.

I think on boot the VM is enumerating various storage devices  
(scsi[0-29] and [ata[1-30]) and not finding a suitable one - it doesn’t  
appear to be checking for sdX but perhaps I’m not using a supported  
VMware product?

## HTH.

Simon  
SUSE Knowledge Partner

* * *

## If you find this post helpful and are logged into the web interface, please show your appreciation and click on the star below. Thanks.

---

<div class="post-metadata">

**Author:** ![smflood](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/smflood/32/10576_2.png) [@smflood](https://forums.suse.com/u/smflood)\
**Post date:** [June 13, 2016, 8:01pm UTC](https://forums.suse.com/t/problem-with-suse-12-1-jeos-image-vmware/28271/5 "2016-06-13T20:01:27Z")

</div>

On 13/06/16 17:26, Simon Flood wrote:  
[color=blue]

> Which VMware product (and version) are you trying this with? ESXi,  
> Workstation, Player, Fusion, etc.
> 
> Having just downloaded it to my Macbook I appear to be seeing the same  
> behaviour as you with Fusion Professional 7.1.3.
> 
> I think on boot the VM is enumerating various storage devices  
> (scsi[0-29] and [ata[1-30]) and not finding a suitable one - it doesn’t  
> appear to be checking for sdX but perhaps I’m not using a supported  
> VMware product?[/color]

I’ve been poking around a bit and now have the same SLES12 SP1 JeOS  
booting under Fusion on my MacBook.

The thing that has made it work is in the Settings to change the Hard  
Disk from SCSI (the default when importing an existing disk image) to  
SATA - see Bus type under the “hidden” Advanced options.

## HTH.

Simon  
SUSE Knowledge Partner

* * *

## If you find this post helpful and are logged into the web interface, please show your appreciation and click on the star below. Thanks.

---

<div class="post-metadata">

**Author:** ![dgersic](https://avatars.discourse-cdn.com/v4/letter/d/8491ac/32.png) [@dgersic](https://forums.suse.com/u/dgersic)\
**Post date:** [June 13, 2016, 10:00pm UTC](https://forums.suse.com/t/problem-with-suse-12-1-jeos-image-vmware/28271/6 "2016-06-13T22:00:02Z")

</div>

On Mon, 13 Jun 2016 17:01:27 +0000, Simon Flood wrote:  
[color=blue]

> On 13/06/16 17:26, Simon Flood wrote:  
> [color=green]
> 
> > Which VMware product (and version) are you trying this with? ESXi,  
> > Workstation, Player, Fusion, etc.
> > 
> > Having just downloaded it to my Macbook I appear to be seeing the same  
> > behaviour as you with Fusion Professional 7.1.3.
> > 
> > I think on boot the VM is enumerating various storage devices  
> > (scsi[0-29] and [ata[1-30]) and not finding a suitable one - it doesn’t  
> > appear to be checking for sdX but perhaps I’m not using a supported  
> > VMware product?[/color]
> 
> I’ve been poking around a bit and now have the same SLES12 SP1 JeOS  
> booting under Fusion on my MacBook.
> 
> The thing that has made it work is in the Settings to change the Hard  
> Disk from SCSI (the default when importing an existing disk image) to  
> SATA - see Bus type under the “hidden” Advanced options.[/color]

Thanks Simon, I’ll give that a try. I’m using Workstation here.

–  
David Gersic  
Knowledge Partner [http://forums.microfocus.com](http://forums.microfocus.com)  
If you find this post helpful, please click on the star below.

---

<div class="post-metadata">

**Author:** ![dgersic](https://avatars.discourse-cdn.com/v4/letter/d/8491ac/32.png) [@dgersic](https://forums.suse.com/u/dgersic)\
**Post date:** [June 14, 2016, 12:00am UTC](https://forums.suse.com/t/problem-with-suse-12-1-jeos-image-vmware/28271/7 "2016-06-14T00:00:03Z")

</div>

On Mon, 13 Jun 2016 17:01:27 +0000, Simon Flood wrote:  
[color=blue]

> The thing that has made it work is in the Settings to change the Hard  
> Disk from SCSI (the default when importing an existing disk image) to  
> SATA - see Bus type under the “hidden” Advanced options.[/color]

Thanks, Simon, that did it. The option for SATA isn’t hidden in  
Workstation, it’s just not obvious that you’d need to change the disk  
type from the default of SCSI.

–  
David Gersic  
Knowledge Partner [http://forums.microfocus.com](http://forums.microfocus.com)  
If you find this post helpful, please click on the star below.
