Search results

So are you using the proxmox environment on top of ubuntu to get it to work? - I might have to do that as I need this working ASAP. Before I do this, any viable alternative that is stable?

Sure but my Proxmox server runs heaps of KVM and LXCs and I would rather not move OS, simply because proxmox bug causes this issue.

Hint: It's KVM so follow one of the guides online and set a few settings in config pertaining to the CPU. Finally Vanilla OSX is a pain to deal with using a distribution helps vastly - no need for fakesmc and annoying config settings. But back to VM passthrough, if QVFM works how can I get it...

Same behavior on AMD hardware with No IGP.

Observed same behavior.

Ok my apologies, similar issue so I thought might be the reason, obviously not then :/

It seems to be caused by a Bug in QEMU - https://bugs.launchpad.net/qemu/+bug/1488363?comments=all - maybe its best to select the affect me too button to gain more attention to a solution.

Wow your really doing something outside the books by visualizing OSX with PCIE Passthrough, but fair enough - hopefully passthrough can get fixed. I really need it too.

Why? Also I use PCIE passthrough and noticed that on Proxmox it didn't work, would using QVMP fix the issue? I really would like to get it working ASAP.

Hi Everyone, I have recently set up a server with a UPS as I have experienced a few power cuts as of late, I use Network UPS Tools (NUT) to shutdown the server in the event of a power outage. Currently it uses "shutdown -h 0" to shutdown the server however this is undesirable as the LXC...

Hell Everyone, Quick Bug Report: When booting the console gets filled with messages like this "EXT4-fs (loop4): couldn't mount as ext2 due to feature incompatibilities" for every LXC container. This is obvious as the FS is ext4 and wouldn't be an issue however dmesg is filled with this error...

Re: Proxmox 4.0 - Maximum Number of LXC Containers is restricted to 9 (LOOP bug) Will a patch be available before release through apt?

When I load Proxmox 4 with the latest update the console no longer works, This is what I instead see when loading NOVNC Console - This happens in both the latest chrome and firefox. Any Ideas? Regards - Harrison

Thanks, I was dealing with this for 2 hours until I saw your post to remove slash.

Re: Proxmox 4.0 - Maximum Number of LXC Containers is restricted to 9 (LOOP bug) Thanks for prompt response, in the mean time manually making them works but is lost upon reboot "mknod -m 660 loop9 b 7 9".

Hi, When I try to launch more than 9 LXC containers after reboot, it seems to fail. When attempting from CLI I get this from the output of 'lxc-start" - lxc-start 20150427012246.584 ERROR bdev - bdev.c:find_free_loopdev:1907 - No loop device found lxc-start 20150427012246.584 ERROR...

Is it still recommended to use a 32bit OS in an LXC container in terms of resources?