Error running QEMU with oe-core / angstrom console-image, hwclock: can't open '/dev/misc/rtc' : No such file or directory

Error running QEMU with oe-core / angstrom console-image, hwclock: can't open '/dev/misc/rtc' : No such file or directory

[Samuel Stirtzel]

Hi,
when running QEMU, build as console-image, some strange errors occur.

QEMU was started with the following command:
qemu-system-arm -M versatilepb -m 128 -kernel
/var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin -hda
/var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2
-append root=/dev/sda

Note: If QEMU would be run without machine configuration, it would
load the machine "integratorcp ARM Integrator/CP (ARM926EJ-S)
(default)" and crash, therefore I run "versatilepb ARM Versatile/PB
(ARM926EJ-S)" which should work according to the machine configuration
of qemuarm.conf (OT: there may be a typo in the conf:  "#@NAME:
arm_versaile_926ejs")


The Angstrom splash screen was displayed, after QEMU loaded a bit and
it stopped (with progress somewhere at the right end of the loading
bar).
Thereafter this error, among others, showed up:
hwclock: can't open '/dev/misc/rtc' : No such file or directory

Also it looks like the root filesystem was only mounted readonly,
makes no sense for me.

For further informations see this Screenshot:
http://imageshack.us/photo/my-images/263/consoleimageqemu.png/


Comments or help would be very appreciated

-- 
Regards
Samuel

Re: Error running QEMU with oe-core / angstrom console-image, hwclock: can't open '/dev/misc/rtc' : No such file or directory

[Samuel Stirtzel]

Hi,
well I never thought this would work out, but after adding "-o rw" to
the -append parameters the system started and the login prompt
appeared.

So this problem is solved, for completenes I append my used command
line to start qemu:

qemu-system-arm -M versatilepb -m 128 -kernel
/var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin -hda
/var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2
-append "root=/dev/sda -o rw"

-- 
Regards
Samuel

Re: Error running QEMU with oe-core / angstrom console-image, hwclock: can't open '/dev/misc/rtc' : No such file or directory

[Koen Kooi]

Op 3 aug. 2011, om 08:18 heeft Samuel Stirtzel het volgende geschreven:

> Hi,
> well I never thought this would work out, but after adding "-o rw" to
> the -append parameters the system started and the login prompt
> appeared.
> 
> So this problem is solved, for completenes I append my used command
> line to start qemu:
> 
> qemu-system-arm -M versatilepb -m 128 -kernel
> /var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin -hda
> /var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2
> -append "root=/dev/sda -o rw"

FWIW, this is what I use:

qemu-system-arm -M versatilepb -m 256M -kernel zImage --append 'root=/dev/sda rw console=tty0 raid=noautodetect' Angstrom-efl-nodm-image-eglibc-ipk-v2011.07-core-qemuarm.rootfs.ext3

Since I'm on OSX I build qemu myself and don't use the wrapper scripts.

regards,

Koen

Re: Error running QEMU with oe-core / angstrom console-image, hwclock: can't open '/dev/misc/rtc' : No such file or directory

[Khem Raj]

On 08/02/2011 11:18 PM, Samuel Stirtzel wrote:
> Hi,
> well I never thought this would work out, but after adding "-o rw" to
> the -append parameters the system started and the login prompt
> appeared.
>
> So this problem is solved, for completenes I append my used command
> line to start qemu:
>
> qemu-system-arm -M versatilepb -m 128 -kernel
> /var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin -hda
> /var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2
> -append "root=/dev/sda -o rw"
>

There is a smart script in scripts/ dir that you could use something 
like this

runqemu /var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin 
/var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2

and it will setup everything (even networking) for you

make sure that its run in shell where you have sourced setup environment 
of either oe-core or angstrom
Hope that helps

-Khem

Re: Error running QEMU with oe-core / angstrom console-image, hwclock: can't open '/dev/misc/rtc' : No such file or directory

[Samuel Stirtzel]

[-- Attachment #1: Type: text/plain, Size: 2225 bytes --]

2011/8/3 Khem Raj <raj.khem@gmail.com>:
> There is a smart script in scripts/ dir that you could use something like
> this
>
> runqemu /var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin
> /var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2
>
> and it will setup everything (even networking) for you
>
Already tried this one, but for some unknown reasons it doesn't work,
I get the following output:
-
samuel@S-Linux:/var/oe-core/setup-scripts$ runqemu
/var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin
/var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2
Set MACHINE to [qemuarm] based on kernel
[/var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin]

Continuing with the following parameters:
KERNEL: [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin]
ROOTFS: [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2]
FSTYPE: [ext2]
Setting up tap interface under sudo
[sudo] password for samuel:
sudo runqemu-ifup <gid> <native-sysroot-basedir>
samuel@S-Linux:/var/oe-core/setup-scripts$
-
This is all, no QEMU window appears or any other messages, or do I
have run something else.

For remote debugging purpose I wrote a generic script that will set up
a tap and bridge interface and restores the network connection after
qemu closes.
This script can also run QEMU with standard network settings.
Basically runqemu and my scripts should do the same thing(?), but
since runqemu doesn't work for me I made my own scripts (also it won't
need sudo if the standard network option is used).

The scripts are attached in this mail, to run the script you could use
"sh /somedir/generic_qemu_loader.sh --help".
This script however may not work on other systems than ubuntu, I share
it only for information exchange purpose.
If you still want to use it, keep in thought that I am a beginner in
shell coding!

The difference between the standard network settings and the
bridge/tap interfaces is, that the standard network only supports
outgoing TCP and UDP connections while the bridge/tap interface can be
used to host, for example, a gdbserver.


Regards
Samuel

[-- Attachment #2: generic_qemu_loader.tar.gz --]
[-- Type: application/x-gzip, Size: 2212 bytes --]

Re: Error running QEMU with oe-core / angstrom console-image, hwclock: can't open '/dev/misc/rtc' : No such file or directory

[Samuel Stirtzel]

Hi,
if anyone might be interested, after a code review I have redone parts
of the scripts.
They should be much more readable now and the user can pass more
parameters (like kernel image, root filesystem, memory and parameters
to qemu), however this still might not work on every machine.

This scripts are not a replacement for runqemu, they where just
created because runqemu does not work on my machine.
Normal users would probably do better if they use runqemu (I've tried
it like it is described here
http://sakrah.homelinux.org/blog/2011/03/using-openembedded-core-to-build-angstrom-for-qemu/
and like Khem hinted in his mail but it didn't won't work for me)

In the future I might update this script and to make things more
comfortable you can allways view the latest version, without
downloading any files, on the pastebin account I created solely for
this purpose:
http://pastebin.com/u/SkipIfEqual

This scripts where tested on ubuntu inside a network with a DHCP and
work fine for me (can connect from host to guest (QEMU) and vice
versa, from the host to the internet and from the guest to the
internet).

Regards
Samuel

Re: Error running QEMU with oe-core / angstrom console-image, hwclock: can't open '/dev/misc/rtc' : No such file or directory

[Khem Raj]

On 08/04/2011 01:08 AM, Samuel Stirtzel wrote:
> 2011/8/3 Khem Raj<raj.khem@gmail.com>:
>> There is a smart script in scripts/ dir that you could use something like
>> this
>>
>> runqemu /var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin
>> /var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2
>>
>> and it will setup everything (even networking) for you
>>
> Already tried this one, but for some unknown reasons it doesn't work,
> I get the following output:
> -
> samuel@S-Linux:/var/oe-core/setup-scripts$ runqemu
> /var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin
> /var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2
> Set MACHINE to [qemuarm] based on kernel
> [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin]
>
> Continuing with the following parameters:
> KERNEL: [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin]
> ROOTFS: [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2]
> FSTYPE: [ext2]
> Setting up tap interface under sudo
> [sudo] password for samuel:
> sudo runqemu-ifup<gid>  <native-sysroot-basedir>
> samuel@S-Linux:/var/oe-core/setup-scripts$

A fix for this problem has been committed to oe-core already. Update and 
retry

> -
> This is all, no QEMU window appears or any other messages, or do I
> have run something else.

Nothing more. It should pop up a window where you will see the new 
machine booting

>
> For remote debugging purpose I wrote a generic script that will set up
> a tap and bridge interface and restores the network connection after
> qemu closes.
> This script can also run QEMU with standard network settings.
> Basically runqemu and my scripts should do the same thing(?), but
> since runqemu doesn't work for me I made my own scripts (also it won't
> need sudo if the standard network option is used).
>
> The scripts are attached in this mail, to run the script you could use
> "sh /somedir/generic_qemu_loader.sh --help".
> This script however may not work on other systems than ubuntu, I share
> it only for information exchange purpose.
> If you still want to use it, keep in thought that I am a beginner in
> shell coding!
>
> The difference between the standard network settings and the
> bridge/tap interfaces is, that the standard network only supports
> outgoing TCP and UDP connections while the bridge/tap interface can be
> used to host, for example, a gdbserver.
>
>
> Regards
> Samuel
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Re: Error running QEMU with oe-core / angstrom console-image, hwclock: can't open '/dev/misc/rtc' : No such file or directory

[Samuel Stirtzel]

2011/8/4 Khem Raj <raj.khem@gmail.com>:
> On 08/04/2011 01:08 AM, Samuel Stirtzel wrote:
>>
>> 2011/8/3 Khem Raj<raj.khem@gmail.com>:
>>>
>>> There is a smart script in scripts/ dir that you could use something like
>>> this
>>>
>>> runqemu /var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin
>>> /var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2
>>>
>>> and it will setup everything (even networking) for you
>>>
>> Already tried this one, but for some unknown reasons it doesn't work,
>> I get the following output:
>> -
>> samuel@S-Linux:/var/oe-core/setup-scripts$ runqemu
>> /var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin
>> /var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2
>> Set MACHINE to [qemuarm] based on kernel
>> [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin]
>>
>> Continuing with the following parameters:
>> KERNEL: [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin]
>> ROOTFS:
>> [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2]
>> FSTYPE: [ext2]
>> Setting up tap interface under sudo
>> [sudo] password for samuel:
>> sudo runqemu-ifup<gid>  <native-sysroot-basedir>
>> samuel@S-Linux:/var/oe-core/setup-scripts$
>
> A fix for this problem has been committed to oe-core already. Update and
> retry
>
After i updated my oe-core files the script still won't work for me.
The new output is::
-
samuel@S-Stirtzel-Linux:/var/oe-core/setup-scripts$ runqemu
/var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin
/var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2
Set MACHINE to [qemuarm] based on kernel
[/var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin]

Continuing with the following parameters:
KERNEL: [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin]
ROOTFS: [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2]
FSTYPE: [ext2]
Setting up tap interface under sudo
[sudo] password for samuel:
Acquiring lockfile for tap0...
Error: Unable to support this combination of options
Set 'tap0' nonpersistent
Releasing lockfile of preconfigured tap device 'tap0'
-

This error was not created from the runqemu script itself.
Maybe the runqemu-initial script was expecting other options?


Regards
Samuel

Re: Error running QEMU with oe-core / angstrom console-image, hwclock: can't open '/dev/misc/rtc' : No such file or directory

[Khem Raj]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/04/2011 10:25 PM, Samuel Stirtzel wrote:
> 2011/8/4 Khem Raj <raj.khem@gmail.com>:
>> On 08/04/2011 01:08 AM, Samuel Stirtzel wrote:
>>> 
>>> 2011/8/3 Khem Raj<raj.khem@gmail.com>:
>>>> 
>>>> There is a smart script in scripts/ dir that you could use 
>>>> something like this
>>>> 
>>>> runqemu 
>>>> /var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> 
/var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2
>>>> 
>>>> and it will setup everything (even networking) for you
>>>> 
>>> Already tried this one, but for some unknown reasons it doesn't 
>>> work, I get the following output: - 
>>> samuel@S-Linux:/var/oe-core/setup-scripts$ runqemu 
>>> /var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin
>>> 
>>> /var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> 
Set MACHINE to [qemuarm] based on kernel
>>> [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin]
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> 
Continuing with the following parameters:
>>> KERNEL: 
>>> [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin]
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> 
ROOTFS:
>>> [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2]
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> 
FSTYPE: [ext2]
>>> Setting up tap interface under sudo [sudo] password for samuel: 
>>> sudo runqemu-ifup<gid>  <native-sysroot-basedir> 
>>> samuel@S-Linux:/var/oe-core/setup-scripts$
>> 
>> A fix for this problem has been committed to oe-core already. 
>> Update and retry
>> 
> After i updated my oe-core files the script still won't work for me. 
> The new output is:: - 
> samuel@S-Stirtzel-Linux:/var/oe-core/setup-scripts$ runqemu 
> /var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin 
> /var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2
>
>
>
>
>
>
>
> 
Set MACHINE to [qemuarm] based on kernel
> [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin]
> 
> Continuing with the following parameters: KERNEL: 
> [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin] 
> ROOTFS: 
> [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2]
>
>
>
>
>
>
>
> 
FSTYPE: [ext2]
> Setting up tap interface under sudo [sudo] password for samuel: 
> Acquiring lockfile for tap0... Error: Unable to support this 
> combination of options

It means QEMUOPTIONS is empty in your case because you are sing ext2
image. It supports ext3 and btrfs

but it should be easy to add ext2 to mix. Can you try something like below

diff --git a/scripts/runqemu-internal b/scripts/runqemu-internal
index c15632d..64635df 100755
- --- a/scripts/runqemu-internal
+++ b/scripts/runqemu-internal
@@ -277,7 +277,7 @@ if [ "$MACHINE" = "qemuarm" -o "$MACHINE" =
"qemuarmv6" -o "$MACHINE" = "qemuarm
     MACHINE_SUBTYPE=versatilepb
     QEMU_UI_OPTIONS="$QEMU_UI_OPTIONS"
     # QEMU_UI_OPTIONS="$QEMU_UI_OPTIONS -force-pointer"
- -    if [ "$FSTYPE" = "ext3" -o "$FSTYPE" = "btrfs" ]; then
+    if [ "$FSTYPE" = "ext3" -o "$FSTYPE" = "btrfs" -o "$FSTYPE" =
"ext2" ]; then
         KERNCMDLINE="root=/dev/sda rw console=ttyAMA0,115200
console=tty $KERNEL_NETWORK_CMD mem=$QEMU_MEMORY hi
         QEMUOPTIONS="$QEMU_NETWORK_CMD -M versatilepb -hda $ROOTFS
- -no-reboot $QEMU_UI_OPTIONS"
     fi


> Set 'tap0' nonpersistent Releasing lockfile of preconfigured tap 
> device 'tap0' -
> 
> This error was not created from the runqemu script itself. Maybe the
>  runqemu-initial script was expecting other options?
> 
> 
> Regards Samuel
> 
> _______________________________________________ Openembedded-core 
> mailing list Openembedded-core@lists.openembedded.org 
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core


- --
>
>
>
>
>
>
> 
- -Khem
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk48KVsACgkQuwUzVZGdMxSNaACffDYUHfK9qKdnYNdzCJCGr+3W
lqoAn2AFkMaezl4MLN7WbaE/zDjvu4vR
=pUFt
-----END PGP SIGNATURE-----

Re: Error running QEMU with oe-core / angstrom console-image, hwclock: can't open '/dev/misc/rtc' : No such file or directory

[Samuel Stirtzel]

2011/8/5 Khem Raj <raj.khem@gmail.com>:
> It means QEMUOPTIONS is empty in your case because you are sing ext2
> image. It supports ext3 and btrfs
>
> but it should be easy to add ext2 to mix. Can you try something like below
>
> diff --git a/scripts/runqemu-internal b/scripts/runqemu-internal
> index c15632d..64635df 100755
> - --- a/scripts/runqemu-internal
> +++ b/scripts/runqemu-internal
> @@ -277,7 +277,7 @@ if [ "$MACHINE" = "qemuarm" -o "$MACHINE" =
> "qemuarmv6" -o "$MACHINE" = "qemuarm
>     MACHINE_SUBTYPE=versatilepb
>     QEMU_UI_OPTIONS="$QEMU_UI_OPTIONS"
>     # QEMU_UI_OPTIONS="$QEMU_UI_OPTIONS -force-pointer"
> - -    if [ "$FSTYPE" = "ext3" -o "$FSTYPE" = "btrfs" ]; then
> +    if [ "$FSTYPE" = "ext3" -o "$FSTYPE" = "btrfs" -o "$FSTYPE" =
> "ext2" ]; then
>         KERNCMDLINE="root=/dev/sda rw console=ttyAMA0,115200
> console=tty $KERNEL_NETWORK_CMD mem=$QEMU_MEMORY hi
>         QEMUOPTIONS="$QEMU_NETWORK_CMD -M versatilepb -hda $ROOTFS
> - -no-reboot $QEMU_UI_OPTIONS"
>     fi
>
This patch didn't work for me, git and patch asserted that it's malformed:
-
samuel@S-Stirtzel-Linux:/var/oe-core/setup-scripts/sources/openembedded-core$
git apply /home/samuel/Downloads/runqemu-initial.diff
fatal: patch with only garbage at line 3
samuel@S-Stirtzel-Linux:/var/oe-core/setup-scripts/sources/openembedded-core$
patch -p0 < /home/samuel/Downloads/runqemu-initial.diff
patching file scripts/runqemu-internal
patch: **** malformed patch at line 6: "qemuarmv6" -o "$MACHINE" = "qemuarm
-

After I got this done, executing runqemu shows this error:
-
samuel@S-Stirtzel-Linux:/var/oe-core/setup-scripts/sources/openembedded-core$
runqemu /var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin
/var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2
Set MACHINE to [qemuarm] based on kernel
[/var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin]

Continuing with the following parameters:
KERNEL: [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin]
ROOTFS: [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2]
FSTYPE: [ext2]
Setting up tap interface under sudo
[sudo] password for samuel:
Acquiring lockfile for tap0...
/var/oe-core/setup-scripts/sources/openembedded-core/scripts/runqemu-internal:
Line 280: [: Too many arguments.
Error: Unable to support this combination of options
Set 'tap0' nonpersistent
Releasing lockfile of preconfigured tap device 'tap0'
-

Ext3 works with the script (reverted the patch), but it seems that i
can't connect my machine (host) to the internet as long as QEMU runs.
Can't try if the guest can access the internet or communicate with the
host since it looks like systemd patches broke some init related
stuff.


Regards
Samuel

Re: Error running QEMU with oe-core / angstrom console-image, hwclock: can't open '/dev/misc/rtc' : No such file or directory

[Khem Raj]

On Mon, Aug 8, 2011 at 2:27 AM, Samuel Stirtzel
<s.stirtzel@googlemail.com> wrote:
> 2011/8/5 Khem Raj <raj.khem@gmail.com>:
>> It means QEMUOPTIONS is empty in your case because you are sing ext2
>> image. It supports ext3 and btrfs
>>
>> but it should be easy to add ext2 to mix. Can you try something like below
>>
>> diff --git a/scripts/runqemu-internal b/scripts/runqemu-internal
>> index c15632d..64635df 100755
>> - --- a/scripts/runqemu-internal
>> +++ b/scripts/runqemu-internal
>> @@ -277,7 +277,7 @@ if [ "$MACHINE" = "qemuarm" -o "$MACHINE" =
>> "qemuarmv6" -o "$MACHINE" = "qemuarm
>>     MACHINE_SUBTYPE=versatilepb
>>     QEMU_UI_OPTIONS="$QEMU_UI_OPTIONS"
>>     # QEMU_UI_OPTIONS="$QEMU_UI_OPTIONS -force-pointer"
>> - -    if [ "$FSTYPE" = "ext3" -o "$FSTYPE" = "btrfs" ]; then
>> +    if [ "$FSTYPE" = "ext3" -o "$FSTYPE" = "btrfs" -o "$FSTYPE" =
>> "ext2" ]; then
>>         KERNCMDLINE="root=/dev/sda rw console=ttyAMA0,115200
>> console=tty $KERNEL_NETWORK_CMD mem=$QEMU_MEMORY hi
>>         QEMUOPTIONS="$QEMU_NETWORK_CMD -M versatilepb -hda $ROOTFS
>> - -no-reboot $QEMU_UI_OPTIONS"
>>     fi
>>
> This patch didn't work for me, git and patch asserted that it's malformed:

ofcouse it was meant to be a hint not cooked patch

> -
> samuel@S-Stirtzel-Linux:/var/oe-core/setup-scripts/sources/openembedded-core$
> git apply /home/samuel/Downloads/runqemu-initial.diff
> fatal: patch with only garbage at line 3
> samuel@S-Stirtzel-Linux:/var/oe-core/setup-scripts/sources/openembedded-core$
> patch -p0 < /home/samuel/Downloads/runqemu-initial.diff
> patching file scripts/runqemu-internal
> patch: **** malformed patch at line 6: "qemuarmv6" -o "$MACHINE" = "qemuarm
> -
>
> After I got this done, executing runqemu shows this error:
> -
> samuel@S-Stirtzel-Linux:/var/oe-core/setup-scripts/sources/openembedded-core$
> runqemu /var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin
> /var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2
> Set MACHINE to [qemuarm] based on kernel
> [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin]
>
> Continuing with the following parameters:
> KERNEL: [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin]
> ROOTFS: [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2]
> FSTYPE: [ext2]
> Setting up tap interface under sudo
> [sudo] password for samuel:
> Acquiring lockfile for tap0...
> /var/oe-core/setup-scripts/sources/openembedded-core/scripts/runqemu-internal:
> Line 280: [: Too many arguments.
> Error: Unable to support this combination of options
> Set 'tap0' nonpersistent
> Releasing lockfile of preconfigured tap device 'tap0'
> -
>
> Ext3 works with the script (reverted the patch), but it seems that i
> can't connect my machine (host) to the internet as long as QEMU runs.

Doesn't happen here where latest snapshot. I can access internet from both
guest and host equally well.

> Can't try if the guest can access the internet or communicate with the
> host since it looks like systemd patches broke some init related
> stuff.
>
>
> Regards
> Samuel
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>