| Summary: | X fails to start in VirtualBox in 1.3 M3 build appliance | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Runtime | Reporter: | Stefan Stanacar <sstncr> | ||||
| Component: | build-appliance | Assignee: | Cristian Iorga <cristian.iorga> | ||||
| Status: | VERIFIED DUPLICATE | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | Low | CC: | alexandru.c.georgescu, sgw | ||||
| Version: | 1.4 | ||||||
| Target Milestone: | 1.5 M3 | ||||||
| Hardware: | x86 | ||||||
| OS: | Multiple | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | --- | |||||
| Attachments: |
|
||||||
This will likely require somekind of machine configuration or form factor changes to get X started correctly in VirtualBox. I know it's been done once before. Hello Stefan, Please add the exact test case. How exactly did you run Build Appliance with VirtualBox? Please provide the procedure. Thanks, Cristian Hi Cristian, Running the build appliance in Virtual Box it's similiar to running it in VMWare Player. - build build-appliance-image or get one from autobuilder (for example last time I used the 1.3_M4 RC3 image from http://autobuilder.yoctoproject.org/pub/nightly/20120916-2/build-appliance/Yocto_Build_Appliance-20120916215307.zip ). You'll only need the .vmdk from the archive. - Create a new VirtualBox VM (choose Linux 2.6 64 bit, or Other Linux when asked which type of operating system). - Do not create a start-up disk when asked (or you could but it's useless because it's added as a SATA disk the VM won't boot) - After the VM it's created go to settings -> storage -> add a hard disk (select IDE controller from the storage tree) -> choose existing disk -> select the Yocto vmdk you unzipped earlier - start the vm -> it will boot but X will fail to launch (most likely some drivers need to be included in the build appliance recipe, vboxvideo or similar) Clarified. Hello, At the moment, taking into account the features approved for YP 1.4 release, there is no support for running Build Appliance under Oracle VM VirtualBox. While I work on investigating a switch from VMware Player to Oracle VM VirtualBox, the facts that I found on the internet suggests that VirtualBox reliability is much lower than that of VMware Player. For the moment, work on this feature is put on hold. If time will allow, this feature will be considered later in the release cycle of YP 1.4. Dup of 1971 *** This bug has been marked as a duplicate of bug 1971 *** Verified as per above comment. |
Created attachment 738 [details] Xorg log My build config used for bitbake build-appliance-image Build Configuration: BB_VERSION = "1.15.3" TARGET_ARCH = "x86_64" TARGET_OS = "linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "1.2+snapshot-20120823" TUNE_FEATURES = "m64" TARGET_FPU = "" meta meta-yocto = "(nobranch):8b8748c8f963900b83dc0fdd7757556f917fe4fd" X fails to start, message on screen is: xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error Xorg.0.log attached.