qm start - Failed to create message: Input/output error

Discussion in 'Proxmox VE: Installation and configuration' started by sysV, Feb 4, 2016.

  1. sysV

    sysV New Member

    Joined:
    Feb 4, 2016
    Messages:
    7
    Likes Received:
    0
    Hello.
    What is it can be ?

    qm start 1003
    Failed to create message: Input/output error
    start failed: command '/usr/bin/systemd-run --scope --slice qemu --unit 1003 -p 'KillMode=none' -p 'CPUShares=1000' /usr/bin/kvm -id 1003 -chardev 'socket,id=qmp,path=/var/run/qemu-server/1003.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/1003.vnc,x509,password -pidfile /var/run/qemu-server/1003.pid -daemonize -smbios 'type=1,uuid=97eca489-2d7b-4863-8c2b-37aac7961c42' -name win1003 -smp '1,sockets=1,cores=1,maxcpus=1' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga cirrus -cpu host,+kvm_pv_unhalt,+kvm_pv_eoi -m 1024 -object 'memory-backend-ram,size=1024M,id=ram-node0' -numa 'node,nodeid=0,cpus=0,memdev=ram-node0' -k en-us -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:278c7bbb5dec' -drive 'if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/var/lib/vz/images/1003/vm-1003-disk-1.qcow2,if=none,id=drive-ide0,discard=on,format=qcow2,cache=none,aio=native,detect-zeroes=unmap' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap1003i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'rtl8139,mac=66:64:62:35:66:38,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime'' failed: exit code 1


    Standalone proxmox node

    ii pve-cluster 4.0-31 amd64 Cluster Infrastructure for Proxmox Virtual Environment
    ii pve-container 1.0-39 all Proxmox VE Container management tool
    ii pve-firewall 2.0-15 amd64 Proxmox VE Firewall
    ii pve-firmware 1.1-7 all Binary firmware code for the pve-kernel
    ii pve-ha-manager 1.0-19 amd64 Proxmox VE HA Manager
    ii pve-kernel-4.2.6-1-pve 4.2.6-34 amd64 The Proxmox PVE Kernel Image
    ii pve-libspice-server1 0.12.5-2 amd64 SPICE remote display system server library
    ii pve-manager 4.1-5 amd64 The Proxmox Virtual Environment
    ii pve-qemu-kvm 2.5-3 amd64 Full virtualization on x86 hardware
     
  2. JustaGuy

    JustaGuy Member

    Joined:
    Jan 1, 2010
    Messages:
    323
    Likes Received:
    1
    I have the same problem, all of a sudden, after a graceful shutdown, even
     
  3. spirit

    spirit Well-Known Member

    Joined:
    Apr 2, 2010
    Messages:
    3,311
    Likes Received:
    131
    can you try

    qm stop 1003 (even if it's already shutdown)
    qm start 1003
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. JustaGuy

    JustaGuy Member

    Joined:
    Jan 1, 2010
    Messages:
    323
    Likes Received:
    1
    Oh, I had changed the CPU from core2duo to nahalem, changed it back & all is well
    Code:
    root@moffat:~# qm start 100 
    Running as unit 100.scope. 
    WARNING: Image format was not specified for '/dev/disk/by-id/ata-ST31000528AS_9VP8GN6C' and probing guessed raw. 
     Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. 
     Specify the 'raw' format explicitly to remove the restrictions. 
    WARNING: Image format was not specified for '/dev/disk/by-id/ata-HGST_HTS721010A9E630_JG40006PG0EVED' and probing guessed raw. 
     Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. 
     Specify the 'raw' format explicitly to remove the restrictions. 
    warning: host doesn't support requested feature: CPUID.01H:ECX.sse4.1|sse4_1 [bit 19] 
    warning: host doesn't support requested feature: CPUID.01H:ECX.sse4.2|sse4_2 [bit 20] 
    warning: host doesn't support requested feature: CPUID.01H:ECX.popcnt [bit 23] 
    kvm: Host doesn't support requested features 
    start failed: command '/usr/bin/systemd-run --scope --slice qemu --unit 100 -p 'KillMode=none' -p 'CPUShares=1000' /usr/bin/kvm -id 100
    -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-serve
    r/100.vnc,x509,password -pidfile /var/run/qemu-server/100.pid -daemonize -smbios 'type=1,uuid=49efa9c6-3122-4256-9b3e-6db24d4a2b10' -na
    me Triborough -smp '2,sockets=1,cores=2,maxcpus=2' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga vmware -cpu Nehalem,+
    kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 4096 -k en-us -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'pci-bridge,i
    d=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhc
    i.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:dd5438f17841' 
    -drive 'file=/var/lib/vz/images/100/vm-100-disk-1.qcow2,if=none,id=drive-virtio0,cache=writeback,serial=6800-9468-3182669401,format=qco
    w2,aio=threads,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=200' -drive 'file=
    /dev/disk/by-id/ata-ST31000528AS_9VP8GN6C,if=none,id=drive-virtio2,cache=writeback,serial=5383-8732-2765624887,aio=threads,detect-zeroe
    s=on' -device 'virtio-blk-pci,drive=drive-virtio2,id=virtio2,bus=pci.0,addr=0xc' -drive 'if=none,id=drive-ide0,media=cdrom,aio=threads'
    -device 'ide-cd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -drive 'file=/dev/disk/by-id/ata-HGST_HTS721010A9E630_JG40006
    PG0EVED,if=none,id=drive-virtio3,cache=writeback,serial=6428-4103-5705898346,aio=threads,detect-zeroes=on' -device 'virtio-blk-pci,driv
    e=drive-virtio3,id=virtio3,bus=pci.0,addr=0xd' -drive 'file=/var/lib/vz/images/100/vm-100-disk-2.qcow2,if=none,id=drive-virtio1,cache=w
    riteback,serial=9521-7812-5179474562,format=qcow2,aio=threads,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio1,id=virtio1,
    bus=pci.0,addr=0xb' -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pv
    e-bridgedown,vhost=on' -device 'virtio-net-pci,mac=62:33:65:35:38:32,netdev=net0,bus=pci.0,addr=0x12,id=net0'' failed: exit code 1 
    root@moffat:~# qm start 100 
    Running as unit 100.scope. 
    WARNING: Image format was not specified for '/dev/disk/by-id/ata-ST31000528AS_9VP8GN6C' and probing guessed raw.  
     Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.  
     Specify the 'raw' format explicitly to remove the restrictions.  
    WARNING: Image format was not specified for '/dev/disk/by-id/ata-HGST_HTS721010A9E630_JG40006PG0EVED' and probing guessed raw.  
     Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.  
     Specify the 'raw' format explicitly to remove the restrictions. 
     
  5. piccardi

    piccardi New Member

    Joined:
    Oct 20, 2012
    Messages:
    12
    Likes Received:
    0
    I got the same exact problem. But qm stop VMID doesn't work. The problem was that the VMID.scope unit created by systemd-run to launch was still there and taken as active (reported as such by systemctl status).

    To solve the problem you have to issue the command systemctl stop VMID.scope, then you can start your VM.

    I have to say that the reported error code (Input/output error) is highly misleading. I got the real problem by chance, reading the launched command and the systemd-run manpage.

    I got the problem with a falling vzdump command given after a shutdown that reported no error. Just the same:
    Failed to create message: Input/output error with a
    /usr/bin/systemd-run --scope --slice qemu --unit XXX etc.
    command.

    From that time every attempt to start the VM failed with the same problem.

    Simone
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice