Is there a spot in the xml i'm not seeing to identify the network DNS server.
Currently it's defaulting to a.b.c.1 I'm running my own though on a different
address and can't find where to configure it in the xml schema or could I
override it in DNSMASQ?
Thanks
Steve
__
Subject line says it all. Every time I restart a network libvirt inserts its
standard rules at the head of the ip forward chain. The deny lines in there
clobber access to my servers. Is there any way to make it append those rules
at a specific number or at the end by default?
Many Thanks,
Stev
Hi,
I'm trying to use blockpeek to open the contents of a file. Inside the vm i
ran debugfs: imap /test/findme and got: inode 32642 is part of block group 4
located at block 131074, offset 0x0100
I try using 0x100 or 256 as the offset to blockpeek into that VM and get
nonsense as a resul
I think so, but I'm locked out at home. I'll have to try at school tomorrow.
It gave me a remote error, but with the correct directory so fingers crossed
thanks!
btw might you or anyone know what I have to include to start a clean project of
my own? So if I want to just build an application
Trying to build the hellolibvirt example. I get the project to compile okay
but when I try to run it I get:
Unable to connect to '/usr/local/var/run/libvirt/libivrt-sock
Given libvirt --status says it's in /var/run/libvirt/libvirt-sock that makes
sense. How do I make the git version run with
Hi,
I just tried x=dom.blockPeek('disk',5,0,buf,0) and it returns
AtrributeError: 'module' object has no attribute 'virDomainBlockPeek'
I found this bug submission from early 09:
https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=492683
Is that still correct are they not implemente
So I just upgraded to 0.8.1-1 and virt-manager 8.4 when i try to attach my
network card that's been perfectly fine in the past i now get...
virsh # attach-device gnome /etc/libvirt/qemu/nic.xml
error: Failed to attach device from /etc/libvirt/qemu/nic.xml
error: internal error unable to send TAP
Hi Everyone,
After upgrading FC12 and now FC13 whenever I try to attach a network device
using attach-device it promptly crashes libvirtd. Is there an option that
changed in the network interface xml spec I missed?
I really need this feature or at least the ability to connect and disconnec
Hi,
Just installed a new FC12 box with all new updates. Figured out to delete
the CDROM so the images actually boot now.
However, after the upgrade, I can no longer attach my network interfaces to
running images? Was this capability removed? Is there some new setting that
has to be con
Working with the two commands there's a noticeable difference in the time
redhat takes to detect interfaces using attach-interface vs attach-device?
About 5-8 seconds using attach interface, and near instant with attach-device.
That little bit aside, I'm trying to find a way to 'unplug' a VM wi
Thanks, but problem still persists. I actually fat fingered entering it the
first time
The xmlfile really is:
I ran xmllint and it just says no DTD specified, however this works perfectly
if i use the attach-device command in virsh. I tired it both with and without
the first
I keep getting an error when I try to attach a device in the libvirt api
through python
The python code is:
conn=libvirt.open('qemu:///system')
dom = conn.lookupByName("fedoratest")
if dom.info()[0]==1:
dom.attachDevice('net.xml')
And I keep getting: "libvirtError: XML
12 matches
Mail list logo