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 1642] New: Crash Installing Windows XP

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1642] New: Crash Installing Windows XP
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Sat, 31 Jul 2010 15:15:01 -0700
Delivery-date: Sat, 31 Jul 2010 15:15:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: Crash Installing Windows XP
           Product: Xen
           Version: unstable
          Platform: x86-64
        OS/Version: Windows
            Status: NEW
          Severity: blocker
          Priority: P2
         Component: 2.6.18 dom0
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: tcereghetti@xxxxxxxxx
                CC: tcereghetti@xxxxxxxxx


I'm using openSUSE 11.3 with 
vmlinux-2.6.34-12-xen.gz  and  xen-4.0.0_21091_05-6.6.gz

I'm trying to install Windows XP x64 with le graphical GUI.
The installation start and all is fine until the guest (windows) try to restart
(just after having finished to copy the files).

The VM goes in the state Pause and after some minute crash.

[2010-07-31 23:41:55 5669] DEBUG (DevController:139) Waiting for devices vif.
[2010-07-31 23:41:55 5669] DEBUG (DevController:144) Waiting for 0.
[2010-07-31 23:41:55 5669] DEBUG (XendDomainInfo:1922)
[2010-07-31 23:41:55 5669] DEBUG (DevController:653) hotplugStatusCallback
[2010-07-31 23:43:35 5669] WARNING (XendDomain:1059) Failed to setup devices
for <domain id=2 name=winxp64_00 memory=3221225472 state=paused>: Device 0
(vif) could not be connected. Hotplug scripts not working.
[2010-07-31 23:43:35 5669] DEBUG (XendDomainInfo:3111) XendDomainInfo.destroy:
[2010-07-31 23:43:36 5669] DEBUG (XendDomainInfo:2446) Destroying device model
[2010-07-31 23:43:37 5669] INFO (image:626) winxp64_00 device model terminated
[2010-07-31 23:43:37 5669] DEBUG (XendDomainInfo:2453) Releasing devices
[2010-07-31 23:43:37 5669] DEBUG (XendDomainInfo:2459) Removing vif/0
[2010-07-31 23:43:37 5669] DEBUG (XendDomainInfo:1289)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2010-07-31 23:43:37 5669] DEBUG (XendDomainInfo:2459) Removing console/0
[2010-07-31 23:43:37 5669] DEBUG (XendDomainInfo:1289)
XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2010-07-31 23:43:37 5669] DEBUG (XendDomainInfo:2459) Removing vbd/768

Exception in thread UnixHttpServer:
Traceback (most recent call last):
  File "/usr/lib64/python2.6/threading.py", line 532, in __bootstrap_inner
  File "/usr/lib64/python2.6/threading.py", line 484, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib64/python2.6/site-packages/xen/web/httpserver.py", line 312, in
    (sock, addr) = self.accept()
  File "/usr/lib64/python2.6/site-packages/xen/web/httpserver.py", line 331, in
    return self.socket.accept()
  File "/usr/lib64/python2.6/socket.py", line 195, in accept
    sock, addr = self._sock.accept()
error: [Errno 22] Invalid argument

Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/xen/xend/server/Hald.py", line 55,
in shutdown
    os.kill(self.pid, signal.SIGINT)
OSError: [Errno 3] No such process
Xend started at Sat Jul 31 23:34:12 2010.
/usr/lib64/python2.6/site-packages/xen/xend/XendAPI.py:551: DeprecationWarning:
object.__new__() takes no parameters
  return object.__new__(cls, *args, **kwds)

domid: 2
config qemu network with xen bridge for  tap2.0 br0
Watching /local/domain/0/device-model/2/logdirty/cmd
Watching /local/domain/0/device-model/2/command
char device redirected to /dev/pts/1
qemu_map_cache_init nr_buckets = 10000 size 4194304
Init blktap pipes
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = 0b39bdc6-afdd-910a-0e31-d15a4ab004f8
Time offset set 0
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/2/xen_extended_power_mgmt): read error
xs_read(): vncpasswd get error.
medium change watch on `hdc' (index: 1): /data/xp64_4.iso
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Log-dirty: no command yet.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
xs_read(/local/domain/2/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/2/log-throttling'
medium change watch on `/local/domain/2/log-throttling' - unknown device,
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0

I couldn't save the configuration: after the crash all files are deleted, raw
disk included

3GB of 8GB
Disk 8GB
4 cpu ( ProBook 4520s]
file iso with windows x64

[I installed win (using the same iso) successfully with kvm on ubuntu, but then
the bridging didn't work correctly]
Thank you and regards,

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>