On Wed, February 21, 2018 11:18 am, ThierryIT wrote: > Le mercredi 21 février 2018 12:31:29 UTC+2, awokd a écrit :
>> Usually there is a script that runs inside the Linux VM that re-assigns >> these to the correct values, but since it's been restored from R3.2 it >> might not be working. From within vm-work, try assigning the above >> values manually. Check another working VM for the appropriate DNS >> settings. > > Seems not able to keep the manual network config ... Is the internal > script can re-write the config ? Possibly, I don't exactly know how it works. > I have add the folder "eth0" in "interfaces.d" -> doesn't keep the config > or I have add the network config to the file "interfaces" Instead of trying to fix this broken HVM, maybe it would be best to create a new "work" AppVM based on a Fedora template (since it sounds like that was your plan in the first place) and to use qvm-copy-to-vm commands to copy your data from the old to the new? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b8c749a5e311ea3599cc21c9e582379d.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
