-
Posts
2801 -
Joined
-
Last visited
-
Days Won
9
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by DZMM
-
-
I think the culprit might be the Rclone plugin - all was ok when I tried to find the culprit until I started my rclone upload job.
@Waseh I'm not sure if there's anything you can or need to do to fix. I have a rclone vfs mount which seemed fine, but when I start my upload that seems to be the trigger for problems
Will try some more testing over the weekend
rclone move /mnt/user/rclone_upload/google_vfs/ gdrive_media_vfs: -vv --drive-chunk-size 512M --checkers 3 --fast-list --transfers 2 --exclude .unionfs/** --exclude *fuse_hidden* --exclude *_HIDDEN --exclude .recycle** --exclude *.backup~* --exclude *.partial~* --bwlimit 9500k --tpslimit 4
-
-
15 minutes ago, Squid said:
Unless I'm mistaken, (could very well be)
Means that when changing the CPU pinning on the VM, if the VM has an emulator pin entry in the XML, then it will be preserved.
It does:
-
Changed Status to Solved
-
I'll have to wait until everyone's gone to sleep to try safe mode
Edit: just tried again and it's working
-
1 hour ago, Squid said:
The GUI will allow you to assign multiple isolated cores to a container. The theory is that you should know exactly what you are doing should you do this.
On the CPU pinning page in Settings, its easy to bounce back and forth to see if there is a conflict. Fix Common Problems however will also look for a conflict between isolated cores and multiple core pinning to docker containers and issue a warning.
Wouldn't it be easier to have the right information in the help details, or to not allow users to try and apply settings that won't work? We're not talking about making changes via command line where yes, you should know what you are doing before attempting, but via a GUI.
-
Probably - closing
-
Changed Status to Solved
-
-
1 hour ago, bonienl said:
Please provide your XML file and tell which custom settings are lost.
CPU pinning only touches the CPU assignment section and all other settings should stay as is.
Ok, that makes sense - I lost my emulatorpin line which is part of the <cputune> section. Probably worth noting that somewhere:
<?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='4'> <name>Baymax</name> <uuid>6a29f72f-ad96-798a-7070-653c59281e4a</uuid> <metadata> <vmtemplate xmlns="unraid" name="FreeBSD" icon="freebsd.png" os="freebsd"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>6</vcpu> <cputune> <vcpupin vcpu='0' cpuset='11'/> <vcpupin vcpu='1' cpuset='25'/> <vcpupin vcpu='2' cpuset='12'/> <vcpupin vcpu='3' cpuset='26'/> <vcpupin vcpu='4' cpuset='13'/> <vcpupin vcpu='5' cpuset='27'/> <emulatorpin cpuset='1,15'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.11'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/6a29f72f-ad96-798a-7070-653c59281e4a_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='3' threads='2'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disks/sm961/domains/Baymax/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='usb'/> <boot order='1'/> <alias name='usb-disk2'/> <address type='usb' bus='0' port='1'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/disks/sm961/iso/pfSense-CE-2.4.3-RELEASE-amd64.iso'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:74:8a:53'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-4-Baymax/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='2'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-gb'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x09' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x09' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>
-
1 hour ago, bonienl said:
Switch to Advanced view and remove the entry from "extra parameters"
That's how I updated all my other dockers - for some reason this one wouldn't let me.
In the end I removed the docker and re-installed via CA and all is ok now.
Not sure what happened
-
I've just joined the 6.6rc family and loving it so far as things feel zippier (except for the docker page) and the cpu pinning page's visual representation has already helped me fix a VM CPU allocation error that must have been there for ages.
I have a question about the CPU Isolation help paragraph:
QuoteCPU isolation allows the user to specify CPU cores that are to be explicitly reserved for assignment (to VMs or Docker containers).
Can I check the VMs or Docker containers section is correct please as I asked this previously and was told that if you isolate CPUs then those CPUs wouldn't be available for dockers. I'm confident the RC version is correct; I'm just double-checking
If correct, this is brilliant as I can keep non-priority dockers away from VMs and let priority ones like Plex have access to all cores if needed
-
4 hours ago, bonienl said:
This is the way docker version 12.09.1 displays stat information. A newer docker version is planned after more testing is done, scheduled for the moment for 6.6.Run the following:
docker stats $(docker ps --format='{{.Names}}')
CONTAINER CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS cAdvisor 4.49% 62.41MiB / 125.9GiB 0.05% 936B / 0B 43.9MB / 0B 44 Netdata 1.82% 117.4MiB / 125.9GiB 0.09% 3.69kB / 0B 99.6MB / 0B 22 Emby 0.00% 72.8MiB / 125.9GiB 0.06% 613kB / 1.97MB 162MB / 19.3MB 16 Heimdall 0.00% 23.98MiB / 125.9GiB 0.02% 3.99kB / 3.35kB 3.11MB / 139kB 14 Tautulli 0.15% 75.05MiB / 125.9GiB 0.06% 0B / 0B 44.6MB / 139kB 20 HandBrake 0.24% 282.4MiB / 125.9GiB 0.22% 3.69kB / 0B 270MB / 279kB 70 Unifi 0.76% 658.8MiB / 125.9GiB 0.51% 9.41MB / 925kB 363MB / 95.5MB 909 Plex 0.11% 185.1MiB / 125.9GiB 0.14% 2.49MB / 551kB 151MB / 1.09MB 48 Nginx 0.02% 36.5MiB / 125.9GiB 0.03% 321kB / 0B 44.6MB / 139kB 25 Pi-hole 0.03% 43.48MiB / 125.9GiB 0.03% 2.72MB / 599kB 104MB / 86MB 22 Tonido 0.03% 21.11MiB / 125.9GiB 0.02% 380kB / 1.85MB 55.7MB / 2.92MB 28
Or, and select which columns to display (example below has all columns)
docker stats --format='table {{.Name}}\t{{.CPUPerc}}\t{{.MemUsage}}\t{{.MemPerc}}\t{{.NetIO}}\t{{.BlockIO}}\t{{.PIDs}}'
thx - pity as 'docker stats' was much easier to remember obviously
6.6.0RC4 - nginx upstream timed errors
-
-
-
-
-
in Prereleases
Posted
Changed Status to Closed