Search results

I have migrated an old old ubuntu server from a KVM server into proxmox kernel 2.6. On boot the network interface will not come up. I checked that it detected the device and it has as eth0 but cannot raise the interface because the tempfs on /dev/shm is not mounted. The error you actually see...

I will mark this as solved because it boots. If I adjust either of the images or the append then it doesn't work so I think its working ok.

I ended up having to put that in quotations: -kernel "/mnt/pve/network-proxmox/images/102/vmlinuz-2.6.24-23-server" -initrd "/mnt/pve/network-proxmox/images/102/initrd.img-2.6.24-23-server" -append "root=/dev/vda ro console=tty1 console=ttyS0,115200 2" And whilst it boots the kernel it does...

Well blow me down that works.

I appended this to the config file: args: -kernel /mnt/pve/network-proxmox/images/102/vmlinuz-2.6.24-23-server -initrd /mnt/pve/network-proxmox/images/102/ -append root=/dev/vda ro console=tty1 console=ttyS0,115200 2 Which I very much doubt is the correct thing to do.

Yes there is no problem with the disk formats, they are RAW and some are qcow2. The issue will be that as-is those disks contain no bootloader. Because in their natural habitat [the xml definition] the kvm does a direct kernel boot. So my question is, since proxmox is using KVM I would have...

We have an unmanageable number of KVM VM's that I'm hoping to migrate. I have set up proxmox and tried a few basics with a few new WM's windows and linux and I'm happy with creating them and even importing a disk image and reattaching, should it be needed. The part I can't immediately find...

Thanks, sorry if I didn't make that clear at the start but note it didn't dent my enthusiasm. Standard practice to try these things in lab environment first and my personal machine is much more capable than our actual servers. So for anyone following along I think you need these two: Mac...

I have just tried a complete new installation using Hyper-V nested virtualisation on to which I have ubuntu with KVM running a windows 10 guest. That seems to have no problems and works out of the box. I then tried exactly the same with a fresh proxmox nested on Hyper-V - and it doesn't...

root@proxmox:~# tcpdump -envi eth0 icmp tcpdump: listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes 09:33:44.556904 00:15:5d:38:01:0b > b0:a7:b9:22:3a:94, ethertype IPv4 (0x0800), length 120: (tos 0xc0, ttl 64, id 4814, offset 0, flags [none], proto ICMP (1), length...

Ubuntu 20.04 LTS proxmox-container tty1 proxmox-container login: root Password: Welcome to Ubuntu 20.04 LTS (GNU/Linux 5.13.19-2-pve x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support: https://ubuntu.com/advantage The...

root@proxmox:~# ip -details link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 promiscuity 0 minmtu 0 maxmtu 0 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536...

PS - thanks for your help so far - this ticks all the boxes if I can get over this hurdle.

My Gateway is 192.168.0.1 and there is no mac filtering on it. Linux proxmox 5.13.19-2-pve #1 SMP PVE 5.13.19-4 (Mon, 29 Nov 2021 12:10:09 +0100) x86_64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the...

OK, so I set win10 and ubuntu to 192.168.0.243 and 192.168.0.242 and the CAN ping each other AND 192.168.0.14 which is proxmox itself But they cannot see anything outside of the proxmox world at all. So to summarise, I have a 192.168.0.0/24 network which has 192.168.0.1 gateway and another 70...

I have rebooted proxmox a few times no change. I have 192.168.0.1 defined as the gateway in the guests. I have one ubuntu and one windows 10 guest at the moment. What I thought I'd try was to configure both guests with a static IP and see if they can ping each other. After that I will report...

And that VM is configured to use vmbr0. I can see some bytes sent and received, but I have no idea what they are and no way to figure that out with no way to install anything useful on the vm. I'm sure I have it configured correctly - it just doesn't work.

correct c:\users\proxmox>ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. Reply from 192.168.0.234: Destination host unreachable.

Yes, root@proxmox:~# ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. 64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=54.1 ms 64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=63.6 ms 64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=63.9 ms

I followed the best practices and yes I have the drivers installed. I used the VirtIO network driver and the network device does show up. I tried other network devices but I think the problem is proxmox not the network drivers. I manually set a fixed IP of 0.234 and gateway to 192.168.0.1 in...