http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=101

Summary: XendDomainInfo self.channel is not intialized for dom0 Product: Xen Version: unstable Platform: All OS/Version: Linux-2.6 Status: NEW Severity: normal Priority: P2 Component: Tools AssignedTo: xen-...@lists.xensource.com ReportedBy: rya...@us.ibm.com

I'm not certain why, but self.channel for dom0 is not intialized. I can see this when testing dom0 vcpu-hotplug with the attached patch applied.

root@bebop:/var/log # xm list Name Id Mem(MB) CPU VCPU(s) State Time(s) Console Domain-0 0 507 0 2 r---- 20.0 root@bebop:/var/log # xm list -v Name Id VCPU CPU CPUMAP Domain-0 0 0 0 0x3 Domain-0 0 1 1 0x3 root@bebop:/var/log # xm vcpu-hotplug 0 1 0 Traceback (most recent call last): File "/usr/lib/python2.4/logging/handlers.py", line 62, in emit if self.shouldRollover(record): File "/usr/lib/python2.4/logging/handlers.py", line 132, in shouldRollover self.stream.seek(0, 2) #due to non-posix-compliant Windows feature ValueError: I/O operation on closed file [xend] ERROR (XendDomainInfo:975) self.channel is not valid

Putting a call to self.create_channel() if not self.channel works, but it is a hack.

------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.