Dear Martin,
Thank you for your suggestion. I have submitted a bug report on this ( libvirt
version 1.2.5). For your reference, the report No. is 1176584.
Just like you said, I set the affinity of my process to temporarily solve this
problem.
With my warmest regards
Cheng
-Original Messa
On 12/22/2014 03:27 PM, Gary R Hook wrote:
> I am experimenting with the blockcopy command, and after figuring out
> how to integrate qemu-nbd, nbd-client and
> dumpxml/undefine/blockcopy/define/et. al. I have one remaining question:
>
> What's the point?
Among other uses, live storage migration.
I am experimenting with the blockcopy command, and after figuring out
how to integrate qemu-nbd, nbd-client and
dumpxml/undefine/blockcopy/define/et. al. I have one remaining question:
What's the point?
The "replication" disk file is not, from what I can ascertain, bootable.
I expect this ope
Hi all,
I'm trying to use libvirt events API, but I can't find what event is
fired when some device (disk in this case) got attached to the domain.
In the docs I see only VIR_DOMAIN_EVENT_ID_DEVICE_REMOVED, but not
VIR_DOMAIN_EVENT_ID_DEVICE_ATTACHED. Is there some event for that?
BTW libxl drive
On Mon, Dec 22, 2014 at 08:40:03AM +, WANG Cheng D wrote:
Dear all,
I want my container to run on the third CPU core and I define this by the
following xml scrpits:
1
When I run my application in a container terminal, I can see the application
runs on the third core as expected.
When I ru
Dear all,
I want my container to run on the third CPU core and I define this by the
following xml scrpits:
1
When I run my application in a container terminal, I can see the application
runs on the third core as expected.
When I run my application using lxc-enter-namespace, the CPU pinning does
