Tag Info

Hot answers tagged

3

-device e1000,netdev=hostnet0 This. Switch to virtio_net before you try anything else. step two: try to play with the NIC offload settings using ethtool -K turn off TSO, LSO, LRO, see if you get different results. step three: try a different distro. Ubuntu is notorious for KVM related bugs, so switch to CentOS or even Fedora as a test.


3

Check that your VMs have ip addresses on 10.x.x.x/24 (netmask 255.255.255.0) Set 10.x.x.11 (br0 ip address) as the default gateway of your VMs Enable ip forwarding on the physical host Enable SNAT with: iptables -t nat -A POSTROUTING -s 10.x.x.x/24 -o eth1 -j SNAT --to y.y.y.102


3

You may be overthinking this. The manual assignment of cores here could actually result in lower performance. In the VMware world, we don't do this unless there are very specific requirements, but for the workload and applications you've described, it's not necessary. Let KVM schedule things and be done. If in doubt, get more cores and sockets. But CPU ...


3

You can, but you probably shouldn't. The DL360 G7 doesn't present disks in a JBOD fashion. If you're using the onboard HP Smart Array controller, this won't work the way you expect. Depending on the OS you use, there are swap and other I/O activity considerations. Why go through all of this? If you want ZFS, just use it on the server in a baremetal OS ...


3

Is it safe to boot Linux from a USB drive? Yes, why not? I do it regularly. But having said that, it's not entirely trivial to do it well. If you just straight install Linux to a USB disk it's usually really slow and doesn't really work that great. However, if you use a tool like unetbootin it'll create a more optimal installation with which you can ...


2

Define "safe". As in: Does the system boot from USB? Yes Data integrity? No Fault tolerance? No I would not trust a file server to be booted from a single USB pen, unless it's a server just for testing/lab etc. We use USB drives (expensive ones) in our vSphere Cluster, and I've encountered failures many times. You've indicated that you have replaced the ...


2

Define the bridge interface with eth0 as port Set the IP address on the bridge interface You will need the bridge-utils package installed (most likely is already there). Here's how you would configure this in /etc/network/interfaces. Restart the network service (or reboot the machine) auto lo iface lo inet loopback auto eth0 iface eth0 inet manual ...


2

Assuming you were using replica 3, when 2 hosts go down the file system becomes read-only and this could explain what you currently see to some degree. In most cases we should expect the VM to freeze as qemu cannot write to the storage, but I need some more information about it so log files from the hosts are needed here. First of all let's see that the ...


2

You appear to be attempting to install using a serial console, rather than a normal console. Not sure why you're doing that, but... By default the installer tries to display either text or graphics on the Linux console. To divert output to the serial console you need to hit Tab at the boot screen, and ensure that you add the following options to the boot ...


1

iptables -t nat -I POSTROUTING -s 10.x.x.x/24 ! -d 10.x.x.x/24 -j SNAT --to-source y.y.y.102 this must be changed to iptables -t nat -I POSTROUTING --out-interface eth1 -j SNAT --to-source y.y.y.102 According to your first rule, only packages with destination to 10.x.x.x must be processed. So, what about traffic from outside to your network? (source ...


1

Ever considered using technology applicable for the job? I can not imagine a backup that requires the VM to be turned off and then is done via a hodge podge script, instead of having a backup software that integrated with the hypervisor. Plus, this is not nevessarily "either or". I use Hyper-V and we do machine backups from the host twice per day - BUT: ...


1

You're seeing this error because Ubuntu put their own customizations into its version of libvirt and qemu/KVM. RHEL, of course, did the same thing. But there's always a machine type that will work, namely, pc. Somewhere in the XML you'll find something like: <type arch='x86_64' machine='pc-i440fx-trusty'>hvm</type> Just change this to: ...


1

The issue ended up being the guest firewall blocking the application port, and not kvm or bridging related


1

You need to remove IP address configuration from eth0, add eth0 to the bridge and then configure IP address on the br0 interface.



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