nowbotstorm

Steps to reproduce

1. Download Vagrant and VirtualBox, then restart the PC.
2. Download all Vagrant files from GitHub and put them in a folder
3. Run CMD (Windows) with admin rights
4. Go to the folder and type vagrant up
5. Try to start the VM

Expected behaviour

The VM should start

Actual Behaviour

The VM dosen't start and gives error Result Code: E_FAIL (0x80004005)

System

Host
Windows 10
VirtualBox version
5.0.0
Vagrant version
1.7.4.msi (Windows)

FYI @karlitschek@LukasReschke@dragotin

These are the files that were created:

From Linux, running the script startup.sh gives me a working appliance.
That is not ported to windows.

Can you try that on a Linux box?

@jnweiger I could, but then I would need to make a VM with Linux as guest as I run Windows - and that kind of makes this box useless IMHO. :/

I mean, as a user I make a box to run a guest operating system. If I'm already on Linux, why make a VM? Then it would be easier to just install it with this guide for example: https://www.en0ch.se/installation/

The idea of this box is to make it as easy as possible for the end-user, and most non-tech users run Windows. People on Linux tend to have the technical skills to do the installation by themselves. Please correct me if I'm wrong.

I meant, you try Linux to see of my scripts are broken there too. If so, I have an issue to fix.
The porting to windows that I mentioned is another TODO, of course. Help welcome!

I'd be happy, if the vm-image can be run from a windows machine after it fell out of a Linux build environment. For me that is more important than porting the build environment to windows.

So in other words you can't just download Vagrant´s Windows version and run the commands from CMD in Windows? What has to be changed? My first time ever using boxes like this.

I mean, the box is created as it should if I type vagrant up with your Vagrantfile, and should just be able to run as any other VM no matter what host machine you run?

For example, if I create a .vmdk I can run that .vmdk on whatever system I want, what is the difference here?

@enoch85 I think it is O.K. to require Windows to build an VM. This is something that developers, packagers or very experienced users do. The normal users will just download the appliance from owncloud.org that we build using this scripts.
So I think it is fine to require Windows to build a VM.
What do you think?

@jnweiger Sorry, can't test the startup.sh. I get connection timeout. It works on Windows with vagrant up as I mentioned before. Maybe I can convert the .sh file to make Windows read it as a script. I'll check if that's possible. EDIT Not possible as the sh file contains Linux commands.

@karlitschek Ok, now I get the picture. :) I thought the users would build the VM and we would just maintain the scripts. Seems like I need to learn how Vagrant works then, and I would also have to get a Linux laptop (don't want to dual-boot) to build the boxes and test it before it's released.

Btw, have a look at this: https://github.com/enoch85/master/blob/master/startup-script.sh

It's not cleaned up and not exactly the one I use, just uploaded it so you can see how I do.

My idea is to build a built in script that runs at startup, and prompt the user with different settings like keyboard and such. It would also be nice if we could make the set-secure-permissions-owncloud.sh execute in the end so that the permissions were safe, owncloud-style.

What do you think?

@jnweiger Here is the output of bash startup.sh:

Hi @enoch85 I tested it on linux and it worked like a charm.

I´ll run it on Windows and will have some results this afternoon.

@Kawohl Thanks for testing! 👍

@jnweiger How do we solve the problem that the user still has to do a initial setup to configure the system to suit their language, keyboard and such?

@enoch85 vagrant and the built vdmk runs just fine on my windows7

What was your exact process of building the vdmk? How did you mount it to Virtualbox? The main issue was not reproduceable.

Btw, have a look at this: https://github.com/enoch85/master/blob/master/startup-script.sh

It's not cleaned up and not exactly the one I use, just uploaded it so you can see how I do.

My idea is to build a built in script that runs at startup, and prompt the user with different settings like keyboard and such. It would also be nice if we could make the set-secure-permissions-owncloud.sh execute in the end so that the permissions were safe, owncloud-style.

What do you think?

I have something similar in the eval appliance at https://owncloud.com/download/#servervirtualimage
the eval appliance is openSUSE-13.1 based. Ubuntu seems to have most of the needed building blocks ready. That makes a much nicer startup script. Thanks for pointing that out!

@Kawohl Hmm, ok. Good! After some further investigation it seems like it's a problem with VirtualBox and Windows 10. I will downgrade to 8.1 later tonight and test again. Regarding the steps I did as I wrote in the main issue.

@jnweiger Nice! Do you want help with the install script?

@enoch85 please feel free to reopen for better visibility. I missed the windows 10 part.

@Kawohl Here is the enhancment regarding the startup-script: #3

@enoch85 thank you for your efforts,

I was able to reproduce this with Windows10 and Virtualbox 5.0.

Thanks for contributing!

Confirmed, works with Win 8.1. I close this and wait for VirtualBox to come up with a fix.

I just realized that I said something wrong in a previous comment. :-)
I mean 'I think it is O.K. to require Linux to build an VM.' instead of 'I think it is O.K. to require Windows to build an VM'. Sorry for the confusion

Hehe, thought so. thanks for the clarification!