Search results

you could install the Debian Wheezy default 3.2 kernel or compile your own up to 3.10 (3.9 is supposed to introduce some good SSD improvements). Of course in the process you loose all OpenVZ capability and all Support from the kindly Dev's from the Proxmox team :D

Would it be possible to add a check box (or like) option that will allow virt-viewer to open full screen. It's just a case of inserting the "-f" switch into the launcher some how. would be usefull when opening desktop OS's that will be used for a length of time, just to skip the "F11" usage for...

Sorry. but while hunting around looking into this I broke the server. So have re-installed from scratch and done a full update from fresh and it all appears to be working fine now. Was a little too keen to have a play around with the new spice viewer :)

I get exactly the same thing ..on IE and firefox. All machines on local LAN. Also noticed in the .vv file host-subject is missing a "U" on the second OU. adding this and the file correctly deletes now. still getting the error message though.

I had a play with a test server after reading this. Installed the SID backport kernel (3.2). Other than loosing the openVZ features it all seems to work quite well. This is clustered to an up to date 2.3 with original kernel and migration etc all still work fine. (don't have fencing set up so...

you've made all the changes as per here? http://doc.pfsense.org/index.php/VirtIO_Driver_Support Admittedly it mentions qemu-kvm 1.0, but....

From what I have read on the PFsense forums 2.0.2 doesnt have virtIO drivers installed. so if you want to stay with that version I'd recommend you move to physical hardware. There is a thread for enabling the virtIO drivers in 2.1(RC1) and plenty of reports that it is in stable production use by...

So your running pre-release 2.3 in production? what version of PFsense are you using? Chances are, your'll get a better response from their forums.

My understanding was that only version 2.1 of PFsense worked well under KVM (has the VirtIO driver in base) and that version is still in beta. You'd be best on deadicated hardware for running a Firewall device.

This is very cool stuff. Now, who do we thank for pushing out spice patches *** ;) ;) *** :rolleyes:

DOH!! yep that did it... thanks Tom.

I'm not seeing RBD in my menu? Have done a dist-upgrade a couple of times to be sure.

Can be done by not assigning an IP to the WiFi nic but to the bridged Virtual nic in a KVM for say a PFsense firewall box. just having the lan vmbr with an IP so you can manage it. but I'm sure that you'll get plenty of people saying it's not a good idea to expose the host NIC (blank IP or not)...

Just out of couriosity as I have used nested esxi vm's for learning purposes before, Can ProxmoxVE be installed onto Debian CT's and make use of the CPU extensions in order to play around with migration, HA etc while learning the software?

Just put your iscsi storage on a deadicated subnet with eth1's physical port pluged into that subnet. I've got an IBM box with 4 NIC's, two of which are doing MPIO iSCSI to a SAN this way. (using vLans).

They're in the WLH folder.. for "Windows Long Horn" Vista's code name pre release. the XP 64bits ones on the other hand do seem to be missing.

I'm also curious as to whether anyone has managed to get SCSI (or iSCSI) tape passthrough working as it is something I would like to setup on a upcoming build.

On the page linked in that URL. Setup your appliance with all these services and tools Step 1: Install NexentaCore, OpenIndiana or Solaris Express 11 (from Boot-CD on real Hardware or virtualized on a vti-d capable esxi Virtual Server to passthrough SAS-controllers and...

you'll need to download devcon.exe from microsoft and then follow the instructions in the Balloon.inf file ;Installation Notes: ; Using Devcon: Type "devcon install BALLOON.inf PCI\VEN_1AF4&DEV_1002&SUBSYS_00051AF4&REV_00" to install

if you want to go the Solaris route, you could have a look at OpenSolaris/OpenIndiana with napp-it. http://www.napp-it.org/index_en.html