January 26, 20215 yr Hi at all Since I restarted the nextcloud VM, there is just the following in my browser: 502 Bad Gateway openresty failure I can't ping the IP of the instance. If I look inside the VM with VNC there is no network configuration available. At first i thought it has to be a problem with nextcloud. However, it must be due to unraid cause I tried to start the vm from a backup disk.img, but there is the same problem. That's why I think it is aproblem with unraid not with nextcloud. When I look at the log there is the following. I think the last 3 lines are not ok. But what can I do? I have also the diagnostic file attached. Would be very nice if someone can help me. This instance runs since 8 months without any problem. Now I can't work anymore... thank you in advance greg -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=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 \ -device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 \ -device pcie-root-port,port=0x1c,chassis=4,id=pci.4,bus=pcie.0,addr=0x3.0x4 \ -device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 \ -device pcie-root-port,port=0x15,chassis=6,id=pci.6,bus=pcie.0,addr=0x2.0x5 \ -device pcie-root-port,port=0x16,chassis=7,id=pci.7,bus=pcie.0,addr=0x2.0x6 \ -device pcie-root-port,port=0x17,chassis=8,id=pci.8,bus=pcie.0,addr=0x2.0x7 \ -device pcie-root-port,port=0x18,chassis=9,id=pci.9,bus=pcie.0,multifunction=on,addr=0x3 \ -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/Debian/vdisk1.img","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.6,addr=0x0,drive=libvirt-1-format,id=virtio-disk2,bootindex=1,write-cache=on \ -fsdev local,security_model=passthrough,id=fsdev-fs0,path=/mnt/user/nc_share_unraid/ \ -device virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=nc_share_unraid,bus=pci.1,addr=0x0 \ -netdev tap,fd=33,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:ef:82:8e,bus=pci.4,addr=0x0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=34,server,nowait \ -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 \ -vnc 0.0.0.0:0,websocket=5700 \ -k de-ch \ -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 2021-01-27 00:07:13.067+0000: Domain id=2 is tainted: high-privileges 2021-01-27 00:07:13.067+0000: Domain id=2 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) sm-tower-8575-diagnostics-20210127-0011.zip
January 28, 20215 yr Author Hi there I realised that if I change in the VM configuration the machine from Q35-5.1 to Q35-4.0 the VM starts normal. But why did it work before? I did nothing change at all. And what is the difference between the two machines? Would be nice if someone give me advice to that. thank you. Greg
Archived
This topic is now archived and is closed to further replies.