I disabled dnssec validation, and after a few days with a number of
reboots and restarts of bind9, I haven't had any further trouble with
stopping the bind9 service or with shutting down my system. So I'm
pretty sure at this point that there's some bug with dnssec validation
that intermittent
This looks like the bug I want to report. I find that shutting down bind9 is
erratic: sometimes it succeeds, sometimes not. This is a common result of
shutting it down at the command line:
codebrian@$ sudo service bind9 stop
* Stopping domain name service... bind9
rndc: connect failed:
@Soren -- Actually, you did help, as I didn't know where to look for
troubleshooting information before your prompting. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
I'm attaching the xml files for server1.example.com and
tester1.example.com, which I used when generating the error messages
above. I have some other VMs defined, and I find that while I can start
any one, any second one fails to start with the same error messages.
** Attachment added:
** Attachment added: tester1.example.com.xml
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+attachment/2425790/+files/tester1.example.com.xml
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
I am uploading the output from 'virsh dumpxml' for each domain. However,
the output is identical to what I already posted.
** Attachment added: server1.example.com.xml
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+attachment/2426894/+files/server1.example.com.xml
--
You
** Attachment added: tester1.example.com.xml
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+attachment/2426895/+files/tester1.example.com.xml
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
That didn't seem to work. Should it have been testing for package
libvirt-bin, rather than for libvirt? I got this:
Waiting to hear from Launchpad about your decision...
Package libvirt not installed and no hook available, ignoring
brian@brian-desktop:~$ sudo aptitude show libvirt
[sudo] password
Those were the files I uploaded the first time. In what way are they
corrupt? I can display them from Launchpad.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/853580
Title:
Unable
They're definitely xml files, and are rendered as such when I click on
the links to the files I've already uploaded. I'll copy-and-paste them
here:
server1.example.com:
domain type='kvm'
nameserver1.example.com/name
uuidfb2d017b-f9cc-7534-126c-ffdd369c745f/uuid
memory1048576/memory
/var/log/libvirt/libvirtd.log does not exist. However, there are log
files for each domain, in /var/log/libvirt/qemu which look to be handled
by logrotate. server1.example.com.log and tester1.example.com.log are 0
length, so I am attaching server1.example.com.log.1 and
tester1.example.com.log.1.
** Attachment added: tester1.example.com.log.1
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/853580/+attachment/2428847/+files/tester1.example.com.log.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
From a quick look at the logs, it looks like the domains I usually
started second kept trying to bind to vnc on port 5900, which presumably
was already claimed by the first domain. I only set the port during
initial installation, so I'm not sure why it doesn't just try port 5901.
--
You received
That was it. Each domain xml file had this line:
graphics type 'vnc' port='5900' autoport='no'/
using edit [domain name] in virsh, I changed the line in each to:
graphics type='vnc' autoport='yes'/
With that, they both started without complaint.
The remaining question is why the
Public bug reported:
Ubuntu 11.04
libvirt-bin 0.8.8-1ubuntu6.5
Whether using virt-manager or virsh, I am unable to start a second
virtual machine while one is already running.
Through virt-manager, I get this:
Error starting domain: operation failed: failed to retrieve chardev info
in qemu
15 matches
Mail list logo
