WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Problem with start WinXP on xen-3.3.0 using stubdom

To: Niu Yan <vivian.niu@xxxxxxxxx>
Subject: Re: [Xen-devel] Problem with start WinXP on xen-3.3.0 using stubdom
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Thu, 30 Oct 2008 11:14:14 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 30 Oct 2008 04:12:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <e4b224300810291935l53347774mfcf6bdfd7960b598@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <e4b224300810291935l53347774mfcf6bdfd7960b598@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.14 (X11/20080505)
This could be bug #1373
(http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1373).

Can you please try to remove 'phy:/dev/cdrom1,hdc:cdrom,r' from the
disks in winxp-dm?

Niu Yan wrote:

> I have start winxp on xen-3.2.0 normally, but I want to use stubdom , so
> I try it with xen-3.3.0, I followed the steps in stubdom/README, including:
> 
> $ mkdir -p /exports/usr/share/xen/qemu
> $ ln -s /usr/share/xen/qemu/keymaps /exports/usr/share/xen/qemu
> $ mkdir -p /exports/var/lib
> $ ln -s /var/lib/xen /exports/var/lib
> $ /usr/sbin/fs-backend &
> 
> $ xm create winxp
> 
> except name the configuration file with 'winxp' and 'winxp-dm'. They are
> as follows:
> 
> $ cat /etc/xen/winxp
> kernel = "/usr/lib/xen/boot/hvmloader"
> builder='hvm'
> memory = 1280
> name = "winxp"
> vif = [ 'type=ioemu, bridge=xenbr0' ]
> device_model = '/usr/lib/xen/bin/stubdom-dm'
> boot="dc"
> sdl=0
> opengl=0
> vnc=0
> vncpasswd=''
> stdvga=0
> 
> 
> $ cat /etc/xen/winxp-dm
> kernel = "/usr/lib/xen/boot/ioemu-stubdom.gz"
> vif = [ '', 'type=ioemu, bridge=xenbr0' ]
> disk = [ 'phy:/dev/cdrom1,hdc:cdrom,r',
> 'file:/home/images/winxp.img,hda,w' ]
> 
> 
> But the sdl window closed quickly after two blink. 
> $  xm list
> Name                                        ID   Mem VCPUs      State  
> Time(s)
> Domain-0                                   0  1280     4     r-----     86.6
> winxp                                          7  1280     1     ------
>      0.0
> 
> $ xm dmesg
> (XEN) AMD SVM: ASIDs disabled.
> (XEN) CPU1: AMD K8 machine check reporting enabled.
> (XEN) CPU1: AMD Dual-Core AMD Opteron(tm) Processor 2212 stepping 02
> (XEN) Booting processor 2/2 eip 8c000
> (XEN) AMD SVM: ASIDs disabled.
> (XEN) CPU2: AMD K8 machine check reporting enabled.
> (XEN) CPU2: AMD Dual-Core AMD Opteron(tm) Processor 2212 stepping 02
> (XEN) Booting processor 3/3 eip 8c000
> (XEN) AMD SVM: ASIDs disabled.
> (XEN) CPU3: AMD K8 machine check reporting enabled.
> (XEN) CPU3: AMD Dual-Core AMD Opteron(tm) Processor 2212 stepping 02
> (XEN) Total of 4 processors activated.
> (XEN) ENABLING IO-APIC IRQs
> (XEN)  -> Using new ACK method
> (XEN) checking TSC synchronization across 4 CPUs: passed.
> (XEN) Platform timer is 25.000MHz HPET
> (XEN) Brought up 4 CPUs
> (XEN) I/O virtualisation disabled
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN)  Xen  kernel: 32-bit, PAE, lsb
> (XEN)  Dom0 kernel: 32-bit, PAE, lsb, paddr 0xc0100000 -> 0xc045257c
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN)  Dom0 alloc.:   000000003e000000->000000003f000000 (323584 pages
> to be allocated)
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN)  Loaded kernel: c0100000->c045257c
> (XEN)  Init. ramdisk: c0453000->c0ba2c00
> (XEN)  Phys-Mach map: c0ba3000->c0ce3000
> (XEN)  Start info:    c0ce3000->c0ce3474
> (XEN)  Page tables:   c0ce4000->c0cf1000
> (XEN)  Boot stack:    c0cf1000->c0cf2000
> (XEN)  TOTAL:         c0000000->c1000000
> (XEN)  ENTRY ADDRESS: c0100000
> (XEN) Dom0 has maximum 4 VCPUs
> (XEN) Scrubbing Free RAM: ..........................done.
> (XEN) Xen trace buffers: disabled
> (XEN) Std. Loglevel: Errors and warnings
> (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
> (XEN) Xen is relinquishing VGA console.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> input to Xen)
> (XEN) Freed 100kB init memory.
> (XEN) mtrr: type mismatch for f0000000,2000000 old: write-back new:
> write-combining
> 
> $ cat /var/log/xen/qemu-dm-winxp.log
> Using config file "/etc/xen/winxp-dm".
> Started domain winxp-dm
> 
> $ cat /var/log/xen/xend-debug.log
> qemu: the number of cpus is 1
> Xend started at Wed Oct 29 21:07:04 2008.
> 
> $ cat /var/log/xen/xend.log
> [2008-10-29 21:07:07 3422] DEBUG (XendDomainInfo:1443)
> XendDomainInfo.handleShutdownWatch
> [2008-10-29 21:07:07 3422] DEBUG (DevController:155) Waiting for devices
> vif.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:160) Waiting for 0.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:645)
> hotplugStatusCallback /local/domain/0/backend/vif/9/0/hotplug-status.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:659)
> hotplugStatusCallback 1.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:160) Waiting for 1.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:645)
> hotplugStatusCallback /local/domain/0/backend/vif/9/1/hotplug-status.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:659)
> hotplugStatusCallback 1.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:155) Waiting for devices
> vscsi.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:155) Waiting for devices
> vbd.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:160) Waiting for 5632.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:645)
> hotplugStatusCallback /local/domain/0/backend/vbd/9/5632/hotplug-status.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:645)
> hotplugStatusCallback /local/domain/0/backend/vbd/9/5632/hotplug-status.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:659)
> hotplugStatusCallback 1.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:160) Waiting for 768.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:645)
> hotplugStatusCallback /local/domain/0/backend/vbd/9/768/hotplug-status.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:659)
> hotplugStatusCallback 1.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:155) Waiting for devices
> irq.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:155) Waiting for devices
> vkbd.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:155) Waiting for devices
> vfb.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:155) Waiting for devices
> console.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:160) Waiting for 0.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:155) Waiting for devices
> pci.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:155) Waiting for devices
> ioports.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:155) Waiting for devices
> tap.
> [2008-10-29 21:07:07 3422] DEBUG (DevController:155) Waiting for devices
> vtpm.
> [2008-10-29 21:07:07 3422] WARNING (XendDomainInfo:1617) Domain has
> crashed: name=winxp-dm id=9.
> [2008-10-29 21:07:08 3422] ERROR (XendDomainInfo:1755) VM winxp-dm
> restarting too fast (1.624753 seconds since the last restart).  Refusing
> to restart to avoid loops.
> [2008-10-29 21:07:08 3422] DEBUG (XendDomainInfo:2389)
> XendDomainInfo.destroy: domid=9
> [2008-10-29 21:07:08 3422] DEBUG (XendDomainInfo:2406)
> XendDomainInfo.destroyDomain(9)
> [2008-10-29 21:07:08 3422] DEBUG (XendDomainInfo:1939) Destroying device
> model
> [2008-10-29 21:07:08 3422] WARNING (image:472) domain winxp-dm: device
> model failure: no longer running; see /var/log/xen/qemu-dm-
> 
> $ cat winxp-dm.log
> [2008-10-29 21:07:08 3422] DEBUG (XendDomainInfo:1946) Releasing devices
> [2008-10-29 21:07:08 3422] DEBUG (XendDomainInfo:1952) Removing vif/0
> [2008-10-29 21:07:08 3422] DEBUG (XendDomainInfo:888)
> XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
> [2008-10-29 21:07:08 3422] DEBUG (XendDomainInfo:1952) Removing vif/1
> [2008-10-29 21:07:08 3422] DEBUG (XendDomainInfo:888)
> XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/1
> [2008-10-29 21:07:08 3422] DEBUG (XendDomainInfo:1952) Removing vbd/5632
> [2008-10-29 21:07:08 3422] DEBUG (XendDomainInfo:888)
> XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/5632
> [2008-10-29 21:07:08 3422] DEBUG (XendDomainInfo:1952) Removing vbd/768
> [2008-10-29 21:07:08 3422] DEBUG (XendDomainInfo:888)
> XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
> [2008-10-29 21:07:08 3422] DEBUG (XendDomainInfo:1952) Removing vkbd/0
> [2008-10-29 21:07:08 3422] DEBUG (XendDomainInfo:888)
> XendDomainInfo.destroyDevice: deviceClass = vkbd, device = vkbd/0
> [2008-10-29 21:07:08 3422] DEBUG (XendDomainInfo:1952) Removing vfb/0
> [2008-10-29 21:07:08 3422] DEBUG (XendDomainInfo:888)
> XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
> [2008-10-29 21:07:08 3422] DEBUG (XendDomainInfo:1952) Removing console/0
> [2008-10-29 21:07:08 3422] DEBUG (XendDomainInfo:888)
> XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
> [2008-10-29 21:07:08 3422] DEBUG (XendDomainInfo:1944) No device model
> [2008-10-29 21:07:08 3422] DEBUG (XendDomainInfo:1946) Releasing devices
> 



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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