Recent content by ParanoiK

Also check if interrupts are not shared with other device.

Add the args line to /etc/qemu-server/<vid>.conf To change cpu type add to args parameter -cpu <type> I suggest using type "host". So to add all things you shoud put this line in config: args: -pcidevice host=05:02.0 -cpu host Also I think you just have to unload the driver...

I've got new kernel and passtrough works great. To do that you shoud modify your config file and add line: args: -pcidevice host=00:00.0 Where 00:00.0 is address of your device. You can get it for example from lspci. And one thing: remember to unload pci driver/module from host...

Try adding this line in config: args: -cpu host

You can't run pfSense as container, it's FreeBSD. I'm using pfSense, I can try running OpenVPN when I get back from work and check it.

Any ideas? ;-)

Hi, I've got quick question: are there any implementation of VIRTIO drivers for FreeBSD? I'm trying to mount some home file server and transfers are bad :/ I'm trying to identify if the bottleneck is net or drive, but I'm afraid that both are the problem.

Ide disk shouldn't be a problem, I use it on FreeNAS ostype: other memory: 1024 sockets: 1 name: FreeNAS bootdisk: scsi0 scsi0: local:101/vm-101-disk-1.raw boot: c freeze: 0 cpuunits: 8000 acpi: 1 kvm: 1 ide0...

Hmm... the configuration is straight-forward, nothing complex. ostype: other memory: 512 sockets: 1 name: SERWER ide2: none,media=cdrom vlan0: e1000=BE:D8:3A:62:EB:A4 bootdisk: scsi0 scsi0: local:104/vm-104-disk-1.raw onboot: 1 cores: 1 scsi9: local:104/vm-104-disk-2.raw One...

What config? VM config or fbsd kernel config? Have you done any updates then?

In that moment yes, there was no point in using customized (or in fact I'm too lazy to make new one while everything works fine ;-)). Also I'm trying to find some info about anyone trying to implement VIRTIO drivers.

Any error msgs, logs? I've got 4 fbsd (7.2, 8.0) machines running with no problems. Have you changed kernel config?

That looks very strange even for raid 5 without write cache. I've got similar output on one old PATA drive. You could try doing hdparm -tT /dev/<drive> and check is it really a drive problem. PS: are you sure that your raid isn't degraded?

That's strange, it souldn't happen. Are you sure the line in /boot/loader.conf is correct, without any special characters, etc?