Duplicate MAC address error
Kushal Das
My Qubes 4.0rc3 (updated) is showing error for sys-net vm saying it
has a duplicate mac address for the NIC. This error message came
before (on the fresh install), and was fixed in a few reboots. But,
now I could not make it work for the last few days :(
Any tips how to solve this? I could not find any duplicate NIC value
in the /var/lib/qubes/qubes.xml file.
Kushal
--
Staff, Freedom of the Press Foundation
CPython Core Developer
Director, Python Software Foundation
https://kushaldas.in
Roy Bernat
Its happen to me also .
you should restart the computer and try again .
if not copy the appvm .
Roy
Kushal Das
> Its happen to me also .
>
> you should restart the computer and try again .
>
> if not copy the appvm .
recreating the vm. I wrote
a post about the same at [1]. I hope this will help someone in future.
[1] https://kushaldas.in/posts/duplicate-mac-address-error-in-qubes-vms.html
cooloutac
boom, was just aobut to suggest this. its the beauty of qubes. do it for any anomaly. when in doubt delete it and recreate it in seconds. its the most suspect vm of them all.
Reynir Björnsson
It may be a coincidence, but when it happened to me I got sys-net running by shutting down sys-whonix first. I've since disabled sys-whonix and haven't had the issue again, although I haven't been rebooting much since.
- Reynir
Holger Levsen
> It may be a coincidence, but when it happened to me I got sys-net running by shutting down sys-whonix first. I've since disabled sys-whonix and haven't had the issue again, although I haven't been rebooting much since.
restart sys-net (after it crashed) and then after shutting down some
random VMs I could start sys-net again...
:/
--
cheers,
Holger
Kushal Das
the vm. After that I tried to restart the system, and now it gets
stuck in the boot screen trying to start sys-firewall :(
Any tips on how to get out of this mess?
cooloutac
wonder if your system runs low on ram? Could also try using system without iommu and see if it still happens.
Kushal Das
>
> wonder if your system runs low on ram? Could also try using system without iommu and see if it still happens.
>
qubes-us...@ralphdouglass.com
> On Tue, Dec 26, 2017 at 8:18 PM, cooloutac wrote:
> >
> > wonder if your system runs low on ram? Could also try using system without iommu and see if it still happens.
> >
> I have 32GB here on a T470. I hope that is okay :)
>
> Kushal
> --
> Staff, Freedom of the Press Foundation
> CPython Core Developer
> Director, Python Software Foundation
> https://kushaldas.in
I can recreate this error message consistently while running the latest R4 rc3.
Inside of sys-net, just shut down the vm from the inside (e.g. sudo reboot)
Afterwards sys-net fails to start:
$ qvm-start sys-net
Start failed: invalid argument: network device with mac XX:XX:XX:XX:XX:XX already exists
To get back in a good state without rebooting the entire machine, I have to shut down (or kill) all dependent vms (AppVMs talking to my firewall-vm and my firewall vm). Then I can start sys-net again, followed by my firewall vm, followed by my regular app vms.
I've managed to trigger this on two Lenovo laptops and one Dell laptop so far, all of which are running R4rc3.
I'm pretty new to QubesOS and haven't figured out how to dig through the innards well enough yet to find anything useful.
cooloutac
afaik, You can't shut down sys-net if other vms using it are running.
Ralph Douglass
--
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 qubes-users+unsubscribe@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5a152401-9275-4f68-af7a-a7903d5b5202%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Unman
qubes using it as a netvm.
Sometimes (and I stress sometimes) you can recover from this by
changing the netvm of child qubes , restarting sys-net and then
reattaching the children.
If you have sys-firewall, then changing netvms of children to
something else, killing sys-firewall, restarting sys-net, restarting
sys-firewall and then reattaching children will work.
Somewhat better than shutting down all dependent qubes.
unman
cooloutac
Yes if you have some programs and data open to continue working on them.
Otherwise if rather just shutting down the vms, There is a script someone made in the community to shut down all vms with one command. Its on forums somewhere.
