[Xen-users] No vmx flag, and no vnc

["David Henningsson" <launchpad.web@xxxxxxxxxxxxxx>]

Hi,

I'm stuck in my attempts to get xen up and running.

I selected Debian Lenny as base as I'm a bit more familiar with
Debian/Ubuntu than with the other Linux distros. Uname -r =
2.6.26-2-xen-amd64. Xen version should be 3.2-1. Guest is Windows Server
2008 R2.

My first problem is that /proc/cpuinfo does not show the vmx flag,
although I know that the processor (Intel E5504) has VT-X support (and
virtualization is enabled in BIOS).

Anyway, I tried to set up a guest anyway. Running the command "xm create"
seems to return successfully, but I can't connect to the guest via VNC. No
VNC-like port is opened (given "netstat -a"). No warnings (only
debug/info) in xend.log while starting the guest domain, although while
starting domain 0 the following warnings occur:

[2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: VBD.set_device
not found
[2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: VBD.set_type
not found
[2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call:
session.get_all_records not found
[2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call:
event.get_record not found
[2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: event.get_all
not found
[2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call:
VM.get_auto_power_on not found
[2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call:
VM.set_auto_power_on not found
[2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: VIF.get_network
not found
[2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: VIF.set_device
not found
[2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: VIF.set_MAC not
found
[2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: VIF.set_MTU not
found
[2009-12-03 09:37:55 2944] WARNING (XendAPI:678) API call: debug.get_all
not found

This one is also interesting:

[2009-12-03 09:37:54 2944] INFO (XendNetwork:114) Not recreating missing
unmanaged network xenbr0

...I thought xenbr0 was no more with xen 3.2, so the question is what the
cause of this message is.

Thankful for help!

// David


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