Search results

Whatever it was, it didn't behave that way in 3.3. Also, this is a generic VGA display on a standard motherboard I/O backplane.

I'm trying to install proxmox 3.4 on a host with a supermicro motherboard, with builtin VGA. It comes up to the splash screen with only a small part of the license screen showing. The Abort button is visible towards the bottom of the screen, but the 'I agree' is apparently off to the right, so...

I don't know how to explain this any more clearly than I already have. I *didn't* set any path because I didn't know what to set it to. '/' seemed dangerous (after years of working on unix-y systems, doing anything recursive to '/' seems risky). You explained exactly what needed to be done...

That worked great. Many thanks!

I'm not being clear. I didn't put anything into PATH (especially not '/') as I was afraid of trashing something. I am trying this in a bit...

I will give that a try, thanks. I had looked through all kinds of docs, and didn't see this. I was afraid to make a major change involving '/'. I will give it a try - thanks again...

Yes, I read that. None of which answers my question as to why the 'Create VM' button is grayed out :(

I was wondering about the dialog that asks for a path. I have no idea what I'm supposed to put there. All I want is to create 3 users who all have PVEAdmin rights over the whole ball of wax. Nowhere I could find does it say how to do that (maybe I just didn't look in the right place?)

I did that. And when I login as one of those users, the 'Create VM' button is grayed out.

Okay, forgive me if this is a silly question, but I've googled and looked at the online help, and came up empty. When I have used proxmox before, I just used root. I need to deploy a server with proxmox for me and two other people to use. I created the unix accounts for them with passwords...

That would be the recommended way, yes. It's sometimes possible to have a hypervisor use storage on a virtualized appliance on that same hypervisor. Whether it works (robustly) depends on the hypervisor. ESXi works fine for that. Xenserver not so much. Can't speak to proxmox.

The reason shared storage is essential for migration is that if you don't have it, migration could take minutes (or hours), since it will have to move N GB of storage, instead of a much smaller amount of ram and other state.

My current setup: two hosts running vmware in 2-node HA. A third node running Centos 7 as a NAS (exporting storage to the vmware hosts.) I wanted storage redundancy, so there are virtual centos guests on each vmware host. The storage is on an SAS JBOD with 2 inputs - one to the physical...

Good to hear!

What is your subnet mask?

Also, you might want to move this conversation to the pfsense forum - I use it but am not an expert. I seem to recall vaguely that traffic has to go into pfsense and then back out to be monitored (although my memory might be flawed), which if true would explain this.

Got it. What I wasn't getting was the point of having two interfaces on the LAN. Is eth0 a different subnet?

I'm confused. Why are there 3 interfaces? It sounds like proxmox host is connected to the switch with eth0 *and* eth2? If so, why? If not, can you clarify?

Agreed vis raid10 if there is any random I/O.

+1 for virtualized pfsense.