On 02/21/2014 04:25 PM, Aneesh Kumar K.V wrote:
> Alexander Graf writes:
>
>>
>>> The second bug is kind of interesting. If you add ~ 256 disks (using
>>> virtio-scsi), then it looks as if the firmware crashes. The total
>>> console output is below. It looks as if "c >" is some kind of prompt.
Hi Anthony,
Can you please merge it before 1.4 soft feature freeze?
Regaqrds,
Avik
On 01/08/2013 12:36 PM, Avik Sil wrote:
> Hi,
>
> This patch series allows a machine to specify if it wants a default boot
> order or not.
>
> Regards,
> Avik
>
> Changes v2 -> v
boots from the devices as set in
guest's non-volatile memory location in case no boot order is
provided by the user.
Reviewed-by: Anthony Liguori
Signed-off-by: Avik Sil
---
hw/alpha_dp264.c | 1 +
hw/an5206.c | 1 +
hw/axis_dev88.c | 1 +
h
t order for every machine
- Remove default boot order for pseries
Avik Sil (2):
Make default boot order machine specific
pseries: set no default boot order
hw/alpha_dp264.c | 1 +
hw/an5206.c | 1 +
hw/axis_dev88.c | 1 +
hw/boards.h
device set in the nvram.
Reviewed-by: Anthony Liguori
Signed-off-by: Avik Sil
---
hw/spapr.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/hw/spapr.c b/hw/spapr.c
index a4a65c7..abfa0d9 100644
--- a/hw/spapr.c
+++ b/hw/spapr.c
@@ -284,7 +284,9 @@ static void
boots from the devices as set in
guest's non-volatile memory location in case no boot order is
provided by the user.
Signed-off-by: Avik Sil
---
hw/alpha_dp264.c | 1 +
hw/an5206.c | 1 +
hw/axis_dev88.c | 1 +
hw/boards.h |
device set in the nvram.
Signed-off-by: Avik Sil
---
hw/spapr.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/hw/spapr.c b/hw/spapr.c
index a4a65c7..abfa0d9 100644
--- a/hw/spapr.c
+++ b/hw/spapr.c
@@ -284,7 +284,9 @@ static void *spapr_create_fdt_skel(const char
t order for every machine
- Remove default boot order for pseries
Avik Sil (2):
Make default boot order machine specific
pseries: set no default boot order
hw/alpha_dp264.c | 1 +
hw/an5206.c | 1 +
hw/axis_dev88.c | 1 +
hw/boards.h
On 10/26/2012 05:15 PM, Alexander Graf wrote:
>
> On 25.10.2012, at 22:57, Alexander Graf wrote:
>
>>
>> On 25.10.2012, at 22:50, Peter Maydell wrote:
>>
>>> On 25 October 2012 21:18, Anthony Liguori wrote:
The other approach to this would be:
static QEMUMachine pseries_machine =
On 11/23/2012 10:22 PM, Alexander Graf wrote:
>
> On 05.11.2012, at 12:34, Avik Sil wrote:
>
>> On 10/26/2012 05:15 PM, Alexander Graf wrote:
>>>
>>> On 25.10.2012, at 22:57, Alexander Graf wrote:
>>>
>>>>
>>>> On 25.10.2012,
On 10/26/2012 05:15 PM, Alexander Graf wrote:
>
> On 25.10.2012, at 22:57, Alexander Graf wrote:
>
>>
>> On 25.10.2012, at 22:50, Peter Maydell wrote:
>>
>>> On 25 October 2012 21:18, Anthony Liguori wrote:
The other approach to this would be:
static QEMUMachine pseries_machine =
isn't used and take an appropriate action accordingly. This
helps machine boots from the devices as set in guest's non-volatile
memory location in case no boot order is provided by the user.
Signed-off-by: Avik Sil
---
hw/alpha_dp264.c | 1 +
hw/an5206.c
der for every machine
- Remove default boot order for pseries
Avik Sil (2):
Make default boot order machine specific
pseries: set no default boot order
hw/alpha_dp264.c | 1 +
hw/an5206.c | 1 +
hw/axis_dev88.c | 1 +
hw/board
device set in the nvram.
Signed-off-by: Avik Sil
---
hw/spapr.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/hw/spapr.c b/hw/spapr.c
index 57db710..6f5be50 100644
--- a/hw/spapr.c
+++ b/hw/spapr.c
@@ -283,7 +283,9 @@ static void *spapr_create_fdt_skel(const char
On 10/24/2012 04:15 AM, David Gibson wrote:
> On Tue, Oct 23, 2012 at 03:39:35PM +0530, Avik Sil wrote:
>> Signed-off-by: Avik Sil
>
> As Anthony suggests, it would be better to explicitly remove the
> normal default boot order in this patch, after adding it for
> absolut
On 10/24/2012 05:13 AM, David Gibson wrote:
> On Wed, Oct 24, 2012 at 12:47:34AM +0200, Alexander Graf wrote:
>>
>> On 24.10.2012, at 00:43, David Gibson wrote:
>>
>>> On Tue, Oct 23, 2012 at 12:20:08PM +0200, Alexander Graf wrote:
>>>>
>>>> On
isn't used and take an appropriate action accordingly. This
helps machine boots from the devices as set in guest's non-volatile
memory location in case no boot order is provided by the user.
Signed-off-by: Avik Sil
---
hw/nseries.c | 2 ++
hw/pc_piix.c | 13 +++
Signed-off-by: Avik Sil
---
hw/spapr.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/hw/spapr.c b/hw/spapr.c
index 637b3fb..1b2340c 100644
--- a/hw/spapr.c
+++ b/hw/spapr.c
@@ -283,7 +283,9 @@ static void *spapr_create_fdt_skel(const char *cpu_model,
_FDT
Hi,
This patch series implements requirement 1 of the mailing list discussion [1],
i.e., to allow a machine to specify if it wants a default boot order or not.
Comments are welcome.
Regards,
Avik
[1] http://lists.nongnu.org/archive/html/qemu-devel/2012-10/msg02799.html
Avik Sil (2):
Make
> On Thu, Oct 11, 2012 at 07:34:42AM +0530, Avik Sil wrote:
>>>>>> This patch adds nvram specified boot device into qemu default
>>>>>> boot_devices list. This helps firmware to boot from nvram specified
>>>>>> boot device if no -bo
On 10/12/2012 05:33 AM, Alexander Graf wrote:
>
> On 12.10.2012, at 00:59, David Gibson wrote:
>
>> On Thu, Oct 11, 2012 at 07:34:42AM +0530, Avik Sil wrote:
>>> This patch adds nvram specified boot device into qemu default
>>> boot_devices list. This helps firm
On 10/12/2012 04:29 AM, David Gibson wrote:
> On Thu, Oct 11, 2012 at 07:34:42AM +0530, Avik Sil wrote:
>> This patch adds nvram specified boot device into qemu default
>> boot_devices list. This helps firmware to boot from nvram specified
>> boot device if no -boot option
This patch adds nvram specified boot device into qemu default
boot_devices list. This helps firmware to boot from nvram specified
boot device if no -boot option is specified.
Suggested by: Alexander Graf
Signed-off-by: Avik Sil
---
vl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion
I looked at the bootindex stuff and found that when the bootindex is
specified for the disk and cdrom it generates a string like:
"/spapr-vio-bridge/spapr-vscsi/channel@0/disk@0,1
/spapr-vio-bridge/spapr-vscsi/channel@0/disk@0,0"
Ok, so I've just started looking at the bootindex stuff. What
fu
On 09/27/2012 03:21 PM, Gleb Natapov wrote:
On Thu, Sep 27, 2012 at 11:33:31AM +0200, Alexander Graf wrote:
On 27.09.2012, at 11:29, Benjamin Herrenschmidt wrote:
On Thu, 2012-09-27 at 14:51 +0530, Avik Sil wrote:
Hi,
We would like to get a method to boot from devices provided in -boot
I looked at the bootindex stuff and found that when the bootindex is
specified for the disk and cdrom it generates a string like:
"/spapr-vio-bridge/spapr-vscsi/channel@0/disk@0,1
/spapr-vio-bridge/spapr-vscsi/channel@0/disk@0,0"
Now converting/translating this to OF device path is going to be
m
So you want to hack around the problem. If -boot is specified what
device are you going to boot from?
It is going to boot from the device specified in -boot as default_boot_order is
set to 0 in that case.
Imagine you have 2 controllers:
* vio
* virtio
and you specify -boot c. Which de
I looked at the bootindex stuff and found that when the bootindex is
specified for the disk and cdrom it generates a string like:
"/spapr-vio-bridge/spapr-vscsi/channel@0/disk@0,1
/spapr-vio-bridge/spapr-vscsi/channel@0/disk@0,0"
Now converting/translating this to OF device path is going to be
m
On 10/04/2012 04:52 PM, Gleb Natapov wrote:
On Thu, Oct 04, 2012 at 04:25:28PM +0530, Avik Sil wrote:
On 09/27/2012 03:21 PM, Gleb Natapov wrote:
On Thu, Sep 27, 2012 at 11:33:31AM +0200, Alexander Graf wrote:
On 27.09.2012, at 11:29, Benjamin Herrenschmidt wrote:
On Thu, 2012-09-27 at 14
29 matches
Mail list logo
