Why and how to I fix?
I tried removing the file and recreating but it does not start my VM.... I don't even know what information to supply. F20 with Xen 4.33. I made no changes to the system prior to it stopped working.
I was able to make this work by creating /etc/default/xendomains file as it was missing, with this data:
XENDOMAINS_SAVE=
XENDOMAINS_RESTORE=false
XENDOMAINS_AUTO=/etc/xen/auto
Then copied my /etc/xen/win7.sxp file to /etc/xen/auto
Reboot and viola!
Use libvirt to manage virtual machine resources, not shell commands in rc.local. virsh --connect xen:///; help should get you started; there's an autostart directive for what you're trying to do.
Are you saying that virsh did not connect to your xen instance?
With systemd things changed.
You may still use rc.local for compatibility reasons, but make sure you have /usr/lib/systemd/system/rc-local.service
Also make sure your rc.local is executable.
It DOES work because the network issue is fixed from this question: https://ask.fedoraproject.org/en/question/62262/for-whatever-reason-i-need-to-run-systemctl-restart-network-after-i-login-in-order-for-everything-to-run-smoothly-what-do-i-need-to-do-to-automate/ but the VM portion of it does not. The file is executable.
/usr/lib/systemd/system/rc-local.service does exist.
No I mean it works because the issue I was having with the network is resolved that way. I just deleted the extra stuff that I had in there that was starting my VM (which stopped working). I was having two issues. The network thing and I wanted to start the VM at boot. I put both in that file and it was working. The network piece kept working but the VM piece stopped. VM piece is fixed with my answer to the question.
Asked: 2015-02-27 07:33:26 -0500
Seen: 420 times
Last updated: Mar 01 '15
Ask Fedora is community maintained and Red Hat or Fedora Project is not responsible for content. Content on this site is licensed under a CC-BY-SA 3.0 license.
