Re: Issue accidentally creating a '--type' defined pool

On 9/29/23 11:40, Joshua Blake wrote: > Hello, > > I seem to have accidentally created a pool called "--type", but it > doesn't appear in 'virsh pool-list'. See below. > > [root@vh01 /]# virsh pool-define-as --name --type dir --target > /data/storage/ > Pool --type defined > > [root@vh01 /]# vir

Re: Issue accidentally creating a '--type' defined pool

On Fri, Sep 29, 2023 at 09:40:26AM +, Joshua Blake wrote: > Hello, > > I seem to have accidentally created a pool called "--type", but it doesn't > appear in 'virsh pool-list'. See below. > > [root@vh01 /]# virsh pool-define-as --name --type dir --target > /data/storage/ > Pool --type defined

Re: Issue accidentally creating a '--type' defined pool

I think I fixed it. Sorry. I went into Cockpit and saw it there. -- Original Message -- From "Joshua Blake" To libvirt-users@redhat.com Date 29/09/2023 10:40:26 Subject Issue accidentally creating a '--type' defined pool Hello, I seem to have accidentally created a pool called "--t

Re: Issue with libvirtd service and virsh on Debian 13 "trixie" (testing)

On 7/14/23 10:29, pascal wrote: Hi, I just upgraded to Debian 13 and observing an issue related to libvirtd service. It happens during up time, the service is initially  running and all is working fine. I can run virt-manager and use VMs. Then close virt-manager. After some time (5min), here is

Re: issue about libvirtd: daemon can not start

On Fri, May 5, 2023 at 3:13 PM 王东亚 wrote: > hi, > > I installed kmv on ubuntu-22.04-desktop-amd64, after installing some > necessary package (qemu-kvm libvirt-daemon-system libvirt-clients > bridge-utils virtinst), the libvirtd can not get start, actually, when I > running *systemctl start li

Re: issue when not using acpi indices in libvirt 7.4.0 and qemu 6.0.0

On Thu, 24 Jun 2021 at 04:11, Laine Stump wrote: > [...] > Hi Laine, Thank you so much for your analysis and thoughtful insights. As you noticed straight away, there were indeed some minor differences in the two VM definitions that I didn't see before posting. The interface naming was not biase

Re: issue when not using acpi indices in libvirt 7.4.0 and qemu 6.0.0

On 6/23/21 7:37 PM, Riccardo Ravaioli wrote: On Wed, 23 Jun 2021 at 18:59, Daniel P. Berrangé > wrote: [...] So your config here does NOT list any ACPI indexes Exactly, I don't list any ACPI indices. > After upgrading to libvirt 7.4.0 and qemu 6.0.0

Re: issue when not using acpi indices in libvirt 7.4.0 and qemu 6.0.0

On Wed, 23 Jun 2021 at 18:59, Daniel P. Berrangé wrote: > [...] > So your config here does NOT list any ACPI indexes > Exactly, I don't list any ACPI indices. > > After upgrading to libvirt 7.4.0 and qemu 6.0.0, the XML snippet above > > yielded: > > - ens1 for the first virtio interface => OK

Re: issue when not using acpi indices in libvirt 7.4.0 and qemu 6.0.0

On Wed, Jun 23, 2021 at 06:49:12PM +0200, Riccardo Ravaioli wrote: > Hi everyone, > > We have an issue with how network interfaces are presented in the VM with > the latest libvirt 7.4.0 and qemu 6.0.0. > > Previously, we were on libvirt 7.0.0 and qemu 5.2.0, and we used increasing > virtual PCI

Re: Issue

On 3/5/21 11:04 AM, Samuel Thampy wrote: Is there any additional info anyone who needs? *From:* Samuel Thampy *Sent:* 03 March 2021 22:11 *To:* libvirt-users@redhat.com *Subject:* Issue I have a storage backend san disks,

Re: Issue

Is there any additional info anyone who needs? From: Samuel Thampy Sent: 03 March 2021 22:11 To: libvirt-users@redhat.com Subject: Issue I have a storage backend san disks, I have five servers which is KVM hosted guests. I am looking to clone an image of a gue