>>Many thanks for your reply, and please, let me to do a question:
>>Then, why I have a great difference of performance between the before and
>>the after of install your patches if i never touched the kernel nor his
>>configuration? (the patches installed are: pve-qemu-kvm_2.2-2_amd64.deb and
Hello,
i use A iSCSI IBM DS3300 bay to store virtual machines. I want to have a
'ready to go' backup on another iSCSI target (NAS QNAP).
I would now is there s a way to copy image from one LVM to another one, i
tried to use rsync to make it running, but rsync can't replicate special
device !
Usi
On 01/02/2015 03:16 PM, Alexandre Derumier wrote:
Signed-off-by: Alexandre Derumier
---
PVE/API2/Qemu.pm | 31 ++-
1 file changed, 30 insertions(+), 1 deletion(-)
diff --git a/PVE/API2/Qemu.pm b/PVE/API2/Qemu.pm
index e39e59b..d097662 100644
--- a/PVE/API2/Qemu.
Damn, I really don't known what I have done here ...sorry
I wanted to do:
foreach my $opt (@revert) {
- Mail original -
De: "dietmar"
À: "pve-devel"
Envoyé: Mercredi 7 Janvier 2015 10:26:04
Objet: Re: [pve-devel] [PATCH 7/7] update_vm api : add optionnal revert option
On 01/02/2015 03
On 01/07/2015 10:48 AM, Alexandre DERUMIER wrote:
Damn, I really don't known what I have done here ...sorry
I wanted to do:
foreach my $opt (@revert) {
OK, I applied a fixed versions:
https://git.proxmox.com/?p=qemu-server.git;a=commitdiff;h=d3df8cf3508232a8682bb8beb28ffa9b261270b2
__
Hi,
today i wanted to migrate a VM which does not have network in their boot
order.
This resulted in the following error of the KVM process:
kvm: Unknown ramblock ":00:12.0/virtio-net-pci.rom", cannot accept
migration
qemu: warning: error while loading state for instance 0x0 of device 'ram'
k
I have changed the vm config file according your suggestions after of apply
your patches:
numa0: memory=124416,policy=bind
numa1: memory=124416,policy=bind
And always with:
...
sockets: 2
cores: 20
cpu: host
hotplug: 1
memory: 248832
tablet: 0
...
Anyway, the change was for much better. ... :-)
Dear,
when you have one container, they use many traffic, you will not find in
the host summary!
Their we see 1.2 Megabit average per hour
and in one container we see averages from 100 to 300 mbit/sec and in
this host we have
ca. 150 client containers running, so we look not every time in all
sta
> They come from the following piece of code:
> # qemu > 0.15 always try to boot from network - we disable that by
> # not loading the pxe rom file
> $extra = ($bootorder !~ m/n/) ? "romfile=," : '';
> ...
> $tmpstr =
> "$device,${extra}mac=$net->{macaddr},netdev=$netid$pciaddr,id=$netid";
>
> I
Am 08.01.2015 um 06:14 schrieb Dietmar Maurer:
They come from the following piece of code:
# qemu > 0.15 always try to boot from network - we disable that by
# not loading the pxe rom file
$extra = ($bootorder !~ m/n/) ? "romfile=," : '';
...
$tmpstr =
"$device,${extra}mac=$net->{macaddr},net
>>Anyway, the change was for much better. ... :-)
>>...Many thanks for the patches !!!
In this case, auto numa balancing is doing the job.
(Note that numa: 1, should do exactly the same thing that the 2numa lines)
Great that it's working fine :)
Thanks for the tests !
- Mail original
>>If we set strict=on qemu only tries the devices we explicitly set to
>>boot. So network is not tried even without the romfile option.
Indeed, this seem to be the right way
https://bugzilla.redhat.com/show_bug.cgi?id=903204
http://www.redhat.com/archives/libvir-list/2013-November/msg01237.html
Hi,
I just notice that something is wrong currently with cpu hotplug implementation,
and that maybe it'll break in coming qemu release according to this patch
http://lists.gnu.org/archive/html/qemu-devel/2014-11/msg01305.html
Start guiding users towards making sure their topology supports the
m
13 matches
Mail list logo
