similar to: measuring stopped time during live migration

On Thu, Jul 30, 2020 at 16:13:09 +0200, Alex Walender wrote: > Dear libvirt community, > > > Using recent Ubuntu Stein Cloud Packages, we are observing random > libvirtd live-migration crashes on the target host. > Libvirt is having a SEGFAULT with the qemu driver. Transferring block > devices usually works without issues. > However, the following memory transfer is

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 > > migrated. I use the following command. > > > > # virsh migrate --live domain

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 live migration after fixing the pc-q35-2.1 error. Now i > >>> have new problem. It seems

I found that the "Save" feature is not supported for the full virtualizaed systems in xen 3.0.4 which comes with the SLES10, and will be available in version 3.0.5. Is there any other way to backup a running "windows guest machine on the fly" _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

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 problems. Apart from beeing way to fast. # virsh migrate --live domain qemu+ssh://newhost/system

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 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

Hello, The pxeconfig part: label sapcl03-xen kernel mboot.c32 append sles10/xen.gz dom0_mem=258048 --- sles10/linux-xen netdevice=eth0 insmod=aic79xx console=ttyS0,57600 --- sles10/initrd-xen.sapcl03 The thing sort of boots: COM32 Multiboot loader v0.2. Copyright (C) 2005-2006 Tim Deegan. Kernel: sles10/xen.gz dom0_mem=258048 Loading sles10/xen.gz..... Module:

Thanks for the reply. Sorry I didn't provide more details, but, yes, these are HVM domains. I use PV domains whenever possible, but in the case of Windows XP, that isn't possible, so I have to use HVM. I haven't tried suspending to OCFS2 with a PV domain, but I may give that a shot. Still, I think it's strange that it works perfectly fine to my ext3 and reiser filesystems, but

Hi, I thought about changing the RPM package the guys of Redhat created, because I wanted an Init Script for SLES10 built-in. I started documenting the steps I took. Maybe it''s useful for someone else, although in German.. but the basic steps should be useable. My little Installating puppet Howto: http://wiki.njh.eu/Konfigurationsmanagement#Installation_3 The Init Script for SLES10:

Hi, I''m trying to build non sles10 domU under sles10 dom0. I''ve downloaded centos and debian images from www.jailtime.org fixed the config file and try to start domU. After creating domU from images I get Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) I''m running without problems two sles10 domU machines. After using google allot :-)

Hi, After some hard trying to use lustre on our debian servers with an up2date kernel I decided to buy sles10 to make everything more comftable: I installed (rpm -i) the new kernelbinaries from 1.6.2/sles10-i686 to a sles10 test box (AMD64). When i try to install the modules form 1.6.2/sles10-i686 it says : sles2:/usr/src/lustre # rpm -i

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 > migrated. I use the following command. > > # virsh migrate --live domain qemu+ssh://newhost/system > --copy-storage-all --verbose --persistent > > It works without problems.

Hello I am working with 3 host machines each running xen with shared NFS storage. I am working on automatic load balancing if one host is over utilized and another is under utilized by measuring the utilization from xentop. I am facing a problem after migration of VM. I am setting the flags ( 1| 8| 16) in order to do live migration, persist VM on destination, undefine host from source. After

Hi to all out there, i know this is not the right mailinglist for this issue, but i?m hoping to get maybe here an answer to my problem. i have succesfully migrated 12.000 mailboxes on a debaian with washington imap to maildir on sles10 with dovecot. although i had some post-converting work to do, i can say that almost everything went fine. but there is one problem with my LDA. When postfix is

I am having issues with guest OSes running on SLES10 (Sun 4200) hosts. Periodically, the guest OS system drops off the network. From the general network it is not pingable, consequently, ssh fails. If however, I log into the SLES10 server that is hosting the guest OS and ssh to the guest OS, then it becomes immediately pingable and accessible to the rest of the network. Almost like the

Hello, I have a difficulty with the option 'hide unreadable' in the smb.conf regarding to it's effect on my Vista machines. In the smb.conf I have declared the following share: [userdata] path = /data/userdata admin users = domain+adminuser browseable = yes writeable = yes hide unreadable = yes csc policy = disable The

We have Samba 3.2.4 on two SLES 10 (one is SP1, the other SP2 64bit) machines. Both are member servers in our ADS, which was over the past month given some additional DCs, new IPs for all DCs, and upgraded to Windows 2008 (from win2003). The krb5.conf and nsswitch.conf files on the two machines are identical; the smb.conf files are *nearly* identical in their common section; the filewall rules

Hi I am running xen on sles10 sp1. Already created one vm for sles10 sp1 using " directory installation " to create image file , by following the instruction given under http://www.novell.com/documentation/suse10/index.html?page=/documentatio n/suse10/adminguide/data/sec_xen_inst.html. Vm created successfully (xm create conffile). But I am not able to connect to the console(vnc

Hi, I have a problem with augeas, puppet and Suse 10 SP2. Augeas works when I use the augtool to edit files. But I would like to use it in combination with puppet. My class looks something like this: augeas {"sysctl.conf": provider => "augeas", context => "/files/etc/sysctl.conf", changes => [ "set

My head hurts from trying to figure this out for the past several hours . . . I want to determine what provider to use based on a fact (thanks for the suse version fact btw) but I ain''t gettin it: What''s wrong? Am I going down the completely wrong path? Is there a better way? # suse-yum.pp case $suse_repo_name { #sled10-i586: {Package{ provider => rug}} sled10-i586: