Hi 

 

I had problem with libvert before, I recreated it (changed path in settings) and that one was solved, but I still can't create any VM, when I go to ADD VM and select template, I can see only bland page, with nothing on it.

 

What should I do?

unraid-diagnostics-20220103-1750.zip

 

 

nothing? 

Is it because everyone is on vacation right now, or just there is nothing we can do? ;]

Not seeing any issue in the logs, try rebooting in safe mode and post new diags if it still doesn't work.

Hi,

 

New diagnostics and new problem, twice during last week kernel panic happens, what the hell...

 

I have this server and this configuration for the last two years almost, and everything was ok. Now it's far from being ok...

 

 

 

unraid-diagnostics-20220111-1033.zip

Jan 11 03:38:06 unRaid kernel: macvlan_broadcast+0x10e/0x13c [macvlan]
Jan 11 03:38:06 unRaid kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan]

 

Macvlan call traces are usually the result of having dockers with a custom IP address, upgrading to v6.10 and switching to ipvlan might fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.

https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/

See also here:

https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

Thanks for pointing the direction

I did exactly that, updated, changed to ipvlan 

restart didn't do anything, tab VM was still not loading new VM template

 

after couple of restarts (winter power outages in the area ) it magically started to work...

 

but if the new VM is now showing what it should none of the VMs are

 

nothing is starting (the green arrow says it is but it's not)... VNC is not working, logs shows the same for all of the machines

Spoiler

ErrorWarningSystemArrayLogin


-uuid 4913dcaf-c849-9787-a605-050a50926da9 \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=34,server=on,wait=off \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=utc,driftfix=slew \
-global kvm-pit.lost_tick_policy=delay \
-no-hpet \
-no-shutdown \
-boot strict=on \
-device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \
-device pcie-root-port,port=0x15,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x5 \
-device pcie-root-port,port=0x11,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x1 \
-device pcie-root-port,port=0x12,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x2 \
-device pcie-root-port,port=0x13,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x3 \
-device pcie-root-port,port=0x14,chassis=6,id=pci.6,bus=pcie.0,addr=0x2.0x4 \
-device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 \
-device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 \
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 \
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x7.0x2 \
-device virtio-serial-pci,id=virtio-serial0,bus=pci.3,addr=0x0 \
-blockdev '{"driver":"file","filename":"/mnt/user/domains/home_assistant/haos_ova-7.2.vmdk","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-1-storage"}' \
-device virtio-blk-pci,bus=pci.2,addr=0x0,drive=libvirt-1-format,id=virtio-disk2,bootindex=1,write-cache=on \
-netdev tap,fd=36,id=hostnet0 \
-device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:9d:8c:58,bus=pci.1,addr=0x0 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=37,server=on,wait=off \
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \
-device usb-tablet,id=input0,bus=usb.0,port=1 \
-audiodev id=audio1,driver=none \
-vnc 0.0.0.0:0,websocket=5700,audiodev=audio1 \
-k en-us \
-device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 \
-device virtio-balloon-pci,id=balloon0,bus=pci.5,addr=0x0 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
char device redirected to /dev/pts/2 (label charserial0)
qxl_send_events: spice-server bug: guest stopped, ignoring

 

 

 

 

unraid-diagnostics-20220125-1422.zip

1 hour ago, Mrobert said:

I did exactly that, updated, changed to ipvlan 

restart didn't do anything, tab VM was still not loading new VM template

That's expected, the change above it to avoid Unraid crashing, nothing to do with VMs working or not.

6 minutes ago, JorgeB said:

That's expected, the change above it to avoid Unraid crashing, nothing to do with VMs working or not.

 

;))

 

oh, ok, nice to have one of them then

 

Ok, do we (and by we I mean You ) have any solution to the VM problem? 

I most definitely do need them

6 minutes ago, Mrobert said:

You ) have any solution to the VM problem? 

Not really, but someone else might have.

Is that how your VM page actually looks? With cutoff text on "Main" (and still highlighted) while you're on the VM tab?  Try it in safe mode from the boot menu

Ni @Squid 

sorry for created confusion

 

So the cut Menu is because of print-screen delay I think I may moved mouse up to Main when the screen shot app kicked.

 

My VM tab is working (meaning I can create new VM) but I can not start any of my VMs (old or new ones)

 

On 1/25/2022 at 2:27 PM, Mrobert said:

Thanks for pointing the direction

I did exactly that, updated, changed to ipvlan 

restart didn't do anything, tab VM was still not loading new VM template

 

after couple of restarts (winter power outages in the area ) it magically started to work...

 

but if the new VM is now showing what it should none of the VMs are

 

nothing is starting (the green arrow says it is but it's not)... VNC is not working, logs shows the same for all of the machines

  Hide contents

ErrorWarningSystemArrayLogin


-uuid 4913dcaf-c849-9787-a605-050a50926da9 \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=34,server=on,wait=off \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=utc,driftfix=slew \
-global kvm-pit.lost_tick_policy=delay \
-no-hpet \
-no-shutdown \
-boot strict=on \
-device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \
-device pcie-root-port,port=0x15,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x5 \
-device pcie-root-port,port=0x11,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x1 \
-device pcie-root-port,port=0x12,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x2 \
-device pcie-root-port,port=0x13,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x3 \
-device pcie-root-port,port=0x14,chassis=6,id=pci.6,bus=pcie.0,addr=0x2.0x4 \
-device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 \
-device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 \
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 \
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x7.0x2 \
-device virtio-serial-pci,id=virtio-serial0,bus=pci.3,addr=0x0 \
-blockdev '{"driver":"file","filename":"/mnt/user/domains/home_assistant/haos_ova-7.2.vmdk","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-1-storage"}' \
-device virtio-blk-pci,bus=pci.2,addr=0x0,drive=libvirt-1-format,id=virtio-disk2,bootindex=1,write-cache=on \
-netdev tap,fd=36,id=hostnet0 \
-device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:9d:8c:58,bus=pci.1,addr=0x0 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=37,server=on,wait=off \
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \
-device usb-tablet,id=input0,bus=usb.0,port=1 \
-audiodev id=audio1,driver=none \
-vnc 0.0.0.0:0,websocket=5700,audiodev=audio1 \
-k en-us \
-device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 \
-device virtio-balloon-pci,id=balloon0,bus=pci.5,addr=0x0 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
char device redirected to /dev/pts/2 (label charserial0)
qxl_send_events: spice-server bug: guest stopped, ignoring

 

 

 

 

unraid-diagnostics-20220125-1422.zip 225.29 kB · 1 download

 

Nothing?

 

I wonder if you can try something.

 

Can you stop the VM service via Settings - VM Manager.  Once it's stopped, switch to Advanced View and change the name of the libvirt.img file (ie: call it test.img instead)

 

Restart the service and see if you can't add a VM now (NOTE that none of your existing VMs will appear because we've set the libvirt image to be something else)

 

It's not going to solve you problem, but it will narrow it down.

 

A

Hi AndrewZ

 

I'm not sure if I got it right, stop the VM Manager, and just type different name in the libvirt location?

 

It marks it red and I can not save it (apply button is not doing anything)

 

Huh.  Try just leaving the name alone and switch the share that it's in.  (It seems to work changing the name occasionally.  I have to investigate why on that one)

\

 

 

 

OK.  So the net result of the test was that the VM tab worked and you could actually add a VM?

18 hours ago, Squid said:

OK.  So the net result of the test was that the VM tab worked and you could actually add a VM?

 

so VM tab work, I can add/edit/remove VMs but

they are not starting (the green triangle icon says Started, but it's not...)

 

(messages above) 

Was the new VM pointed to the original VDisks or created by copying and pasting an xml or was it basically a stock VM as a test?

Ok, something may be seriously wrong with your gear or setup.  VMs "just work" especially when there is no pass through of PCI device involved.  I would be very suspicious of your USB flash device (could be corrupted) or the memory (might be bad).  That said, let's try starting from scratch and having you take screenshots along the way.  First, let's delete your existing libvirt image and create a new one.

1. Navigate to the VM Manager Settings page (Settings > VM Manager).
2. Stop the VM service (Enable VMs > No > Apply).
3. Make sure the path for libvirt image file is /mnt/user/system/libvirt/libvirt.img.
4. Delete the libvirt image file (VM Manger Settings > libvirt storage location > click "delete" checkbox and click "apply")
5. Start the VM manager service again (Enable VMs > Yes > Apply).

Now if you go to the VMs tab, you should see no VMs defined there.  Go ahead and try to create one.  Before creating, take a screenshot of the settings you have configured for the VM.  Once you click create, if any error message pops up, screenshot that as well.  If no errors show up but the VM doesn't start, navigate to the Tools > Diagnostics page and download the diagnostics zip from there and attach it to a new forum post reply here.  We can then try to figure out what's going on.

 

For starters, thank you so much for helping,

 

sorry I left you hanging for so long, I had a business trip and was out of the country for the last two weeks.

I'm back and really want to make this work again, will be here twice a day to keep it moving now. Sorry again.

 

 

On 2/14/2022 at 10:21 AM, AndrewZ said:

 

 

Was the new VM pointed to the original VDisks or created by copying and pasting an xml or was it basically a stock VM as a test?

 

 

The VM is a qcow disk downloaded from the HomeAssistant web page

 

On 2/14/2022 at 7:01 PM, jonp said:

Ok, something may be seriously wrong with your gear or setup.  VMs "just work" especially when there is no pass through of PCI device involved.  I would be very suspicious of your USB flash device (could be corrupted) or the memory (might be bad).  That said, let's try starting from scratch and having you take screenshots along the way.  First, let's delete your existing libvirt image and create a new one.

1. Navigate to the VM Manager Settings page (Settings > VM Manager).
2. Stop the VM service (Enable VMs > No > Apply).
3. Make sure the path for libvirt image file is /mnt/user/system/libvirt/libvirt.img.
4. Delete the libvirt image file (VM Manger Settings > libvirt storage location > click "delete" checkbox and click "apply")
5. Start the VM manager service again (Enable VMs > Yes > Apply).

Now if you go to the VMs tab, you should see no VMs defined there.  Go ahead and try to create one.  Before creating, take a screenshot of the settings you have configured for the VM.  Once you click create, if any error message pops up, screenshot that as well.  If no errors show up but the VM doesn't start, navigate to the Tools > Diagnostics page and download the diagnostics zip from there and attach it to a new forum post reply here.  We can then try to figure out what's going on.

 

Done,

Mission Failed Successfully

 

 

 

diagnostics:

unraid-diagnostics-20220301-2309.zip

Edited March 1, 20224 yr by Mrobert