On Wed, Feb 27, 2013 at 11:16:53AM +0000, YamakasY wrote:
Hi All,
I have this same issue on Pfsense (FreeBSD) and even a fresh Ubuntu installation.
I have installed Ubuntu to see if it was really an issue with the nics or the routing on Pfsense. On 3.1 this was working, I'm sure.
I have one Ubuntu box running as VM that is connected to the management network and I can access it. When I attach my new installed VM to it, it cannot ping anything in that network, strange.
I also have seen that when I attach two network e1000 cards to my Pfsense box that only one is up. Th Realtek ones are both up. With the e1000 I can only ping the gateway from the PFsense install and nothing more.
What is going on here ? I'm already busy with this a long time and cannot fix it.
I hope someone can help me out here.
Have you tried my wild guess of forcing acpiEnable=False?
Cheers,
Matt
On 24 Feb 2013 22:21:20, Dan Kenigsberg wrote:
On Sun, Feb 24, 2013 at 07:18:46PM +0100, René Koch wrote:
Thanks a lot for your feedback.
I'll try to play around with qemu options next week and try to find out which setting causes this issue. What's the best way for changing this options - using hook scripts I guess...
I'm told that unsetting this option is not possible in Engine. So yeah, you are left with either hook script or a temporary hack of
diff --git a/vdsm/clientIF.py b/vdsm/clientIF.py index 38aa0d7..b489e0e 100644 --- a/vdsm/clientIF.py +++ b/vdsm/clientIF.py @@ -341,6 +341,7 @@ class clientIF: return res['status']['code']
def createVm(self, vmParams): + vmParams['acpiEnable'] = False self.vmContainerLock.acquire() self.log.info("vmContainerLock acquired by vm %s", vmParams['vmId']) _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users