July 21, 20169 yr I have been experiencing some issues with my VM just shutting off, which I believe I have narrowed down to needing more RAM. However, when I try to create a new VM I get the following error: cannot write data to file '/var/run/libvirt/qemu/[NameofVM].xml.new': No space left on device. After searching around the forums I ran across this thread: https://lime-technology.com/forum/index.php?topic=42919.0 I followed jonp's instructions for configuring a new USB, however, I still get the issue: I suspect your flash device is nearing the end of its life. The configuration for VMs is stored in a loopback image on the flash device. Typically a file can get renamed to .new when a system crash or other major event occurs while trying to add a new or update an existing VM. How old is the USB flash device you are using? The steps would be to format a new USB flash device (preferably a quality brand as we recommend on our website) and then copy the files over from the old flash to the new, then running make bootable on the new flash stick. You will then need to boot up and initiate a registration key transfer which you can do through the webgui. This will transfer your key to the new flash device. I realized that my issue didn't totally line up with the other users as I do not have the plugin that was causing his issues nor did I experience an array rebuild. Another thing that I noticed is that after trying to create the VM and upon receiving the error my shares are not available for roughly 5 minutes. I tried generating diagnostics and system log to post but I am getting a 404 File not found page for both files. Any help would be much appreciated. I guess the first step would be to get the log issue figured out. Edit #1: Here is the link to my domain.img: https://drive.google.com/open?id=0B5FQeJW99h6zM3NhdmtyZm1IRWs Edit #2: The issue still occurs even after trying the following from jonp: 1 - With the array started (and the VMs tab visible), click on each vm and select Edit XML. From there, copy the entire contents of the XML and store it in a notepad somewhere for safe keeping temporarily. 2 - Goto Settings -> VM Manager and set Enable VMs to No, then click Apply. 3 - On your flash device, delete the domain.img file I directed you to upload previously. 4 - Go back to Settings -> VM Manager and set Enable VMs to Yes, then click Apply. 5 - Go to the VMs tab. It will be empty (your VMs will not show up there; this is expected). 6 - Click Add VM and select XML Expert from the template drop down. 7 - Paste the XML for one of your VMs there (that you copied to a notepad earlier). 8 - Click Add VM. 9 - Repeat the above process for each VM you wish to re-add. Let me know if the issue occurs again after you've followed this process.
July 21, 20169 yr If you copied over all the old config files to the new USB, it's not strange that it's the same problem. Either your libvirt loopback image is full or corrupted. Try to stop libvirt in VM settings, rename the file and enable libvirt again. It should now create a new libvirt image, I think....
July 21, 20169 yr Author If you copied over all the old config files to the new USB, it's not strange that it's the same problem. Either your libvirt loopback image is full or corrupted. Try to stop libvirt in VM settings, rename the file and enable libvirt again. It should now create a new libvirt image, I think.... Not sure I understand why this would be different from what I tried in Edit#2. Nonetheless I tried it and it created a new domain.img, however, I still get the same error when creating a VM.
July 21, 20169 yr If you copied over all the old config files to the new USB, it's not strange that it's the same problem. Either your libvirt loopback image is full or corrupted. Try to stop libvirt in VM settings, rename the file and enable libvirt again. It should now create a new libvirt image, I think.... Not sure I understand why this would be different from what I tried in Edit#2. Nonetheless I tried it and it created a new domain.img, however, I still get the same error when creating a VM. As you're not able to get the diagnostic either, I suspect you have a hardware problem. Have you tried running memtest to see if the memory might be bad? Also post your hardware specs.
July 21, 20169 yr Author If you copied over all the old config files to the new USB, it's not strange that it's the same problem. Either your libvirt loopback image is full or corrupted. Try to stop libvirt in VM settings, rename the file and enable libvirt again. It should now create a new libvirt image, I think.... Not sure I understand why this would be different from what I tried in Edit#2. Nonetheless I tried it and it created a new domain.img, however, I still get the same error when creating a VM. As you're not able to get the diagnostic either, I suspect you have a hardware problem. Have you tried running memtest to see if the memory might be bad? Also post your hardware specs. I have not run a memtest, I'll have to run it later when I get home. While we wait on the results of a memtest here are my hardware specs for you to digest: CPU: AMD Athlon X4 860K Kaveri Quad-Core 3.7 GHz Socket FM2+ 95W AD860KXBJABOX Desktop Processor (BLACK EDITION) RAM: G.SKILL Ripjaws Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model F3-12800CL9D-8GBRL MOBO: GIGABYTE GA-F2A88XM-D3H FM2+ / FM2 AMD A88X (Bolton D4) SATA 6Gb/s USB 3.0 HDMI Micro ATX AMD Motherboard PSU: Thermaltake Toughpower TPD-0750M - SLI/ CrossFire Ready 80 PLUS Gold Certification and Semi Modular Cables Black ... I've also noticed that my RAM usage has slowly been creeping up over the last couple days. With nothing more than my dockers running. It is currently at 71% usage.
July 21, 20169 yr How much ram and cores have you assigned for your VM? Do you try to create the new VM while the the first one is running?
July 21, 20169 yr Author How much ram and cores have you assigned for your VM? Do you try to create the new VM while the the first one is running? For the VM that I have always had and has been working up until these issues: 3 Cores 2 Gig of Ram XML: <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>BennyHTPC</name> <uuid>9823f860-5a24-bdd5-ab27-51b090f854bc</uuid> <description>Home Theater PC</description> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>3</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='3' threads='1'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/Config/VMs/BennyHTPC/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/Config/Images/Windows8.1.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/Config/Images/virtio-win-0.1.102.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:a6:c7:af'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/BennyHTPC.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=00.1'/> </qemu:commandline> </domain> For the one that I have been trying to create: 2 Cores, 2 Gig. And I wasn't planning on running them simultaneous. Also read that I shouldn't run Windows VMs or any VMs for that matter from the array and that I should run them from a cache pool. I currently do no have any cache drives. I guess I should order one. However, I do not believe this has anything to do with what I am experiencing. I rebooted my server and was able to get a diagnostics and system log. My memory usage is down to 17% and holding, if a VM runs away with memory and shuts itself off due to low memory will it continue to keep consuming it while it is powered off? Also after reboot I was able to start a VM as well create a new one. bennysrv-syslog-20160721-1355.zip bennysrv-diagnostics-20160721-1354.zip
July 21, 20169 yr Author Is this the first time you have rebooted your server since getting the problem? Its the first time I have rebooted since making this post. Everything seems to be okay, for now.
Archived
This topic is now archived and is closed to further replies.