* [Qemu-devel] [Bug 1243287] Re: [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
[not found] <20131022162416.15428.47621.malonedeb@soybean.canonical.com>
@ 2013-10-30 16:10 ` Manoj Iyer
2013-10-30 16:11 ` [Qemu-devel] [Bug 1243287] [NEW] " Launchpad Bug Tracker
` (17 subsequent siblings)
18 siblings, 0 replies; 19+ messages in thread
From: Manoj Iyer @ 2013-10-30 16:10 UTC (permalink / raw)
To: qemu-devel
** Summary changed:
- [cloud-init][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
+ [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
** Project changed: cloud-init => qemu
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1243287
Title:
[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
Status in QEMU:
New
Bug description:
On booting the cloud image using qemu/kvm fails with the following
error:
Cloud-init v. 0.7.3 running 'init' at Thu, 03 Oct 2013 16:45:21 +0000. Up 360.78 seconds.
ci-info: +++++++++++++++++++++++++Net device info+++++++++++++++++++++++++
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | Device | Up | Address | Mask | Hw-Address |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . |
ci-info: | eth0 | True | 10.0.2.15 | 255.255.255.0 | 52:54:00:12:34:56 |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: ++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | 0 | 0.0.0.0 | 10.0.2.2 | 0.0.0.0 | eth0 | UG |
ci-info: | 1 | 10.0.2.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
error: kvm run failed Function not implemented
/usr/lib/python2.7/dist-
packages/cloudinit/sources/DataSourceAltCloud.py assumes that
dmidecode command is availabe (ie it assumes that system is x86) on
arm systems there is no dmidecode command so host kvm fails with the
message "error: kvm run failed Function not implemented"
The patch makes get_cloud_type() function return with UNKNOWN for ARM
systems.
I was able to boot the cloud-image on ARM after applying this change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1243287/+subscriptions
^ permalink raw reply [flat|nested] 19+ messages in thread* [Qemu-devel] [Bug 1243287] [NEW] [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
[not found] <20131022162416.15428.47621.malonedeb@soybean.canonical.com>
2013-10-30 16:10 ` [Qemu-devel] [Bug 1243287] Re: [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail Manoj Iyer
@ 2013-10-30 16:11 ` Launchpad Bug Tracker
2013-10-30 16:19 ` [Qemu-devel] [Bug 1243287] " Manoj Iyer
` (16 subsequent siblings)
18 siblings, 0 replies; 19+ messages in thread
From: Launchpad Bug Tracker @ 2013-10-30 16:11 UTC (permalink / raw)
To: qemu-devel
You have been subscribed to a public bug:
On booting the cloud image using qemu/kvm fails with the following
error:
Cloud-init v. 0.7.3 running 'init' at Thu, 03 Oct 2013 16:45:21 +0000. Up 360.78 seconds.
ci-info: +++++++++++++++++++++++++Net device info+++++++++++++++++++++++++
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | Device | Up | Address | Mask | Hw-Address |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . |
ci-info: | eth0 | True | 10.0.2.15 | 255.255.255.0 | 52:54:00:12:34:56 |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: ++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | 0 | 0.0.0.0 | 10.0.2.2 | 0.0.0.0 | eth0 | UG |
ci-info: | 1 | 10.0.2.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
error: kvm run failed Function not implemented
/usr/lib/python2.7/dist-packages/cloudinit/sources/DataSourceAltCloud.py
assumes that dmidecode command is availabe (ie it assumes that system is
x86) on arm systems there is no dmidecode command so host kvm fails with
the message "error: kvm run failed Function not implemented"
The patch makes get_cloud_type() function return with UNKNOWN for ARM
systems.
I was able to boot the cloud-image on ARM after applying this change.
** Affects: qemu
Importance: Undecided
Status: New
--
[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
https://bugs.launchpad.net/bugs/1243287
You received this bug notification because you are a member of qemu-devel-ml, which is subscribed to QEMU.
^ permalink raw reply [flat|nested] 19+ messages in thread* [Qemu-devel] [Bug 1243287] Re: [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
[not found] <20131022162416.15428.47621.malonedeb@soybean.canonical.com>
2013-10-30 16:10 ` [Qemu-devel] [Bug 1243287] Re: [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail Manoj Iyer
2013-10-30 16:11 ` [Qemu-devel] [Bug 1243287] [NEW] " Launchpad Bug Tracker
@ 2013-10-30 16:19 ` Manoj Iyer
2013-11-08 17:39 ` Manoj Iyer
` (15 subsequent siblings)
18 siblings, 0 replies; 19+ messages in thread
From: Manoj Iyer @ 2013-10-30 16:19 UTC (permalink / raw)
To: qemu-devel
Ubuntu kernels use CONFIG_STRICT_MEM which prevents access to physical
mem other than BIOS and PCI region so that X or dmidecode tools can read
this info. On a native ARM system since there is no BIOS (yet) this
causes mmap() of /dev/mem to return a -1. But with KVM/QEMU emulating
ARM (mach virt) on native ARM, mmap() /dev/mem does not return a -1 but
returns a valid address (or what looks like a valid address). Could it
be that kvm/qemu is not passing protections correctly for phy mem ?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1243287
Title:
[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
Status in QEMU:
New
Bug description:
On booting the cloud image using qemu/kvm fails with the following
error:
Cloud-init v. 0.7.3 running 'init' at Thu, 03 Oct 2013 16:45:21 +0000. Up 360.78 seconds.
ci-info: +++++++++++++++++++++++++Net device info+++++++++++++++++++++++++
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | Device | Up | Address | Mask | Hw-Address |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . |
ci-info: | eth0 | True | 10.0.2.15 | 255.255.255.0 | 52:54:00:12:34:56 |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: ++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | 0 | 0.0.0.0 | 10.0.2.2 | 0.0.0.0 | eth0 | UG |
ci-info: | 1 | 10.0.2.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
error: kvm run failed Function not implemented
/usr/lib/python2.7/dist-
packages/cloudinit/sources/DataSourceAltCloud.py assumes that
dmidecode command is availabe (ie it assumes that system is x86) on
arm systems there is no dmidecode command so host kvm fails with the
message "error: kvm run failed Function not implemented"
The patch makes get_cloud_type() function return with UNKNOWN for ARM
systems.
I was able to boot the cloud-image on ARM after applying this change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1243287/+subscriptions
^ permalink raw reply [flat|nested] 19+ messages in thread* [Qemu-devel] [Bug 1243287] Re: [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
[not found] <20131022162416.15428.47621.malonedeb@soybean.canonical.com>
` (2 preceding siblings ...)
2013-10-30 16:19 ` [Qemu-devel] [Bug 1243287] " Manoj Iyer
@ 2013-11-08 17:39 ` Manoj Iyer
2013-11-08 19:10 ` Peter Maydell
` (14 subsequent siblings)
18 siblings, 0 replies; 19+ messages in thread
From: Manoj Iyer @ 2013-11-08 17:39 UTC (permalink / raw)
To: qemu-devel
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1243287
Title:
[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
Status in QEMU:
Confirmed
Bug description:
On booting the cloud image using qemu/kvm fails with the following
error:
Cloud-init v. 0.7.3 running 'init' at Thu, 03 Oct 2013 16:45:21 +0000. Up 360.78 seconds.
ci-info: +++++++++++++++++++++++++Net device info+++++++++++++++++++++++++
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | Device | Up | Address | Mask | Hw-Address |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . |
ci-info: | eth0 | True | 10.0.2.15 | 255.255.255.0 | 52:54:00:12:34:56 |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: ++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | 0 | 0.0.0.0 | 10.0.2.2 | 0.0.0.0 | eth0 | UG |
ci-info: | 1 | 10.0.2.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
error: kvm run failed Function not implemented
/usr/lib/python2.7/dist-
packages/cloudinit/sources/DataSourceAltCloud.py assumes that
dmidecode command is availabe (ie it assumes that system is x86) on
arm systems there is no dmidecode command so host kvm fails with the
message "error: kvm run failed Function not implemented"
The patch makes get_cloud_type() function return with UNKNOWN for ARM
systems.
I was able to boot the cloud-image on ARM after applying this change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1243287/+subscriptions
^ permalink raw reply [flat|nested] 19+ messages in thread* [Qemu-devel] [Bug 1243287] Re: [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
[not found] <20131022162416.15428.47621.malonedeb@soybean.canonical.com>
` (3 preceding siblings ...)
2013-11-08 17:39 ` Manoj Iyer
@ 2013-11-08 19:10 ` Peter Maydell
2013-11-08 20:01 ` Andreas Färber
` (13 subsequent siblings)
18 siblings, 0 replies; 19+ messages in thread
From: Peter Maydell @ 2013-11-08 19:10 UTC (permalink / raw)
To: qemu-devel
(1) If you are trying to mmap /dev/mem then you are going to be
accessing physical addresses. This is obviously totally board specific.
In particular the memory layout between a Midway system and a KVM
virtual machine is likely to be different (you don't say what QEMU
configuration you're using) so it is unsurprising that looking at
/dev/mem address zero gives different effects between the host and the
VM. If dmidecode wants to access physical address space it needs to be
aware of the physical memory layout of every board it might run on (and
that is an enormous range of systems for ARM).
(2) The guest kernel has sufficient privilege to cause kvm to exit (the
easiest way it can do this is to do something that KVM doesn't support,
such as trying to access emulated devices via LDM/STM or some other
"complex" instruction). If you let your guest userspace open /dev/mem it
has equivalent privilege and can do the same thing (again, by trying LDM
on device MMIO space)
(3) My kernel sources don't have any references to CONFIG_STRICT_MEM,
and the only two google hits are references back to this bug report, so
I'm not sure what this is.
My best guess is that there are two underlying bugs here:
a. CONFIG_STRICT_MEM (whatever that is) either doesn't work with ARM or doesn't work with KVM or doesn't work with KVM/ARM
b. dmidecode is making bad assumptions about the physical memory layout of the machine it is running on and needs to be fixed somehow (what does it think is the actual data it is copying out of physical memory??)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1243287
Title:
[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
Status in QEMU:
Confirmed
Bug description:
On booting the cloud image using qemu/kvm fails with the following
error:
Cloud-init v. 0.7.3 running 'init' at Thu, 03 Oct 2013 16:45:21 +0000. Up 360.78 seconds.
ci-info: +++++++++++++++++++++++++Net device info+++++++++++++++++++++++++
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | Device | Up | Address | Mask | Hw-Address |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . |
ci-info: | eth0 | True | 10.0.2.15 | 255.255.255.0 | 52:54:00:12:34:56 |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: ++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | 0 | 0.0.0.0 | 10.0.2.2 | 0.0.0.0 | eth0 | UG |
ci-info: | 1 | 10.0.2.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
error: kvm run failed Function not implemented
/usr/lib/python2.7/dist-
packages/cloudinit/sources/DataSourceAltCloud.py assumes that
dmidecode command is availabe (ie it assumes that system is x86) on
arm systems there is no dmidecode command so host kvm fails with the
message "error: kvm run failed Function not implemented"
The patch makes get_cloud_type() function return with UNKNOWN for ARM
systems.
I was able to boot the cloud-image on ARM after applying this change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1243287/+subscriptions
^ permalink raw reply [flat|nested] 19+ messages in thread* [Qemu-devel] [Bug 1243287] Re: [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
[not found] <20131022162416.15428.47621.malonedeb@soybean.canonical.com>
` (4 preceding siblings ...)
2013-11-08 19:10 ` Peter Maydell
@ 2013-11-08 20:01 ` Andreas Färber
2013-11-11 15:45 ` Peter Maydell
` (12 subsequent siblings)
18 siblings, 0 replies; 19+ messages in thread
From: Andreas Färber @ 2013-11-08 20:01 UTC (permalink / raw)
To: qemu-devel
Manoj, dmidecode seems highly x86-specific according to http://www.nongnu.org/dmidecode/, so not running it on arm does seem a correct solution for closing this bug. Suggest you assign it back to cloud-init to have that fixed.
An alternative to checking for the command's presence would be checking uname or whatever Python offers as equivalent.
What do you expect to read from 0xf0000 to 0xfffff on your arm mach-virt
guest? I suggest you file a separate bug report more understandable to
QEMU/KVM developers if there's a valid use case failing, along with
versions, command line and anything else needed for someone to actually
investigate this beyond speculation.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1243287
Title:
[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
Status in QEMU:
Confirmed
Bug description:
On booting the cloud image using qemu/kvm fails with the following
error:
Cloud-init v. 0.7.3 running 'init' at Thu, 03 Oct 2013 16:45:21 +0000. Up 360.78 seconds.
ci-info: +++++++++++++++++++++++++Net device info+++++++++++++++++++++++++
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | Device | Up | Address | Mask | Hw-Address |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . |
ci-info: | eth0 | True | 10.0.2.15 | 255.255.255.0 | 52:54:00:12:34:56 |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: ++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | 0 | 0.0.0.0 | 10.0.2.2 | 0.0.0.0 | eth0 | UG |
ci-info: | 1 | 10.0.2.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
error: kvm run failed Function not implemented
/usr/lib/python2.7/dist-
packages/cloudinit/sources/DataSourceAltCloud.py assumes that
dmidecode command is availabe (ie it assumes that system is x86) on
arm systems there is no dmidecode command so host kvm fails with the
message "error: kvm run failed Function not implemented"
The patch makes get_cloud_type() function return with UNKNOWN for ARM
systems.
I was able to boot the cloud-image on ARM after applying this change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1243287/+subscriptions
^ permalink raw reply [flat|nested] 19+ messages in thread* [Qemu-devel] [Bug 1243287] Re: [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
[not found] <20131022162416.15428.47621.malonedeb@soybean.canonical.com>
` (5 preceding siblings ...)
2013-11-08 20:01 ` Andreas Färber
@ 2013-11-11 15:45 ` Peter Maydell
2013-11-14 14:20 ` Andre Przywara
` (11 subsequent siblings)
18 siblings, 0 replies; 19+ messages in thread
From: Peter Maydell @ 2013-11-11 15:45 UTC (permalink / raw)
To: qemu-devel
dmidecode itself should probably be checking at runtime what cpu
architecture it is running on so it can refuse to read /dev/mem on
systems which it doesn't know it understands.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1243287
Title:
[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
Status in QEMU:
Confirmed
Bug description:
On booting the cloud image using qemu/kvm fails with the following
error:
Cloud-init v. 0.7.3 running 'init' at Thu, 03 Oct 2013 16:45:21 +0000. Up 360.78 seconds.
ci-info: +++++++++++++++++++++++++Net device info+++++++++++++++++++++++++
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | Device | Up | Address | Mask | Hw-Address |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . |
ci-info: | eth0 | True | 10.0.2.15 | 255.255.255.0 | 52:54:00:12:34:56 |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: ++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | 0 | 0.0.0.0 | 10.0.2.2 | 0.0.0.0 | eth0 | UG |
ci-info: | 1 | 10.0.2.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
error: kvm run failed Function not implemented
/usr/lib/python2.7/dist-
packages/cloudinit/sources/DataSourceAltCloud.py assumes that
dmidecode command is availabe (ie it assumes that system is x86) on
arm systems there is no dmidecode command so host kvm fails with the
message "error: kvm run failed Function not implemented"
The patch makes get_cloud_type() function return with UNKNOWN for ARM
systems.
I was able to boot the cloud-image on ARM after applying this change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1243287/+subscriptions
^ permalink raw reply [flat|nested] 19+ messages in thread* [Qemu-devel] [Bug 1243287] Re: [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
[not found] <20131022162416.15428.47621.malonedeb@soybean.canonical.com>
` (6 preceding siblings ...)
2013-11-11 15:45 ` Peter Maydell
@ 2013-11-14 14:20 ` Andre Przywara
2013-11-14 14:30 ` Peter Maydell
` (10 subsequent siblings)
18 siblings, 0 replies; 19+ messages in thread
From: Andre Przywara @ 2013-11-14 14:20 UTC (permalink / raw)
To: qemu-devel
Peter, the config option is called: CONFIG_STRICT_DEVMEM
And /dev/mem behaves differently between doing read() and doing mmap().
As Peter already hinted, the memory layout is different on native Midway (which has DRAM starting at 0) and mach-virt/vexpress (which start at 128MB / 2GB respectively). So accessing 0xf0000 reads memory on native, but faults in stage 2 mapping in the host kernel.
But the actual problem is that the host kernel passes this abort on to userspace, where QEMU just does abort(), thus crashing the whole virtual machine. Actually I think we should change the host kernel to inject the data abort into the guest. I tested this with a simple patch, it now makes dmidecode crash (due to a signal), but keeps the guest alive.
This approach needs some discussion on the ML, I guess.
But near term we should not call dmidecode on ARM, since AFAIK it does
not give any information. There once was a discussion on patching
dmidecode to output hardcoded or elsewhere gathered information to make
scripts happy, but I don't know where this ended.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1243287
Title:
[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
Status in QEMU:
Confirmed
Bug description:
On booting the cloud image using qemu/kvm fails with the following
error:
Cloud-init v. 0.7.3 running 'init' at Thu, 03 Oct 2013 16:45:21 +0000. Up 360.78 seconds.
ci-info: +++++++++++++++++++++++++Net device info+++++++++++++++++++++++++
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | Device | Up | Address | Mask | Hw-Address |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . |
ci-info: | eth0 | True | 10.0.2.15 | 255.255.255.0 | 52:54:00:12:34:56 |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: ++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | 0 | 0.0.0.0 | 10.0.2.2 | 0.0.0.0 | eth0 | UG |
ci-info: | 1 | 10.0.2.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
error: kvm run failed Function not implemented
/usr/lib/python2.7/dist-
packages/cloudinit/sources/DataSourceAltCloud.py assumes that
dmidecode command is availabe (ie it assumes that system is x86) on
arm systems there is no dmidecode command so host kvm fails with the
message "error: kvm run failed Function not implemented"
The patch makes get_cloud_type() function return with UNKNOWN for ARM
systems.
I was able to boot the cloud-image on ARM after applying this change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1243287/+subscriptions
^ permalink raw reply [flat|nested] 19+ messages in thread* [Qemu-devel] [Bug 1243287] Re: [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
[not found] <20131022162416.15428.47621.malonedeb@soybean.canonical.com>
` (7 preceding siblings ...)
2013-11-14 14:20 ` Andre Przywara
@ 2013-11-14 14:30 ` Peter Maydell
2014-02-25 18:31 ` Manoj Iyer
` (9 subsequent siblings)
18 siblings, 0 replies; 19+ messages in thread
From: Peter Maydell @ 2013-11-14 14:30 UTC (permalink / raw)
To: qemu-devel
I agree we should probably make KVM inject a data abort here. That
doesn't change the fact that a userspace program that looks in /dev/mem
without being 100% sure what hardware it is running on is really
dangerous and needs to be fixed.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1243287
Title:
[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
Status in QEMU:
Confirmed
Bug description:
On booting the cloud image using qemu/kvm fails with the following
error:
Cloud-init v. 0.7.3 running 'init' at Thu, 03 Oct 2013 16:45:21 +0000. Up 360.78 seconds.
ci-info: +++++++++++++++++++++++++Net device info+++++++++++++++++++++++++
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | Device | Up | Address | Mask | Hw-Address |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . |
ci-info: | eth0 | True | 10.0.2.15 | 255.255.255.0 | 52:54:00:12:34:56 |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: ++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | 0 | 0.0.0.0 | 10.0.2.2 | 0.0.0.0 | eth0 | UG |
ci-info: | 1 | 10.0.2.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
error: kvm run failed Function not implemented
/usr/lib/python2.7/dist-
packages/cloudinit/sources/DataSourceAltCloud.py assumes that
dmidecode command is availabe (ie it assumes that system is x86) on
arm systems there is no dmidecode command so host kvm fails with the
message "error: kvm run failed Function not implemented"
The patch makes get_cloud_type() function return with UNKNOWN for ARM
systems.
I was able to boot the cloud-image on ARM after applying this change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1243287/+subscriptions
^ permalink raw reply [flat|nested] 19+ messages in thread* [Qemu-devel] [Bug 1243287] Re: [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
[not found] <20131022162416.15428.47621.malonedeb@soybean.canonical.com>
` (8 preceding siblings ...)
2013-11-14 14:30 ` Peter Maydell
@ 2014-02-25 18:31 ` Manoj Iyer
2014-02-25 18:54 ` Peter Maydell
` (8 subsequent siblings)
18 siblings, 0 replies; 19+ messages in thread
From: Manoj Iyer @ 2014-02-25 18:31 UTC (permalink / raw)
To: qemu-devel
A workaround that we used was to rename dmidecode to /bin/true and .make
it persistent. dpkg-divert --local --divert /path/dmidecode --rename
--add /bin/true. But that is just a workaround, any code that maps()
/dev/mem can cause these crashes. Is there a fix for this in the horizon
?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1243287
Title:
[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
Status in QEMU:
Confirmed
Bug description:
On booting the cloud image using qemu/kvm fails with the following
error:
Cloud-init v. 0.7.3 running 'init' at Thu, 03 Oct 2013 16:45:21 +0000. Up 360.78 seconds.
ci-info: +++++++++++++++++++++++++Net device info+++++++++++++++++++++++++
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | Device | Up | Address | Mask | Hw-Address |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . |
ci-info: | eth0 | True | 10.0.2.15 | 255.255.255.0 | 52:54:00:12:34:56 |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: ++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | 0 | 0.0.0.0 | 10.0.2.2 | 0.0.0.0 | eth0 | UG |
ci-info: | 1 | 10.0.2.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
error: kvm run failed Function not implemented
/usr/lib/python2.7/dist-
packages/cloudinit/sources/DataSourceAltCloud.py assumes that
dmidecode command is availabe (ie it assumes that system is x86) on
arm systems there is no dmidecode command so host kvm fails with the
message "error: kvm run failed Function not implemented"
The patch makes get_cloud_type() function return with UNKNOWN for ARM
systems.
I was able to boot the cloud-image on ARM after applying this change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1243287/+subscriptions
^ permalink raw reply [flat|nested] 19+ messages in thread* [Qemu-devel] [Bug 1243287] Re: [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
[not found] <20131022162416.15428.47621.malonedeb@soybean.canonical.com>
` (9 preceding siblings ...)
2014-02-25 18:31 ` Manoj Iyer
@ 2014-02-25 18:54 ` Peter Maydell
2014-02-26 19:28 ` Launchpad Bug Tracker
` (7 subsequent siblings)
18 siblings, 0 replies; 19+ messages in thread
From: Peter Maydell @ 2014-02-25 18:54 UTC (permalink / raw)
To: qemu-devel
The most recent mailing list discussion about the problem is here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2013-December/219176.html
It does not look likely that there will be a fix soon: it's complicated
(and the suggestion to inject a data abort has been rejected), and it
only affects broken guest code which has direct access to /dev/mem.
You should get dmidecode and any other similarly broken guest binaries
fixed.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1243287
Title:
[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
Status in QEMU:
Confirmed
Bug description:
On booting the cloud image using qemu/kvm fails with the following
error:
Cloud-init v. 0.7.3 running 'init' at Thu, 03 Oct 2013 16:45:21 +0000. Up 360.78 seconds.
ci-info: +++++++++++++++++++++++++Net device info+++++++++++++++++++++++++
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | Device | Up | Address | Mask | Hw-Address |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . |
ci-info: | eth0 | True | 10.0.2.15 | 255.255.255.0 | 52:54:00:12:34:56 |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: ++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | 0 | 0.0.0.0 | 10.0.2.2 | 0.0.0.0 | eth0 | UG |
ci-info: | 1 | 10.0.2.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
error: kvm run failed Function not implemented
/usr/lib/python2.7/dist-
packages/cloudinit/sources/DataSourceAltCloud.py assumes that
dmidecode command is availabe (ie it assumes that system is x86) on
arm systems there is no dmidecode command so host kvm fails with the
message "error: kvm run failed Function not implemented"
The patch makes get_cloud_type() function return with UNKNOWN for ARM
systems.
I was able to boot the cloud-image on ARM after applying this change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1243287/+subscriptions
^ permalink raw reply [flat|nested] 19+ messages in thread* [Qemu-devel] [Bug 1243287] Re: [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
[not found] <20131022162416.15428.47621.malonedeb@soybean.canonical.com>
` (10 preceding siblings ...)
2014-02-25 18:54 ` Peter Maydell
@ 2014-02-26 19:28 ` Launchpad Bug Tracker
2014-02-26 19:44 ` Scott Moser
` (6 subsequent siblings)
18 siblings, 0 replies; 19+ messages in thread
From: Launchpad Bug Tracker @ 2014-02-26 19:28 UTC (permalink / raw)
To: qemu-devel
** Branch linked: lp:cloud-init
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1243287
Title:
[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
Status in QEMU:
Confirmed
Bug description:
On booting the cloud image using qemu/kvm fails with the following
error:
Cloud-init v. 0.7.3 running 'init' at Thu, 03 Oct 2013 16:45:21 +0000. Up 360.78 seconds.
ci-info: +++++++++++++++++++++++++Net device info+++++++++++++++++++++++++
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | Device | Up | Address | Mask | Hw-Address |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . |
ci-info: | eth0 | True | 10.0.2.15 | 255.255.255.0 | 52:54:00:12:34:56 |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: ++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | 0 | 0.0.0.0 | 10.0.2.2 | 0.0.0.0 | eth0 | UG |
ci-info: | 1 | 10.0.2.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
error: kvm run failed Function not implemented
/usr/lib/python2.7/dist-
packages/cloudinit/sources/DataSourceAltCloud.py assumes that
dmidecode command is availabe (ie it assumes that system is x86) on
arm systems there is no dmidecode command so host kvm fails with the
message "error: kvm run failed Function not implemented"
The patch makes get_cloud_type() function return with UNKNOWN for ARM
systems.
I was able to boot the cloud-image on ARM after applying this change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1243287/+subscriptions
^ permalink raw reply [flat|nested] 19+ messages in thread* [Qemu-devel] [Bug 1243287] Re: [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
[not found] <20131022162416.15428.47621.malonedeb@soybean.canonical.com>
` (11 preceding siblings ...)
2014-02-26 19:28 ` Launchpad Bug Tracker
@ 2014-02-26 19:44 ` Scott Moser
2014-02-26 21:05 ` Peter Maydell
` (5 subsequent siblings)
18 siblings, 0 replies; 19+ messages in thread
From: Scott Moser @ 2014-02-26 19:44 UTC (permalink / raw)
To: qemu-devel
I just worked around this in cloud-init by disabling the smartOS datasource if the uname arch is arm* or aarch*
http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/sources/DataSourceSmartOS.py
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1243287
Title:
[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
Status in QEMU:
Confirmed
Bug description:
On booting the cloud image using qemu/kvm fails with the following
error:
Cloud-init v. 0.7.3 running 'init' at Thu, 03 Oct 2013 16:45:21 +0000. Up 360.78 seconds.
ci-info: +++++++++++++++++++++++++Net device info+++++++++++++++++++++++++
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | Device | Up | Address | Mask | Hw-Address |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . |
ci-info: | eth0 | True | 10.0.2.15 | 255.255.255.0 | 52:54:00:12:34:56 |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: ++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | 0 | 0.0.0.0 | 10.0.2.2 | 0.0.0.0 | eth0 | UG |
ci-info: | 1 | 10.0.2.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
error: kvm run failed Function not implemented
/usr/lib/python2.7/dist-
packages/cloudinit/sources/DataSourceAltCloud.py assumes that
dmidecode command is availabe (ie it assumes that system is x86) on
arm systems there is no dmidecode command so host kvm fails with the
message "error: kvm run failed Function not implemented"
The patch makes get_cloud_type() function return with UNKNOWN for ARM
systems.
I was able to boot the cloud-image on ARM after applying this change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1243287/+subscriptions
^ permalink raw reply [flat|nested] 19+ messages in thread* [Qemu-devel] [Bug 1243287] Re: [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
[not found] <20131022162416.15428.47621.malonedeb@soybean.canonical.com>
` (12 preceding siblings ...)
2014-02-26 19:44 ` Scott Moser
@ 2014-02-26 21:05 ` Peter Maydell
2014-02-26 22:35 ` Manoj Iyer
` (4 subsequent siblings)
18 siblings, 0 replies; 19+ messages in thread
From: Peter Maydell @ 2014-02-26 21:05 UTC (permalink / raw)
To: qemu-devel
"uname not i386 or x86_64" might be a better check -- restrict to the
archs where it actually works.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1243287
Title:
[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
Status in QEMU:
Confirmed
Bug description:
On booting the cloud image using qemu/kvm fails with the following
error:
Cloud-init v. 0.7.3 running 'init' at Thu, 03 Oct 2013 16:45:21 +0000. Up 360.78 seconds.
ci-info: +++++++++++++++++++++++++Net device info+++++++++++++++++++++++++
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | Device | Up | Address | Mask | Hw-Address |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . |
ci-info: | eth0 | True | 10.0.2.15 | 255.255.255.0 | 52:54:00:12:34:56 |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: ++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | 0 | 0.0.0.0 | 10.0.2.2 | 0.0.0.0 | eth0 | UG |
ci-info: | 1 | 10.0.2.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
error: kvm run failed Function not implemented
/usr/lib/python2.7/dist-
packages/cloudinit/sources/DataSourceAltCloud.py assumes that
dmidecode command is availabe (ie it assumes that system is x86) on
arm systems there is no dmidecode command so host kvm fails with the
message "error: kvm run failed Function not implemented"
The patch makes get_cloud_type() function return with UNKNOWN for ARM
systems.
I was able to boot the cloud-image on ARM after applying this change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1243287/+subscriptions
^ permalink raw reply [flat|nested] 19+ messages in thread* [Qemu-devel] [Bug 1243287] Re: [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
[not found] <20131022162416.15428.47621.malonedeb@soybean.canonical.com>
` (13 preceding siblings ...)
2014-02-26 21:05 ` Peter Maydell
@ 2014-02-26 22:35 ` Manoj Iyer
2014-02-27 0:40 ` Ben Howard
` (3 subsequent siblings)
18 siblings, 0 replies; 19+ messages in thread
From: Manoj Iyer @ 2014-02-26 22:35 UTC (permalink / raw)
To: qemu-devel
Is there something we can do for ARM32 cloud-images so that customers
who might download the image and try to deploy it will not see this
issue? Something like:
dpkg-divert --local --divert /path/dmidecode --rename --add /bin/true
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1243287
Title:
[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
Status in QEMU:
Confirmed
Bug description:
On booting the cloud image using qemu/kvm fails with the following
error:
Cloud-init v. 0.7.3 running 'init' at Thu, 03 Oct 2013 16:45:21 +0000. Up 360.78 seconds.
ci-info: +++++++++++++++++++++++++Net device info+++++++++++++++++++++++++
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | Device | Up | Address | Mask | Hw-Address |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . |
ci-info: | eth0 | True | 10.0.2.15 | 255.255.255.0 | 52:54:00:12:34:56 |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: ++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | 0 | 0.0.0.0 | 10.0.2.2 | 0.0.0.0 | eth0 | UG |
ci-info: | 1 | 10.0.2.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
error: kvm run failed Function not implemented
/usr/lib/python2.7/dist-
packages/cloudinit/sources/DataSourceAltCloud.py assumes that
dmidecode command is availabe (ie it assumes that system is x86) on
arm systems there is no dmidecode command so host kvm fails with the
message "error: kvm run failed Function not implemented"
The patch makes get_cloud_type() function return with UNKNOWN for ARM
systems.
I was able to boot the cloud-image on ARM after applying this change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1243287/+subscriptions
^ permalink raw reply [flat|nested] 19+ messages in thread* [Qemu-devel] [Bug 1243287] Re: [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
[not found] <20131022162416.15428.47621.malonedeb@soybean.canonical.com>
` (14 preceding siblings ...)
2014-02-26 22:35 ` Manoj Iyer
@ 2014-02-27 0:40 ` Ben Howard
2014-02-27 1:36 ` Manoj Iyer
` (2 subsequent siblings)
18 siblings, 0 replies; 19+ messages in thread
From: Ben Howard @ 2014-02-27 0:40 UTC (permalink / raw)
To: qemu-devel
Manoj, the fix that Scott just put through should fix it. However, I've
gone ahead and put in a fix for the cloud image build process. I would
really like to see this fix though in dmidecode.
** Changed in: qemu
Assignee: (unassigned) => Ben Howard (utlemming)
** Changed in: qemu
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1243287
Title:
[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
Status in QEMU:
Fix Committed
Bug description:
On booting the cloud image using qemu/kvm fails with the following
error:
Cloud-init v. 0.7.3 running 'init' at Thu, 03 Oct 2013 16:45:21 +0000. Up 360.78 seconds.
ci-info: +++++++++++++++++++++++++Net device info+++++++++++++++++++++++++
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | Device | Up | Address | Mask | Hw-Address |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . |
ci-info: | eth0 | True | 10.0.2.15 | 255.255.255.0 | 52:54:00:12:34:56 |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: ++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | 0 | 0.0.0.0 | 10.0.2.2 | 0.0.0.0 | eth0 | UG |
ci-info: | 1 | 10.0.2.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
error: kvm run failed Function not implemented
/usr/lib/python2.7/dist-
packages/cloudinit/sources/DataSourceAltCloud.py assumes that
dmidecode command is availabe (ie it assumes that system is x86) on
arm systems there is no dmidecode command so host kvm fails with the
message "error: kvm run failed Function not implemented"
The patch makes get_cloud_type() function return with UNKNOWN for ARM
systems.
I was able to boot the cloud-image on ARM after applying this change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1243287/+subscriptions
^ permalink raw reply [flat|nested] 19+ messages in thread* [Qemu-devel] [Bug 1243287] Re: [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
[not found] <20131022162416.15428.47621.malonedeb@soybean.canonical.com>
` (15 preceding siblings ...)
2014-02-27 0:40 ` Ben Howard
@ 2014-02-27 1:36 ` Manoj Iyer
2014-03-03 22:00 ` Launchpad Bug Tracker
2016-03-17 23:04 ` Ben Howard
18 siblings, 0 replies; 19+ messages in thread
From: Manoj Iyer @ 2014-02-27 1:36 UTC (permalink / raw)
To: qemu-devel
I did send a patch for dmidecode to exit gracefully if there is no bios
or smbus before it did all the mmap() damage, but no one seemed
interested in that patch. I was told that upstream is working on a
different approach.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1243287
Title:
[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
Status in QEMU:
Fix Committed
Bug description:
On booting the cloud image using qemu/kvm fails with the following
error:
Cloud-init v. 0.7.3 running 'init' at Thu, 03 Oct 2013 16:45:21 +0000. Up 360.78 seconds.
ci-info: +++++++++++++++++++++++++Net device info+++++++++++++++++++++++++
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | Device | Up | Address | Mask | Hw-Address |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . |
ci-info: | eth0 | True | 10.0.2.15 | 255.255.255.0 | 52:54:00:12:34:56 |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: ++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | 0 | 0.0.0.0 | 10.0.2.2 | 0.0.0.0 | eth0 | UG |
ci-info: | 1 | 10.0.2.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
error: kvm run failed Function not implemented
/usr/lib/python2.7/dist-
packages/cloudinit/sources/DataSourceAltCloud.py assumes that
dmidecode command is availabe (ie it assumes that system is x86) on
arm systems there is no dmidecode command so host kvm fails with the
message "error: kvm run failed Function not implemented"
The patch makes get_cloud_type() function return with UNKNOWN for ARM
systems.
I was able to boot the cloud-image on ARM after applying this change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1243287/+subscriptions
^ permalink raw reply [flat|nested] 19+ messages in thread* [Qemu-devel] [Bug 1243287] Re: [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
[not found] <20131022162416.15428.47621.malonedeb@soybean.canonical.com>
` (16 preceding siblings ...)
2014-02-27 1:36 ` Manoj Iyer
@ 2014-03-03 22:00 ` Launchpad Bug Tracker
2016-03-17 23:04 ` Ben Howard
18 siblings, 0 replies; 19+ messages in thread
From: Launchpad Bug Tracker @ 2014-03-03 22:00 UTC (permalink / raw)
To: qemu-devel
** Branch linked: lp:ubuntu/cloud-init
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1243287
Title:
[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
Status in QEMU:
Fix Committed
Bug description:
On booting the cloud image using qemu/kvm fails with the following
error:
Cloud-init v. 0.7.3 running 'init' at Thu, 03 Oct 2013 16:45:21 +0000. Up 360.78 seconds.
ci-info: +++++++++++++++++++++++++Net device info+++++++++++++++++++++++++
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | Device | Up | Address | Mask | Hw-Address |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . |
ci-info: | eth0 | True | 10.0.2.15 | 255.255.255.0 | 52:54:00:12:34:56 |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: ++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | 0 | 0.0.0.0 | 10.0.2.2 | 0.0.0.0 | eth0 | UG |
ci-info: | 1 | 10.0.2.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
error: kvm run failed Function not implemented
/usr/lib/python2.7/dist-
packages/cloudinit/sources/DataSourceAltCloud.py assumes that
dmidecode command is availabe (ie it assumes that system is x86) on
arm systems there is no dmidecode command so host kvm fails with the
message "error: kvm run failed Function not implemented"
The patch makes get_cloud_type() function return with UNKNOWN for ARM
systems.
I was able to boot the cloud-image on ARM after applying this change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1243287/+subscriptions
^ permalink raw reply [flat|nested] 19+ messages in thread* [Qemu-devel] [Bug 1243287] Re: [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
[not found] <20131022162416.15428.47621.malonedeb@soybean.canonical.com>
` (17 preceding siblings ...)
2014-03-03 22:00 ` Launchpad Bug Tracker
@ 2016-03-17 23:04 ` Ben Howard
18 siblings, 0 replies; 19+ messages in thread
From: Ben Howard @ 2016-03-17 23:04 UTC (permalink / raw)
To: qemu-devel
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1243287
Title:
[KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
Status in QEMU:
Fix Released
Bug description:
On booting the cloud image using qemu/kvm fails with the following
error:
Cloud-init v. 0.7.3 running 'init' at Thu, 03 Oct 2013 16:45:21 +0000. Up 360.78 seconds.
ci-info: +++++++++++++++++++++++++Net device info+++++++++++++++++++++++++
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | Device | Up | Address | Mask | Hw-Address |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . |
ci-info: | eth0 | True | 10.0.2.15 | 255.255.255.0 | 52:54:00:12:34:56 |
ci-info: +--------+------+-----------+---------------+-------------------+
ci-info: ++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
ci-info: | 0 | 0.0.0.0 | 10.0.2.2 | 0.0.0.0 | eth0 | UG |
ci-info: | 1 | 10.0.2.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U |
ci-info: +-------+-------------+----------+---------------+-----------+-------+
error: kvm run failed Function not implemented
/usr/lib/python2.7/dist-
packages/cloudinit/sources/DataSourceAltCloud.py assumes that
dmidecode command is availabe (ie it assumes that system is x86) on
arm systems there is no dmidecode command so host kvm fails with the
message "error: kvm run failed Function not implemented"
The patch makes get_cloud_type() function return with UNKNOWN for ARM
systems.
I was able to boot the cloud-image on ARM after applying this change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1243287/+subscriptions
^ permalink raw reply [flat|nested] 19+ messages in thread