[libvirt] Permissions and ownership on /dev/kvm keep reverting after starting a vm
Hey guys, /dev/kvm permissions and ownership keeps reverting after starting a vm. The ownership and permissions keep going back to crw-rw—— root root After starting a vm. I have to revert the perms and ownership to: crw-crw-crw root kvm To start any vm but it goes back to the first set of permissions as soon as I start another vm. Any hints what I could check? Cheers, Tom Sent from my iPhone -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH] lxc: Add virCgroupSetOwner()
Am 14.02.2014 13:42, schrieb Stephan Sachse: set LogLevel to DEBUG3. keyexchange is down. put then hangs for some time und sshd dies sshd[269]: debug1: KEX done [preauth] sshd[269]: debug1: userauth-request for user root service ssh-connection method none [preauth] sshd[269]: debug1: attempt 0 failures 0 [preauth] sshd[269]: debug3: mm_getpwnamallow entering [preauth] sshd[269]: debug3: mm_request_send entering: type 8 [preauth] sshd[269]: debug3: mm_getpwnamallow: waiting for MONITOR_ANS_PWNAM [preauth] sshd[269]: debug3: mm_request_receive_expect entering: type 9 [preauth] sshd[269]: debug3: mm_request_receive entering [preauth] sshd[269]: debug3: mm_request_receive entering sshd[269]: debug3: monitor_read: checking request 8 sshd[269]: debug3: mm_answer_pwnamallow sshd[269]: debug3: Trying to reverse map address 10.1.25.151. systemd[1]: Received SIGCHLD from PID 270 (sshd). systemd[1]: Got SIGCHLD for process 270 (sshd) systemd[1]: Child 270 died (code=killed, status=15/TERM) Also keep in mind that running a compete distro within LXC + user namespaces requires some changes. Like disabling pam_loginuid.so in pam. For systemd distros you have to remove OOMScoreAdjust= and CapabilityBoundingSet= from all units... yes, i know. i have no errors from systemd, all looks fine with exec /sbin/init systemd.log_level=debug /stephan I have the same problem on a slightly different setup. Both host and guest are Archlinux with systemd-208, libvirt-git with the chown() patches. LXC Console login works fine (and I do not have such issues with messed up console), but login via SSH fails with the exact same symptoms. ~tom -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH] lxc: Add virCgroupSetOwner()
Am 14.02.2014 14:17, schrieb Tom Kuther: Am 14.02.2014 13:42, schrieb Stephan Sachse: set LogLevel to DEBUG3. keyexchange is down. put then hangs for some time und sshd dies sshd[269]: debug1: KEX done [preauth] sshd[269]: debug1: userauth-request for user root service ssh-connection method none [preauth] sshd[269]: debug1: attempt 0 failures 0 [preauth] sshd[269]: debug3: mm_getpwnamallow entering [preauth] sshd[269]: debug3: mm_request_send entering: type 8 [preauth] sshd[269]: debug3: mm_getpwnamallow: waiting for MONITOR_ANS_PWNAM [preauth] sshd[269]: debug3: mm_request_receive_expect entering: type 9 [preauth] sshd[269]: debug3: mm_request_receive entering [preauth] sshd[269]: debug3: mm_request_receive entering sshd[269]: debug3: monitor_read: checking request 8 sshd[269]: debug3: mm_answer_pwnamallow sshd[269]: debug3: Trying to reverse map address 10.1.25.151. systemd[1]: Received SIGCHLD from PID 270 (sshd). systemd[1]: Got SIGCHLD for process 270 (sshd) systemd[1]: Child 270 died (code=killed, status=15/TERM) Also keep in mind that running a compete distro within LXC + user namespaces requires some changes. Like disabling pam_loginuid.so in pam. For systemd distros you have to remove OOMScoreAdjust= and CapabilityBoundingSet= from all units... yes, i know. i have no errors from systemd, all looks fine with exec /sbin/init systemd.log_level=debug /stephan I have the same problem on a slightly different setup. Both host and guest are Archlinux with systemd-208, libvirt-git with the chown() patches. LXC Console login works fine (and I do not have such issues with messed up console), but login via SSH fails with the exact same symptoms. ~tom Setting UseDNS=no in the container's sshd_config fixes this. I have no idea why that happens. DNS lookups generally do work in the container. ~tom -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH] lxc: Add virCgroupSetOwner()
Am 14.02.2014 14:32, schrieb Daniel P. Berrange: On Fri, Feb 14, 2014 at 02:17:24PM +0100, Tom Kuther wrote: Am 14.02.2014 13:42, schrieb Stephan Sachse: set LogLevel to DEBUG3. keyexchange is down. put then hangs for some time und sshd dies sshd[269]: debug1: KEX done [preauth] sshd[269]: debug1: userauth-request for user root service ssh-connection method none [preauth] sshd[269]: debug1: attempt 0 failures 0 [preauth] sshd[269]: debug3: mm_getpwnamallow entering [preauth] sshd[269]: debug3: mm_request_send entering: type 8 [preauth] sshd[269]: debug3: mm_getpwnamallow: waiting for MONITOR_ANS_PWNAM [preauth] sshd[269]: debug3: mm_request_receive_expect entering: type 9 [preauth] sshd[269]: debug3: mm_request_receive entering [preauth] sshd[269]: debug3: mm_request_receive entering sshd[269]: debug3: monitor_read: checking request 8 sshd[269]: debug3: mm_answer_pwnamallow sshd[269]: debug3: Trying to reverse map address 10.1.25.151. systemd[1]: Received SIGCHLD from PID 270 (sshd). systemd[1]: Got SIGCHLD for process 270 (sshd) systemd[1]: Child 270 died (code=killed, status=15/TERM) Also keep in mind that running a compete distro within LXC + user namespaces requires some changes. Like disabling pam_loginuid.so in pam. For systemd distros you have to remove OOMScoreAdjust= and CapabilityBoundingSet= from all units... yes, i know. i have no errors from systemd, all looks fine with exec /sbin/init systemd.log_level=debug /stephan I have the same problem on a slightly different setup. Both host and guest are Archlinux with systemd-208, libvirt-git with the chown() patches. LXC Console login works fine (and I do not have such issues with messed up console), but login via SSH fails with the exact same symptoms. Most likely is the pam_loginuid module denying access. Sadly I find debugging PAM a complete pain - if anyone knows how to make it spew logs for each module executed and then accept/reject state, that'd be awesome for troubleshooting this. Daniel I have that disabled. As I wrote in the other mail, it seems to be a funny DNS lookup problem. Setting UseDNS=no in sshd_config fixes it. But there is a more general problem with local LAN DNS lookup. I do have set the router's DNS server in /etc/resolv.conf, yet I cannot reach any clients on the LAN using their lan hostname.domainname - this works fine when not using user namespace. Using their IP works, Internet DNS lookup works, too. Interface type for the container is bridge via the hosts's br0. No idea if this could be a libvirt, kernel or systemd problem. ~tom -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] 0.10.2 virtualport profileid (802.1Qbh) malformed
Hi, I've just upgraded a test libvirtd host to 0.10.2 from 0.9.4 to be able to make use of the new 'virsh net-update add portgroup' live updates, however can't get my private/802.1Qbh interfaces working at all after the upgrade. Trying to start an existing domain or install a new domain after the upgrade gives: ERROR internal error corrupted profileid string and a corresponding error in the libvirtd log: error : virNetDevVPortProfileMerge:381 : internal error corrupted profileid string I've tried all sorts of profileid combinations and tried defining the virtualport in the domain instead of in the network, to no avail. The source indicates this is to do with a malformed (not null terminated) profile id when merging the port profile. Why would this be happening? Any hints how to debug it? My example network definition: network nametestnet/name uuid76d32a2d-8433-6873-9c15-cdae30e7a632/uuid forward dev='eth1' mode='private' interface dev='eth1'/ interface dev='eth2'/ interface dev='eth3'/ ... /forward portgroup name='server1' default='yes' virtualport type='802.1Qbh' parameters profileid='profile-server1'/ /virtualport /portgroup portgroup name='server2' virtualport type='802.1Qbh' parameters profileid='profile-server2'/ /virtualport /portgroup portgroup name='server3' virtualport type='802.1Qbh' parameters profileid='profile-server3'/ /virtualport /portgroup /network and a domain definition which throws an error on start-up: interface type='network' mac address='52:54:00:d1:94:5f'/ source network='testnet' portgroup='server1'/ model type='virtio'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface Tom -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] Patch for verbose Disk transfer
A virsh command like:
migrate --live --copy-storage-all Guest qemu+ssh://user@host/system
--persistent --verbose
shows
Migration: [ 0 %]
during the storage copy and does not start counting
untill the ram transfer starts
Patch for including the storage copy:
diff --git a/src/qemu/qemu_monitor_text.c b/src/qemu/qemu_monitor_text.c
index 7bf733d..4ac8008 100644
--- a/src/qemu/qemu_monitor_text.c
+++ b/src/qemu/qemu_monitor_text.c
@@ -1183,6 +1183,9 @@ cleanup:
#define MIGRATION_TRANSFER_PREFIX transferred ram:
#define MIGRATION_REMAINING_PREFIX remaining ram:
#define MIGRATION_TOTAL_PREFIX total ram:
+#define MIGRATION_DISK_TRANSFER_PREFIX transferred disk:
+#define MIGRATION_DISK_REMAINING_PREFIX remaining disk:
+#define MIGRATION_DISK_TOTAL_PREFIX total disk:
int qemuMonitorTextGetMigrationStatus(qemuMonitorPtr mon,
int *status,
@@ -1246,6 +1249,7 @@ int qemuMonitorTextGetMigrationStatus(qemuMonitorPtr mon,
goto cleanup;
}
*remaining *= 1024;
+tmp = end;
if (!(tmp = strstr(tmp, MIGRATION_TOTAL_PREFIX)))
goto done;
@@ -1257,7 +1261,53 @@ int qemuMonitorTextGetMigrationStatus(qemuMonitorPtr mon,
goto cleanup;
}
*total *= 1024;
+tmp = end;
+
+/*
+ * Check for Optional Disk Migration status
+ */
+
+unsigned long long disk_transferred= 0;
+unsigned long long disk_remaining= 0;
+unsigned long long disk_total= 0;
+
+if (!(tmp = strstr(tmp, MIGRATION_DISK_TRANSFER_PREFIX)))
+goto done;
+tmp += strlen(MIGRATION_DISK_TRANSFER_PREFIX);
+if (virStrToLong_ull(tmp, end, 10, disk_transferred) 0) {
+qemuReportError(VIR_ERR_INTERNAL_ERROR,
+_(cannot parse disk migration data
transferred statistic %s), tmp);
+goto cleanup;
+}
+disk_transferred *= 1024;
+(*transferred)+= disk_transferred;
+tmp = end;
+
+if (!(tmp = strstr(tmp, MIGRATION_DISK_REMAINING_PREFIX)))
+goto done;
+tmp += strlen(MIGRATION_DISK_REMAINING_PREFIX);
+
+if (virStrToLong_ull(tmp, end, 10, disk_remaining) 0) {
+qemuReportError(VIR_ERR_INTERNAL_ERROR,
+_(cannot parse disk migration data
remaining statistic %s), tmp);
+goto cleanup;
+}
+disk_remaining *= 1024;
+(*remaining)+= disk_remaining;
+tmp = end;
+
+if (!(tmp = strstr(tmp, MIGRATION_DISK_TOTAL_PREFIX)))
+goto done;
+tmp += strlen(MIGRATION_DISK_TOTAL_PREFIX);
+
+if (virStrToLong_ull(tmp, end, 10, disk_total) 0) {
+qemuReportError(VIR_ERR_INTERNAL_ERROR,
+_(cannot parse disk migration data
total statistic %s), tmp);
+goto cleanup;
+}
+disk_total *= 1024;
+(*total)+= disk_total;
}
}
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] libvirt 0.7.5 vs qemu 0.12.1 imcompatability?
On 06/01/10 18:56, Nikola Ciprich wrote: I've had similar trouble with old bios images. Once I replaced them with those built with qemu-kvm, things started working... I've using the packages from virt-preview so I've got whatever BIOS images are being packaged. I've experimented some more now and even a simple: qemu-kvm -enable-kvm just gives me nothing whereas the older version brings up the BIOS screen. Actually looking at it, the BIOS is a separate package which doesn't exist in the virt-preview repository so I'm still using the normal Fedora one. Maybe that's the problem? What's the best channel for reporting issues with the virt-preview packages? Tom -- Tom Hughes (t...@compton.nu) http://www.compton.nu/ -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] libvirt 0.7.5 vs qemu 0.12.1 imcompatability?
The update from qemu 0.11.0 to qemu 0.12.1 in the virt-preview repository seems to have broken things. Starting a VM now just gives me a blank screen and a log which says: Option 'ipv4': Use 'on' or 'off' Failed to parse yes for dummy.ipv4 I assume libvirt is sending a it a command on the monitor interface that it no longer understands... Tom -- Tom Hughes (t...@compton.nu) http://www.compton.nu/ -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] libvirt 0.7.5 vs qemu 0.12.1 imcompatability?
On 06/01/10 15:53, Daniel P. Berrange wrote: On Wed, Jan 06, 2010 at 03:38:29PM +, Tom Hughes wrote: The update from qemu 0.11.0 to qemu 0.12.1 in the virt-preview repository seems to have broken things. Starting a VM now just gives me a blank screen and a log which says: Option 'ipv4': Use 'on' or 'off' Failed to parse yes for dummy.ipv4 I assume libvirt is sending a it a command on the monitor interface that it no longer understands... That warning message should be harmless - all my VMs show that and they work ok. It is not actually something libirt sets - its a internal QEMU default setting which is wrong Hmm... Well something is wrong because I just get a black screen. I don't even get the BIOS messages since I updated this morning. Downgrading back to the fedora-updates version of qemu makes it work again. BTW the trigger for that warning seems to be that I have listen='0.0.0.0' set on the vnc adaptor to allow connections from remote machines, which causes libvirt to build a qemu command line with -vnc 0.0.0.0:0. Tom -- Tom Hughes (t...@compton.nu) http://www.compton.nu/ -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] libvirt 0.7.5 vs qemu 0.12.1 imcompatability?
On 06/01/10 17:32, Thomas Treutner wrote: On Wednesday 06 January 2010 17:11:17 Tom Hughes wrote: Hmm... Well something is wrong because I just get a black screen. I don't even get the BIOS messages since I updated this morning. If you start your VM with -kernel $image, there's a bug in qemu-0.12.1(.1?), which is fixed in 0.12.1.2. It's a windows VM, so no. The qemu command libvirt is using is: /usr/bin/qemu-kvm -S -M pc-0.11 -enable-kvm -m 1024 -smp 2 -name windows_xp_64 -uuid bb4c089d-1a5e-b349-07fe-4098efdf5fe0 -monitor unix:/var/lib/libvirt/qemu/windows_xp_64.monitor,server,nowait -localtime -boot c -drive file=/var/lib/libvirt/images/windows_xp_64.img,if=virtio,index=0,boot=on -drive if=ide,media=cdrom,index=2 -net nic,macaddr=00:16:3e:12:4a:56,vlan=0,model=virtio,name=virtio.0 -net tap,fd=27,vlan=0,name=tap.0 -serial pty -parallel none -usb -usbdevice tablet -vnc 0.0.0.0:0 -k en-gb -vga std -soundhw es1370 That said, I've tried stripping most of that out and still get nothing so I think something more fundamental is wrong. Tom -- Tom Hughes (t...@compton.nu) http://www.compton.nu/ -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
gPXE (was Re: [libvirt] [RFC,PATCH] network: add 'netboot' option to dhcp config)
I very much like this idea - e.g. I'd really like to have this to give people simple instructions for testing gPXE in next week's Fedora Test Day. On the subject of gPXE has anybody else found that it doesn't seem to be working at all? I'm using the virt-preview packages on F11 and ever since qemu switched to use gPXE network booting has been completely broken. I get the gPXE banner message appear and then nothing happens. Monitoring the network shows no signs of any DHCP requests being sent at all. Tom -- Tom Hughes (t...@compton.nu) http://www.compton.nu/ -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Re: [fedora-virt] ANNOUNCE: New release virt-manager 0.8.0
On 29/07/09 11:21, Ján ONDREJ (SAL) wrote: And one thing, which can make me happy. When I am trying virtual machines, I often reinstall existing one. Then I need to boot from network and after installation again from disk. I can't test new gPXE until it will work with my F11 kernel, may be it's better with this, but with currently functional bootrom I can't boot from disk if network boot is enabled and vice versa. If my guest is set to boot from disk (after previous installation) and I need to reinstall it, I have to do these steps: - click details panel (i) - click Boot Options - click on Boot Device menu - select Network (PXE) and confirm (click) - click Apply - click back to guest console - click start (play button) That's not a virt-manager issue, it's a qemu issue I assume. It works for me though - if I have network boot selected that I can bring up the boot menu with F12 and select the hard disk instead? What I suspect you may be referring to is the fact that if you don't have network boot set as the default then the F12 boot menu doesn't include the network option - so you can't be set to boot from the hard disk by default and then choose to boot from network instead using the boot menu. I too find that rather annoying, but as I say it is (I believe) a qemu issue rather than a libvirt issue. Tom -- Tom Hughes (t...@compton.nu) http://www.compton.nu/ -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] VMware support and libcurl on rhel-u1
On 27/07/09 06:17, Shahar Klein wrote: I'll try with 7.15 can I test with ESX4i? ESX4i doesn't seem to work yet - the API version has changed: error: internal error Expecting VI API version '2.5.0' or '2.5u2' but found '4.0' Patching libvirt to allow the 4.0 API version allows me to connect and list guests, but trying to dumpxml a guest definition fails: virsh # dumpxml alvis error: memory conf:1: expecting a name Then again dumpxml fails for me with ESX3i as well, though with a different error: virsh # dumpxml bsa error: internal error Missing essential config entry 'scsi0.virtualDev' Tom -- Tom Hughes (t...@compton.nu) http://www.compton.nu/ -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] VMware support and libcurl on rhel-u1
On 27/07/09 09:38, Shahar Klein wrote: How do you connect to the esxi? Over https. Should I open an ssh in my ESXi server? [r...@rain8 libvirt]# virsh -c esx+ssh://rain3/system error: cannot recv data: Connection reset by peer error: failed to connect to the hypervisor I just use virsh -c esx://r...@server and it connects over https by default. I did have to hack the code to stop curl trying to validate the self signed cert on the server. Tom -- Tom Hughes (t...@compton.nu) http://www.compton.nu/ -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] VMware support and libcurl on rhel-u1
On 27/07/09 09:19, Matthias Bolte wrote: 2009/7/27 Tom Hughest...@compton.nu: Patching libvirt to allow the 4.0 API version allows me to connect and list guests, but trying to dumpxml a guest definition fails: virsh # dumpxml alvis error: memory conf:1: expecting a name What's the content of line number 1 of the alvis.vmx file? The first two lines are: .encoding = UTF-8 config.version = 8 Looking at an ESX3i one I see the .encoding line is not there so I guess that is the problem. Then again dumpxml fails for me with ESX3i as well, though with a different error: virsh # dumpxml bsa error: internal error Missing essential config entry 'scsi0.virtualDev' Oh, that's a bug in the VMX parsing code, I'll fix that. The VMX parsing hasn't get much testing with in-the-wild VMX files yet. It would be useful if you could send my some of your VMX files to build up a pool as input for automatic testing and to make the VMX parser more robust. You could apply this quick fix for testing: That works, yes. Tom -- Tom Hughes (t...@compton.nu) http://www.compton.nu/ -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] VMware support and libcurl on rhel-u1
On 27/07/09 11:00, Matthias Bolte wrote: I assume you set CURLOPT_SSL_VERIFYPEER to 0. Good idea I'll add that in they way the no_verify query parameter work for libvirtd based transports. That's the one, yes. Tom -- Tom Hughes (t...@compton.nu) http://www.compton.nu/ -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] VMware ESX: Allow leading dots in VMX config entry names
On 27/07/09 12:25, Matthias Bolte wrote: '.encoding = UTF-8' is a valid VMX config entry, so the virConfParser must accept it in VMX mode. This patch lets the parser accept those names with leading dots. With that patch ESX4i gets a bit further but barfs on a version check: error: internal error Expecting VMX entry 'virtualHW.version' to be 4 but found 7 Tom -- Tom Hughes (t...@compton.nu) http://www.compton.nu/ -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] VMware ESX: Allow leading dots in VMX config entry names
On 27/07/09 13:28, Matthias Bolte wrote: It seems that I should setup an ESXi 4 just in case there are more differences between version 3.5 and 4.0. See the other patch regarding VI API 4.0, that one should fix the virtualHW.version problem and make the version checking more robust. Latest git code is now able to connect to 4i, list domains, and dumpxml their definitions. Tom -- Tom Hughes (t...@compton.nu) http://www.compton.nu/ -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] PATCH: Video device config
On 08/07/09 12:21, Daniel Veillard wrote: On Tue, Jul 07, 2009 at 10:17:18PM +0100, Tom Hughes wrote: The updated patch is attached, and based on the list of outstanding tasks given before what remains to be done is: Upon rereading that patch it seems that Dan's version is a superset, am I missing something ? The new patch he posted last night is, yes. The one I was working from wasn't - that was this one: http://www.mail-archive.com/libvir-list@redhat.com/msg13520.html Tom -- Tom Hughes (t...@compton.nu) http://www.compton.nu/ -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] PATCH: Video device config
I recently posted a patch on the RedHat bugzilla (bug #467038) to add a
model attribute to the graphics element so that the different graphics
cards supported by QEMU could be selected.
Apparently that approach has been rejected in the past however, and the
preferred approach is to add a separate video element.
I've taken the patch that Daniel Berrange posted here a few months ago
that added the necessary XML handling for the new element and extended
it by filling in the QEMU driver code to make it use the model details
as well as fixing the default video model for XEN domains as per the
list of outstanding issues given with the original patch.
The updated patch is attached, and based on the list of outstanding
tasks given before what remains to be done is:
- Add RNG XML schemas website docs
- Make Xen drivers use this info for setting stdvga=1|0 config arg
- Make VirtualBox use this info in whatever way it needs
Tom
--
Tom Hughes (t...@compton.nu)
http://www.compton.nu/
diff --git a/src/domain_conf.c b/src/domain_conf.c
index ffa2aef..0f1f249 100644
--- a/src/domain_conf.c
+++ b/src/domain_conf.c
@@ -82,6 +82,7 @@ VIR_ENUM_IMPL(virDomainDevice, VIR_DOMAIN_DEVICE_LAST,
interface,
input,
sound,
+ video,
hostdev)
VIR_ENUM_IMPL(virDomainDisk, VIR_DOMAIN_DISK_TYPE_LAST,
@@ -142,6 +143,12 @@ VIR_ENUM_IMPL(virDomainSoundModel,
VIR_DOMAIN_SOUND_MODEL_LAST,
pcspk,
ac97)
+VIR_ENUM_IMPL(virDomainVideo, VIR_DOMAIN_VIDEO_TYPE_LAST,
+ vga,
+ cirrus,
+ vmvga,
+ xen)
+
VIR_ENUM_IMPL(virDomainInput, VIR_DOMAIN_INPUT_TYPE_LAST,
mouse,
tablet)
@@ -374,6 +381,14 @@ void virDomainSoundDefFree(virDomainSoundDefPtr def)
VIR_FREE(def);
}
+void virDomainVideoDefFree(virDomainVideoDefPtr def)
+{
+if (!def)
+return;
+
+VIR_FREE(def);
+}
+
void virDomainHostdevDefFree(virDomainHostdevDefPtr def)
{
if (!def)
@@ -401,6 +416,9 @@ void virDomainDeviceDefFree(virDomainDeviceDefPtr def)
case VIR_DOMAIN_DEVICE_SOUND:
virDomainSoundDefFree(def-data.sound);
break;
+case VIR_DOMAIN_DEVICE_VIDEO:
+virDomainVideoDefFree(def-data.video);
+break;
case VIR_DOMAIN_DEVICE_HOSTDEV:
virDomainHostdevDefFree(def-data.hostdev);
break;
@@ -458,6 +476,10 @@ void virDomainDefFree(virDomainDefPtr def)
virDomainSoundDefFree(def-sounds[i]);
VIR_FREE(def-sounds);
+for (i = 0 ; i def-nvideos ; i++)
+virDomainVideoDefFree(def-videos[i]);
+VIR_FREE(def-videos);
+
for (i = 0 ; i def-nhostdevs ; i++)
virDomainHostdevDefFree(def-hostdevs[i]);
VIR_FREE(def-hostdevs);
@@ -1653,6 +1675,84 @@ error:
goto cleanup;
}
+static virDomainVideoDefPtr
+virDomainVideoDefParseXML(virConnectPtr conn,
+ const xmlNodePtr node,
+ int flags ATTRIBUTE_UNUSED) {
+virDomainVideoDefPtr def;
+xmlNodePtr cur;
+char *type = NULL;
+char *heads = NULL;
+char *vram = NULL;
+
+if (VIR_ALLOC(def) 0) {
+virReportOOMError(conn);
+return NULL;
+}
+
+cur = node-children;
+while (cur != NULL) {
+if (cur-type == XML_ELEMENT_NODE) {
+if ((type == NULL) (vram == NULL) (heads == NULL)
+xmlStrEqual(cur-name, BAD_CAST model)) {
+type = virXMLPropString(cur, type);
+vram = virXMLPropString(cur, vram);
+heads = virXMLPropString(cur, heads);
+}
+}
+cur = cur-next;
+}
+
+if (type
+(def-type = virDomainVideoTypeFromString(type)) 0) {
+virDomainReportError(conn, VIR_ERR_INTERNAL_ERROR,
+ _(unknown video model '%s'), type);
+goto error;
+}
+
+if (vram
+virStrToLong_ui(vram, NULL, 10, def-vram) 0) {
+virDomainReportError(conn, VIR_ERR_INTERNAL_ERROR,
+ _(cannot parse video ram '%s'), vram);
+goto error;
+} else {
+switch (def-type) {
+/* Wierd, QEMU defaults to 9 MB ??! */
+case VIR_DOMAIN_VIDEO_TYPE_VGA:
+case VIR_DOMAIN_VIDEO_TYPE_CIRRUS:
+case VIR_DOMAIN_VIDEO_TYPE_VMVGA:
+def-vram = 9 * 1024;
+break;
+case VIR_DOMAIN_VIDEO_TYPE_XEN:
+/* Original PVFB hardcoded to 4 MB */
+def-vram = 4 * 1024;
+break;
+}
+}
+
+if (heads
+virStrToLong_ui(heads, NULL, 10, def-heads) 0) {
+virDomainReportError(conn, VIR_ERR_INTERNAL_ERROR,
+ _(cannot parse video heads '%s'), heads);
+goto error;
+} else {
+def-heads = 1;
+}
+
+VIR_FREE(type);
+VIR_FREE(vram);
+VIR_FREE(heads);
+
+return def;
+
+error
Re: [libvirt] RE: Libvirt - Xen Enterprise - Koan
Daniel Veillard wrote: Well the public XenAPI list seems mostly dead but there are reports of incompatibilities between their proprietary and old open sounce versions. Check the archives, it doesn't look good. nope - not good at all - and the really annoying thing is that its quite likely that in 6months from now we'd not be using XenEnterprise but in the meantime i have to try to come up with something that just works. Alas it seems thats not going to be possible. -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] RE: Libvirt - Xen Enterprise - Koan
We should really as customers demand better integration/support. I have started enquiring about this but am not too hopefull about my requests being heard/listened to. Quite true - as from my POV forcing the customer to use a single product for provisioning as well as virtualization makes that product less desirable. I dont want to feel locked in. -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] RE: Libvirt - Xen Enterprise - Koan
I have managed to make some noise with our supplier... if there is any positive results I will let you know. that would be great thanks -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Libvirt - Xen Enterprise - Koan
I've not tried it, but the likely problem is that you'll need to turn on XenD's UNIX server config option in /etc/xen/xend-config.sxp http://libvirt.org/drvxen.html Thanks for this - this sounds like the most likely issue. The problem is that Citrix seems to move things around somewhat as that config file does not exist. There is a xensource directory that contains the following but other than that i am a bit stuck. # ll /etc/xensource total 72 -rw-r--r-- 1 root root 1956 Dec 31 11:22 boot_time_cpus -rw--- 1 root root 11 Dec 31 11:22 boot_time_memory -rwxr-xr-x 1 root root 71 Sep 4 13:46 db.conf -rwxr-xr-x 1 root root 74 Sep 4 13:46 db.conf.rio -rw-r--r-- 1 root root 655 Sep 4 13:46 db-default-fields -rw-r--r-- 1 root root 8660 Sep 4 13:46 db_schema.sql -rw--- 1 root root 653 Dec 31 11:18 license -rwxr-xr-x 1 root root 776 Sep 4 13:46 log.conf drwxr-xr-x 2 root root 4096 Aug 29 20:11 master.d -rwxr-xr-x 1 root root6 Sep 4 13:46 pool.conf -rw--- 1 root root 110 Dec 30 17:52 ptoken drwxr-xr-x 2 root root 4096 Sep 4 13:46 scripts -rwxr-xr-x 1 root root 199 Sep 4 13:46 xapi.conf -rwxr-xr-x 1 root root 172 Sep 4 13:46 xapi-ssl.conf -r 1 root root 1286 Dec 30 17:52 xapi-ssl.pem -rwxr-xr-x 1 root root9 Sep 4 13:46 xsdata_allowed_prefix thanks -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] RE: Libvirt - Xen Enterprise - Koan
Daniel P. Berrange wrote: On Tue, Jan 06, 2009 at 11:57:34AM -, gerhardus.geldenh...@gta-travel.com wrote: No it does not use xend. # ps auxwww | grep xen root21 0.0 0.0 0 0 ?S2008 0:00 [xenwatch] root22 0.0 0.0 0 0 ?S2008 0:00 [xenbus] root 5240 0.0 0.1 2076 908 ?S 2008 0:00 /usr/sbin/xenstored root 5243 0.0 0.0 12232 532 ?Sl2008 0:00 /usr/sbin/xenconsoled root 5254 0.0 0.0 2608 444 ?S 2008 0:00 /opt/xensource/libexec/cdrommon /dev/xapi/cd/hda root 5269 0.0 0.4 19156 3800 ?S2008 0:00 /opt/xensource/bin/xapi -daemon -writereadyfile /var/run/xapi_startup.cookie -writeinitcomplete /var/run/xapi_init_complete.cookie -onsystemboot root 5271 0.0 1.3 178612 10056 ?Sl 2008 1:00 /opt/xensource/bin/xapi -daemon -writereadyfile /var/run/xapi_startup.cookie -writeinitcomplete /var/run/xapi_init_complete.cookie -onsystemboot root 5561 0.0 0.4 21580 3720 ?Sl2008 0:00 python /opt/xensource/sm/snapwatchd/snapwatchd -d /var/log/SMlog root 6181 0.0 0.7 12380 5592 ?Ss2008 1:19 python /opt/xensource/bin/perfmon --daemon root 6405 0.0 0.1 4756 1524 ?Ss2008 0:00 /usr/lib/xen/bin/vncterm -v 127.0.0.1 -r -x /local/domain/0/serial/0 -c /usr/lib/xen/bin/dom0term.sh root 10301 0.0 0.1 2424 1024 pts/0Ss+ Jan05 0:00 /bin/bash /usr/lib/xen/bin/dom0term.sh That's pretty much game over then. Someone will have to write a new libvirt driver specifically for XenEnterprise to get it to work. damn - that really scuppers me trying to forge ahead with the cobbler route as XenEnterprise will be around here for a while much to my annoyance. Is that really it ? -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] Libvirt - Xen Enterprise - Koan
Hi Our VM's currently run on top of Xen Enterprise, not my choice but thats the way it has to be at the moment. I'd like to be able to still use cobbler/koan to provision the systems and so i have managed to get libvirt installed onto a Xen Enterprise host. Libvirt starts but it cant connect to Xend as i presume Xen Enterprise behaves differently to Xen. Does anyone have any success with libvirt and Xen Enterprise ? thanks for any tips/experience -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] Re: ruby-libvirt on debian based systems
Hi,
Solved, i had to install libxen3-dev in order to make it work.
Thanks anyways :-)
On Fri, Jul 18, 2008 at 10:22 PM, Tom Verhaeghe [EMAIL PROTECTED]
wrote:
Hello
I don't know if ruby-libvirt can work in a debian-based environment. I
installed kvm, libvirt, RoR, etc on Ubuntu and it all works fine.
I pasted the output when installing the gem below. I think the problem
could be that libvirt is called differently in Ubuntu or stored on a
different location. Is there a way to get around?
Thanks in advance
Tom
Building native extensions. This could take a while...
ERROR: While executing gem ... (RuntimeError)
Error instaling ruby-libvirt-0.0.7.gem:
ERROR: Failed to build gem native extension.
ruby extconf.rb install ruby-libvirt-0.0.7.gem
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of
necessary libraries and/or headers. Check the mkmf.log file for more
details. You may need configuration options.
Provided configuration options:
--with-opt-dir
--without-opt-dir
--with-opt-include
--without-opt-include=${opt-dir}/include
--with-opt-lib
--without-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
--srcdir=.
--curdir
--ruby=/usr/bin/ruby1.8
--with-_libvirt-dir
--without-_libvirt-dir
--with-_libvirt-include
--without-_libvirt-include=${_libvirt-dir}/include
--with-_libvirt-lib
--without-_libvirt-lib=${_libvirt-dir}/lib
--with-libvirt-config
--without-libvirt-config
--with-pkg-config
--without-pkg-config
extconf.rb:16: libvirt not found (RuntimeError)
Gem files will remain installed in
/var/lib/gems/1.8/gems/ruby-libvirt-0.0.7 for inspection.
Results logged to
/var/lib/gems/1.8/gems/ruby-libvirt-0.0.7/ext/libvirt/gem_make.out
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] Re: ruby-libvirt on debian based systems
Yes it does, it works like a train on rails 2.0.2 ruby 1.8.6 I'll keep you in touch if anything goes wrong On Tue, Jul 22, 2008 at 1:19 AM, David Lutterkort [EMAIL PROTECTED] wrote: On Mon, 2008-07-21 at 16:48 +0200, Tom Verhaeghe wrote: Solved, i had to install libxen3-dev in order to make it work. I assume that that contains the pkgconfig for libvirt; the extconf.rb in ruby-libvirt needs that. With that ruby-libvirt works fine on Ubuntu ? I am glad to hear that. David -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] ruby-libvirt on debian based systems
Hello
I don't know if ruby-libvirt can work in a debian-based environment. I
installed kvm, libvirt, RoR, etc on Ubuntu and it all works fine.
I pasted the output when installing the gem below. I think the problem
could be that libvirt is called differently in Ubuntu or stored on a
different location. Is there a way to get around?
Thanks in advance
Tom
Building native extensions. This could take a while...
ERROR: While executing gem ... (RuntimeError)
Error instaling ruby-libvirt-0.0.7.gem:
ERROR: Failed to build gem native extension.
ruby extconf.rb install ruby-libvirt-0.0.7.gem
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of
necessary libraries and/or headers. Check the mkmf.log file for more
details. You may need configuration options.
Provided configuration options:
--with-opt-dir
--without-opt-dir
--with-opt-include
--without-opt-include=${opt-dir}/include
--with-opt-lib
--without-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
--srcdir=.
--curdir
--ruby=/usr/bin/ruby1.8
--with-_libvirt-dir
--without-_libvirt-dir
--with-_libvirt-include
--without-_libvirt-include=${_libvirt-dir}/include
--with-_libvirt-lib
--without-_libvirt-lib=${_libvirt-dir}/lib
--with-libvirt-config
--without-libvirt-config
--with-pkg-config
--without-pkg-config
extconf.rb:16: libvirt not found (RuntimeError)
Gem files will remain installed in /var/lib/gems/1.8/gems/ruby-libvirt-0.0.7
for inspection.
Results logged to
/var/lib/gems/1.8/gems/ruby-libvirt-0.0.7/ext/libvirt/gem_make.out
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
Re: [Libvir] build problems on RHEL5, at least some are now fixed
All versions of libvirt should build successfully with RHEL-5. It is one of our supported platforms - we intend to support any Linux distro with software of RHEL-5 vintage or later. ok thanks - i will give that a go -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [Libvir] build problems on RHEL5, at least some are now fixed
I've tested on RHEL-5 it works as expected now. can you let me know which version of libvirt builds on RHEL5 please as i have been having nightmare getting the src rpm to build - Or does anyone have a recent libvirt for RHEL5 as i could do with it to go with Xen 3.2 thanks -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
