Search results

No more need to patch qemu. http://forum.proxmox.com/threads/19722-Mini-HOWTO-Running-Mac-OS-X-10-9-under-Proxmox-3-3

Can you prove it? We have quite a lot of software raids, and experienced problems only with ext4 on them when sparse qcow2 files were expanded greatly.

We had problems with ext4 (http://forum.proxmox.com/threads/19149-filesystem-failure-%28ext4%29), so on newer installations we have good old ext3.

And what about your openvz containers? :) It's better to do kill `cat /run/rsyslogd.pid`.

See that thread: http://forum.proxmox.com/threads/19722-Mini-HOWTO-Running-Mac-OS-X-10-9-under-Proxmox-3-3

It's started, but I can't say anything whether it runs normally or not, because I don't use it for something useful yet. It sh'ld be jenkins node in future.

Today I succeed to run Mac OS X 10.9.2 under Proxmox 3.3. You need Intel Core2Duo or later Intel's CPU. Read carefully this post. I won't explain things explained there. Install OSX into virtual hdd as described in link above, and copy file with hdd image to proxmox...

yes

We've encountered a problem with host filesystem (twice with 2.6.32-29 on one system and 4 times with 2.6.32-30 on another one): EXT4-fs error (device md0): ext4_ext_search_left: inode #27526386: (comm kvm) ix (4064983) != EXT_FIRST_INDEX (0) (depth 1)! We've encountered it during...

no, fstab has only options "noatime,errors=remount-ro", so mount shows "rw,noatime,errors=remount-ro,barrier=1,data=ordered"

Software RAID1 on cheap SATA3 drives.

We tried to run one of Win2k8 VM with cache=writeback to test its disk performance as with default cache=none we have very poor disk performance (io wait is about 20% with only one active VM). Host system had pve-kernel-2.6.32-29-pve. After several minutes of not very active write operations...

Yesterday I was experimenting with different SCSI controllers emulation (I had a problem with VM migrated from VMWare), and I've found problems with LSI 53C810 and VMware PVSCSI. LSI 53C810 — seabios doesn't see it. VMware PVSCSI — 1) seabios doesn't see it, 2) kvm doesn't with 2...

There was a OS loader installed inside to "activate" system. It was causing problems.

[SOLVED] Re: Win2k8r2 dies when "Microsoft Windows 7/2008" profile is set I'm sorry, but it was not a Proxmox issue, it was issue with OS inside VM. Clean Win2k8r2 runs as it should.

2.6.32-29-pve 2008R2 Standart Actually, on proxmox it dies even with CPU set to `host', i can't notice actual bsod code cause VM reboots immediately. I was experimenting on my Debian Wheezy desktop with QEMU 2.0 taken from backports to find solution. CPU on proxmox: cpu family : 6 model...

When "Microsoft Windows 7/2008" profile is selected on OS tab during VM creation, then qemu will be invoked with options -cpu kvm64,hv_spinlocks=0xffff,hv_relaxed,+lahf_lm,+x2apic,+sep -global kvm-pit.lost_tick_policy=discard, so when VM is started Windows dies with bsod code 0x5d (Unsupported...