#just how it was when I set it up i think
1 messages · Page 1 of 1 (latest)
Please share what your history output looks like.
PVE is not set up to use local for VM disks by default.
Wait a second. What hardware is this running on?
Oh. That explains a few things. I don't recommend this. You probably can't use the x86 image for this. Get a x86 machine if you want to use PVE. ARM is not officially supported: https://www.proxmox.com/en/proxmox-virtual-environment/requirements
I was orginally trying to use pimox then got redirected to that since pimox is only supported up to pi 4
You might have to use one of the aarch images. I don't know.
os-agent_1.6.0_linux_aarch64.deb
?
I used haos_generic-aarch64-12.3.qcow2.xz
in the vm
where do I find that?
Enter history, share what it says.
That is not the aarch one.
Ah it’s cos I used the generic one through the home assistant website let me try an aargh one
x86 machines are cheaper than a pi. Any reason you're using a pi for this?
I have the pi and would like to avoid buying a x86 machine tbh
I sort of spontaneously bought the pi not really thinking about it
It's just lots of pain and hacks and workarounds as you can see.
Yeah I know and has been pain since I got it but would rather the pain than buying another machine
I have thought of selling the pi but I like the form factor lower power consumption although I’m x86 machines are around the same
I would like to invest in a x86 machine later down the line and run just run multiple vms
You can get a used office PC for 50 or so depending on where you are.
Don't forget to set the newly imported disk as boot medium.
I’m in the uk and have looked at some and I’ve seen some on Ali express although a bit dodgy they actually seem alright looking at YouTube reviews and other forum posts
I kind of prefer the (U)SFF ones from eBay. They can be extended a lot more than the Mini PCs.
I replaced/exchanged the CPU of most of mine for example.
And it worked right away makes me feel stupid since I knew I needed a aarch64 os after some research but thank you for helping me out
🎉
But back to the snapshot thing.
Your disk is raw. Not good.
Try
qm disk import ... --format qcow2
This way you can do snapshots and thin allocation.
yeah my friends bought a mini pc and he mostly said he wouldnt buy it again since the only upgradability was the ssd and that was it I would like to be able to upgrade stuff like ram and have multiple sata ports
You can upgrade RAM with a Mini PC too.
Im planning to restart it all and reinstall all of it and do it right
You can't really easily add PCIe devices though.
only some ive seen on many very mini pc its just soldered on to save space
You also can't add a big HDD inside it. Lots of examples. Tower PCs are even the cheapest usually. Might not matter to you. Just depends what your goal is. I really don't like pis and most SBCs:
hmm after launching the vm im getting
Waiting for the Home Assistant CLI to be ready...
[WARN] Home Assistant CLI not starting! Jump into emergency console...
#
Tried the command login
You're already in the CLI, no login needed.
Check journalctl -ru docker.service and journalctl -ru hassos-supervisor.service.
Sometimes the CLI takes a little while and times out. Might work at the next boot.
Please also share cat /etc/network/interfaces.
https://imgur.com/yiHnPAM I think i did it right but prob not
That's wrong.
Your bridge is not connected to anything. Make it look exactly like in the link just with your ip and gateway.
lets go another thing wrong
Technically you can use dns-nameservers but I recommend you use the resolv file. PVE's GUI can also edit this.
same Ip I guess?
Atleast im learning bit by bit
Same. If there's nothing more to learn I doubt I'd still be around.
tbf I always just jump into complicated stuff not alot of reason mainly just cos I like to problem solve
Waiting for the Home Assistant CLI to be ready...
[WARN] Home Assistant CLI not starting! Jump into emergency console...
#
Still jumping into this going to try rebooting everything again
Check the logs and try stuff like ping google.com.
does seem to be working outputting icmp_seq=1 destination host unreachable
probabply why ha is launching
but i can ping 0.0.0.0 just not google.com 8.8.8.8 8.8.4.4
also noticed a few errors https://imgur.com/FUFxUBj
Try it on the node.
Also try nslookup google.com.
Pinging 0.0.0.0 makes no sense, btw.
Please also share your new interfaces file.
Gotta go for a while. Will respond when able.
still not working just giving me destination host unreachable
Unless you run exactly what I share and show me what you see I can't help you.
https://imgur.com/a/k7bPcZk - Thats the new interfaces file
I said to make it look exactly like in the wiki and only edit the ip and gateway.
Weird gateway ip, btw.
that is my bad i glanced at it and it looked to same
yeah Ik i set it not sure why I set it to .5 but I did I have 2 routers the other is .6
The ip range is correct yeah?
https://imgur.com/NBJacuF - Thats pinging google
Yeah unless that works there's no point continuing with HAOS.
Try ifdown vmbr0; dhclient -v eth0. Do this via keyboard and monitor of course.
Uhh wait.
Can I use ssh?
Why are you using 0.0.0.0 as name server?
No. It will lose connection.
Try ping 1.1.1.1.
Np im in the uk so I will also be going to sleep but will probably need the help in the morning if u havent been driven crazy by me already
https://imgur.com/vLhSDZO - Before doing ifdown vmbr0; dhclient -v eth0 ping google.com wouldnt work after it would. Sorry for the picture tv was easiest to be a monitor
Please also share your new interfaces file.
You could try https://helper-scripts.com/scripts?id=PiMox+HAOS
:<
Again. Make it look exactly like in the wiki and only edit the ip, gateway and interface name.
Get the NIC name from ip a.
And please use code blocks.
It is the exact same no? or do I need to get rid of the auto eth0?
this bit?
auto lo
iface lo inet loopback
iface eno1 inet manual
auto vmbr0
iface vmbr0 inet static
address 192.168.10.2/24
gateway 192.168.10.1
bridge-ports eno1
bridge-stp off
bridge-fd 0
Or is it the one below
Exactly to what I linked.
You have to replace eno1 with your NIC and the ip and gateway ip. Don't do anything else. At least for now.
So in my case it would be eth0?
Perhaps.
Unless you share the result of the commands I give you you have to judge this yourself.
Aaaaaaaaa.
Why is dns-nameservers still there? When I say exactly like in the wiki I mean it.
Please use code blocks.
This whole eth0 section should not exist. Wipe the whole file, use the stuff from the wiki and only edit what I said.
I'm not sure why I have to repeat myself dozens of times about this but it's very annoying.
https://imgur.com/CgjsFHj Right if this isnt the same then I need to go back to primary school I copy and pasted it in and put the things that you asked me to put it
Perfect
But you have a typo in the bridge-ports.
If you use code blocks I can copy paste stuff from there and it's much easier to read. Please use them.
To format your text as code, enter three backticks on the first line, press Enter for a new line, paste your code, press Enter again for another new line, and lastly three more backticks.
```yaml
example: here
```
Don't forget you can edit your post rather than repeatedly posting the same thing.
You can reload the networking with ifreload -av.
auto lo
iface lo inet loopback
iface eth0 inet manual
auto vmbr0
iface vmbr0 inet static
address 192.168.0.133/24
gateway 192.168.0.5
bridge-ports eth0
bridge-stp off
bridge-fd 0
Like this?
Ok
I'd recommend you put your gateway into /etc/resolv.conf now.
Like this for example
echo "nameserver 192.168.0.5" > /etc/resolv.conf
Then after running ifreload -av test these
ping 1.1.1.1
ping google.com
nslookup google.com
nameserver 192.168.0.5
Was already in there
If all this works: #1250214974907744309 message
we can move to the HAOS VM again. I'd power it off and start it again
All pings came back but the
nslookup google.com
Came back as
-bash: nslookup: Command not found
Both
Ping 1.1.1.1
And
Ping google.com
Pinged back
apt install bind9-dnsutils then try again.
You can also use dig google.com.
But if you can ping google.com it should be fine.
Server: 192.168.0.5
Address: 192.168.0.5#53
Non-authoritative answer:
Name: google.com
Address: 216.58.201.110
Name: google.com
Address: 2a00:1450:4009:826::200e
after nslookup google.com
Alright.You now have a networking setup that is working. Kind of a necessity 😄
Now start the HAOS VM and try ha network info.
Well I can connect to the web adress everything seems to be working in the console
Yay.
Thank you thank you thank you
not only for helping me fix it but more put up with me
No problem. Just next time try to follow the instructions 😛