Xen project Mailing List

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

To: Niu Yan <vivian.niu@xxxxxxxxx>

From: "Wan, Shuang" <shuang.wan@xxxxxxxxx>

Date: Thu, 30 Oct 2008 14:36:57 +0800

Accept-language: en-US

Acceptlanguage: en-US

Cc: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>

Delivery-date: Wed, 29 Oct 2008 23:37:59 -0700

List-id: Xen user discussion <xen-users.lists.xensource.com>

Thread-index: Ack6WNj/caBO9RMKQxSE1qeqeWjKzAAADI8w

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

You need to use # to mask this line: (while true ; do sleep 60 ; done) | /bin/sh -c "$creation" & , Also you can redirect log messages to a file, just modify this line: creation=âxm create âc $domname-dm target=$domid memory=32 extra=\â$extra\"" To creation=âxm create âc $domname-dm target=$domid memory=32 extra=\â$extra\" >/your_log_file" ________________________________________ From: Niu Yan [mailto:vivian.niu@xxxxxxxxx] Sent: 2008å10æ30æ 14:29 To: Wan, Shuang Cc: xen-users@xxxxxxxxxxxxxxxxxxx Subject: Re: [Xen-users] Problem with start winxp on xen-3.3.0 using stubdom 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

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.