Reconsidering ProxMox
-
And after all of that. It won't finish booting. It gets to here and then when I click OK, it reboots an d stop here again. Lovely.
-
@JasGot said in Reconsidering ProxMox:
Having found no documentation on how to use local usb for the installation source, I did upload an ISO. It took MUCH longer than sticking the USB stick in the USB port.
But that isn't repeatable.
And it's just a quick dd command to turn that USB stick into an ISO on the storage.
-
@JasGot said in Reconsidering ProxMox:
And after all of that. It won't finish booting. It gets to here and then when I click OK, it reboots an d stop here again. Lovely.
Hardware virtualization definitely enabled?
-
@scottalanmiller said in Reconsidering ProxMox:
@JasGot said in Reconsidering ProxMox:
And after all of that. It won't finish booting. It gets to here and then when I click OK, it reboots an d stop here again. Lovely.
Hardware virtualization definitely enabled?
Yes. Looks like a virtio-win issue. I need to find and install a newer version of virtio-win.
-
@JasGot said in Reconsidering ProxMox:
@scottalanmiller said in Reconsidering ProxMox:
@JasGot said in Reconsidering ProxMox:
And after all of that. It won't finish booting. It gets to here and then when I click OK, it reboots an d stop here again. Lovely.
Hardware virtualization definitely enabled?
Yes. Looks like a virtio-win issue. I need to find and install a newer version of virtio-win.
Did you load it from the downloaded ISO from Fedora? Or load with Chocolatey?
-
@scottalanmiller said in Reconsidering ProxMox:
@JasGot said in Reconsidering ProxMox:
@scottalanmiller said in Reconsidering ProxMox:
@JasGot said in Reconsidering ProxMox:
And after all of that. It won't finish booting. It gets to here and then when I click OK, it reboots an d stop here again. Lovely.
Hardware virtualization definitely enabled?
Yes. Looks like a virtio-win issue. I need to find and install a newer version of virtio-win.
Did you load it from the downloaded ISO from Fedora? Or load with Chocolatey?
The whole debian package provided by Proxmox.
https://www.proxmox.com/en/downloads 6.1 ISO installer. -
@JasGot Make sure you run updates on the proxmox host.
You have to disable the enterprise repo, and add the no subscription repo first.
-
@VoIP_n00b said in Reconsidering ProxMox:
@JasGot Make sure you run updates on the proxmox host.
You have to disable the enterprise repo, and add the no subscription repo first.
I was just going to comment that I couldn't run updates because it was not enterprise licensed. Thanks to your post, it's updating right now!
I hope it updates Virtio-win!
-
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/
Download the virtio-win iso file and upload that to Proxmox.
Since Proxmox is using LVM thin the controller is a virtio scsi so you will need the virtio-win driver.
-
Proxmox also has a basic mobile GUI. It’s not super useful, but it handy if you need to reboot a VM quickly, etc
-
@VoIP_n00b said in Reconsidering ProxMox:
@JasGot Make sure you run updates on the proxmox host.
You have to disable the enterprise repo, and add the no subscription repo first.
Sadly, this either didn't Update Virtio, or it didn't solve the problem.
So, I grabbed the latest Virtio-Win driver iso from https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/virtio-win.iso and attached it to the VM, I loaded the driver during Windows server installation, and all is good now.
-
@black3dynamite said in Reconsidering ProxMox:
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/
Download the virtio-win iso file and upload that to Proxmox.
Since Proxmox is using LVM thin the controller is a virtio scsi so you will need the virtio-win driver.
I think we were typing at the same time!
-
@JasGot said in Reconsidering ProxMox:
So, I grabbed the latest Virtio-Win driver iso from https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/virtio-win.iso and attached it to the VM, I loaded the driver during Windows server installation, and all is good now.
Yup, that's required to use the high performance PV peripherals. So lame that Windows lacks some of the most common and basic drivers on the market from being build in.
-
To get rid of the no subscription message pop up
https://johnscs.com/remove-proxmox51-subscription-notice/
sed -i.bak "s/data.status !== 'Active'/false/g" /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js && systemctl restart pveproxy.serviceClear your browser cache.
-
@JasGot said in Reconsidering ProxMox:
@JaredBusch said in Reconsidering ProxMox:
You are intentionally doing it the hard way. No hypervisor is designed to use a full install media to turn up guests, even if they have an option for CDROM. Just put the ISO on there like you should.
I understand this is easy to do. I also understand that if I was sourcing the media at the time of install, this would be super simple and I would not have even thought about local USB access.
But I also believe if I have bootable usb server media in my hand, I should be able to use it without much difficulty. After all, they made the CD/DVD an option..... and why? Most servers don't even come with CD/DVDs any more.....
Having found no documentation on how to use local usb for the installation source, I did upload an ISO. It took MUCH longer than sticking the USB stick in the USB port. (USB Stick - 2.1 seconds; ISO Media - 9 Minutes to download from MS, and 3 minutes to upload to PVE).
That's all. Nothing more, nothing less, I just think I should be able to easily use the resources that are already laying next to the server on the bench.
I don't think that using a USB bootable stick on the hypervisor is possible with xenserver/xcp-ng either.
What you really want there is a file share outside the hypervisor that has all the ISO files. If you have no infrastructure available, the easiest thing would be to download the iso file to your workstation and share that folder with the hypervisor.
-
@Pete-S said in Reconsidering ProxMox:
I don't think that using a USB bootable stick on the hypervisor is possible with xenserver/xcp-ng either.
It is, but it is not recommended.
-
@scottalanmiller said in Reconsidering ProxMox:
Not ideal, but with compression and dedupe, not the problem it seems to be. And it is far less risky that continuous partials that always depend on rehydration.
2TB of data and a large backup window? Not a huge deal.
50TB of data, and 100% 24/7 workloads? Not going to fly.
-
@black3dynamite said in Reconsidering ProxMox:
It’s supports multiple storage types like nfs or cifs
Obligatory - https://blog.fosketts.net/2012/02/16/cifs-smb/
(Saying CIFS is my pet peeve).
-
-
This post is deleted!
