Re: [Xen-users] My first Windows VM

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

On Thu, 2015-03-12 at 06:20 -0700, Steffan A. Cline wrote:
> Not having much luck. I've been able to create any Linux guest at any
> time but windows is being difficult. Typically I use Cloudmin to
> manage this for me but am getting more into the manual config since
> Windows doesn't seem to play nice. I've looked at numerous examples
> and tried them all yet nothing seems to work. I can't get it to launch
> at all. Here are the relevant configs. Hopefully someone will know
> what the errors are.
> 
> 
> [root@h1 xen]# cat win-2008-server.cfg
> memory = 8192
> maxmem = 12000

Unless you have PV drivers already installed in your HVM guest then you
cannot start with memory<maxmem, since a balloon driver is needed to
pickup the slack. I'm not sure what the failure would look like though.

When you say can't get it to launch, does xm create return an error or
does it do nothing? Or can you connect to VNC and it's silent or is
there some other behaviour etc?

> 
> I can't find a clear definition of the errors though.
> 
> 
> domid: 8
> Using file /dev/vg_h2/win-2008-server_img in read-write mode
> Using file /images/en_windows_server_2012_r2_vl_x64_dvd.iso in
> read-only mode
> Watching /local/domain/0/device-model/8/logdirty/cmd
> Watching /local/domain/0/device-model/8/command
> Watching /local/domain/8/cpu
> qemu_map_cache_init nr_buckets = 10000 size 4194304
> shared page at pfn feffd
> buffered io page at pfn feffb
> Guest uuid = 43996c35-2f9f-52f2-6d66-d8ec0eec3a46
> Time offset set 0
> char device redirected to /dev/pts/10
> xen be: console-0: xen be: console-0: initialise() failed
> initialise() failed
> 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/8/xen_extended_power_mgmt): read
> error
> medium change watch on `hdc' (index:
> 1): /images/en_windows_server_2012_r2_vl_x64_dvd.iso
> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
> Log-dirty: no command yet.
> xen be: console-0: xen be: console-0: initialise() failed
> initialise() failed
> vcpu-set: watch node error.
> [xenstore_process_vcpu_set_event]: /local/domain/8/cpu has no CPU!
> xen be: console-0: xen be: console-0: initialise() failed
> initialise() failed
> xs_read(/local/domain/8/log-throttling): read error
> qemu: ignoring not-understood drive `/local/domain/8/log-throttling'
> medium change watch on `/local/domain/8/log-throttling' - unknown
> device, ignored
> xen be: console-0: xen be: console-0: initialise() failed
> initialise() failed
> 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.
> ACPI:debug: write addr=0xb044, val=0x0.
> ACPI:debug: write addr=0xb045, val=0x89.

I suppose this is the qemu log?

It's been a long time since I looked at at a Xen 4.2 system or an
xm/xend one, but I know qemu can be quite "chatty", so I'm not sure if
any of this indicates a problem or not.

> â
> Followed by tons of ACPI errors.

i.e. more of the ACPI:debug stuff or by actual errors?

Is there any other interesting logging under /var/log/xen i.e. in the
xend log?

Ian.


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users