similar to: Hotplug/hotadd functionality of libvirt?

Hi, Look under examples: http://builder.virt-tools.org/artifacts/libvirt-virshcmdref/html/sect-attach-disk.html (root at h2)-(/)# virsh attach-disk vps_99 /dev/nbd2 vdb --address pci:0000.00.11.0 --persistent *error: command 'attach-disk' doesn't support option --address* (root at h2)-(/)# virsh --version 0.7.5 Is someone playing a trick on me? Regards, Daniele -------------- next

On 09/02/2010 07:51 PM, Dan Gohman wrote: > > On Sep 2, 2010, at 10:03 AM, Kees van Reeuwijk wrote: > >> - snprintf(buf, PATH_MAX, "%s//%s", dir, bin); > > There's no comment, and no mention in the commit message. > It seems pretty safe to fix. > >> Also, the if-all-else-fails return value of GetMainExecutable is an empty path, but since the users of

Hi, The attached patch ensures that GetMainExecutable function in llvm-trunk/lib/System/Unix/Path.inc also works on Minix. I'm not sure it should be applied unmodified, because there may be controversial changes in it. In particular, one of the things it changes is this: - snprintf(buf, PATH_MAX, "%s//%s", dir, bin); + snprintf(buf, PATH_MAX, "%s/%s", dir, bin); in

On Sep 2, 2010, at 10:03 AM, Kees van Reeuwijk wrote: > - snprintf(buf, PATH_MAX, "%s//%s", dir, bin); There's no comment, and no mention in the commit message. It seems pretty safe to fix. > Also, the if-all-else-fails return value of GetMainExecutable is an empty path, but since the users of this function don't test for that, this choice leads to rather obscure

Hello, I think I have come across an inconsistency between gcc and clang/llvm with respect to returning small structs. Given the following code: > struct s { > int a; > int b; > }; > > struct s3 { > int a; > int b; > int c; > }; > > struct s new_s(int v){ > struct s res; > res.a = v; > res.b = -v; > return res;

Hello, Does KVM support hotadd memory and hot-plug cpu? I checked it using the virsh command but I can only increase the memory to the maximum memory that is initially set But setmaxmem command is failing. Which means this require a reboot of the guest # virsh setmaxmem 4 1048576 error: Unable to change MaxMemorySize error: Requested operation is not valid: cannot resize the maximum memory on

I just noticed the entries on attach-disk and attach-devices are a bit on the empty size. As I am just attaching a usb device to one of my vm clients, I was wondering if I could offer examples to those entries.

Hi Kees, You added some support for Minix to LLVM's copy of googletest: http://llvm.org/viewvc/llvm-project?view=rev&revision=100895 Is it still being used? If so, would you mind pushing these patches upstream to the googletest project: http://code.google.com/p/googletest/ Otherwise we may drop them, because it makes it harder to import new releases of googletest into the LLVM

I am wondering what the default value for migrate-setmaxdowntime is when using QEMU/KVM. http://builder.virt-tools.org/artifacts/libvirt-virshcmdref/html/sect-migrate-setmaxdowntime.html Is the default the same as QEMU's default in this case? I was looking at libvirts source and it appears there is no default set within libvirt, unless I missed it. I do see

Hey everyone, Can anyone explain the scedinfo parameters? I am wondering if I can use this, (along with host side niceness scheduler tweaks) to cause vCPUs to dominate the total time of the CPUs they are pinned to. Here are the sched info parameters: Scheduler : posix cpu_shares : 0 vcpu_period : 0 vcpu_quota : 0 emulator_period: 0 emulator_quota : 0 The documentation (

On 27 July 2011 11:20, dr. ir. Kees van Reeuwijk <reeuwijk at few.vu.nl> wrote: > At the time I submitted  those patches I also submitted them to googletest. As far as I know they got accepted, although I didn't verify that. OK, I see from this thread: http://groups.google.com/group/googletestframework/browse_thread/thread/3081a14965764366/332ce9869f4bbe31 ... that rather than add

Hi list, According to the libvirt documentation [1] "Show maximum number of virtual CPUs for guest domains on this connection" This may not be a complete definition. My first guess from the above was that this returns the number of virtual CPUs that can exist at the same time on the host, either one or several VMs. In fact it returned 16 in my fedora 20 desktop running with KVM,

Hello Everyone, I have set up a xen server with 10 physical network devices using the bridge mode of XEN. This is because I want to split and separate the network traffic for security reasons. Maybe the best way is to use pci back hide. But I want to understand what is going on here. For all testings I have only activated eth[0-3]. My first tests were successful. I have created a VM using

Hi! I'm new to libvirt and face problems connecting to an iSCSI target. What I intend to do is to connect libvirt (I tried virt-manager and virsh) to an iSCSI target and then boot from the LUNs which contain the VMs. I followed the documentation¹ but got stuck at section 12.1.5.4.3. 1) virsh pool-define-as \ --name foo \ --type iscsi

Package: xen-hypervisor-4.1-i386 Version: 4.1.1-1 Severity: important Tags: wheezy I cannot boot a domU with networking after installing the package. root at topsail:~# xm create /etc/xen/udevtest.cfg -c root at topsail:~# Error: Device 0 (vif) could not be connected. Hotplug scripts not working. [2011-08-03 15:56:53 4411] DEBUG (DevController:139) Waiting for devices tap2. [2011-08-03

We are using samba 3.4.8. We have some pc's using OS Windows XP Pro dan others Windows 7 Pro. All of them can join and logon domain to samba PDC + LDAP. FYI, the windows 7 clients are already hacked at registry settings: [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters] "DNSNameResolutionRequired"=dword:00000000

Hi, In RHEL5/6 we have been able to create bridges on our hyper-visor of a number of vlans (eg. em1 -> em1.483 -> br483) We would be able to see this br483 in the virt-manager drop down network choice at the end of creating a new host. On RHEL7 we are not using NetworkManager per the documentation[0] for bridges (and because it is not worth it). So a RHEL7 virt-manager (0.10.0) when

I believe there has been a bug in KRL signature verification that has been present since the KRL feature was first introduced. It prevents signed KRLs from being loaded by OpenSSH [0]. I believe this bug applies to all versions of OpenSSH, although the majority of my effort has been devoted to (and all of my code snippets come from) openssl-portable. The bug is that an offset is incorrectly

On 04/29/2017 06:50 AM, Gregory P. Ennis wrote: > about 4 years ago, I tried to install CentOS 6 on a Supermicro server > with SCSI drives using a LSI raid system. Red Hat does discontinue support for some storage driver for very old hardware when they start a new release series. For EL6, that list is here:

This is, I guess, version 3 of this patch series which adds disk labels and hotplugging (only hot-add implemented so far). The good news is .. it works! Rich.