Recent content by Bwalker

Solved it seems the second NIC in the server created a route to no where, used ip link down and its fixed. Seemed to happen after it did a update package database? not sure that's last thing in the logs

I have had a community version running for couple months now (may) pve-manager/5.2-1/0fcd7879 (running kernel: 4.15.17-1-pve) All of a sudden the Web Console just times out when it worked fine for months All the guest VMs are running and work, I can ssh into the server as root and run all...

OK thanks thats what I will use its funny but Disk Type SCSI is a bit slower then Disk Type Virtio

In my DOCS /pve-docs/chapter-qm.html#qm_hard_disk

we have Under ADD DRIVE we get BUS IDE SATA VIRTIO SCSI Under Options - Scsi Controller Types we have LSI MegaRaid Virtio Scsi Etc. Which is the ideal to pick - Virtio DISK + Virtio SCSI controller or - SCSI DISK + Passthrough Controller

Also here are my Disk stats Virtio - SYNC 550 read / 25 Write Virtio - Writethrough 2837 / 12 Virtio - Writeback - 2800 / 2800 Virtio - No Cache 600 / 600 But your docs don't seem to make sense When I use Virtio - it installs "red hat virtio-scsi...

All machines are brand new created on this box, never moved or migrated.

https://social.technet.microsoft.com/Forums/en-US/1bfc030f-6c00-46d4-a5f9-c7516a7a1136/server-2012-evaluation-shuts-down-every-hour-or-so-and-wont-activate?forum=winserver8setup

Okay I think I figured it out, since it appears to happen after 1 hour - I googled and find out that even with 180 days trail on Server2008 you must ACTIVATE this or it will shutdown every hour after 10 days. Since my VM seems to run excellent I am very sure this is the issue - I just Activated...

Anyway to get more detailed logs? It's driving me nuts and I need to have this up before Monday or this client which is our first potential client for Proxmox will cancel and buy dedicated server instead if we fail this POC for them.

I ran if for 1 hour and same thing no output of any kind root@cloud1:~# qm list VMID NAME STATUS MEM(MB) BOOTDISK(GB) PID 100 Tsuru1 running 8000 100.00 2550 101 Sasamat running 2048 100.00 2624...

Okay I modified the command to run in foreground: too out 104 and Daemonize /usr/bin/kvm -chardev 'socket,id=qmp,path=/var/run/qemu-server/104.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/104.pid -smbios 'type=1,uuid=94dabc99-239f-4d6d-b702-bcc84b325301'...

I think you mean showcmd not config root@cloud1:~# qm showcmd 104 /usr/bin/kvm -id 104 -chardev 'socket,id=qmp,path=/var/run/qemu-server/104.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/104.pid -daemonize -smbios...

I have another post going so far these are all the tricks I know: - try raw disks - try different disk types like IDE,virtio,scsi - turn off all power saving and windows updates - try CPU = HOST setting - disable tablet - Turn on off ballooning - Install / Remove Qemu Agent - Try different...

I am actually not using the local disks at all , I use an ISCSI SAN and all of my linux VM run off it 100% fine for weeks. I tried a SSD direct attach and it also made no difference, VM just enter a STOPPED state after about 1 hour.