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

[Xen-users] Xen 3.3 Windows xp guest insufficient resources



Hello all,

Been using Xen a while, previously with Netbsd and few weeks ago changed dom0 to Gentoo linux. Change wen't very nice, but now I'm facing strange out of resources problem in Windows XP HVM guests. At first there was no issues but when we added second windows guest users started to complain that they cannot access network drivers and cannot unzip large zips ( the operation stucks at some point). After that we started to notice same kind of behaviour in our first (previously fully working windows guest). I have used GPL PV drivers 0.9.9 (tried also with 0.9.12.pre4 and yesterday tried without PV drivers (without /gplpv switch). I have tried pretty much everything that comes to my mind without no luck, so if anybody have had same kind of sympthons, please, please let me know (and hopefully also with answer how you managed to solve this problem).

Windows guests have 700 MB of ram reserved (tried also with 1GB). Both are using same base installation of windows from 10 Gb image file (C:\). First uses data disk partition from external Sata disk (My Book Studio II 2TB), second is using 100 GB file backed image..

Exact windows error info is:

"ERROR: insufficient system resrouces exits to complete the requested service".

And Last night the hole machine had crashed (ie not able to do anything but turn off from powerswitch, i have now serial console attached..)

Some details on xen / machine:

DELL 755, Core(TM)2 Quad CPU Q6600 @ 2.40GHz GenuineIntel GNU/Linux

release                : 2.6.21-xen
version                : #4 SMP Tue Nov 18 16:49:39 EET 2008
machine                : x86_64
nr_cpus                : 4
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 1
cpu_mhz                : 2394
hw_caps : bfebfbff:20100800:00000000:00000140:0000e3bd:00000000:00000001:00000000
virt_caps              : hvm
total_memory           : 3965
free_memory            : 11
node_to_cpu            : node0:0-3
node_to_memory         : node0:11
xen_major              : 3
xen_minor              : 3
xen_extra              : .0
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : unavailable
cc_compiler            : gcc version 4.1.2 (Gentoo 4.1.2 p1.1)
cc_compile_by          : root
cc_compile_domain      : (none)
cc_compile_date        : Tue Oct 28 16:02:43 Local time
xend_config_format     : 4


Second guest config:

kernel = "/usr/lib/xen/boot/hvmloader"
builder="hvm"
memory = 1000
name = "windows2
vcpus=2
# device model to use: only qemu-dm available for now
device_model = '/usr/lib64/xen/bin/qemu-dm'

## network from dhcp
vif = [ 'mac=00:16:3e:01:00:20' ]
dhcp = "dhcp"

#DISKS
disk = [ 'file:/mnt/external_1/xenstorage/windows2/windows_10gb.disk,ioemu:hda,w', \
'file:/mnt/external_2/xenstorage/windows2/windows.100gb.disk,ioemu:hdb,w', \
'file:/mnt/external_1/xenstorage/windows2/windows_5gb_logs.disk,ioemu:hdc,w' ]

# boot device: a = floppy, c= hard drive, d= cdrom (with the disk entry before)
boot="c"
sdl=0
vnc = 1
vncdisplay =11

#Xen emulates a PS/2 mouse, but the pointer in the guest has difficulties
# tracking the absolute position. Xen can emulate a USB tablet in addition
# to the mouse which will report the absolute position of the pointer,
# and make the mouse much easier to use.
#
usb=1
usbdevice='tablet'

qemu log from second domain:

domid: 6
qemu: the number of cpus is 2
config qemu network with xen bridge for  tap6.0 xenbr0
Watching /local/domain/0/device-model/6/logdirty/next-active
Watching /local/domain/0/device-model/6/command
qemu_map_cache_init nr_buckets = 10000 size 3145728
shared page at pfn 3e7fe
buffered io page at pfn 3e7fc
Time offset set 0
Register xen platform.
Done register platform.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
gpe_sts_write: addr=0x1f68, val=0x0.
gpe_sts_write: addr=0x1f69, val=0x0.
gpe_sts_write: addr=0x1f6a, val=0x0.
gpe_sts_write: addr=0x1f6b, val=0x0.
gpe_en_write: addr=0x1f6c, val=0x0.
gpe_en_write: addr=0x1f6d, val=0x0.
gpe_en_write: addr=0x1f6e, val=0x0.
gpe_en_write: addr=0x1f6f, val=0x0.
gpe_en_write: addr=0x1f6c, val=0x0.
gpe_en_write: addr=0x1f6d, val=0x0.
gpe_en_write: addr=0x1f6e, val=0x0.
gpe_en_write: addr=0x1f6f, val=0x0.
gpe_sts_write: addr=0x1f68, val=0x0.
gpe_sts_write: addr=0x1f69, val=0x0.
gpe_sts_write: addr=0x1f6a, val=0x0.
gpe_sts_write: addr=0x1f6b, val=0x0.
gpe_en_write: addr=0x1f6c, val=0x8.
gpe_en_write: addr=0x1f6d, val=0x0.
gpe_en_write: addr=0x1f6e, val=0x0.
gpe_en_write: addr=0x1f6f, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
Time offset set 1, added offset 1
Time offset set 7201, added offset 7200
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
gpe_en_write: addr=0x1f6c, val=0x8.
gpe_en_write: addr=0x1f6d, val=0x0.
gpe_en_write: addr=0x1f6e, val=0x0.
gpe_en_write: addr=0x1f6f, val=0x0.
gpe_en_write: addr=0x1f6c, val=0x8.
gpe_en_write: addr=0x1f6d, val=0x0.
gpe_en_write: addr=0x1f6e, val=0x0.
gpe_en_write: addr=0x1f6f, val=0x0.
reset requested in cpu_handle_ioreq.
Issued domain 6 reboot
track_dirty_vram(f0000000, 240) failed (-1, 3)



_______________________________________________
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®.