On Monday, January 7, 2019 at 8:56:36 PM UTC-5, pixel fairy wrote: > > On Thursday, January 3, 2019 at 4:51:12 PM UTC-8, 799 wrote: > > Am Fr., 4. Jan. 2019, 01:46 hat pixel fairy <[email protected]> > geschrieben: > > $ sudo qubes-dom0-update qubes-template-fedora-29 > > [...] > > > > Downloading Packages: > > > > [MIRROR] qubes-template-fedora-29-4.0.1-201812091508.noarch.rpm: Curl > error (23): Failed writing received data to disk/application for > https://mirrors.edge.kernel.org/qubes/repo/yum/r4.0/templates-itl/rpm/qubes-template-fedora-29-4.0.1-201812091508.noarch.rpm > > [Failed writing body (8615 != 16384)] > > > > [FAILED] qubes-template-fedora-29-4.0.1-201812091508.noarch.rpm: Curl > error (23): Failed writing received data to disk/application for > https://mirrors.edge.kernel.org/qubes/repo/yum/r4.0/templates-itl/rpm/qubes-template-fedora-29-4.0.1-201812091508.noarch.rpm > > [Failed writing body (8615 != 16384)] > > [...] > > > > > > Do you have enough free space in sys-firewall (df -h) > > > > > > - O > > That was the problem. made a clone of the template, gave it more system > storage, and used that for sys-firewall, which worked. >
I had this same issue and the same solution. Here is my question: Why does Qubes require me to increase the size of the *system storage* in order to enable a larger download in the updateVM (sys-firewall)? In other words, there is the sys-firewall "Private storage" (/dev/xvdb) and "System storage" (/dev/xvda3). I would think the update downloads to this VM (which are just destinated for another vm, in this case dom0) should go in private storage. Private storage setting is particular to the vm and can be set while it is running, etc. Also it is a payload that should have nothing to do with the running system of the VM (at least not at that moment). Instead, the downloads seem to be going to the system storage. This means, to make room for the updatevm download in sys-firewall, I have to go into the template settings, change the size -- which will affect every VM using this template, right? -- and then shut it down, and then reboot sys-firewall which is a big pain. In other words, enabling the download in dom0 means touching two other VMs just to get it working :-\ This seems wrong to me, because shouldn't downloads be kept far from the system files in sys-firewall? Is this an oversight or something intentional/required? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2c063bb5-b156-4c0c-8227-fdf2f1c71984%40googlegroups.com.
