similar to: virsh's editor configuration

On 16/09/14 13:46, Martin Kletzander wrote: > On Tue, Sep 16, 2014 at 01:34:37PM +0100, lejeczek wrote: >> hi all >> where/how to change vim's I presume configuration, one that >> virsh uses? >> thanks. >> P. >> > > Well, virsh just starts an $EDITOR. Set it up properly > and you're > good to go ;) > > Martin thanks, but more

On 16/09/14 15:21, Eric Blake wrote: > On 09/16/2014 08:15 AM, lejeczek wrote: >> On 16/09/14 13:46, Martin Kletzander wrote: >>> On Tue, Sep 16, 2014 at 01:34:37PM +0100, lejeczek wrote: >>>> hi all >>>> where/how to change vim's I presume configuration, one that >>>> virsh uses? >>>> thanks. >>>> P.

On 09/16/2014 08:15 AM, lejeczek wrote: > > On 16/09/14 13:46, Martin Kletzander wrote: >> On Tue, Sep 16, 2014 at 01:34:37PM +0100, lejeczek wrote: >>> hi all >>> where/how to change vim's I presume configuration, one that >>> virsh uses? >>> thanks. >>> P. >>> >> >> Well, virsh just starts an $EDITOR. Set it up

On Tue, Sep 16, 2014 at 01:34:37PM +0100, lejeczek wrote: >hi all >where/how to change vim's I presume configuration, one that >virsh uses? >thanks. >P. > Well, virsh just starts an $EDITOR. Set it up properly and you're good to go ;) Martin

On 03/10/14 17:15, Laine Stump wrote: > On 10/03/2014 11:38 AM, lejeczek wrote: >> hi everybody >> >> I'd presume virsh makes the best possible choice, right? >> It is that just seems bit... odd having realtek in guest and Intel's >> VF on host, no? > This can safely be ignored - in the case of an SRIOV VF that is assigned > to the guest using PCI

Hi: when I modify VM's xml file,the editor is VI,how to set to other editor forever? Now I can change the editor to VIM from VI with setting environment EDITOR=$my-favorite-editor, but after rebooting,it is VI again. thanks

hi everybody I'd presume virsh makes the best possible choice, right? It is that just seems bit... odd having realtek in guest and Intel's VF on host, no? regards

Hello dw, Can you plz try this method and check if it works: Set the preferred editor in /etc/environment file (to define it globally) and then restart the session. You may follow these links for more info on the topic. Link 1: https://www.redhat.com/archives/libvirt-users/2014-September/msg00039.html Link 2:

Hello, I found in the docs that I can change the editor I use on a per vm bases with the following: *EDITOR=$your-favorite-editor virsh edit $your-vm-name* But how do I change it permanently so when I run: *virsh edit $your-vm-name* It defaults to my favorite editor (vim)? Ref: http://wiki.libvirt.org/page/FAQ

On 03/03/2014 13:42, Martin Kletzander wrote: > On Mon, Mar 03, 2014 at 11:15:51AM +0000, Struan Bartlett wrote: >> On 03/03/2014 10:55, Martin Kletzander wrote: >>> On Mon, Mar 03, 2014 at 10:47:03AM +0000, Struan Bartlett wrote: >>>> On 03/03/2014 10:44, Martin Kletzander wrote: >>>>> On Mon, Mar 03, 2014 at 10:30:11AM +0000, Struan Bartlett wrote:

On 03/03/2014 10:55, Martin Kletzander wrote: > On Mon, Mar 03, 2014 at 10:47:03AM +0000, Struan Bartlett wrote: >> On 03/03/2014 10:44, Martin Kletzander wrote: >>> On Mon, Mar 03, 2014 at 10:30:11AM +0000, Struan Bartlett wrote: >>>> Hi Martin >>>> >>>> Thanks for your response. Here's the output of that grep: >>>>

hi Martin, thanks again for the feedback. maybe you have noted that I am not yet all too familiar with those tools. this is now sort of working for me. But I sense that you seem this method to be less then ideal. Reading through the virsh manual it looks like ... $ virsh snapshot-create [domain] --disk-only --live ... might be doing a similar thing. Maybe more elegant (pure virsh) and on a

On 03/03/2014 10:44, Martin Kletzander wrote: > On Mon, Mar 03, 2014 at 10:30:11AM +0000, Struan Bartlett wrote: >> Hi Martin >> >> Thanks for your response. Here's the output of that grep: >> >> # grep ^flags /proc/cpuinfo | sort -u >> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca >> cmov pat pse36 clflush dts acpi mmx

On 2 July 2013 10:36, Martin Kletzander <mkletzan@redhat.com> wrote: > I couldn't know you were able to do that. Since I presume you are using > the same server and client to check that, I must fallback to default > questions like "SELinux?". Or some OpenStack config which I > (unfortunately) know almost nothing about. Last thing that occurs on my > mind is

On 2 July 2013 09:58, Martin Kletzander <mkletzan@redhat.com> wrote: > I'd say this is a problem with sasl, nothing else. "No mechanism found" > may mean that libraries for configured mechanism aren't found or unknown > mechanism is being requested. I doubt that access to those libraries > would be a permisison problem, but you might be missing some >

I take an internal snapshot (VM is 'shutdown' when taking it) of a qcow2 image like this: $ qemu-img snapshot -c sn1 [my_image].qcow2 I see that snapshot when asking for: $ qemu-img info [my_image].qcow but do NOT see it with: $ virsh domblklist [my_domain] is that how it is meant to be?

hi guys I have a qemu guest and openvswitch bridge and the guest fails to start: $ virsh start work8 error: Failed to start domain work8-vm-win2016 error: Cannot get interface MTU on 'ovsbr0': No such device LXC guest which uses the same source network starts just fine. I'm on Centos 7 with openvswitch-2.9.0-3.el7.x86_64 from centos-openstack-pike repo and

On 29/09/14 16:28, Martin Kletzander wrote: > On Fri, Sep 26, 2014 at 08:16:25AM +0800, Bill Kenworthy wrote: >> Hi, >> I am using libvirt with qemu/kvm with qemu-guest-agent and >> suspend/save/resume linux and windows vm's. Time in Windows gets >> handled fine with ntp but I can get neither ntp or chrony to sync after >> resume without manually setting

hi everyone I wonder why, when I attach an interface like this: virsh # attach-interface --domain win10Ent --type direct --source nm-team --config --persistent --model virtio host cannot ip ping the guest and vice versa, yet guest can ping other nodes(outside of its host, connected via phys net via a switch) Would you know? I thought maybe routing on the host, so I did: $ route add -host

Logs from newly added node helped me in RCA of the issue. Info file on node 10.5.6.17 consist of an additional property "tier-enabled" which is not present in info file from other 3 nodes, hence when gluster peer probe call is made, in order to maintain consistency across the cluster cksum is compared. In this case as both files are different leading to different cksum, causing state in