Re: openVswitch won't get to a virtual IP
On 14/07/2021 16:12, Michal Prívozník wrote: On 7/14/21 3:54 PM, lejeczek wrote: Hi guys. Among all the mailing lists I'm subscriber of this one I thought, would where chances to find 'openvswitch'+'libvirtd' experts to share thoughts & suggestions should be grater. A case: a) all guests are KVM. b) I have NM managed OVS bridge and libvirtd network to/on that bridge c) "regular" NM bridge and network off it in libvirt problem is - guests on OVS network can _not_ ping a virtual IP of a guest(s) on 'regular' bridge network, but.. can ping "actual" IP of that same guest(s) okey. I'm not sure what you mean by: "actual" IP of that same guest. But in general, if you have two bridges you also have two separate subnets. So you want to set up routing between them. And also inspect rules that libvirt adds to its default network, because those might clash with your setup. Michal No need to complicate.. guestOVSa <-> guestBRa 10.3.3.1 => pings OK guestOVSa <-> guestBRa 10.3.3.2 virtual IP = cannot ping, "Destination Host Unreachable" The host on which guestOVSa resides pings both those IPs OKey. thanks for response Michal. L
Re: DAC & glusterFS - errors
On 08/07/2021 10:34, Michal Prívozník wrote: On 7/5/21 11:28 PM, lejeczek wrote: Hi guys I'm trying to spin up a VM whose image is on a GlusterFS vol, and I fail: -> $ virsh create /var/lib/pacemaker/conf.d/win10Pro.xml error: Failed to create domain from /var/lib/pacemaker/conf.d/win10Pro.xml error: failed to initialize gluster connection (src=0x7f0af807b410 priv=0x7f0af8090070): Invalid argument In logs: ... 2021-07-05 21:13:12.950+: 141524: warning : virSecurityDACSetOwnership:828 : Unable to restore label on 'win10Pro.qcow2'. XATTRs might have been left in inconsistent state. internal error: child reported (status=125): failed to initialize gluster connection (src=0x7f0b00097030 priv=0x7f0b000956c0): Invalid argument Any ideas & suggestions greatly appreciated. thanks, L. Hey, since this is gluster I wonder if it is related to this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1786301 That one is a deadlock scenario, but nevertheless might be worth turning off seclabel remembering to see if that's the root cause. Just set remember_owner=0 in /etc/libvirt/qemu.conf, restart libvirtd and see if the problem persists. Michal This error is, well, in my opinion quite misleading, as the problem turns out was - a non-existent GlusterFS Vol to which storage path pointed to in my guest/domain definition. Whether there were any other underlying problems I cannot say, don't know, but if you guys get those or similar to aforementioned errors, then I suggest check that 'obvious' bit. many thanks, L.
openVswitch won't get to a virtual IP
Hi guys. Among all the mailing lists I'm subscriber of this one I thought, would where chances to find 'openvswitch'+'libvirtd' experts to share thoughts & suggestions should be grater. A case: a) all guests are KVM. b) I have NM managed OVS bridge and libvirtd network to/on that bridge c) "regular" NM bridge and network off it in libvirt problem is - guests on OVS network can _not_ ping a virtual IP of a guest(s) on 'regular' bridge network, but.. can ping "actual" IP of that same guest(s) okey. any thoughts and ideas on how & what to investigate are very appreciated. many thanks, L.
Re: how to build a github release tarball
On Wed, Jul 14, 2021 at 04:44:43PM +0200, Martin Kletzander wrote: > On Wed, Jul 14, 2021 at 08:44:52PM +0800, Jiatong Shen wrote: > > Hello community, > > > > I am trying to figure out a way to build a release tarball like > > https://github.com/libvirt/libvirt/releases?after=v6.2.0, for libvirt > > 6.0.0, but don't know how. > > Could anyone teach me how to package it? thank you. > > If you look at https://libvirt.org/downloads.html then there is a link > to release tarballs: https://libvirt.org/sources/ This is definitely the way to go. > If you want to build it yourself, then something along the lines of > `meson build && ninja -C build dist` should do, but it should not be > needed. libvirt 6.0.0 was still using autotools ;) > Otherwise the tarball provided by github is just a snapshot of the git > tree at the point in time of the tag and build needs to be done the same > way as building from git. GitHub / GitLab "releases" are somewhere between git snapshots and proper release tarballs in terms of contents, and for projects such as libvirt they are basically unusable - the build process will break in interesting ways very quickly. Pretend they don't exist and grab a proper, signed source tarball from the location Martin pointed you to instead. -- Andrea Bolognani / Red Hat / Virtualization
Re: openVswitch won't get to a virtual IP
On 7/14/21 3:54 PM, lejeczek wrote: > Hi guys. > > Among all the mailing lists I'm subscriber of this one I thought, would > where chances to find 'openvswitch'+'libvirtd' experts to share thoughts > & suggestions should be grater. > > A case: > a) all guests are KVM. > b) I have NM managed OVS bridge and libvirtd network to/on that bridge > c) "regular" NM bridge and network off it in libvirt > > problem is - guests on OVS network can _not_ ping a virtual IP of a > guest(s) on 'regular' bridge network, but.. can ping "actual" IP of > that same guest(s) okey. I'm not sure what you mean by: "actual" IP of that same guest. But in general, if you have two bridges you also have two separate subnets. So you want to set up routing between them. And also inspect rules that libvirt adds to its default network, because those might clash with your setup. Michal
Re: how to build a github release tarball
On Wed, Jul 14, 2021 at 08:44:52PM +0800, Jiatong Shen wrote: Hello community, I am trying to figure out a way to build a release tarball like https://github.com/libvirt/libvirt/releases?after=v6.2.0, for libvirt 6.0.0, but don't know how. Could anyone teach me how to package it? thank you. If you look at https://libvirt.org/downloads.html then there is a link to release tarballs: https://libvirt.org/sources/ If you want to build it yourself, then something along the lines of `meson build && ninja -C build dist` should do, but it should not be needed. Otherwise the tarball provided by github is just a snapshot of the git tree at the point in time of the tag and build needs to be done the same way as building from git. Did that answer your question? Martin -- Best Regards, Jiatong Shen signature.asc Description: PGP signature
how to build a github release tarball
Hello community, I am trying to figure out a way to build a release tarball like https://github.com/libvirt/libvirt/releases?after=v6.2.0, for libvirt 6.0.0, but don't know how. Could anyone teach me how to package it? thank you. -- Best Regards, Jiatong Shen
Re: virsh qemu-monitor-command block_resize not working
On Wed, 14 Jul 2021 09:34:22 +0100 Daniel P. Berrangé wrote: > On Wed, Jul 14, 2021 at 10:10:35AM +0200, arjen-libv...@gugu.be wrote: > > Hi List, > > [sNap] > > > > In a previous qemu version this worked (EL 7). Can someone help me > > out? > > Libvirt has changed the way it configures disks with QEMU to use the > modern -blockdev argument. I expect this impacts your usage, but I > dont know what the correct naming should be. > > Ignoring that though, why are you even using qemu-monitor-command in > the first place ? Libvirt directly supports live block resizing > via the 'virsh blockresize' command Hah, didn't know that live resizing was implemented in virsh. Great! Thanks, Arjen.
Re: virsh qemu-monitor-command block_resize not working
On Wed, Jul 14, 2021 at 10:10:35AM +0200, arjen-libv...@gugu.be wrote: > Hi List, > > some version info: > ]# /usr/libexec/qemu-kvm -version > QEMU emulator version 4.2.0 > (qemu-kvm-4.2.0-48.module+el8.4.0+534+4680a14e) Copyright (c) 2003-2019 > Fabrice Bellard and the QEMU Project developers > > ]# virsh version > Compiled against library: libvirt 6.0.0 > Using library: libvirt 6.0.0 > Using API: QEMU 6.0.0 > Running hypervisor: QEMU 4.2.0 > > information about block devices for one specific guest: > ]# virsh qemu-monitor-command uat-win201202.uat.gugu.be --hmp info block > libvirt-2-format: > /data/kvm/storage/diskimages01/uat-win201202_disk1_C.qcow2 (qcow2) > Attached to: /machine/peripheral/virtio-disk0/virtio-backend Cache > mode: writeback > > ide0-0-0: [not inserted] > Attached to: ide0-0-0 > Removable device: not locked, tray closed > > > But then, when I want to resize the block device, I just cannot seem to > find the correct device. I tried all of these: > > virsh qemu-monitor-command uat-win201202.uat.gugu.be --hmp block_resize > libvirt-2-storage 48G > Error: Cannot find device=libvirt-2-storage nor node_name= > > virsh qemu-monitor-command uat-win201202.uat.gugu.be --hmp block_resize > drive-libvirt-2-storage 48G > Error: Cannot find device=drive-libvirt-2-storage nor node_name= > > virsh qemu-monitor-command uat-win201202.uat.gugu.be --hmp block_resize > virtio-disk0 48G > Error: Cannot find device=virtio-disk0 nor node_name= > > virsh qemu-monitor-command uat-win201202.uat.gugu.be --hmp block_resize > drive-virtio-disk0 48G > Error: Cannot find device=drive-virtio-disk0 nor node_name= > > In a previous qemu version this worked (EL 7). Can someone help me out? Libvirt has changed the way it configures disks with QEMU to use the modern -blockdev argument. I expect this impacts your usage, but I dont know what the correct naming should be. Ignoring that though, why are you even using qemu-monitor-command in the first place ? Libvirt directly supports live block resizing via the 'virsh blockresize' command Regards, Daniel -- |: https://berrange.com -o-https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o-https://fstop138.berrange.com :| |: https://entangle-photo.org-o-https://www.instagram.com/dberrange :|
virsh qemu-monitor-command block_resize not working
Hi List, some version info: ]# /usr/libexec/qemu-kvm -version QEMU emulator version 4.2.0 (qemu-kvm-4.2.0-48.module+el8.4.0+534+4680a14e) Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers ]# virsh version Compiled against library: libvirt 6.0.0 Using library: libvirt 6.0.0 Using API: QEMU 6.0.0 Running hypervisor: QEMU 4.2.0 information about block devices for one specific guest: ]# virsh qemu-monitor-command uat-win201202.uat.gugu.be --hmp info block libvirt-2-format: /data/kvm/storage/diskimages01/uat-win201202_disk1_C.qcow2 (qcow2) Attached to: /machine/peripheral/virtio-disk0/virtio-backend Cache mode: writeback ide0-0-0: [not inserted] Attached to: ide0-0-0 Removable device: not locked, tray closed But then, when I want to resize the block device, I just cannot seem to find the correct device. I tried all of these: virsh qemu-monitor-command uat-win201202.uat.gugu.be --hmp block_resize libvirt-2-storage 48G Error: Cannot find device=libvirt-2-storage nor node_name= virsh qemu-monitor-command uat-win201202.uat.gugu.be --hmp block_resize drive-libvirt-2-storage 48G Error: Cannot find device=drive-libvirt-2-storage nor node_name= virsh qemu-monitor-command uat-win201202.uat.gugu.be --hmp block_resize virtio-disk0 48G Error: Cannot find device=virtio-disk0 nor node_name= virsh qemu-monitor-command uat-win201202.uat.gugu.be --hmp block_resize drive-virtio-disk0 48G Error: Cannot find device=drive-virtio-disk0 nor node_name= In a previous qemu version this worked (EL 7). Can someone help me out? Best regards, Arjen Van Drie, Antwerp
