Re: [vdsm] Problem hotplugging an Interface

2012-08-28 Thread Dan Kenigsberg 
On Thu, Aug 16, 2012 at 01:19:46PM +, Itzik Brown wrote:
 The same - 'acpiEnable': 'true'  
 
 Itzik
 
 -Original Message-
 From: Dan Kenigsberg [mailto:dan...@redhat.com] 
 Sent: יום ה 16 אוגוסט 2012 15:42
 To: Itzik Brown
 Cc: vdsm-devel@lists.fedorahosted.org
 Subject: Re: [vdsm] Problem hotplugging an Interface
 
 On Thu, Aug 16, 2012 at 12:11:52PM +, Itzik Brown wrote:
  1. I'm sure I'm using the same libvirt and qemu.
  2. Here are the files:
  
  Domxml of the VM running with packages from the repository(before attaching 
  NIC):
  
  domain type='kvm' id='10'
namevm1/name
uuid54028863-6910-44ac-a843-a61083e65b70/uuid
memory unit='KiB'2097152/memory
currentMemory unit='KiB'2097152/currentMemory
vcpu1/vcpu
cputune
  shares1020/shares
/cputune
sysinfo type='smbios'
  system
entry name='manufacturer'Red Hat/entry
entry name='product'RHEV Hypervisor/entry
entry name='version'17-1/entry
entry 
  name='serial'53D19F64-D663-A017-8922-003048C440B8_00:30:48:c4:40:b8/entry
entry name='uuid'54028863-6910-44ac-a843-a61083e65b70/entry
  /system
/sysinfo
os
  type arch='x86_64' machine='pc-0.14'hvm/type
  smbios mode='sysinfo'/
/os
features
  acpi/
/features
 
 A diff reveals that this is missing from your other domain. Also, upstream 
 creates a socket for qemu guest agent, but I put my money on acpi.
 
 Could you post the vmCreate parameters in the two case? I would like to 
 verify that acpiEnable is the same.
 

Itzik, I'm sorry that I've missed your response for over a weak.
I believe that I've nailed this upstream bug. Please review
http://gerrit.ovirt.org/7533
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel

[vdsm] Problem hotplugging an Interface

2012-08-15 Thread Itzik Brown 
Hi,

I installed vdsm latest git version.
When trying to hotplug a new NIC the operation fails.

Here are some lines from vdsmd.log 

Thread-480::DEBUG::2012-08-15 
11:50:52,150::libvirtvm::1398::vm.Vm::(hotplugNic) 
vmId=`54028863-6910-44ac-a843-a61083e65b70`::Hotplug NIC xml: interface 
type=bridge
mac address=00:1a:4a:1e:31:0c/
model type=virtio/
source bridge=ovirtmgmt/
/interface

Thread-480::ERROR::2012-08-15 
11:50:52,297::libvirtvm::1403::vm.Vm::(hotplugNic) 
vmId=`54028863-6910-44ac-a843-a61083e65b70`::Hotplug failed
Traceback (most recent call last):
  File /usr/share/vdsm/libvirtvm.py, line 1401, in hotplugNic
self._dom.attachDevice(nicXml)
  File /usr/share/vdsm/libvirtvm.py, line 487, in f
ret = attr(*args, **kwargs)
  File /usr/lib64/python2.7/site-packages/vdsm/libvirtconnection.py, line 82, 
in wrapper
ret = f(*args, **kwargs)
  File /usr/lib64/python2.7/site-packages/libvirt.py, line 400, in 
attachDevice
if ret == -1: raise libvirtError ('virDomainAttachDevice() failed', 
dom=self)
libvirtError: internal error unable to execute QEMU command 'device_add': Bus 
'pci.0' does not support hotplugging

OS: Fedora17
VDSM Packages: vdsm-4.10.0-0.313.git8bedc7e.fc17.x86_64 
vdsm-xmlrpc-4.10.0-0.313.git8bedc7e.fc17.noarch 
vdsm-python-4.10.0-0.313.git8bedc7e.fc17.x86_64
Libvirt: libvirt-0.9.11.4-3.fc17.x86_64
QEMU: qemu-common-1.0.1-1.fc17.x86_64

Trying to attach the NIC using virsh fails as well:

virsh -c qemu+tcp://localhost/system attach-device vm1 --file /tmp/1.xml
error: Failed to attach device from /tmp/1.xml
error: internal error unable to execute QEMU command 'device_add': Bus 'pci.0' 
does not support hotplugging


When running with VDSM from ovirt repository with the following packages the 
hotplug of the NIC works:
vdsm-xmlrpc-4.10.0-6.fc17.noarch
vdsm-4.10.0-6.fc17.x86_64
vdsm-python-4.10.0-6.fc17.x86_64

Please advise,
Itzik

___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel