diff options
Diffstat (limited to '')
| -rw-r--r-- | results/classifier/108/other/1261 | 40 | ||||
| -rw-r--r-- | results/classifier/108/other/1261320 | 62 | ||||
| -rw-r--r-- | results/classifier/108/other/1261450 | 113 | ||||
| -rw-r--r-- | results/classifier/108/other/1261743 | 35 |
4 files changed, 250 insertions, 0 deletions
diff --git a/results/classifier/108/other/1261 b/results/classifier/108/other/1261 new file mode 100644 index 000000000..a08f63c86 --- /dev/null +++ b/results/classifier/108/other/1261 @@ -0,0 +1,40 @@ +graphic: 0.797 +files: 0.784 +device: 0.741 +semantic: 0.622 +performance: 0.497 +PID: 0.469 +network: 0.462 +debug: 0.376 +socket: 0.376 +other: 0.277 +vnc: 0.221 +boot: 0.127 +permissions: 0.125 +KVM: 0.063 + +qemu-user syscall 439 (faccessat2) not implemented - loongarch64 +Description of problem: +On LoongArch64 architecture faccessat syscall is missing and only faccessat2 is present, but it is not handled in linux-user/syscall +Steps to reproduce: +1. Launch a simple bash test script (call it test.sh): if [[ -r test.sh ]] ; then echo OK ; else echo ERROR ; fi +2. The result is "ERROR" even if the file "test.sh" exists and it is readeable +3. The correct result should be "OK" +Additional information: +test.sh: + ``` + if [[ -r test.sh ]] ; then echo OK ; else echo ERROR ; fi + ``` +qemu-loongarch -strace log: + ``` +[...] +12579 statx(255,"",AT_EMPTY_PATH|AT_NO_AUTOMOUNT,STATX_BASIC_STATS,0x0000004000802a50) = 0 +12579 lseek(255,0,SEEK_CUR) = 0 +12579 read(255,0x2016d490,56) = 56 +12579 Unknown syscall 439 +12579 write(1,0x20172010,6) = 6 +12579 read(255,0x2016d490,56) = 0 +12579 rt_sigprocmask(SIG_BLOCK,0x0000004000802b60,0x0000004000802be0) = 0 +12579 rt_sigprocmask(SIG_SETMASK,0x0000004000802be0,NULL) = 0 +12579 exit_group(0) + ``` diff --git a/results/classifier/108/other/1261320 b/results/classifier/108/other/1261320 new file mode 100644 index 000000000..c2fd31f83 --- /dev/null +++ b/results/classifier/108/other/1261320 @@ -0,0 +1,62 @@ +performance: 0.649 +other: 0.560 +semantic: 0.468 +device: 0.459 +PID: 0.389 +graphic: 0.364 +socket: 0.275 +permissions: 0.269 +files: 0.263 +boot: 0.246 +KVM: 0.231 +vnc: 0.218 +network: 0.197 +debug: 0.196 + +Virtual Disk with over 16TB + +Hi, + +is there a option to create a disk for a vm with a size over 16TB. + +the problem that after the diskfile reach 16TB, the disk get a state of read-only at this limit. +I know, that 16TB file size is max, is there a option to create the disk in mutliple files? +we want to use 22 TB. in the VM + +To attach a partition directly to the vm, is not what we want to do. + +best regards + +Chris + +On Mon, Dec 16, 2013 at 09:37:34AM -0000, Chris Weltzien wrote: +> is there a option to create a disk for a vm with a size over 16TB. +> +> the problem that after the diskfile reach 16TB, the disk get a state of read-only at this limit. +> I know, that 16TB file size is max, is there a option to create the disk in mutliple files? +> we want to use 22 TB. in the VM + +Basically no, not in a clean way for a production VM. Can you attach +multiple disks to the guest and then use software RAID0 or LVM to get a +22 TB device inside the guest? + +If not, here are some options: +1. Switch to a different file system (XFS is your best bet) +2. Use LVM (and get a slight performance boost for free!) +3. Tweak file system settings (e.g. bigger block size may allow larger +files) + +Stefan + + +Hi Stefan, + +thank you for your response. + +We're decided to only use 16Tb as vhd for the system. + + +best regards + +Chris + diff --git a/results/classifier/108/other/1261450 b/results/classifier/108/other/1261450 new file mode 100644 index 000000000..3dc8be682 --- /dev/null +++ b/results/classifier/108/other/1261450 @@ -0,0 +1,113 @@ +other: 0.972 +graphic: 0.965 +permissions: 0.963 +KVM: 0.960 +PID: 0.958 +vnc: 0.956 +device: 0.955 +network: 0.945 +socket: 0.939 +performance: 0.933 +debug: 0.933 +semantic: 0.919 +files: 0.910 +boot: 0.880 + +libvirtd reload and hooks problem routed-net + +if we do a reload of libvirt, some iptables rules, which are created through /etc/libvirt/hooks/qemu are not working anymore. +Every time a other (one or two,thee) vm is affected. + + +our qemu file: + +#!/bin/bash + + +do_net() { + local status=$2 + local ip=$3 + local in=$4 + local out=$5 + + if [[ ! $status || ! $ip || ! $in || ! $out ]]; then + echo "Not all parameters were passed!" + exit 1 + fi + + if [ "$status" = "stopped" -o "$status" = "reconnect" ]; then + ip route del $ip via 191.255.255.1 dev $out + ip neigh del proxy $ip dev $in + iptables -D FORWARD -i $in -o $out -s 0.0.0.0/0 -d $ip/32 -j ACCEPT + iptables -D FORWARD -i $out -o $in -s $ip/32 -d 0.0.0.0/0 -j ACCEPT + fi + + if [ "$status" = "start" -o "$status" = "reconnect" ]; then + ip route add $ip via 191.255.255.1 dev $out + ip neigh add proxy $ip dev $in + iptables -I FORWARD 4 -i $in -o $out -s 0.0.0.0/0 -d $ip/32 -j ACCEPT + iptables -I FORWARD 4 -i $out -o $in -s $ip/32 -d 0.0.0.0/0 -j ACCEPT + fi +} + +CONF=//etc/libvirt/hooks/vms/* +for file in $CONF +do + guest_ipaddr="" + guest_name="" + type="" + destination="0.0.0.0/0" + + while read line; do + eval $line + done < $file + guest_ipaddrnet=$guest_ipaddr"/32" + for dest in ${destination} + do + if [ "${1}" = "${guest_name}" ]; then + echo "SRC-IP="$guest_ipaddr " " $guest_ipaddrnet " VM="$guest_name " Dest="$dest + if [ "${2}" = "stopped" ]; then + ip route del $guest_ipaddr via 191.255.255.1 dev virbr1 + ip neigh del proxy $guest_ipaddr dev bond0 + iptables -D FORWARD -i bond0 -o virbr1 -s $dest -d $guest_ipaddrnet -j ACCEPT + iptables -D FORWARD -i virbr1 -o bond0 -s $guest_ipaddrnet -d $dest -j ACCEPT + fi + if [ "${2}" = "start" ]; then + ip route add $guest_ipaddr via 191.255.255.1 dev virbr1 + ip neigh add proxy $guest_ipaddr dev bond0 + iptables -I FORWARD 4 -i bond0 -o virbr1 -s $dest -d $guest_ipaddrnet -j ACCEPT + iptables -I FORWARD 4 -i virbr1 -o bond0 -s $guest_ipaddrnet -d $dest -j ACCEPT + fi + if [ "${2}" = "reconnect" ]; then + ip route del $guest_ipaddr via 191.255.255.1 dev virbr1 + ip neigh del proxy $guest_ipaddr dev bond0 + iptables -D FORWARD -i bond0 -o virbr1 -s $dest -d $guest_ipaddrnet -j ACCEPT + iptables -D FORWARD -i virbr1 -o bond0 -s $guest_ipaddrnet -d $dest -j ACCEPT + sleep 1 + ip route add $guest_ipaddr via 191.255.255.1 dev virbr1 + ip neigh add proxy $guest_ipaddr dev bond0 + iptables -I FORWARD 4 -i bond0 -o virbr1 -s $dest -d $guest_ipaddrnet -j ACCEPT + iptables -I FORWARD 4 -i virbr1 -o bond0 -s $guest_ipaddrnet -d $dest -j ACCEPT + fi + fi + done +done + +On Mon, Dec 16, 2013 at 05:00:51PM -0000, Chris Weltzien wrote: +> if we do a reload of libvirt, some iptables rules, which are created through /etc/libvirt/hooks/qemu are not working anymore. +> Every time a other (one or two,thee) vm is affected. + +Please report this to the libvirt project: +http://libvirt.org/bugs.html + +Stefan + + +Hi, + +we have a workaround for that. We´ve add sleep ${RANDOM:0:1}.${RANDOM:-1:1} between the IP Tables rules. The Problem is, that IP tables cannot execute twice or more times simultaneously. + +Cheers Tim + +Closing, since this is not a QEMU bug. + diff --git a/results/classifier/108/other/1261743 b/results/classifier/108/other/1261743 new file mode 100644 index 000000000..a96185bef --- /dev/null +++ b/results/classifier/108/other/1261743 @@ -0,0 +1,35 @@ +device: 0.664 +files: 0.554 +network: 0.552 +performance: 0.520 +socket: 0.511 +vnc: 0.504 +semantic: 0.464 +permissions: 0.453 +PID: 0.438 +graphic: 0.369 +boot: 0.300 +debug: 0.273 +other: 0.231 +KVM: 0.187 + +trace-backend "simple" doesn't support "disable" property of event + +trace-backend "simple" generates wrong eventid in trace/generated-tracers.c after "disable" property occured in trace-events record. + +Result: missing or mixing logs in trace file. + +On Tue, Dec 17, 2013 at 9:19 PM, bkantor <email address hidden> wrote: +> Public bug reported: +> +> trace-backend "simple" generates wrong eventid in trace/generated- +> tracers.c after "disable" property occured in trace-events record. +> +> Result: missing or mixing logs in trace file. + +Thanks for the bug report. I have posted a fix: +http://permalink.gmane.org/gmane.comp.emulators.qemu/250845 + + +I assume Stefan's fix had been included (likely https://git.qemu.org/?p=qemu.git;a=commitdiff;h=736ec1677f1ae7e64f2f ?), so I'm closing this ticket now. But if you still can reproduce this issue, please let us know. + |