[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Fully virtualized guest boot problem



Petersson, Mats wrote:
-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of anant
Sent: 12 February 2007 13:02
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Fully virtualized guest boot problem


I got the similar problem with FC6 and Xen 3.0.3.Finally i had to change the disto which worked quite well for me. So try your best to work out, if it doesnt then i would suggest you to move on with OpenSuSE10.2 which is really
stable in getting windows or linux based guest OS on top of Xen

However, I doubt that the distribution is really the problem here, it's
most likely the fact that FC and OpenSuSE are using slightly different
versions of Xen, and thus works differently.
I'm pretty sure the actual base-distribution is (pretty much) irrelevant
- there are some obscure cases, but in general it's not an issue.
I don't see anything wrong in the configuration or the log messages. Are
you running Intel or AMD processor?


Hi Mats,
I am running on an AMD64 processor. Could that be the reason for this problem ? I haven't tried it on an Intel machine.
So, similar to Anant, do you also suggest to try OpenSuse instead FC6 ?

Thanks,
Abhishek.

--
Mats
All the Best
Anant

Abhishek Gaurav wrote:
Hi,

I am new to Xen and I am trying to start a fully
virtualized machine on
an AMD64 base system running FC6. I have an FC2 image for
booting the
guests. I get the following problem when the VM starts booting. The status of the VM as seen from xm list is 'running' forever.

(XEN) (GUEST: 44) HVM Loader
(XEN) (GUEST: 44) Detected Xen v3.0.3-rc3-1.2798.f
(XEN) (GUEST: 44) Writing SMBIOS tables ...
(XEN) (GUEST: 44) Loading ROMBIOS ...
(XEN) (GUEST: 44) Loading Cirrus VGABIOS ...
(XEN) (GUEST: 44) SVM go ...
(XEN) (GUEST: 44) rombios.c,v 1.138 2005/05/07 15:55:26
vruppert Exp $
(XEN) (GUEST: 44) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50 vruppert Exp $ (XEN) (GUEST: 44) HVMAssist BIOS, 1 cpu,
$Revision: 1.138
$ $Date: 2005/05/07 15:55:26 $

(XEN) (GUEST: 44)
(XEN) (GUEST: 44) ata0-0: PCHS=12292/16/32 translation=none
LCHS=1024/16/32
(XEN) (GUEST: 44) ata0 master: QEMU HARDDISK ATA-7
Hard-Disk (3073 MBytes)
(XEN) (GUEST: 44) ata0  slave: Unknown device
(XEN) (GUEST: 44)
(XEN) (GUEST: 44) Booting from Hard Disk...
(XEN) (GUEST: 44) int13_harddisk: function 41, unmapped
device for ELDL=81
(XEN) (GUEST: 44) int13_harddisk: function 08, unmapped
device for ELDL=81
(XEN) (GUEST: 44) *** int 15h function AX=00C0, BX=0000 not
yet supported!
My config file looks like this:
name = "grc59"
builder = "hvm"
memory = "1024"
disk = [ 'file:/root/guestos/fc2_86_64/hd.img,ioemu:hda,w', ]
vif = [ 'type=ioemu, mac=00:16:3e:1b:ce:29, bridge=xenbr0', ]
uuid = "76e3de0e-8e6f-656c-4e06-62752c2b6641"
device_model = "/usr/lib64/xen/bin/qemu-dm"
kernel = "/usr/lib/xen/boot/hvmloader"
nographic=1
apic=1
acpi=1
pae=1
boot='c'

vcpus=1
serial = "pty" # enable serial console
on_reboot   = 'restart'
on_crash    = 'restart'

Can anybody please let me know what is that I am doing wrong?

Thanks,
Abhishek.


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


--
View this message in context: http://www.nabble.com/Fully-virtualized-guest-boot-problem-tf3
210602.html#a8923765
Sent from the Xen - User mailing list archive at Nabble.com.


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






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


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.