Ian/Lennart,
Just a quick update - been busy and haven't had much of a chance to work
on it. But I wanted to update you before I hit the hay - you've been so
much help.
I tried adding mmci to the modules list and rebuilding initrd. The
result was a kernel panic. No command line to check status
On Mon, 2016-11-14 at 23:13 -0500, Jerry Stuckle wrote:
>
> Everything I've found on the internet indicates the -sd parameter should
> be all I need, but it doesn't work. Any ideas here?
The armmp kernel flavour works on many different platforms and is
therefore more modular than the old vexpres
OK, the problem here is I'm not able to mount the disk. Nothing I do
causes it to show up in /dev. I'm using
qemu-system-arm -M vexpress-a9 \
-cpu cortex-a9 \
-m 1024M \
-kernel /export/armmp/vmlinuz \
-initrd /export/armmp/initrd.g
Lennart,
Bingo! The virtual serial port (on 3, btw) showed the system trying to
boot. An error pointed out that in this iteration I had forgotten the
-sd parameter, so no (virtual) hard disk.
I added -sd /export/armhf.qcow2 to the command, but still no hard disk
in the /dev listing. I'm wonder
On Mon, Nov 14, 2016 at 02:48:24PM -0500, Jerry Stuckle wrote:
> I have tried with your command:
>
> qemu-system-arm -M vexpress-a9 \
> -cpu cortex-a9 \
> -kernel /export/armmp/vmlinuz \
> -initrd /export/armmp/initrd.gz \
> -append c
Ian,
I have tried with your command:
qemu-system-arm -M vexpress-a9 \
-cpu cortex-a9 \
-kernel /export/armmp/vmlinuz \
-initrd /export/armmp/initrd.gz \
-append console=ttyAMA0,115200 \
-dtb /export/armmp/vexpress-v2p
On Mon, 2016-11-14 at 12:46 -0500, Jerry Stuckle wrote:
> Hi, Ian,
>
> I tried several variations with different DTBs, and nothing worked. I
> also tried your example, with no difference. All I get is an empty console.
Please tell us the actual commands which you have tried to run.
Ian.
Hi, Ian,
I tried several variations with different DTBs, and nothing worked. I
also tried your example, with no difference. All I get is an empty console.
My initrd.gz is a symlink to initrd.img-3.16.0-4-armmp and vmlinuz is a
symlink to vmlinuz-3.16.0-4-armmp, which I think are the correct fil
On Sun, 2016-11-13 at 21:39 -0500, Jerry Stuckle wrote:
> Boot only gave me an empty window. No messages, nothing. I had to
> force close the machine.
You need the DTB too. /usr/lib/linux-image-3.16.0-4-armmp should
contain vexpress-v2p-ca9.dtb which seems like the one you want (but
there are ot
Hi, Ian,
Sorry for the delay - I'm really confused now.
Yes, the vmlinuz and initrd are loaded off the local machine - but these
are the same copies that are in the /boot directory on the Debian guest.
I would have thought those were updated when I upgraded Debian.
In any case - I looked for an
On Sat, 2016-11-12 at 16:16 -0500, Jerry Stuckle wrote:
> Ian,
>
> That's interesting, because when I do lsb_release-a returns
>
> No LSB modules are available.
> Distribution ID: Debian
> Description: Debian GNU/Linux 8.6 (jessie)
> Release: 8.6
> Codename:Jessie
>
> /etc/ap
Ian,
That's interesting, because when I do lsb_release-a returns
No LSB modules are available.
Distribution ID: Debian
Description: Debian GNU/Linux 8.6 (jessie)
Release: 8.6
Codename:Jessie
/etc/apt/sources.list entries all point at stable, which should be
jessie, I think.
On Sat, 2016-11-12 at 10:22 -0500, Jerry Stuckle wrote:
> Ian,
>
> Thanks for clarifying this - I misunderstood your previous statement
> and
> thought it was the Wheezy kernel which supported virtio and not
> Jessie.
>
> However, I am already running Jessie.
The logs you posted earlier contain:
Ian,
Thanks for clarifying this - I misunderstood your previous statement and
thought it was the Wheezy kernel which supported virtio and not Jessie.
However, I am already running Jessie. The only non-PCI nic QEMU
supports for a bridge is the virtio_device. The one used for SLIRP is
not an opti
On Fri, 2016-11-11 at 20:05 -0500, Jerry Stuckle wrote:
> Ian,
>
> Thanks much for the info.
>
> I find it interesting that the virtio options for vexpress would require
> PCI, since the vexpress architecture doesn't support PCI.
IIRC there was _no_ option to support virtio on any platform witho
Ian,
Thanks much for the info.
I find it interesting that the virtio options for vexpress would require
PCI, since the vexpress architecture doesn't support PCI.
Unfortunately, I guess that means we can't use Debian, as I really need
to get the virtualization working. I'll be traveling over the
On Fri, 2016-11-11 at 11:55 -0500, Jerry Stuckle wrote:
> Hi, Ian, and thanks again for your time.
>
> No, this is an armhf kernel, installed from
> debian-7.1.0-armhf-netinst.iso (and updated). It does not include PCI
> support (neither does hardware) and trying to use virtio-net-pci returns
> a
Hi, Ian, and thanks again for your time.
No, this is an armhf kernel, installed from
debian-7.1.0-armhf-netinst.iso (and updated). It does not include PCI
support (neither does hardware) and trying to use virtio-net-pci returns
a message about PCI not found (which it isn't).
I could try somethin
On Fri, 2016-11-11 at 14:38 +, Mark Morgan Lloyd wrote:
> On 11/11/16 08:00, Ian Campbell wrote:
> >
> > On Wed, 2016-11-09 at 08:18 -0500, Jerry Stuckle wrote:
> > >
> > > Again, I appreciate any insight you can provide.
> >
> > Looks like you are using the armel vexpress kernel, which AFAI
On 11/11/16 08:00, Ian Campbell wrote:
On Wed, 2016-11-09 at 08:18 -0500, Jerry Stuckle wrote:
Again, I appreciate any insight you can provide.
Looks like you are using the armel vexpress kernel, which AFAICT
includes PCI based virtio support, unlike most other ARM configurations
which include
On Wed, 2016-11-09 at 08:18 -0500, Jerry Stuckle wrote:
> Again, I appreciate any insight you can provide.
Looks like you are using the armel vexpress kernel, which AFAICT
includes PCI based virtio support, unlike most other ARM configurations
which include the MMIO (discovered via DTB or ACPI) va
On Wed, Nov 09, 2016 at 08:18:06AM -0500, Jerry Stuckle wrote:
> Hi, Ian,
>
> Sorry for the delay and not posting to the listserv - my mistake.
>
> The entire qemu command line is:
>
> qemu-system-arm -m 1024M \
> -sd /export/armhf.qcow2 \
> -M vexpress-a9 \
> -cpu cortex-a9 \
> -kernel /export/
On 11/8/2016 9:16 AM, Ian Campbell wrote:
> On Tue, 2016-11-08 at 08:51 -0500, Jerry Stuckle wrote:
>> Any other ideas?
>
> I'm at a bit of a loss, maybe someone else has some bright ideas.
>
> A few bits of info whic might jolt someones memory:
>
> What is your full qemu command line for the wo
On 11/8/2016 4:25 PM, Mark Morgan Lloyd wrote:
> On 08/11/16 21:00, Jerry Stuckle wrote:
>
>> Thanks for the input. There are no error messages from QEMU, and the
>> console status looks good. I started out with this on the QEMU mailing
>> list, but after lots of looking, people basically threw
On 08/11/16 21:00, Jerry Stuckle wrote:
Thanks for the input. There are no error messages from QEMU, and the
console status looks good. I started out with this on the QEMU mailing
list, but after lots of looking, people basically threw up their hands.
At this point it doesn't *look* like a QEM
On Tue, Nov 8, 2016 at 3:20 AM, Ian Campbell wrote:
> On Mon, 2016-11-07 at 22:57 -0500, Jerry Stuckle wrote:
>> The only odd thing I see in the syslog at startup are lines indicating
>> eth0 is not found.
>
> Wild stab in the dark: Perhaps things have remembered the mac address
> of the original
Re,
On Tue, Nov 08, 2016 at 02:27:30PM -0500, Lennart Sorensen wrote:
[...]
> > Could you try with another macadress ?
> >
> > Here (on amd64, though), sometimes qemu doesn't like some macadress,
> > dunno why...
> >
> > The tool 'macchanger' can create a valid one.
>
> I tried with that mac
On Tue, Nov 08, 2016 at 06:29:38PM +0100, JF Straeten wrote:
> Hi,
>
> On Tue, Nov 08, 2016 at 09:51:37AM -0500, Lennart Sorensen wrote:
>
> [...]
> > > If I don't specify any nic, QEMU supplies a default which is
> > > accepted by Debian. However, when I specify a virtio-net-device
> > > (so I c
Hi,
On Tue, Nov 08, 2016 at 09:51:37AM -0500, Lennart Sorensen wrote:
[...]
> > If I don't specify any nic, QEMU supplies a default which is
> > accepted by Debian. However, when I specify a virtio-net-device
> > (so I can bridge to the host nic), I get no nic.
[...]
> > -netdev
> > -bridge,br=
On 08/11/16 14:30, Ian Campbell wrote:
On Tue, 2016-11-08 at 08:51 -0500, Jerry Stuckle wrote:
Any other ideas?
I'm at a bit of a loss, maybe someone else has some bright ideas.
A few bits of info whic might jolt someones memory:
I can't usefully help, since while I use Qemu for various tar
On Mon, Nov 07, 2016 at 10:57:29PM -0500, Jerry Stuckle wrote:
> Hi, all,
>
> I'm trying to get Debian armhf (jessie) running under qemu-system-arm.
> It's working OK except for one point.
>
> If I don't specify any nic, QEMU supplies a default which is accepted by
> Debian. However, when I spec
On Tue, 2016-11-08 at 08:51 -0500, Jerry Stuckle wrote:
> Any other ideas?
I'm at a bit of a loss, maybe someone else has some bright ideas.
A few bits of info whic might jolt someones memory:
What is your full qemu command line for the working case (with the
default nic) and non-working cases?
On 11/8/2016 3:20 AM, Ian Campbell wrote:
> On Mon, 2016-11-07 at 22:57 -0500, Jerry Stuckle wrote:
>> The only odd thing I see in the syslog at startup are lines indicating
>> eth0 is not found.
>
> Wild stab in the dark: Perhaps things have remembered the mac address
> of the original (automatic
On 08/11/16 09:30, Ian Campbell wrote:
On Tue, 2016-11-08 at 08:42 +, Mark Morgan Lloyd wrote:
Does "ifconfig -a" (as root) show the virtio device with some name
other than eth0? If so then you might need to edit
/etc/udev/rules.d/70-persistent-net.rules to cause it to forget the
old
device.
On Tue, 2016-11-08 at 08:42 +, Mark Morgan Lloyd wrote:
> > Does "ifconfig -a" (as root) show the virtio device with some name
> > other than eth0? If so then you might need to edit
> > /etc/udev/rules.d/70-persistent-net.rules to cause it to forget the
> > old
> > device.
>
> Is that file sti
On 08/11/16 08:30, Ian Campbell wrote:
On Mon, 2016-11-07 at 22:57 -0500, Jerry Stuckle wrote:
The only odd thing I see in the syslog at startup are lines indicating
eth0 is not found.
Wild stab in the dark: Perhaps things have remembered the mac address
of the original (automatically added) d
On Mon, 2016-11-07 at 22:57 -0500, Jerry Stuckle wrote:
> The only odd thing I see in the syslog at startup are lines indicating
> eth0 is not found.
Wild stab in the dark: Perhaps things have remembered the mac address
of the original (automatically added) device as eth0 and so the virtio
device
Hi, all,
I'm trying to get Debian armhf (jessie) running under qemu-system-arm.
It's working OK except for one point.
If I don't specify any nic, QEMU supplies a default which is accepted by
Debian. However, when I specify a virtio-net-device (so I can bridge to
the host nic), I get no nic.
The
38 matches
Mail list logo
