Hi,
I'm new to Xen. I've been trying unsucessfully to setup an x86_64 guest on my x86_64 Dom0 (both running Fedora Core 6). The dom0 system is a fresh install of FC6 with latest updates applied.
What I have been able to do is run the 'virt-install' utility to create the guest environment, however when the FC6 install finishes on the guest, it says 'rebooting' and then dies i.e. I can't see the guest listed when I do an 'xm list'.
What I've then done is 'xm create -c /etc/xen/fc6_64' (the name of the config created above) which takes my to the pygrub boot screen, then attempts to boot, however I only get as far as 'creating root device' and it stops. Now, when I do an 'xm list' I can see the guest listed but it is in the 'blocked' state. The xend.log file doesn't appear to show any errors, just a whole lot of DEBUG - the last message is 'INFO (XendDomain:370) Domain fc6_64 (1) unpaused'
Now if I try to reboot the guest i.e 'xm reboot fc6_64' things go horribly wrong. The guest console says 'restarting' then drops back to Dom0 command line. When I do 'xm list' I get the error 'Error: Device 51712 not connected' instead of the usual list and xend.log shows the following:
[2006-12-10 07:24:42 xend.XendDomainInfo 2488] DEBUG (XendDomainInfo:933) XendDomainInfo.handleShutdownWatch [2006-12-10 07:24:42 xend.XendDomainInfo 2488] DEBUG (XendDomainInfo:933) XendDomainInfo.handleShutdownWatch [2006-12-10 07:24:44 xend.XendDomainInfo 2488] INFO (XendDomainInfo:892) Domain has shutdown: name=fc6_64 id=1 reason=reboot. [2006-12-10 07:24:44 xend.XendDomainInfo 2488] DEBUG (XendDomainInfo:1457) XendDomainInfo.destroyDomain(1) [2006-12-10 07:24:44 xend.XendDomainInfo 2488] DEBUG (XendDomainInfo:190) XendDomainInfo.create(['domain', ['domid', 1], ...... [2006-12-10 07:24:44 xend.XendDomainInfo 2488] DEBUG (XendDomainInfo:296) parseConfig: config is ['domain', ['domid', 1], ........... [2006-12-10 07:24:44 xend.XendDomainInfo 2488] DEBUG (XendDomainInfo:395) parseConfig: result is {'shadow_memory': 0,.............. [2006-12-10 07:24:44 xend.XendDomainInfo 2488] DEBUG (XendDomainInfo:1253) XendDomainInfo.construct: None [2006-12-10 07:24:44 xend.XendDomainInfo 2488] DEBUG (XendDomainInfo:1285) XendDomainInfo.initDomain: 2 1.0 [2006-12-10 07:24:44 xend 2488] INFO (image:214) configuring linux guest [2006-12-10 07:24:44 xend 2488] DEBUG (balloon:133) Balloon: 4608 KiB free; 258464 to scrub; need 262144; retries: 20. [2006-12-10 07:24:44 xend 2488] DEBUG (balloon:141) Balloon: waiting on scrubbing [2006-12-10 07:24:45 xend 2488] DEBUG (balloon:127) Balloon: 263072 KiB free; need 262144; done. [2006-12-10 07:24:45 xend 2488] INFO (image:138) buildDomain os=linux dom=2 vcpus=1 [2006-12-10 07:24:45 xend 2488] DEBUG (image:193) dom = 2 [2006-12-10 07:24:45 xend 2488] DEBUG (image:194) image = /var/lib/xen/vmlinuz.ZheCMH [2006-12-10 07:24:45 xend 2488] DEBUG (image:195) store_evtchn = 1 [2006-12-10 07:24:45 xend 2488] DEBUG (image:196) console_evtchn = 2 [2006-12-10 07:24:45 xend 2488] DEBUG (image:197) cmdline = ro root=/dev/VolGroup00/LogVol00 console=xvc0 [2006-12-10 07:24:45 xend 2488] DEBUG (image:198) ramdisk = /var/lib/xen/initrd.LC7J9l [2006-12-10 07:24:45 xend 2488] DEBUG (image:199) vcpus = 1 [2006-12-10 07:24:45 xend 2488] DEBUG (image:200) features = [2006-12-10 07:24:45 xend 2488] DEBUG (DevController:110) DevController: writing {'backend-id': '0', 'mac': '00:16:3e:55:69:53', 'handle': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/2/0'} to /local/domain/2/device/vif/0. [2006-12-10 07:24:45 xend 2488] DEBUG (DevController:112) DevController: writing {'bridge': 'xenbr0', 'domain': 'fc6_64', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/2/device/vif/0', 'mac': '00:16:3e:55:69:53', 'online': '1', 'frontend-id': '2'} to /local/domain/0/backend/vif/2/0. [2006-12-10 07:24:45 xend 2488] DEBUG (blkif:24) exception looking up device number for xvda: [Errno 2] No such file or directory: '/dev/xvda' [2006-12-10 07:24:45 xend 2488] DEBUG (DevController:110) DevController: writing {'backend-id': '0', 'virtual-device': '51712', 'device-type': 'disk', 'state': '1', 'backend': '/local/domain/0/backend/tap/2/51712'} to /local/domain/2/device/vbd/51712. [2006-12-10 07:24:45 xend 2488] DEBUG (DevController:112) DevController: writing {'domain': 'fc6_64', 'frontend': '/local/domain/2/device/vbd/51712', 'dev': 'xvda', 'state': '1', 'params': 'aio:/data/fc6_64.img', 'mode': 'w', 'online': '1', 'frontend-id': '2', 'type': 'tap'} to /local/domain/0/backend/tap/2/51712. [2006-12-10 07:24:45 xend.XendDomainInfo 2488] DEBUG (XendDomainInfo:712) Storing VM details: {'shadow_memory': '0', 'uuid': ............ [2006-12-10 07:24:45 xend.XendDomainInfo 2488] DEBUG (XendDomainInfo:747) Storing domain details: {'console/ring-ref': '230727', .......... [2006-12-10 07:24:45 xend.XendDomainInfo 2488] DEBUG (XendDomainInfo:933) XendDomainInfo.handleShutdownWatch [2006-12-10 07:24:59 xend.XendDomainInfo 2488] WARNING (XendDomainInfo:875) Domain has crashed: name=fc6_64 id=2. [2006-12-10 07:24:59 xend.XendDomainInfo 2488] ERROR (XendDomainInfo:1661) VM fc6_64 restarting too fast (15.225058 seconds since the last restart). Refusing to restart to avoid loops. [2006-12-10 07:24:59 xend.XendDomainInfo 2488] DEBUG (XendDomainInfo:1449) XendDomainInfo.destroy: domid=2 [2006-12-10 07:24:59 xend.XendDomainInfo 2488] DEBUG (XendDomainInfo:1457) XendDomainInfo.destroyDomain(2)
_________________________________________________________________ Advertisement: Fresh jobs daily. Stop waiting for the newspaper. Search now! www.seek.com.au http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau&am...
On Sun, 10 Dec 2006 07:34:40 +1000 ". ." porjo38@hotmail.com wrote:
I'm new to Xen. I've been trying unsucessfully to setup an x86_64 guest on my x86_64 Dom0 (both running Fedora Core 6). The dom0 system is a fresh install of FC6 with latest updates applied.
My exact situation as well, but installing the guest by blindly following the instructions in the FC6 Xen page worked OK for me, when it did the initial reboot, I just ran an xm create to get it running again, and the initial firstboot stuff came up and worked OK.
I've been working on my Xen Frequently Confusing Issues web page documenting stuff I learn (and have yet to learn) as I go along:
http://home.att.net/~Tom.Horsley/xen-fci.html
Don't know if anything in there will help...