Help with VM configuration, please

[Sir.Zex]

So Im completely new to proxmox and I booted it on my only laptop without thinking, and from what I found it seems like my WiFi adapter isn't supported so I don't have internet connection.
So Im planning to run Linux mint in a VM to use as work space, I already copied the iso to my node and made the VM, but I'm stuck when is comes to making changes to things in the command line, since I'm still getting accustomed to it.
Can any maybe offer some advice on my next steps?

 

[Hannes Laimer]

Hey,

a few things,
- it is generally recommended to have a wired connection for PVE
- for wifi you want to look at wpa_supplicant[1] (I doubt the adapter is not supported, linux is really good with compatibility)
- you can have a desktop environment on the PVE node and use it like one, so install with ISO then just install whatever DE you want with apt

I'm not super sure if I understood your setup correctly though. My assumption is that the laptop you mentioned is also then PVE node in question.

Hope this makes sense, if you have more specific questions, feel free to ask

[1] https://manpages.debian.org/trixie/wpasupplicant/wpa_supplicant.8.en.html

 

[DerekG]

So Im completely new to proxmox and I booted it on my only laptop without thinking, and from what I found it seems like my WiFi adapter isn't supported so I don't have internet connection.

I would suggest that you are being way over ambitious as a newbie, you have way more unforeseen problems than just the wifi access. I have years of home lab experience with Proxmox but even I wouldn't attempt to do what you are trying there.

Key points to note.

Proxmox is designed to be managed via the web interface from another machine, you are setting yourself a massive task by attempting to use it in a way it was never designed to be used.

Proxmox needs a fixed and stable IP address / network connectivity, so as Hannes Laimer advised, a wifi connection is discouraged as the primary access method.

A desktop OS can be run in a VM, But trying to use that as your 'only' daily driver is asking for more trouble than it's worth even attempting to do. Consider that even if you do get it working, when you make ANY change which breaks anything, you will not only lose access to the Proxmox environment, but also to the machine which you would use to diagnose the problem. That is creating an unsolvable circular problem for yourself.

With all that being the case, I would advise that you give up on any idea of doing any of this. If you can afford it, purchase a used tiny PC on eBay or the likes (with at least an Intel 6th Gen i5 CPU) and use that as your 1st Proxmox node, that is if you really need Proxmox at all.

 

[Sir.Zex]

Hey,

a few things,
- it is generally recommended to have a wired connection for PVE
- for wifi you want to look at wpa_supplicant[1] (I doubt the adapter is not supported, linux is really good with compatibility)
- you can have a desktop environment on the PVE node and use it like one, so install with ISO then just install whatever DE you want with apt

I'm not super sure if I understood your setup correctly though. My assumption is that the laptop you mentioned is also then PVE node in question.

Hope this makes sense, if you have more specific questions, feel free to ask

[1] https://manpages.debian.org/trixie/wpasupplicant/wpa_supplicant.8.en.html

Ok then thank you so much for such a fast response, I will definitely try this method, and thank you so much to the added resource

 

[Sir.Zex]

I would suggest that you are being way over ambitious as a newbie, you have way more unforeseen problems than just the wifi access. I have years of home lab experience with Proxmox but even I wouldn't attempt to do what you are trying there.

Key points to note.

Proxmox is designed to be managed via the web interface from another machine, you are setting yourself a massive task by attempting to use it in a way it was never designed to be used.

Proxmox needs a fixed and stable IP address / network connectivity, so as Hannes Laimer advised, a wifi connection is discouraged as the primary access method.

A desktop OS can be run in a VM, But trying to use that as your 'only' daily driver is asking for more trouble than it's worth even attempting to do. Consider that even if you do get it working, when you make ANY change which breaks anything, you will not only lose access to the Proxmox environment, but also to the machine which you would use to diagnose the problem. That is creating an unsolvable circular problem for yourself.

With all that being the case, I would advise that you give up on any idea of doing any of this. If you can afford it, purchase a used tiny PC on eBay or the likes (with at least an Intel 6th Gen i5 CPU) and use that as your 1st Proxmox node, that is if you really need Proxmox at all.

Thank you for you advice, I'm very new to Linux as a whole and have been self-studying with software and hardware alike. And I've been finding it Incredible fascinating, and getting as familiar as these completely alien concepts is really for me, and this is a project I decided to do to gain some of that familiarity through this insanely complicated goal and learn along the way.

 

[Johannes S]

A Desktop virtualization Software like virtualbox ( runs too in Windows) or virt-manager might be a better Option until you have dedicated Hardware for ProxmoxVE

 

[DerekG]

this is a project I decided to do to gain some of that familiarity through this insanely complicated goal and learn along the way.

You are taking on an almost impossible task, attempting to manage Proxmox from the command line, because you do not have the experience to understand that there are better ways to achieve the end goal.

Proxmox is a web wrapper for the standard Linux virtualisation stack, so why would anyone attempt to manage a tool designed for the web interface, via the terminal.?

Just start with a Debian based Linux distro install and then manage the kvm / qemu virtualization from the terminal within your Linux desktop. You will learn a lot more with a system which is actually designed and works as intended. In addition you will actually be able to get online assistance in that case.

Hell, with that you might actually be able to run Proxmox in a VM (although I wouldn't recommend that idea either)

That is why a hinted that you might not actually 'need' or want Proxmox at all. It's the wrong tool for what you are trying to achieve.