Ubuntu VM inside Proxmox VM is not accessing Internet
- Thread starter mohtashim
- Start date
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
You don't seem to have assigned an IP to the Ubuntu VM.
Your PVE appears to be running in Virtualbox so there's a whole other layer of networking that you have not described. How it is Virtualbox networking configured (default NAT? Host? Bridged?). How that is set up will determine how you must assign IP's to VM's running under PVE.
Your PVE appears to be running in Virtualbox so there's a whole other layer of networking that you have not described. How it is Virtualbox networking configured (default NAT? Host? Bridged?). How that is set up will determine how you must assign IP's to VM's running under PVE.
I Attached 2 adopter with PVEYou don't seem to have assigned an IP to the Ubuntu VM.
Your PVE appears to be running in Virtualbox so there's a whole other layer of networking that you have not described. How it is Virtualbox networking configured (default NAT? Host? Bridged?). How that is set up will determine how you must assign IP's to VM's running under PVE.
1. Bridge
2. NAT
and i had not attached static ip with ubuntu vm because i tried multiple times it give me error of
WARNING:root:Cannot call Open VSwitch: ovsdb-server.service is not running.
when i enter sudo netplan apply
Why? And which one is vmbr0 connected to? The Bridge network won't have a DHCP server unless you have one external somewhere.I Attached 2 adopter with PVE
1. Bridge
2. NAT
This seems to be a warning only:and i had not attached static ip with ubuntu vm because i tried multiple times it give me error of
WARNING:root:Cannot call Open VSwitch: ovsdb-server.service is not running.
when i enter sudo netplan apply
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2041727
I had attached only bridge adopter now and vmbr is attached to that adopter i assign manual ip to etc/network/interface and in vmbr0
ReminderI had attached only bridge adopter now and vmbr is attached to that adopter i assign manual ip to etc/network/interface and in vmbr0
I have never done this in Ubuntu, but what does your
Use this as reference.
You probably need to have in there under the correct adapter something like this:
Good luck.
/etc/netplan/99_config.yaml look like.Use this as reference.
You probably need to have in there under the correct adapter something like this:
Code:
routes:
- to: default
via: xxx.xxx.xxx.xxx #fill in with GW of your NW that Oracle VB is onGood luck.
What about in the VM? The IP on vmbr0 has exactly nothing to do with the VM, it is only the IP for the PVE server itself.I had attached only bridge adopter now and vmbr is attached to that adopter i assign manual ip to etc/network/interface and in vmbr0
Reminder
Yes for accessing the PVE Interface in browser but in my case i have internet issue in PVE VM's and after strugglying alot not able to find any solution why this is happening.What about in the VM? The IP on vmbr0 has exactly nothing to do with the VM, it is only the IP for the PVE server itself.
You need to set appropriate IP address and gateway in the VM's. You have to do that individually for each one. If you use DHCP, then you need to have a DHCP server on your network (maybe your router?) because Virtualbox bridged network does not provide one. That or you have to set static IP's.
I had setup the static ip in PVE but i am having issue while assigning static ip in PVE VMYou need to set appropriate IP address and gateway in the VM's. You have to do that individually for each one. If you use DHCP, then you need to have a DHCP server on your network (maybe your router?) because Virtualbox bridged network does not provide one. That or you have to set static IP's.
i got an error when executing command:
sudo netplan apply
error:
WARNING:root:Cannot call Open VSwitch: ovsdb-server.service is not running.
resolution:
sudo apt-get install openvswitch-switch-dpdk this is the resolution but unfortunately i have not internet access so how can i resolve this issue. stuck in this.
The bug reports says that message is only a warning and does not prevent the IP from being set. It also includes a patch showing what to change to get rid of the warning.
ETA: You could also install a newer version of Ubuntu. 24.04 is the current LTS release.
ETA: You could also install a newer version of Ubuntu. 24.04 is the current LTS release.
Last edited:
For clarity sake; with "PVE VM" you mean (or should mean) inside the Ubuntu VMI had setup the static ip in PVE but i am having issue while assigning static ip in PVE VM
Look at my above post concerning that Ubuntu VM.