Ahh, my bad, should have posted that. I ahve everything updated to current with 4.2. This is a relatively fresh install:
root@proxmox:~# pveversion -v
proxmox-ve: 4.2-48 (running kernel: 4.4.6-1-pve)
pve-manager: 4.2-2 (running version: 4.2-2/725d76f0)
pve-kernel-4.4.6-1-pve: 4.4.6-48...
Yeah, 9% is pretty high. My mirrored SSD's average about 0.2% at idle, and I have never seen them go above ~2%.
So, you plugged the SSD in, but you haven't yet mounted it or made it accessible?
Hi all,
I have been following the guide in the Proxmox Wiki on the topic, but I have run into issues.
First off, let me share my plan:
My proxmox box will also serve as a HTPC for two different TV's using two separate Geforce 720 GT cards passed through to VM's running Ubuntu and KODI...
Interesting note on this. I did a fresh install using the same 16.04 template, and this time avahi-daemon installed normally. (???) o_O Maybe an Ubuntu repository change?
During your install of Windows, what are your IO wait percentages under the server status tab?
If that 500GB sata drive is a single spinning hard drive, I'd imagine it might be your bottleneck. Hard drives are not fun to wait for even with a single OS at a time, run multiple OS:es on a...
Hey all,
So I know the two common methods of USB pass through are either on a per device basis using the USB device ID, or to pass through an entire USB controller, so that any devices plugged into that controller show up in the VM not in the host.
I have some problems with both of these...
So, while I got the driver to install, I ran into problems getting it to work in an LXC container.
I bind mounted /dev/nvidia0 and /dev/nvidiactl inside my container in the /dev folder (I didn't have a /dev/nvidia-uvm) and then also installed the same Nvidia driver binary inside the container...
Interesting side note.
I have two pools on my Proxmox box:
rpool, the pool created by the proxmox installer, which contains the root file system and my container storage and VM drive images. This pool consists of two mirrored 512GB Samsung 850 EVO drives.
zfshome is my mass storage pool. It...
I found a comment on the lxc mailing list which speaks to your auto-start issue here
For this person - for some reason - defining the dns-nameservers manually in the /etc/network/interfaces in the container and suddenly his services were starting on boot.
I'm not sure WHY this would work, but...
That is a very good page, thanks for that link. I've been looking for data like this for some time.
Back when I bought my SLOG/ZIL drives two years ago (dual 100GB Intel S3700 in mirror) I couldn't find much information like this. I wound up going with the S3700's based on forums...
Hmm. I had a similar problem when I copied my 14.04 based Mythbuntu 0.27 install into a 14.04 based template. Everything worked, but suddenly my mythbackend stopped starting on boot and needed to be manually started.
I wonder if this is somehow related.
Hmm. I've removed the devices from /etc/initramfs-tools/modules, and updated initramfs, so on next reboot they should be freed from pci-stub, but I really don't want to reboot right now.
I wonder if there is a way to release the devices from pci-stub in the running environment.
Ugh.
Never mind. I'm an idiot.
I had originally planned to do a PCI passthrough of the adapter, but decided that a container would be better. When I did that I added the nvidia adapter to stub, and forgot all about it. I'm guessing this error is happening because the device is claimed by...
Thank you for your response. I blacklisted nouveau back over a week ago when I first posted this thread. The others I have never seen:
root@proxmox:~# lsmod |grep -i riva
root@proxmox:~# lsmod |grep -i nvidia
root@proxmox:~# lsmod |grep -i nouv
Judging by the content of /proc/version the...
So, I tested this template today. It installs OK, but I had a problem with package installs.
The package avahi-daemon fails to install through apt with the following error:
Setting up avahi-daemon (0.6.32~rc+dfsg-1ubuntu2) ...
Failed to add /run/systemd/ask-password to directory watch: No...
For what it is worth, I followed my proposed steps, and after a brief issue in getting the UUID of the newly created swap partition to update in udev, because I mistakenly thought that marking a partition as swap (code 82?) in fdisk automatically ran makeswap, everything worked beautifully.
Oh jeez.
I spent hours troubleshooting this. It turns out it was not a problem with my samba shares at all, I had them set up right the first time. It was a problem with the permissions set on the standard image of the work windows 7 laptop I was using to test... :rolleyes:
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.