Tag Info

Hot answers tagged

6

install virsh then virsh autostart your_vm_name


5

Open the VM display, click View->Details Select Boot Options, and tick Start virtual machine on host boot up


4

The normal way to do this installation is: Create the VM with a virtualized IDE disk, not a virtio disk. Before running the installation, choose to customize the hardware, and attach a second virtual hard drive which does use virtio. This hard drive need only be a temporary drive; it could be a tiny 1GB blank something or other. Install Windows. (I ...


4

Or you can place the VM xml in /etc/libvirt/qemu/autostart/


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

You can use a virtual tablet instead of the virtual mouse, and then you won't have to press Ctrl_L & Alt_L. The virtual tablet also improves the mouse tracking by using absolute coordinates instead of relative motion deltas. To use the virtual tablet, first shutdown your vm. Using virt-manager, select the virtual machine, then select View -> Details, ...


3

This fixed the issue.. mkdir /usr/lib64/xen -p cp /usr/lib/xen-4.1/* -r /usr/lib64/xen/ cp -r /usr/share/qemu-linaro/ /usr/share/qemu


2

The problem is with the xen config I think. I had a similar issue with connecting. To solve this on you need to edit /etc/xen/xend-config.sxp, and uncomment the following line: (xend-unix-server yes) and then restart xend http://www.xen-support.com/?p=338


2

Virt-manager (and virt-install) is just a front end for running QEMU (qemu-kvm in this case). When called with a PXE install, it works just like a physical server doing a PXE boot. That is, it runs QEMU as a virtual machine with a network-capable BIOS, with a built in IP stack. Now when run as a Network install (non-PXE), virt-install first fetches a ...


2

Assuming you KVM host server's (CentOS) IP is $SERVER. Run the following in console: localhost$ virsh -c qemu+ssh://$SERVER/system list --all This should show the list of libvirt quests as seen from your PC. Here's an example output (taken from my server): ID Name Status ---------------------------------- 1 freebsd9 ...


2

If you see a connection for localhost (QEMU) listed, double click it. If you don't see any connections listed, go to File > Add Connection, leave all the defaults set as they are, then click Add.


2

--graphics none SHOULD work. By default RHEL bootup grub chooses graphical install mode if adapter is present. To use text mode installation "text" or "askmethod" must be specified in kernel options i.e. grub and it doesn't matter do you have text console or not. It's impossible to specify kernel options at installation for virt-install. It's possible for ...


2

I think you've got two problems. 1) setting up a single ssh connection that goes through the bastion host. This is basically the same problem as How do I do Multihop SCP transfers? so go read that first. 2) now that you know how to deal with it on the command line more transparently, you need to set it so that it happens without the CLI options. Set up ...


2

Yes. Use SPICE and the vdagent to have the best experience. SPICE is far more efficient than VNC and the vdagent will provide nice pointer and clipboard integration. I'm not familiar with the exact steps, but it comes down to this: Install the QXL video driver and virtio serial driver in the guest. Install the vdagent and start the Windows service. ...


1

Ok, I found this sudo nano /etc/polkit-1/localauthority/50-local.d/50-libvirt-remote-access.pkla with content [libvirt Management Access] Identity=unix-user:USER And restart sudo service libvirtd restart Verification virsh -c qemu+ssh://USER@SERVER/system sysinfo Source: How To Install KVM And libvirt On CentOS 6.2 With Bridged Networking


1

You probably haven't logged into your hardware node using -X switch of ssh. [root@yourmachine]# ssh -X root@<your-hardware-node-ip> From the man page: Enables X11 forwarding. This can also be specified on a per-host basis in a configuration file. X11 forwarding should be enabled with caution. Users with the ...


1

your problem happened to me then I try to solve it and I found that happened because KVM memory that I allowed to used from my computer and changed thee "ram from 512 MB allowed to 1024 MB allowed". You can open virtual manager (virt-manager) and edit your physical KVM resource.


1

The starting point of your investigation should be here : And it does not listens to port 16514: lsof -i tcp:16514 prints nothing This is quite a low level issue : the daemon does not listen on the tcp port. You should check for any log messages that could indicate an error, or launch the daemon manually in a terminal to see what it says...


1

For me the trouble was not having libvirtd_opts="-dl" in the config file /etc/default/libvirt-bin. so the daemon was not listening.


1

I found the solution here Unable to connect Xend with virt-manager: I need to enable xend-unix-server in /etc/xen/xend-config.sxp (xend-unix-server yes) I add this to my original question (instead of deleting it) in case someone needs it.


1

I needed to install the openssh-askpass package.



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