QEMU launch NodeOS failed #92
Comments
|
It should work out of the box. Could you be able to start only the
|
|
Hi piranna, I do "npm start" at node-barebones it look like same prolem. ................................... I launch it on my Ubuntu VM. |
|
It's really strange what you say... pleasy try with 'PLATFORM=qemu_32 npm By the way, the timestamp are too high, they should be just 2 seconds, not
|
|
I am trying to do "PLATFORM=qemu_32 npm install". And my result of "uname -a" is: Linux APPLE 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
It's really strange, it should work... Could you give me the full outputs? |
|
Same problem on qemu-system-i386 qemu-system-i386 -enable-kvm -nographic --kernel bzImage -append console=ttyS0 full log outputs: ...........there's nothing after this |
Then honestly I don't know what could be happening here, sorry :-/ For reference, I'm using as development platform Ubuntu Mate 14.10 "Si quieres viajar alrededor del mundo y ser invitado a hablar en un |
|
Inside a VM I had to remove the |
|
I have been getting some compilation problems with latest master and needed to go back some commits... just to find this same issue! O_O I've gone down to previous ones (up to dda61c4 "x86 64 bits support") The worst thing is that I'm running Linux natively and they are some commits that I compiled from scratch. I've also checked about some installed package like QEmu or Linux kernel, but they are from several days before... Removing Don't know what's happening here, but seems something serious and don't know what could be happening here... :-( |
|
Ok, I think I've found it! :-D Last Tuesday Node.js got updated to v0.11.15. Since we are using the latest available unstable release, I've hardcoded it to use the v0.11.14 version and has been able to run it :-) Need to test with a fully clean repo, but seems that's the reason why it didn't worked. @joeking11829, could you be able to confirm this? If so, then maybe we should use fixed versions instead of depend in the latest ones available, and maybe configure a bot task to test the new ones, what do you think? |
|
I've open an issue on Node.js regarding to this regression. |
|
Hi I download the new repo for NodeOS. But I get another error. Error log: [ 14.856312] EXT4-fs (sda): couldn't mount as ext3 due to feature incompatibilities it look like mount root file system failed. Any idea !? |
Oh, sh*t, my fault. No, both rootfs & usersfs has been mounted (good! as set this for the size instead DISK_SIZE=32 # Size in MB
$((DISK_SIZE*1024))I'll try to fix it later. "Si quieres viajar alrededor del mundo y ser invitado a hablar en un |
|
Fixed in master |
|
Awesome !! It works !! |
|
I'm happy you got it working again :-) |
|
I just built the latest master and this error still shows up: And the system is quite slow to boot. I don't remember seeing these warnings the last time I built it. |
|
Those errors are normal, it's only saying that the root filesystem is Ext4 but it's mounting it as Ext2, probably related to the auto filesystem detection (I don't know why, the order in Regarding to being slower, how much slower? It should fully boot in under 10 seconds... Do you have KVM disabled on QEmu? This would make it to boot up to 30 seconds... |
|
Yes, KVM is disabled, but it was not this slow the last time. It boots up around 20+ seconds, and the most wait time is when the mount warnings show up, so I guess they are related. |
|
auto filesystem detection is implemented by reading |
|
Yeah, I remember. However my main concern is that we didn't come a long way since I converted the old modules, and the boot time is already about 10 seconds slower. By the way the login is slow too. When I give it the password and press enter several seconds pass until it actually logs in. |
|
I don't remember about having any similar issue, but it's true I'm having a hard time and didn't work on NodeOS since a week ago. I'll try to find some time and test it again paying attention to this. |
|
I m installing NodeOS on Ubuntu 14.04LTS 32-bit. npm ERR! Linux 3.13.0-35-generic npm ERR! Please include the following file with any support request: Help me!!! |
|
Did you try installing it using docker? |
|
No, I have problem regarding the docker, in fact i didnt get through docker. So i tried Qemu. |
|
Docker is currently unmaintained, hope we can retake it soon when finish to define the filesystem architecture. |
Hi,
I'm new to NodeOS.
I'm trying to build NodeOS.
use npm install to get and build NodeOS
But, when i use qemu-system-x86_64 to launch NodeOS
When linux kernel initial, it stay on :
.........................
[ 20.437522] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 20.524758] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 20.652660] TCP: cubic registered
[ 20.751746] Initializing XFRM netlink socket
[ 20.815748] NET: Registered protocol family 10
[ 20.884425] sda: unknown partition table
[ 21.045296] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 21.092952] sd 0:0:0:0: [sda] Attached SCSI disk
[ 21.133849] sit: IPv6 over IPv4 tunneling driver
[ 21.184698] NET: Registered protocol family 17
[ 21.232982] Key type dns_resolver registered
[ 21.351737] registered taskstats version 1
[ 21.422624] Magic number: 15:958:761
[ 21.446296] console [netcon0] enabled
[ 21.476595] netconsole: network logging started
[ 21.642662] ALSA device list:
[ 21.653663] No soundcards found.
[ 22.132709] Freeing unused kernel memory: 5948K (ffffffff81a72000 - ffffffff82041000)
[ 22.216699] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input3
It can not launch successfully !!
What can i do !?
The text was updated successfully, but these errors were encountered: