On Thu, 15 Aug 2019 18:24:53 +0200
Paolo Bonzini wrote:
> On 15/08/19 18:07, Igor Mammedov wrote:
> > Looking at Q35 code and Seabios SMM relocation as example, if I see it
> > right QEMU has:
> > - SMRAM is aliased from DRAM at 0xa
> > - and TSEG steals from the top of low RAM when c
On 15/08/19 18:07, Igor Mammedov wrote:
> Looking at Q35 code and Seabios SMM relocation as example, if I see it
> right QEMU has:
> - SMRAM is aliased from DRAM at 0xa
> - and TSEG steals from the top of low RAM when configured
>
> Now problem is that default SMBASE at 0x3 isn't b
On Wed, 14 Aug 2019 16:04:50 +0200
Paolo Bonzini wrote:
> On 14/08/19 15:20, Yao, Jiewen wrote:
> >> - Does this part require a new branch somewhere in the OVMF SEC code?
> >> How do we determine whether the CPU executing SEC is BSP or
> >> hot-plugged AP?
> > [Jiewen] I think this is block
On 15/08/19 11:55, Yao, Jiewen wrote:
> Hi Paolo
> I am not sure what do you mean - "You do not need a reset vector ...".
> If so, where is the first instruction of the new CPU in the virtualization
> environment?
> Please help me understand that at first. Then we can continue the discussion.
The
Hi Paolo
I am not sure what do you mean - "You do not need a reset vector ...".
If so, where is the first instruction of the new CPU in the virtualization
environment?
Please help me understand that at first. Then we can continue the discussion.
Thank you
Yao Jiewen
> -Original Message-
On 14/08/19 15:20, Yao, Jiewen wrote:
>> - Does this part require a new branch somewhere in the OVMF SEC code?
>> How do we determine whether the CPU executing SEC is BSP or
>> hot-plugged AP?
> [Jiewen] I think this is blocked from hardware perspective, since the first
> instruction.
> There
My comments below.
> -Original Message-
> From: Laszlo Ersek [mailto:ler...@redhat.com]
> Sent: Wednesday, August 14, 2019 12:09 AM
> To: edk2-devel-groups-io
> Cc: edk2-rfc-groups-io ; qemu devel list
> ; Igor Mammedov ;
> Paolo Bonzini ; Yao, Jiewen
> ; Chen, Yingwen ;
> Nakajima, Jun ;
On 08/13/19 18:09, Laszlo Ersek wrote:
> On 08/13/19 16:16, Laszlo Ersek wrote:
>> (06) Host CPU: (SMM) Save 38000, Update 38000 -- fill simple SMM
>> rebase code.
>>
>> (07) Host CPU: (SMM) Send message to New CPU to Enable SMI.
>
> Aha, so this is the SMM-only register you mention in step
On 08/13/19 16:16, Laszlo Ersek wrote:
> Yingwen and Jiewen suggested the following process.
>
> Legend:
>
> - "New CPU": CPU being hot-added
> - "Host CPU": existing CPU
> - (Flash):code running from flash
> - (SMM): code running from SMRAM
>
> Steps:
>
> (01) New CPU: (Flash) enter res
Hi,
this message is a problem statement, and an initial recommendation for
solving it, from Jiewen, Paolo, Yingwen, and others. I'm cross-posting
the thread starter to the ,
and lists. Please use "Reply All" when
commenting.
In response to the initial posting, I plan to ask a number of question
Hi Cedric,
On Wed, 2017-07-12 at 19:19 +0200, Cédric Le Goater wrote:
> Hi,
>
> Today, if you try to hotplug a CPU on a POWER9 guest (TCG), it fails
> with an assert on the LPCR_UPRT bit missing in
> ppc_radix64_handle_mmu_fault()
>
> (qemu) device_add POWER9_v1.0-spapr-cpu-core,core-id=4,id=
Hi,
Today, if you try to hotplug a CPU on a POWER9 guest (TCG), it fails
with an assert on the LPCR_UPRT bit missing in ppc_radix64_handle_mmu_fault()
(qemu) device_add POWER9_v1.0-spapr-cpu-core,core-id=4,id=foo
(qemu) [ 12.766102] pseries-hotplug-cpu: Attempting to add CPU, drc index:
1
On Thu, 22 Dec 2016 10:40:29 +0100
Eduardo Otubo wrote:
> Hi guys,
>
> I'm just trying Qemu 2.7 and 2.8 and Windows 2016 as guest and cpu
> hotplug doesn't seem to be working. CPU appears on qemu device tree, but
> doesn't appear inside the guest (nor control panel, performance monitor
> or devi
Hi guys,
I'm just trying Qemu 2.7 and 2.8 and Windows 2016 as guest and cpu
hotplug doesn't seem to be working. CPU appears on qemu device tree, but
doesn't appear inside the guest (nor control panel, performance monitor
or device manager)
Anyone going through this?
--
Eduardo Otubo
ProfitBrick
On Thu, 25 Feb 2016 17:41:14 +1100
David Gibson wrote:
> On Wed, Feb 24, 2016 at 02:41:17PM +0100, Igor Mammedov wrote:
> > On Wed, 24 Feb 2016 22:28:22 +1100
> > David Gibson wrote:
> >
> > > On Wed, Feb 24, 2016 at 11:48:33AM +0100, Igor Mammedov wrote:
> > > > On Wed, 24 Feb 2016 13:01:0
On Wed, Feb 24, 2016 at 02:41:17PM +0100, Igor Mammedov wrote:
> On Wed, 24 Feb 2016 22:28:22 +1100
> David Gibson wrote:
>
> > On Wed, Feb 24, 2016 at 11:48:33AM +0100, Igor Mammedov wrote:
> > > On Wed, 24 Feb 2016 13:01:06 +1100
> > > David Gibson wrote:
> > >
> > > > On Tue, Feb 23, 2016
On Wed, 24 Feb 2016 22:28:22 +1100
David Gibson wrote:
> On Wed, Feb 24, 2016 at 11:48:33AM +0100, Igor Mammedov wrote:
> > On Wed, 24 Feb 2016 13:01:06 +1100
> > David Gibson wrote:
> >
> > > On Tue, Feb 23, 2016 at 12:18:59PM +0100, Igor Mammedov wrote:
> > > > On Tue, 23 Feb 2016 21:05:0
On Wed, Feb 24, 2016 at 11:48:33AM +0100, Igor Mammedov wrote:
> On Wed, 24 Feb 2016 13:01:06 +1100
> David Gibson wrote:
>
> > On Tue, Feb 23, 2016 at 12:18:59PM +0100, Igor Mammedov wrote:
> > > On Tue, 23 Feb 2016 21:05:04 +1100
> > > David Gibson wrote:
> > >
> > > > On Tue, Feb 23, 2016
On Wed, 24 Feb 2016 13:01:06 +1100
David Gibson wrote:
> On Tue, Feb 23, 2016 at 12:18:59PM +0100, Igor Mammedov wrote:
> > On Tue, 23 Feb 2016 21:05:04 +1100
> > David Gibson wrote:
> >
> > > On Tue, Feb 23, 2016 at 03:10:26PM +0530, Bharata B Rao wrote:
> > > > On Tue, Feb 23, 2016 at 04:
On Wed, Feb 24, 2016 at 01:01:06PM +1100, David Gibson wrote:
> On Tue, Feb 23, 2016 at 12:18:59PM +0100, Igor Mammedov wrote:
> > On Tue, 23 Feb 2016 21:05:04 +1100
> > David Gibson wrote:
> >
> > > On Tue, Feb 23, 2016 at 03:10:26PM +0530, Bharata B Rao wrote:
> > > > On Tue, Feb 23, 2016 at 04
On Tue, Feb 23, 2016 at 12:18:59PM +0100, Igor Mammedov wrote:
> On Tue, 23 Feb 2016 21:05:04 +1100
> David Gibson wrote:
>
> > On Tue, Feb 23, 2016 at 03:10:26PM +0530, Bharata B Rao wrote:
> > > On Tue, Feb 23, 2016 at 04:24:31PM +1100, David Gibson wrote:
> > > > Hi Andreas,
> > > >
> > > >
On Tue, 23 Feb 2016 21:05:04 +1100
David Gibson wrote:
> On Tue, Feb 23, 2016 at 03:10:26PM +0530, Bharata B Rao wrote:
> > On Tue, Feb 23, 2016 at 04:24:31PM +1100, David Gibson wrote:
> > > Hi Andreas,
> > >
> > > I've now found (with Thomas' help) your RFC series for socket/core
> > > based
On Tue, Feb 23, 2016 at 03:10:26PM +0530, Bharata B Rao wrote:
>
> 5) QOM-links
>
> Andreas, You have often talked about setting up links from machine object
> to the CPU objects. Would the below code correctly capture that idea of
> yours ?
>
> #define SPAPR_MACHINE_CPU_CORE_PROP "core"
>
> /*
On Tue, Feb 23, 2016 at 03:10:26PM +0530, Bharata B Rao wrote:
> On Tue, Feb 23, 2016 at 04:24:31PM +1100, David Gibson wrote:
> > Hi Andreas,
> >
> > I've now found (with Thomas' help) your RFC series for socket/core
> > based cpu hotplug on x86
> > (https://github.com/afaerber/qemu-cpu/compare/q
On Tue, Feb 23, 2016 at 04:24:31PM +1100, David Gibson wrote:
> Hi Andreas,
>
> I've now found (with Thomas' help) your RFC series for socket/core
> based cpu hotplug on x86
> (https://github.com/afaerber/qemu-cpu/compare/qom-cpu-x86). It seems
> sensible enough as far as it goes, but doesn't see
Hi Andreas,
I've now found (with Thomas' help) your RFC series for socket/core
based cpu hotplug on x86
(https://github.com/afaerber/qemu-cpu/compare/qom-cpu-x86). It seems
sensible enough as far as it goes, but doesn't seem to address a bunch
of the things that I was attempting to do with the cp
On Wed, Feb 03, 2016 at 12:50:02PM +1100, David Gibson wrote:
> On Tue, Feb 02, 2016 at 04:33:27PM -0200, Eduardo Habkost wrote:
> > On Mon, Feb 01, 2016 at 04:35:17PM +1100, David Gibson wrote:
> > > Hi,
> > >
> > > It seems to me we're getting rather bogged down in how to proceed with
> > > an i
On Wed, Feb 03, 2016 at 10:33:48AM +0530, Bharata B Rao wrote:
> On Mon, Feb 01, 2016 at 04:35:17PM +1100, David Gibson wrote:
> > Hi,
> >
> > It seems to me we're getting rather bogged down in how to proceed with
> > an improved CPU hotplug (and hot unplug) interface, both generically
> > and for
On Mon, Feb 01, 2016 at 04:35:17PM +1100, David Gibson wrote:
> Hi,
>
> It seems to me we're getting rather bogged down in how to proceed with
> an improved CPU hotplug (and hot unplug) interface, both generically
> and for ppc in particular.
>
> So here's a somewhat more concrete suggestion of a
On Tue, Feb 02, 2016 at 04:33:27PM -0200, Eduardo Habkost wrote:
> On Mon, Feb 01, 2016 at 04:35:17PM +1100, David Gibson wrote:
> > Hi,
> >
> > It seems to me we're getting rather bogged down in how to proceed with
> > an improved CPU hotplug (and hot unplug) interface, both generically
> > and f
On Mon, Feb 01, 2016 at 04:35:17PM +1100, David Gibson wrote:
> Hi,
>
> It seems to me we're getting rather bogged down in how to proceed with
> an improved CPU hotplug (and hot unplug) interface, both generically
> and for ppc in particular.
>
> So here's a somewhat more concrete suggestion of a
On 02/01/2016 06:35 AM, David Gibson wrote:
> Hi,
>
> It seems to me we're getting rather bogged down in how to proceed with
> an improved CPU hotplug (and hot unplug) interface, both generically
> and for ppc in particular.
Yes, s390 also needs this.
Can you add Matthew in any cpu hotplug discu
Hi,
It seems to me we're getting rather bogged down in how to proceed with
an improved CPU hotplug (and hot unplug) interface, both generically
and for ppc in particular.
So here's a somewhat more concrete suggestion of a way forward, to see
if we can get some consensus.
The biggest difficulty I
use ? standard or datacenter
?)
Thanks for your help!
Regards,
Alexandre
- Mail original -
De: "Andrey Korolyov"
À: "aderumier"
Cc: "qemu-devel"
Envoyé: Mercredi 21 Janvier 2015 00:16:45
Objet: Re: [Qemu-devel] cpu hotplug and windows guest (win2012r2)
On Tue, Jan 20, 2015 at 10:06 PM, Alexandre DERUMIER
wrote:
> Hi,
>
> I have tried with numa enabled, and it's still don't work.
> Can you send me your vm qemu command line ?
>
>
> Also, with numa I have notice something strange with "info numa" command.
>
> starting with -smp socket=2,cores=1
>
>
size: 2048 MB
cpu1 has been hotplugged on numa node0 ??
- Mail original -
De: "Andrey Korolyov"
À: "aderumier"
Cc: "qemu-devel"
Envoyé: Mercredi 14 Janvier 2015 17:07:41
Objet: Re: [Qemu-devel] cpu hotplug and windows guest (win2012r2)
On Fri, Jan
BTW both 2008r2 and 2012r2 are supporting this. 2008r2 is kind enough
to tell me that the cpu count is changed and I should relaunch task
manager.
center edition was needed)
- Mail original -
De: "Igor Mammedov"
À: "aderumier"
Cc: "qemu-devel"
Envoyé: Lundi 19 Janvier 2015 17:06:37
Objet: Re: [Qemu-devel] cpu hotplug and windows guest (win2012r2)
On Fri, 9 Jan 2015 11:26:08 +0100 (CET)
Alexandre D
y hotplug, maybe for cpu too)
- Mail original -
De: "Andrey Korolyov"
À: "aderumier"
Cc: "qemu-devel"
Envoyé: Mercredi 14 Janvier 2015 17:07:41
Objet: Re: [Qemu-devel] cpu hotplug and windows guest (win2012r2)
On Fri, Jan 9, 2015 at 4:35 PM, Andrey Kor
On Fri, 9 Jan 2015 11:26:08 +0100 (CET)
Alexandre DERUMIER wrote:
> Hi,
>
> I'm currently testing cpu hotplug with a windows 2012R2 standard guest,
>
> and I can't get it too work. (works fine with linux guest).
>
> host kernel : rhel7 3.10 kernel
> qemu 2.2
>
>
> qemu command line : -smp cp
On Fri, Jan 9, 2015 at 4:35 PM, Andrey Korolyov wrote:
> On Fri, Jan 9, 2015 at 1:26 PM, Alexandre DERUMIER
> wrote:
>> Hi,
>>
>> I'm currently testing cpu hotplug with a windows 2012R2 standard guest,
>>
>> and I can't get it too work. (works fine with linux guest).
>>
>> host kernel : rhel7 3.
On Fri, Jan 9, 2015 at 1:26 PM, Alexandre DERUMIER wrote:
> Hi,
>
> I'm currently testing cpu hotplug with a windows 2012R2 standard guest,
>
> and I can't get it too work. (works fine with linux guest).
>
> host kernel : rhel7 3.10 kernel
> qemu 2.2
>
>
> qemu command line : -smp cpus=1,sockets=2
Hi,
I'm currently testing cpu hotplug with a windows 2012R2 standard guest,
and I can't get it too work. (works fine with linux guest).
host kernel : rhel7 3.10 kernel
qemu 2.2
qemu command line : -smp cpus=1,sockets=2,cores=1,maxcpus=2
Started with 1cpu, topogoly is 2sockets with 1cores.
T
ld like to have a look at it. (I would like to prepare work for next
proxmox release)
- Mail original -
De: "Igor Mammedov"
À: "Alexandre DERUMIER"
Cc: "qemu-devel"
Envoyé: Mercredi 12 Décembre 2012 21:13:06
Objet: Re: [Qemu-devel] cpu hotplug roadmap
On Wed, 12 Dec 2012 17:55:38 +0100 (CET)
Alexandre DERUMIER wrote:
> Hi,
> this wiki talked about cpu hotplug for qemu 1.3.
>
> http://wiki.qemu.org/Features/CPUHotplug
>
> Is it planned for qemu 1.4 ? or later release ?
WiKi is not complete yet and shows only foreseeable steps
that hopefully w
Hi,
this wiki talked about cpu hotplug for qemu 1.3.
http://wiki.qemu.org/Features/CPUHotplug
Is it planned for qemu 1.4 ? or later release ?
Regards,
Alexandre
Am 30.08.2012 20:56, schrieb Igor Mammedov:
On Thu, 30 Aug 2012 20:45:10 +0200
Stefan Priebe wrote:
Am 30.08.2012 20:40, schrieb Igor Mammedov:
Am 30.08.2012 um 17:41 schrieb Andreas Färber :
Am 30.08.2012 11:06, schrieb Stefan Priebe:
I tried latest 1.2rc1 kvm-qemu with vanilla kernel v3.
On Thu, 30 Aug 2012 20:45:10 +0200
Stefan Priebe wrote:
> Am 30.08.2012 20:40, schrieb Igor Mammedov:
> Am 30.08.2012 um 17:41 schrieb Andreas Färber :
>
> > Am 30.08.2012 11:06, schrieb Stefan Priebe:
> >> I tried latest 1.2rc1 kvm-qemu with vanilla kernel v3.5.2 but the VM
> >
Am 30.08.2012 20:40, schrieb Igor Mammedov:
Am 30.08.2012 um 17:41 schrieb Andreas Färber :
Am 30.08.2012 11:06, schrieb Stefan Priebe:
I tried latest 1.2rc1 kvm-qemu with vanilla kernel v3.5.2 but the VM
just crashes when sending cpu_set X online through qm monitor.
For SLES we're carrying
On Thu, 30 Aug 2012 19:23:14 +0200
Stefan Priebe wrote:
> Am 30.08.2012 18:43, schrieb Andreas Färber:
> > Am 30.08.2012 18:35, schrieb Stefan Priebe:
> >> Am 30.08.2012 um 17:41 schrieb Andreas Färber :
> >>
> >>> Am 30.08.2012 11:06, schrieb Stefan Priebe:
> I tried latest 1.2rc1 kvm-qemu
Am 30.08.2012 18:43, schrieb Andreas Färber:
Am 30.08.2012 18:35, schrieb Stefan Priebe:
Am 30.08.2012 um 17:41 schrieb Andreas Färber :
Am 30.08.2012 11:06, schrieb Stefan Priebe:
I tried latest 1.2rc1 kvm-qemu with vanilla kernel v3.5.2 but the VM
just crashes when sending cpu_set X online
Am 30.08.2012 18:35, schrieb Stefan Priebe:
> Am 30.08.2012 um 17:41 schrieb Andreas Färber :
>
>> Am 30.08.2012 11:06, schrieb Stefan Priebe:
>>> I tried latest 1.2rc1 kvm-qemu with vanilla kernel v3.5.2 but the VM
>>> just crashes when sending cpu_set X online through qm monitor.
>>
>> For SLES
Am 30.08.2012 um 17:41 schrieb Andreas Färber :
> Hello,
>
> Am 30.08.2012 11:06, schrieb Stefan Priebe:
>> I tried latest 1.2rc1 kvm-qemu with vanilla kernel v3.5.2 but the VM
>> just crashes when sending cpu_set X online through qm monitor.
>
> For SLES we're carrying a patch by Kamalesh Babul
30.08.2012 19:41, Andreas Färber wrote:
> Hello,
>
> Am 30.08.2012 11:06, schrieb Stefan Priebe:
>> I tried latest 1.2rc1 kvm-qemu with vanilla kernel v3.5.2 but the VM
>> just crashes when sending cpu_set X online through qm monitor.
>
> For SLES we're carrying a patch by Kamalesh Babulal that p
Hello,
Am 30.08.2012 11:06, schrieb Stefan Priebe:
> I tried latest 1.2rc1 kvm-qemu with vanilla kernel v3.5.2 but the VM
> just crashes when sending cpu_set X online through qm monitor.
For SLES we're carrying a patch by Kamalesh Babulal that prevents this
(BNC#747339).
Don't know why that patc
On Thu, 30 Aug 2012 11:06:21 +0200
Stefan Priebe wrote:
> Hello list,
>
> what is the status of CPU hotplug support?
>
> I tried latest 1.2rc1 kvm-qemu with vanilla kernel v3.5.2 but the VM
> just crashes when sending cpu_set X online through qm monitor.
>
it's work in progress and not impleme
Hello list,
what is the status of CPU hotplug support?
I tried latest 1.2rc1 kvm-qemu with vanilla kernel v3.5.2 but the VM
just crashes when sending cpu_set X online through qm monitor.
Greets,
Stefan
57 matches
Mail list logo
