Tag Info

Hot answers tagged

9

When you move the disk image, the installed OS is not aware of that, and it tries to boot with the drivers for the controllers of the previously used virtualization platform. Windows, when it cannot find the driver for the currently installed disk controller, BSOD's and reboots. This is pretty much the same as moving a windows hard drive between different ...


7

You should be using NTFS, unless you have a good reason not, such as a very old legacy application not supporting NTFS. You can have a look at a feature set comparison here, but basically, NTFS has more features (including native file security options that FAT lacks), and there's just no reason to pick FAT over NTFS for an internal disk unless you have to. ...


7

I still don't understand why /22 instead of /23 Because you have calculated your subnets wrong, and you are trying to use IPs from two different subnets. Or to put it a different way, if you use a /23 bit mask your starting address for the range, must be the first address for that range. 192.168.1.1 is not a starting address for any network described ...


5

The Snapshot is part of a chain of images and requires the availability of all snapshots. You can boot off the snapshot, but you must have all the previous images intact as well Having a snapshot chain does degrade performance. Highly loaded server VMs should not be running off of snapshots at all To manage snapshots, you simply try to keep ...


4

start using libvirt - there's no reason to use qemu-kvm directly, when you have a good management package available start using virtio devices for disks and networking define what it is you're trying to do, and ask a question then the benefits are very simple - libvirt generates the kvm command line for you, pushing in a large set of optimizations, ...


4

Look into ZFS on Linux. That will deduplicate all day long... You'll need a lot of RAM and may find that this may not be worth the effort (you could have sized appropriately for your needs), but it does work.


4

This is very simple to do. Normally, you would use bridging on the host, the bridge acting as a virtual switch for the VMs and the physical NICs to plug into: network -> Host NIC -> BRIDGE <- VM With VLANs this gets a bit more complicated: network (trunk port) -> Host NIC -> Tagged IF -> BRIDGE <- VM All of this is managed in ifcfg scripts on a ...


4

Disclaimer: I work for Red Hat but have no idea about the decisions related to this particular bug. I made a request, though, and the bug is now public. The short version is: passthrough seems to have a lot of bugs in different situations, none of them simple fixes, and it (again, really not speaking officially here) seems like it was judged to not really ...


4

When the user's home directory is encrypted with ecryptfs sshd cannot read the authorized_keys file from the user's home directory before the home directory has been mounted. During login sshd will use pam to authenticate the user, and pam will use the password entered by the user to mount the encrypted home directory. This is problematic if you want to ...


3

You can use ebtables for this assuming you are assigning a mac to every VM on the host node. http://ebtables.sourceforge.net/ This in simple terms locks it down by mac address and will only allow the VM's to use IP's specifically assigned to them.


3

list files in /etc/libvirt/qemu/networks/ and /etc/libvirt/qemu/networks/autostart/ if empty - create it useful commands: virsh net-start default or virsh net-autostart default and virsh net-destroy default virsh net-undefine default service libvirtd restart for detailed explanation read wiki: http://wiki.libvirt.org/page/Networking


3

You need to restart your VM for it to use the new version of qemu.


3

Install the SPICE Guest Tools in your Windows guest. Then shut it down and reconfigure it so that it uses a SPICE channel and QXL video. The corresponding XML is: <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> ...


3

.img is just an extension, you can call the file disk.disk or whatever else. The default format is what matters. The most common format is RAW - it has the best access speeds because it is what it's called - just direct mapping of blocks, nothing else. This also means no extra features. The arguably second most common format is QCOW2, this is a bit slower ...


3

OpenStack will run fine on a single machine, and this is indeed a useful setup in scenarios like evaluation or developing OpenStack itself. A tool called PackStack, which is available on RHEL variants, makes it pretty easy to deploy. But OpenStack is probably overkill for your scenario, unless you plan to expand to multiple physical servers in the future. ...


3

If "ifconfig -a" on the guest does not show an eth0, then run "virt-manager" on the host to get a nice GUI for editing the virtual machine's parameters instead of doing it on the command line. Through that GUI you can add a network interface if you need one. Once you have an eth0 on the guest, then you will need to specify the parameters of the interface in ...


3

You are over-NATting; you are NATting not just inbound connections to port 80, but outbound ones as well. Modify the NAT rule to specify that the traffic must be coming in from outside, eg -A PREROUTING -p tcp -m tcp -i eth0 --dport 80 -j DNAT --to-destination 192.168.122.47:80 and it will stop matching (and interfering with) legitimate outbound traffic ...


3

As you are using Openstack, when you create a flavour you can specify the rxtx_factor. My understanding is that this is used to calculate a percentage of the rtx_cap on the network that is available to the VM. I'm not sure if all hypervisors will support it however, though so you may need to do some additional digging to see if KVM does.


3

I would say you have a lot more to consider than just hard drives. You are intending to transfer to a completely different virtualization package, which will take much more than a days worth of work. Theoretically you would need to: - Transcribe the VM configurations (more than likely by hand) from Microsoft's spec to QEmu's spec. - Convert the VHD images ...


3

I got so inspired by kasperd's idea yesterday that I made this: https://github.com/bjornnorman/decryptfs-ssh I've tried it out a little already and it seems to work brilliantly. It makes it really simple to add/remove keys for passwordless decryption of ecryptfs home folders when using SSH... Like kasperd's original, it hasn't been exposed to a peer ...


3

This is for google guys like me. Those answers are pretty useless, this is not a distro problem but a bug in Windows: http://keyliner.blogspot.se/2009/11/windows-7-slow-keyboard-response.html (second clause) That is what helped me: a. Start, Run, "Regedit" If the RUN command is not visible, see this link. b. Tunnel to this key: ...


3

If you don't want to do any configuration inside the guest, then the only option is a DHCP server that hands out static IP addresses. If you use bridge mode, that will probably be some external DHCP server. Consult its manual to find out how to serve static leases. But at least in forward modes nat or route, you could use libvirt's built-in 'dnsmasq' (More ...


3

You need to specify a valid URI for the migration to be successful. What kind of transport is available depends on your setup, but try qemu+ssh://10.8.1.9.


2

How to achieve top performance with QCOW2: qemu-img create -f qcow2 -o preallocation=metadata,compat=1.1,lazy_refcounts=on imageXYZ The most important one is preallocation which gives nice boost, according to qcow2 developers. It is almost on par with LVM now! Also you can provide unsafe cache if this is not production instance (good for testing): ...


2

Old question, I know. But to answer anyway: you cannot have two default gateways. That's where the RTNETLINK answers: File exists error comes from when issuing ifdown and ifup. Remove the gateway 10.10.20.1 line from either eth0 or eth1. And more general: /etc/init.d/networking restart or service networking restart were never really supported and are not ...


2

As I know you can put ISO image here /var/lib/vz/template/iso Then you can install guest OS from web interface.


2

I mostly agree with Jeffrey's answer. However I wrote the post you mentioned for that specific purpose (running smartos with 1 public IP) so here my suggestions if you applied my procedure. http/https traffic: Install nginx in a zone or kvm guest (let's say ip 10.0.0.2 port 80) Add the port redirection in /etc/ipf/ipnat.conf (or NAT section in ...


2

Hyper-V - no question here. Not becasue of performance but because all viretualization is fully integrated and maintained as part of windows updates. No need to install anything unless you run outdated windows versions. That said: HD 500 GB Welcome to the reality of virtualization. It does not makgically make crappy hardware faster. A 500gb HD is not ...


2

Not possible with proxmox, since it doesn't implement all of KVM's potential. On normal KVM setups with libvirt or other management systems, like oVirt, this is possible using a serial console to the VM.


2

No, there isn't for KVM guests according to Proxmox.



Only top voted, non community-wiki answers of a minimum length are eligible