two mouse cursors and no network after power cutoff

[arash.abghari]

Hi every body,

We have experienced a power cut off on our proxmox machine. At the time there were two win xp VM were on. After that these two win xp VM machines are displaying two mouse cursors and worse there is no network connectivity from inside these VMs. The network status from inside the VMs show as if the network is connected but ping gets timeout. Other win xp and win 7 machines are working fine which they were off at the power cut off. Here is the output of pveversion -v:

pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-55+ovzfix-2
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.32-6-pve: 2.6.32-55+ovzfix-1
pve-kernel-2.6.32-7-pve: 2.6.32-55+ovzfix-2
qemu-server: 1.1-32
pve-firmware: 1.0-15
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-2
ksm-control-daemon: 1.0-6

and here is the config file of one the VMs:

name: Win-Xp(SP3)
bootdisk: ide0
vlan1: rtl8139=42:AE:8A:EE:1D:83
ostype: wxp
ide0: local:140/vm-140-disk-1.raw
memory: 1024
sockets: 1
onboot: 0
cores: 1
boot: cad
freeze: 0
cpuunits: 1000
vga: std
acpi: 1
kvm: 1
ide1: local:140/vm-140-disk-2.raw
ide2: none,media=cdrom

I appeciate any help.

Thanks,

Arash

 

[dietmar]

What kind of hardware do you use for the local disk?

 

[arash.abghari]

Here is the output of lshw if that what you are looking for:
*-storage

description: SATA controller
product: SB700/SB800 SATA Controller [AHCI mode]
vendor: ATI Technologies Inc
physical id: 11
bus info: pci@0000:00:11.0
logical name: scsi1
version: 40
width: 32 bits
clock: 66MHz
capabilities: storage msi ahci_1.0 bus_master cap_list emulated
configuration: driver=ahci latency=32 module=ahci
*-disk
​

description: ATA Disk
product: WDC WD2001FASS-0
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@1:0.0.0
logical name: /dev/sda
version: 05.0
serial: WD-WMAUR0584394
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5
*-volume:0
​

description: EXT3 volume
vendor: Linux
physical id: 1
bus info: scsi@1:0.0.0,1
logical name: /dev/sda1
logical name: /boot
version: 1.0
serial: acce7a2a-53d9-429c-81d6-6e06e23ac652
size: 512MiB
capacity: 512MiB
capabilities: primary bootable journaled extended_attributes large_files huge_files recover ext3 ext2 initialized
configuration: created=2010-11-05 13:11:22 filesystem=ext3 modified=2012-03-01 11:21:19 mount.fstype=ext3 mount.options=rw,relatime,errors=continue,barrier=0,data=ordered mounted=2012-02-29 15:28:57 state=mounted​

*-volume:1
​

description: Linux LVM Physical Volume partition
physical id: 2
bus info: scsi@1:0.0.0,2
logical name: /dev/sda2
serial: yz3ZM3-QQq6-hsf7-YsVl-PhWN-ctKU-g6pqqy
size: 1862GiB
capacity: 1862GiB
capabilities: primary multi lvm2
​

 

[dietmar]

Looks like you use a single HD drive with 64MB cache? You do not have a HW-RAID controller with BBU, so it is likely that you lost the content of the HD cache, which can result in serious damage of your vm images. One way to repair is to restore those VMs from backup.