search for: forceably

...flight in the guest OS will still be ready to go when the guest starts > back up, no fsck needed. --quiesce says to tell the guest to flush all > I/O, then captures disk state, all without stopping the guest. But > --quiesce requires the guest to be running to work, while --memspec > forceably stops the guest (the migration algorithm must pause, even if > --live minimizes the pause to a fraction of a second). Would calling snapshot-create-as with --disk-only and --quiese still succeed on a VM that is stopped (since the disk would already be consistent, it would just call "qemu-im...

RESULT! ~# kinit administrator at MY-DOMAIN.LOCAL Password for administrator at MY-DOMAIN.LOCAL: Warning: Your password will expire in 41 days on Thu Apr 23 16:57:35 2015 !!!! --- I should have listened to you guys much sooner. I suspect that the .local did indeed have something to do with it since mDNS was running and may have screwed with dns resolution for *.local. tlds? additionally, I

----- Original Message ----- > From: "Eric Blake" <eblake@redhat.com> To: "Andrew Martin" > <amartin@xes-inc.com>, libvirt-users@redhat.com Sent: Thursday, May 22, 2014 > 5:44:54 PM Subject: Re: [libvirt-users] Live snapshots of a single block > device > > On 05/22/2014 04:31 PM, Andrew Martin wrote: > > Hello, > > > > [Can you

On 12/03/15 22:31, Matthias Busch wrote: > RESULT! > > ~# kinit administrator at MY-DOMAIN.LOCAL > Password for administrator at MY-DOMAIN.LOCAL: > Warning: Your password will expire in 41 days on Thu Apr 23 16:57:35 2015 > > !!!! > > --- > > I should have listened to you guys much sooner. I suspect that the > .local did indeed have something to do with it

I''m wondering what other folks think of Dojo (0.1 just released), MochiKit, and some of the other js frameworks relative to prototype/scriptaculous (p/s). P/S seems to have broader support although I''m not sure about IE 5.5 in the other frameworks. A second question is related. I''ve got some AJAX working with prototype + behaviour, and I''m building in refresh

On 05/23/2014 12:16 PM, Andrew Martin wrote: >> --quiesce requires the guest to be running to work, while --memspec >> forceably stops the guest (the migration algorithm must pause, even if >> --live minimizes the pause to a fraction of a second). > Would calling snapshot-create-as with --disk-only and --quiese still succeed > on a VM that is stopped (since the disk would already be consistent, it would > just...

...kup process hangs. > > If we kill the bacula storage daemon on dom0, all of the virtual > machines release and we can log in again. At no point does anything > reboot -- it just hangs, and it''s not a fatal hang. If the backup > process stops, whether through a timeout or by forceably stopping the > storage daemon, the virtual machines are again pingable and we can log > in both with ssh or ''xm console''. > > We tried monitoring the memory usage during the backup test by running > ''top'' in separate console windows. Loads were ac...

...ng I/O operations in flight in the guest OS will still be ready to go when the guest starts back up, no fsck needed. --quiesce says to tell the guest to flush all I/O, then captures disk state, all without stopping the guest. But --quiesce requires the guest to be running to work, while --memspec forceably stops the guest (the migration algorithm must pause, even if --live minimizes the pause to a fraction of a second). > > However I don't have qemu-guest-agent installed on the guests, so would using > --memspec instead of --disk-only produce a snapshot that is consistent (since it &gt...

Hey Peter, many thanks for your reply. --- regarding .local domains I know this is regarded by some as bad form, is actively being discouraged by the samba wiki and can cause problems with bonjour/zerobla configuration. I can say for certain that no apple devices will ever come anywhere near that network and the other drawbacks of .local like getting signed certs... should never be an issue

Before, in my "Hard Problem" email I was trying to communicate a design issue were trying to solve with Xen. This is what we need to do: 1) Deploy 24 Windows XP VMs in parallel. 2) Boot them from a shared Windows XP C: drive. 3) Since this is a read-only shared image we obviously can''t have multiple VM''s writing to it. 4) All writes to the boot image for logging,

Before, in my "Hard Problem" email I was trying to communicate a design issue were trying to solve with Xen. This is what we need to do: 1) Deploy 24 Windows XP VMs in parallel. 2) Boot them from a shared Windows XP C: drive. 3) Since this is a read-only shared image we obviously can''t have multiple VM''s writing to it. 4) All writes to the boot image for logging,