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...
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...
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 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.
Okay all 3 WIN VM are OFF again no reason, after same time about 1 hour :(
Status
stopped
2 x Win2008 R2
Win2012
with various settings for disk, lan, and all of them with CPU = HOST
Where can I see some kind of Log or anything to tell me why these are OFF
Cluster log - nothing
These are the...
In the KVM tuning docs it says
QEMU also supports a wide variety of caching modes. If you're using raw volumes or partitions, it is best to avoid the cache completely, which reduces data copies and bus traffic:
qemu -drive file=/dev/mapper/ImagesVolumeGroup-Guest1,cache=none,if=virtio
Ok so I will test with or without SCSI I guess it all depends on CACHE not the BUS. Speed wise its 4x faster with the CACHE on but it also seems too fast. Not sure how risky the cache is , would it only apply to a full host power loss.
Ok thanks Woflgang I have set both instance to HOST and now they report the AMD CPU when I view the System Settings.
As a side note is it safe for me to run the Virio-SCSI drivers?
For performance I get
IDE: 120MB (no cache)
Virtio: 650MB (no cache)
Virtio-Scsi: 2500MB (write back)
So I get...
No idea I tried with and without Ballooning and right now I am also on AMD 6000 series Supermicro and I cannot even keep my VM's UP they just turn off or crash - they are OFF with no error logs of any kind both 2008R2 and Win2012
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.