similar to: So why does "destroy" not actually destroy?

On Tue, Jul 14, 2015 at 12:51:31AM +0000, KARR, DAVID wrote: > I thought it odd that if I have a running VM and I do "virsh destroy" > it results in a VM that is "shut off". To ACTUALLY destroy a VM, you > have to follow that with "undefine". Could someone elaborate on how > we ended up with these slightly confusing semantics? I asked this question in

I am trying to create a DomU guest domain to run snv77 over an a snv77 host, following the instructions and example in http://opensolaris.org/os/community/xen/docs/virt-install.html. I booted the xVM partition (selected xVM from the grub menu). virt-install spends 2 or 3 minutes after "Starting install ..." then fails. here''s what I get: bash-3.2# virt-install --name

Hi, Dear Mr/Mrs. I have two questions ask for help: my virt-manager and libvirt version is : linux-vaan:~ # rpm -q libvirt libvirt-0.8.5-1.2.i586 linux-vaan:~ # uname -a Linux linux-vaan 2.6.34-12-desktop #1 SMP PREEMPT 2010-06-29 02:39:08 +0200 i686 i386 GNU/Linux linux-vaan:~ # rpm -q virt-manager virt-manager-0.8.5-3.1.i586 linux-vaan:~ # cat /etc/SuSE-release openSUSE 11.3 (i586) VERSION =

Hi All, Im getting the following error when I run virt-install: bash-3.2# virt-install -n winxp-01 --hvm -r 384 --vnc -f /etc/opt/vms/winxp-01.img -s 16 -c /etc/opt/images/windowsXP_SP2.iso Starting install... libvir: Xen Daemon error : POST operation failed: (xend.err ''Error creating domain: vncpasswd is not set up in VMconfig and xend-config.'') Traceback (most recent call

Hi, After full new install of Fedora 19 or 20, I am getting this when I want to create a new VMs. Impossible de terminer l'installation : « Unable to create vcpu cgroup for fedora20(vcpu: 0): Aucun fichier ou dossier de ce type » Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper callback(asyncjob, *args,

Hi, I have been trying to get Xen 3.1 running on Fedora 7 since yesterday and no luck. At the beginning I thought it was a problem with teh installation of Fedora 7 so I reinstalled it. Still, I have the same problem. I have never had this problem with Xen (FC5,FC6). The xend.log (below) includes a line "VmError: Device 0 (vif) could not be connected. Hotplug scripts not working."

I’m confused. You’re asking if I’m able to connect with VNC in response to my comment that I’m unable to connect with VNC? What I see when I open the viewer on the port is a window titled “<username> X desktop”, with a grey background, an “X” cursor, and an error dialog (with an “okay” prompt) saying what I described before. Ctrl-Alt-F1 and similar keys do nothing. From: Jeff Tchang

This is offtopic, but related to what you’ve told me so far. I’m having some trouble getting the VNC connection to work. Technically, the “connection” is working fine, but the Windows TightVNC Viewer comes up with an error dialog saying this: Xsession: unable to start X session --- no "/home/.../.xsession" file, no "/home/.../.Xsession" file, no session managers, no window

On Sun, Jun 15, 2014 at 01:33:46PM +0300, Patrick Chemla wrote: > Hi, > > I sill need some help. > > I tried to remove cdrom and USB controllers from qemu xml definition > file. > > > Still same Failed to create chardev when trying to run a Vms that run > on my local Fedora 20 computer. You didn't answer my question in the previous email that you ensured that

Thanks for replying. Good info so far. After I start the VM, I’m going to need to see the boot console, and I’ll need to ssh into it with a hostname or IP. What are some required steps for those needs? This VM is going to need to access a few associated networks. I can see that the “—networks” option is part of the interface for configuring this. What are some things I’ll have to do for

Hello, I would like to ask what I am doing  wrong and what is the best approach to resolve this situation: First of all I start virtual machine by virDomainCreateXML. In my application I use libvncclient library that sends mouse events to this running domain. I had some troubles with coordinates of mouse cursor but all problem was solved when I added <input type='tablet'

Hi, I am trying to install CentOS on an Opensolaris Dom0. virt-install fails with an error in virDomainCreateLinux(). Is this a known issue? Am I missing some step? manoj@mowgli:~$ uname -a SunOS mowgli 5.11 snv_101b i86pc i386 i86xpv Solaris manoj@mowgli:~$ pfexec virt-install What is the name of your virtual machine? centos How much RAM should be allocated (in megabytes)? 512 What would

I''m unable to create a centos domU on Opensolaris 2009.6. I had no problem following the instructions to make Solaris a dom0. The same process worked just fine with the GUI virtual machine manager under OpenSUSE 11.1. For a number of reasons I''d prefer to use Opensolaris as my Dom0, but not if it going to be a battle to get everything to work. Is Xen actually a

Hi I have reinstall Fedora 20 from distrib. I have run yum update and yum upgrade. Running kernel is : 3.14.7-200.fc20.x86_64 Installed Libvirt packages are: libvirt-client-1.1.3.5-2.fc20.x86_64 libvirt-daemon-1.1.3.5-2.fc20.x86_64 libvirt-daemon-config-network-1.1.3.5-2.fc20.x86_64 libvirt-daemon-driver-interface-1.1.3.5-2.fc20.x86_64 libvirt-daemon-driver-network-1.1.3.5-2.fc20.x86_64

Hi, I try to start Solaris10 HVM DomU on SNV_93 dom0 running amd athlon x2 and 8gb ram. When I try to create a domU i get: bash-3.2# virt-install -n sol10 --hvm -r 1024 --vnc -f /dev/zvol/dsk/rpool/sol10 -c /rpool/pub/sol-10-u5-ga-x86-dvd.iso Starting install... virDomainCreateLinux() failed POST operation failed: (xend.err ''Device 0 (vif) could not be connected. Backend device not

Nah, RHEL 5.1+ supports 32-bit domU (PAE and non PAE) on 64-bit dom0. Actually RHEL Xen is 3.1 with the brain damaged 3.0 userland utilities. -Ross ----- Original Message ----- From: centos-bounces at centos.org <centos-bounces at centos.org> To: CentOS mailing list <centos at centos.org> Sent: Fri Feb 29 04:46:42 2008 Subject: Re: [CentOS] error creating Centos 5.1 x32 dum_U

Nah, RHEL 5.1+ supports 32-bit domU (PAE and non PAE) on 64-bit dom0. Actually RHEL Xen is 3.1 with the brain damaged 3.0 userland utilities. -Ross ----- Original Message ----- From: centos-bounces at centos.org <centos-bounces at centos.org> To: CentOS mailing list <centos at centos.org> Sent: Fri Feb 29 04:46:42 2008 Subject: Re: [CentOS] error creating Centos 5.1 x32 dum_U

On Jun 15, 2016, at 10:46 AM, Tanstaafl <tanstaafl at libertytrek.org> wrote: > On 6/15/2016 12:30 PM, @lbutlr <kremels at kreme.com> wrote: >> On Jun 15, 2016, at 9:44 AM, Tanstaafl <tanstaafl at libertytrek.org> wrote: >>> On 6/14/2016 6:50 PM, @lbutlr <kremels at kreme.com> wrote: >>>> Where exactly does dovecot get the date that it reports

I'm a beginner to libvirt and creating VMs, for that matter. I have a set of specifications for VMs I need to create and log into, but I have to create them on an Ubuntu box that I only have ssh access to. I won't have desktop GUI access, although I do have dynamic port forwarding, so I can access a browser GUI from my desktop. Reading through the libvirt info, I see numerous mentions

OK, I obviously forgot something when setting up new user accounts (which I did via postfix admin to add them to the MySQL database): dovecot: lda(chance at example.com): Error: User initialization failed: Namespace '': Ambiguous mail location setting, don't know what to do with it: /usr/local/virtual/chance@ example.com (try prefixing it with mbox: or milder:) I have lots of mysql