bender1 Posted January 2, 2016 Share Posted January 2, 2016 Have tried creating a VM with a variety of settings and get the same error each time. I've tried enabling and disabling PCIe ACS override, I've tried using SeaBIOS and OVMF as well as several different OS ISO's (Ubuntu server 15.04, lubuntu, slack) with no luck. Same message every time. I'm not trying to pass-through any devices....yet. What am I doing wrong? char device redirected to /dev/pts/0 (label charserial0) qemu: terminating on signal 15 from pid 10844 2016-01-02 17:09:09.357+0000: shutting down 2016-01-02 17:13:08.717+0000: starting up libvirt version: 1.2.18, qemu version: 2.3.0 Domain id=1 is tainted: high-privileges Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) I have run Unraid 6 with VM's on this exact hardware. Only thing that changed was Unraid config. I started fresh with my flash drive. Things had become a bit messy after 5 or so years of running various plugins, docker containers, vm's and a multitude of shares. Any ideas? Quote Link to comment
CHBMB Posted January 2, 2016 Share Posted January 2, 2016 Have you set up a bridge? Quote Link to comment
bender1 Posted January 2, 2016 Author Share Posted January 2, 2016 yes! I didn't try disabling that, although it worked before. I'll disable it and see if that helps. Quote Link to comment
CHBMB Posted January 2, 2016 Share Posted January 2, 2016 yes! I didn't try disabling that, although it worked before. I'll disable it and see if that helps. I wouldn't have thought disabling it would make any difference, if anything, less likely to work... Changed anything in your BIOS? Might be worth checking... Quote Link to comment
bender1 Posted January 2, 2016 Author Share Posted January 2, 2016 That worked. Didn't disable the bridge, just told the vm to use the default bridge instead of br0. Do you know the cause/solution? Thank you! Quote Link to comment
CHBMB Posted January 2, 2016 Share Posted January 2, 2016 So you're using virbr0? Only problem with that is I think you get an IP from a different subnet than the rest of your LAN Quote Link to comment
bender1 Posted January 2, 2016 Author Share Posted January 2, 2016 correct, need to get it back to br0 for networking. When I change it back to br0, the vm starts but the same errors pop up in the logs. Quote Link to comment
CHBMB Posted January 2, 2016 Share Posted January 2, 2016 correct, need to get it back to br0 for networking. When I change it back to br0, the vm starts but the same errors pop up in the logs. And you've definitely gone to settings ==> network settings and created the bridge? Quote Link to comment
saarg Posted January 2, 2016 Share Posted January 2, 2016 What happens when you start the VM? Do you see it booting? Please post a screenshot of the VM's template and the XML. And be sure as CHBMB says to check that you did create the br0 bridge. Quote Link to comment
bender1 Posted January 2, 2016 Author Share Posted January 2, 2016 1. Yes, bridge is definitely created and is br0 2. The VM starts to boot. I get the bootloader screen but then vnc exits and the log shows 2016-01-02 20:26:01.456+0000: starting up libvirt version: 1.2.18, qemu version: 2.3.0 Domain id=3 is tainted: high-privileges Domain id=3 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2016-01-02T20:26:10.794940Z qemu-system-x86_64: Guest moved used index from 4 to 33319 2016-01-02 20:26:10.847+0000: shutting down Here's the XML <domain type='kvm'> <name>MediaManager</name> <uuid>f564b4e9-7393-a0ca-d8c7-0fe9604fd19c</uuid> <metadata> <vmtemplate name="Custom" icon="ubuntu.png" os="ubuntu"/> </metadata> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>262144</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-2.3'>hvm</type> <loader type='pflash'>/usr/share/qemu/ovmf-x64/OVMF-pure-efi.fd</loader> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='2' threads='1'/> </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/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/vmstore/MediaManager/vdisk1.img'/> <target dev='hdb' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/iso/ubuntu-15.10-server-amd64.iso'/> <target dev='hda' bus='usb'/> <readonly/> <boot order='2'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:ec:c5:7f'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' 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/MediaManager.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> <input type='tablet' bus='usb'/> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='cirrus' vram='16384' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/> </memballoon> </devices> </domain> Quote Link to comment
saarg Posted January 2, 2016 Share Posted January 2, 2016 Try setting the memory to the same amount in both min and max if you have enabled advanced mode in the template. You have set the current memory to only 262 MB it looks like. That is too little. Set it 2GB and try again. Quote Link to comment
CHBMB Posted January 2, 2016 Share Posted January 2, 2016 Try setting the memory to the same amount in both min and max if you have enabled advanced mode in the template. You have set the current memory to only 262 MB it looks like. That is too little. Set it 2GB and try again. Wow... eagle eyes there... Quote Link to comment
saarg Posted January 2, 2016 Share Posted January 2, 2016 Try setting the memory to the same amount in both min and max if you have enabled advanced mode in the template. You have set the current memory to only 262 MB it looks like. That is too little. Set it 2GB and try again. Wow... eagle eyes there... Ha! More like glasses Quote Link to comment
bender1 Posted January 3, 2016 Author Share Posted January 3, 2016 Ill try that. I set initial to 256mb and max to 4 gigs. Quote Link to comment
Creativity404 Posted April 17, 2021 Share Posted April 17, 2021 Did you guys end up finding a fix? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.