Search results

Since Coffee Lake GVT-g is not supported yet in the current Proxmox kernel (5.0.18-1pve), I solved my issue by using "pci-stub.ids=xxxx:xxxx" function.

I recently bough a supermicro c246 chipset motherboard with built in BMC graphics. My processor is i3-8100 with built in igd. I am trying to use the intel graphics for GVT-g but i would like proxmox to display the console only using the BMC graphics so if something goes wrong i can use iKVM...

Glad it worked out for you! If you have enough RAM I would keep ballooning driver turned off. Windows 10 is pretty good with RAM usage.

Windows does not have drivers for the VirtIO SCSI. There is no generic model of the driver. Windows will either blue screen or will have something like NTDLR not found and will not load. Adding second drive to install the SCSI driver in Windows. The reason i said to install the second drive is...

Try turning off Ballooning, it should help with performance. As for the changing the drive, I don't remember if you can through GUI but from the conf file you can change it. I will let you know on that soon.

I would change the network to VirtIO and disk drive to VirtIO SCSI Controller with IO Thread enabled. Changing the disk drive to VirtIO SCSI Controller to boot drive will make the system unbootable. Since windows is already installed, i would add extra drive with VirtIO SCSI Controller, load...

That's great news! Still curious why it wouldn't work.

I REALLY apologize on replying so late. I didn't see the notification on the reply. Do you have any update on this or are you still having the issue?

On /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on video=efifb:off,vesafb:off" On /etc/modprobe.d/vfio.conf options vfio-pci ids=8086:1912 disable_vga=1 The rest seems okay to me. Edit: Dont forget to update grub and initramfs. Also, the screen will go blank after couple of...

I have no effect on performance on KVM64. Others have indicated that having a ZIL SSD helps significantly since VMs does sync writes.

It will extend the life of the SSD. That is one of the reasons why enterprise drives are weird sizes. They come over provisioned from factory which is not user changeable.

One way to get more life out of the SSD drives is to over provision them. I have pretty cheap SSD with 256GB but actual partition size is 100GB with rest as unallocated. That will help with wear leveling.

I get the same about 10MB/s write speed a Windows VM. It may have to do with sync writes. I dont have a test server to test putting a SLOG SSD drive to see if it improves performance or disable sync writes entirely.

I am running Celeron J3455

It is the exact problem I am having. I changed the CPU as you mentioned to kvm64 and it reboots just fine. I am currently running the latest version of proxmox as of today. I need the host option since I need some flags that kvm64 doesn't have.

Correct. I used the latest and stable VirtIO drivers. Windows has no yellow exclamation on any drivers. Windows ISO was downloaded directly from Microsoft and verified. It installs just fine in ESXi using the same hardware.

I am aware of that. I have clean installed windows every time. Also made independent VMs for each modes. Still have the same issue.

I ran journalctl -b and just gave the past few logs while the KVM VM was in bootloop state. Apr 10 21:37:00 pve systemd[1]: Starting Proxmox VE replication runner... Apr 10 21:37:01 pve systemd[1]: Started Proxmox VE replication runner. Apr 10 21:38:00 pve systemd[1]: Starting Proxmox VE...

You will not have any issues with 8111c nics, shouldnt have issues with the 8139 either. if it doesnt you can always 'apt' it. As for IDE no idea.

The guest doesnt finish initial bios/uefi loader. Where would i get the information in the host?