[PVE-User] VM Won't start
Gilberto Nunes
gilberto.nunes32 at gmail.com
Wed Jan 13 18:28:51 CET 2016
Not at all!
Still get I/O error...
Funny, because there's nothing indicate any disk I/O failure...
Dmesg, show me nothing.
syslog show me nothing....
I will try performe a apt-get dist-upgrade and restart the entire server,
tonight.. ( and screw my pretty 46 days uptime... :/ )
Tomorrow will see it...
Or, if somebody else has better idea, I'll appreciated...
Thanks
2016-01-13 15:19 GMT-02:00 Thomas Lamprecht <t.lamprecht at proxmox.com>:
> Did you tried a recreation of the VM? Even if that helps it would be
> strange.
> Also you can try to run the command from this VM manually, maybe you have
> better luck and get a specific error.
> Get the command with
> # qm showcmd 108
> then simply execute the output from the command above in a shell as root.
>
> On 13.01.2016 17:24, Gilberto Nunes wrote:
>
> Well... Ok... Here we go....
> More info below:
>
> Server: HP Proliant with 64 Intel(R) Xeon(R) CPU X7560 @ 2.27GHz ( 4
> sockets)
> 256 GB memory
> SAS local storage with 3.2 TB
>
> I haved others VM's with the same behaviors.
> When I started the VM creation setting the configuration like CPU type to
> Nehalem or even host, and set memory disck and so, created normally.
> But, when I point the virtual CD/DVD to an ISO image, I get that message...
> There is no special requirement to this VM... ISO is Centos 7 x64.
> VM config:
>
> bootdisk: virtio0
> cores: 1
> cpu: Nehalem
> ide2: none,media=cdrom
> memory: 4096
> name: LcomBPMAppServer
> net0: virtio=36:64:65:38:64:63,bridge=vmbr0
> numa: 0
> ostype: l26
> smbios1: uuid=deb5b877-25ae-42db-913a-77815c88cc20
> sockets: 1
> virtio0: stg-local:108/vm-108-disk-1.qcow2,size=120G
>
>
> looks good
>
>
>
> Thanks
>
>
> 2016-01-13 14:14 GMT-02:00 Thomas Lamprecht <t.lamprecht at proxmox.com>:
>
>> Hi,
>>
>> I didn't looked at the entire command if there is an
>> error/misconfiguration, to tiresome for me.
>>
>> Can you please also post the VMs config file and maybe some additional
>> info you have: is this VM special in any sense? did the VM never work
>> (since creation) or stopped working?
>>
>> Further, is more information in the log? Please look in the journal at
>> the time from a failed start. (journalctl)
>> That info should make it easier to track down the problem and help you.
>>
>> cheers,
>> Thomas
>>
>>
>> On 13.01.2016 16:53, Gilberto Nunes wrote:
>>
>> Hello list
>>
>> I just set a VM like any other one here in Proxmox 4.1 with more than 16
>> VM's running smootlhy
>>
>> However, one of them (always has The Rebel!), refused to go up.
>> I get this error:
>>
>> Failed to create message: Input/output error
>>
>> TASK ERROR: start failed: command '/usr/bin/systemd-run --scope --slice
>> qemu --unit 108 -p 'KillMode=none' -p 'CPUShares=1000' /usr/bin/kvm -id 108
>> -chardev 'socket,id=qmp,path=/var/run/qemu-server/108.qmp,server,nowait'
>> -mon 'chardev=qmp,mode=control' -vnc
>> unix:/var/run/qemu-server/108.vnc,x509,password -pidfile
>> /var/run/qemu-server/108.pid -daemonize -smbios
>> 'type=1,uuid=deb5b877-25ae-42db-913a-77815c88cc20' -name LcomBPMAppServer
>> -smp '1,sockets=1,cores=1,maxcpus=1' -nodefaults -boot
>> 'menu=on,strict=on,reboot-timeout=1000' -vga cirrus -cpu
>> Nehalem,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 4096 -k pt-br -device
>> 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device
>> 'pci-bridge,id=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=uhci.0,port=1' -device
>> 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi
>> 'initiator-name=iqn.1993-08.org.debian:01:9a3690d7aafb' -drive
>> 'file=/storage/images/108/vm-108-disk-1.qcow2,if=none,id=drive-virtio0,format=qcow2,cache=none,aio=native,detect-zeroes=on'
>> -device
>> 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100'
>> -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' -netdev
>> 'type=tap,id=net0,ifname=tap108i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on'
>> -device
>> 'virtio-net-pci,mac=36:64:65:38:64:63,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300''
>> failed: exit code 1
>>
>>
>> Somebody can help me with any assistance???
>>
>> Thanks a lot
>>
>> --
>>
>> Gilberto Ferreira
>> +55 (47) 9676-7530 <%2B55%20%2847%29%209676-7530>
>> Skype: gilberto.nunes36
>>
>>
>>
>> _______________________________________________
>> pve-user mailing listpve-user at pve.proxmox.comhttp://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>
>>
>>
>> _______________________________________________
>> pve-user mailing list
>> pve-user at pve.proxmox.com
>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>
>>
>
>
> --
>
> Gilberto Ferreira
> +55 (47) 9676-7530
> Skype: gilberto.nunes36
>
>
>
> _______________________________________________
> pve-user mailing listpve-user at pve.proxmox.comhttp://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>
>
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>
--
Gilberto Ferreira
+55 (47) 9676-7530
Skype: gilberto.nunes36
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.proxmox.com/pipermail/pve-user/attachments/20160113/0a8295c8/attachment.htm>
More information about the pve-user
mailing list