vicidial.org

Hello Kumba,
I just created a vmware machine simply to view the new vicibox version (vmware options: 1 processor / 768mb ram / 20gb hd) and i got this after the first reboot:

doing fast boot
FATAL: Module processor not found.
FATAL: Module thermal not found.
FATAL: Module fan not found.
Creating device nodes with udev
Waiting for device /dev/sda1 to appear: ...............................Could not find /dev/sda1.

Host processors:
- try1 i3
- try2 core 2 duo

(only on 64bit version)
I hope it is useful for you

hi,

your hard drive must be larger than 20Gb, try 30 or 40.

I had the same problem, during install, the automatic partitioner won't calculate correctly for this size.

strange, my 20G HD worked just fine (but i gave it 1G RAM)

40gb hd and 1gb ram... same result

! I was using the 32 bit processor (preferred for VMware).

After all, it's a test environment, 64 bit vs 32 bit is not the issue, and VMWare is certainly not supported. (I do not think any changes will be made to the distro to accommodate VMWare unless you specify something rather simple that will not affect other options)

And what "Guest OS" did you specify in the setup?

yes 32bit works
but previous (3.0.x) 64bit releases work too...
the specified guest os was opensuse-64bit

I'm not totally agree when you say that vmware is for test purpose only. For a webserver install or better for a db install (not telephony) there are certain companies that cannot use physical machines and you have to deal with the existing vmware vsphere (64) infrastructure to set up those machines.. and the latest vsphere is better with 64bit guests.. that's why

vicidial does not run virtual. although you can run pieces of it in a limited environment virtually ... since you MUST have at least one machine that's not virtual ... you can run everything in that physical machine.

that's what vicidial is built and designed for. (at least until someone succeeds in virtualizing all of it, which may happen this year, and may not)

for me: VMware vicidial is for purely development and testing.

i bet that others use it this way as well.

but i do not expect that any development time will be spent to "make it work" in VMware, or Virtualbox or any other virtual environment for production. Not unless someone pays for it!

There was a stale repository that might have been causing issues. I rebuilt both the 32 and 64 bit versions of ViciBox, and both booted and installed fine under VirtualBox (What I use for dev work). If that doesn't solve your problem then I am not sure what will.

solved!

thanks a lot Kumba