Re: [Users] oVirt 3.2 and Solaris 10 guests

2013-02-27 Thread YamakasY
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.

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



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] oVirt 3.2 and Solaris 10 guests

2013-02-27 Thread Dan Kenigsberg
On Wed, Feb 27, 2013 at 11:16:53AM +, 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
 
 
 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] oVirt 3.2 and Solaris 10 guests

2013-02-24 Thread René Koch
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...


Regards,
René

 
 
-Original message-
 From:Dan Kenigsberg dan...@redhat.com
 Sent: Wednesday 20th February 2013 11:52
 To: René Koch r.k...@ovido.at
 Cc: Jean-Francois Saucier jsauc...@gmail.com; ovirt-users users@ovirt.org
 Subject: Re: [Users] oVirt 3.2 and Solaris 10 guests
 
 On Thu, Feb 14, 2013 at 05:25:47PM +0100, René Koch (ovido) wrote:
  
  On Thu, 2013-02-14 at 11:22 -0500, Jean-Francois Saucier wrote:
   On Thu, Feb 14, 2013 at 11:21 AM, Jiri Belka jbe...@redhat.com
   wrote:
   On Thu, 14 Feb 2013 10:49:13 -0500
   Jean-Francois Saucier jsauc...@gmail.com wrote:
   
 oVirt 3.2:
 -netdev tap,fd=25,id=hostnet0 -device


   
   rtl8139,netdev=hostnet0,id=net0,mac=00:1a:4a:00:64:9e,bus=pci.0,addr=0x3,bootindex=3
   
   ^^^ - realtek, really? Try e1000 which is usually much
   more reliable or virtio iface. I personally always had
   terrible
   experience with emulated rtl8139 by qemu-kvm, e1000 was OK.
   
   For me, it's the same if I choose the e1000 (which I choose the first
   time and then try the rtl8139).
   
  Same for me - e1000 aren't working with oVirt 3.2 and Solaris 10, too.
 
 I've heard rumours that it might be related to the fact that oVirt
 starts VMs with ACPI enabled by default (there's a way in Engine to turn
 this off).
 
 If this is not the case, please do a more extensive bisection of the
 qemu command line. You have one bad cmdline; start trimming it until
 it becomes good.
 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] oVirt 3.2 and Solaris 10 guests

2013-02-24 Thread Dan Kenigsberg
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


Re: [Users] oVirt 3.2 and Solaris 10 guests

2013-02-20 Thread Dan Kenigsberg
On Thu, Feb 14, 2013 at 05:25:47PM +0100, René Koch (ovido) wrote:
 
 On Thu, 2013-02-14 at 11:22 -0500, Jean-Francois Saucier wrote:
  On Thu, Feb 14, 2013 at 11:21 AM, Jiri Belka jbe...@redhat.com
  wrote:
  On Thu, 14 Feb 2013 10:49:13 -0500
  Jean-Francois Saucier jsauc...@gmail.com wrote:
  
oVirt 3.2:
-netdev tap,fd=25,id=hostnet0 -device
   
   
  
  rtl8139,netdev=hostnet0,id=net0,mac=00:1a:4a:00:64:9e,bus=pci.0,addr=0x3,bootindex=3
  
  ^^^ - realtek, really? Try e1000 which is usually much
  more reliable or virtio iface. I personally always had
  terrible
  experience with emulated rtl8139 by qemu-kvm, e1000 was OK.
  
  For me, it's the same if I choose the e1000 (which I choose the first
  time and then try the rtl8139).
  
 Same for me - e1000 aren't working with oVirt 3.2 and Solaris 10, too.

I've heard rumours that it might be related to the fact that oVirt
starts VMs with ACPI enabled by default (there's a way in Engine to turn
this off).

If this is not the case, please do a more extensive bisection of the
qemu command line. You have one bad cmdline; start trimming it until
it becomes good.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[Users] oVirt 3.2 and Solaris 10 guests

2013-02-14 Thread Koch (ovido)
Hi,

I've a strange network issue with Solaris 10 x86 guests on oVirt 3.2
(beta) with an CentOS 6.3 hypervisor (using dreyou's repository for VDSM
packages).

My host configuration is the following:
Operating system: Other
Network interface type: rtl8139
Network Name: ovirtmgmt
Disk interface: IDE

Disk is working fine and the network interface is detected by Solaris 10
guest, as I can see a rtls0 interface with ifconfig -a and Solaris
installer also detects this interface.

But when I try to send packages over this interface they never reach a
target - e.g. ping the gateway and arp -an doesn't show it's MAC
address. On the hypervisor I can see vnet(x) interface is on ovirtmgmt
bridge. Network traffic is working fine for all other VMs (RHEL 6 and
Fedora 18) on ovirtmgmt bridge.

Btw, when creating a Solaris 10 guest on RHEV 3.1 with RHEL 6.3
hypervisor the exactly same issue occurs - network interface is detected
but no traffic passes this interface.

On a plain KVM-Host (RHEL 6.3) I can create a Solaris 10 host with
virt-manager using rtl8139 Virtual Network Interface Device model on a
bridge (network setup is nearly the same as for oVirt and RHEV). On this
RHEL 6.3 KVM-host network is working fine for Solaris guests.

In the process list (ps -ef) the settings for oVirt and RHEL-KVM seem
the be nearly the same (different fd's and option bootindex=3 is missing
on KVM):

oVirt 3.2:
-netdev tap,fd=25,id=hostnet0 -device
rtl8139,netdev=hostnet0,id=net0,mac=00:1a:4a:00:64:9e,bus=pci.0,addr=0x3,bootindex=3
 

RHEL 6.3 KVM: 
-netdev tap,fd=36,id=hostnet0 -device
rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:8e:3a:57,bus=pci.0,addr=0x3 

KVM-Version is exactly the same on CentOS-oVirt-Hypervisor as on RHEL
KVM-host:
# rpm -qa | grep kvm
qemu-kvm-rhev-tools-0.12.1.2-2.295.el6.10.x86_64
qemu-kvm-rhev-0.12.1.2-2.295.el6.10.x86_64

Do you have any clue why Solaris networking isn't working on oVirt but
on RHEL-KVM it is?

I didn't try Fedora 18 or oVirt Node as a hypervisor yet - don't think
that there will be a difference.

Thanks a lot for your feedback.


-- 
Best Regards,
René Koch




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] oVirt 3.2 and Solaris 10 guests

2013-02-14 Thread Jean-Francois Saucier
I can confirm the same issue with Solaris 11 and oVirt 3.1. Everything
seems OK, my network card is configured correctly (static IP) but cannot
communicate with anyone.


On Thu, Feb 14, 2013 at 10:46 AM, René Koch (ovido) r.k...@ovido.at wrote:

 Hi,

 I've a strange network issue with Solaris 10 x86 guests on oVirt 3.2
 (beta) with an CentOS 6.3 hypervisor (using dreyou's repository for VDSM
 packages).

 My host configuration is the following:
 Operating system: Other
 Network interface type: rtl8139
 Network Name: ovirtmgmt
 Disk interface: IDE

 Disk is working fine and the network interface is detected by Solaris 10
 guest, as I can see a rtls0 interface with ifconfig -a and Solaris
 installer also detects this interface.

 But when I try to send packages over this interface they never reach a
 target - e.g. ping the gateway and arp -an doesn't show it's MAC
 address. On the hypervisor I can see vnet(x) interface is on ovirtmgmt
 bridge. Network traffic is working fine for all other VMs (RHEL 6 and
 Fedora 18) on ovirtmgmt bridge.

 Btw, when creating a Solaris 10 guest on RHEV 3.1 with RHEL 6.3
 hypervisor the exactly same issue occurs - network interface is detected
 but no traffic passes this interface.

 On a plain KVM-Host (RHEL 6.3) I can create a Solaris 10 host with
 virt-manager using rtl8139 Virtual Network Interface Device model on a
 bridge (network setup is nearly the same as for oVirt and RHEV). On this
 RHEL 6.3 KVM-host network is working fine for Solaris guests.

 In the process list (ps -ef) the settings for oVirt and RHEL-KVM seem
 the be nearly the same (different fd's and option bootindex=3 is missing
 on KVM):

 oVirt 3.2:
 -netdev tap,fd=25,id=hostnet0 -device

 rtl8139,netdev=hostnet0,id=net0,mac=00:1a:4a:00:64:9e,bus=pci.0,addr=0x3,bootindex=3

 RHEL 6.3 KVM:
 -netdev tap,fd=36,id=hostnet0 -device
 rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:8e:3a:57,bus=pci.0,addr=0x3

 KVM-Version is exactly the same on CentOS-oVirt-Hypervisor as on RHEL
 KVM-host:
 # rpm -qa | grep kvm
 qemu-kvm-rhev-tools-0.12.1.2-2.295.el6.10.x86_64
 qemu-kvm-rhev-0.12.1.2-2.295.el6.10.x86_64

 Do you have any clue why Solaris networking isn't working on oVirt but
 on RHEL-KVM it is?

 I didn't try Fedora 18 or oVirt Node as a hypervisor yet - don't think
 that there will be a difference.

 Thanks a lot for your feedback.


 --
 Best Regards,
 René Koch




 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users




-- 
Jean-Francois Saucier (djf_jeff)
GPG key : 0xA9E6E953
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] oVirt 3.2 and Solaris 10 guests

2013-02-14 Thread Jiri Belka
On Thu, 14 Feb 2013 10:49:13 -0500
Jean-Francois Saucier jsauc...@gmail.com wrote:

  oVirt 3.2:
  -netdev tap,fd=25,id=hostnet0 -device
 
  rtl8139,netdev=hostnet0,id=net0,mac=00:1a:4a:00:64:9e,bus=pci.0,addr=0x3,bootindex=3
^^^ - realtek, really? Try e1000 which is usually much
more reliable or virtio iface. I personally always had terrible
experience with emulated rtl8139 by qemu-kvm, e1000 was OK.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] oVirt 3.2 and Solaris 10 guests

2013-02-14 Thread Jean-Francois Saucier
On Thu, Feb 14, 2013 at 11:21 AM, Jiri Belka jbe...@redhat.com wrote:

 On Thu, 14 Feb 2013 10:49:13 -0500
 Jean-Francois Saucier jsauc...@gmail.com wrote:

   oVirt 3.2:
   -netdev tap,fd=25,id=hostnet0 -device
  
  
 rtl8139,netdev=hostnet0,id=net0,mac=00:1a:4a:00:64:9e,bus=pci.0,addr=0x3,bootindex=3
 ^^^ - realtek, really? Try e1000 which is usually much
 more reliable or virtio iface. I personally always had terrible
 experience with emulated rtl8139 by qemu-kvm, e1000 was OK.


For me, it's the same if I choose the e1000 (which I choose the first time
and then try the rtl8139).

-- 
Jean-Francois Saucier (djf_jeff)
GPG key : 0xA9E6E953
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] oVirt 3.2 and Solaris 10 guests

2013-02-14 Thread Koch (ovido)

On Thu, 2013-02-14 at 11:22 -0500, Jean-Francois Saucier wrote:
 On Thu, Feb 14, 2013 at 11:21 AM, Jiri Belka jbe...@redhat.com
 wrote:
 On Thu, 14 Feb 2013 10:49:13 -0500
 Jean-Francois Saucier jsauc...@gmail.com wrote:
 
   oVirt 3.2:
   -netdev tap,fd=25,id=hostnet0 -device
  
  
 
 rtl8139,netdev=hostnet0,id=net0,mac=00:1a:4a:00:64:9e,bus=pci.0,addr=0x3,bootindex=3
 
 ^^^ - realtek, really? Try e1000 which is usually much
 more reliable or virtio iface. I personally always had
 terrible
 experience with emulated rtl8139 by qemu-kvm, e1000 was OK.
 
 For me, it's the same if I choose the e1000 (which I choose the first
 time and then try the rtl8139).
 
Same for me - e1000 aren't working with oVirt 3.2 and Solaris 10, too.


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users