Is there an official recommended way of building vbox_x86-eng target?
Ron M
Nathaniel Husted
lunch vbox-x86-eng
make -j16
make install_vdi
Though the installer won't boot in Virtualbox. It complains about a
corrupted partition.
I've also tried:
lunch vbox-x86-eng
make -j16
make android_disk_vdi
But receive a kernel panic followed by:
"atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying
access hardware directly."
My only though is that I need to try this on a machine that supports
hardware virtualization... though I really hope it's not depending on
me have VT-d capabilities.
Cheers,
Nathaniel
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
Doug Schaefer
they? I'm mainly interested in how you set up the SATA devices and
what commands you used to get the installer running correctly.
Nathaniel Husted
instructions for running the VirtualBox option. It appears that
Android just will not function with SATA drives. Virtualbox MUST be
set up with an IDE controller.
Cheers,
Nathaniel
On Wed, Nov 16, 2011 at 4:45 PM, Mark Renouf <mre...@google.com> wrote:
> Here's what I'm seeing. I tried both the "Install to" option and the "Boot
> from" option.
> "Install to" stops, waiting for a /dev/sdb2 (which apparently never appears)
> "Boot from" fails to boot fully because there is no /system partition
> mounted (or so it seems).
>
> I've also included a screenshot of my VirtualBox settings, I believe I have
> these correct.
>
> I'm hoping somebody can figure this out :-)
Doug Schaefer
mouse pointer.
One cool thing I saw on the first boot, it put me right into the home
screen and I was able to use the keyboard to select things, including
a very nice swap to another page that showed very acceptable graphics
performance. Now, just need to get a mouse pointer.
:D
Nathaniel Husted
development server rebuild so I will not be able to play around with
Android and VirtualBox until tomorrow eve. However, if you happen to
find a solution I will be most interested. I'm curious as it does not
seem that the previous post I linked to earlier had the mouse issues.
I'd love to know what step I have either conveniently left out or if
there's something different about ICS when it comes to mouse
interaction.
Hopefully someone comes up with a solution for this one!
Cheers,
Nathaniel
Doug Schaefer
home screen where keyboard navigation works).
It's use is pretty limited. I think this turns into an
android-porting, or android-x86.org discussion pretty quickly.
:D
dfages
the good news with the mouse is that ICS now includes all the
necessary code in the framework to support mouse type input devices
(with previous versions you had to hack the framework - you can check
what have been done on this in the android-x86 project).
Then, you can get the mouse pointer quite easily : you just have to
rebuild a kernel with the appropriate PS/2 mouse driver.
- Get the emulator kernel source "android-goldfish-2.6.29" (as stated
by JQB)
- Copy the arch/x86/configs/vbox_defconfig to .config
- "make ARCH=x86 menuconfig" and add the PS/2 mouse driver ("Device
Drivers"->"Input device support"->"Mice"->"PS/2 mouse"
- "make ARCH=x86"
- Get the arch/x86/boot/bzImage and replace the prebuilt vbox kernel
in your ICS source code tree (or create a dedicated device for this)
- Rebuild your android_disk.vdi as stated and use it :-)
If you have some difficulties to do it, I'll happily share my kernel
binary.
Concerning the network, it works well at a "system level" (on my side,
I've configured my Android VM in VBox to use a "Bridge" type of
virtual NIC - so that my Android directly access the network and uses
the DHCP server on my LAN). I'm able to ping from the shell. The
network is not available from the GUI because the "Ethernet" type of
network device doesn't seem to be supported in the Android framework -
I'll look if there's an easy solution on this.
Best regards,
Dan.
On 17 nov, 03:17, Doug Schaefer <cdtd...@gmail.com> wrote:
> That and there's no network access (reinstalled to get back to the
> home screen where keyboard navigation works).
>
> It's use is pretty limited. I think this turns into an
> android-porting, or android-x86.org discussion pretty quickly.
>
> :D
>
>
>
>
>
>
>
> On Wed, Nov 16, 2011 at 8:30 PM, Nathaniel Husted <nhus...@gmail.com> wrote:
> > I am currently having the exact same issue. I am in the middle of a
> > development server rebuild so I will not be able to play around with
> > Android and VirtualBox until tomorrow eve. However, if you happen to
> > find a solution I will be most interested. I'm curious as it does not
> > seem that the previous post I linked to earlier had the mouse issues.
> > I'd love to know what step I have either conveniently left out or if
> > there's something different about ICS when it comes to mouse
> > interaction.
>
> > Hopefully someone comes up with a solution for this one!
>
> > Cheers,
> > Nathaniel
>
> >> A-ha, that did it. Now back to your original point. How do I get a
> >> mouse pointer.
>
> >> One cool thing I saw on the first boot, it put me right into the home
> >> screen and I was able to use the keyboard to select things, including
> >> a very nice swap to another page that showed very acceptable graphics
> >> performance. Now, just need to get a mouse pointer.
>
> >> :D
>
> >>> This is the closest thing I've found in the archive that discusses
> >>> instructions for running the VirtualBox option. It appears that
> >>> Android just will not function with SATA drives. Virtualbox MUST be
> >>> set up with an IDE controller.
>
>
> >>> Cheers,
> >>> Nathaniel
dfages
mouse), eth0 is on and configured for DHCP by default.
So, if you're using DHCP, you just have to manually set the DNS server
using the command line.
For example, "setprop net.dns1 8.8.8.8"
The DHCP client sets the net.eth0.dnsX properties which are not used
(certainly because Ethernet is not well supported).
> home screen where keyboard navigation works).
>
> It's use is pretty limited. I think this turns into an
> android-porting, or android-x86.org discussion pretty quickly.
>
> :D
>
>
>
>
>
>
>
> On Wed, Nov 16, 2011 at 8:30 PM, Nathaniel Husted <nhus...@gmail.com> wrote:
> > I am currently having the exact same issue. I am in the middle of a
> > development server rebuild so I will not be able to play around with
> > Android and VirtualBox until tomorrow eve. However, if you happen to
> > find a solution I will be most interested. I'm curious as it does not
> > seem that the previous post I linked to earlier had the mouse issues.
> > I'd love to know what step I have either conveniently left out or if
> > there's something different about ICS when it comes to mouse
> > interaction.
>
> > Hopefully someone comes up with a solution for this one!
>
> > Cheers,
> > Nathaniel
>
> >> A-ha, that did it. Now back to your original point. How do I get a
> >> mouse pointer.
>
> >> One cool thing I saw on the first boot, it put me right into the home
> >> screen and I was able to use the keyboard to select things, including
> >> a very nice swap to another page that showed very acceptable graphics
> >> performance. Now, just need to get a mouse pointer.
>
> >> :D
>
> >>> This is the closest thing I've found in the archive that discusses
> >>> instructions for running the VirtualBox option. It appears that
> >>> Android just will not function with SATA drives. Virtualbox MUST be
> >>> set up with an IDE controller.
>
>
> >>> Cheers,
> >>> Nathaniel
Ron M
Ron M
Jean-Baptiste Queru
sure that it'd compile. I wouldn't go as far as calling it a hack, but
it probably fell behind a bit, especially in the domain of graphics
(where things have evolved a lot) and input (where things have changed
as well). Let's call it "work in progress".
JBQ
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
Doug Schaefer
It's really an input issue I suppose. Android-x86 used to have a patch
to make it work. Given I've seen a mouse pointer on the Transformer, I
was hoping it would be part of the base and not a driver that ASUS had
added (who seems to be quasi involved with android-x86 now that I
think about it, hmmm).
Jean-Baptiste Queru
know that there've been some changes in the way inputs are handed off
from the kernel to userland, and it's possible that the default 2.6.29
vbox kernel might not have all the necessary support for that.
I believe that the framework has some debugging commands to help
figure out which input events it's receiving, and that would probably
be useful to debug this case. You'll probably get the best expertise
in android-platform, where the framework experts lurk.
JBQ
Daniel FAGES
I'm not sure you saw my post few hours ago but to get the mouse pointer you have to rebuild the kernel with the good driver.
Dan.
Doug Schaefer
Nathaniel Husted
link JBQ posted to the 4.0.1 kernel sources that were released in the
SDK. I figure that could be easily rebuild as well with appropriate
x86 support.
Cheers,
Nathaniel
On Thu, Nov 17, 2011 at 12:30 PM, Daniel FAGES <dfa...@gmail.com> wrote:
Jean-Baptiste Queru
that I've released, so a straight rebuild as-is should get the same
results (fingers crossed), and you'll need to actually make changes in
order to make progress.
JBQ
Daniel FAGES
Dan.
Doug Schaefer
Thanks,
Doug.
Daniel FAGES
The emulator kernel source is available:
git clone https://android.googlesource.com/kernel/goldfish
cd goldfish
git checkout origin/android-goldfish-2.6.29
Jean-Baptiste Queru
have the relevant projects created, I'll create a proper list on
source.android.com.
JBQ
Doug Schaefer
guoqi...@gmail.com
Does anyone know how to configure the screen size and skin for the
vbox image as in emulator ?
Thanks,
Ron M
Ron M
Ron M
Ron M
guoqi...@gmail.com
one more question about the simulation. Seems the vbox emulate a
tablet. Is there anyway to simulate a phone in vbox?
On Nov 17, 2:47 pm, dfages <dfa...@gmail.com> wrote:
Daniel FAGES
It should be related to your version of gcc - according to https://bbs.archlinux.org/viewtopic.php?id=119341
--
unsubscribe: android-kerne...@googlegroups.com
website: http://groups.google.com/group/android-kernel
Doug Schaefer
Google search is your friend :). I changed the mentioned lines
manually and things are working with the 4.6 gcc. If we had gerrit
review up and running, we could submit a patch to fix it for
everyone...
Bzbit
platform, let's say notebook (with basic functionality of course)
On Nov 18, 12:00 am, Doug Schaefer <cdtd...@gmail.com> wrote:
> And I have a mouse pointer. Thanks for the help guys!
>
>
>
> On Thu, Nov 17, 2011 at 2:05 PM, Jean-Baptiste Queru <j...@android.com> wrote:
> > Yup. Sorry the kernels are a bit hard to find without gitweb. Once I
> > have the relevant projects created, I'll create a proper list on
> > source.android.com.
>
> > JBQ
>
> > On Thu, Nov 17, 2011 at 10:55 AM, Daniel FAGES <dfa...@gmail.com> wrote:
> >> Quoting JBQ :
>
> >> The emulator kernel source is available:
>
> >> git clonehttps://android.googlesource.com/kernel/goldfish
> >> cd goldfish
> >> git checkout origin/android-goldfish-2.6.29
>
> >> 2011/11/17 Doug Schaefer <cdtd...@gmail.com>
>
> >>> Sorry guys, I lost track of where the kernel source is. Could you repeat
> >>> that?
>
> >>> Thanks,
> >>> Doug.
>
> >>> On Thu, Nov 17, 2011 at 1:43 PM, Daniel FAGES <dfa...@gmail.com> wrote:
> >>> > Yes, and you have to add the "PS/2 mouse" support to the vbox_defconfig
> >>> > to
> >>> > have the mouse working using VirtualBox.
>
> >>> > Dan.
>
> >>> > 2011/11/17 Jean-Baptiste Queru <j...@android.com>
>
> >>> >> Just as an FYI, the prebuilt vbox kernel exactly matches the sources
> >>> >> that I've released, so a straight rebuild as-is should get the same
> >>> >> results (fingers crossed), and you'll need to actually make changes in
> >>> >> order to make progress.
>
> >>> >> JBQ
>
> >>> >> On Thu, Nov 17, 2011 at 10:28 AM, Nathaniel Husted <nhus...@gmail.com>
> >>> >> wrote:
> >>> >> > I'll try that later as well. I know with a bit of searching there's a
> >>> >> > link JBQ posted to the 4.0.1 kernel sources that were released in the
> >>> >> > SDK. I figure that could be easily rebuild as well with appropriate
> >>> >> > x86 support.
>
> >>> >> > Cheers,
> >>> >> > Nathaniel
>
> >>> >> > On Thu, Nov 17, 2011 at 12:30 PM, Daniel FAGES <dfa...@gmail.com>
> >>> >> > wrote:
> >>> >> >> Hi,
> >>> >> >> I'm not sure you saw my post few hours ago but to get the mouse
> >>> >> >> pointer
> >>> >> >> you
> >>> >> >> have to rebuild the kernel with the good driver.
>
> >>> >> >> Dan.
>
> >>> >> >> 2011/11/17 Doug Schaefer <cdtd...@gmail.com>
> >>> >> >>> >>> <cdtd...@gmail.com>
> >>> >> >>> >>> wrote:
>
> >>> >> >>> >>>> That and there's no network access (reinstalled to get back to
> >>> >> >>> >>>> the
> >>> >> >>> >>>> home screen where keyboard navigation works).
>
> >>> >> >>> >>>> It's use is pretty limited. I think this turns into an
> >>> >> >>> >>>> android-porting, or android-x86.org discussion pretty quickly.
>
> >>> >> >>> >>>> :D
>
> >>> >> >>> >>>> On Wed, Nov 16, 2011 at 8:30 PM, Nathaniel Husted
> >>> >> >>> >>>> <nhus...@gmail.com>
> >>> >> >>> >>>> > <cdtd...@gmail.com>
> >>> >> >>> >>>> > wrote:
> >>> >> >>> >>>> >> A-ha, that did it. Now back to your original point. How do
> >>> >> >>> >>>> >> I
> >>> >> >>> >>>> >> get a
> >>> >> >>> >>>> >> mouse pointer.
>
> >>> >> >>> >>>> >> One cool thing I saw on the first boot, it put me right
> >>> >> >>> >>>> >> into
> >>> >> >>> >>>> >> the
> >>> >> >>> >>>> >> home
> >>> >> >>> >>>> >> screen and I was able to use the keyboard to select things,
> >>> >> >>> >>>> >> including
> >>> >> >>> >>>> >> a very nice swap to another page that showed very
> >>> >> >>> >>>> >> acceptable
> >>> >> >>> >>>> >> graphics
> >>> >> >>> >>>> >> performance. Now, just need to get a mouse pointer.
>
> >>> >> >>> >>>> >> :D
>
> >>> >> >>> >>>> >> On Wed, Nov 16, 2011 at 6:47 PM, Nathaniel Husted
> >>> >> >>> >>>> >> <nhus...@gmail.com>
> >>> >> >>> >>>> >> wrote:
> >>> >> >>> >>>> >>> This is the closest thing I've found in the archive that
> >>> >> >>> >>>> >>> discusses
> >>> >> >>> >>>> >>> instructions for running the VirtualBox option. It appears
> >>> >> >>> >>>> >>> that
> >>> >> >>> >>>> >>> Android just will not function with SATA drives.
> >>> >> >>> >>>> >>> Virtualbox
> >>> >> >>> >>>> >>> MUST
> >>> >> >>> >>>> >>> be
> >>> >> >>> >>>> >>> set up with an IDE controller.
>
> >>> >> >>> >>>> >>> Link:
>
> >>> >> >>> >>>> >>>https://groups.google.com/group/android-building/browse_thread/thread...
>
> >>> >> >>> >>>> >>> Cheers,
> >>> >> >>> >>>> >>> Nathaniel
>
> >>> >> >>> >>>> >>> On Wed, Nov 16, 2011 at 4:45 PM, Mark Renouf
> >>> >> >>> >>>> >>> <mren...@google.com>
> ...
>
> read more »- Hide quoted text -
>
> - Show quoted text -
Doug Schaefer
that need to be built before it'll run on real x86 hardware.
1) Hardware acceleration. Looks like the software renderer is using
LLVM now, which is OK but not great. And it seems there is a tiny bit
of Mesa to hook that up. I'd like to see full blown Mesa to at least
get the open source graphics drivers working.
2) Network management. Android assumes wireless networking so there
are things missing.
android-x86.org has stuff for #2 and has been on/off again with #1
(off in Gingerbread). So I would look there to see if any progress is
being made towards notebook support. AOSP is really close which is
very cool, but there's still porting work to do.
Jean-Baptiste Queru
for ES and the necessary extensions.
JBQ
Nathaniel Husted
AndroidX86 list. The current available source, however, is just a
clone of the official ICS source as of early this morning EST. My
guess is the difficulty right now will be getting Mesa to play nice,
especially the vm environments.
Cheers,
Nathaniel
Daniel FAGES
Concerning, the network management, it's not a very big deal - it 's already working with some "command line".
I agree the biggest work is on the OpenGL hardware support.
Dan.
Chih-Wei Huang
Nathaniel Husted於 2011年11月23日星期三UTC+8上午3時36分18秒寫道：
Bzbit
Is hardware-acceleration for OpenGL ES is must? or we can live with SW
implementation?
If so - can you please elaborate how can I build ICS with the SW
implementation.
Thx
Jean-Baptiste Queru
JBQ
Ron M
There are four build configs for the goldfish project kernel:
goldfish_defconfig i386_defconfig vbox_defconfig x86_64_defconfig
x86_64_defconfig configuration, from your experience?
Is anybody here really using the VBOX configuration with AOSP, now
that emulator-x86+KVM is on, and performing quite well?
I can tell that I am using VBOX with the android-x86 project, but it
is quite broken as per my experience, at the moment (just FYI it uses
a 3+ kernel)
>
> read more »
Jean-Baptiste Queru
to making sure that the vbox config actually compiles. I've never
built an emulator kernel myself. That's really the realm of
android-kernel, though, not android-building. At the platform level,
we happily use prebuilt kernels.
JBQ
Daniel Fages
I can tell you'd rather use the vbox_defconfig for VirtualBox.
I use it to build my VBox images - which you can find on my blog : http://www.buildroid.org/blog/
I had to modify the vbox_defconfig to add the following drivers :
- Mouse
- Audio (Intel AC97)
You may also want to enable ACPI on it.
Regards,
Dan.
Ron M
Can you please post your .config file? I am having issues with "make
menuconfig" (see below.)
I have a couple of questions which are probably more related to the
kernel build system, but as we already have a thread going on for this
subject, it would be easier to follow here:
(1)
Is only "menuconfig" supported as the config menu editor?
make xconfig fails for the goldfish branch, falsely claiming that QT
is not properly installed although I am able to use "make xconfig"
for vanilla linux kernel on the very same host.
~/Android/ICS_Master/kernel/goldfish$ make xconfig
CHECK qt
*
* Unable to find the QT3 installation. Please make sure that
* the QT3 development package is correctly installed and
* either install pkg-config or set the QTDIR environment
* variable to the correct location.
*
make[1]: *** No rule to make target `scripts/kconfig/.tmp_qtcheck',
needed by `scripts/kconfig/qconf.o'. Stop.
make: *** [xconfig] Error 2
(2)
When I
make vbox_defconfig
make menuconfig
Then the .config file completely changes between the vbox_defconfig
and when I quit the "menuconfig" editor. I think it actually reverts
to some x86_64 configuration, and it breaks my kernel compilation, so
I can't trust it to work.
Any idea why that would happen? Any work around to the problem?
>
> read more »
Daniel Fages
you'll find attached a .config with mouse and sound enabled.
Your mistake is to forgot to put the "ARCH=x86" in the make command line
You have to write "make ARCH=x86 menuconfig"
Dan.
> ...
>
> read more »