On Sun, Mar 14, 2010 at 10:12 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> On Sun, Mar 14, 2010 at 09:52:02PM +0800, Rommel M. Martinez wrote:
>> Hi! I want to run a Xen Dom0 (and DomUs) inside VMware Workstation. I
>> used Debian for this and had the Xen-related packages installed with
>> it. When I booted the VM using the Xen kernel, I get the following
>> message from VMware Workstation:
>>
>> A virtual CPU has entered the shutdown state. This would have caused a
>> physical machine to restart. This can be caused by an incorrect
>> configuration of the virtual machine, a bug in the operating system or
>> a problem in the VMware Workstation software. Press OK to restart the
>> virtual machine or Cancel to power off the virtual machine.
>>
>> 1- What could be causing this?
>
> If your grub configuration is correct, it could be Xen or dom0 kernel
> is crashing.
The entire grub configuration:
----------------------------------------------------------------------
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-legacy-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not change this entry to 'saved' or your
# array will desync and will not let you boot your system.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 5
# Pretty colours
color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#
#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below
## DO NOT UNCOMMENT THEM, Just edit them to your needs
## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=/dev/sda1 ro
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)
## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true
## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false
## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet
## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false
## Xen hypervisor options to use with the default Xen boot option
# xenhopt=
## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(single-user) single
# altoptions=(single-user mode) single
## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all
## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true
## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false
## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false
## ## End Default Options ##
title Xen 3.2-1-i386 / Debian GNU/Linux, kernel 2.6.26-2-xen-686
root (hd0,0)
kernel /boot/xen-3.2-1-i386.gz
module /boot/vmlinuz-2.6.26-2-xen-686 root=/dev/sda1 ro console=tty0
module /boot/initrd.img-2.6.26-2-xen-686
title Debian GNU/Linux, kernel 2.6.26-2-xen-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.26-2-xen-686 root=/dev/sda1 ro quiet
initrd /boot/initrd.img-2.6.26-2-xen-686
title Debian GNU/Linux, kernel 2.6.26-2-xen-686 (single-user mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.26-2-xen-686 root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.26-2-xen-686
title Debian GNU/Linux, kernel 2.6.26-2-openvz-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.26-2-openvz-686 root=/dev/sda1 ro quiet
initrd /boot/initrd.img-2.6.26-2-openvz-686
title Debian GNU/Linux, kernel 2.6.26-2-openvz-686 (single-user mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.26-2-openvz-686 root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.26-2-openvz-686
title Debian GNU/Linux, kernel 2.6.26-2-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.26-2-686 root=/dev/sda1 ro quiet
initrd /boot/initrd.img-2.6.26-2-686
title Debian GNU/Linux, kernel 2.6.26-2-686 (single-user mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.26-2-686 root=/dev/sda1 ro single
initrd /boot/initrd.img-2.6.26-2-686
### END DEBIAN AUTOMAGIC KERNELS LIST
----------------------------------------------------------------------
>
>> 2- Are there things that I need to tweak to make things work?
>
> You shouldn't need anything special.. you could try pci=nomsi for the dom0
> kernel,
> maybe that helps.
>
>> 3- I currently have limited access to extra physical machines that's
>> why I'm using a solution like VMware Workstation
>> 4- The VM boots well using the vanilla kernel and other kernels (e.g.,
>> OpenVZ).
>> 5- Does this have anything to do with Xen's compatibility with VMware
>> Workstation?
>>
>
> Difficult to say which one is to blame.
> Would be good to see the actual console output to see what's wrong!
The boot sequence:
http://www.youtube.com/watch?v=1u33eHlzIPY
>
> -- Pasi
>
>
--
Rommel M. Martinez
http://www.bespin.org/~ebzzry
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home