search for: forceable

> >> --live only makes sense when mixed with memory snapshots (with --memspec); > >> but > >> as you are doing a --disk-only snapshot, it doesn't help (I'm not sure if > >> it > >> will error out as mutually exclusive or just be silently ignored, > >> without reading the code). > > I'm using this code in a script for creating

...92.168.7.254:88 0.0.0.0:* 2239/samba ah, I was looking for krb5 or similar process name... --- > ipv6 well, its not exactly enabled. no ipv6 in network/interfaces, none in /etc/hosts and i am pretty sure I build without ipv6 support. if need be I could go deeper into raspbian and see if I can forceable disable ipv6 however, in the not too distant future, the possibility to at least run a dualstack should exist. forcing ipv6 off in the OS would be a step in the wrong direction for that :) --- just tested... I was able to add a win7pro to the domain!

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

...ah, I was looking for krb5 or similar process name... > > --- > >> ipv6 > well, its not exactly enabled. no ipv6 in network/interfaces, none in > /etc/hosts > and i am pretty sure I build without ipv6 support. > if need be I could go deeper into raspbian and see if I can forceable > disable ipv6 > > however, in the not too distant future, the possibility to at least > run a dualstack should exist. > forcing ipv6 off in the OS would be a step in the wrong direction for > that :) > > --- > > just tested... > I was able to add a win7pro to th...

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

The issues I''ve had with PE2650 and Linux in general all related to a lack of IRQ''s. I had to disable all non-essential devices in the BIOS (lpt, usb and com). It seems the BIOS on that server still has legacy IRQ issues (< IRQ15). In my xenU''s I also renamed /etc/sysconf/hwconf so it would''nt try to init any hardware devices directly. Maybe these options

On 05/23/2014 08:41 AM, Andrew Martin wrote: >> >> Any reason you aren't upgrading to newer versions? Although these seem >> sufficient for what you are trying. > The VM hosts I'm using all run Ubuntu 12.04 and I haven't had time to backport > and test newer versions yet. I've published the latest versions I built in this > PPA:

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,