Recent content by kappclark

Late to the game, but this is very helpful .. thx for sharing the screenshot.

The hard drive is the drive that was created originally...it is the VM's hard drive as originally created... Nothing exotic here with pass-through etc.. ..I will investigate the correct syntax for using the CLI to include the hard drive in the creation of the backup...your advice will save me...

THX - So here is what I would like to do -- I have an Ubuntu 20 VM running some media server software. If I backup to NAS, I can restore from NAS, but there is no hard drive/bootable device after the restore...if I do this with a container, there is no plm. (A wordpress CT). I cannot locate...

I have 2 VM's which I would like to move/restore to a new host, which I will be building next week. I have current backups on a NAS. Is it just a matter of mounting the NAS resource to the new Prox box and restoring from there ? One is 6.4-9 the other is 6.4-4 .. comments appreciated.. thx in...

THX - I am beginning to understand -- I have pfsense router - lan nw and wireless nw on different subnets on dedicated ethernet ports on router..pfsense runs dhcp on both interfaces (LAN = 10.209.162.0/24 wireless = 192.168.2.0 ..both get to Internet, of course ...currently have wired nw...

Want to follow this thread - I am having similar plm ... host has 1 NIC, and all vms currently on same subnet (10.209.162.0/24). Would like to have 2nd subnet (192.168.2.0/24) for new set of vms on same host. Do I need a second nic on host ?

OK - Found this comment on the very same issue, but cannot understand what file needs to be changed ... he claims the exact update issue, and provided a remedy *FWIW - I do not have an enterprise subscription) ... get some error messages when I try to update the proxmox host ... Here is his...

OK - sorry to belabor this -- after update - all good (dns, dig etc) ... then after reboot, cannot access..... Appears that the update-reboot will cripple the Container .... I have confirmed this on 2 nodes.. Install ct with static defaults dhclient (to get connectivity reboot -----> NO...

FWIW - here are the settings for the container which made it work: I changed IPV6 to SLAAC. Rebbots right away now...the DHCP server is not configured for IPV6 addresses - should I worry about this in a small home network ??

I have been having the same issue -- I create the Debian 10 container, with network settings of static for IPV4 and IPV6 (which appear to be default) .. start the machine... Then I issue dhclient command, get an address, and do update and upgrade. Then I reboot the machine from the cli with...

my current version Is it save to update the kernel with version 5.4.3 ? What are advantages and/or risks ?

I found a thread about the same issue, and he solved the plm...

FWIW, Had to go into Options for windows VMs and set "Use Local Time for RTC" to yes, then the time displayed correctly. All the Linux clients behaved properly and didn't require the tweak ...

Does anyone have incorrect time on windows VM's under Proxmox ? Linux boxes are reporting correctly, but 2 windows servers set the clock back 1 hour ...

Great advice -- the backup folder is actually located on a NFS share (Freenas) ... I have only done 1 restore, and it worked perfectly...I can sometimes make things too complicated !