On Mon, Aug 13, 2012 at 04:56:53PM +0300, Avi Kivity wrote:
> IMO we need to fix CMOS reporting.
>
> (technically we shouldn't touch CMOS NVRAM at all; seabios should
> discover memory size via fwcfg and program it itself. But it's
> pointless to change it now)
It would be nice to pass all value
On 08/14/2012 04:25 PM, Jan Kiszka wrote:
> On 2012-08-14 15:16, Avi Kivity wrote:
>> On 08/14/2012 02:01 PM, Jan Kiszka wrote:
>>
> We can also easily automatically disable it when there is insufficient
> (<1MB) memory. Will post a patch.
Would be nicer if it auto-disables itsel
On 2012-08-14 15:16, Avi Kivity wrote:
> On 08/14/2012 02:01 PM, Jan Kiszka wrote:
>
We can also easily automatically disable it when there is insufficient
(<1MB) memory. Will post a patch.
>>>
>>> Would be nicer if it auto-disables itself, but don't know if the option
>>> ROM has access
On 08/14/2012 02:12 PM, Markus Armbruster wrote:
> Avi Kivity writes:
>
>> On 08/14/2012 11:44 AM, Markus Armbruster wrote:
> [...]
>>> And another one:
>>>
>>> $ qemu-system-x86_64 -nodefaults --enable-kvm -vnc :0 -monitor
>>> stdio -m 900k
>>> QEMU 1.1.50 monitor - type 'help' for more
On 08/14/2012 02:01 PM, Jan Kiszka wrote:
>>> We can also easily automatically disable it when there is insufficient
>>> (<1MB) memory. Will post a patch.
>>
>> Would be nicer if it auto-disables itself, but don't know if the option
>> ROM has access to the memory size.
>
> There is that global
Avi Kivity writes:
> On 08/14/2012 11:44 AM, Markus Armbruster wrote:
[...]
>> And another one:
>>
>> $ qemu-system-x86_64 -nodefaults --enable-kvm -vnc :0 -monitor
>> stdio -m 900k
>> QEMU 1.1.50 monitor - type 'help' for more information
>> (qemu) KVM internal error. Suberror: 1
>>
On 2012-08-14 12:51, Avi Kivity wrote:
> On 08/14/2012 01:44 PM, Jan Kiszka wrote:
>> On 2012-08-14 12:20, Avi Kivity wrote:
>>> On 08/14/2012 11:44 AM, Markus Armbruster wrote:
Next error:
$ gdb --args qemu-system-x86_64 -nodefaults --enable-kvm -vnc :0
-monitor stdio
On 08/14/2012 01:44 PM, Jan Kiszka wrote:
> On 2012-08-14 12:20, Avi Kivity wrote:
>> On 08/14/2012 11:44 AM, Markus Armbruster wrote:
>>>
>>> Next error:
>>>
>>> $ gdb --args qemu-system-x86_64 -nodefaults --enable-kvm -vnc :0
>>> -monitor stdio -m 640k
>>> [...]
>>> Program received
On 2012-08-14 12:20, Avi Kivity wrote:
> On 08/14/2012 11:44 AM, Markus Armbruster wrote:
>>
>> Next error:
>>
>> $ gdb --args qemu-system-x86_64 -nodefaults --enable-kvm -vnc :0
>> -monitor stdio -m 640k
>> [...]
>> Program received signal SIGSEGV, Segmentation fault.
>> [...]
>>
On 08/14/2012 11:44 AM, Markus Armbruster wrote:
>
> Next error:
>
> $ gdb --args qemu-system-x86_64 -nodefaults --enable-kvm -vnc :0 -monitor
> stdio -m 640k
> [...]
> Program received signal SIGSEGV, Segmentation fault.
> [...]
> (gdb) bt
> #0 0x003b0de884ac in __m
Anthony Liguori writes:
> Markus Armbruster writes:
>
>> Avi Kivity writes:
>>
>>> On 08/08/2012 12:04 PM, Markus Armbruster wrote:
>
> Yes please, maybe with a notice to the user.
Next problem: minimum RAM size.
For instance, -M pc -m X, where X < 32KiB dies "qemu
On Mon, Aug 13, 2012 at 2:10 PM, Gleb Natapov wrote:
> On Mon, Aug 13, 2012 at 05:04:30PM +0300, Avi Kivity wrote:
>> On 08/13/2012 05:02 PM, Gleb Natapov wrote:
>>
>> >> IMO we need to fix CMOS reporting.
>> >>
>> >> (technically we shouldn't touch CMOS NVRAM at all; seabios should
>> >> discover
Anthony Liguori writes:
> Markus Armbruster writes:
>
>> Avi Kivity writes:
>>
>>> On 08/08/2012 12:04 PM, Markus Armbruster wrote:
>
> Yes please, maybe with a notice to the user.
Next problem: minimum RAM size.
For instance, -M pc -m X, where X < 32KiB dies "qemu
Markus Armbruster writes:
> Avi Kivity writes:
>
>> On 08/08/2012 12:04 PM, Markus Armbruster wrote:
Yes please, maybe with a notice to the user.
>>>
>>> Next problem: minimum RAM size.
>>>
>>> For instance, -M pc -m X, where X < 32KiB dies "qemu: fatal: Trying to
>>> execute code ou
On Mon, Aug 13, 2012 at 05:04:30PM +0300, Avi Kivity wrote:
> On 08/13/2012 05:02 PM, Gleb Natapov wrote:
>
> >> IMO we need to fix CMOS reporting.
> >>
> >> (technically we shouldn't touch CMOS NVRAM at all; seabios should
> >> discover memory size via fwcfg and program it itself. But it's
> >>
On 08/13/2012 05:02 PM, Gleb Natapov wrote:
>> IMO we need to fix CMOS reporting.
>>
>> (technically we shouldn't touch CMOS NVRAM at all; seabios should
>> discover memory size via fwcfg and program it itself. But it's
>> pointless to change it now)
>>
> Chipset we emulate does not support all
On Mon, Aug 13, 2012 at 04:56:53PM +0300, Avi Kivity wrote:
> On 08/13/2012 04:41 PM, Markus Armbruster wrote:
> > Avi Kivity writes:
> >
> >> On 08/08/2012 12:04 PM, Markus Armbruster wrote:
>
> Yes please, maybe with a notice to the user.
> >>>
> >>> Next problem: minimum RAM size.
>
On 08/13/2012 04:41 PM, Markus Armbruster wrote:
> Avi Kivity writes:
>
>> On 08/08/2012 12:04 PM, Markus Armbruster wrote:
Yes please, maybe with a notice to the user.
>>>
>>> Next problem: minimum RAM size.
>>>
>>> For instance, -M pc -m X, where X < 32KiB dies "qemu: fatal: Trying
Avi Kivity writes:
> On 08/08/2012 12:04 PM, Markus Armbruster wrote:
>>>
>>> Yes please, maybe with a notice to the user.
>>
>> Next problem: minimum RAM size.
>>
>> For instance, -M pc -m X, where X < 32KiB dies "qemu: fatal: Trying to
>> execute code outside RAM or ROM at [...] Aborted (core
Peter Maydell writes:
> On 8 August 2012 10:04, Markus Armbruster wrote:
>> Next problem: minimum RAM size.
>>
>> For instance, -M pc -m X, where X < 32KiB dies "qemu: fatal: Trying to
>> execute code outside RAM or ROM at [...] Aborted (core dumped)" with
>> TCG, and "KVM internal error. Suberr
On 08/08/2012 12:04 PM, Markus Armbruster wrote:
>>
>> Yes please, maybe with a notice to the user.
>
> Next problem: minimum RAM size.
>
> For instance, -M pc -m X, where X < 32KiB dies "qemu: fatal: Trying to
> execute code outside RAM or ROM at [...] Aborted (core dumped)" with
> TCG, and "KVM
On 8 August 2012 10:04, Markus Armbruster wrote:
> Next problem: minimum RAM size.
>
> For instance, -M pc -m X, where X < 32KiB dies "qemu: fatal: Trying to
> execute code outside RAM or ROM at [...] Aborted (core dumped)" with
> TCG, and "KVM internal error. Suberror: 1" with KVM.
>
> Should a m
Blue Swirl writes:
> On Mon, Jul 30, 2012 at 12:56 PM, Markus Armbruster wrote:
>> Blue Swirl writes:
>>
>>> On Sat, Jul 28, 2012 at 6:41 AM, Markus Armbruster
>>> wrote:
Blue Swirl writes:
> On Wed, Jul 25, 2012 at 11:49 AM, Markus Armbruster
> wrote:
>> Asking for "f
On Mon, Jul 30, 2012 at 12:56 PM, Markus Armbruster wrote:
> Blue Swirl writes:
>
>> On Sat, Jul 28, 2012 at 6:41 AM, Markus Armbruster wrote:
>>> Blue Swirl writes:
>>>
On Wed, Jul 25, 2012 at 11:49 AM, Markus Armbruster
wrote:
> Asking for "funny" memory sizes sometimes crashes
Blue Swirl writes:
> On Sat, Jul 28, 2012 at 6:41 AM, Markus Armbruster wrote:
>> Blue Swirl writes:
>>
>>> On Wed, Jul 25, 2012 at 11:49 AM, Markus Armbruster
>>> wrote:
Asking for "funny" memory sizes sometimes crashes for me. For instance
-m 0.8 or the equivalent -m 838860b. -m
On Sat, Jul 28, 2012 at 6:41 AM, Markus Armbruster wrote:
> Blue Swirl writes:
>
>> On Wed, Jul 25, 2012 at 11:49 AM, Markus Armbruster
>> wrote:
>>> Asking for "funny" memory sizes sometimes crashes for me. For instance
>>> -m 0.8 or the equivalent -m 838860b. -m 0.7 appears to work.
>>>
>>>
Blue Swirl writes:
> On Wed, Jul 25, 2012 at 11:49 AM, Markus Armbruster wrote:
>> Asking for "funny" memory sizes sometimes crashes for me. For instance
>> -m 0.8 or the equivalent -m 838860b. -m 0.7 appears to work.
>>
>> Should we round memory sizes? How? Where?
>
> We had a discussion ab
On Wed, Jul 25, 2012 at 11:49 AM, Markus Armbruster wrote:
> Asking for "funny" memory sizes sometimes crashes for me. For instance
> -m 0.8 or the equivalent -m 838860b. -m 0.7 appears to work.
>
> Should we round memory sizes? How? Where?
We had a discussion about this recently:
http://list
Asking for "funny" memory sizes sometimes crashes for me. For instance
-m 0.8 or the equivalent -m 838860b. -m 0.7 appears to work.
Should we round memory sizes? How? Where?
$ gdb --args qemu-system-x86_64 -nodefaults --enable-kvm -S -vnc :0 -monitor
stdio -m 0.8
[...]
(gdb) r
Starting pro
29 matches
Mail list logo
