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-users

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [Xen-users] Problem with start winxp on xen-3.3.0 using stubdom

from [Niu Yan] [Permanent Link][Original]
To: "Wan, Shuang" <shuang.wan@xxxxxxxxx>
Subject: Re: [Xen-users] Problem with start winxp on xen-3.3.0 using stubdom
From: "Niu Yan" <vivian.niu@xxxxxxxxx>
Date: Thu, 30 Oct 2008 14:29:14 +0800
Cc: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 29 Oct 2008 23:31:28 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=N0tYt0B8SO8LI4VICF7pRVsQb5n+7uuvTcEJg21O1hg=; b=YMqZG03ITkzIi4n7VekaEugaF4dXEkjuFAHdKf5hVjLJ3R3DxKan/5PMgP2jKHaOs4 nW/7kqfNcMqbjkvczb8NwFVSFjOk9v9oIPTpkOJ9KyUpr5ccJlYqMldv5RXNf+prhMH4 EhVvV3NWkVdlhGkBW6/MrWiew2xO/GEF4DZ+4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=XcYvEv5Na5oRxG9qpaP1rOBItnYfGqbl8L3cKd7xDzj4Gmc21ALzwQnr7Aigt8uMHO MjMgI4iHVwj2/OK/mMLPcWIvX2NdlakD16DTUvBEkwhfnEdNYEGywTY9jQ0L5ApZlpbt 7eeqiaHLdDbAXGv3oitadbBzaxwVAsRzsuOl8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <e4b224300810292314u5d5674e1o3459d854de11035@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <e4b224300810291949n244a8039hf9a7495e89309a28@xxxxxxxxxxxxxx> <E2263E4A5B2284449EEBD0AAB751098401C00BA0BA@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <e4b224300810292314u5d5674e1o3459d854de11035@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I have uncomment line 'xterm -geometry ......'  in /usr/lib/xen/bin/stub-dm, and two windows popped up,  the first one closed automatically, and the second window said:

Using config file "/etc/xen/winxp-dm"
Error: Domain 'winxp-dm' already exists with ID '17'
Press ENTER to shut down
 
$ cat ps aux | grep stub

root     13863  0.0  0.0   4716  1180 ?        S    14:23   0:00 /bin/bash /usr/lib/xen/bin/stubdom-dm -d 16 -domain-name winxp -nographic -vcpus 1 -boot dc -acpi -net nic,vlan=1,macaddr=00:16:3e:76:15:0b,model=rtl8139 -net tap,vlan=1,ifname=tap16.0,bridge=xenbr0 -M xenfv
root     13911  0.0  0.0   4716   444 ?        S    14:23   0:00 /bin/bash /usr/lib/xen/bin/stubdom-dm -d 16 -domain-name winxp -nographic -vcpus 1 -boot dc -acpi -net nic,vlan=1,macaddr=00:16:3e:76:15:0b,model=rtl8139 -net tap,vlan=1,ifname=tap16.0,bridge=xenbr0 -M xenfv

Is it normal to start two stubdoms for one domain? how to avoid it?


2008/10/30 Niu Yan <vivian.niu@xxxxxxxxx>
I have try with disk = [ 'file:/home/images/winxp.img,hda,w' ]  and set boot='c' ,  the result is the   same.


2008/10/30 Wan, Shuang <shuang.wan@xxxxxxxxx>

Hi NiuYan,

 

disk = [ 'phy:/dev/cdrom1,hdc:cdrom,r', 'file:/home/images/winxp.img,hda,w' ]

Enable the hdc:cdrom configuration option in disk section is a known issue to stubdom(tested changeset 18569), you can try to remove it.

And also there a another place you can catch many of useful log message, you can edit the /usr/lib/xen/bin/stubdom-dm, change the lines as bellow:

#(while true ; do sleep 60 ; done) | /bin/sh -c "$creation" &

xterm -geometry +0+0 -e /bin/sh -c "$creation ; echo ; echo press ENTER to shut down ; read" &

it will popup a xterm window,  you can see many of messages from that.

 

 

Best regards

Wan Shuang

 

From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Niu Yan
Sent: 2008年10月30日 10:50
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Problem with start winxp on xen-3.3.0 using stubdom

 

There is some messages talking about start windows using stubdom on  xen-devel@xxxxxxxxxxxxxxxxxxx, but i think it may be more proper to send it here.

---------------------------

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

 

----------

vivian



--
Best regards,
Niu Yan

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  RE: [Xen-users] Problem with start winxp on xen-3.3.0 using stubdom, Wan, Shuang
Next by Date:  RE: [Xen-users] Problem with start winxp on xen-3.3.0 using stubdom, Wan, Shuang
Previous by Thread:  RE: [Xen-users] Problem with start winxp on xen-3.3.0 using stubdom, Wan, Shuang
Next by Thread:  RE: [Xen-users] Problem with start winxp on xen-3.3.0 using stubdom, Wan, Shuang
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy