:
>On Wed, Apr 07, 2021 at 19:46:54 +0200, Thomas Stein wrote:
>>
>> Got a little bit further. "virsh backup-begin jitsi jitsi-backup.xml"
>works
>> and I have a backup file now. VM was running all the time. Question.
>Is it
>> save to use this functio
4-07 19:03, Thomas Stein wrote:
Hello one and all.
Just wanted to check out the new feature domainbackup but having
trouble to configure it. I thought I just have to put
at the top level of my domain xml file but that does not seem to work.
I get:
error: XML document
Hello one and all.
Just wanted to check out the new feature domainbackup but having trouble
to configure it. I thought I just have to put
at the top level of my domain xml file but that does not seem to work. I
get:
error: XML document failed to validate aga
On 2020-05-11 08:58, Peter Krempa wrote:
On Fri, May 08, 2020 at 13:05:01 +0200, Thomas Stein wrote:
Maybe:
from 6.3.0 release notes:
- qemu: Fix domain restore from a block device
When using namespaces, libvirt was unable to restore a domain from
a
block device because libvirt tried
.
cheers, t.
On 2020-05-08 12:48, Thomas Stein wrote:
Hello one and all.
Got a problem with libvirt 6.2.0 and qemu 5.0.0.
virsh blockcommit mymachine vda --active --verbose --pivot
works until it shows [100%] but it never actually pivots. It just sits
there. Is this a known issue with 6.2.0 and i
Hello one and all.
Got a problem with libvirt 6.2.0 and qemu 5.0.0.
virsh blockcommit mymachine vda --active --verbose --pivot
works until it shows [100%] but it never actually pivots. It just sits
there. Is this a known issue with 6.2.0 and i should
try 6.3.0? For now i switched back to qem
Hello all.
My currently used versions: libvirt-5.2.0 and qemu-4.0.0.
Here is my problem. I'm struggeling since a few weeks with a strange
behaviour by either qemu or libvirt. After a reboot of
the hardware node the $domain.xml contains suddenly a backingStore
setting which was not there before
(switched to libvirt-users as it seems to be more appropriate)
On 2019-05-16 23:02, Eric Blake wrote:
On 5/16/19 10:20 AM, Thomas Stein wrote:
Hello all.
My currently used versions: libvirt-5.2.0 and qemu-4.0.0.
Here is my problem. I'm struggeling since a few weeks with a strange
beha
Am 26.07.16 um 10:25 schrieb Prof. Dr. Michael Schefczyk:
> Dear All,
>
> using CentOS 7.2.1511, and libvirt from ovirt repositories (currently
> 1.2.17-13.el7_2.5, but without otherwise using ovirt) I am regularly backing
> up my VMs which are on qcow2 files. In general, I am trying to follow
Am 12.06.15 um 11:31 schrieb Thomas Stein:
> Hello.
>
> I seem to be to stupid to configure vcpu hotplugging on one of my
> machines. Whenever i set:
Aieee! It seems this setting is not needed anymore. "8" just works fine. I can downscale with this
setting as i wish.
c
Am 12.06.15 um 11:50 schrieb Thomas Stein:
> Am 12.06.15 um 11:43 schrieb Dominique Ramaekers:
>> Did you shutdown the guest before making this change?
It seems this setting is accepted:
8
Now i can say:
virsh # setvcpus --live --guest serve 2
Within the machine:
[ 47.833016] smp
m-x86_64
cheers
t.
> -Oorspronkelijk bericht-----
> Van: Thomas Stein [mailto:himbe...@meine-oma.de]
> Verzonden: vrijdag 12 juni 2015 11:32
>
Hello.
I seem to be to stupid to configure vcpu hotplugging on one of my
machines. Whenever i set:
4
and save this setting, this setting is undone by libvirt. It jumps back to:
4
I'm confused now. Someone has an idea what's going on here? Any hints
are really appreciated.
cheers
t.
_
Am 17.05.15 um 11:03 schrieb Thomas Stein:
> On Tuesday 28 April 2015 17:13:38 Matthew Schumacher wrote:
>
>> Got a chance to work on this today, and posted a bunch of debug on the
>> bug ticket:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1210903
>>
On Tuesday 28 April 2015 17:13:38 Matthew Schumacher wrote:
> Got a chance to work on this today, and posted a bunch of debug on the
> bug ticket:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1210903
>
> Hopefully that helps track this down.
Currently it works for me again. Linux-4.0.3, Qemu
Am 21.04.15 um 03:44 schrieb Chengyuan Li:
> Hi Eric,
>
> Thanks!
> You are right, I missed declaring namespace, now, the is
> saved after virsh edit.
Nice. Can you give a full example? Also are the limitations still the
same as of 2013? This is what the internet is telling me.
- Image formats
On Friday 10 April 2015 13:07:38 Matthew Schumacher wrote:
> Hello List,
>
> Seems like blockcopy --wait doesn't work work qemu-2.2.x.
>
> I found someone else having the same problem, but it never went anywhere:
>
> https://www.redhat.com/archives/libvirt-users/2015-January/msg00045.html
>
> I
On Tuesday 24 February 2015 17:47:11 you wrote:
> On Tuesday 24 February 2015 16:58:22 you wrote:
> > On 24.02.2015 16:10, Thomas Stein wrote:
> > > On Tuesday 24 February 2015 14:56:10 Michal Privoznik wrote:
> > >> On 24.02.2015 14:29, Thomas Stein wrote:
>
On Tuesday 24 February 2015 16:58:22 you wrote:
> On 24.02.2015 16:10, Thomas Stein wrote:
> > On Tuesday 24 February 2015 14:56:10 Michal Privoznik wrote:
> >> On 24.02.2015 14:29, Thomas Stein wrote:
> >>> Hola.
> >>>
> >>> Just tried a l
On Tuesday 24 February 2015 14:56:10 Michal Privoznik wrote:
> On 24.02.2015 14:29, Thomas Stein wrote:
> > Hola.
> >
> > Just tried a live migration after fixing the pc-q35-2.1 error. Now i
> > have new problem. It seems during live migration only the ram gets
> &
Hola.
Just tried a live migration after fixing the pc-q35-2.1 error. Now i
have new problem. It seems during live migration only the ram gets
migrated. I use the following command.
# virsh migrate --live domain qemu+ssh://newhost/system
--copy-storage-all --verbose --persistent
It works without
Thanks Laine for taking the time to clarify this.
cheers
t.
On Monday 23 February 2015 16:51:26 Laine Stump wrote:
> On 02/23/2015 02:26 PM, Thomas Stein wrote:
> > Hello.
> >
> > I'm not able to disable the sata controller on a machine='pc-q35-2.1'
Am 09.01.15 um 15:38 schrieb Thomas Stein:
> Am 07.01.15 um 18:26 schrieb Thomas Stein:
>
>>> Based on this message, it is qemu that is refusing to do the pivot, but
>>> I don't know if that is because of permissions on the destination file,
>>> or some
Am 07.01.15 um 18:26 schrieb Thomas Stein:
>> Based on this message, it is qemu that is refusing to do the pivot, but
>> I don't know if that is because of permissions on the destination file,
>> or something else (that is, it may still be a libvirt bug for not
>>
On Wednesday 07 January 2015 09:46:09 Eric Blake wrote:
> On 01/07/2015 07:19 AM, Thomas Stein wrote:
> > Hello.
> >
> > I'm seeing this error while doing a backup of a VM.
> >
> > + virsh blockcommit kaltura vda --active --verbose --pivot
> > Block C
Hello.
I'm seeing this error while doing a backup of a VM.
+ virsh blockcommit kaltura vda --active --verbose --pivot
Block Commit: [100 %]error: failed to pivot job for disk vda
error: internal error: unable to execute QEMU command
'block-job-complete': The active block job for device
'drive-vir
Am 05.11.14 14:48, schrieb Eric Blake:
> On 11/05/2014 01:20 PM, Thomas Stein wrote:
>> Am 05.11.14 11:48, schrieb Martin Kletzander:
>>> On Wed, Nov 05, 2014 at 11:35:37AM +0100, Thomas Stein wrote:
>>>> Hello.
>>>>
>>>> I'm strugge
Am 05.11.14 14:44, schrieb Eric Blake:
> On 11/05/2014 10:50 AM, Thomas Stein wrote:
>> Am 04.11.14 17:55, schrieb Thomas Stein:
>>> Hello.
>>>
>>> Just a quick question. Is "setvcpus $windowsVM --guest 4" supposed to
>>> work? I have qem
Am 05.11.14 11:48, schrieb Martin Kletzander:
> On Wed, Nov 05, 2014 at 11:35:37AM +0100, Thomas Stein wrote:
>>Hello.
>>
>>I'm struggeling a little bit with the setvcpus command. I'm trying now
>>to get this running for a linux VM. Here is what i have:
>&
Hello.
I'm struggeling a little bit with the setvcpus command. I'm trying now
to get this running for a linux VM. Here is what i have:
4
Now the VM is starting with 2 CPUs. When i try to increase the number of
CPUs i get:
setvcpus dev --guest 4
error: invalid argument: requested vcpu count is
Am 04.11.14 17:55, schrieb Thomas Stein:
> Hello.
>
> Just a quick question. Is "setvcpus $windowsVM --guest 4" supposed to
> work? I have qemu-guest-agent (1.6.something) running inside a windows7
> vm but all i get is:
>
> virsh # setvcpus windows7 --gu
Hello.
Just a quick question. Is "setvcpus $windowsVM --guest 4" supposed to
work? I have qemu-guest-agent (1.6.something) running inside a windows7
vm but all i get is:
virsh # setvcpus windows7 --guest 4
error: invalid argument: requested vcpu count is greater than the count
of enabled vcpus in
Am 03.11.14 09:39, schrieb Eric Blake:
> On 11/02/2014 02:13 PM, Thomas Stein wrote:
>
>> After a little bit of fiddling i've got this running. Here is what's
>> neccessary in case someone wanna try this too.
>
> That's awesome news! Thanks for sharing
> > A quick google search found this:
> > http://callecalle.uach.cl/ovirt-engine/docs/manual/en_US/html/Technical_Gu
> > id e/QEMU_Guest_Agent_Overview.html
> >
> > Sadly, it didn't spell out the name of where you install hook scripts
> > into the guest. But this commit is pretty telling:
> > ht
On Wednesday 29 October 2014 13:29:25 Eric Blake wrote:
> On 10/29/2014 01:07 PM, Thomas Stein wrote:
> > About the --quiesce option. Do i need to do something inside the vm? The
> > most commonly would probably be a sql server running inside the vm. Do i
> > need to tell the
On Saturday 11 October 2014 10:13:14 Kashyap Chamarthy wrote:
> 2. Create an external live snapshot:
>
> $ virsh snapshot-create-as --domain vm1 sn1 \
> --diskspec vda,file=/export/images/sn1.qcow2 \
> --disk-only --atomic --no-metadata
>
> Note (thanks Eric Blake): Above
On Monday 13 October 2014 16:35:15 Thomas Stein wrote:
> Am 13.10.14 16:25, schrieb Eric Blake:
> > On 10/13/2014 03:56 AM, Thomas Stein wrote:
> >> Hello.
> >>
> >>> blockcommit vm1 vda --active --verbose --pivot
> >>
> >>
Am 13.10.14 16:25, schrieb Eric Blake:
> On 10/13/2014 03:56 AM, Thomas Stein wrote:
>> Hello.
>>
>>> blockcommit vm1 vda --active --verbose --pivot
>>
>> That's where libvirt stops working at the moment, right?
>>
>> virsh # blockcommi
Hello.
> blockcommit vm1 vda --active --verbose --pivot
That's where libvirt stops working at the moment, right?
virsh # blockcommit puppet-test vda --active --verbose --pivot
error: unsupported flags (0x4) in function qemuDomainBlockCommit
cheers
t.
___
Am 22.09.14 10:42, schrieb Daniel P. Berrange:
> On Sat, Sep 20, 2014 at 02:13:16PM +0200, Thomas Stein wrote:
>> hello.
>>
>> I have an issue with libvirt-1.2.6 and qemu-2.1.1. As soon as i do:
>>
>> "savevm $domain"
>>
>> the doma
hello.
I have an issue with libvirt-1.2.6 and qemu-2.1.1. As soon as i do:
"savevm $domain"
the domain ist gone. Console says "unable to connect to monitor". Libvirt.log
says:
qemu-system-x86_64: /var/tmp/portage/app-
emulation/qemu-2.1.1/work/qemu-2.1.1/hw/net/virtio-net.c:1348:
virtio_net_
On 19. Juni 2014 14:38:06 MESZ, Laine Stump wrote:
>On 06/19/2014 02:47 PM, Thomas Stein wrote:
>> Hello.
>>
>> I have a strange error with one of my VMs. If i use dumpxml to save a
>VM
>> description the source part of the network part is missing. This
>prevent
Hello.
I have a strange error with one of my VMs. If i use dumpxml to save a VM
description the source part of the network part is missing. This prevents
redifining the machine from the dumped xml file:
This is how it looks before dumpxml:
And afterwards
Am 06.05.14 08:00, schrieb xeon_feng:
> Hello everyone
Hello.
Well i think thats not a problem with libvirt. Thats a problem with your
distribution. You should fill a bug report there.
cheers
t.
> I encountered a problem when I completed the update of libvirt from 0.10
> to 1.2.4 .
>
Am 22.04.14 14:00, schrieb Eric Blake:
> On 04/22/2014 01:47 AM, Thomas Stein wrote:
>> Hello.
>>
>> The Changelog of qemu-2.0.0 mentioned "Live snapshot merging". Someone
>> has an idea what could be ment by this? I'm asking because i'm still
>&g
Hello.
The Changelog of qemu-2.0.0 mentioned "Live snapshot merging". Someone
has an idea what could be ment by this? I'm asking because i'm still
struggling with finding a reliable backup solution for running kvm
machines. Blockcopy is my current solution.
best regards
Thomas
__
Am 27.09.13 14:57, schrieb cooldharma06:
> hi
>
> thanks for your information. i installed libvirt 1.1.2 as per your
> suggestion.
>
> Installation commands are as follows:
>
> ./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc
> --with-xen=yes --with-libxl=yes
> make
> make instal
Am 23.09.13 16:00, schrieb Daniel Berteaud:
> Le vendredi 20 septembre 2013 à 15:31 +0200, Thomas Stein a écrit :
>> Hello.
>>
>> Is someone performing incremental backups via libvirt for qemu/kvm
>> machines? I'm still having a hard time to
>> find a ni
Hello.
Another question regarding incremental backups. How can i roll back to a
specific version?
Example.
I have:
1. a base image
-rw-r--r-- 1 qemu qemu 39538851840 Sep 23 11:09 serve.lordcritical.qcow2
2. two external snapshots
-rw--- 1 qemu qemu 1179648 Sep 23 11:17
daily0.serve.l
On 2013-09-20 16:05, Davide Guerri wrote:
Hi
hn LibVirtKvm-scripts # ./fi-backup.sh -b /opt/virt-backup-local/ -d
serve.lordcritical
[DEB] qemu-img version '1.6.0' is supported
[DEB] KVM version '1.6.0,' is supported
[DEB] Snapshot for domain 'serve.lordcritical' requested
[DEB] Using timestam
ting backing file for
'/var/lib/libvirt/images/serve.lordcritical.bimg-20130920-151742'.
At the moment i try:
https://bitbucket.org/guilhemfr/virt-back
cheers
t.
It's very simple and on ubuntu requires some tweaks on apparmour
configuration.
Hth
Cheers,
Davide
--
Davi
Hello.
Is someone performing incremental backups via libvirt for qemu/kvm
machines? I'm still having a hard time to
find a nice procedure. I mean is it possible to make a full backup of an
image on monday a do the next days of the week
incremental backups?
Another way could be mount the image
Hello.
Suddenly on one of my vm's i get:
2013-09-06 09:44:39.501+: 2277: error :
qemuMonitorJSONGetMigrationStatusReply:2377 : internal error: unexpected
migration status in setup
This happens when i try to migrate /and/ when i try to do a "savevm".
error: Failed to save domain domain to
On Tuesday 03 September 2013 16:49:31 Gao feng wrote:
> On 09/03/2013 04:36 PM, Thomas Stein wrote:
> > Hello.
> >
> > Since upgrading to libvirt-1.1.2 i get this error:
> >
> > 2013-09-03 08:29:55.258+: 2281: error : virDBusCallMethod:1156 : The
> >
Hello.
Since upgrading to libvirt-1.1.2 i get this error:
2013-09-03 08:29:55.258+: 2281: error : virDBusCallMethod:1156 : The name
org.freedesktop.machine1 was not provided by any .service files
Also live migration doesn't seem to work anymore. There is no error except the
above one but t
On Friday 09 August 2013 09:03:50 Eric Blake wrote:
> On 08/09/2013 09:01 AM, Thomas Stein wrote:
> >> Meanwhile, you can try using 'setvcpus gentookvm
> >>
> >> --guest 4' to use the guest agent (assuming you have qemu-ga running in
> >> the
Am 09.08.13 17:03, schrieb Eric Blake:
> On 08/09/2013 09:01 AM, Thomas Stein wrote:
>>> Meanwhile, you can try using 'setvcpus gentookvm
>>> --guest 4' to use the guest agent (assuming you have qemu-ga running in
>>> the guest, and the proper plu
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 chang
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
Am 23.07.13 15:22, schrieb Eric Blake:
> [please don't commandeer unrelated threads - when starting a new topic,
> make sure you are NOT setting in-reply-to]
I'm sorry. You're right.
> On 07/23/2013 06:33 AM, Thomas Stein wrote:
>> Hello.
>>
>> Can s
Hello.
Can someone shed some light on the copy-storage-all feature? There are
many hits on google. My current questions are.
1. is it possible to do a migrate --live --copy-storage-all without
shared storage?
2. Do i need to have a preexisting image on the destination node?
3. Is this still
Am 02.07.13 17:43, schrieb Eric Blake:
> On 07/02/2013 08:19 AM, Thomas Stein wrote:
>>> Try this modification (again untested, but at least doesn't have a block
>>> job running during the save attempt):
>>>
>>>virsh dumpxml --security-info dom >
Am 02.07.13 15:42, schrieb Eric Blake:
> On 07/02/2013 06:55 AM, Thomas Stein wrote:
>>
>>> virsh dumpxml --security-info dom > dom.xml
>>> virsh undefine dom
>>
>> Hello.
>>
>> Someone was talking about this (undefining the VM) wou
> virsh dumpxml --security-info dom > dom.xml
> virsh undefine dom
Hello.
Someone was talking about this (undefining the VM) would not be
neccessary anymore when qemu-1.5 has been released. Is that true?
> virsh blockcopy dom vda /path/to/backup-vda
> polling loop - check periodically u
Am 10.06.13 10:40, schrieb Kashyap Chamarthy:
> On 06/10/2013 01:20 PM, Thomas Stein wrote:
>> Am 10.06.13 09:07, schrieb Kashyap Chamarthy:
>>> On 06/09/2013 02:46 PM, Thomas Stein wrote:
>>>> Hello.
>>>>
>>>> I just tried the following:
&
Am 10.06.13 09:07, schrieb Kashyap Chamarthy:
> On 06/09/2013 02:46 PM, Thomas Stein wrote:
>> Hello.
>>
>> I just tried the following:
>>
>> virsh dumpxml --security-info gentoo-template > gentoo-template.xml
>> virsh snapshot-create gentoo-template
&
Hello.
I just tried the following:
virsh dumpxml --security-info gentoo-template > gentoo-template.xml
virsh snapshot-create gentoo-template
virsh undefine gentoo-template
virsh blockcopy gentoo-template vda
/opt/virt-backup-blockcopy/gentoo-template/gentoo-template.qcow2 --wait
--verbose --fi
On 2013-03-09 14:31, Thomas Stein wrote:
Hello.
I'm not able to create a snapshot for none of my vm's running on a
particular node. And i have absolut no idea where to look to solve
this. Someone can point me to the right direction?
Okay. Answering myself.
hn images # qemu-x86_6
Hello.
I'm not able to create a snapshot for none of my vm's running on a
particular node. And i have absolut no idea where to look to solve this.
Someone can point me to the right direction?
hn images # qemu-x86_64 -version
qemu-x86_64 version 1.2.2 (qemu-kvm-1.2.0), Copyright (c) 2003-2008
69 matches
Mail list logo
