This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 832] New: Both Linux and Windows VMX domain fail to rebo

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 832] New: Both Linux and Windows VMX domain fail to reboot with "cdrom" is configured
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 6 Dec 2006 00:00:07 -0800
Delivery-date: Wed, 06 Dec 2006 00:01:08 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: Both Linux and Windows VMX domain fail to reboot with
                    "cdrom" is configured
           Product: Xen
           Version: unstable
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Guest-OS
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: ping.y.yu@xxxxxxxxx

Bug detailed description:
If "cdrom" is configured, Linux and Windows guest OS fail to reboot. It just
halt down. If "cdrom" is not configured, "reboot" is OK.

Here is some log fron xend.log:
2006-12-06 09:37:58 xend.XendDomainInfo 4748] DEBUG (XendDomainInfo:1484) 
XendDomainInfo.destroy: domid=None
[2006-12-06 09:37:58 xend.XendDomainInfo 4748] DEBUG (XendDomainInfo:1492) 
[2006-12-06 09:37:58 xend.XendDomainInfo 4748] ERROR (XendDomainInfo:1115) 
Failed to restart domain 165.
Traceback (most recent call last):
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1101, in _restart
    new_dom = XendDomain.instance().domain_create(config)
  File "/usr/lib/python/xen/xend/XendDomain.py", line 849, in domain_create
    dominfo = XendDomainInfo.create(config)
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 154, in create
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 442, in start
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1339, in _initDomain
  File "/usr/lib/python/xen/xend/image.py", line 45, in create
  File "/usr/lib/python/xen/xend/image.py", line 243, in __init__
    ImageHandler.__init__(self, vm, vmConfig, imageConfig, deviceConfig)
  File "/usr/lib/python/xen/xend/image.py", line 75, in __init__
    self.configure(vmConfig, imageConfig, deviceConfig)
  File "/usr/lib/python/xen/xend/image.py", line 255, in configure
    self.dmargs = self.parseDeviceModelArgs(imageConfig, deviceConfig)
  File "/usr/lib/python/xen/xend/image.py", line 341, in parseDeviceModelArgs
    uname = devinfo['uname']
KeyError: 'uname'

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

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>