Hi all Thanks for reading this article... I install Xen 4.1.2 with Ubuntu 10.04 64-bit server. I can run Para-virtualization and HVM with qemu-dm. I want to try stub domain, but it fails. Here''s my log and cfg below. cat stub-xl kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' memory = 2048 name = "rtes-big-stub-1" vcpus=2 vif = [ ''type=ioemu, bridge=xenbr0'' ] disk = [ ''file:/home/rtes-big/guestfull1/ubuntu.img,hda,w'' ] device_model_stubdomain_override = 1 boot="c" sdl=0 vnc=1 vnclisten="0.0.0.0" vncconsole=1 vncpasswd=''rtes'' stdvga=0 serial=''pty'' sudo xl create -c stub-xl Parsing config file stub-xl xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->0000000000179830 TOTAL: 0000000000000000->000000007f800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000000 Daemon running with PID 3909 The process stop here cat /var/log/xen/xl-rtes-big-stub-1.log Waiting for domain rtes-big-stub-1 (domid 3) to die [pid 3911] cat /var/log/xen/xen-hotplug.log RTNETLINK answers: Operation not supported cat qemu-dm-rtes-big-stub-1.log domid: 3 -videoram option does not work with cirrus vga device model. Videoram set to 4M. Using file /dev/xen/blktap-2/tapdev0 in read-write mode Watching /local/domain/0/device-model/3/logdirty/cmd Watching /local/domain/0/device-model/3/command Watching /local/domain/3/cpu char device redirected to /dev/pts/2 qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = d21e248b-1d3b-42d5-8ba5-125b586bac7f 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/3/xen_extended_power_mgmt): read error 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 vcpu-set: watch node error. xs_read(/local/domain/3/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/3/log-throttling'' medium change watch on `/local/domain/3/log-throttling'' - unknown device, ignored cirrus vga map change while on lfb mode mapping vram to f0000000 - f0400000 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. I know xen-hotplug.log tells me I missed something. But I can''t figure it out..... Thanks for reading this page.... -- View this message in context: http://xen.1045712.n5.nabble.com/Cannot-run-Stub-domain-in-Ubuntu-tp5712254.html Sent from the Xen - User mailing list archive at Nabble.com.
On Sun, 2012-11-04 at 05:36 +0000, fronter wrote:> Hi all > > Thanks for reading this article... > > I install Xen 4.1.2 with Ubuntu 10.04 64-bit server. > > I can run Para-virtualization and HVM with qemu-dm. > > I want to try stub domain, but it fails.I''m not sure if xl in 4.1.2 was capable of doing stubdomains properly (it was a tech preview) or not. I''d recommend using xl from 4.2 or sticking with xend in 4.1.x. FYI "xl -vvv create ..." often gives more useful debugging output. Ian.> > Here''s my log and cfg below. > > cat stub-xl > > kernel = "/usr/lib/xen/boot/hvmloader" > builder=''hvm'' > memory = 2048 > name = "rtes-big-stub-1" > vcpus=2 > vif = [ ''type=ioemu, bridge=xenbr0'' ] > disk = [ ''file:/home/rtes-big/guestfull1/ubuntu.img,hda,w'' ] > device_model_stubdomain_override = 1 > boot="c" > sdl=0 > vnc=1 > vnclisten="0.0.0.0" > vncconsole=1 > vncpasswd=''rtes'' > stdvga=0 > serial=''pty'' > > > sudo xl create -c stub-xl > > Parsing config file stub-xl > xc: info: VIRTUAL MEMORY ARRANGEMENT: > Loader: 0000000000100000->0000000000179830 > TOTAL: 0000000000000000->000000007f800000 > ENTRY ADDRESS: 0000000000100000 > xc: info: PHYSICAL MEMORY ALLOCATION: > 4KB PAGES: 0x0000000000000200 > 2MB PAGES: 0x00000000000003fb > 1GB PAGES: 0x0000000000000000 > Daemon running with PID 3909 > > > > The process stop here > > > > cat /var/log/xen/xl-rtes-big-stub-1.log > Waiting for domain rtes-big-stub-1 (domid 3) to die [pid 3911] > > cat /var/log/xen/xen-hotplug.log > RTNETLINK answers: Operation not supported > > > cat qemu-dm-rtes-big-stub-1.log > > domid: 3 > -videoram option does not work with cirrus vga device model. Videoram set to > 4M. > Using file /dev/xen/blktap-2/tapdev0 in read-write mode > Watching /local/domain/0/device-model/3/logdirty/cmd > Watching /local/domain/0/device-model/3/command > Watching /local/domain/3/cpu > char device redirected to /dev/pts/2 > qemu_map_cache_init nr_buckets = 10000 size 4194304 > shared page at pfn feffd > buffered io page at pfn feffb > Guest uuid = d21e248b-1d3b-42d5-8ba5-125b586bac7f > 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/3/xen_extended_power_mgmt): read error > 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 > vcpu-set: watch node error. > xs_read(/local/domain/3/log-throttling): read error > qemu: ignoring not-understood drive `/local/domain/3/log-throttling'' > medium change watch on `/local/domain/3/log-throttling'' - unknown device, > ignored > cirrus vga map change while on lfb mode > mapping vram to f0000000 - f0400000 > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw > state. > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro > state. > > > > > > I know xen-hotplug.log tells me I missed something. But I can''t figure it > out..... > Thanks for reading this page.... > > > > > > > > > > -- > View this message in context: http://xen.1045712.n5.nabble.com/Cannot-run-Stub-domain-in-Ubuntu-tp5712254.html > Sent from the Xen - User mailing list archive at Nabble.com. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users
Thanks for your reply. I install Xen 4.2 with ubuntu 12.04 server 64bit. I follow the installation guide here <http://wiki.xen.org/mediawiki/images/b/b6/Building_and_Installing_Xen_4.x_and_Linux_Kernel_3.x_on_Ubuntu_and_Debian_Linux_-_Version_2.0_-_REDUCED.pdf> I can run hvm with qemu-dm. But, I still can not run hvm with stub domain. ==== configure file ===cat xl-exe firmware_override = "/usr/lib/xen/boot/hvmloader" builder="hvm" name="full-1" device_model_version="qemu-xen-traditional" device_model_override = ''/usr/lib/xen/bin/stubdom-dm'' device_model_stubdomain_override = 1 vcpus=2 memory=2048 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" disk = [ ''file:/home/rtes-big/guestfull1/ubuntu.img,hda,w'', ''file:/home/rtes-big/image/ubuntu-12.04.1-server-amd64.iso,hdc:cdrom,r'' ] boot="c" acpi=0 stdvga=0 vnc=1 vnclisten="localhost" vncpasswd="passwd" sdl=0 usb=1 gfx_passthru=0 vncconsole=1 serial=''pty'' cat xl-exe-dm mem=128 disk = [ ''file:/home/rtes-big/guestfull1/ubuntu.img,hda,w'', ] kernel = "/usr/lib/xen/boot/ioemu-stubdom.gz" vif = [ ''bridge=xenbr0'', ] serial=''pty'' vnc=1 vnclisten="localhost" vncpasswd="passwd" sdl=0 usb=1 vncconsole=1 ==== Create HVM ===sudo xl create -c xl-exe Parsing config from xl-exe xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->000000000019db48 TOTAL: 0000000000000000->000000007f800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000000 libxl: error: libxl_exec.c:436:spawn_middle_death: domain 84 device model [20048]: unexpectedly exited with exit status 0, when we were waiting for it to confirm startup libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 84 device model: spawn failed (rc=-3) Daemon running with PID 20092 xenconsole: Could not read tty from store: No such file or directory libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited with error status 2 ==== Log ===less /var/log/xen/xl-full-1.log Waiting for domain full-1 (domid 83) to die [pid 20093] less /var/log/xen/qemu-dm-full-1-dm.log xenstore-ls: xs_directory (/local/domain/84/device/vif): No such file or directory mkfifo: cannot create fifo `/tmp/full-1-dm-dm'': File exists Error: Block device type "qdisk" is invalid. Using config file "/etc/xen/stubdoms/full-1-dm-dm". Using config file "/etc/xen/stubdoms/full-1-dm-dm". -- View this message in context: http://xen.1045712.n5.nabble.com/Cannot-run-Stub-domain-in-Ubuntu-tp5712254p5712325.html Sent from the Xen - User mailing list archive at Nabble.com.
Do I need to stop xend service? when I execute sudo xl -vvv create -c xl-exe , I get the message below xend is running, which may cause unpredictable results when using this xl command. Please shut down xend before continuing. (This check can be overridden with the -f option.) xc: debug: hypercall buffer: total allocations:0 total releases:0 xc: debug: hypercall buffer: current allocations:0 maximum allocations:0 xc: debug: hypercall buffer: cache current size:0 xc: debug: hypercall buffer: cache hits:0 misses:0 toobig:0 if I sudo service xend stop, /var/log/xen/qemu-dm-full-1-dm.log get the message below Error: Unable to connect to xend: Connection refused. Is xend running? xenstore-ls: xs_directory (/local/domain/129/device/vif): No such file or directory mkfifo: cannot create fifo `/tmp/full-1-dm-dm'': File exists Error: Unable to connect to xend: Connection refused. Is xend running? Using config file "/etc/xen/stubdoms/full-1-dm-dm". Using config file "/etc/xen/stubdoms/full-1-dm-dm". -- View this message in context: http://xen.1045712.n5.nabble.com/Cannot-run-Stub-domain-in-Ubuntu-tp5712254p5712326.html Sent from the Xen - User mailing list archive at Nabble.com.