Maybe one last thing, is that after I tried to create the machine in MAAS and gave the error, it is not shown in MAAS composed machines, but it is shown in virsh list --all, so I have to manually delete it
On Sat, Jan 18, 2020 at 9:15 AM Luis Alfonso Rodríguez Aragonés < [email protected]> wrote: > > > On Sat, Jan 18, 2020 at 12:37 AM Newell Jensen < > [email protected]> wrote: > >> $ virsh dumpxml <machin-name-that-maas-created-that-caused-issues> >> > root@node35:~# virsh dumpxml testers > > <domain type='kvm'> > > <name>testers</name> > > <uuid>ad6b59c9-76b5-4481-a0bb-dc896782f27e</uuid> > > <memory unit='KiB'>1048576</memory> > > <currentMemory unit='KiB'>1048576</currentMemory> > > <vcpu placement='static'>1</vcpu> > > <os> > > <type arch='x86_64' machine='pc-i440fx-bionic'>hvm</type> > > <boot dev='hd'/> > > </os> > > <features> > > <acpi/> > > <apic/> > > </features> > > <clock offset='utc'/> > > <on_poweroff>destroy</on_poweroff> > > <on_reboot>restart</on_reboot> > > <on_crash>restart</on_crash> > > <pm> > > <suspend-to-mem enabled='no'/> > > <suspend-to-disk enabled='no'/> > > </pm> > > <devices> > > <emulator>/usr/bin/qemu-system-x86_64</emulator> > > <controller type='pci' index='0' model='pci-root'/> > > <controller type='virtio-serial' index='0'> > > <address type='pci' domain='0x0000' bus='0x00' slot='0x05' > function='0x0'/> > > </controller> > > <controller type='usb' index='0' model='piix3-uhci'> > > <address type='pci' domain='0x0000' bus='0x00' slot='0x01' > function='0x2'/> > > </controller> > > <interface type='bridge'> > > <mac address='52:54:00:41:d7:d3'/> > > <source bridge='br1'/> > > <model type='virtio'/> > > <address type='pci' domain='0x0000' bus='0x00' slot='0x04' > function='0x0'/> > > </interface> > > <serial type='pty'> > > <log file='/var/log/libvirt/qemu/testers-serial0.log' append='off'/> > > <target type='isa-serial' port='0'> > > <model name='isa-serial'/> > > </target> > > </serial> > > <console type='pty'> > > <log file='/var/log/libvirt/qemu/testers-serial0.log' append='off'/> > > <target type='serial' port='0'/> > > </console> > > <channel type='spicevmc'> > > <target type='virtio' name='com.redhat.spice.0'/> > > <address type='virtio-serial' controller='0' bus='0' port='1'/> > > </channel> > > <input type='mouse' bus='ps2'/> > > <input type='keyboard' bus='ps2'/> > > <graphics type='spice' autoport='yes'> > > <listen type='address'/> > > <image compression='off'/> > > </graphics> > > <video> > > <model type='cirrus' vram='16384' heads='1' primary='yes'/> > > <address type='pci' domain='0x0000' bus='0x00' slot='0x02' > function='0x0'/> > > </video> > > <memballoon model='virtio'> > > <address type='pci' domain='0x0000' bus='0x00' slot='0x03' > function='0x0'/> > > </memballoon> > > </devices> > </domain> > > $ virsh pool-dumpxml <name-of-zfs-pool> >> > root@node35:~# virsh pool-dumpxml zpool > > <pool type='zfs'> > > <name>zpool</name> > > <uuid>93a40940-eed8-47a7-8eba-3559e83bb24c</uuid> > > <capacity unit='bytes'>1245540515840</capacity> > > <allocation unit='bytes'>782941757440</allocation> > > <available unit='bytes'>462598758400</available> > > <source> > > <name>zpool</name> > > </source> > > <target> > > <path>/dev/zvol/zpool</path> > > </target> > </pool> > > I had the pool created as mirror of two HDD partitions with no custom > parameters: > > zpool create zpool -m /data/zpool mirror /dev/sda4 /dev/sdb4 > > virsh pool-define-as --name zpool --source-name zpool --type zfs > > virsh pool-start zpool > > virsh pool-autostart zpool > > $ /sbin/zfs create -s -V 8789063K >> zpool/52a7cb41-4241-4336-b624-1f930ff398ed >> > root@node35:~# /sbin/zfs create -s -V 8789063K > zpool/52a7cb41-4241-4336-b624-1f930ff398ed > > cannot create 'zpool/52a7cb41-4241-4336-b624-1f930ff398ed': volume size > must be a multiple of volume block size > root@node35:~# > >> >> Christian, if there are any other specific commands that you know that >> Luis should execute since he has his setup still, please let him know. >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1858201 >> >> Title: >> volume size pod zfs >> >> Status in MAAS: >> Triaged >> Status in libvirt package in Ubuntu: >> Incomplete >> >> Bug description: >> I am trying to create a pod on a MAAS node that has virsh installed, >> I added a specific ZFS storage pool >> >> And when trying to create the pod I see the following error on >> /var/log/syslog >> >> Jan 03 18:13:00 node34 libvirtd[3340]: 2020-01-03 12:43:00.310+0000: >> 3341: error : virCommandWait:2601 : internal error: Child process >> (/sbin/zfs create -s -V 8789063K >> zpool/52a7cb41-4241-4336-b624-1f930ff398ed) unexpected exit status 1: >> cannot create 'zpool/52a7cb41-4241-4336-b624-1f930ff398ed': volume >> size must be a multiple of volume block size >> >> >> Any setting for the volume size in GB doesn't match the 8K volume block >> that ZS requires >> >> >> On MAAS while executing the "Create Pod" button I get the following >> error: >> >> Add another device >> Pod unable to compose machine: Unable to compose machine because: >> Failed talking to pod: Start tag expected, '<' not found, line 1, column 1 >> (<string>, line 1) >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/maas/+bug/1858201/+subscriptions >> > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858201 Title: volume size pod zfs To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1858201/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
