Installation issue ...
 
Notifications
Clear all

[Solved] Installation issue with Virtual Box

13 Posts
5 Users
0 Reactions
3,267 Views
0959e40b151a6923a10e38782cecb12e?s=80&d=mm&r=g
Posts: 7
Admin
(@jmichaelson)
Member
Joined: 5 months ago

Hi @Bern_G, Quick question for you on your Virtualbox situation. What kind of disk did you set it up with (i.e., SCSI, SATA, PIIX4, etc.) in the virtual machine settings. We recommend the PIIX4 or some other IDE variant for the virtual box environment. The specific problem you're having is very common with SCSI or SATA drives

Reply
a5fced1136088a4e08e1de35cc6490e6?s=80&d=mm&r=g
Posts: 5
(@rleejr)
Active Member
Joined: 4 weeks ago

Seems that CSP on VirtualBox will only boot in rescue mode. Otherwise it can't find anything in /dev/cs.

Reply
0959e40b151a6923a10e38782cecb12e?s=80&d=mm&r=g
Posts: 7
Admin
(@jmichaelson)
Member
Joined: 5 months ago

Hi @rleejr, have you tried changing the device type for the virtual machine?

Reply
1 Reply
a5fced1136088a4e08e1de35cc6490e6?s=80&d=mm&r=g
(@rleejr)
Joined: 4 weeks ago

Active Member
Posts: 5

@jmichaelson 

I imported the CSP-1.0.1.ova file, which created the Controller: SCSI LsiLogic csp-1.0.1-64-disk1.vdi. I then deleted that and moved that disk to Controller: IDE PIIX4. Then it failed to boot at all. When configured with SCSI controller, system does boot up in rescue mode only.

Reply
0959e40b151a6923a10e38782cecb12e?s=80&d=mm&r=g
Posts: 7
Admin
(@jmichaelson)
Member
Joined: 5 months ago

Don't delete and recreate the disc. Change its type to PIIX4. Go into settings, change from Basic to Expert, click storage and then change the type like in the pic i attached

Reply
a5fced1136088a4e08e1de35cc6490e6?s=80&d=mm&r=g
Posts: 5
(@rleejr)
Active Member
Joined: 4 weeks ago

For the OP solution, open VirtualBox, go to settings > storage and drag the disk vmdk file from the SCSI controller up to the IDE controller. Start the vm and it should boot properly without issue. 

For those who have converted the vmdk file to qcow2 file, run openstack cli command:
openstack image set --property hw_disk_bus=ide <image ID>

Reply
1 Reply
f63654a35ea0c3ef153a4cd650ec4e56?s=80&d=mm&r=g
Admin
(@sandor)
Joined: 5 months ago

Member
Posts: 16

@rleejr 
Thanks for sharing your findings for a working solution! It seems like theres a few routes to go for making virtualbox work, which is nice to know.

Reply
Page 2 / 2
Share: