Displaying 7 results from an estimated 7 matches for "setvcpu".
Did you mean:
setmcpu
2013 Aug 09
2
state of setvcpus
Hello.
Does someone know in what state setvcpu command is?
I get:
virsh # setvcpus gentookvm 4
error: internal error: cannot change vcpu count of this domain
and
error : qemuDomainHotplugVcpus:4087 : internal error: cannot change vcpu
count of this domain
Does this work for someone?
cheers
t.
2013 Aug 09
0
Re: state of setvcpus
On 08/09/2013 06:26 AM, Thomas Stein wrote:
> Hello.
>
> Does someone know in what state setvcpu command is?
>
> I get:
>
> virsh # setvcpus gentookvm 4
> error: internal error: cannot change vcpu count of this domain
>
> and
>
> error : qemuDomainHotplugVcpus:4087 : internal error: cannot change vcpu
> count of this domain
>
> Does this work for someon...
2013 Aug 09
3
Re: state of setvcpus
Am 09.08.13 15:09, schrieb Eric Blake:
> On 08/09/2013 06:26 AM, Thomas Stein wrote:
>> Hello.
>>
>> Does someone know in what state setvcpu command is?
>>
>> I get:
>>
>> virsh # setvcpus gentookvm 4
>> error: internal error: cannot change vcpu count of this domain
>>
>> and
>>
>> error : qemuDomainHotplugVcpus:4087 : internal error: cannot change vcpu
>> count of this dom...
2017 Nov 20
2
4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk
On 11/20/2017 08:42 PM, Jens Axboe wrote:
> On 11/20/2017 12:29 PM, Christian Borntraeger wrote:
>>
>>
>> On 11/20/2017 08:20 PM, Bart Van Assche wrote:
>>> On Fri, 2017-11-17 at 15:42 +0100, Christian Borntraeger wrote:
>>>> This is
>>>>
>>>> b7a71e66d (Jens Axboe 2017-08-01 09:28:24 -0600 1141) * are mapped to
2017 Nov 20
2
4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk
On 11/20/2017 08:42 PM, Jens Axboe wrote:
> On 11/20/2017 12:29 PM, Christian Borntraeger wrote:
>>
>>
>> On 11/20/2017 08:20 PM, Bart Van Assche wrote:
>>> On Fri, 2017-11-17 at 15:42 +0100, Christian Borntraeger wrote:
>>>> This is
>>>>
>>>> b7a71e66d (Jens Axboe 2017-08-01 09:28:24 -0600 1141) * are mapped to
2017 Nov 21
2
4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk
...ck/vda/sched/write_fifo_list
/sys/kernel/debug/block/vda/sched/read_next_rq
/sys/kernel/debug/block/vda/sched/read_fifo_list
/sys/kernel/debug/block/vda/write_hints
/sys/kernel/debug/block/vda/state
/sys/kernel/debug/block/vda/requeue_list
/sys/kernel/debug/block/vda/poll_stat
--> in host virsh setvcpu zhyp137 2
[root at zhyp137 ~]# chcpu -e 1
CPU 1 enabled
[root at zhyp137 ~]# find /sys/kernel/debug/block/vd*
/sys/kernel/debug/block/vda
/sys/kernel/debug/block/vda/hctx0
/sys/kernel/debug/block/vda/hctx0/cpu0
/sys/kernel/debug/block/vda/hctx0/cpu0/completed
/sys/kernel/debug/block/vda/hctx0/cpu...
2017 Nov 21
2
4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk
...ck/vda/sched/write_fifo_list
/sys/kernel/debug/block/vda/sched/read_next_rq
/sys/kernel/debug/block/vda/sched/read_fifo_list
/sys/kernel/debug/block/vda/write_hints
/sys/kernel/debug/block/vda/state
/sys/kernel/debug/block/vda/requeue_list
/sys/kernel/debug/block/vda/poll_stat
--> in host virsh setvcpu zhyp137 2
[root at zhyp137 ~]# chcpu -e 1
CPU 1 enabled
[root at zhyp137 ~]# find /sys/kernel/debug/block/vd*
/sys/kernel/debug/block/vda
/sys/kernel/debug/block/vda/hctx0
/sys/kernel/debug/block/vda/hctx0/cpu0
/sys/kernel/debug/block/vda/hctx0/cpu0/completed
/sys/kernel/debug/block/vda/hctx0/cpu...