Search results

when run eject command in pve3.4, got "eject: unable to eject, last error: Inappropriate ioctl for device". I have to reboot the server to eject the cdrom. but once I closed the cdrom and run eject again, I got same error message again. how to solve this problem?

Sadly, I found nothing like "timer sources=hpet" in my bios setup. To make it worse, I have tried to use one core for the windows 2000 vm, and it resulted another problem mentioned in the following link. Don't know how to solve the situation...

udo, thanks. I'll check it and report on next monday.

hi, udo, thanks for replay again! I'm a little confused. Do you mean that I should check the bios setup of my physical server (lenovo R680)? and what do you mean by timer-config and bios-updates? do you have any suggest about how to setup timer-config and bios-updates?

Thanks for the reply. I think the keypoint is to run windows 2000 server vm on single core cpu? Isn't it? Was windows 2000 server operating system has bug on multiprocessor CPU?

I have checked the configuration and it shows "ACPI Multiprocessor PC". Can't windows 2000 server vm run on multiprocessor?

thanks for reply my question. here is the crazy vm config. boot: cdn bootdisk: ide0 cores: 4 cpuunits: 1000 ide0: S01-nx3200-lvmoiscsi-101:vm-105-disk-2,cache=writethrough,size=320G ide1: S01-nx3200-lvmoiscsi-101:vm-105-disk-1,cache=writethrough,size=600G ide2: none,media=cdrom memory: 4096...

I have a pve cluster with 3 nodes, and the pveversion command output is as following: root@pmx01:~# pveversion -v proxmox-ve-2.6.32: 3.2-136 (running kernel: 2.6.32-32-pve) pve-manager: 3.3-1 (running version: 3.3-1/a06c9f73) pve-kernel-2.6.32-32-pve: 2.6.32-136 lvm2: 2.02.98-pve4 clvm...

It turns out this is a problem of windows server 2000 itself. and according following link http://forum.proxmox.com/threads/3861-kvm-high-cpu-load-running-a-Windows-2000-VM I found this solution http://support2.microsoft.com/default.aspx?scid=kb;EN-US;919521 It indeed works. thanks proxmox and...

Magrated vm from vmware esxi 4.0 with windows server 2000 os, in PVE summary, CPU Uage keep 100%, but the windows task manager shows cpu usage 3%. I have run top command in the PVE nodes, it shows that KVM process keep high cpu usage. What's the problem and how to solve it?

[solved] And the process is as following: step 1. Imagrate the vmware workstation 10 vm to proxmox with systemrescued cd 4.3.1 and “netcat -w30 -vvnlp 3333 | gzip -dc > /root/test.raw" on proxmox server and "dd if=/dev/sda | gzip -c | nc -w30 -vvn pmxipaddress 3333" on vmware vm. step 2. setup a...

thanks, I'll look into this.

To the best of my knowledge, I know that vmware-vdiskmanager can convert vmdk to another vmdk, but not qcow2 or raw. Is there any vmware tools to convert vmdk to qcow2 or raw? any details? Also I'd like to migrate the vm through network. Can clonezilla solve this problem?

mir, thanks for replying. I have tried pessing F12 in the BIOS screen, the output is as following Select boot device: 1. ata0-0: QEMU HARDDISK ATA-7 Hard-Disk (21504 MiBytes) 2. DVD/CD [ata1-0: QEMU DVD-ROM ATAPI-4 DVD/CD] 3. iPXE (PCI 00:12.0) 4. Legacy option rom the option 1 is the...

or run out of space on the vmware esx server? dd if=/dev/sda | gzip -c | nc -w 30 -vvn proxmoxipaddress 3333, is this command requires a lot of memory space or disk space on the vmware esx server? Can clonezilla solve this problem?

I have built another vmware workstation 10 vm, with vmware IDE disk. I checked the IDE disk, fdisk -l reports that /dev/sda1 start by sector 63. I imagrated this vm to Proxmox, and everything is ok. The imagration-failed vm uses vmware scsi disk, which has the /dev/sda1 start sector 56. Is it...

Migration VMware workstation 10 vm to Proxmox. I have done the migration according to the wiki page by Systemrescued CD 4.3.1. Everything seems ok. but when I boot the vm in proxmox, it reports error loading operating system. I checked the migrated disk image. fdisk -l reports that the /dev/sda1...

According to wiki page, I am tring to Migrate a windows 2000 server vm (with 2 vmware scsi disk, disk 1 about 300G, disk 3 about 500G) to proxmox. I reboot the vm with SystemrescuedCD 4.3.1, and run following commands on proxmox server and vm respectively proxmox server: netcat -w30 -vvnlp 3333...

Good news!

I have proposed the case to the vendor of the security scanning product already, and I will keep this posted once I got the reply.