That's the template I also used and it is displaying the actual stats for input reads (no, writes as I just learned) and both network input/output. Those were not super-important to me, so payed them not too much attention, but I will take a look at the missing write I/Os…
Yeah, unfortuanetly it seems to be that way - bummer. So you either focus on how to speed-up your WS 2019/guest setup or you abandon the idea of running WS2019 on kvm for the time being. Maybe you should start a new thread about the performance issues of WS2019 on Proxmox - worth a shot.
Relax… ;) Cut @alexskysilk some slack… it's not unreasonable to suggest that. However, having not experienced those errors myselg, I also went for some searching and found a couple of posts which deal with this dreadful KMODE_EXCEPTION_NOT_HANDLED error. To get to know, what actually causes this...
Well… the best advice I can give you is to try a new install to a different guest and see, if it runs stable. If your guest crashes randomly, then it looks to me like there are some other issues with your host. We do run a couple of RDP hosts - admittedly not WS2019, but 2016 but they all run...
Hmm… I am still not sure, that setting the guest's CPU config to host will help you. Regarding the BSODs… does this new server has some radical different CPU? Did you switch from Intel to AMD perhaps…? If you're getting a BSOD, there should be an error message, that you can try to look up and...
Would be good to know, what your intent with this setup is. You seem to try to roll some kind of VDI service? If that's the case, then you should look into passing through the GPU to the guest directly. No CPU can match a GPU for it's designed purpose. If you need graphics power, you will have...
From my experience you don't need to tweak the CPU type unless, you want to achieve some very specific results or have a need for a specific CPU flag, which is not offered by kvm64. Note, that these are not emulations per se, these settings enable/disable certain CPU flags which are provided -...
That's why I suggested to try that first using umount/mount to see whether the enry in fstab is correct. You can also change the entry to look like this:
/dev/sdb1 /mnt/sdb ext4 defaults 0 0
But you should in any case test that before rebooting…
adjust...
Well… what did you actually do in the storage tab? Looks a bit like you have severely damaged your boot device. I am operating approx. 18 PVE server and none had ever such an issue. I'd say, as long as you don't mess with the boot drive, such things couldn't happen, unless your boot device...
Sure, grab the UUID from the output you shared above and insert in into your fstab like this (remeber to adjust the UUID!):
UUID=<UUID of partition> /mnt/sdb ext4 defaults 1 2
replace <UUID of partition> with the actual UUID. Then unmount your volume and remount it...
If those nodes get fenced, then you should be able to get from the logs (syslog/messages) why that has been the case. I'd assume some issue with your ceph/osd config. I was actually wondering about this config:
osd pool default min size = 1
osd pool default size = 2
when you do have a 3-node...
Well… create a mount folder for it and try it:
mkdir /mnt/sdb
mount -t ext4 /dev/sdb1 /mnt/sdb
and see, if it shows up in the PVE UI. If yes make this permanent by editing /etc/fstab accordingly.
You're saying that you had a Proxmox VE config, which showed you the contents of arbitrary disks? I wonder, how you did that. Afaik, PVE will only show you configured storages and only if you configure some directory to contain also snippets, you will be able to get it's content listed in the...
Well… not, this is not what the PVE GUI is supposed to show you. It's not a file browser. PVE GUI will show you the contents of local storage, in case you added that drive as one, but only of your're running LVM on it.
…and why should the PVE GUI display any movie anyway? Proxmox is for running...
Okay, care to elaborate on the goal you want to achieve? What kind of data is that? What type of file systems are on the drive? Sou you want to access the data from the proxmox host itself or from a guest on that proxmox host?
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.