Hi friends ;
Host : windows 7
Guest : Linux 5.5
I am using virtual machine version 9 (brigged n/w)
I want to connect my vmware machine from putty without LAN connection.
I strongly believe it is possible. I dont know how can i do that ?
Always i am facing 'network unreachable'
Please help me ..
I noticed on my windows server (VM) that one of the disk drives was getting low. This was showing 22gb free from the OS. (Windows 2008 R2) It is functioning as the file storage and print server. So, I extended the SAN LUN by 100gb, extended the vCenter Datastore by the same amount and now it's showing in vCenter that I have an extra 100gb of space. On the OS, it's still showing 22gb free. I know that if I go into the VM and edit the properties of the disk drive, and add up to 100gb of space, then on the OS, in this case Windows I can go into disk management and extend the volume I will see the additional space. My question, Do I need to do this if my Datastore is thin provisioned? Will it not grow if needed? or am I getting the OS and VMware confused as to how it functions?
I have a VM which is running under VM Server 2.0 on a W2003 machine perfectly for months.
Now, I have a new machine running OpenSuse11, also with VM Server 2.
I copied all the files in the original Windows-machine directory to the linux-machine and added this machine to the inventory saying that this machines wasn't new, but copied.
The final try to start ended with an error message, saying thta the virtual harddisk is not valid.
Here comes the text from vmware.log:
Dec 12 18:55:44.380: vmx| DISK: OPEN scsi0:0 '/NAS_alt/VMWare/Windows Server 2003 Enterprise Edition-000001.vmdk' independent-persistent R[]
Dec 12 18:55:44.426: vmx| DISKLIB-DSCPTR: Opened : "Windows Server 2003 Enterprise Edition-000001.vmdk" (0x2a)
Dec 12 18:55:44.426: vmx| DISKLIB-LINK : Opened '/NAS_alt/VMWare/Windows Server 2003 Enterprise Edition-000001.vmdk' (0x2a): monolithicSparse, 52428800 sectors / 25 GB.
Dec 12 18:55:44.426: vmx| DISKLIB-LINK : "/NAS_alt/VMWare/Windows Server 2003 Enterprise Edition.vmdk" : failed to open (The system cannot find the file specified).
Dec 12 18:55:44.426: vmx| DISKLIB-CHAIN :"/NAS_alt/VMWare/Windows Server 2003 Enterprise Edition-000001.vmdk": Failed to open parent "/NAS_alt/VMWare/Windows Server 2003 Enterprise Edition.vmdk": The system cannot find the file specified.
Dec 12 18:55:44.426: vmx| DISKLIB-CHAIN : "/NAS_alt/VMWare/Windows Server 2003 Enterprise Edition.vmdk" : failed to open (The parent of this virtual disk could not be opened).
Dec 12 18:55:44.468: vmx| DISKLIB-LIB : Failed to open '/NAS_alt/VMWare/Windows Server 2003 Enterprise Edition-000001.vmdk' with flags 0x2a (The parent of this virtual disk could not be opened).
Dec 12 18:55:44.515: vmx| DISKLIB-DSCPTR: Opened : "Windows Server 2003 Enterprise Edition-000001.vmdk" (0x28)
Dec 12 18:55:44.515: vmx| DISKLIB-LINK : Opened '/NAS_alt/VMWare/Windows Server 2003 Enterprise Edition-000001.vmdk' (0x28): monolithicSparse, 52428800 sectors / 25 GB.
Dec 12 18:55:44.515: vmx| DISKLIB-LIB : Opened "/NAS_alt/VMWare/Windows Server 2003 Enterprise Edition-000001.vmdk" (flags 0x28).
Dec 12 18:55:44.515: vmx| DISKLIB-LINK : "Windows Server 2003 Enterprise Edition.vmdk" : failed to open (The system cannot find the file specified).
Dec 12 18:55:44.515: vmx| DISKLIB-CHAIN : "Windows Server 2003 Enterprise Edition.vmdk" : failed to open (The system cannot find the file specified).
Dec 12 18:55:44.515: vmx| DISKLIB-LIB : Failed to open 'Windows Server 2003 Enterprise Edition.vmdk' with flags 0x2a (The system cannot find the file specified).
Dec 12 18:55:44.515: vmx| DISK: Cannot open disk 'Windows Server 2003 Enterprise Edition.vmdk' : The system cannot find the file specified.
Dec 12 18:55:44.558: vmx| Msg_Post: Error
Dec 12 18:55:44.558: vmx| http://msg.disk.fileNotFound VMware Server cannot find the virtual disk "Windows Server 2003 Enterprise Edition.vmdk". Please verify the path is valid and try again.
Dec 12 18:55:44.558: vmx| http://msg.disk.noBackEnd Cannot open the disk '/NAS_alt/VMWare/Windows Server 2003 Enterprise Edition-000001.vmdk' or one of the snapshot disks it depends on.
Dec 12 18:55:44.558: vmx| http://msg.disk.configureDiskError Reason: The system cannot find the file specified.----
Dec 12 18:55:44.576: vmx| Module DiskEarly power on failed.
Dec 12 18:55:44.576: vmx| VMX_PowerOn: ModuleTable_PowerOn = 0
Dec 12 18:55:44.576: vmx| WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0
Dec 12 18:55:44.582: vmx| VMMon_UnlockPage: failed addr = 7F82F001A000, return = -1, errno = 22
Dec 12 18:55:44.583: vmx| Transitioned vmx/execState/val to poweredOff
Dec 12 18:55:44.654: vmx| vmdbPipe_Streams Couldn't read: OVL_STATUS_EOF
Dec 12 18:55:44.654: vmx| VMX idle exit
Dec 12 18:55:44.655: vmx| Flushing VMX VMDB connections
Dec 12 18:55:44.655: vmx| IPC_exit: disconnecting all threads
Dec 12 18:55:44.655: vmx| VMX exit (0).
Dec 12 18:55:44.655: vmx| AIOMGR-S : stat o=2 r=6 w=0 i=0 br=25600 bw=0
Some messages say that the files cannot be found, but they are there on the Linux-machine.
Because I asked for this behaviour aonce before, i checked the properties for the whole directory, which is 'Can modify & view' for all files, ownwer is root.
Here is the message text from the startip command:
VMware Server cannot find the virtual disk "Windows Server 2003 Enterprise Edition.vmdk". Please verify the path is valid and try again.
Cannot open the disk '/NAS_alt/VMWare/Windows Server 2003 Enterprise Edition-000001.vmdk' or one of the snapshot disks it depends on.
Reason: The system cannot find the file specified.
What can I do ?
Greetings from cold Germany, Nico
Hi there, I'm in a bit of a pickle...... I have a Domain Controller running server 2003SP2 virtualised on vmware server. its a site i have recently taken over support for.... the phsical server is a dell pe2900 called vmhost running three virtual servers: 1. dellserver - DC/DNS/GC ETC 2. simsserver - Database server for personnel etc 3. exchange server - email server the network is only small, and have recently purchased new laptops (win7) and as the DC is only on 2003 i thought i would add the physical server(server2008R2)64bit as a secondary domain controller so i could configure and integrate the new laptops into the domain...... after restarting the physical, after performing a successful dcpromo....... The server started up fine, with all the DC structure, but when trying to comunicate with the main DC it doesnt seem to be running. Also when clicking the VMWareServer home page icon/shortcut on the desktop to opens internet explorer but then fails to load the login box here: https://vmhost:8333/ui/ just doesnt display and cant connect. so i looked at the services and two VMWARE services refuse to start: 1. VMWare authorisation service 2. VMware host agent when you try to start these - they error out and say check event viewer. basically comes down to the fact that the user it is trying to use to access the vmware software is not available - because the DC is down....... on Dellserver So stuck in a vicsous cycle of 'cannot start vmware servers because the services wont start, to let me in to the webinterface, because the user account is not available......... any ideas i'm in the process of backing up the virtual machine folders to another machine on the network - install vmware server on this new machine to try and get the virtual machines working again. once the DC server is started and running, i should then be able to access vmware server web interface on the main physical server. Unless you have any ideas of how to make the services run using a different user account, to get them started !?
Hi!
I am using vmware since about one year on my quite slow machine - worked great for small systems.
Via Nehemiah 1GHz, 1GB RAM, Debian Etch with selfcompiled kernel 2.6.26.5.
vmware server 1.0.4 run great on 2.6.24.X (I think), later the moduls didn't compile altough actual vmware-any-any-patches.
today I upgrade to vmware server 2.0 and loved it, because it compiled without problems (except vsock, but I think I dont need it) and without any patches. great.
but, my machines are not working. I have no idea why this happens - here is a logfile, perhaps anybody is able to help me.
The machine tries to start, modules are loaded correctly without errors, no special logs in dmesg is reported ...
As I have (as small homeuser) no support I am not venturing sending the file anywhere which was created with vm-support.
Thanks.
>>>Cyber
Hi there,
Anybody knows what this error message means:
"msg.vmxaiomgr.retrycontabort.rudeunplug:Operation
on file "
.\PhysicalDrive1" failed.
If the file resides on a remote file system, please make sure your
network connection and the server where this disk resides are
functioning properly. If the file resides on removable media, reattach
the media.
Choose Retry to attempt the operation again.
Choose Abort to terminate this session.
Choose Continue to forward the error to the guest operating system."
I guess it wants to say that there are problems with the disk attached to the guest. It happened before, I checked the disk for errors but none were found.I restarted the guest and after a couple of tries it was back on. Now it happened again.
Hi,
Im currently hosted at poundhost where bridging the connection is blocked. ive tried several steps to try to get an IP address on my Virtual Machine
the ethernet type on VMware im using is host only
My Default Gateway on my Host OS is 94.76.241.65.
Ive set my VMNet01 ipaddress to xxx.xxx.69.211 and the Linux to xxx.xxx.69.212 and i set the gateway to xxx.xxx.69.211
Ive enabled IPRouting in regedit for windows 2003
below are a list of my allowed IP's
94.76.241.79-added to my hosts main ethernet
xxx.xxx.69.208-added to my hosts main ethernet
xxx.xxx.69.209-added to my hosts main ethernet
xxx.xxx.69.210-added to my hosts main ethernet
xxx.xxx.69.211-added to my hosts VMNet01
xxx.xxx.69.212-added to my guest os
xxx.xxx.69.213-unused
xxx.xxx.69.214-unused
xxx.xxx.69.215-unused
xxx.xxx.69.216-unused
xxx.xxx.69.217-unused
xxx.xxx.69.218-unused
xxx.xxx.69.219-unused
xxx.xxx.69.220-unused
xxx.xxx.69.221-unused
xxx.xxx.69.222-unused
xxx.xxx.69.223-unused
The datacentre has had a look and cant get it working also.
if anyone could give any tips or help me i would be more than greatful.
It took a while, but I found the solution for the blank web page on vmware server 2. If I viewed the source, I could see that content was being delivered, however the page would appear blank.
I also saw a variety of errors at the command line, including "599 vmware-authd PANIC: getpeername failed: Socket operation on non-socket", "terminate called after throwing an instance of 'VmdbError'" and " Failed to connect: 514 Error connecting to hostd-vmdb service instance."
When this happens, here is how I fix it:
tcp 0 0 0.0.0.0:902 0.0.0.0:* LISTEN 18939/vmware-authdl
tcp 0 0 0.0.0.0:902 0.0.0.0:* LISTEN 15935/vmware-authdl
Hello,
I can't install w2k8 on VMware Server 2.0.2, because I still received error :
"The installation was canceled
Any changes that were made to your computer during installation process will not be saved"
and next window:
"Windows could not create a partition on disk 0. The error occurred while applying the unattend answer file's setting. Error code: 0x80004005"
I try other version of w2k8 in this cd, but is the same issue.
Could you help me
Radek
Problem: Connectivity between the host and the VM randomly drops out.
Observed: The problem only seems to occur when the host network cards are teamed and the host OS is Windows 2008 R2 (x64). This problem is happening on 14 of our Dell 2900's and 6 of our IBM 3650 M3's.
It does not occur when the host is running Windows 2003 R2 (x32) with teaming.
Here is a screenshot (http://imageshack.us/f/30/unledyit.png/) showing the virtual network editor settings as well as a ping from the host to the VM (you'll notice that 1 network card is disconnected and you may think that is the problem but it happens even when both network cards are plugged in).
btw I'm using VMWare Server 2.0
Hi,
I am using "vmware-vdiskmanager" to convert a virtual disk from growable to preallocated. I have had enough of the defrags and poor disk i/o.
To do this I have copied the vmwaredisk.vmdk file of 8.5 GB to D:\Dump, because spaces in (sub)Folder and File names are causing other problems (the D partition has 189 GB FREE space) and want the new file vmwaredisk_2.vmdk to be created in the same folder by putting in Command Prompt:
C:\Program Files (x86)\VMware\VMware Workstation>vmware-vdiskmanager -r D:\Dump\vmwaredisk.vmdk -t 2 D:\Dump\vmwaredisk_2.vmdk
Now I keep getting the same error message below (and I know I should have more than enough FREE space). Why is it telling me that the disk is full?
Creating disk 'D:\Dump\VMwareDisk_2.vmdk'
Failed to convert disk: An error occurred while writing a file; the disk is full
. Data has not been saved. Free some space and try again (0xd00000008).
Please your help because I really don't know what to do anymore!
Many thanks in advance,
Erik
i'm in the process of spec'ing new hardare for a virtualization server for home. decied on ESXi for the OS.
some graphics intensive games will be on windows guests and some on linux guests.
as for a graphics card, when my notebooks connect to any of the guests will a really good graphics card be able to be used by the guests and thus display well via the the remote access?
G'day,
I'm running VMServer 2.0.1 on Ubuntu 9.0.4 (Jaunty) hosting CentOS 4.7 guest VMs.
I am continually seeing the following message when powering on a guest VM:
The network bridge on device vmnet0 is temporarily down because the bridged Ethernet interface is down. The virtual machine may not be able to communicate with the host or with other machines on your network.
The work-around I've discovered is to restart the vmware services, i.e.
$ sudo /etc/init.d/vmware stop
Stopping VMware autostart virtual machines:
Virtual machines done
Stopping VMware management services:
VMware Virtual Infrastructure Web Access
VMware Server Host Agent done
Stopping VMware services:
VMware Authentication Daemon done
Virtual machine communication interface done
Virtual machine monitor done
Bridged networking on /dev/vmnet0 done
Host network detection done
DHCP server on /dev/vmnet1 done
Host-only networking on /dev/vmnet1 done
DHCP server on /dev/vmnet8 done
NAT service on /dev/vmnet8 done
Host-only networking on /dev/vmnet8 done
Virtual ethernet done
$ sudo /etc/init.d/vmware start
Starting VMware services:
Virtual machine monitor done
Virtual machine communication interface done
Virtual ethernet done
Bridged networking on /dev/vmnet0 done
Host-only networking on /dev/vmnet1 (background) done
DHCP server on /dev/vmnet1 done
Host-only networking on /dev/vmnet8 (background) done
DHCP server on /dev/vmnet8 done
NAT service on /dev/vmnet8 done
VMware Server Authentication Daemon (background) done
Shared Memory Available done
Starting VMware management services:
VMware Server Host Agent (background) done
VMware Virtual Infrastructure Web Access
Starting VMware autostart virtual machines:
Virtual machines done
Output from ifconfig and ps -ef |grep vmnet is given below.
Why isn't vmnet0 available after booting, and how can I make it so?
Thanks,
Chris.
$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:1e:0b:35:d5:12
inet addr:10.1.1.2 Bcast:10.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::21e:bff:fe35:d512/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1354 errors:0 dropped:0 overruns:0 frame:0
TX packets:1798 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:383251 (383.2 KB) TX bytes:1126131 (1.1 MB)
Memory:f0500000-f0520000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:6225 errors:0 dropped:0 overruns:0 frame:0
TX packets:6225 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4962948 (4.9 MB) TX bytes:4962948 (4.9 MB)
pan0 Link encap:Ethernet HWaddr 96:e2:2c:be:eb:c6
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
vmnet1 Link encap:Ethernet HWaddr 00:50:56:c0:00:01
inet addr:172.16.181.1 Bcast:172.16.181.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
vmnet8 Link encap:Ethernet HWaddr 00:50:56:c0:00:08
inet addr:192.168.60.1 Bcast:192.168.60.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
$ ps -ef |grep vmnet
root 2885 1 0 11:45 ? 00:00:00 /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-0.pid -n 0 -i eth0
root 2900 1 0 11:45 ? 00:00:00 /usr/bin/vmnet-netifup -d /var/run/vmnet-netifup-vmnet1.pid /dev/vmnet1 vmnet1
root 2911 1 0 11:45 ? 00:00:00 /usr/bin/vmnet-dhcpd -cf /etc/vmware/vmnet1/dhcpd/dhcpd.conf -lf /etc/vmware/vmnet1/dhcpd/dhcpd.leases -pf /var/run/vmnet-dhcpd-vmnet1.pid vmnet1
root 2927 1 0 11:45 ? 00:00:00 /usr/bin/vmnet-netifup -d /var/run/vmnet-netifup-vmnet8.pid /dev/vmnet8 vmnet8
root 2943 1 0 11:45 ? 00:00:00 /usr/bin/vmnet-dhcpd -cf /etc/vmware/vmnet8/dhcpd/dhcpd.conf -lf /etc/vmware/vmnet8/dhcpd/dhcpd.leases -pf /var/run/vmnet-dhcpd-vmnet8.pid vmnet8
root 2948 1 0 11:45 ? 00:00:00 /usr/bin/vmnet-natd -d /var/run/vmnet-natd-8.pid -m /var/run/vmnet-natd-8.mac -c /etc/vmware/vmnet8/nat/nat.conf
Hi,
I have just installed VM Server 2.0.2 on Ubuntu 10.04 and tried to open an existing guest. However on start up I get the following error:
BIOS
.bios440 has unexpected file size 0xffffffffffffffff; not in the range
I have had a hunt around on google etc... but to no avail.
Does anyone have any ideas of where to start in resolving this issue.
Any assistance would be appreciated.
Cheers,
Tim.
I hope this is the right forum. I'll try to keep this as brief as possible. Please keep in mind that I basically know enough about vmware to be dangerous, but am by no means an expert.
I was asked by a client to set up a somewhat "failover backup". They are a small office with only one 2003 SBS. I found THIS SITE and suggested that we do that. Overall, the method worked pretty well.
However, upon booting up the VM (network adapters disconnected of course), I noticed that the three connections on the original box are named LAN, WAN, and BACKUP...all with static addresses. The three connections in the VM are called Local Area Connection, Local Area Connection 2, and Local Area Connection 3...all with default DHCP settings. When I booted down the original SBS and connected the VM, I could not connect to the network at all. When I went into the connections, renamed them, and assigned the appropriate IP settings, I got a message that a connection already exists with those settings, but is "hidden".
I discussed this with a colleague who had seen this before and told me to check HKEY_LOCAL_MACHINE\system\currentcontrolset\control\network\(the first key under that), and to remove the incorrect connections. I did this, rebooted, and now 2003 SBS is "stuck" on "preparing network connections".
I'm going to do a new p2v tonight and start over tomorrow, but I thought someone else might have more info before I start again in the morning.
Any suggestions?
Since my host is low on physical RAM I unfortunately need to allow swapping. There are two options that I can do:
I could tell the guest's OS to swap, so it will use the virtual disk to swap.
*I could tell VMware Server's memory manager to allow swapping.
The question is: What is better for performance?
I could imagine that it is better to give a VM plenty of virtual RAM, disallow guest-OS's swapping, but enable VMware memory manager's swapping? But is that really the best option?
Good morning all. I was wondering if there is a way I can connect an .iso file to my host os (win xp pro 64 in this case) so that I can save files dorectly to the .iso. Is there a way I can make the .iso be emulated as either a harddrive, or perhaps turn my 'cd rom' into a cd-rw to where i can just keep 'burning' my RW disc with new software? Thank you for your assistance!
After upgrading to firefox 3.6 I can't open up my virtual machine through the browser.
I downgraded to 3.5 and it worked.
This is the message I get:
Cannot access virtual machine console. The request timed out
The attempt to acquire a valid session ticket for * took longer than expected. If this problem persists, contact your system administrator.
Anyone know how to fix this?
I have VMWare Server running on Windows 7 64-bit host. I built a CentOS55 vm and installed zimbra mailserver. All went fine. I have my vnic set to Bridged (vmnet0). I have given my zimbra server a static IP address of 192.168.1.55. The server can reach the net/send mail out. The server cannot get mail in. Port 25 is blocked. Initially I blamed by ISP, Comcast for blocking port 25, and after a big mess have my MX pointing to dnsexit which then is configured to forward the mail to my zimbra server on port 26. On the zimbra vm, telneting to localhost port 26 works. On my local lan from my win7 and other non-virtual machines, telneting to port 26 works. From the outside world, telneting to port 26 fails, just as it did when I had it sitting on port 25. I have a linksys WRT54G wireless router. It has port forwarding set up to forward port 26 to 192.168.1.55 (my zimbra vm). The linksys router can ping the host 192.168.1.55. (It doesnt have the tools to test addl ports via a telnet connection.) For testing purposes, Ive disabled all firewalls on my Win7 host.
I have other port forwarding set up in the router to the physical win7 box, and those ports redirect fine. Redirecting to the VM just doesnt work.
I decided to power off the vm, and configure the nic as NAT instead of bridged. Once I did that and rebooted the vm, the vm wouldnt come up. It hung.
I really dont want to tear apart the whole vm and rebuild. Seems silly. Why doesnt port forwarding from the router to the bridged vmnet0 work?
Hello,
I get this message
msg.vmxaiomgr.retrycontabort.rudeunplug:Operation on file "D:\Virtual_Machines\Arbeit\Arbeit.vmdk" failed.
...
The last thing I have done in this VM was installing Microsoft updates.
Has anybody any idea ?
Hendrik
except from log
Jan 19 15:21:18.212: vmx| VMXAIOMGR: Retry on write "D:\Virtual_Machines\Arbeit\Arbeit.vmdk" : Unknown error 665 (0x299).
Jan 19 15:21:18.212: vmx| VMXAIOMGR: system : err=170242 errCode=665 freeSpace=213551165440
Jan 19 15:21:18.212: vmx| VMXAIOMGR: "D:\Virtual_Machines\Arbeit\Arbeit.vmdk" : write s=49279991808 n=65536 ne=2
Jan 19 15:21:18.212: vmx| VMXAIOMGR: v[0]=30F14200:3584
Jan 19 15:21:18.212: vmx| VMXAIOMGR: v[1]=22AC000:61952
Jan 19 15:21:18.213: vmx| VMXAIOMGR: Retry on write "D:\Virtual_Machines\Arbeit\Arbeit.vmdk" : Unknown error 665 (0x299).
Jan 19 15:21:18.213: vmx| VMXAIOMGR: system : err=170242 errCode=665 freeSpace=213551099904
Jan 19 15:21:18.213: vmx| VMXAIOMGR: "D:\Virtual_Machines\Arbeit\Arbeit.vmdk" : write s=49279991808 n=65536 ne=2
Jan 19 15:21:18.213: vmx| VMXAIOMGR: v[0]=30F14200:3584
Jan 19 15:21:18.213: vmx| VMXAIOMGR: v[1]=22AC000:61952
Jan 19 15:21:18.213: vmx| VMXAIOMGR: Retry on write "D:\Virtual_Machines\Arbeit\Arbeit.vmdk" : Unknown error 665 (0x299).
Jan 19 15:21:18.213: vmx| VMXAIOMGR: system : err=170242 errCode=665 freeSpace=213551099904
Jan 19 15:21:18.213: vmx| VMXAIOMGR: "D:\Virtual_Machines\Arbeit\Arbeit.vmdk" : write s=49279991808 n=65536 ne=2
Jan 19 15:21:18.213: vmx| VMXAIOMGR: v[0]=30F14200:3584
Jan 19 15:21:18.213: vmx| VMXAIOMGR: v[1]=22AC000:61952
Jan 19 15:21:18.214: vmx| VMXAIOMGR: Retry on write "D:\Virtual_Machines\Arbeit\Arbeit.vmdk" : Unknown error 665 (0x299).
Jan 19 15:21:18.214: vmx| VMXAIOMGR: system : err=170242 errCode=665 freeSpace=213551099904
Jan 19 15:21:18.214: vmx| VMXAIOMGR: "D:\Virtual_Machines\Arbeit\Arbeit.vmdk" : write s=49279991808 n=65536 ne=2
Jan 19 15:21:18.214: vmx| VMXAIOMGR: v[0]=30F14200:3584
Jan 19 15:21:18.214: vmx| VMXAIOMGR: v[1]=22AC000:61952
Jan 19 15:21:18.214: vmx| VMXAIOMGR: Retry on write "D:\Virtual_Machines\Arbeit\Arbeit.vmdk" : Unknown error 665 (0x299).
Jan 19 15:21:18.214: vmx| VMXAIOMGR: system : err=170242 errCode=665 freeSpace=213551099904
Jan 19 15:21:18.214: vmx| VMXAIOMGR: "D:\Virtual_Machines\Arbeit\Arbeit.vmdk" : write s=49279991808 n=65536 ne=2
Jan 19 15:21:18.214: vmx| VMXAIOMGR: v[0]=30F14200:3584
Jan 19 15:21:18.215: vmx| VMXAIOMGR: v[1]=22AC000:61952
Jan 19 15:21:18.215: vmx| VMXAIOMGR: Retry on write "D:\Virtual_Machines\Arbeit\Arbeit.vmdk" : Unknown error 665 (0x299).
Jan 19 15:21:18.215: vmx| VMXAIOMGR: system : err=170242 errCode=665 freeSpace=213551099904
Jan 19 15:21:18.215: vmx| VMXAIOMGR: "D:\Virtual_Machines\Arbeit\Arbeit.vmdk" : write s=49279991808 n=65536 ne=2
Jan 19 15:21:18.215: vmx| VMXAIOMGR: v[0]=30F14200:3584
Jan 19 15:21:18.215: vmx| VMXAIOMGR: v[1]=22AC000:61952
Jan 19 15:21:18.215: vmx| Msg_Question:
Jan 19 15:21:18.215: vmx| [msg.vmxaiomgr.retrycontabort.rudeunplug] Operation on file "D:\Virtual_Machines\Arbeit\Arbeit.vmdk" failed.
Jan 19 15:21:18.215: vmx| If the file resides on a remote file system, please make sure your network connection and the server where this disk resides are functioning properly. If the file resides on removable media, reattach the media.
Jan 19 15:21:18.215: vmx| Choose Retry to attempt the operation again.
Jan 19 15:21:18.215: vmx| Choose Abort to terminate this session.
Jan 19 15:21:18.215: vmx| Choose Continue to forward the error to the guest operating system.----------------------------------------
Jan 19 15:22:18.946: vmx| Msg_Question: msg.vmxaiomgr.retrycontabort.rudeunplug reply=1
Jan 19 15:22:18.946: vmx| Msg_Post: Warning
Jan 19 15:22:18.946: vmx| [msg.vmxaiomgr.corrupted] VMware Server cannot sync with disk before abort. Disk D:\Virtual_Machines\Arbeit\Arbeit.vmdk may be inconsistent.
Jan 19 15:22:18.946: vmx| ----------------------------------------
Jan 19 15:22:18.964: vmx| User requested abort: Exiting because of failed disk operation.
Jan 19 15:22:18.964: vmx| Win32 object usage: GDI 4, USER 5
Jan 19 15:22:18.964: vmx| CoreDump_CoreDump: faking exception to get context